src/usr.sbin/burncd, branch stable/8 FreeBSD source tree MFC: r226179 2012-03-30T23:48:15+00:00 Marius Strobl marius@FreeBSD.org 2012-03-30T23:48:15+00:00 35a4e25e132564c8b0b0f7fd0b464547eb3c05a2 Add a "kern.features.ata_cam" sysctl in the kernel when the ATA_CAM kernel option is defined. This sysctl can be queried by feature_present(3). Query for this feature in /sbin/atacontrol and /usr/sbin/burncd. If these utilities detect that ATA_CAM is enabled, then these utilities will error out. These utilities are compatible with the old ATA driver, but are incomptible with the new ATA_CAM driver. By erroring out, we give end-users an idea as to what remedies to use, and reduce the need for them to file PR's. For atacontrol, camcontrol must be used instead, and for burncd, alternative utilties from the ports collection must be used such as sysutils/cdrtools. In future, maybe someone can re-write burncd to work with ATA_CAM, but at least for now, we give a somewhat useful error message to end users. PR: 160979 Reviewed by: jh, Arnaud Lacombe <lacombar at gmail dot com> Reported by: Joe Barbish <fbsd8 at a1poweruser dot com> 
Add a "kern.features.ata_cam" sysctl in the kernel when the ATA_CAM kernel
option is defined.  This sysctl can be queried by feature_present(3).

Query for this feature in /sbin/atacontrol and /usr/sbin/burncd.
If these utilities detect that ATA_CAM is enabled, then these utilities
will error out.  These utilities are compatible with the old ATA
driver, but are incomptible with the new ATA_CAM driver.  By erroring out,
we give end-users an idea as to what remedies to use, and reduce the need for them
to file PR's.  For atacontrol, camcontrol must be used instead,
and for burncd, alternative utilties from the ports collection must be used
such as sysutils/cdrtools.

In future, maybe someone can re-write burncd to work with ATA_CAM,
but at least for now, we give a somewhat useful error message to end users.

PR:		160979
Reviewed by:	jh, Arnaud Lacombe <lacombar at gmail dot com>
Reported by:	Joe Barbish <fbsd8 at a1poweruser dot com>
MFC r206622,207939,208593,208732,209031: mdoc cleanup 2010-08-27T10:47:17+00:00 Ulrich Spörlein uqs@FreeBSD.org 2010-08-27T10:47:17+00:00 2b9d9e2d4b0f969796c995bbbc424bc6049b5ce1 - order prologue by Dd/Dt/Os - fix prologue - remove empty lines and other garbage - uppercase document title 
- order prologue by Dd/Dt/Os
- fix prologue
- remove empty lines and other garbage
- uppercase document title
MFC r202709: 2010-01-23T00:52:32+00:00 Xin LI delphij@FreeBSD.org 2010-01-23T00:52:32+00:00 aa0cab05173af275978dd31f695b623550dfe932 Give the right value when complaining it being wrong. Reported by: danfe 
Give the right value when complaining it being wrong.

Reported by:	danfe
MFC r200795: 2010-01-20T00:43:15+00:00 Xin LI delphij@FreeBSD.org 2010-01-20T00:43:15+00:00 3895783a8af9700f2bd42758178adcfe5372e146 Add support of using environment variable BURNCD_SPEED to specify recodring speed. PR: bin/140530 Submitted by: Alexander Best <alexbestms wwu.de> 
Add support of using environment variable BURNCD_SPEED to specify
recodring speed.

PR:		bin/140530
Submitted by:	Alexander Best <alexbestms wwu.de>
Correct the type for the global var accessed in sig handlers. 2009-01-05T16:47:42+00:00 David E. O'Brien obrien@FreeBSD.org 2009-01-05T16:47:42+00:00 613ff97130ca66fe1afafd67d67d25d68f511dd5 






Make signal handler safer.
2008-12-23T17:57:17+00:00

David E. O'Brien
obrien@FreeBSD.org

2008-12-23T17:57:17+00:00

11a2f37eed203da09cf1a391024e38d18b36eeb7

Submitted by:	Jaakko Heinonen <jh@saunalahti.fi>





Submitted by:	Jaakko Heinonen <jh@saunalahti.fi>







burncd(8) doesn't handle signals and interrupting burncd during operation.
2008-12-19T20:20:14+00:00

David E. O'Brien
obrien@FreeBSD.org

2008-12-19T20:20:14+00:00

970bfaf67f4cf77dbc4a9b4ca8019b6e9638ae3a

For example, ^C (SIGINT) may leave the drive spinning and locked.
This may also happen if you try to write a too-large image to a disc
and burncd(8) exits with an I/O error.

Add signal handling by doing a CDRIOCFLUSH ioctl to attempt to leave
burner in a sane state when burning is interrupted with SIGHUP, SIGINT,
SIGTERM, or in case an I/O error occurs during write.
Note, that blanking will still continue after interrupt but it seems to
finish correctly even after burncd(8) has quit.

Also, while I'm here bump WARNS to "6".

PR:		48730
Submitted by:	Jaakko Heinonen <jh@saunalahti.fi>





For example, ^C (SIGINT) may leave the drive spinning and locked.
This may also happen if you try to write a too-large image to a disc
and burncd(8) exits with an I/O error.

Add signal handling by doing a CDRIOCFLUSH ioctl to attempt to leave
burner in a sane state when burning is interrupted with SIGHUP, SIGINT,
SIGTERM, or in case an I/O error occurs during write.
Note, that blanking will still continue after interrupt but it seems to
finish correctly even after burncd(8) has quit.

Also, while I'm here bump WARNS to "6".

PR:		48730
Submitted by:	Jaakko Heinonen <jh@saunalahti.fi>







- Remove MLINKS to nonexistant manpages
2005-07-14T20:29:08+00:00

Christian Brueffer
brueffer@FreeBSD.org

2005-07-14T20:29:08+00:00

f0ea72a038914507b9dec8491d46ee3974c43169

- Change some section numbers to match reality
- For MLINKS to manpages from ports, mention which port installs them

MFC after:	3 days





- Change some section numbers to match reality
- For MLINKS to manpages from ports, mention which port installs them

MFC after:	3 days







Fix the "only wrote -1 of 32768 bytes: Input/output error" error message.
2005-05-13T20:06:44+00:00

Ruslan Ermilov
ru@FreeBSD.org

2005-05-13T20:06:44+00:00

de6a1361a5d5f8d79402071ccd28948e041f3ee4












Document the device burncd uses by default.
2005-05-02T11:59:21+00:00

Christian Brueffer
brueffer@FreeBSD.org

2005-05-02T11:59:21+00:00

756d2046fb7768520443eb40e50c5bf5be611e65

Submitted by:	Christoph Mallon <christoph.mallon@gmx.de>
MFC after:	3 days





Submitted by:	Christoph Mallon <christoph.mallon@gmx.de>
MFC after:	3 days