Jelenlegi hely


LibreOffice 5.4.2 - 2017, október 5 - 16:42

LibreOffice 5.4.2 is now available, and includes over 100 bugfixes since the previous release:

— LibreOffice (@libreoffice) October 5, 2017

Elérhető a LibreOffice 5.4.2-es kiadása. Részletek a bejelentésben.

Kategóriák: Informatika

Bemutatkozik a Google Pixel 2 és Pixel 2 XL - 2017, október 5 - 14:30

Back with the highest-rated smartphone camera ever, meet the new Google Pixel 2 and Pixel 2 XL → #madebygoogle

— Google (@Google) October 4, 2017

Részletek itt.

Kategóriák: Informatika

1 millió dollárnál a Librem 5 kampánya - 2017, október 5 - 14:12

1 millió dollárnál (68,36%) a #Librem5 kampánya, még 18 nap van hátra #mobilephone #security #privacy— HUP (@huphu) October 5, 2017 #onhup

Részletek a kampányoldalon.

Kategóriák: Informatika

Melyik IT céget utálod a legjobban? - 2017, október 5 - 14:10
Kategóriák: Informatika

pgAdmin 4 v2.0 Released - 2017, október 5 - 02:00

The pgAdmin Development Team are pleased to announce pgAdmin 4 version 2.0, the most popular graphical administration and management tool for the PostgreSQL database.

This release of pgAdmin 4 includes over 70 bug fixes and new features. For more details please see the release notes.

Notable changes in this release include:

  • PostgreSQL and EDB Advanced Server 10 support, including table partitioning
  • An updated icon set and embedded fonts for consistent look and feel on all platforms
  • Significant speed enhancements, particularly at startup time
  • Out-of-the-box ability to run in either server or desktop mode with no additional configuration changes required
  • Support for SSL certificate based authentication
  • Detailed display of server status info on the dashboards, with options to cancel queries and terminate sessions

For more information, please see the website

Download your copy here

Kategóriák: Informatika

PostgreSQL 10 Released - 2017, október 5 - 02:00

The PostgreSQL Global Development Group today announced the release of PostgreSQL 10, the latest version of the world's most advanced open source database.

A critical feature of modern workloads is the ability to distribute data across many nodes for faster access, management, and analysis, which is also known as a "divide and conquer" strategy. The PostgreSQL 10 release includes significant enhancements to effectively implement the divide and conquer strategy, including native logical replication, declarative table partitioning, and improved query parallelism.

"Our developer community focused on building features that would take advantage of modern infrastructure setups for distributing workloads," said Magnus Hagander, a core team member of the PostgreSQL Global Development Group. "Features such as logical replication and improved query parallelism represent years of work and demonstrate the continued dedication of the community to ensuring Postgres leadership as technology demands evolve."

This release also marks the change of the versioning scheme for PostgreSQL to a "x.y" format. This means the next minor release of PostgreSQL will be 10.1 and the next major release will be 11.

Logical Replication - A publish/subscribe framework for distributing data

Logical replication extends the current replication features of PostgreSQL with the ability to send modifications on a per-database and per-table level to different PostgreSQL databases. Users can now fine-tune the data replicated to various database clusters and will have the ability to perform zero-downtime upgrades to future major PostgreSQL versions.

"We have been heavily using PostgreSQL since 9.3 and are very excited about version 10 since it brings basis for long-awaited partitioning and built-in logical replication. It will allow us to use PostgreSQL in even more services," said Vladimir Borodin, DBA Team Lead at Yandex.

Declarative Table Partitioning - Convenience in dividing your data

Table partitioning has existed for years in PostgreSQL but required a user to maintain a nontrivial set of rules and triggers for the partitioning to work. PostgreSQL 10 introduces a table partitioning syntax that lets users easily create and maintain range and list partitioned tables. The addition of the partitioning syntax is the first step in a series of planned features to provide a robust partitioning framework within PostgreSQL.

Improved Query Parallelism - Quickly conquer your analysis

PostgreSQL 10 provides better support for parallelized queries by allowing more parts of the query execution process to be parallelized. Improvements include additional types of data scans that are parallelized as well as optimizations when the data is recombined, such as pre-sorting. These enhancements allow results to be returned more quickly.

Quorum Commit for Synchronous Replication - Distribute data with confidence

PostgreSQL 10 introduces quorum commit for synchronous replication, which allows for flexibility in how a primary database receives acknowledgement that changes were successfully written to remote replicas. An administrator can now specify that if any number of replicas has acknowledged that a change to the database has been made, then the data can be considered safely written.

"Quorum commit for synchronous replication in PostgreSQL 10 gives more options to extend our ability to promote database infrastructure with nearly zero downtime from the application perspective. This allows us to continuously deploy and update our database infrastructure without incurring long maintenance windows," said Curt Micol, Staff Infrastructure Engineer at Simple Finance.

SCRAM-SHA-256 authentication - Secure your data access

The Salted Challenge Response Authentication Mechanism (SCRAM) defined in RFC5802 defines a protocol to improve upon the secure storage and transmission of passwords by providing a framework for strong password negotiation. PostgreSQL 10 introduces the SCRAM-SHA-256 authentication method, defined in RFC7677, to provide better security than the existing MD5-based password authentication method.

Links About PostgreSQL

PostgreSQL is the world's most advanced open source database, with a global community of thousands of users, contributors, companies and organizations. The PostgreSQL Project builds on over 30 years of engineering, starting at the University of California, Berkeley, and has continued with an unmatched pace of development. PostgreSQL's mature feature set not only matches top proprietary database systems, but exceeds them in advanced database features, extensibility, security and stability. Learn more about PostgreSQL and participate in our community at

Kategóriák: Informatika

hypopg 1.1.0 released - 2017, október 5 - 02:00

Version 1.1.0 of hypopg has just been released.

hypopg is a PostgreSQL extension adding support for hypothetical indexes.

An hypothetical, or virtual, index is an index that doesn't really exist, and thus doesn't cost CPU, disk, or any resource to create. They're useful to know if specific indexes might increase performance for problematic queries, since you could know if PostgreSQL will use these indexes or not without having to spend resources to create them.

This release adds support for hypothetical indexes on expression, an hypopg_get_indexdef() function to get the SQL command that will create the real index corresponding to a stored hypothetical index, PostgreSQL 10 compatiiblity, and bug fixes.

Please see the changelog for more details.

Many thanks to Andrew Kane and Rob Stolarz for reporting issues.

Source repository:

Kategóriák: Informatika

drupal 8.4.0 - 2017, október 4 - 21:44
Release notesDrush users: Update to Drush 8.1.12

Versions of Drush earlier than 8.1.12 will not work with Drupal 8.4.x. Update Drush to 8.1.12 or higher before using it to update to Drupal core 8.4.x or you will encounter fatal errors that prevent updates from running. (Drush 8.1.12 and 8.1.13 will successfully update Drupal 8.3.x to 8.4.0, but users may still see other error messages after updates have run.)

Updated browser requirements: Internet Explorer 9 and 10 no longer supported

In April 2017, Microsoft discontinued all support for Internet Explorer 9 and 10. Therefore, Drupal 8.4 has as well. Drupal 8.4 still mostly works in these browser versions, but bugs that affect them only will no longer be fixed, and existing workarounds for them will be removed beginning in Drupal 8.5.

Additionally, Drupal 8's browser requirements documentation page currently lists incorrect information regarding very outdated browser versions such as Safari 5 and Firefox 5. Clarifications to the browser policy and documentation are underway.

Known Issues

Drupal 8.4.0 includes major version updates for two dependencies: Symfony 3.2 and jQuery 3. Both updates may introduce backwards compatibility issues for some sites or modules, so test carefully. For more information, see the "Third-party library updates" section below. Known issues related to the Symfony update include:

Important fixes since 8.3.x

