Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 121143

Summary: "Invalid argument" from initscripts
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: bmillett, cacruden, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 7.51-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1338716 (view as bug list) Environment:
Last Closed: 2004-05-03 21:18:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 114961    

Description Michal Jaegermann 2004-04-18 00:57:05 UTC 
Description of problem:

When booting with 'selinux=0' one sees this:

INIT: version 2.85 booting
cat: /proc/self/attr/current: Invalid argument

The culprit is that line:

if [ -n "$selinuxfs" -a  "`cat /proc/self/attr/current`" != "kernel"
]; then
.....

because 'test' is not short-circuiting '-a'.  Replacing the above
with

if [ -n "$selinuxfs" ] && \
   [ "`cat /proc/self/attr/current`" != "kernel" ]; then

will work as clearly intended.

Version-Release number of selected component (if applicable):
initscripts-7.50-1

How reproducible:
Always
Comment 1 Craig Cruden 2004-05-01 16:39:23 UTC 
Looks similar to another FC Blocker bug:

121663 [NEW - normal - notting] strange boot message when
rc.sysinit starts to run.
Comment 2 Bill Nottingham 2004-05-03 00:57:20 UTC 
*** Bug 121663 has been marked as a duplicate of this bug. ***
Comment 3 Bill Nottingham 2004-05-03 21:18:22 UTC 
Fixed, will be in 7.51-1, thanks!