From: Marcin Dalecki <dalecki@evision.ag>
To: Andries.Brouwer@cwi.nl
Cc: mingo@elte.hu, alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [bug, 2.5.29, IDE] partition table corruption?
Date: Thu, 08 Aug 2002 09:46:27 +0200 [thread overview]
Message-ID: <3D5221D3.7090807@evision.ag> (raw)
In-Reply-To: UTC200208071843.g77IhUc20546.aeb@smtp.cwi.nl
> Since 2.5.30 many people will have a different geometry, so many
> people will have to find grub or a recent LILO, or add "linear"
> to their old LILO. This is all well understood - I just repeat it
> a few times in the hope that that will reduce the amount of email.
I think you confuse two entierly unrelated issues a bit:
1. Remapping s single sector and thus making the behaviour of dd
if=/dev/hda /of=dev/hdb less then intuitive, namely: severly BROKEN. It
doesn't matter that this was broken for years. Now I can remember it did
bite me once I tryed to clone a system precisely in the dd way. (Of
course rerunning lilo on the clone wasn't impossible for me...) The only
thing which makes me worry here are the problems Petr was reporting about...
2. The xlate trick which was only supposed to be used by the MSDOS fs
driver and only on i386 and only if this thing was residuent and
ide-disk was not compiled as a module and so on. This is actually the
*geometry* issue. If someone needs access to an MS-DOS partition, well
he can always resort to mtools. FAT16, which is likely the affected
variant of FAT filesystem, was broken before anyway and I have still to
recheck whatever the removal of the geomtry "translation" didn't even
maybe make my CF PSION system disk readbale.
next prev parent reply other threads:[~2002-08-08 7:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 18:43 [bug, 2.5.29, IDE] partition table corruption? Andries.Brouwer
2002-08-07 21:12 ` [bug, 2.5.29, (not IDE)] partition table (not) corruption? Ingo Molnar
2002-08-08 7:30 ` Marcin Dalecki
2002-08-08 7:37 ` Ingo Molnar
2002-08-08 8:42 ` Marcin Dalecki
2002-08-08 9:03 ` Ingo Molnar
2002-08-08 9:18 ` Marcin Dalecki
2002-08-08 7:46 ` Marcin Dalecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 18:22 [bug, 2.5.29, IDE] partition table corruption? 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-08 9:08 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
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
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=3D5221D3.7090807@evision.ag \
--to=dalecki@evision.ag \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--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