From: Martin Dalecki <dalecki@evision-ventures.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: [PATCH] 2.5.18 IDE 73
Date: Thu, 30 May 2002 16:20:37 +0200 [thread overview]
Message-ID: <3CF63535.6000907@evision-ventures.com> (raw)
In-Reply-To: <UTC200205300019.g4U0JtH24034.aeb@smtp.cwi.nl> <3CF622F0.4050304@evision-ventures.com> <1022772774.12888.380.camel@irongate.swansea.linux.org.uk> <3CF62F2A.6030009@evision-ventures.com> <1022775219.9255.385.camel@irongate.swansea.linux.org.uk>
Alan Cox wrote:
> On Thu, 2002-05-30 at 14:54, Martin Dalecki wrote:
>
>>I don't use and don't care about devfs - it's a misconception in my opinnion.
>
>
> Yes but there are lots of other opinions. And it was just one of several
> examples of why you were proposing something utterly bogus
>
>
>
>>And last but not least: some devices which should be viewd as "same type"
>>are hooked up to different major numbers instead of sharing them.
>>Most prominent here are the differences between SCSI disks and ATA disks
>>for example. From a technical point of view they don't make *any* sense.
>
>
> Linus has explicitly stated he wants to do this and make all disks
> appear the same and the same place. It actually makes lots of sense.
LAST WARNING:
Every body out there: watch out to use LABEL= in /etc/fstab or you will
not be able to reboot between 2.4 and 2.5 soon!
Things which have to be done in front:
1. Extract device registration from SCSI code.
2. Let the ATA/ATAPI code hook up on it. (ide-cs is the most difficult one.)
3. Let the old ATA/ATAPI major go down the bin...
next prev parent reply other threads:[~2002-05-30 15:19 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 0:19 [PATCH] 2.5.18 IDE 73 Andries.Brouwer
2002-05-30 13:02 ` Martin Dalecki
2002-05-30 15:32 ` Alan Cox
2002-05-30 13:54 ` Martin Dalecki
2002-05-30 15:05 ` Tomas Szepe
2002-05-30 15:13 ` Rene Rebe
2002-05-30 15:39 ` Wichert Akkerman
2002-05-30 16:13 ` Alan Cox
2002-05-30 14:20 ` Martin Dalecki [this message]
2002-05-30 15:31 ` Linus Torvalds
2002-05-30 18:55 ` Martin Dalecki
2002-05-30 15:25 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2002-05-30 15:56 Andries.Brouwer
2002-05-30 14:43 Andries.Brouwer
2002-05-30 14:01 ` Martin Dalecki
2002-05-30 15:09 ` Rene Rebe
2002-05-31 13:25 ` Denis Vlasenko
2002-05-30 12:35 Bartlomiej Zolnierkiewicz
2002-05-29 23:40 Andries.Brouwer
2002-05-29 22:53 ` Martin Dalecki
2002-05-29 18:16 Andries.Brouwer
2002-05-29 18:07 Andries.Brouwer
2002-05-29 21:57 ` Martin Dalecki
2002-05-29 13:59 Gerald Champagne
2002-05-29 13:03 ` Martin Dalecki
2002-05-29 14:26 ` Gerald Champagne
2002-05-29 14:35 ` Russell King
2002-05-29 13:40 ` Martin Dalecki
2002-05-29 16:33 ` Vojtech Pavlik
2002-05-29 15:46 ` Martin Dalecki
2002-05-29 18:47 ` Alan Cox
2002-05-30 8:48 ` David Woodhouse
2002-05-30 12:22 ` Martin Dalecki
2002-05-29 17:55 ` Alan Cox
2002-05-29 17:01 ` Vojtech Pavlik
2002-05-29 16:05 ` Martin Dalecki
2002-05-29 17:05 ` Vojtech Pavlik
2002-05-29 18:43 ` Alan Cox
2002-05-25 2:02 Linux-2.5.18 Linus Torvalds
2002-05-29 12:11 ` [PATCH] 2.5.18 IDE 73 Martin Dalecki
2002-05-29 12:58 ` Zwane Mwaikambo
2002-05-29 12:52 ` Martin 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=3CF63535.6000907@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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