On Fri, 13 May 2005 17:00:20 +0100 Ian disseminated the following:
On Friday 13 May 2005 16:36, Miark wrote:
On Fri, 13 May 2005 10:05:32 +0100, Margot wrote:
[a half-mile of useless quotes snipped--take a hint people]
One thing nobody seems to have mentioned so far - to burn successfully, you must use k3b as root, not as normal user.
If you open k3b as root - either use a root terminal to open k3b, or use the command kdesu k3b in a run command box and then give your root password - then you should have access to ALL files, no need to copy them to /home.
I've always understood that one should do as little as possible as root for security and whatever other reasons. Isn't this kind of a Bad Thing (tm) to make people su for such a common task?
Strange, I'm using K3B 0.11.20 here with cdrdao 1.1.9, cdrecord 2.1.1a01-dvd, dvd+rw-format4.10, growisofs 5.21, makeisofs 2.1 and haven't gone into root to burn anything.
Do:
uname -r
From what I've gleaned from Tom Brinkman's posts on this subject, it's a kernelissue, not the software you are using to burn. If you did an upgrade, and did not install the newer kernel, your kernel may still be the older patched version. MandrXXX, up to now, had patched the kernel to allow for burning apps to access kernel space directly, but no longer. Something to do with conforming to the LSB (IIANM), which personally I think is a dumb idea, but I'm no expert.
To address the previous posts, I don't see why a distro cannot allow for two versions of the kernel, one for people who are setting up their machine as a fully functional desktop box, another for those who are setting said box up as a server and are perhaps more paranoid about security. Anyhow, that's just my somewhat, possibly terribly, misinformed opinion.
Well hell Joe, you can't hog all the opinions, informed or not ;) Here's what I posted earlier on the OT list:
It's all CD's, audio, data, or iso's. BTW, I'm surprised this is news to y'all. Specially those that subscribe to the cooker ML. BUT, there's also been articles about it on Newsforge, /., the Inquirer an others. Months ago. AND it's not just cdrecord either, it's any app that needs to make kernel calls that affect security. It seems this is due to RSBAC and LSB compliance, and not really a distro decision.
[an addition to this reply; the kernel calls that are not allowed as user/cdrecord are (they do not appear as root):
.......
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.
.......
...and IME, it does. To the point of making a few coasters, even with burnfree. Others have reported even more severe problems. See bugzilla #15955 http://qa.mandriva.com/wiki ]
OTOH, it seems ridiculous when Mandriva an other desktop distros know damn well that the majority of their users are tainting their kernel an systems by using nVidia or ATI drivers, installing Flash, j2re and other proprietary bug attractors an security holes. 'Course I'm amused when the same people on the ML's that are so concerned with getting security updates for some obscure risk, turn right around in other threads an give advice about how to install proprietary drivers an apps.
FWIW, I did a LE2005 (6 CD) fresh install yesterday, and then re-upped it to cooker. I'm a little pissed that it installed the nVidia driver without asking. Now I've got to search for the instructions to completely remove it and use the nv driver. I've already installed a newer untainted kernel, the edit to xorg.conf is NBFD, but I vaguely remember I'll need to boot to lvl 3 and remove, then re-install all of the xorg packages in order to get back the xorg stuff (mostly GLX) that nVidia removes, an get rid of the crap that nVidia replaces it with.
~~~~~~~~~~~~~~~~~~~~~~~
More added on: CL users know that speed= parameters to cdrecord are just an option. cdrecord will try to use it as an upper limit, or may resort to lower speed as it determines, not you. Burning at very low speeds with newer kernels, will not avoid the high risk for buffer underruns. cdrecord already burns no faster than it believes it can, no matter what you tell it, an may stop altogether and need burnfree to make it. IME if burnfree is needed right at the end of a session, it's likely you'll have a coaster.
The only way to get permission to the RR-scheduler, setpriority kernel functions, an avoid buffer depletion.... is to burn as root. Since the recent kernel change, I've probly forgot to su an burned about 20 CD's as user. One was a coaster. OTOH, during the same period I've burned several hundred as root, full speed, burnfree never called, and no coasters.
IMO, the only problem is remberin to su to root ;)
--
Tom Brinkman Corpus Christi, Texas
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
