rw and ro

Hi

re Darrens

Quote:

---

The only gotcha you must remember is to issue a rw before starting otherwise no changes will be made, and after finishing issue a ro to put the file system back to read only.

---

I have frequently wondered:

If one reboots without resetting ro does it matter - presumably the OS reboots into ro?

How does one read the status that the OS is currently in? (Other than attempting to save an Edit?

So is it critical if one forgets to resume ro status?

Quote:

---

Originally Posted by TimesOwn

If one reboots without resetting ro does it matter - presumably the OS reboots into ro?

---

Yes it matters, see below. It will automatically mount root in Read Only

Quote:

---

Originally Posted by TimesOwn

How does one read the status that the OS is currently in? (Other than attempting to save an Edit?

---

[TiVo [p0] ~]# mount
/dev/hda4 on / type ext2 (ro)
/dev/hda9 on /var type ext2 (rw)
/dev/hda2 on /hack type ext2 (rw)
/proc on /proc type proc (rw)

Also shown in TWP

Quote:

---

Originally Posted by TimesOwn

So is it critical if one forgets to resume ro status?

---

Yes, there is a chance of a file becoming corrupted if left in RW when rebooting.

Peter.

PS don't forget /var & /hack are always RW, don't make them RO.