Translators should take note of several string additions and changes since the last release.

File usage tracking

Drupal 8 has several longstanding file usage tracking bugs. To prevent further data loss, Drupal 8.4 has disabled the automatic deletion of files with no known remaining usages. This will result of the accumulation of unused files on sites, but ensures that files erroneously reporting 0 usages are not deleted while in use. Additionally, an issue with validation errors when saving content referencing these files has also been resolved.

The change record explains how sites can opt back into marking files temporary. If you choose to enable the setting, you can also set "Delete orphaned files" to "Never" on /admin/config/media/file-system to avoid permanent deletion of the affected files.

While the files will no longer be deleted by default, file usage is still not tracked correctly in several scenarios, regardless of the setting. Discussion on how to evolve the file usage tracking system is underway.

Configuration export sorting Revision data integrity fixes Other critical improvements New stable modules

The following modules, previously considered experimental, are now stable and safe for use on production sites, with full backwards compatibility and upgrade paths from 8.4.0 to future releases:

Datetime Range

The Datetime Range module provides a field type that allows end dates to support contributed modules like Calendar. This stable release is backwards-compatible with the 8.3.x experimental version and shares a consistent API with other Datetime fields.

Future releases may improve Views support, usability, Datetime Range field validation, and REST support. For bugs or feature requests for this module, see the core Datetime issue queue.

Layout Discovery

The Layout Discovery module provides an API for modules or themes to register layouts as well as five common layouts. Providing this API in core enables core and contributed layout solutions to be compatible with each other. This stable release is backwards-compatible with the 8.3.x experimental version and introduces support for per-region attributes.


The new core Media module provides an API for reusable media entities and references. It is based on the contributed Media Entity module.

Since there is a rich ecosystem of Drupal contributed modules built on Media Entity, the top priority for this release is to provide a stable core API and data model for a smoother transition for these modules. Developers and expert site builders can now add Media as a dependency. Work is underway to provide an update path for existing sites' Media Entity data and to port existing contributed modules to the improved core API. Both versions cannot be used at the same time, so we also prevent the 1.x version of the contributed Media Entity module from being enabled at the same time as the core Media module.

Note that the core Media module is currently marked hidden and will not appear on the 'Extend' (module administration) page. (Enabling a contributed module that depends on the core Media module will also enable Media automatically.) The module will be displayed to site builders normally once user experience issues with it are resolved. Similarly, the REST API and normalizations for Media is not final and support for decoupled applications will also be improved in a future release.

Inline Form Errors

The Inline Form Errors module provides a summary of any validation errors at the top of a form and places the individual error messages next to the form elements themselves. This helps users understand which entries need to be fixed, and how. Inline Form Errors was provided as an experimental module from Drupal 8.0.0 on, but it is now stable and polished enough for production use. See the core Inline Form Errors module issue queue for outstanding issues.


The Workflows module provides an abstract system of states (like Draft, Archived, and Published) and transitions between them. Workflows can be used by modules that implement non-publishing workflows (such as for users or products) as well as content publishing workflows.

Drupal 8.4 introduces a final significant backwards compatibility and data model break for this module, moving responsibility for workflow states and transitions from the Workflow entity to the Workflow type plugin. Read Workflow type plugins are now responsible for state and transition schema for full details on the API and data model changes related to this fix. Now that this change is complete, the Workflows module became stable!

While the module can be installed as-is, it is not useful in itself without either Content Moderation and/or some other module that requires it.

Content authoring and site administration improvements REST and API-first improvements Performance and scalability improvements Developer experience improvements Automated testing improvements Third-party library updates Experimental modules Migrate (beta stability)

