From: Miles Lane <miles@megapathdsl.net>
To: Chris Mason <mason@suse.com>
Cc: newsreader@mediaone.net, linux-kernel@vger.kernel.org
Subject: Re: did 2.4 messed up lilo?
Date: Fri, 02 Feb 2001 17:50:09 -0800 [thread overview]
Message-ID: <3A7B63D1.2588963B@megapathdsl.net> (raw)
In-Reply-To: <786060000.981147343@tiny>
Chris Mason wrote:
>
> On Friday, February 02, 2001 03:36:18 PM -0500 newsreader@mediaone.net
> wrote:
>
> > I'm not sure whether this problem is related
> > to 2.4 kernel.
> >
>
> I suspect it is a reiserfs problem, and that you are using lilo older than
> 21.6. Are you mounting /boot with -o notail?
>
> Regardless, I'm willing to bet upgrading to lilo 21.6 will solve this. It
> calls an ioctl reiserfs provides to unpack small files, and I've seen it
> fix this exact problem on one of my devel boxes (no lilo prompt, append
> lines in lilo.conf ignored).
I also found this patch for lilo 21.6:
http://industrial-linux.org/distro/download/lilo-21.6-glibc-2.2-reiserfs.patch
Perhaps someone familiar with the lilo and reiserfs code could explain
whether or not this patch is really needed.
Miles
-
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-02-03 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 20:36 did 2.4 messed up lilo? newsreader
2001-02-02 20:55 ` Chris Mason
2001-02-03 1:50 ` Miles Lane [this message]
2001-02-03 1:58 ` Miles Lane
2001-02-03 5:14 ` newsreader
2001-02-03 11:27 ` newsreader
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=3A7B63D1.2588963B@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=newsreader@mediaone.net \
/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