It would appear that on May 15, Michael Schwendt did say: > On Fri, 14 May 2004 11:11:32 -0400 (EDT), Joe(theWordy)Philbrook wrote: > > > > I myself find xcdroast works pretty good. (and actually seams to be > > getting better) I tried kb3 once on my mandrake 9.1 and it insisted on > > reconfiguring some permission settings (which messed with xcdroast) > > It does not do that. k3b recommends raising the privileges on a few helper > tools (such as cdrecord, cdrdao) with k3bsetup. The warning when these > tools are not setuid root, can be disabled, so it is not shown again. Perhaps it was an old version... The version of xcdroast that I got for mandrake permitted root to select if non root could burn... if I attempted to run the version of k3b it did not succeed in burning with my hardware. Most attempts did lock up my pc. And every time I loaded it, whether I tried to burn one or not, the next time I wanted xcdroast I had to re-enable the user settings... Thinking about it, I think there was an opportunity to avoid raising those privileges when it displayed the "Warning" you speak of. But I don't believe it explained that the reason why it wanted to make those changes was only to upgrade security, or that it was capable of functioning without making the changes... And certainly letting it have it's way did mess with xcdroast's user burn set-up... To be fair, until I found out when to tell xcdroast to use raw mode and when not to, more than a few attempts to burn with it also locked up my pc. Though once I learned it I was able to burn with great success. And I was not able to find a corresponding success with k3b with my hardware using mandrake. -- | --- ___ | <0> <-> Joe (theWordy) Philbrook | ^ J(tWdy)P | ~\___/~ <<jtwdyp@xxxxxxxx>> But if I actually knew everything, then I'd know I was an idiot...
