Re: [gentoo-user] cannot burn cd: permissions error
Andrey Vul [EMAIL PROTECTED] wrote: Unfortunately, the gentoo people say that cdrkit does it without root, why can't cdrtools? http://bugs.gentoo.org/show_bug.cgi?id=116026 Well, imaging there is a road that ends in an abyss and there is a sign beware of the abyss and some people remove that sign and replace it with a sign There is no abyss, just drive on, what do you believe will happen with the prople who drive on? The same has been done by the people behind wodim. These people have no clue how cdrecord or wodim works and they just removed the checks and warnings in the wodim source. Wodim still fails but the user don't know anymore that this is a result of missing privileges. I don't care about the wrong information in the bugreport at: http://bugs.gentoo.org/show_bug.cgi?id=116026 Some people on Linux are a bit problemactic to deal with as they miss the needed skills to discuss a problem. The wrong comments in this bugreport have been written by such people. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
Re: [gentoo-user] cannot burn cd: permissions error
Allan Gottlieb [EMAIL PROTECTED] wrote: Joerg believes that cdrkit is not as good as cdrtools (I have used only cdrtools and it works well for me). Believes is less that knows. I know that if you take a very old source and add new bugs that the result cannot be better than the maintained original. In contrary to the people behing cdrkit, I carefully listen to the problems uf the users and I add bug-fixes for cdrtools or workarounds for defective drive firmware or conceptional bugs in e.g. the Linux kernel. As a result, there are much less problems with the original software than with the fork. Debates like this go on for far too long on the list. I think you should accept that: 1. cdrecord needs to be suid root 2. joerg is the expert on cdrtools including cdrecord 3. If you do not wish to install cdrecord suid root, you can try cdrkit, but then you cannot expect joerg to help. wodim is known to have problems if not installed suid root. The fact that several warnings about this fact have been removed by the people behind wodim just makes the related failures obscure and not easily assignable to missing privileges. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
Re: [gentoo-user] cannot burn cd: permissions error
At Wed, 10 Dec 2008 11:00:39 +0100 [EMAIL PROTECTED] (Joerg Schilling) wrote: Allan Gottlieb [EMAIL PROTECTED] wrote: Joerg believes that cdrkit is not as good as cdrtools (I have used only cdrtools and it works well for me). Believes is less that knows. I was/am trying to sound neutral and not spark a long debate. I know that if you take a very old source and add new bugs that the result cannot be better than the maintained original. In contrary to the people behing cdrkit, No comment. I carefully listen to the problems uf the users and I add bug-fixes for cdrtools or workarounds for defective drive firmware or conceptional bugs in e.g. the Linux kernel. I very much agree and appreciate your helpful comments on this mailing list with regard to technical questions involving use of cdrtools As a result, there are much less problems with the original software than with the fork. I have not used the fork, but will say that cdrtools works well for me, thanks in part to your helpful technical comments on this list. thank you for cdrtools, allan
Re: [gentoo-user] cannot burn cd: permissions error
Andrey Vul [EMAIL PROTECTED] wrote: Just follow my advise... Jörg Unfortunately, the gentoo people say that cdrkit does it without root, why can't cdrtools? http://bugs.gentoo.org/show_bug.cgi?id=116026 Let me append a proof for the incorrectness of the claim that wodim does not need root privileges: http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/fc4ec2e74849c6a?q=wodim#eb7d42e724ffebf9 If you look at the first problem where wodium returns: wodim: Cannot load media. This is _definitely_ a result of missing root privileges. Most people however would not understand the relation between the problem and the missing root privileges because the wodim peiple removed the warning message that explains the problem. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
Re: [gentoo-user] cannot burn cd: permissions error
Andrey Vul wrote: I get the following error: [EMAIL PROTECTED] ~ $ cdrecord dev=ATA:1,0,0 vmware/Windows\ XP\ Professional/shared/vLite.iso ... cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. I'm not familiar with cdrecord, but have you tried this?
Re: [gentoo-user] cannot burn cd: permissions error
Andrey Vul [EMAIL PROTECTED] wrote: I get the following error: [EMAIL PROTECTED] ~ $ cdrecord dev=ATA:1,0,0 vmware/Windows\ XP\ Professional/shared/vLite.iso cdrecord: No write mode specified. cdrecord: Asuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a53 (i686-pc-linux-gnu) Copyright (C) 1995-2008 JÃ?rg Schilling cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2). cdrecord: WARNING: This causes a high risk for buffer underruns. cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). cdrecord: WARNING: This causes a high risk for buffer underruns. scsidev: 'ATA:1,0,0' devname: 'ATA' scsibus: 1 target: 0 lun: 0 Warning: Using badly designed ATAPI via /dev/hd* interface. Linux sg driver version: 3.5.27 cdrecord: No such file or directory. Cannot open '/dev/hd*'. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. You did not install cdrecord correctly (suid root is needed). You called cdrecord with an outdated dev= argument. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
Re: [gentoo-user] cannot burn cd: permissions error
On Tue, Dec 9, 2008 at 03:47, Joerg Schilling [EMAIL PROTECTED] wrote: Andrey Vul [EMAIL PROTECTED] wrote: I get the following error: [EMAIL PROTECTED] ~ $ cdrecord dev=ATA:1,0,0 vmware/Windows\ XP\ Professional/shared/vLite.iso [snip] cdrecord: No such file or directory. Cannot open '/dev/hd*'. Cannot open or use SCSI driver. This error is bothering me. It happens even when ran as root, yet I have /dev/hdc. You did not install cdrecord correctly (suid root is needed). I need to suid root a program that fails when ran as root?!?!? Something is very wrong. You called cdrecord with an outdated dev= argument. I had permission denied on /dev/sg0 too, so dev= is sort of irrelevant. Also, I had the same error during cdrecord -scanbus, even though I am in the cdrom and disk groups. Also, the same error happened when it was run *as root*. And not sudo, but su. -- Andrey Vul A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: [gentoo-user] cannot burn cd: permissions error
Andrey Vul schrieb: On Tue, Dec 9, 2008 at 03:47, Joerg Schilling [EMAIL PROTECTED] wrote: Andrey Vul [EMAIL PROTECTED] wrote: I get the following error: [EMAIL PROTECTED] ~ $ cdrecord dev=ATA:1,0,0 vmware/Windows\ XP\ Professional/shared/vLite.iso [snip] cdrecord: No such file or directory. Cannot open '/dev/hd*'. Cannot open or use SCSI driver. This error is bothering me. It happens even when ran as root, yet I have /dev/hdc. You did not install cdrecord correctly (suid root is needed). I need to suid root a program that fails when ran as root?!?!? Something is very wrong. You called cdrecord with an outdated dev= argument. I had permission denied on /dev/sg0 too, so dev= is sort of irrelevant. Also, I had the same error during cdrecord -scanbus, even though I am in the cdrom and disk groups. Also, the same error happened when it was run *as root*. And not sudo, but su. When I run cdrecord I do it as root with the following command: cdrecord -dev=4,0,0 -gracetime=3 -v -dao -speed=4 /path/to/my/file.iso In fact I did not find a translation for suid root root to german, so I don't know what that means. kh
Re: [gentoo-user] cannot burn cd: permissions error
Andrey Vul [EMAIL PROTECTED] wrote: On Tue, Dec 9, 2008 at 03:47, Joerg Schilling [EMAIL PROTECTED] wrote: Andrey Vul [EMAIL PROTECTED] wrote: I get the following error: [EMAIL PROTECTED] ~ $ cdrecord dev=ATA:1,0,0 vmware/Windows\ XP\ Professional/shared/vLite.iso [snip] cdrecord: No such file or directory. Cannot open '/dev/hd*'. Cannot open or use SCSI driver. This error is bothering me. It happens even when ran as root, yet I have /dev/hdc. So you installed it suid to an unprivileged user. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
Re: [gentoo-user] cannot burn cd: permissions error
On Tue, Dec 9, 2008 at 14:18, Joerg Schilling [EMAIL PROTECTED] wrote: So you installed it suid to an unprivileged user. Should I do 'chown root:cdrom' for /dev/hd* or 'chown root:disk' for /dev/sg*? Which is preferred? And what is group bin supposed to be for? Apparently /usr/bin/cdrecord is suid bin:bin. I am facepalming myself right now. -- Andrey Vul A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: [gentoo-user] cannot burn cd: permissions error
Andrey Vul [EMAIL PROTECTED] wrote: On Tue, Dec 9, 2008 at 14:18, Joerg Schilling [EMAIL PROTECTED] wrote: So you installed it suid to an unprivileged user. Should I do 'chown root:cdrom' for /dev/hd* or 'chown root:disk' for /dev/sg*? Which is preferred? If you like to make your system inherently insecure, do this! And what is group bin supposed to be for? Apparently /usr/bin/cdrecord is suid bin:bin. This is wrong as mentioned before. I told you to do what's in the cdrecord documentation: Install cdrecord suid root. Just follow my advise... Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
Re: [gentoo-user] cannot burn cd: permissions error
On Tue, Dec 9, 2008 at 17:39, Joerg Schilling [EMAIL PROTECTED] wrote: Andrey Vul [EMAIL PROTECTED] wrote: On Tue, Dec 9, 2008 at 14:18, Joerg Schilling [EMAIL PROTECTED] wrote: So you installed it suid to an unprivileged user. Should I do 'chown root:cdrom' for /dev/hd* or 'chown root:disk' for /dev/sg*? Which is preferred? If you like to make your system inherently insecure, do this! And what is group bin supposed to be for? Apparently /usr/bin/cdrecord is suid bin:bin. This is wrong as mentioned before. I told you to do what's in the cdrecord documentation: Install cdrecord suid root. Just follow my advise... Jörg Unfortunately, the gentoo people say that cdrkit does it without root, why can't cdrtools? http://bugs.gentoo.org/show_bug.cgi?id=116026 -- Andrey Vul A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: [gentoo-user] cannot burn cd: permissions error
At Tue, 09 Dec 2008 18:44:21 -0500 Andrey Vul [EMAIL PROTECTED] wrote: On Tue, Dec 9, 2008 at 17:39, Joerg Schilling [EMAIL PROTECTED] wrote: Andrey Vul [EMAIL PROTECTED] wrote: On Tue, Dec 9, 2008 at 14:18, Joerg Schilling [EMAIL PROTECTED] wrote: So you installed it suid to an unprivileged user. Should I do 'chown root:cdrom' for /dev/hd* or 'chown root:disk' for /dev/sg*? Which is preferred? If you like to make your system inherently insecure, do this! And what is group bin supposed to be for? Apparently /usr/bin/cdrecord is suid bin:bin. This is wrong as mentioned before. I told you to do what's in the cdrecord documentation: Install cdrecord suid root. Just follow my advise... Jörg Unfortunately, the gentoo people say that cdrkit does it without root, why can't cdrtools? http://bugs.gentoo.org/show_bug.cgi?id=116026 Joerg believes that cdrkit is not as good as cdrtools (I have used only cdrtools and it works well for me). Debates like this go on for far too long on the list. I think you should accept that: 1. cdrecord needs to be suid root 2. joerg is the expert on cdrtools including cdrecord 3. If you do not wish to install cdrecord suid root, you can try cdrkit, but then you cannot expect joerg to help. Again, I should say that I have not used cdrkit so am not commenting on its quality. allan
Re: [gentoo-user] cannot burn cd: permissions error
On Tue, Dec 9, 2008 at 19:46, Allan Gottlieb [EMAIL PROTECTED] wrote:
At Tue, 09 Dec 2008 18:44:21 -0500 Andrey Vul [EMAIL PROTECTED] wrote:
On Tue, Dec 9, 2008 at 17:39, Joerg Schilling
[EMAIL PROTECTED] wrote:
Andrey Vul [EMAIL PROTECTED] wrote:
On Tue, Dec 9, 2008 at 14:18, Joerg Schilling
[EMAIL PROTECTED] wrote:
So you installed it suid to an unprivileged user.
Should I do 'chown root:cdrom' for /dev/hd* or 'chown root:disk' for
/dev/sg*?
Which is preferred?
If you like to make your system inherently insecure, do this!
And what is group bin supposed to be for? Apparently /usr/bin/cdrecord
is suid bin:bin.
This is wrong as mentioned before.
I told you to do what's in the cdrecord documentation: Install cdrecord suid
root.
Just follow my advise...
Jörg
Unfortunately, the gentoo people say that cdrkit does it without
root, why can't cdrtools?
http://bugs.gentoo.org/show_bug.cgi?id=116026
Joerg believes that cdrkit is not as good as cdrtools (I have used only
cdrtools and it works well for me).
Debates like this go on for far too long on the list. I think you
should accept that:
1. cdrecord needs to be suid root
2. joerg is the expert on cdrtools including cdrecord
3. If you do not wish to install cdrecord suid root, you can try cdrkit,
but then you cannot expect joerg to help.
Again, I should say that I have not used cdrkit so am not commenting on
its quality.
cdrecord (wodim) had support for dev=/dev/hdX. That was its only advantage.
genisoimage filed in comparison to mkisofs.
In short, cdrtools is better.
What are the chances that suid root would be allowed in an ebuild
patch *without* reigniting the cdr{kit,tools} flamewar?
--
Andrey Vul
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Re: [gentoo-user] cannot burn cd: permissions error
Andrey Vul wrote: On Tue, Dec 9, 2008 at 17:39, Joerg Schilling [EMAIL PROTECTED] wrote: Andrey Vul [EMAIL PROTECTED] wrote: On Tue, Dec 9, 2008 at 14:18, Joerg Schilling [EMAIL PROTECTED] wrote: So you installed it suid to an unprivileged user. Should I do 'chown root:cdrom' for /dev/hd* or 'chown root:disk' for /dev/sg*? Which is preferred? If you like to make your system inherently insecure, do this! And what is group bin supposed to be for? Apparently /usr/bin/cdrecord is suid bin:bin. This is wrong as mentioned before. I told you to do what's in the cdrecord documentation: Install cdrecord suid root. Just follow my advise... Jörg Unfortunately, the gentoo people say that cdrkit does it without root, why can't cdrtools? http://bugs.gentoo.org/show_bug.cgi?id=116026 I have this installed: [I--] [ ~] app-cdr/cdrtools-2.01.01_alpha52 (0) I use k3b but cdrtools seems to work very well here, since k3b uses cdrtools to burn. I went down the cdrkit before and it was a unpleasant experience. Jörg and a few others helped shine the light on cdrtools and I have been burning DVD's and CDs ever since. I would uninstall cdrkit and just give cdrtools a shot. You can always switch back if you want. Dale :-) :-)
[gentoo-user] cannot burn cd: permissions error
I get the following error: [EMAIL PROTECTED] ~ $ cdrecord dev=ATA:1,0,0 vmware/Windows\ XP\ Professional/shared/vLite.iso cdrecord: No write mode specified. cdrecord: Asuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a53 (i686-pc-linux-gnu) Copyright (C) 1995-2008 Jörg Schilling cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2). cdrecord: WARNING: This causes a high risk for buffer underruns. cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). cdrecord: WARNING: This causes a high risk for buffer underruns. scsidev: 'ATA:1,0,0' devname: 'ATA' scsibus: 1 target: 0 lun: 0 Warning: Using badly designed ATAPI via /dev/hd* interface. Linux sg driver version: 3.5.27 cdrecord: No such file or directory. Cannot open '/dev/hd*'. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. [EMAIL PROTECTED] ~ $ ls /dev/hd* -lh brw-rw 1 root disk 3, 0 Dec 8 14:06 /dev/hda brw-rw 1 root disk 3, 1 Dec 8 14:06 /dev/hda1 brw-rw 1 root disk 3, 2 Dec 9 02:15 /dev/hda2 brw-rw 1 root disk 3, 64 Dec 8 14:06 /dev/hdb brw-rw 1 root disk 3, 65 Dec 8 14:06 /dev/hdb1 brw-rw 1 root disk 3, 66 Dec 8 14:06 /dev/hdb2 brw-rw 1 root disk 3, 67 Dec 8 14:06 /dev/hdb3 brw-rw 1 root disk 3, 69 Dec 8 14:06 /dev/hdb5 brw-rw 1 root disk 3, 70 Dec 8 14:06 /dev/hdb6 brw-rw 1 root cdrom 22, 0 Dec 8 14:06 /dev/hdc [EMAIL PROTECTED] ~ $ groups tty disk lp mem wheel audio cdrom video games usb andrey How do I solve this (it's not a hardware issue)? -- Andrey Vul A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
