Amos Shapira <[email protected]> writes:
> 2009/10/30 Daniel Pittman <[email protected]>
>> Actually, there is a second reason for /boot on a separate partition: until
>> very, very, very recently grub1 shipped with most Linux distributions, and it
>> was a fairly stupid bit of software.
>
> Thanks for the heads up. That's the only reason I keep doing that (a few Mb
> for /boot, rest in one large PV). Won't be relevant for CentOS 5, which is
> what I install on servers every day, but still nice to know I should look
> for it in the desktop/laptop Ubuntu's.
*nod* Personally, it will be a few years before I trust grub2 enough to do
away with the "dead simple" boot partition, and perhaps longer. (Plus, if we
end up with EFI rather than BIOS machines we will need to do it anyway; they
use a FAT partition for the same reason. :)
> Another potential casus-belli: once you use the entire disk as a PV - would
> you still create a partition table with one partition in it? Personally I'd
> do it that way because it helps "label" the disk with something anything can
> read - even a Windows would know that the disk is occupied by *something*.
*nod* That is exactly what I do: partition table, for other systems, one or
two partitions, depending on separate /boot or not, and the rest of the data
inside LVs.
Daniel
Perhaps seasons with a bit of luks or MD software RAID in between the
partition and the PV.
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
Looking for work? Love Perl? In Melbourne, Australia? We are hiring.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
