|
|
| Line 1: |
Line 1: |
| {{header|docs}} | | {{header|docs}} |
| | {{Docs_beat_open}} |
|
| |
|
|
| |
| = <span style="color:red;">Warning - Beat Converted</span> =
| |
|
| |
| {{admon/warning| Beat has already been converted to XML|Be sure to set Wiki Good to '''*''' and In Publican to '''0''' if this beat is modified}}
| |
|
| |
|
| |
| == systemd ==
| |
|
| |
| '''systemd''' is a system and service manager, replacement for SysVinit and Upstart. After a six months shift, during which it has been more granularly tested, Fedora 15 brings in, by default, a new system daemon whose code is designed from scratch, with the objective to take the maximum advantage offered by modern Linux kernel.
| |
|
| |
| With '''systemd''', Fedora 15 boots-up faster, particularly on SSD; native systemd service configuration files (or units) are much easier to understand and configure compared to sysvinit scripts, as systemd uses <code>.service</code> files instead of bash script; all daemons are sorted into their own Linux cgroups, which you may explore beneath <code>/cgroup/systemd</code> in the file system hierarchy; administrative features of the init system are considerably extended.
| |
|
| |
| Refer to https://fedoraproject.org/wiki/Systemd for more complete information on systemd in Fedora.
| |
|
| |
| == /run directory ==
| |
|
| |
| Fedora 15 has a /run directory for storing runtime data. /run is now a tmpfs, and /var/run is bind mounted to it. /var/lock is bind mounted to /run/lock. Applications can use /run the same way as /var/run. Several programs including udev, dracut, mdadm, mount and initscripts used used hidden directories under /dev for runtime data during early bootup before /var is mounted. However /dev/ is supposed to be used for only device nodes and there is consensus between major distributions to shift to using /run instead. Fedora 15 is leading this change. Details including the benefits are explained [http://lists.fedoraproject.org/pipermail/devel/2011-March/150031.html here].
| |
|
| |
| This change ''is'' compliant with the [http://www.pathname.com/fhs/pub/fhs-2.3.html#THEROOTFILESYSTEM Filesystem Hierarchy Standard], which allows distributions to create new directories in the root hierarchy as long as there is careful consideration of the consequences. Co-author of the latest FHS specification has [https://lwn.net/Articles/436177/ expressed support] for this change. Lennart Poettering has filed a [http://bugs.freestandards.org/show_bug.cgi?id=718 request] to update the FHS standard to include this change as well.
| |
|
| |
| == /var/run and /var/lock ==
| |
|
| |
| /var/run and /var/lock are now bind mounted to /run and /run/lock from tmpfs, and hence emptied on reboot. Applications must ensure to recreate their own files/dirs on startup, and cannot rely that doing this at package installation will suffice. It is possible to use systemd's tmpfiles.d mechanism to recreate directories and files beneath /var/run and /var/lock on boot, if necessary. See tmpfiles.d(5) for details (http://0pointer.de/public/systemd-man/tmpfiles.d.html) and the conf files in /etc/tmpfiles.d for examples of such configuration. Fedora packaging guidelines for tmpfiles.d is at
| |
|
| |
| http://fedoraproject.org/wiki/Packaging:Tmpfiles.d
| |
|
| |
| == 4kB Sector disk boot support ==
| |
|
| |
| Booting 4kB sector disks in UEFI environments is now supported.
| |
|
| |
|
|
| |
|
