[uClibc-cvs] [buildroot 0000371]: Fakeroot ext2 root some /dev entries are just files, erratic rootfs creation behaviour

bugs at busybox.net bugs at busybox.net
Mon Aug 8 19:38:54 UTC 2005


The following issue has been SUBMITTED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=371 
====================================================================== 
Reported By:                emalkowski
Assigned To:                uClibc
====================================================================== 
Project:                    buildroot
Issue ID:                   371
Category:                   Other
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             08-08-2005 12:38 PDT
Last Modified:              08-08-2005 12:38 PDT
====================================================================== 
Summary:                    Fakeroot ext2 root some /dev entries are just files,
erratic rootfs creation behaviour
Description: 
Using ext2root filesystem synced through 11060 this morning, my /dev/hda*
or /dev/hdb* inodes are showing up as regular files.  Sometimes both hda
and hdb entries are files, other times just hdb entries.

I can't tell if makedevs is broken or fakeroot is playing havoc here
(hosed $(STAGING_DIR)/fakeroot.env file?)

Also -- the recent change to makedevs.mk to add these lines seem bogus:

-$(STAGING_DIR)/fakeroot.env:
-       cat $(STAGING_DIR)/.fakeroot.* > $(STAGING_DIR)/fakeroot.env
-       touch -c $(STAGING_DIR)/fakeroot.env
-

w/o ltp testsuite configured, $(STAGING_DIR)/.fakeroot.* will NOT exist! 
but in my builds, cat of something that doesn't exist doesn't error out
the make and it seems to zero fakeroot.env which is what I was doing
before to get consistency when changing around my rootfs and rebuilding.

If I hack the top level makefile to delete fakeroot.env and also manually
purge my $(TARGET_DIR), I get my /dev/hda entries as devices and hdb as
files.  If I don't delete fakeroot.env and manually purge $(TARGET_DIR)
and rebuild, I get both /dev/hda and /dev/hdb entries as all files.

This is frustrating -- how can I debug this further?  I really can't tell
what's going on.

What I'd like to be able to do is simply this:

tweek something in my target/device/*/target_skeleton
rm -rf build_i386/root
make

An have the newly built build_i386/root be correct...  Shouldn't a purge
of $(STAGING_DIR)/fakeroot.env before doing the make above just make it
rebuild everything?

====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-08-05 12:38  emalkowski     New Issue                                    
08-08-05 12:38  emalkowski     Status                   new => assigned     
08-08-05 12:38  emalkowski     Assigned To               => uClibc          
======================================================================




More information about the uClibc-cvs mailing list