> > One way to look at that issue is to ask what user mode notifications
> > will be used to address that part of the hotplug problem. Devfsd
> > is what some folk like, but it's not universally accepted. GUI
> > driven solutions don't seem right in all cases either.
>
> devfsd is at least already here. The existing /sbin/hotplug architecture
> can't handle it. A new kind of event would be needed.
A new event type doesn't change the architecture ... if
that's all that's needed, the architecture is unchanged!
To some folk, it won't even matter if the event comes from
a devfsd thread or a kernel thread. Implementation detail.
Except maybe to the US Patent Office ... sigh. (One
iteration of USB hotplugging did just that: devfsd called
the same policy scripts as the kernel thread version.)
> Even so, you'll probably won't make the user happy if it works only
> on plugging in and not when he puts in a new medium.
> A look at supermount might be in order.
Yep, lots of tools to choose from. But again, not everyone
runs supermount (or wants to) -- Yet Another Daemon, as I
recall the situation.
- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
