[systemd-devel] [ANNOUNCE] systemd v196
Heya, This is a feature release: http://www.freedesktop.org/software/systemd/systemd-196.tar.xz CHANGES WITH 196: * udev gained support for loading additional device properties from an indexed database that is keyed by vendor/product IDs and similar device identifiers. For the beginning this "hwdb" is populated with data from the well-known PCI and USB database, but also includes PNP, ACPI and OID data. In the longer run this indexed database shall grow into becoming the one central database for non-essential userspace device metadata. Previously, data from the PCI/USB database was only attached to select devices, since the lookup was a relatively expensive operation due to O(n) time complexity (with n being the number of entries in the database). Since this is now O(1), we decided to add in this data for all devices where this is available, by default. Note that the indexed database needs to be rebuilt when new data files are installed. To achieve this you need to update your packaging scripts to invoke "udevadm hwdb --update" after installation of hwdb data files. For RPM-based distributions we introduced the new %udev_hwdb_update macro for this purpose. * The Journal gained support for the "Message Catalog", an indexed database to link up additional information with journal entries. For further details please check: http://www.freedesktop.org/wiki/Software/systemd/catalog The indexed message catalog database also needs to be rebuilt after installation of message catalog files. Use "journalctl --update-catalog" for this. For RPM-based distributions we introduced the %journal_catalog_update macro for this purpose. * The Python Journal bindings gained support for the standard Python logging framework. * The Journal API gained new functions for checking whether the underlying file system of a journal file is capable of properly reporting file change notifications, or whether applications that want to reflect journal changes "live" need to recheck journal files continously in appropriate time intervals. * It is now possible to set the "age" field for tmpfiles entries to 0, indicating that files matching this entry shall always be removed when the directories are cleaned up. * coredumpctl gained a new "gdb" verb which invokes gdb right-away on the selected coredump. * There's now support for "hybrid sleep" on kernels that support this, in addition to "suspend" and "hibernate". Use "systemctl hybrid-sleep" to make use of this. * logind's HandleSuspendKey= setting (and related settings) now gained support for a new "lock" setting to simply request the screen lock on all local sessions, instead of actually executing a suspend or hibernation. * systemd will now mount the EFI variables file system by default. * Socket units now gained support for configuration of the SMACK security label. * timedatectl will now output the time of the last and next daylight saving change. * We dropped support for various legacy and distro-specific concepts, such as insserv, early-boot SysV services (i.e. those for non-standard runlevels such as 'b' or 'S') or ArchLinux /etc/rc.conf support. We recommend the distributions who still need support this to either continue to maintain the necessary patches downstream, or find a different solution. (Talk to us if you have questions!) * Various systemd components will now bypass PolicyKit checks for root and otherwise handle properly if PolicyKit is not found to be around. This should fix most issues for PolicyKit-less systems. Quite frankly this should have been this way since day one. It is absolutely our intention to make systemd work fine on PolicyKit-less systems, and we consider it a bug if something doesn't work as it should if PolicyKit is not around. * For embedded systems it is now possible to build udev and systemd without blkid and/or kmod support. * "systemctl switch-root" is now capable of switching root more than once. I.e. in addition to transitions from the initrd to the host OS it is now possible to transition to further OS images from the host. This is useful to implement offline updating tools. * Various other additions have been made to the RPM macros shipped with systemd. Use %udev_rules_update() after i
Re: [systemd-devel] [ANNOUNCE] systemd v196
Hi, Would anyone know why the latest releases no longer work on 3.1 kernels? I tried to update from 187 to 196 today and booting the system on a vendor kernel based on 3.1.10 no longer gets to the boot prompt. It hangs somewhere near where it should actually be spawning a getty on the serial port. Booting systemd 196 on a kernel based on linux-next doesn't have this issue. I've gone over the NEWS entries between 187 and 196, but nothing obvious stood out. Any ideas? Thierry pgp01DItuJdaX.pgp Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [ANNOUNCE] systemd v196
Thierry Reding writes: > Hi, > > Would anyone know why the latest releases no longer work on 3.1 kernels? > I tried to update from 187 to 196 today and booting the system on a > vendor kernel based on 3.1.10 no longer gets to the boot prompt. It > hangs somewhere near where it should actually be spawning a getty on > the serial port. > > Booting systemd 196 on a kernel based on linux-next doesn't have this > issue. I've gone over the NEWS entries between 187 and 196, but nothing > obvious stood out. > > Any ideas? I'm running 196 just fine on a 3.0 vendor kernel, so it's not a universal problem. I also use getty on the serial port, with no local modifications. I believe the requirement for a 3.4 (or something) kernel came in 188 for some logging bits, although I'm not sure. systemd should work just fine without it, though. -- Henrik Grindal Bakken PGP ID: 8D436E52 Fingerprint: 131D 9590 F0CF 47EF 7963 02AF 9236 D25A 8D43 6E52 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [ANNOUNCE] systemd v196
On Fri, Nov 23, 2012 at 10:29:53AM +0100, Henrik Grindal Bakken wrote: > > Any ideas? > > I'm running 196 just fine on a 3.0 vendor kernel, so it's not a > universal problem. I also use getty on the serial port, with no local > modifications. > > I believe the requirement for a 3.4 (or something) kernel came in 188 > for some logging bits, although I'm not sure. systemd should work > just fine without it, though. v189 NEWS: * Support for reading kernel messages from /proc/kmsg has now been removed. If you want kernel messages in the journal make sure to run a recent kernel (>= 3.5) that supports reading structured messages from /dev/kmsg (see above). -- Tomasz TorczThere exists no separation between gods and men: xmpp: zdzich...@chrome.pl one blends softly casual into the other. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [ANNOUNCE] systemd v196
On Fri, Nov 23, 2012 at 10:29:53AM +0100, Henrik Grindal Bakken wrote: > Thierry Reding writes: > > > Hi, > > > > Would anyone know why the latest releases no longer work on 3.1 kernels? > > I tried to update from 187 to 196 today and booting the system on a > > vendor kernel based on 3.1.10 no longer gets to the boot prompt. It > > hangs somewhere near where it should actually be spawning a getty on > > the serial port. > > > > Booting systemd 196 on a kernel based on linux-next doesn't have this > > issue. I've gone over the NEWS entries between 187 and 196, but nothing > > obvious stood out. > > > > Any ideas? > > I'm running 196 just fine on a 3.0 vendor kernel, so it's not a > universal problem. I also use getty on the serial port, with no local > modifications. > > I believe the requirement for a 3.4 (or something) kernel came in 188 > for some logging bits, although I'm not sure. systemd should work > just fine without it, though. Okay, maybe there's an issue with this particular version of the kernel or something's odd with my configuration. I'll have to dig deeper. Thanks for the information. Thierry pgpqfoyZHu51D.pgp Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [ANNOUNCE] systemd v196
On Fri, Nov 23, 2012 at 10:41:20AM +0100, Tomasz Torcz wrote: > On Fri, Nov 23, 2012 at 10:29:53AM +0100, Henrik Grindal Bakken wrote: > > > Any ideas? > > > > I'm running 196 just fine on a 3.0 vendor kernel, so it's not a > > universal problem. I also use getty on the serial port, with no local > > modifications. > > > > I believe the requirement for a 3.4 (or something) kernel came in 188 > > for some logging bits, although I'm not sure. systemd should work > > just fine without it, though. > > v189 NEWS: > > * Support for reading kernel messages from /proc/kmsg has now >been removed. If you want kernel messages in the journal >make sure to run a recent kernel (>= 3.5) that supports >reading structured messages from /dev/kmsg (see above). Okay, that doesn't sound very much like a general incompatibility. The way I read that, the worst that will happen on older kernels is that kernel messages don't make it to the journal. But the boot process shouldn't be hanging because of it. Thierry pgp7PBZnrWkMu.pgp Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
