Recent Features
| |||||||||||||
The case for the /usr mergeThe case for the /usr mergePosted Jan 27, 2012 1:53 UTC (Fri) by rgmoore (subscriber, #75)In reply to: The case for the /usr merge by josh Parent article: The case for the /usr merge
Or a root filesystem on LVM, software RAID, or any other kind of complicated filesystem the bootloader can't understand. Although it looks as though GRUB2 is smart enough to get all those systems (including encrypted filesystems), so maybe separate /boot partitions are going to be as unnecessary as separate /bin, /sbin, and /lib directories.
(Log in to post comments)
The case for the /usr merge Posted Jan 27, 2012 4:49 UTC (Fri) by jackb (subscriber, #41909) [Link]
Is it possible to install grub 2 on a hard drive that has a LUKS header instead of a partition table?
The case for the /usr merge Posted Jan 27, 2012 9:54 UTC (Fri) by jengelh (subscriber, #33263) [Link]
There is no bootblock hole like there is on ext2, so the answer is no.
The case for the /usr merge Posted Jan 30, 2012 19:13 UTC (Mon) by blitzkrieg3 (subscriber, #57873) [Link]
Not _instead_ of, but you could get grub to read your partition table and then read the luks volume inside the partition.
The case for the /usr merge Posted Jan 27, 2012 9:01 UTC (Fri) by job (guest, #670) [Link]
I think it's much more common to utilize an initrd to boot from encrypted or DMed filesystems. At least all the normal distros do it that way.
The case for the /usr merge Posted Jan 30, 2012 19:16 UTC (Mon) by blitzkrieg3 (subscriber, #57873) [Link]
Initrd and separate /boot are two separate things. You could have the initrd on a / file system in your /boot directory, as you can have a separate /boot partition that just tells linux to load / on another partition and execute /bin/init there.
|
|||||||||||||