Documentation Boot Beat

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Faster boot with host-only initramfs: Copy from the feature page was much better than mine, we'll use that.)
Line 1: Line 1:
 
{{header|docs}}
 
{{header|docs}}
{{Docs_beat_open}}
+
{{Docs_beat_closed}}
  
 
= Faster boot with host-only initramfs =
 
= Faster boot with host-only initramfs =

Revision as of 04:59, 8 May 2013

DocsProject Header docTeam1.png
Warning (medium size).png
Beat Closed on Wiki
Work on beats has now moved to git. If you have changes or additions, please contact the docs team via #fedora-docs, docs@lists.fp.o, or with the fedora-release-notes BZ component.


Contents

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.