From owner-freebsd-current Sun Sep 27 00:44:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25674 for freebsd-current-outgoing; Sun, 27 Sep 1998 00:44:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA25668; Sun, 27 Sep 1998 00:44:35 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA01371; Sun, 27 Sep 1998 06:43:11 +0100 From: Luigi Rizzo Message-Id: <199809270543.GAA01371@labinfo.iet.unipi.it> Subject: Re: cd9660 mounts... To: dan@math.berkeley.edu (Dan Strick) Date: Sun, 27 Sep 1998 06:43:11 +0100 (MET) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199809270144.SAA22103@math.berkeley.edu> from "Dan Strick" at Sep 26, 98 06:43:55 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > mount -t cd9660 -o -s=0 /dev/wcd0tN /cdrom > > > > > > to mount the n-th track. > > > > I think this method is the best one, we can keep the mods in the ... > FreeBSD already relies far too heavily on a proliferation of > minor devices, each of which requires its own entry in /dev. > Exactly how large a (worst case) track number are we prepared > to handle? correct observation, especially because we would need 99 tracks :) In fact you are very right, i can easily add a -t option to mount_cd9660 to call the ioctl which selects the right track. This will double the complexity fo the kernel part but being still below 10 lines there should be no worries :) > Alternaticely, device drivers could have memory that transcends > close()es. In this case, one might issue commands like: > > settrack /dev/rwcd0 N > mount -t cd9660 /dev/wcd0 /cdrom this is worse, because would complicate putting this sort of things in say /etc/fstab thanks luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message