0.53.14 problems

[Adi Linden]

Hi,

It looks like your filesystem isn't extracted. Did you make sure to
convert binary rpms to packages first?

I am using 0.53.14 myself to build some wireless boxes and I haven't
encountered any such problems. I've changed the mount -a statement from
rc.init to rc.sysinit. However, that shouldn't make a difference and
doesn't affect the minimal system I use for testing. Especially, since the
mount -a statement didn't exist in the rc.init created by pwlconfig

Your error messages look like part of the filesystem tree is missing. Take
a look at the extracted filesystem tree at projects/<your project>/mnt and
see if projects/<your project>/mnt/lib/modules/2.2.17-full and
projects/<your project>/mnt/var/run exist...

TTYL,
Adi


On Mon, 13 Nov 2000, Dean Brown wrote:

> Adi,
> 	It seems that 0.53.14 is broken!! :^(
> 
> Taking a configuration that worked correctly under 0.53.10, and updating
> to 0.53.14 is causing bootup problems. Symptoms are as follows:
> 
> The error spew is:
> ----begin----
> /etc/rc.sysinit: cannot create /var/run/utmp: directory nonexistent
> INIT: Entering runlevel: 3
> Setting hostname
> Bringing up interface lo....
> modprobe: modprobe: Can't open dependencies file
> /lib/modules/2.2.17-full/modules.dep (No such file or directory)
> (the above line is repeated about 16 times)
> Bringing up interface eth0....
> Determining IP information for eth0....modprobe: modprobe: Can't open
> dependencies file /lib/modules/2.2.17-full/modules.dep (No such file or
> directory)
> dhcpd[49]: dhcpStart: ioctl SIOCGIFHWADDR: no such device
> 
> failed....
> touch: /var/lock/subsys/network: No such file or directory
> INIT: Id "1" respawning too fast: disabled for 5 minutes
> INIT: Id "2" respawning too fast: disabled for 5 minutes
> INIT: Id "3" respawning too fast: disabled for 5 minutes
> INIT: Id "4" respawning too fast: disabled for 5 minutes
> INIT: no more processes left in this runlevel
> ----end----
> 
> The problem is in the 'load filesystem' portion of pwl. If I Extract a
> filesystem using the 0.53.14 scripts and then load them onto the device
> with the 0.53.10 versions, the errors don't occur. Loading with the
> 0.53.14 scripts causes the errors regardless of how the extracted system
> was created.
> 
> 
> -- 
> Dean Brown
> ---------------------------------------------------
> See the list archives at http://adis.on.ca/archives/
> See the PWL homepage at  http://peeweelinux.com
> ---------------------------------------------------
> 

---------------------------------------------------
See the list archives at http://adis.on.ca/archives/
See the PWL homepage at  http://peeweelinux.com
---------------------------------------------------