All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Renaming lost+found
Date: 28 Jan 2001 13:35:44 -0800	[thread overview]
Message-ID: <9523bg$7dc$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010126084632.208A-100000@chaos.analogic.com> <3A73565B.6EBC7F77@ngforever.de>

Followup to:  <3A73565B.6EBC7F77@ngforever.de>
By author:    Thunder from the hill <thunder@ngforever.de>
In newsgroup: linux.dev.kernel
>
> > A file-system without a lost+found directory is like love without sex.
> You mean, possible but leaving you unsatisfied? Well, I think a file
> system without a lost+found is a lot worse.
> 

Hello people... the original question was: can lost+found be
*renamed*, i.e. does the tools (e2fsck &c) use "/lost+found" by name,
or by inode?  As far as I know it always uses the same inode number
(11), but I don't know if that is anywhere enforced.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
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-28 21:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26 13:13 Renaming lost+found Rob Kaper
2001-01-26 13:49 ` Richard B. Johnson
2001-01-26 18:19   ` James Lewis Nance
2001-01-26 20:05     ` Rodrigo Barbosa (aka morcego)
2001-01-27 20:43       ` Stephen C. Tweedie
2001-01-28 19:26     ` Chris Mason
2001-01-27 23:14   ` Thunder from the hill
2001-01-28 21:35     ` H. Peter Anvin [this message]
2001-01-28 21:41       ` Mo McKinlay
2001-01-28 21:56         ` Support for 802.11 cards? Mike Pontillo
2001-01-28 22:07           ` John Jasen
2001-01-28 23:23             ` Michael H. Warfield
2001-01-29  0:13               ` Joe deBlaquiere
2001-01-29  2:00               ` Anton Blanchard
2001-01-29 18:18               ` Bryan O'Sullivan
2001-01-30  1:09                 ` Mike Pontillo
2001-01-29  6:41         ` Renaming lost+found Mike Galbraith
2001-01-29  7:17       ` Andreas Dilger
2001-01-31 15:32       ` tytso
2001-01-26 19:24 ` Andreas Dilger
2001-01-26 19:45   ` patrick.mourlhon
     [not found]     ` <200101262005.PAA05246@mah21awu.cas.org>
2001-01-26 20:21       ` patrick.mourlhon
  -- strict thread matches above, loose matches on Subject: below --
2001-01-26 22:09 NDias
2001-01-27 21:01 ` Albert D. Cahalan

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='9523bg$7dc$1@cesium.transmeta.com' \
    --to=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.