From owner-freebsd-bugs Thu Apr 20 10:10: 5 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A322637BE39 for ; Thu, 20 Apr 2000 10:10:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id KAA40694; Thu, 20 Apr 2000 10:10:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 20 Apr 2000 10:10:02 -0700 (PDT) Message-Id: <200004201710.KAA40694@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Bauer Subject: Re: misc/18108: strange dev assignment with multiple scsi cdrom drives Reply-To: David Bauer Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/18108; it has been noted by GNATS. From: David Bauer To: "Kenneth D. Merry" Cc: "FreeBSD-gnats-submit@FreeBSD.ORG" Subject: Re: misc/18108: strange dev assignment with multiple scsi cdrom drives Date: Thu, 20 Apr 2000 17:03:51 +0000 "Kenneth D. Merry" wrote: > cd1{a,c} and cd0{a,c} both have the same minor numbers. That is why you > were able to mount cd0 as cd1. OK! But even with this setup I could not mount cd0c but only cd1c. > > As for why you couldn't mount cd0 -- were you root when you tried to mount > it? Yes. If not I get the message: 'cd9660: Operation not permitted.' But what I got was 'Device not configured' > > Try re-making your CD devices, like this: > > sh MAKEDEV cd4 > > That will make cd0->cd3. This cleanup solved the problem. But it is exactly what I have done before but only with MAKEDEV cd1. There are only 2 SCSI CDROMS (0 and 1). What I have changed in the meantime were the SCSI IDs because in messages the cd1 was probed before cd0. But now if I change it back it also works. So no idea what was the reason. Many thanks !. David. -- Dr. David Bauer GenProfile AG, Robert-Roessle-Str. 10, D-13125 Berlin, Germany Tel:+49-30-94892165, Fax:+49-30-94892151 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message