Bug 28713 – FIX: users often copy kernels to /boot without it being mounted.

• Status: RESOLVED WORKSFORME
• Product: Gentoo Linux

[Description James Harlow (RETIRED) 2003-09-14 10:13:49 UTC]

While having a seperate kernels partition (/boot) is a good idea, it's easy to forget to mount it 
when copying kernels across. If it were made unwritable (chmod 000) in the installation process 
this would not be possible. The permissions of mount points are ignored, so it won't change 
anything in the case of users who never get it wrong. 

Reproducible: Always
Steps to Reproduce:
1. Compile kernel. 
2. Forget to mount boot. 
3. Copy kernel across. 
4. Reboot. 
Actual Results:  
Be confused as to why your "new kernel" isn't working as expected. 

Expected Results:  
Feedback that a silly action was being performed.

[Comment 1 Sven Vermeulen (RETIRED) 2003-09-14 10:21:30 UTC]

This could very well be implemented with the baselayout ebuild. There is no need to have the user "do" extra commands (i.e. use the documentation to fix/enhance).

[Comment 2 James Harlow (RETIRED) 2003-09-14 13:13:44 UTC]

Thanks. Should I submit a new one or can it be reassigned? 

[Comment 3 SpanKY 2003-09-14 13:32:34 UTC]

*** Bug 28723 has been marked as a duplicate of this bug. ***

[Comment 4 Sven Vermeulen (RETIRED) 2003-09-15 01:54:51 UTC]

I'll reassign to azarah.

[Comment 5 Heiko Helmle 2003-09-15 07:29:08 UTC]

Why not mount /boot read-only by default?

[Comment 6 SpanKY 2004-10-15 23:42:45 UTC]

current documentation takes care of all this now i think