On Saturday 11 December 2004 09:13, Mrugesh Karnik wrote:
Hi,
I'm a newbie, so could I have instructions on how to do this?
as root, first make: #umount /dev/cdrecorder then open /etc/fstab file. There should be a line like: /dev/cdrecorder /media/cdrecorder subfs .... Duplicate this line and put "#" in the beginning of one of them (just a backup so we can revert :) ) now, change the other line to look like: /dev/cdrecorder /media/cdrecorder udf,iso9660 noauto,users,ro,exec save the file. From command prompt: mount /dev/cdrecorder (be sure you have disk in it :) )
If that's not possible, atleast where can I find some good and in-deapth documentation for subfs? What is it btw? :$
subfs is pretty good :). But sometimes it does not work well with some devices, or at least I had problems with it with my dvd recorder, so I needed to disable it. so, from now on, you have to manually mount/umount the drive. But at least it will show you if the problem was with subfs or with the drive itself. Cheers Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
Hi,
Thanks for that Sunny. Actually, I found the info on
SuSE portal about mounting devices yesterday, as soon
as I replied to your message!!
And sorry about that reply, I messed up with the
address field!!
Thanks very much though and I'll see if it's got
anything to do with subfs.
Cheers!
--- Sunny
On Saturday 11 December 2004 09:13, Mrugesh Karnik wrote:
Hi,
I'm a newbie, so could I have instructions on how to do this?
as root, first make: #umount /dev/cdrecorder
then open /etc/fstab file. There should be a line like: /dev/cdrecorder /media/cdrecorder subfs ....
Duplicate this line and put "#" in the beginning of one of them (just a backup so we can revert :) ) now, change the other line to look like:
/dev/cdrecorder /media/cdrecorder udf,iso9660 noauto,users,ro,exec
save the file. From command prompt: mount /dev/cdrecorder (be sure you have disk in it :) )
If that's not possible, atleast where can I find some good and in-deapth documentation for subfs? What is it btw? :$
subfs is pretty good :). But sometimes it does not work well with some devices, or at least I had problems with it with my dvd recorder, so I needed to disable it.
so, from now on, you have to manually mount/umount the drive. But at least it will show you if the problem was with subfs or with the drive itself.
Cheers Sunny
-- Get Firefox
http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. http://yahoo.shaadi.com/india-matrimony/
--- Sunny
On Saturday 11 December 2004 09:13, Mrugesh Karnik wrote:
Hi,
I'm a newbie, so could I have instructions on how to do this?
as root, first make: #umount /dev/cdrecorder
then open /etc/fstab file. There should be a line like: /dev/cdrecorder /media/cdrecorder subfs ....
Duplicate this line and put "#" in the beginning of one of them (just a backup so we can revert :) ) now, change the other line to look like:
/dev/cdrecorder /media/cdrecorder udf,iso9660 noauto,users,ro,exec
save the file. From command prompt: mount /dev/cdrecorder (be sure you have disk in it :) )
If that's not possible, atleast where can I find some good and in-deapth documentation for subfs? What is it btw? :$
subfs is pretty good :). But sometimes it does not work well with some devices, or at least I had problems with it with my dvd recorder, so I needed to disable it.
so, from now on, you have to manually mount/umount the drive. But at least it will show you if the problem was with subfs or with the drive itself.
Cheers Sunny
Hi again, As Sunny said, I disabled subfs. But here's another newbie question... How do I make K3B detect the drive? And do I have to unmount every time I want to change the cd? Here's what I've added to the fstab file: (It has mounted perfectly) /dev/hdc /media/cdrecorder udf,iso9660 noauto,users,ro,exec Thanks for the help :) Mrugesh ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. http://yahoo.shaadi.com/india-matrimony/
On Thu, 16 Dec 2004 15:50:42 +0000 (GMT), Mrugesh Karnik
As Sunny said, I disabled subfs. But here's another newbie question... How do I make K3B detect the drive?
k3b should detect the drive without problem. If it does not, there is something else wrong. Try from terminal, as root to issue: #cdrecord dev=ATA -scanbus this should list all ATAPI devices attached. Try this as regular user as well, to see if it is the same. If you see your device, the k3b should recognize it too. Actually k3b is only a very good frontend to various programs, incl. cdrecord.
And do I have to unmount every time I want to change the cd?
Thats the price you pay :). Try changing the option noauto to auto. That way you should be able to automount the cd when you click on its icon on desktop. I.e. it should mount the disk in the drive whenever you need to access the data on it. And it should unmount it after some period of inactivity. But if you need to change the disk right now :), the rightclick over the icon and select eject.
Here's what I've added to the fstab file: (It has mounted perfectly)
/dev/hdc /media/cdrecorder udf,iso9660 noauto,users,ro,exec
I've got a new DVD recorder. After installing it, the default settings in /etc/fstab have changed to: /dev/dvdrecorder /media/dvdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 and now it works as it should. So, maybe this was a device problem. You may try such an entry so see if it works. Cheers Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
k3b should detect the drive without problem. If it does not, there is something else wrong. Try from terminal, as root to issue: #cdrecord dev=ATA -scanbus
this should list all ATAPI devices attached. Try this as regular user as well, to see if it is the same. If you see your device, the k3b should recognize it too. Actually k3b is only a very good frontend to various programs, incl. cdrecord.
Here's the cdrecord output as a regular user ZY$�: Operation not permitted. WARNING: Cannot set RR-scheduler ZY$�: Permission denied. WARNING: Cannot set priority using setpriority(). ZY$�: WARNING: This causes a high risk for buffer underruns. Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 cdrecord: No such file or directory. Cannot open '/dev/hd*'. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. And here's the output as root: Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.80-resmgr-patch '@(#)scsi-linux-sg.c 1.80 04/03/08 Copyright 1997 J. Schilling'). scsibus1: 1,0,0 100) 'SAMSUNG ' 'CD-R/RW SW-252B ' 'R701' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * Now, K3B doesn't detect drive. I checked in YaST and it shows me the drive. I removed it as the Installation Source and added it again and it works fine. As I said, I've had this problem before. K3B just doesn't detect the drive even if I point it /dev/hdc And speaking of the drive having problems, it works perfectly in windows. Also, eject /dev/hdc worked fine!
Here's what I've added to the fstab file: (It has mounted perfectly)
/dev/hdc /media/cdrecorder udf,iso9660 noauto,users,ro,exec
I've got a new DVD recorder. After installing it, the default settings in /etc/fstab have changed to:
/dev/dvdrecorder /media/dvdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
and now it works as it should. So, maybe this was a device problem. You may try such an entry so see if it works.
Cheers Sunny
The previous line in fstab was this: /dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid ,nodev,exec,iocharset=utf8 0 0 and /dev/cdrom /media/cdrom subfs fs=cdfss,ro,procuid,nosuid ,nodev,exec,iocharset=utf8 0 0 Sometimes it used to mount both cdrecorder and cdrom even though I have only one drive! Both the locations would show the same contents of course! Thanks for the help again... Mrugesh ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. http://yahoo.shaadi.com/india-matrimony/
On Thu, 16 Dec 2004 16:42:38 +0000 (GMT), Mrugesh Karnik
k3b should detect the drive without problem. If it does not, there is something else wrong. Try from terminal, as root to issue: #cdrecord dev=ATA -scanbus
this should list all ATAPI devices attached. Try this as regular user as well, to see if it is the same. If you see your device, the k3b should recognize it too. Actually k3b is only a very good frontend to various programs, incl. cdrecord.
Here's the cdrecord output as a regular user
ZY$�: Operation not permitted. WARNING: Cannot set RR-scheduler ZY$�: Permission denied. WARNING: Cannot set priority using setpriority(). ZY$�: WARNING: This causes a high risk for buffer underruns. Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 cdrecord: No such file or directory. Cannot open '/dev/hd*'. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
And here's the output as root:
Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.80-resmgr-patch '@(#)scsi-linux-sg.c 1.80 04/03/08 Copyright 1997 J. Schilling'). scsibus1: 1,0,0 100) 'SAMSUNG ' 'CD-R/RW SW-252B ' 'R701' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) *
Now, K3B doesn't detect drive. I checked in YaST and it shows me the drive. I removed it as the Installation Source and added it again and it works fine.
So, this is permission problem. If as root the drive is detected, but not as regular user. I have some suggestions, but first respond with the k3b vershion info. From terminal, as regular user: $k3b -v
As I said, I've had this problem before. K3B just doesn't detect the drive even if I point it /dev/hdc
k3b uses cdrecord for drive detection, so if cdrecord fails, then k3b will fail as well.
The previous line in fstab was this:
/dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid ,nodev,exec,iocharset=utf8 0 0
and
/dev/cdrom /media/cdrom subfs fs=cdfss,ro,procuid,nosuid ,nodev,exec,iocharset=utf8 0 0
Sometimes it used to mount both cdrecorder and cdrom even though I have only one drive! Both the locations would show the same contents of course!
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
comment out the /cdrom line, you do not need 2 mount points. it can confuse the system. -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
k3b should detect the drive without problem. If it does not, there is something else wrong. Try from terminal, as root to issue: #cdrecord dev=ATA -scanbus
this should list all ATAPI devices attached. Try this as regular user as well, to see if it is the same. If you see your device, the k3b should recognize it too. Actually k3b is only a very good frontend to various programs, incl. cdrecord.
Here's the cdrecord output as a regular user
ZY$�: Operation not permitted. WARNING: Cannot set RR-scheduler ZY$�: Permission denied. WARNING: Cannot set priority using setpriority(). ZY$�: WARNING: This causes a high risk for buffer underruns. Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 cdrecord: No such file or directory. Cannot open '/dev/hd*'. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
And here's the output as root:
Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.80-resmgr-patch '@(#)scsi-linux-sg.c 1.80 04/03/08 Copyright 1997 J. Schilling'). scsibus1: 1,0,0 100) 'SAMSUNG ' 'CD-R/RW SW-252B ' 'R701' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) *
Now, K3B doesn't detect drive. I checked in YaST and it shows me the drive. I removed it as the Installation Source and added it again and it works fine.
So, this is permission problem. If as root the drive is detected, but not as regular user. I have some suggestions, but first respond with the k3b vershion info. From terminal, as regular user: $k3b -v
Here's the output: Qt: 3.3.1 KDE: 3.2.1 K3b: 0.11.7
As I said, I've had this problem before. K3B just doesn't detect the drive even if I point it
/dev/hdc
k3b uses cdrecord for drive detection, so if cdrecord fails, then k3b will fail as well.
The thing is, that the drive was detected perfectly till some days ago! Till before I sent out the first email, the drive was detected perfectly!!
The previous line in fstab was this:
/dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid ,nodev,exec,iocharset=utf8 0 0
and
/dev/cdrom /media/cdrom subfs fs=cdfss,ro,procuid,nosuid ,nodev,exec,iocharset=utf8 0 0
Sometimes it used to mount both cdrecorder and cdrom even though I have only one drive! Both the locations would show the same contents of course!
comment out the /cdrom line, you do not need 2 mount points. it can confuse the system.
I've already done that ;) ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. http://yahoo.shaadi.com/india-matrimony/
On Thu, 16 Dec 2004 17:10:02 +0000 (GMT), Mrugesh Karnik
k3b should detect the drive without problem. If it does not, there is something else wrong. Try from terminal, as root to issue: #cdrecord dev=ATA -scanbus
this should list all ATAPI devices attached. Try this as regular user as well, to see if it is the same. If you see your device, the k3b should recognize it too. Actually k3b is only a very good frontend to various programs, incl. cdrecord.
Here's the cdrecord output as a regular user
ZY$�: Operation not permitted. WARNING: Cannot set RR-scheduler ZY$�: Permission denied. WARNING: Cannot set priority using setpriority(). ZY$�: WARNING: This causes a high risk for buffer underruns. Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 cdrecord: No such file or directory. Cannot open '/dev/hd*'. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
And here's the output as root:
Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.80-resmgr-patch '@(#)scsi-linux-sg.c 1.80 04/03/08 Copyright 1997 J. Schilling'). scsibus1: 1,0,0 100) 'SAMSUNG ' 'CD-R/RW SW-252B ' 'R701' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) *
Now, K3B doesn't detect drive. I checked in YaST and it shows me the drive. I removed it as the Installation Source and added it again and it works fine.
So, this is permission problem. If as root the drive is detected, but not as regular user. I have some suggestions, but first respond with the k3b vershion info. From terminal, as regular user: $k3b -v
Here's the output:
Qt: 3.3.1 KDE: 3.2.1 K3b: 0.11.7
As I said, I've had this problem before. K3B just doesn't detect the drive even if I point it
/dev/hdc
k3b uses cdrecord for drive detection, so if cdrecord fails, then k3b will fail as well.
The thing is, that the drive was detected perfectly till some days ago! Till before I sent out the first email, the drive was detected perfectly!!
The previous line in fstab was this:
/dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid ,nodev,exec,iocharset=utf8 0 0
and
/dev/cdrom /media/cdrom subfs fs=cdfss,ro,procuid,nosuid ,nodev,exec,iocharset=utf8 0 0
Sometimes it used to mount both cdrecorder and cdrom even though I have only one drive! Both the locations would show the same contents of course!
comment out the /cdrom line, you do not need 2 mount points. it can confuse the system.
I've already done that ;)
Ok, 1. Add "users" option in the fstab line for the cdrecorder. This should make the device mountable (and unmountable) by all users. 2. See if you have k3bsetup. From terminal type: k3bsetup. If it is there, open yast go to user/group management and create a new group "burning". Then add all users you need to burn cds in that group. Now, note, I have no k3bsetup running here, and I have no graphical display exposted from home, so I write by memory, and some terms/field names, etc may be not exact, so follow the meaning :) 3. go back to k3bsetup. in the permissions, enable "use burning group". In the text field opened, type the name of the group as you created it. Hit Apply, or if there is Set permissions button, so that k3bsetup will set the neccessary permissions for the group and the programs. Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
Ok, 1. Add "users" option in the fstab line for the cdrecorder. This should make the device mountable (and unmountable) by all users.
2. See if you have k3bsetup. From terminal type: k3bsetup. If it is there, open yast go to user/group management and create a new group "burning". Then add all users you need to burn cds in that group.
Now, note, I have no k3bsetup running here, and I have no graphical display exposted from home, so I write by memory, and some terms/field names, etc may be not exact, so follow the meaning :)
3. go back to k3bsetup.
in the permissions, enable "use burning group". In the text field opened, type the name of the group as you created it. Hit Apply, or if there is Set permissions button, so that k3bsetup will set the neccessary permissions for the group and the programs.
Sunny
I'm compiling the latest version of K3B. Let's see. And there's no command like k3bsetup!! cdrecord -dev=ATA -scanbus doesn't work as non-root. What do I do about that? "users" is already in the fstab file ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. http://yahoo.shaadi.com/india-matrimony/
On Thursday 16 December 2004 13:14, Mrugesh Karnik wrote:
I'm compiling the latest version of K3B. Let's see. And there's no command like k3bsetup!!
cdrecord -dev=ATA -scanbus doesn't work as non-root. What do I do about that? "users" is already in the fstab file
You can access k3b Setup from the main k3b screen under Settings. Bob S.
Mrugesh Karnik wrote:
k3b should detect the drive without problem. If it does not, there is something else wrong. Try from terminal, as root to issue: #cdrecord dev=ATA -scanbus
this should list all ATAPI devices attached. Try this as regular user as well, to see if it is the same. If you see your device, the k3b should recognize it too. Actually k3b is only a very good frontend to various programs, incl. cdrecord.
Here's the cdrecord output as a regular user
ZY$�: Operation not permitted. WARNING: Cannot set RR-scheduler ZY$�: Permission denied. WARNING: Cannot set priority using setpriority(). ZY$�: WARNING: This causes a high risk for buffer underruns. Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 cdrecord: No such file or directory. Cannot open '/dev/hd*'. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
And here's the output as root:
Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.80-resmgr-patch '@(#)scsi-linux-sg.c 1.80 04/03/08 Copyright 1997 J. Schilling'). scsibus1: 1,0,0 100) 'SAMSUNG ' 'CD-R/RW SW-252B ' 'R701' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) *
Schilling has issues with the Linux kernel developers and the anti-SuSE propaganda is just another rant amounting to FUD. Since the kernel took the direction to move away from calling an IDE device a SCSI, he's been riled, though Linus wrote a workaround. Here's what I've done, in /boot/grub/menu.lst, I've altered hdb=ide-scsi to hdb=ide-cd and used xcdroast, putting that problem to bed, but I know many people are using k3b successfully, they're happy using k3b and I'm happy using xcdroast with the latest greatest cdrtools that Schilling writes - as Linus says, be happy!. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
participants (4)
-
B. Stia -
Mrugesh Karnik -
Sid Boyce -
Sunny