Date: Thu, 24 Feb 2011 14:35:51 -0600 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org, Mitya <mitya@cabletv.dp.ua> Subject: Re: Cosmetic path to bsdinstall Message-ID: <4D66C127.6060701@freebsd.org> In-Reply-To: <201102241514.19727.jhb@freebsd.org> References: <4D64FF99.2070908@cabletv.dp.ua> <4D66729C.6040303@freebsd.org> <201102241514.19727.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/24/11 14:14, John Baldwin wrote: > On Thursday, February 24, 2011 10:00:44 am Nathan Whitehorn wrote: >> Thanks! I've received basically this patch from a couple people now. I'm >> going to investigate whether this is a more generic way to get this >> information (so the list doesn't grow infinitely long), and will commit >> this if I can't. Having CAM devices be part of newbus would simplify >> this a very great deal... > Note that all these disk devices are not CAM devices, so CAM changing to > use new-bus wouldn't really matter one whit. They do all show up as 'DISK' > GEOM's however (I also hacked on a GEOM-based libdisk replacement at one > point, though probably less developed than Marcel's. I used libgeom to > discover DISK devices.) Given that disk_create() already hooks into GEOM, > that is probably the right way to discover disks in a generic fashion. Right, stepping through that is how I build the list. Adding a device description to the XML actually seems like a good idea (and maybe the drive serial number?). Would anyone have any objections to me starting to go through and do that? -Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D66C127.6060701>