Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by nailer on Friday January 27, 2012 @04:10PM
(#3520180)
It annoys the hell out of me that people are still imposing the 486-era 1024Cyl and 8GB limitations in 2012.
ArchLinux, for example, still really, really wants you to make a /boot.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by triffidhunter on Friday January 27, 2012 @04:18PM
(#3520206)
There are plenty of good reasons to make a /boot. Encrypted laptops for example.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by vacri on Friday January 27, 2012 @06:15PM
(#3520647)
I ran into problems when /boot was part of the larger xfs filesystem, so had to create an ext3 /boot instead.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by sirclueless on Friday January 27, 2012 @07:24PM
(#3520834)
And in general, if you want to use any filesystem that your operating system supports but your bootloader does not, you need a /boot
Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by dredmorbius on Friday January 27, 2012 @05:56PM
(#3520580)
Excellent point, I forgot that use case.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by EvilLook on Monday January 30, 2012 @10:42AM
(#3529160)
People who are serious about having an encrypted system should have absolutely none of the bootstrap process residing unencrypted on the disks of that system because somebody could take out the drive, look through the boot process, and log your passphrase.
I have an encrypted laptop that boots from a read-only USB key that is attached to my keyring. It will only boot from this keyring (and a backup CD-R that I have), and the system and the boot media are never stored together. Before USB keyrings became common, I would have the boot media be a CD-R.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by a1k0n on Friday January 27, 2012 @05:14PM
(#3520428)
These limits are chiefly imposed by the BIOS (int 10h) calls available to a boot sector program (the 512 bytes of machine code you get inside the master boot record of a disk), and require a lot of cleverness to escape from.
This situation has only improved a little. There are still lingering bits of it here and there, depending on how deeply you poke and which distribution you have installed.