Bug 155986

Summary: mkinitrd should not source profiles
Product: [Fedora] Fedora Reporter: Charles P. Wright <cpwright>
Component: mkinitrdAssignee: Peter Jones <pjones>
Status: CLOSED INSUFFICIENT_DATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: mattdm
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-08 03:25:00 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:

Description Charles P. Wright 2005-04-26 13:49:09 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3

Description of problem:
Some user's profiles have cd aliased, and it produces special characters (e.g., to set an xterm title).  This confuses mkinitrd, and causes it to produce error messages saying that it can't find modules.  To avoid this problem, instead of using "#!/bin/bash" mkinitrd should use "#!/bin/sh" or "#!/bin/bash -norc".

Version-Release number of selected component (if applicable):
mkinitrd-4.1.18-2

How reproducible:
Always

Steps to Reproduce:
1. Use a cd replacement that sets an xterm title.
2. Run mkinitrd, no modules will be found.

Actual Results:  mkinitrd fails

Expected Results:  mkinitrd should make an initrd.

Additional info:
Comment 1 Matthew Miller 2006-07-10 23:13:37 UTC 
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!
Comment 2 petrosyan 2008-02-08 03:25:00 UTC 
Fedora Core 3 is not maintained anymore.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.