LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-03-2005, 04:57 PM   #1
flebber
Member
 
Registered: Jan 2005
Location: Newcastle, Australia
Distribution: debian stable
Posts: 394

Rep: Reputation: 30
fstab cdburner


Hi

I am running slack 10.1 and running kernel-2.6.11.8 which i just finished doing, am having a problem with the permissions for the cd player.

I have seen several posts as it is actually seeing my burner its fstab is
/dev/sr0 /mnt/burner iso9660 noauto,ro,user 0 0


I thought I would try something I read in another post about this and that was to

chmod 666 /dev/sr0

Ok so it saw the cd rom then and brought up a track list but that was it Slackware froze couldn't unfreeze it ctrl+F1 ..ctrl+Esc+F1 nothing but the power off button would turn it off.

What did I do? what can I do to get the device working normally?

Last edited by flebber; 05-04-2005 at 12:15 AM.
 
Old 05-03-2005, 06:21 PM   #2
Tinkster
Moderator
 
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928
I don't use 2.6 kernels (yet) but I believe to have read
that since 2.6.8 ide-scsi is broken (on purpose) ... so if
the burner isn't an actual SCSI device you may want
to omit the ide-scsi and use the ATA interface ... versions
2.0.1x of cdrecord should be working with the newer
kernels.

On another note: 2.6 kernels use udev, the perms are
set on each boot according to /etc/udev

Cheers,
Tink

Last edited by Tinkster; 05-03-2005 at 06:24 PM.
 
Old 05-03-2005, 09:41 PM   #3
April
LQ Newbie
 
Registered: Apr 2005
Distribution: Slackware 10.1
Posts: 18

Rep: Reputation: 0
Tinkster,

do you have a link where we could read more about this?
So, support for SCSI devices [edit: SCSI emulation!] is going to be lost entirely? Why?

Last edited by April; 05-03-2005 at 10:14 PM.
 
Old 05-03-2005, 09:44 PM   #4
April
LQ Newbie
 
Registered: Apr 2005
Distribution: Slackware 10.1
Posts: 18

Rep: Reputation: 0
hmmm.... just found this article

http://www.reactivated.net/weblog/ar...nt-26-kernels/
 
Old 05-03-2005, 09:47 PM   #5
Tinkster
Moderator
 
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928
Quote:
Originally posted by April
So, support for SCSI devices is going to be lost entirely? Why?
SCSI won't be lost - ide-scsi emulation will... as for the
why: the kernel developers think of it as a kludge.

The link April provided pretty much states it :)


Cheers,
Tink
 
Old 05-04-2005, 12:08 AM   #6
flebber
Member
 
Registered: Jan 2005
Location: Newcastle, Australia
Distribution: debian stable
Posts: 394

Original Poster
Rep: Reputation: 30
ok read article and understand what is happening but not not sure how to add myself(user) to the /dev/sr0 group...

I received the OK echo from root, but from my user a/c received no echo or error

root@flebslack:/home/flebber# [ -w /dev/sr0 ] && echo "OK"
OK

&

root@flebslack:/home/flebber# ls -lF /dev/sr0
brw-rw---- 1 root cdrom 11, 0 2005-05-05 00:49 /dev/sr0


So I can assume its a permissions error so how would I add myself so that user has priviledges for reading and writing.

If I edit my /etc/group file inserting user name as follows, I have but a cdrom entry, no burner or /dev/sr0 entry:

news::13:news
uucp::14:uucp
man::15:
audio::17:flebber
video::18:
cdrom::19:flebber

Last edited by flebber; 05-04-2005 at 12:28 AM.
 
Old 05-04-2005, 01:12 AM   #7
Tinkster
Moderator
 
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928
You'd add the users who you want to be able to burn
to the group cdrom

But you're still using the ide-scsi device?

Your burner should be something like /dev/hdd if you
don't ...



Cheers,
Tink
 
Old 05-04-2005, 01:16 AM   #8
April
LQ Newbie
 
Registered: Apr 2005
Distribution: Slackware 10.1
Posts: 18

Rep: Reputation: 0
flebber,

I've had the same problem. It seems like no matter what I do with groups, permissions, etc..I cant get permission to burn a CD as a regular user. So after trying everything else, I finally just made a SUID wrapper program. For example, using fireburner

as root:

burner.c

+------------------------------------------------------------+
main () {
setuid (0,0) ;
system ("/usr/local/bin/fireburner") ;
}

+------------------------------------------------------------+

gcc -o burner burner.c
chmod 4755

this way at least I can burn CD's as a regular user. Even though, fireburner IS running as root, it's better than nothing!

The only advantage to this over 'sudo fireburner' is that you don't have to enter a password or edit the sudoers file. But it makes for a nice quick way for users to burn CD's

Last edited by April; 05-04-2005 at 01:50 AM.
 
Old 05-04-2005, 05:29 AM   #9
cathectic
Member
 
Registered: Sep 2004
Location: UK, Europe
Distribution: Slackware64
Posts: 761

Rep: Reputation: 35
flebber,

If your drive is still being seen as /dev/sr0, remove/ comment out the line "append=hdc:ide-scsi" (or something like that) in /etc/lilo.conf, run /sbin/lilo and restart. Your drive should return to its correct designation, probably /dev/hdc or /dev/hdd
 
Old 05-04-2005, 02:19 PM   #10
April
LQ Newbie
 
Registered: Apr 2005
Distribution: Slackware 10.1
Posts: 18

Rep: Reputation: 0
I have a Lite On LTR-52327S. The original configuration was /dev/hdc, which /dev/cdrom pointed to. If left like this, running cdrecord --scanbus found nothing. The only way to get the cdrw recognized was to append the ide-scsi to lilo.conf. In which case, the designation became /dev/sr0.

