Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Still undecided...thinking of SUSE, Slackware, Kubuntu.
Posts: 25
Rep:
VERY annoying Floppy problem in Slackware... :-/ (fixed). Now CD-RW problems...
My dad wants to access his Floppy with some important files on it (files made on Winbloze - where he works they're still using that crap). So anyway, I mount the floppy for him, and everything goes smooth. The PC can read the Word files and opens them in OO.o. No problems so far. But when we try to save the changes to the file, Slackware spits out an error message. "General Input/Output Error". WTF?! I know the Matrix isn't real, but that's scary...
The only way we can save the file on the Floppy is to save it on the PC first, then copy that file back to the Floppy (we can't erase or overwrite the old file on the Floppy) as Root. Anyone know what the problem could be? Because I can't figure it out and I'm still a...
Distribution: Still undecided...thinking of SUSE, Slackware, Kubuntu.
Posts: 25
Original Poster
Rep:
Thanks Mara! That did the trick!
On a related note, Slackware detects my current CD-RW/DVD-ROM but I couldn't find a way to mount it. Someone suggested that I should type in Konsole:
# mkdir /mnt/hdd (create the mount point)
# mount /dev/hdd /mnt/hdd
So I did that, but now when I insert a blank CD-RW, it says:
"Error Kio_devices_mounthelper"
Code:
mount: block device /dev/hdd is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/hdd,
missing codepage or other error
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
In some cases useful info is found in syslog - try
dmesg | tail or so
Please check that the disk is entered correctly.
So I did that, but now when I insert a blank CD-RW, it says:
You can't mount blank media or audio CDs. To write to a CD, either use a GUI like K3B, or use the CLI 'cdrecord' or 'mkisofs' (K3B is just a front end for these anyway)
You can find a complete list of all available packages that come with Slackware in the PACKAGES.TXT file. You can also find a complete list of every file on a complete slackware system in the slackware/MANIFEST.bz2 file.
Distribution: Still undecided...thinking of SUSE, Slackware, Kubuntu.
Posts: 25
Original Poster
Rep:
Thanks, I've got them installed.
But now I've got another problem...
Code:
cdrecord does not run with root privileges
It is highly recommended to configure cdrecord to run with root privileges. Only then cdrecord runs with high priority which increases the overall stability of the burning process. Apart from that it allows changing the size of the used burning buffer. A lot of user problems could be solved this way. This is also true when using SuSE's resmgr.
Solution: Use K3bSetup to solve this problem.
cdrdao does not run with root privileges
It is highly recommended to configure cdrdao to run with root privileges to increase the overall stability of the burning process.
Solution: Use K3bSetup to solve this problem.
So I started the K3bSetup, but I don't know how to change the permission. This is what I get:
Since we're both running Slack 10.1, I feel it okay to share this bit of info with you. I checked out the permissions of the various devices in the previous screenshot you linked to. The cdrdao and cdrecord permissions were identical to mine. The devices, however, differed slightly. On my system (which I have only a CD-RW hanging off /dev/hdb) the permission were of the following:
/dev/hdb is owned by root.cdrom, not root.disk. Also, the permissions on /dev/hdb are rw / rw / none for owner / group / others. Your devices were marked 666 with means rw for everyone. If it were me, and the standard disclaimer applies here, I would try reassigning the owner of one of the drives to root:cdrom using the "chown" command (you'll have to be root to do this). If this fixes the problem, then change the other one as well. If it doesn't fix the problem (or it makes it worse), just change the owner back to root:disk.
Distribution: Still undecided...thinking of SUSE, Slackware, Kubuntu.
Posts: 25
Original Poster
Rep:
Hey Tino27,
Thank you sooo much for your help. I can finally burn CD's again! Woohoo! This O.S. is kick-ass!!!
All I had to do was login as root, go to Devices (in Konqueror) and right-click on the CD-RW icon. There I just set the permission so that "others" could read/write too. That's it! I'm a happy camper. Thanks again for your invaluable help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.