Bug 8563 - Bugs in nonroot mode/CD-Paranoia mode fixed
Summary: Bugs in nonroot mode/CD-Paranoia mode fixed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Powertools
Classification: Retired
Component: xcdroast
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ngo Than
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-01-18 11:21 UTC by till.kamppeter
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-02-11 10:38:07 UTC
Embargoed:


Attachments (Terms of Use)

Description till.kamppeter 2000-01-18 11:21:15 UTC
In the 'nonroot' mode of X-CD-Roast 0.96e the child processes called by
X-CD-Roast are running as the calling user and not as 'root'. So most
operations end up in 'Permission denied' (for example when one reads a CD
in 'Copy Data CD' one gets 'Permission denied' when 99% of the CD are
read). This problem appeared probably with the change von bash 1.x to bash
2.x (see 'man 3 system'). I developed the 'nonroot' mode under an old
Linux distribution (SuSE 5.x) and there the problem didn't appear. In
newer distributions (SuSE 6.x, Mandrake 6.1, RedHat 6.x) it appeared.

This problem I have addressed with a new version (0.96ex2) which one can
download the source tarball at

www.xcdroast.org

as

http://www.fh-muenchen.de/home/ze/rz/services/projects/xcdroast/src/xcdroast-0.96ex2.tar.gz

Note that the correct version is stored as xcdroast-0.96ex2.tar.gz.
xcdroast-0.96ex.tar.gz (without the '2' after 'ex') is an older version
which still has bugs.

Also all binary and '.rpm' packages still have bugs.

In this version I have also fixed the problem of the not working progress
bar when using CD-Paranoia. This should work with CD-Paranoia III Alpha
9.5 or newer. I tested with 9.7.

   Till Kamppeter

(author of the 'nonroot' mode of X-CD-Roast)

Comment 1 Ngo Than 2000-02-11 10:38:59 UTC
xcdroast-0.96ex2 is now in redhat-6.2


Note You need to log in before you can comment on or make changes to this bug.