From: Marcin Dalecki <dalecki@evision.ag>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: martin@dalecki.de, Ingo Molnar <mingo@elte.hu>,
"Adam J. Richter" <adam@yggdrasil.com>,
Andries.Brouwer@cwi.nl, johninsd@san.rr.com,
linux-kernel@vger.kernel.org
Subject: Re: [bug, 2.5.29, IDE] partition table corruption?
Date: Thu, 08 Aug 2002 13:22:49 +0200 [thread overview]
Message-ID: <3D525489.3050209@evision.ag> (raw)
In-Reply-To: 1028809830.28883.13.camel@irongate.swansea.linux.org.uk
Użytkownik Alan Cox napisał:
> On Thu, 2002-08-08 at 10:34, Marcin Dalecki wrote:
>
>>> [mingo@a mingo]$ ls -l /sbin/lilo
>>> -rwxr-xr-x 1 root root 59324 Aug 23 2000 /sbin/lilo
>>
>>Yes sure. It is simply a very old bug in lilo, which the kernel worked
>>around and did fight against in a diallectic way.
>
>
> Its not a bug in lilo. Its a bug in the new kernel. Breaking backward
> compatibility arbitarily is bad. The kernel needs to know geometry
> anyway for the folks who have force ide translation
1. Requiring the kernel to read the partition table information is a
BUG.
2. Falling back on the values which are used by the application
afterwards is a BUG. (BIOS IRQ after all)
3. Not detecting LBA disk access is required by checking Cylinder value
to emulate BIOS behaviour is a BUG.
4. Asking the kernel to kindly avoid 100% partition table scanning and
*guessing* some *heuristic* values which fail frequently enough is a
BUG. (Take a look at the jumps and hops in the function in question if
you don't think it is guessing. I recommend the switch in esp.)
5. Relying on the kernel for the translation "trick" himself (if
anything) is a BUG.
6. It's after all no more inconvenient then renaming well for example
the USB host controller module.
7. It is *not* breaking backward compatibility. After the lilo
configuration fix the old kernel boots fine as well.
Not reading confusing lilo docs which should better say what to do is a
BUG.
BTW.> Silly RH beta fdisk did tell me bogous things about the
geometry of disks I did install under plain RH 7.3...
BTW.> And finally what about dd if=/dev/hda of=/dev/hdb?
next prev parent reply other threads:[~2002-08-08 11:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 9:08 [bug, 2.5.29, IDE] partition table corruption? Adam J. Richter
2002-08-08 9:24 ` Marcin Dalecki
2002-08-08 9:31 ` Ingo Molnar
2002-08-08 9:34 ` Marcin Dalecki
2002-08-08 10:01 ` Ingo Molnar
2002-08-08 11:45 ` Andries Brouwer
2002-08-08 12:30 ` Alan Cox
2002-08-08 11:22 ` Marcin Dalecki [this message]
2002-08-08 13:23 ` Alan Cox
2002-08-08 12:18 ` Marcin Dalecki
2002-08-08 18:11 ` Alan Cox
2002-08-09 0:11 ` Thunder from the hill
2002-08-09 6:27 ` Marcin Dalecki
[not found] ` <3D523B25.5 <20020808181100Z315277-685+26763@vger.kernel.org>
2002-08-09 6:25 ` Marcin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 18:22 Andries.Brouwer
2002-08-08 22:36 ` John Coffman
2002-08-09 6:06 ` H. Peter Anvin
2002-08-08 12:29 Andries.Brouwer
2002-08-07 18:43 Andries.Brouwer
2002-08-08 7:46 ` Marcin Dalecki
2002-08-06 22:27 Andries.Brouwer
2002-08-07 17:46 ` Ingo Molnar
2002-08-07 17:51 ` Ingo Molnar
2002-08-01 13:45 Ingo Molnar
2002-08-01 13:48 ` Marcin Dalecki
2002-08-01 16:16 ` Alan Cox
2002-08-01 15:02 ` Marcin Dalecki
2002-08-01 15:12 ` Alan Cox
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=3D525489.3050209@evision.ag \
--to=dalecki@evision.ag \
--cc=Andries.Brouwer@cwi.nl \
--cc=adam@yggdrasil.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=johninsd@san.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--cc=mingo@elte.hu \
/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