>No problem. The file does not show up in the driectory. You can still
>try to open it, if you know it's name. The kernel can autoload the
>appropriate module. This differs from normal autoloading a little
>bit. There you have the device files and the kernel perform a loading
>request for block-major-XY ...
And if you don't know the name? Then you have to keep trying every
possible combination until you find it. One of my machines has nearly
30 SCSI CDROMs on it... for each CDROM to be opened, I have to try
probing each target and LUN on all six chains? At what point do I
give up and assume the device doesn't exist?
A better way has to be found. The above guessing game is not acceptible.
>> Am I insane? Am I the only one who believes that 'stable' means
>> 'don't randomly fuck with it'?
>
>Richards devfs is not randomly fucking with anything. It's an approach which
>has been discussed on linux-kernel in every detail and implemented and
>maintained by RG, since then.
How is introducing a piece of infrastructure this large in the middle
of a stable kernel series "not randomly fucking with anything"? See
my above question. Given that, I can even leave potential bug
introductions out of it :-)
>devfs has been out for a very loing time now and a lot of people use it
>without problems. As it's fully backward compatible, using it does not hurt
>anybody.
So you say and so you think. I honestly don't mean to sound
antagonstic (or condescending), but I simply can't believe what you
say. Are you honestly claiming that devfs is 100%, totally bug-free?
I thought not-- then it doesn't belong being introduced in the middle
of a stable release. Stable means 'bugfix only'. Anything you might
do that will knowingly introduce more bugs is not for a stable
release.
>I don't know the exact reasons, why Linus didn't schedule it's inclusion for
>2.1.130 but for 2.2.x, but I think, he does not want to care about problems,
>which might be caused by devfs interactions, so he wants the mainline rock
>solid before.=20
"Bingo."
Monty
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
