All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-fsdevel@vger.kernel.org, Milind <milind@gslab.com>,
	xfs@oss.sgi.com
Subject: Re: EXT vs XFS at 80% filled filesystem
Date: Wed, 20 May 2009 06:46:22 -0600	[thread overview]
Message-ID: <20090520124622.GJ31779@parisc-linux.org> (raw)
In-Reply-To: <20090520105011.GD3523@mit.edu>

On Wed, May 20, 2009 at 06:50:11AM -0400, Theodore Tso wrote:
> The debian packages ultimately end up building e2fsprogs three times,
> with different sets of configure options.  One is the standard build,
> one is for the restricted-size build for boot floppies (which arguably
> we don't need any more since we these days CD-ROM's have plenty of
> space, and Debian doesn't support boot floppies any more) and one is
> for the static build for e2fsck.static (although the utility of that
> one is somewhat dubious given that even the shell is with shared
> library, so if the filesystem is corrupted enough that shared libaries
> don't work, it's rescue CD-ROM time; the main use for e2fsck.static is
> for emergency use when someone running an older version of Debian
> needs a newer e2fsck to fix a filesystem corruption).

If you install sash, you really do get a statically linked shell:

$ ldd /bin/sash 
ldd: exited with unknown exit code (126)
$ file /bin/sash 
/bin/sash: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for GNU/Linux 2.6.8, stripped

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <matthew@wil.cx>
To: Theodore Tso <tytso@mit.edu>
Cc: Milind <milind@gslab.com>,
	linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: EXT vs XFS at 80% filled filesystem
Date: Wed, 20 May 2009 06:46:22 -0600	[thread overview]
Message-ID: <20090520124622.GJ31779@parisc-linux.org> (raw)
In-Reply-To: <20090520105011.GD3523@mit.edu>

On Wed, May 20, 2009 at 06:50:11AM -0400, Theodore Tso wrote:
> The debian packages ultimately end up building e2fsprogs three times,
> with different sets of configure options.  One is the standard build,
> one is for the restricted-size build for boot floppies (which arguably
> we don't need any more since we these days CD-ROM's have plenty of
> space, and Debian doesn't support boot floppies any more) and one is
> for the static build for e2fsck.static (although the utility of that
> one is somewhat dubious given that even the shell is with shared
> library, so if the filesystem is corrupted enough that shared libaries
> don't work, it's rescue CD-ROM time; the main use for e2fsck.static is
> for emergency use when someone running an older version of Debian
> needs a newer e2fsck to fix a filesystem corruption).

If you install sash, you really do get a statically linked shell:

$ ldd /bin/sash 
ldd: exited with unknown exit code (126)
$ file /bin/sash 
/bin/sash: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for GNU/Linux 2.6.8, stripped

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  parent reply	other threads:[~2009-05-20 12:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30  7:42 EXT vs XFS at 80% filled filesystem Milind Dumbare
2009-04-30 17:28 ` Michael Monnerie
2009-04-30 18:34 ` Theodore Tso
2009-04-30 18:34   ` Theodore Tso
2009-05-18 13:03   ` Milind
2009-05-18 13:03     ` Milind
2009-05-18 13:17     ` Theodore Tso
2009-05-18 13:17       ` Theodore Tso
2009-05-20  5:43       ` Milind
2009-05-20  5:43         ` Milind
2009-05-20 10:50         ` Theodore Tso
2009-05-20 10:50           ` Theodore Tso
2009-05-20 11:51           ` Milind
2009-05-20 11:51             ` Milind
2009-05-20 14:20             ` Theodore Tso
2009-05-20 14:20               ` Theodore Tso
2009-05-20 12:46           ` Matthew Wilcox [this message]
2009-05-20 12:46             ` Matthew Wilcox

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=20090520124622.GJ31779@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=milind@gslab.com \
    --cc=tytso@mit.edu \
    --cc=xfs@oss.sgi.com \
    /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.