Bug 62199

Summary: /sbin/bin ->bin link created instead of /sbin ->bin
Product: [Retired] Red Hat Public Beta Reporter: Miloslav Trmac <mitr>
Component: mkinitrdAssignee: Matt Wilson <msw>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: low Docs Contact:
Priority: medium    
Version: skipjack-beta1   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-04-05 03:45:25 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: 61590    
Attachments:
Description Flags
Suggested patch none

Description Miloslav Trmac 2002-03-28 11:47:54 UTC 
Description of problem:
In the initrd, a /sbin directory is created and then ln -s bin .../sbin
is executed, which creates a /sbin/bin symlink. I think the intent was to create
a symlink /sbin ->bin.

Version-Release number of selected component (if applicable):
mkinitrd-3.3.6-1

Additional info:
Unrelated issue, just a bit strange: when I gunzip the mkinitrd in 7.2 with
kernel 2.4.9-21, I can see contents of my /etc/group in it. However, the file is
not there when I loop mount the initrd. When I ran mkinitrd again, the
/etc/group file was there again. I haven't been able to find how the file gets
in there (the only place the mkinitrd gets written to is the tar cf - . | tar xf
-, and strac'ing
tar showed nothing). Unless you find this interesting (or security problem?),
forget about it.
Comment 1 Miloslav Trmac 2002-03-28 11:48:20 UTC 
Created attachment 51127 [details]
Suggested patch
Comment 2 Jeremy Katz 2002-04-05 03:45:21 UTC 
Fixed in mkinitrd-3.3.7-1 and newer
Comment 3 Jay Turner 2002-04-09 00:48:00 UTC 
Fix confirmed with 3.3.8-1.