Bug 1009596 - [kickstart] Cannot use process substitution even if interpreter set to bash
Summary: [kickstart] Cannot use process substitution even if interpreter set to bash
Keywords:
Status: CLOSED DUPLICATE of bug 814850
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-18 16:40 UTC by Jan Pokorný [poki]
Modified: 2013-09-18 18:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-18 18:38:49 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jan Pokorný [poki] 2013-09-18 16:40:20 UTC 
Cannot get kickstart file containing process substitution in %post
to work correctly.  Explicitly setting interpreter (--interpreter)
to /bin/bash won't help.

Either I am missing something or this is a bug.
Comment 3 Jan Pokorný [poki] 2013-09-18 18:11:02 UTC 
Found /tmp/ks-script-wauWIy (standalone %post section) and the respective
/tmp/ks-script-wauWIy.log states:

> cat: /dev/fd/63: No such file or directory
> cat: /dev/fd/62: No such file or directory
> tail: write error: Broken pipe

(where tail is one of the two commands used for process substitutions)

Looks like the chroot environment is not built properly incl. /dev
hierarchy (if possible, indeed, not a chroot expert), effectively
preventing process substitution?  If it's a known limitation, it doesn't
seem to be properly documented.  Definitely more desired would be to
prevent any such artificial and unobvious limitations
(process substitution is a standard feature of bash).
Comment 4 Jan Pokorný [poki] 2013-09-18 18:38:49 UTC 
Oh, [bug 814850].

*** This bug has been marked as a duplicate of bug 814850 ***
Note You need to log in before you can comment on or make changes to this bug.