mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cataldo Thomas <cataldo@essi.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.0ac11
Date: Wed, 24 Jan 2001 16:05:13 +0100	[thread overview]
Message-ID: <01012416081105.19999@nessie> (raw)
In-Reply-To: <E14LOAm-0006z0-00@the-village.bc.nu>
In-Reply-To: <E14LOAm-0006z0-00@the-village.bc.nu>

On Wed, 24 Jan 2001, Alan Cox wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
> 
> Slightly delayed because I had take some time out to fall off a horse..
> 
> 
> 2.4.0-ac11
> o	Major NTFS updates				(Anton Altaparmakov)

Is read access safe ?
I would really be interested by a link to ntfs status in linux. I mean what is
safe and what is not.

-- 

Passe que moi, au départ, j'avais fait informatique comme études, pas
NT, et je voudrais revenir à mon métier premier.
-+- BB in Guide du Linuxien pervers - Bien configurer son metier.


-
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/

  reply	other threads:[~2001-01-24 15:08 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 ` Alan Cox
2001-01-24 15:05   ` Cataldo Thomas [this message]
2001-01-24 17:03     ` NTFS safety and lack thereof - Was: " Timur Tabi
2001-01-24 17:09       ` 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=01012416081105.19999@nessie \
    --to=cataldo@essi.fr \
    --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

all inboxes | Powered by JetHome®