mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
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 10:15:56 +0100	[thread overview]
Message-ID: <20010117101556.B2399@khan.acc.umu.se> (raw)
In-Reply-To: <Pine.LNX.4.21.0101161605570.17397-100000@sol.compendium-tech.com> <Pine.HPX.4.10.10101170957350.29885-100000@stud3.tuwien.ac.at>
In-Reply-To: <Pine.HPX.4.10.10101170957350.29885-100000@stud3.tuwien.ac.at>; from e9725446@student.tuwien.ac.at on Wed, Jan 17, 2001 at 10:00:31AM +0100

On Wed, Jan 17, 2001 at 10:00:31AM +0100, Stefan Ring wrote:
> On Tue, 16 Jan 2001, Dr. Kelsey Hudson wrote:
> 
> > Is there a reason you are using a relatively new machine like that with
> > such an outdated and arcane kernel (and distribution, for that
> > matter)? I'd suggest you upgrade to a more recent kernel and/or
> > distribution...it'll be a lot more stable (and not to mention secure!)
> 
> 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. It just happened that RH4.2 was the only one I
> had handy at that moment.

Actually, v2.0.39 _does_ cope with sparse superblocks.


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </
-
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-17  9:16 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 [this message]
2001-01-17  9:24     ` Andreas Dilger
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=20010117101556.B2399@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --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®