From: Marcin Dalecki <dalecki@evision.ag>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: martin@dalecki.de, Petr Vandrovec <VANDROVE@vc.cvut.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.29 IDE 110
Date: Thu, 01 Aug 2002 23:16:34 +0200 [thread overview]
Message-ID: <3D49A532.1090606@evision.ag> (raw)
In-Reply-To: 1028238427.14871.95.camel@irongate.swansea.linux.org.uk
Użytkownik Alan Cox napisał:
> On Thu, 2002-08-01 at 21:21, Marcin Dalecki wrote:
>
>>Maybe not a loop device? But how about handling this at partition scan
>>time then? Partitions are after all nothing else then devices
>>with remapped sectors in first place. Could you manage to insert
>>at the proper place in paritions/*.c the magical + 1.
>>It could then be turned in no instant in to a global kernel
>>option - whch it what it is after all.
>
>
> Is there any reason this can't be dumped on LVM2 and/or EVMS whichever
> gets in ?
Lets not forgett that the code removed would allow to read behind the
partion in question and was broken therefore. However the real world
example from Petr worries me and makes me thinking that the partition
scanning time solution could turn out to be most adequate -> we have the
FAT partition ID there at hand and could adjust the partition
parameters in question properly with ease. Both of them: offset *and* size.
Petr would you mind dumping the dd=/dev/hdx count=10 of the
disk in question at me? Or do you preferr to go after this blotch
yourself?
next prev parent reply other threads:[~2002-08-01 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 16:54 [PATCH] 2.5.29 IDE 110 Petr Vandrovec
2002-08-01 20:21 ` Marcin Dalecki
2002-08-01 21:47 ` Alan Cox
2002-08-01 21:16 ` Marcin Dalecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-01 21:45 Petr Vandrovec
2002-08-01 21:57 ` Marcin Dalecki
2002-08-01 17:37 Adam J. Richter
2002-08-01 0:40 Marcin Dalecki
2002-08-01 18:51 ` Albert D. Cahalan
2002-08-01 20:13 ` Marcin Dalecki
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=3D49A532.1090606@evision.ag \
--to=dalecki@evision.ag \
--cc=VANDROVE@vc.cvut.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
/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