Date: Fri, 11 Jun 2004 12:53:07 -0500 From: "Chris" <bsdnewbie@coolarrow.com> To: freebsd-current@FreeBSD.org Subject: Re[2]: Bug report 64462 Message-ID: <200406111253070276.2A318324@coolarrow.com> In-Reply-To: <20040611165106.GB31651@diogenis.ceid.upatras.gr> References: <200406101254260359.250C5C0A@coolarrow.com> <40C9D0DB.5030305@cronyx.ru> <20040611155710.GX9228@elvis.mu.org> <40C9DC25.1030700@cronyx.ru> <20040611165106.GB31651@diogenis.ceid.upatras.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
*This message was transferred with a trial version of CommuniGate(tm) Pro* >FWIW, if merely ejecting the disk can fix things up (as mentioned in >the PR), then this is a non-bug; burncd(8) already features a '-e' >option to "eject the media when done". Hello, and thanks to everyone looking into this problem. I was using 4.x= prior to 5.x, and it worked fine. After changing to 5.x is when it stopped= working. Second, this is a remote box that is not here at my desktop...= ejecting the cd causes the spring-loaded tray to "pop" out, and someone= has to actually push it back in.... also, it's rack-mounted, and the tray= would hit the glass door if it tried to eject, unless someone opened the= rack door for me first. So ejecting the CD is not really an option for me. My main concern is that the burncd commands are exactly the same ones I was= using with 4.x, but this problem surfaced with 5.x, so that's why I= thought it might be a SW bug. I appreciate yalls help, Chris _________________________________________________________ Email harvesters eat this: sendjunkmailhere@coolarrow.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406111253070276.2A318324>