From: Timur Tabi <ttabi@interactivesi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: NTFS safety and lack thereof - Was: Re: Linux 2.4.0ac11
Date: Wed, 24 Jan 2001 11:03:30 -0600 [thread overview]
Message-ID: <20010124170337Z129710-18594+930@vger.kernel.org> (raw)
In-Reply-To: <5.0.2.1.2.20010124162842.00a48720@pop.cus.cam.ac.uk>
In-Reply-To: <E14LOAm-0006z0-00@the-village.bc.nu> <E14LOAm-0006z0-00@the-village.bc.nu> <01012416081105.19999@nessie>
** Reply to message from Anton Altaparmakov <aia21@cam.ac.uk> on Wed, 24 Jan
2001 16:54:36 +0000
> >Is read access safe ?
>
> Of course read-only is safe. As long as you mount the partition READ-ONLY
> nothing can happen to it in any way, your NTFS data is at least safe.
Isn't it still theoretcially possible for the driver to send commands to the
disk controller that cause data to become overwritten, even when it's just
supposed to read that data?
--
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com
When replying to a mailing-list message, please direct the reply to the mailing list only. Don't send another copy to me.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-24 17:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.31ksi3.0101241721470.605-100000@nomad.cyberbill s.com>
2001-01-24 11:33 ` Linux 2.4.0ac11 Alan Cox
2001-01-24 15:05 ` Cataldo Thomas
2001-01-24 17:03 ` Timur Tabi [this message]
2001-01-24 17:09 ` NTFS safety and lack thereof - Was: " mirabilos
2001-01-26 17:38 ` Pavel Machek
2001-01-24 17:23 ` Anton Altaparmakov
2001-01-24 16:54 ` Anton Altaparmakov
2001-01-24 20:06 ` Luc de Louw
2001-01-25 1:36 ` Alan Cox
2001-01-25 1:39 ` Sergey Kubushin
2001-01-25 5:18 ` Andre Hedrick
2001-01-25 11:02 ` Matthias Andree
2001-01-25 16:50 ` Sergey Kubushin
2001-01-25 2:04 ` Anton Altaparmakov
2001-01-25 2:13 ` Sergey Kubushin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010124170337Z129710-18594+930@vger.kernel.org \
--to=ttabi@interactivesi.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox