Skip to contentSkip to conversation

OT] Joerg Schilling flames Linux on his Blog

DISCUSSION Bodo Eggert 2 participants 2 messages May 26, 2005 5 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw
Quoted 9 lines · Bill Davidsen
Quoted 8 lines · Kyle Moffett
Quoted 7 lines · Joerg Schilling

"Bodo Eggert <[email protected]>"

Quoted 3 lines

I just burned a CD on my IDE-burner using mmc_cdr with cdrtools-2.01 (the one without the hack) on a vanilla 2.6.11.10. I can even scan both my SCSI and IDE devices using -dev=ATAPI, but not without -dev.

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

The unability to give this kind of convenience to cdrecord users is a result
of the refusal of the Linux kernel crew to include the kernel internal device instance numbers in the ioctl structures I need to read.

It's just strange if you're able to see my SCSI devices only through ATAPI.

Quoted 9 lines
Quoted 7 lines

There is a specific reason that the numbers are _kernel_internal_!!! I
set up
my udev so that my green CD burner is /dev/green_burner, and my blue CD burner
is /dev/blue_burner. Please tell me again why exactly I can't just give the
option -dev=/dev/green_burner and have it use my green CD burner?

You do realize that you can?

It's "unintentional and not supported". Users are supposed to convert the device name into scsi numbers (e.g. using lsscsi) in order to to enable cdrecord to peek around until it finds that number instead of directly opening the correct device.

Quoted 9 lines
Quoted 6 lines
Quoted 4 lines

Note that the fields are there but the information is intentionally obscured
for come of the calls just to make the life of cdrecord useers harder :-(

The information is obscured because userspace shouldn't know or care

So having you see the information to set up your udev is a good use and having Joerg use them is bad?

Udev is supposed to handle physical to logical mappings. No other program should need to care, except for lsscsi and similar programs.

Quoted 5 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line

(I'm running as user, and cdrecord has no need for suid bits.)

Which is fine if you have a system to dedicate to burning CDs. But on a loaded system Joerg is right, you get a better burn if you don't have the burnfree used.

If I need RT privileges, I'll need to suid untill the non-root RT support is ready and I'll be glad that it's supported.

Quoted 3 lines

Like any other minor defect it may or may not bite
you, a lot of them will measurably reduce your CD capacity, which actually will bite you if you are trying to use every last byte.

AFAI read, burnfree isn't supposed to do anything unless a buffer underrun occures. If that's true, I'd prefer a warning message to really destroying my CD.

Quoted 2 lines

There is an option if you would read the manpage. There are legitimate complaints, this doesn't seem to be one of them.

I had to write a wrapper, and wrappers tend to indicate bad programs.

Signature · 2 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
#6 lore raw
Quoted 2 lines · Bodo Eggert

If I need RT privileges, I'll need to suid untill the non-root RT support is ready and I'll be glad that it's supported.

It is in 2.6.12-rc5. You need to patch PAM (and bash, if you want to use ulimit) to use it.

Lee