From owner-freebsd-questions@FreeBSD.ORG Thu Mar 18 09:24:11 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDD5716A4CE for ; Thu, 18 Mar 2004 09:24:11 -0800 (PST) Received: from server.tcslea.org (server.tcslea.org [205.238.132.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E07843D2D for ; Thu, 18 Mar 2004 09:24:11 -0800 (PST) (envelope-from bsdnewbie@coolarrow.com) Received: from [205.238.178.119] (HELO system) by server.tcslea.org (CommuniGate Pro SMTP 4.1.8) with ESMTP id 240065 for freebsd-questions@freebsd.org; Thu, 18 Mar 2004 11:25:55 -0600 Message-ID: <200403181124090793.467D23A7@coolarrow.com> In-Reply-To: <44fzc66saz.fsf@be-well.ilk.org> References: <200403180935440470.461A17AA@coolarrow.com> <44fzc66saz.fsf@be-well.ilk.org> X-Mailer: Courier 3.50.00.01.1091 (http://www.rosecitysoftware.com) (P) Date: Thu, 18 Mar 2004 11:24:09 -0600 From: "Chris" To: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re[2]: cdrom mount problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Mar 2004 17:24:12 -0000 *This message was transferred with a trial version of CommuniGate(tm) Pro* >> In summary: the only way to mount my cdrom after burning an ISO >> is to reboot first. >Try ejecting and re-loading the disk. >I've seen some firmware that gets confused easily in these cases... I use the CDRW to burn backup files every night via cron, so driving to the= machine (45 min away) and cycling the drive is not feasible. Further, this= was never an issue with 4.x releases, and if I'm not mistaken, 5.1 either.= I think this started somewhere with 5.2 and beyond. >You first have to unmount the cdrom before you can mount >a new cd, you can do that by typing: >umount /cdrom Normally it's not in a mounted state after burning, as best I recall. But= I've tried that several times anyway, to no avail. Thanks for the= suggestion. >Looks like bug. Submit problem report on it, is only way it will be >looked at and fixed by 5.x development team. This is possible, I guess. Makes since, as this problem cropped up after= upgrading. I could be wrong, but it seems that since mount does not do= anything different from the point just before reboot and just after= reboot, perhaps it's more likely the burncd command not "releasing" the= cdrw drive properly, or something like that... Thanks, Chris _________________________________________________________ Email harvesters eat this: sendjunkmailhere@coolarrow.com