[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: /boot is readonly file system -why?



On Sat, 2004-03-20 at 18:49, Kenneth Macdoald Karlsen wrote:
> edit fstab eg:
> /dev/hdxx       /boot           ext3    defaults     0      2
>  lsof |grep /boot
> kill process that locks boot (eg klogd)
> umount and remount
> or else you have to reboot.

Not so.

First of all, you are correct that /boot is mounted read-only in
accordance with /etc/fstab's settings. This is done because it contains
data that is very important to the function of the system, and being
read-only makes it very hard to accidentally damage it.

That said, you do need to open it to writing any time a package with
files there is updated or installed. To do this without unmounting or
rebooting:

$ mount -o remount,rw /boot

And proceed with the install. After installation is complete, return
/boot to it's original state. (You don't really have to, but again, it's
a good idea to protect that critical data).

$ mount -o remount,ro /boot

If anything about this options isn't obvious, the complete descriptions
will be in `man mount`.

-- 
Jeremy Nickurak -= Email/Jabber: atrus@rifetech.com =-
Remember, when you buy major label CD's, you're paying
companies to sue families and independant music. Learn
more now at downhillbattle.org.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: