public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 14:18:53 +0200	[thread overview]
Message-ID: <3D5261AD.9000706@evision.ag> (raw)
In-Reply-To: 1028813033.28882.37.camel@irongate.swansea.linux.org.uk

Użytkownik Alan Cox napisał:
> 
> So why did you take it out ?

I say it n-th time already dd if=/dev/hda of=/dev/hdb should give
a prefect sector by sector disk clone.

The bugs should be fixed in lilo and not worked around in the kernel.
We have the goal (and in fact obligation for scalability issues) to move
partition scanning out of the kernel space.

Did you ever bother looking the the function in question?

Did you ever look at the missordered code in lilo I cited here?

Did you ever think about what to do about the recurring complains
from people about disk order differences between BIOS and Linux?

Or the whole GET_GEO_BIG confusion ioctl()?

Please compare it with the proper formulas provided at www.phoenix.com
in excellent white papers. (Which can't be linked to directly, since
they  check the refferrer.)

It did contain 'heuristics" which stopped to annoy people just becouse
many have developed the immediate reflex of always adding the linear
parameter during lilo configuration already a very very long time ago
becouse anything else doesn't make much sense and disks have passed the 
512MB or even 4G barrier quite a time ago.


  reply	other threads:[~2002-08-08 12:20 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
2002-08-08 13:23           ` Alan Cox
2002-08-08 12:18             ` Marcin Dalecki [this message]
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=3D5261AD.9000706@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