Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • 4
    +1 for "mounting itself might write to the disk": I never thought about that (though it's logical in retrospect).
    – sleske
    Commented Aug 20, 2010 at 0:01
  • 2
    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"...
    – sleske
    Commented Aug 20, 2010 at 0:04
  • @sleske Yet, I'm trying to mount an NTFS system, not an extended one ;)
    – Pylsa
    Commented Aug 20, 2010 at 0:19
  • 1
    @BlookPhilia: I'm fairly certain noload is specific to ext3. No idea if there's an equivalten for NTFS.
    – sleske
    Commented Aug 20, 2010 at 13:15
  • 1
    "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.
    – Hello71
    Commented Jul 20, 2011 at 19:58