| 1 |
On 5/18/06, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> It is supposed to have noauto, because /boot does not need to be mounted |
| 3 |
> in the normal course of events. GRUB doesn't use /etc/fstab, it uses |
| 4 |
> grub.conf to find the kernel. The only time you need to mount /boot is |
| 5 |
> when installing a new kernel. |
| 6 |
|
| 7 |
I disagree that it is 'supposed' to have noauto. This could make the |
| 8 |
system more secure, but so could mounting it read-only. Users do |
| 9 |
forget to mount it before updating the kernel, and they get confused |
| 10 |
about why the system isn't booting from their freshly compiled kernel. |
| 11 |
I am sure Maxim is not the only one to do this... |
| 12 |
|
| 13 |
In fact, the current handbook says: |
| 14 |
|
| 15 |
------- |
| 16 |
Code Listing 2: An example /boot line for /etc/fstab |
| 17 |
/dev/hda1 /boot ext2 defaults 1 2 |
| 18 |
|
| 19 |
Some users don't want their /boot partition to be mounted |
| 20 |
automatically to improve their system's security. Those people should |
| 21 |
substitute defaults with noauto. This does mean that you need to |
| 22 |
manually mount this partition every time you want to use it. |
| 23 |
------- |
| 24 |
|
| 25 |
So it seems that 'noauto' is an option for specific users. Not for |
| 26 |
general use... |
| 27 |
|
| 28 |
-Richard |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-user@g.o mailing list |
Archives