Bug 181873

Summary: mknod: Failed to create '/dev/ram0': already exists
Product: [Fedora] Fedora Reporter: Mark McLoughlin <markmc>
Component: mkinitrdAssignee: Peter Jones <pjones>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 5.0.29-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-27 16:20:24 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:
Attachments:
Description Flags
mkinitrd-fix-ramdisk-device-nodes.patch
none
mkinitrd-fix-find-command.patch
none
mkinitrd-fix-ramdisk-device-nodes.patch none

Description Mark McLoughlin 2006-02-17 12:24:41 UTC 
With mkinitrd CVS HEAD, I see the above warning (and for /dev/ram1 too)

What seems to be happening is that when you mount devpts, the ramdisk device
nodes (ram0 - ram15) automatically get created. I haven't been able to figure
out why ... :-)

Removing the two mknods seems to work fine

Patch also makes the /dev/ram link on the initramfs link to /dev/ram1 rather
than /dev/ram1 linking to non-existent /dev/ram
Comment 1 Mark McLoughlin 2006-02-17 12:24:41 UTC 
Created attachment 124808 [details]
mkinitrd-fix-ramdisk-device-nodes.patch
Comment 2 Mark McLoughlin 2006-02-17 12:29:53 UTC 
Created attachment 124810 [details]
mkinitrd-fix-find-command.patch

Fixed indentation
Comment 3 Mark McLoughlin 2006-02-17 12:30:57 UTC 
Created attachment 124811 [details]
mkinitrd-fix-ramdisk-device-nodes.patch

Bah, getting confused between bugs
Comment 4 Peter Jones 2006-02-27 16:20:24 UTC 
They get created by mkblkdevs.