Timeline for Will mounting my disk as "ro" make it completely read-only?
Current License: CC BY-SA 2.5
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 20, 2011 at 19:58 | comment | added | Hello71 | "Disks and partitions are only accessible by root unless you've explicitly changed this" Not entirely correct. With the capabilities system, a process can have access to raw I/O while still running as a standard user. However, with a standard kernel and base system, the only thing that can grant capabilities is processes run by root. In other words, only root has CAP_SETPCAP. | |
| Aug 25, 2010 at 0:36 | vote | accept | Pylsa | ||
| Aug 20, 2010 at 13:15 | comment | added | sleske |
@BlookPhilia: I'm fairly certain noload is specific to ext3. No idea if there's an equivalten for NTFS.
|
|
| Aug 20, 2010 at 12:59 | vote | accept | Pylsa | ||
| Aug 20, 2010 at 12:59 | |||||
| Aug 20, 2010 at 12:56 | comment | added | Pylsa |
@sleske But will I need noload for NTFS too?
|
|
| Aug 20, 2010 at 0:29 | comment | added | Gilles 'SO- stop being evil' |
@sleske: Thanks for the tip! I found that one the hard way, I wish noload had (existed|been documented) then...
|
|
| Aug 20, 2010 at 0:19 | comment | added | Pylsa | @sleske Yet, I'm trying to mount an NTFS system, not an extended one ;) | |
| Aug 20, 2010 at 0:04 | comment | added | sleske | Actually you can mount ext3 without modifying it using options "ro,noload" (from Documentation/filesystems/ext3.txt in the Linux docs). The docs note, however, that this can lead to "various problems"... | |
| Aug 20, 2010 at 0:01 | comment | added | sleske | +1 for "mounting itself might write to the disk": I never thought about that (though it's logical in retrospect). | |
| Aug 19, 2010 at 23:47 | history | answered | Gilles 'SO- stop being evil' | CC BY-SA 2.5 |