We need a STANDARD Identifiers for HWs.

hai

To identify different Hardwares we need soon STANDARD IDENTIFIERS for to handle them finitely.....

I want to mean to the /dev/fd0 , /dev/hd1 etc as in LINUX....

Am i right??
Give your opinion frankly.......

Why?

Submitted by Stephen Crawley on Sat, 02/24/2007 - 22:35.

I suppose standard names are a reasonable idea ... but why do you think that they so important?

The thing that makes /dev/fd0, etc so powerful is not the names (which are not standardized across different UNIXes) but the fact that they support the same API as regular UNIX files; i.e. open(), close(), read(), write(), etc. Is this what you are really talking about?

For Using in HW accessing commands

Submitted by tango_java_06 on Sun, 02/25/2007 - 12:14.

hi,
I think this will be useful for the different HW accessing commands.
Bcs, if one user knows that the Floppy Drives in his machine are in this Unique name, i think this will help him.But, i think this names will set as the drive's priority like Primary,Secondary etc.
like as
jnode/>raid -0 JFd0 JFd1
the command for setting the RAID0 configuration on the JFd0 and JFd1 etc....

Pls give your opinion on that....say is t resonable?? or not...

Reasonable, but ...

Submitted by Stephen Crawley on Mon, 02/26/2007 - 01:29.

... for what you are trying to achieve, it is not crucial for the device names are standardized. Rather, it is more important that the 'raid' utility (and others like it) can do the following:

  1. The utilities need to be able to lookup the device names in some namespace implemented by JNode to give device objects. This is the logical equivalent of the "/dev/*" tree in UNIX.
  2. The utilities need to be able to access the device objects using an appropriate interface. The corresponding abstractions in UNIX are the read, write, fnctl, etc syscalls and the block i/o device layers. (But then again, to implement a software RAID in a UNIX like OS, you need to insert the RAID layer between the "raw" block device and the cached block device ... in the OS kernel.)

If the logical equivalent of the "/dev/" namespace and device I/O APIs do not exist, standardizing the names is a meaningless sideshow. Besides, history tells us that we could easily get by with conventional names rather than standardized names. Buy, hey, if you want to propose some Standard Names, I've no problems with that. Write an intelligible document and I'm sure someone will put it up for you.