mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: Rob Kaper <cap@capsi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Renaming lost+found
Date: Fri, 26 Jan 2001 12:24:32 -0700 (MST)	[thread overview]
Message-ID: <200101261924.f0QJOWH15609@webber.adilger.net> (raw)
In-Reply-To: <20010126141350.Q6979@capsi.com> from Rob Kaper at "Jan 26, 2001 02:13:50 pm"

Rob Kaper writes:
> Is there a way to rename lost+found ?? It bothers me to see it in ls all the
> time because 99.9% of my time it's just useless and I really think
> .lost+found (a hidden file) would make much more sense for daily use. I
> assume this would require some ext2 changes as well as a patch to e2fsck
> etc. (with backwards compatibility of course)

You could also just delete it, but then you run into problems when e2fsck
is run on a broken filesystem.  Use ext3 instead.  The lost+found dir is
in many (most?) Unix filesystems, for use when things go bad.

You _could_ change it to be a hidden file, but then you would have to
remember where it was after e2fsck moves half of your files into it
after a crash.  It probably wouldn't be too much work to change e2fsck.
You also need to change mke2fs and mklost+found as well.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
-
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/

  parent reply	other threads:[~2001-01-26 19:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26 13:13 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
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 [this message]
2001-01-26 19:45   ` patrick.mourlhon
     [not found]     ` <200101262005.PAA05246@mah21awu.cas.org>
2001-01-26 20:21       ` patrick.mourlhon
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=200101261924.f0QJOWH15609@webber.adilger.net \
    --to=adilger@turbolinux.com \
    --cc=cap@capsi.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

all inboxes | Powered by JetHome®