I tried adding myself to the disk group [for /dev/hdc], I tried adding myself to the cdrom group and tried adding myself to both. And I tried adding a 'burners' group, which had write access to disk and cdrom. In none of these cases was I able to burn as a regular user.

Have any of you done this and actually burned a cd as a regular user? If so, maybe you can post EXACTLY what you did step by step and your configuration. Like I said, I have tried everything, and nothing worked.

Further, when adding 'append=ide-scsi /dev/hdc' to lilo.conf, running a program like 'eject' would no longer eject the cdrw tray, because it was no longer recognized as /dev/cdrom. You had to enter 'eject /dev/sr0'

So finally, after reading everything I could find on the subject, and trying everything I mentioned, I finally added "append=ide-scsi /dev/sr0' to lilo.conf and changed /dev/cdrom to point to /dev/sr0.

This way, cdrecord --scanbus would recognize the cdrw, and 'eject' would eject the cdrw. I added the wrapper that I mentioned above, so that as a user I could launch fireburner.

So please, like i said, if any of you have actually burned a cd as a regular user, please post your config and step by step what you did to get permission to burn as a regular user! Phew....

Thanks ;-)
 
Old 05-04-2005, 02:51 PM   #11
cathectic
Member
 
Registered: Sep 2004
Location: UK, Europe
Distribution: Slackware64
Posts: 761

Rep: Reputation: 35
April,

On 2.6 kernels:

1) You don't need ide-scsi (it's broken, don't touch it) or any append lines. Get rid of all append lines for the CDRW in lilo.conf

2) Ignore --scanbus - it can't pick up IDE devices (and it even tells you it has problems with post 2.5 kernels). Doesn't mean cdrecord can't write to the device.

3) Just use the /dev/hdX name for the device (not ATAPI:0,0,1 or anything else)

e.g.

cdrecord dev=/dev/hdd some.iso

4) Permissions:

The only 'permissions' I have changed is that I am a member of cdrom.
 
Old 05-04-2005, 03:17 PM   #12
April
LQ Newbie
 
Registered: Apr 2005
Distribution: Slackware 10.1
Posts: 18

Rep: Reputation: 0
Okay....thank you

I am actually still using the original 10.1 2.4.29 kernel, but what you said about scanbus not picking up IDE devices explains everything. I assumed that because cdrecord --scanbus could not identify the device, that it wasn't working! So all I really have to do is put back the original configuration and use /dev/hdc, and add myself to the cdrom group. cool!

One last question though, cdrdao asks you to use the format of ATAPI:0,0,0, but can you go ahead and use /dev/hdc with cdrdao, or do you still have to use the ATAPI:0,0,0 format?

Last edited by April; 05-04-2005 at 03:18 PM.
 
Old 05-05-2005, 05:02 AM   #13
flebber
Member
 
Registered: Jan 2005
Location: Newcastle, Australia
Distribution: debian stable
Posts: 394

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by cathectic
flebber,

If your drive is still being seen as /dev/sr0, remove/ comment out the line "append=hdc:ide-scsi" (or something like that) in /etc/lilo.conf, run /sbin/lilo and restart. Your drive should return to its correct designation, probably /dev/hdc or /dev/hdd
I don't the append=hdc:ide-scsi line in fstab I just went and removed everything scsi from my kernel and rebuilt it in order to have it work, but I seem to have removed dma from my hard disk said on boot it will slow so I am going to have to track that down. My Fstab now reads:

# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/hda6 swap swap defaults 0 0
/dev/hda5 / reiserfs defaults 1 1
/dev/hda1 /fat-c ntfs auto,rw,unmask=000 1 0
/dev/cdrom /mnt/cdrom iso9660 noauto,ro 0 0
/dev/hdd /mnt/burner iso9660 noauto,ro,user 0 0
/dev/fd0 /mnt/floppy auto noauto, 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
none /sys sysfs defaults 0 0
user,exec,noauto,comment 0 0

And my error has now changed to this

dev/sr0 does not appear to point to a valid CD device. This may be because:
a) CD support is not present in your machine
b) You do not have the correct permissions to access the CD drive
c) /dev/sr0 is not the CD drive.

Press 'Set device' to go to a dialog where you can set the device, or press 'Quit' to quit the CD player
 
Old 05-05-2005, 06:14 AM   #14
cathectic
Member
 
Registered: Sep 2004
Location: UK, Europe
Distribution: Slackware64
Posts: 761

Rep: Reputation: 35
flebber,

Please read what I said carefully. Remove the append line from:
Code:
/etc/lilo.conf
rerun /sbin/lilo, restart. fstab has *nothing* to do with that.

/dev/sr0 problems are coming up because ide-scsi is not being used, but the append line in LILO prevents the drive from being seen as an IDE device (it caught me out the first time I upgraded to the 2.6 series).

Once that's done, find out what your CDRW/CD is being seen as and correct the /dev/sr0 entry in /etc/fstab (as I said before, it's probably /dev/hdc or /dev/hdd).
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
cdburner for users DavidPhillips Linux - General 10 01-19-2005 02:16 PM
delete cdrom/cdburner cabinetcrafter Mandriva 2 10-31-2004 10:50 AM
cdburner not working right zeroability Linux - Newbie 4 05-17-2003 02:21 AM
cdburner reads not writes NGraphiX Linux - Hardware 1 02-28-2003 04:29 AM
cdburner crapped out crashmeister Linux - Hardware 3 11-06-2002 09:06 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:01 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration