From Fedora Project Wiki

(host-only initramfsen)
(→‎Faster boot with host-only initramfs: Copy from the feature page was much better than mine, we'll use that.)
Line 3: Line 3:


= Faster boot with host-only initramfs =
= Faster boot with host-only initramfs =
Fedora's initramfs, a compressed filesystem packed with the resources required to initialize hardware and boot the system, is getting trimmed. Instead of a large file with all possible requirements, the initramfs will contain only resources required for the hardware that actually exists on the system. The resulting system boots and updates faster.
This Fedora release builds an initramfs tailored especially for your computer hardware, allowing faster boot. If you change your machine or significant hardware, you might have to boot with the "Rescue" boot entry and execute "dracut --regenerate-all". If you want your initramfs to be hardware independent, install the "dracut-nohostonly" rpm package. If you don't want rescue images at all (like in virtual machines), install the "dracut-norescue" rpm package.
 
A fully featured initramfs is kept permanently available if needed, such as after the addition of new hardware. To create a new machine-specific initramfs, select the rescue environment from the boot menu and run the command `dracut --regenerate-all`


= systemd =
= systemd =

Revision as of 03:14, 15 April 2013

DocsProject Header docTeam1.png
Note.png
Beat is open
This beat is now ready to have Fedora 25 content added by the beat writer


Faster boot with host-only initramfs

This Fedora release builds an initramfs tailored especially for your computer hardware, allowing faster boot. If you change your machine or significant hardware, you might have to boot with the "Rescue" boot entry and execute "dracut --regenerate-all". If you want your initramfs to be hardware independent, install the "dracut-nohostonly" rpm package. If you don't want rescue images at all (like in virtual machines), install the "dracut-norescue" rpm package.

systemd

Modular service configuration with drop-in files

systemd will now look for configuration directives for a service as /etc/sytemd/system/foobar.service.d/*.conf, making site-specific changes easier to deploy and distribute .

graphing the boot process

- systemd-analyze can now use the GraphViz dot tool to generate graphs of the boot process. GraphViz can be installed with yum install graphviz and will create a representation of the full boot process with systemd-analyze dot | dot -Tsvg > systemd.svg More refined plots can be generated with the optional arguments "--order" "--require" "--from-pattern=" and "--to-pattern="

For more details and examples, see man 1 systemd-analyze.

PrivateTmp

Services with a PrivateTmp= directory defined in their configuration make use of a private temporary directory that is shared by all processes of the service. These temporary files are deleted when the service is stopped.