Migrate provides a general API for migrations. It will be considered completely stable once all issues tagged Migrate critical are resolved.

  • This release includes numerous developer experience improvements for Migrate and Migrate Drupal, including deprecating outdated references to "CCK", simplifying field type mapping, renaming several plugins to better capture their and many other API and documentation improvements. (Backwards compatibility is provided in each case Migrate is in beta.)
  • Added the ability to provide the source module to migrations to help site owners review what data is being migrating, especially for cases where the source and destination module are not the same (for example if a new Drupal 8 module replaces old functionality.
Migrate Drupal and Migrate Drupal UI (alpha stability)

Migrate Drupal module provides API support for Drupal-to-Drupal migrations, and Migrate Drupal UI offers a simple user interface to run migrations from older Drupal versions.

Content Moderation (beta stability)

Content Moderation allows workflows from the Workflows module to be applied to content. Notable improvements in this release:

As per the experimental module process, there were some backwards-incompatible changes since Drupal 8.3.x. Experimental modules do not offer a supported upgrade path, but an unofficial upgrade path is available.

Field Layout (alpha stability)

This module provides the ability for site builders to rearrange fields on content types, block types, etc. into new regions, for both the form and display, on the same forms provided by the normal field user interface. Field Layout has had several bugfixes since 8.3.0, but no significant changes. See the entity display layout roadmap for the next steps for this module, which needs to become stable by 8.5.0 to remain in Drupal core.

Settings Tray (beta stability)

The Settings Tray module allows configuring page elements such as blocks and menus from the frontend of your site. Settings Tray has improved significantly since Drupal 8.3.0, including numerous user interaction and accessibility fixes, better compatibility with stable core modules like Quick Edit and Contextual Links, added documentation, and a CSS reset for better themer experience.

The module reached beta stability following completion of moving the off-canvas dialog renderer into a core component, and renaming the machine name of the module to settings_tray, to match its user-facing name. We hope to make Settings Tray stable by 8.5.0. To track progress, see the "outside in" roadmap issue.

Place Blocks (alpha stability)

This feature allows the user to place a block on any page and see the region where it will be displayed, without having to navigate to a backend administration form. 8.4.0-alpha1 was the deadline for Place Blocks to stabilize, but the module's roadmap was not completed. Furthermore, the module is not intended as a standalone feature and should instead be a built-in part of the Block system. For these reasons, Place Blocks module has been marked hidden in this release (it can still be enabled with Drush). The Place Blocks module itself will be turned into an empty module in Drupal 8.5.x, since ideally the core Block system will offer the same functionality in 8.5.0 (though this depends on completion of a core patch for the feature.)

Download Size md5 hash drupal-8.4.0.tar.gz 12.76 MB 074795a2f5fc0b599a7dcfb9d1fb03f5 21.14 MB 60ed1b57a672366eaa54335621ec89fe Last updated: 4 Oct 2017 at 19:44 UTCOfficial release from tag: 8.4.0Core compatibility: 8.xRelease type: Bug fixesNew featuresShort description: The latest minor release includes new features and backwards-compatible API improvements, and is ready for new development and production sites.Packaged Git sha1: abfe77673a5a6194ef13600e05f1ca2c5dd59db8
Kategóriák: Informatika

Kamerás megfigyelőrendszer QNAP NAS-okra építve (x) - 2017, október 4 - 18:14

Bár a hálózati tárolókat jellemzően első számú felhasználási területük, tehát az adattárolás miatt választják a vásárlók, a NAS-ok egy része számos extra funkciót is kínál. A QNAP esetében több más mellett ilyen a QVR (Quality Surveillance Recording) fantázia névre keresztelt, gyakorlatilag a DVR (Digital Video Recorder), azaz a digitális videó rögzítők kiváltásához fejlesztett képesség. A gyártó ehhez széleskörű támogatással készült, amely több tucat gyártó összesen nagyjából 3000 darab különböző IP kamera modellje mellett egy komplett, kifejezetten a videós megfigyeléshez fejlesztett szoftvert jelent.

Utóbbi súlyát jól mutatja, hogy a QVR Pro néven futó fejlesztés a QNAP NAS-ok operációs rendszerétől elkülönül, a QTS-től elszeparálva fut a videók rögzítése és az azzal kapcsolatos különféle folyamatok. Ez többek között úgy manifesztálódik, hogy a hálózati adattároló a tárhelyet is képes elkülöníteni a felvételek tárolásához, amelynek pontos szabályozását rugalmas keretek között a felhasználóra bízza a szoftver. Így egyszerre akár több különálló diszkre is menthetőek a videofolyamok, sőt, akár minden kamera külön meghajtót kaphat. A rendszer úgy is konfigurálható, hogy az előre beállított esemény (pl. mozgás vagy időkeret) felvételét az elérhető legjobb minőségben SSD-re, a folyamatos, de gyengébb minőségű rögzítést pedig HDD-kre végezze a NAS egyazon időben. Amennyiben a tároló maximális kapacitása kevés lenne, úgy akár egy második NAS-ra is menthetőek a felvételek, amely USB-n, SAS-on, Thunderbolton, illetve LAN-on is csatlakozhat az elsődleges egységhez.

Az egyes eseményekhez különféle akciók is rendelhetőek, a felvétel indítása mellett riasztás is beállítható, a szoftver például azonnali üzenetben (E-mail, SMS, vagy push) értesítheti a felhasználót (vagy felhasználókat), egy eseményhez pedig akár több akció is rendelhető. Utóbb kettő kombinációi meglehetősen egyszerűen, illetve gyakorlatilag teljesen szabadon állíthatóak össze, akár kameránként, egyesével. A rendszer természetesen bármilyen, a rögzítést befolyásoló tényező esetében is képes jelezni, például a hálózati kapcsolat problémája vagy a tárhely szűkössé válása esetében.

A szoftver a Windows és Mac operációs rendszerekkel, valamint természetesen a QNAP HD Stationnel is tökéletesen kompatibilis, a keresztplatform alkalmazás minden esetben egységes, átlátható felületet nyújt. Utóbbihoz sorolható, hogy például egyazon felületen és egy időben lehet visszajátszani a felvételt és nyomon követni az aktuális eseményeket. A felhasználó felület nagy része személyre szabható, néhány beépített elrendezés mellett viszonylag nagy szabadságot nyújt a QVR Pro a csatornák elrendezésénél. Emellett a felvétel vagy a képfolyam egyes részei kiemelhetőek, azaz nagyíthatóak is (ROI - Region of Interest), a Qdewarp funkcióval pedig a halszem vagy széles látószögű kamera képének egyes szekció külön szeletekre bontható így a teljes kép jobban kezelhető, áttekinthető.

A QNAP hálózati tárolók tehát a QVR Próval társítva kiválthatnak egy DVR-t, miközben azokra a szokásos NAS funkció is ugyanúgy rábízhatók, így bizonyos esetekben megtakarítható az önálló digitális videó rögzítő beszerzése, amely kkv-s felhasználás mellett akár otthoni környezetben is kapóra jöhet. A QVR-hez 64 bites processzorral szerelt QNAP NAS szükséges 4 gigabájt rendszermemóriával, az operációs rendszer oldaláról pedig 4.3.0-s vagy újabb QTS és Container Station kell.

(A QNAP Systems megbízásából készített anyag.)

Kategóriák: Informatika

Írd be a naptárba! - 2017, október 4 - 17:55

HWSW mobile! mobiltermék-fejlesztési, fintech és IoT konferencia, 2017. november 29-30. 80 hazai és nemzetközi előadó, workshop nap, early bird jegyek október 18-ig. További részletek »

Kategóriák: Informatika

Elérhető a pkgsrc-2017Q3 - 2017, október 4 - 09:46

pkgsrc-2017Q3 released, celebrating the 20th anniversary of pkgsrc which was created on 20/08/97 from FreeBSD ports

— pkgsrc (@pkgsrc) October 3, 2017 #onhup

A pkgsrc csapat nevében Greg Troxel bejelentette, hogy elérhető a pkgsrc nevű multiplatformos csomagkezelő rendszer 2017. évi hamradik negyedéves kiadása (2017Q3). Ez a pkgsrc 56. negyedévenkénti kiadása. Részletek a bejelentésben.

Kategóriák: Informatika

Magyar kormányzati adatigénylések - Apple vs. Google - 2017, október 2 - 09:50

A magyar állam személyes adatokat kért ki a két nagyvállalattól azok felhasználóiról. Az Apple szinte zokszó nélkül teljesítette a kéréseket, míg a Google egyet sem adott ki. Részletek itt és itt.

Kategóriák: Informatika a Windows Store-ban - 2017, október 2 - 09:43

Paint. NET is in the Windows Store!

— Paul Thurrott (@thurrott) October 1, 2017

Originally intended as a free replacement for the Microsoft Paint software that comes with Windows, it has grown into a powerful yet simple image and photo editor tool. It has been compared to other digital photo editing software packages such as Adobe® Photoshop®, Corel® Paint Shop Pro®, Microsoft Photo Editor, and The GIMP.

Akinek hiányozna a Paint a Windowsból, annak jó hír lehet, a, ami pár dollárért elérhető a Windows Store-ból. Ráadásul most akcióban...

Kategóriák: Informatika

CentOS Seven blog: New CentOS Atomic Release and Kubernetes System Containers Now Available - 2017, augusztus 11 - 20:53

Last week, the CentOS Atomic SIG released an updated version of CentOS Atomic Host (7.1707), a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host.

The release, which came as part of the monthly CentOS release stream, was a modest one, including only a single glibc bugfix update. The next Atomic Host release will be based on the RHEL 7.4 source code and will include support for overlayfs container storage, among other enhancements.

Outside of the Atomic Host itself, the SIG has updated its Kubernetes container images to be usable as system containers. What's more, in addition to the Kubernetes 1.5.x-based containers that derive from RHEL, the Atomic SIG is now producing packages and containers that provide the current 1.7.x version of Kubernetes.

Containerized Master

The downstream release of CentOS Atomic Host ships without the kubernetes-master package built into the image. You can install the master kubernetes components (apiserver, scheduler, and controller-manager) as system containers, using the following commands:

# atomic install --system --system-package=no --name kube-apiserver # atomic install --system --system-package=no --name kube-scheduler # atomic install --system --system-package=no --name kube-controller-manager Kubernetes 1.7.x

The CentOS Virt SIG is now producing Kubernetes 1.7.x rpms, available through this yum repo. The Atomic SIG is maintaining system containers based on these rpms that can be installed as as follows:

on your master # atomic install --system --system-package=no --name kube-apiserver # atomic install --system --system-package=no --name kube-scheduler # atomic install --system --system-package=no --name kube-controller-manager on your node(s) # atomic install --system --system-package=no --name kubelet # atomic install --system --system-package=no --name kube-proxy

Both the 1.5.x and 1.7.x sets of containers have been tested with the kubernetes ansible scripts provided in the upstream contrib repository, and function as drop-in replacements for the installed rpms. If you prefer to run Kubernetes from installed rpms, you can layer the master components onto your Atomic Host image using rpm-ostree package layering with the command: atomic host install kubernetes-master.

The containers referenced in these systemd service files are built in and hosted from the CentOS Community Container Pipeline, based on Dockerfiles from the CentOS-Dockerfiles repository.

Download CentOS Atomic Host

CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. For links to media, see the CentOS wiki.


If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command:

$ sudo atomic host upgrade Release Cycle

The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they're rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them.

Getting Involved

CentOS Atomic Host is produced by the CentOS Atomic SIG, based on upstream work from Project Atomic. If you'd like to work on testing images, help with packaging, documentation -- join us!

The SIG meets every two weeks on Tuesday at 04:00 UTC in #centos-devel, and on the alternating weeks, meets as part of the Project Atomic community meeting at 16:00 UTC on Monday in the #atomic channel. You'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-devel mailing list if you'd like to discuss the direction of Project Atomic, its components, or have other questions.

Kategóriák: Informatika


Theme by me