On Qui, 2015-01-22 at 13:36 -0800, Adam Williamson wrote:
There's a proposed anaconda patch ATM which would disallow
mounting an
existing partition as /boot or /var (or any subdirectory of those
except /var/www ) without reformatting it. i.e., you can't reuse an
existing partition with those mountpoints.
I'm curious to know if anyone / many people do this, and if so, if
there's a particularly good use case for it; if so, we might want to
provide that feedback to the anaconda folks.
There are a few references to using shared /boot on Google, but not
that many, and mostly for crazy multiboot configurations that we
really don't want to be stuck dealing with. Does anyone know of a
really sensible use case for this?
For the record, this is actually re-hooking up code that was used in
oldUI - that is, F17 and earlier - but in oldUI it just produced a
warning you had to click through; the current patch flat disallows it.
The main driving force for this is
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=1074358 , as it
keeps turning out to be annoyingly tricky to make sure that only newly-
installed kernels have their initramfs regenerated when installing to a
shared /boot partition.
My test machine in office got Debian and Fedora and both systems have
same /boot , because /boot can't be on LVM [1], so /boot is just to hold
kernels at boot time for Debian and for Fedora , grub2 from Fedora keeps
boots entries of Debian system .
[1]
/dev/sda2 2048 1026047 500M Linux filesystem
/dev/sda3 1026048 488396799 232,4G Linux LVM
--
Sérgio M. B.