Date: Tue, 16 Jan 2001 23:31:53 +0000 From: Josef Karthauser <joe@tao.org.uk> To: Paul Richards <paul@freebsd-services.co.uk> Cc: Josef Karthauser <joe@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/compat/linux linux_stats.c Message-ID: <20010116233153.E1731@tao.org.uk> In-Reply-To: <3A64D05A.ABFD3322@freebsd-services.co.uk>; from paul@freebsd-services.co.uk on Tue, Jan 16, 2001 at 10:51:06PM %2B0000 References: <200101142333.f0ENXqB09391@freefall.freebsd.org> <3A64D05A.ABFD3322@freebsd-services.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 16, 2001 at 10:51:06PM +0000, Paul Richards wrote: > Josef Karthauser wrote: > > Log: > > Instead of hard coding the major numbers for IDE and SCSI disks > > look in the device's cdevsw for the D_DISK flag. > > Ahh, I didn't commit this because it's not just IDE and SCSI disks that > have D_DISK set. CDROM's also have it set, as do md and vn devices and I > wasn't sure that they should be remapped in the same way as IDE and SCSI > disks, particularly the mapping of the major number to 0, which I wasn't > even sure was right for SCSI disks. > > I think what is needed is a more generic solution, such as a table that > maps FreeBSD devices to Linux devices as appropriate. On the assumption that linux uses block mode for all "disk" access it seems like the correct thing to do. I'll verify that vmware still accesses the cdrom device... md's and vn's aren't going to be directly accessed by the linuxulator (are they?), rather accessed as pre-mounted filesystems. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010116233153.E1731>