Date: Sat, 25 Feb 2006 18:56:30 +0000 (GMT) From: Nate Nielsen <nielsen-list@memberwebs.com> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-hackers@freebsd.org Subject: Re: devctl attach/detach notification for disks Message-ID: <20060225185629.E0BA1DCAA41@mail.npubs.com> References: <20060222190919.C6B9FDCA99B@mail.npubs.com> <20060224.112310.48529779.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
M. Warner Losh wrote: > In message: <20060222190919.C6B9FDCA99B@mail.npubs.com> > Nate Nielsen <nielsen-list@memberwebs.com> writes: > : I'm working on a bit of code to get devctl notifications for attaching > : and removing of disks. This would allow actions to be taken via devd > : when a disk is attached or removed from the system. > > I'm not sure I like the API changes you've made to subr_bus. Why are > they needed? Currently the memory passed to devctl_queue_data is required to be allocated via M_BUS, which is declared static in subr_bus.c. The other option would be to put the M_BUS declaration in bus.h. > : Currently I have the attach and detach notifications hooked into > : disk_create() and disk_destroy() in geom_disk.c. See attached (rough) > : patch. > : > : However at these points the disks are not yet present in the /dev/ > : filesystem. Anyone have any clues or tips for a better place to hook > : these notifications into the system? > > That's one of the main reasons that this hasn't happened yet. The > hard part is getting all of the devices in place before sending > notifications. Robert Watson had a similar thing that I think solved > some of the problems a little better... K, well I guess this is out of my scope then. I'll just watch for umassX and other plugabble diskish devices, and then configure them after a 5 second delay or something. Cheers, Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060225185629.E0BA1DCAA41>