on 5/17/00 8:30 AM, m. allan noah at [EMAIL PROTECTED] wrote:
> you obviously dont understand how device files work.
You are correct, that is one particular part of the opsys that is still
pretty much mystery to me.
Even reading through /usr/src/linux/Documentation/devices.txt makes it
pretty obvious that some intricate studying of this aspect will be
necessary.
While I appreciate the patch/diff provided by James Manning, I am extremely
weary of applying anything to a system that I don't fully understand -
particularly if it is suffixed by "Who knows..." (shiver).
Now, I just need to make sure all devices are attached as Master devices, on
their own controller port, and then figure out what minor and major to set
them at... *ANY* help in allowing me to better understand how that's done,
or in actually doing this will be appreciated.
> you MUST make the device
> files in /dev/ in order for the kernel to know what devices you are trying to
> access (ok- that is oversimplified to the point of being almost incorrect)
Alright, maybe it's oversimplified, but I grok that part (that the kernel
needs the proper device files, and that I don't have the device files, and
thus need to create them.
> until you use mknod to create these device files, you will NOT be able to open
> the drives, or do anything with them with ANY tool in linux. the only thing
> that will be able to see them is the kernel at boot time. hence- your problem.
Thanks, and thanks to James Manning as well for finally tracking down what
the core of this problem is.
Is there some utility that will quickly and easily create /dev/ files and
provides qualified questions to assist in properly creating /dev/ files?
Thanks, your help is appreciated.
Harry
