> This is a problem with hotswap of course, and shouldn't be solved
> by the kernel putting the same device always in the same
> major/minor. A userspace application should query the OS and build
> the device nodes based upon scsi serial number, FC port WWN, or
> access path (host/channel/id/lun). The current "MAKEDEV" works
> fine for people with and ide disk and cdrom, but for real systems
> with lots of disks and hotswap capabilities, static naming just
> doesn't work (as you have said). :) Devfs solves the naming
> problem by using access path automatically within the OS. Downside
> of this methodology is that access permissions are not persistent
> between reboots (which is one significant limitation of devfs).
Are you aware of devfsd? It keeps permissions for you across reboots,
and does it just fine.
The real limitation in this case is SCSI host numbers. There is no
way to permanently assign logical controller numbers like it happens
in other systems. add or remove another SCSI adapter and all your
names are shifted.
which is true for any adapter not just SCSI.
-andrey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jan 31 2003 - 22:00:23 EST