Messages in this thread | | | Date | Fri, 4 Oct 2002 17:06:13 -0700 | From | Greg KH <> | Subject | Re: [Evms-devel] Re: EVMS Submission for 2.5 |
| |
On Fri, Oct 04, 2002 at 10:07:24AM +0200, Oliver Neukum wrote: > On Friday 04 October 2002 00:56, Greg KH wrote: > > On Thu, Oct 03, 2002 at 11:02:36PM +0200, Oliver Neukum wrote: > > > Perhaps this is a misunderstanding. > > > You need to report changes of the actual physical medium of eg. a zip > > > drive. How you want to do this from a class driver, I fail to see. > > > > When a "medium" goes away from the system, it is unregistered somehow, > > right? So, in the disk class, that device would disappear, and cause > > the /sbin/hotplug event. > > Well, sadly this is not the case. You can put a medium into a drive and > pull it out without the kernel ever noticing. Unless of course you try to use > the thing. But even in this case there's no hotplug event. > Yet user space and evms have to learn about it in the long term. > Changing a medium can mean that a new type of medium is inserted. > A modern zip drive goes from 100M(ro) to 250M(rw) and even 750M(rw) > We need to know and report.
I agree we need to know this. And if the kernel figures it out (somehow) then userspace should also be told about this, through /sbin/hotplug. That's all I'm saying.
thanks,
greg k-h - 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/
| |