Adam Williamson composed on 2015-01-22 13:36 (UTC-0800): > 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. No comment on /var. Not mounting as boot a partition containing kernels and/or initrds in its root I could understand and agree with, but not forced reformatting. >From my experience with the various distros' utilities responsible for installing and updating kernels and initrds I see sharing a /boot partition as a virtual demand for the trouble like that described in bug 1074358. As long as kernels, initrds and the normal files accompanying them in /boot are not present, other content should be allowed to remain. If any such are present, it should be OK to wipe them away, but not format, which would lose both content Anaconda should have no need to care about (which might include an installation and/or rescue image), and a UUID one or more prior installations are probably depending on. > 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? Whether others might see what I do as sensible I can't say, but what I do for a first OS installation on a BIOS with software RAID system, I: 1-partition 2-format non-RAID partition(s) 3-install Grub to master/realboot primary partition 4-copy small number of scripts & binaries to one or more subdirectories on realboot 5-install sans bootloader 1st "OS", mounting realboot partition on /boot Before a 2nd OS installation, I reconfigure fstab on the original by mounting realboot elsewhere, let /boot fall on /, and copy the appropriate content to the new /boot location. Next installations get no bootloader installed and have /boot on respective /. I copy their kernels and initrds to realboot and add them to my personally managed custom bootloader menu on realboot. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
