From: "Petr Titera" <owl@volny.cz>
To: <linux-kernel@vger.kernel.org>
Subject: Re: linux kernel 2.4.10 possibly breaks LILO
Date: Wed, 3 Oct 2001 22:46:16 +0200 [thread overview]
Message-ID: <000001c14cae$e56eaa20$28a76cc0@NEVSKIJ> (raw)
In-Reply-To: <002c01c14b6b$5f19ba30$13a76cc0@NEVSKIJ> <E15on6m-0005ET-00@schizo.psychosis.com>
>
> If this is the case, I'd call that a feature. ; >
>
> Dave
> <Well known absolute block offset bootloader hater>
I hate it too now. I even booted from image I deleted. God knows what would
happen if I did not noticed it early :))
>
> --
Petr
next prev parent reply other threads:[~2001-10-04 8:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 17:55 linux kernel 2.4.10 possibly breaks LILO Petr Titera
2001-10-02 23:55 ` David Ford
2001-10-02 23:45 ` Jonathan Walther
2001-10-03 14:36 ` Dave Cinege
2001-10-03 20:46 ` Petr Titera [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-02 18:03 Rui Ribeiro
2001-10-02 17:54 Rui Ribeiro
2001-10-02 18:10 ` Petr Titera
2001-10-02 19:09 ` Andreas Dilger
2001-09-27 3:48 Ken Zalewski
2001-09-27 5:01 ` Andreas Dilger
2001-09-27 5:10 ` Steve Kieu
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='000001c14cae$e56eaa20$28a76cc0@NEVSKIJ' \
--to=owl@volny.cz \
--cc=Petr.Titera@quick.cz \
--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;
as well as URLs for NNTP newsgroup(s).