ead...@freebsd.org wrote:
Synopsis: 9.0 burncd error caused by change to cd0 from acd0
State-Changed-From-To: open-analyzed
State-Changed-By: eadler
State-Changed-When: Mon Sep 26 23:24:00 UTC 2011
State-Changed-Why:
requires only a release notes entry; use cdrecord instead of burncd
http
On 09/26/2011 17:59, Fbsd8 wrote:
Your solution is very un-professional.
Good thing we're all volunteers. :)
What your solution purposes to do
is do nothing. I think your judgment is flawed and a larger group of
your peers need to review your judgment in this case.
Ok, done. Eitan is
On 09/26/2011 18:43, Craig Rodrigues wrote:
On Mon, Sep 26, 2011 at 6:28 PM, Doug Barton do...@freebsd.org wrote:
burncd has been part of the system utilities included in the basic
release since release 4.0 and cdrecord is a port. The professional
solution is to remove burncd from the 9.0
On Mon, Sep 26, 2011 at 6:58 PM, Doug Barton do...@freebsd.org wrote:
I have used burncd on many releases of FreeBSD, on many machines
without problem. I can see the fact that burncd suddenly failing to
work on ATAPI hardware could annoy and confused end-users.
It doesn't fail to work on
On Mon, Sep 26, 2011 at 6:28 PM, Doug Barton do...@freebsd.org wrote:
burncd has been part of the system utilities included in the basic
release since release 4.0 and cdrecord is a port. The professional
solution is to remove burncd from the 9.0 system release and add the
cdrecord command to
On Mon, 26 Sep 2011, Craig Rodrigues wrote:
On Mon, Sep 26, 2011 at 6:58 PM, Doug Barton do...@freebsd.org wrote:
I have used burncd on many releases of FreeBSD, on many machines
without problem. I can see the fact that burncd suddenly failing to
work on ATAPI hardware could annoy and
On Mon, Sep 26, 2011 at 8:30 PM, Garrett Cooper yaneg...@gmail.com wrote:
...
Please fix it and move on.
Thanks,
-Garrett
$ usr.sbin/burncd/burncd -f /dev/cd0 blank
burncd: device provided not an acd(4) device: /dev/cd0.
Please verify that your kernel is built with acd(4) and the
On Mon, 26 Sep 2011, Craig Rodrigues wrote:
On Mon, Sep 26, 2011 at 8:30 PM, Garrett Cooper yaneg...@gmail.com wrote:
...
Please fix it and move on.
Thanks,
-Garrett
$ usr.sbin/burncd/burncd -f /dev/cd0 blank
burncd: device provided not an acd(4) device: /dev/cd0.
Please verify that
.. and if someone would like to contribute patches to burncd to update
it, I think there'd be at least one committer here who would be happy
to help you get your changes into the tree.
:-)
Adrian
___
freebsd-questions@freebsd.org mailing list
Aloha,
Recently when I try to use burncd I get this error when trying to burn
any 8 CURRENT discs . I even got a new Burner and put it on a different
machine but still get this error.
Install fails from these burned discs.
Error message.
acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11
On Thu, 14 Aug 2008 08:21:11 -1000, Al Plant [EMAIL PROTECTED] wrote:
Install fails from these burned discs.
Error message.
acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11
Defective media?
/dev/acd0c used to work. Now you have to use /dev/acd0 (no c) to get
burncd to work.
As far
Napoleon Dynamite wrote:
[ ...top posting recovered... ]
On Wednesday 07 June 2006 10:44, Michael S wrote:
I had the same kind of issue, also with 6.1-RELEASE, and just fixed it
the Windows way - reboot. And it worked fine.
I got that error pretty routinely for a while. The cd-r was always
On 6/8/06, Pablo Mora [EMAIL PROTECTED] wrote:
On 6/7/06, Josh Paetzel [EMAIL PROTECTED] wrote:
On Wednesday 07 June 2006 14:46, you wrote:
On Wednesday 07 June 2006 11:04, Josh Paetzel wrote:
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy#
On 6/7/06, Josh Paetzel [EMAIL PROTECTED] wrote:
On Wednesday 07 June 2006 14:46, you wrote:
On Wednesday 07 June 2006 11:04, Josh Paetzel wrote:
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate
next writeable LBA 0
writing from file i386pkg-3.0.iso size 710566 KB
written this track 710566 KB (100%) total 710566 KB
fixating CD, please wait..
burncd:
I had the same kind of issue, also with 6.1-RELEASE, and just fixed it
the Windows way - reboot. And it worked fine.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail
On Wednesday 07 June 2006 11:04, Josh Paetzel wrote:
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate
next writeable LBA 0
writing from file i386pkg-3.0.iso size 710566 KB
written this track 710566 KB
Josh Paetzel wrote:
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate
next writeable LBA 0
writing from file i386pkg-3.0.iso size 710566 KB
written this track 710566 KB (100%) total 710566 KB
fixating CD,
On Wednesday 07 June 2006 14:46, you wrote:
On Wednesday 07 June 2006 11:04, Josh Paetzel wrote:
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate
next writeable LBA 0
writing from file
I got that error pretty routinely for a while. The cd-r was always usable,
though. I switched to k3b for cd burning and have not seen that error since.
On Wednesday 07 June 2006 10:44, Michael S wrote:
I had the same kind of issue, also with 6.1-RELEASE, and just fixed it
the Windows way -
Josh Paetzel wrote:
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate
next writeable LBA 0
writing from file i386pkg-3.0.iso size 710566 KB
written this track 710566 KB (100%) total 710566 KB
I have been using mkisofs and burncd for some time now on 4.7-RELEASE
with no problems. I recently upgraded the same hardware to 4.8-RELEASE
(complete re-install) and now I notice that a backup script which
creates CD's of system tarballs now returns the following error on
completion:
Kevin Oberman [EMAIL PROTECTED] wrote:
I suspected that both -allow-lowercase and -allow-multidot were
implicit in -r, but I had never actually tried it.
No, they're not implicit, but they're not necessary either.
Let me explain ...
Standard ISO9660 filesystems have several limitations.
in message [EMAIL PROTECTED],
wrote Oliver Fromme thusly...
Kevin Oberman [EMAIL PROTECTED] wrote:
I suspected that both -allow-lowercase and -allow-multidot were
implicit in -r, but I had never actually tried it.
No, they're not implicit, but they're not necessary either.
Let me
Marco Beishuizen [EMAIL PROTECTED] wrote:
I am trying to burn cd's with burncd. The first thing I tried was to blank
an already burned cd with:
burncd -f /dev/acd1c -s 4 blank fixate
Don't fixate a blank CD-RW. Fixation is only required after
recording something on a CD-R or CD-RW.
On Fri, Oct 04, 2002 at 09:15:00PM +0200, Marco Beishuizen wrote:
Hi,
I am trying to burn cd's with burncd. The first thing I tried was to blank
an already burned cd with:
burncd -f /dev/acd1c -s 4 blank fixate
It seems that blanking is going ok, but when it tries to fixate I get
On Fri, 4 Oct 2002, the wise Oliver Fromme spoke, and said:
Marco Beishuizen [EMAIL PROTECTED] wrote:
I am trying to burn cd's with burncd. The first thing I tried was to blank
an already burned cd with:
burncd -f /dev/acd1c -s 4 blank fixate
Don't fixate a blank CD-RW. Fixation
Marco Beishuizen [EMAIL PROTECTED] wrote:
That did the trick. I wrote a file to the cd and fixate worked correctly.
At least I think it did, because when I want to mount the cd to look at
it, mount gives me an invalid argument error.
So my new problem is how to access a cd-rw with data
On Fri, 4 Oct 2002, the wise Oliver Fromme spoke, and said:
Marco Beishuizen [EMAIL PROTECTED] wrote:
That did the trick. I wrote a file to the cd and fixate worked correctly.
At least I think it did, because when I want to mount the cd to look at
it, mount gives me an invalid argument
Date: Fri, 4 Oct 2002 22:49:45 +0200 (CEST)
From: Marco Beishuizen [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
On Fri, 4 Oct 2002, the wise Oliver Fromme spoke, and said:
Marco Beishuizen [EMAIL PROTECTED] wrote:
That did the trick. I wrote a file to the cd and fixate worked
Sigh! Some days you just can't win. (Or type.)
I just read my own post and realized that I messed up the second
burncd command. the commands are:
mkisofs -allow-lower-case -allow-multidot -d -L -r -o ~/newcd.iso path
burncd -f /dev/acd0c blank
burncd -s 4 -f /dev/acd0c data ~/newcd.iso fixate
On Friday 04 October 2002 04:49 pm, Marco Beishuizen wrote:
| On Fri, 4 Oct 2002, the wise Oliver Fromme spoke, and said:
| Marco Beishuizen [EMAIL PROTECTED] wrote:
|That did the trick. I wrote a file to the cd and fixate worked
|correctly. At least I think it did, because when I want
On Fri, 4 Oct 2002, the wise Kevin Oberman spoke, and said:
Sigh! Some days you just can't win. (Or type.)
I just read my own post and realized that I messed up the second
burncd command. the commands are:
mkisofs -allow-lower-case -allow-multidot -d -L -r -o ~/newcd.iso path
burncd -f
Date: Sat, 5 Oct 2002 00:29:48 +0200 (CEST)
From: Marco Beishuizen [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Thanks! It worked great. I have one remark though: the option
-allow-lower-case wasn't recognised by mkisofs. Looking at the manpage
it should be -allow-lowercase. :-) But this
On Fri, 4 Oct 2002, the wise Kevin Oberman spoke, and said:
Date: Sat, 5 Oct 2002 00:29:48 +0200 (CEST)
From: Marco Beishuizen [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Thanks! It worked great. I have one remark though: the option
-allow-lower-case wasn't recognised by mkisofs.
Hi,
I am trying to burn cd's with burncd. The first thing I tried was to blank
an already burned cd with:
burncd -f /dev/acd1c -s 4 blank fixate
It seems that blanking is going ok, but when it tries to fixate I get the
following error:
burncd: ioctl(CDRIOCFIXATE): Input/output error
When I
36 matches
Mail list logo
