Hi Jaroslav, I would like to raise a caution about implementing this change. Several other non-Linux systems are able to handle a variety of hardware changes after installation, and still boot afterwards. I think it would be unfortunate if, after changing hardware, it were not possible to boot other than with a rescue image. Hardware is becoming faster, and even on our small ARM boards, initramfs size is not such a huge problem, especially in the medium term.
Jon. -- Sent from my iPad On Jan 29, 2013, at 10:00, Jaroslav Reznik <jrez...@redhat.com> wrote: > = Features/DracutHostOnly = > https://fedoraproject.org/wiki/Features/DracutHostOnly > > Feature owner(s): Harald Hoyer <har...@redhat.com> > > Only create "host-only" initramfs images. A generic fallback image should be > installed by anaconda on installation/update and never ever be removed. > > == Detailed description == > Current initramfs images contain most of the kernel drivers to boot from any > hardware. This results in a very big initramfs, which takes a long time to > load on system start and a long time to create on kernel updates. Switching > to > host-only will improve the situation. To cope with hardware change, a boot > entry "Rescue System" should be installed with a full fledged initramfs also > containing debug tools. This boot entry can then be used to recover from > hardware changes and also from unforseen software failure after updates. > _______________________________________________ > devel-announce mailing list > devel-annou...@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel-announce > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
