From: Andreas Dilger <adilger@turbolinux.com>
To: Stefan Ring <e9725446@student.tuwien.ac.at>
Cc: "Dr. Kelsey Hudson" <kernel@blackhole.compendium-tech.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.0.37 crashes immediately
Date: Wed, 17 Jan 2001 02:24:39 -0700 (MST) [thread overview]
Message-ID: <200101170924.f0H9Odu04425@webber.adilger.net> (raw)
In-Reply-To: <Pine.HPX.4.10.10101170957350.29885-100000@stud3.tuwien.ac.at> "from Stefan Ring at Jan 17, 2001 10:00:31 am"
Stefan Ring writes:
> Every version above 2.0.36 behaves the same (from the 2.0.x series). Gee,
> I should have said a few words about my intent. Of course, I'm not
> actually using these old versions of everything. I just wanted to run a
> 2.0.x kernel to do some hardware testing, and since 2.0.x can't access the
> new ext2fs with the spare superblock option, I thought, I might be up and
> running fastest by installing a RH distribution still using the 2.0.x
> kernel.
Actually, if you have the 2.0.39 kernel (or a pre-patch), it can use the
sparse ext2 superblock feature. Even so, it is only a matter of turning the
sparse_super flag on or off and running e2fsck on the filesystem to convert.
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/
next prev parent reply other threads:[~2001-01-17 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 23:35 Stefan Ring
2001-01-17 0:08 ` Dr. Kelsey Hudson
2001-01-17 9:00 ` Stefan Ring
2001-01-17 9:15 ` David Weinehall
2001-01-17 9:24 ` Andreas Dilger [this message]
2001-01-17 4:08 ` Mike A. Harris
2001-01-17 9:43 ` Stefan Ring
2001-01-17 12:33 ` David Weinehall
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=200101170924.f0H9Odu04425@webber.adilger.net \
--to=adilger@turbolinux.com \
--cc=e9725446@student.tuwien.ac.at \
--cc=kernel@blackhole.compendium-tech.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®