Hi Volker,
On Tue, 17 Apr 2007 at 0:08 +0200, Volker Springer wrote:
> Hi Waldemar,
>
> thanks for the quick answer.
>
> > Hmm, very strange. Are you sure you haven't updated with a corrupt
> > image?
> >
> Pretty sure I did have a correct image. Will try to find the image on my host
> computer :-)
>
> > Just go into failsafe, mount_root && fwcf setup && chown 0:0
> > /bin/busybox && chmod u+s /bin/busybox && reboot
> >
> Hmm.. tried that: "mount_root" and "fwcf setup" naturally work ok,
> but chown returns "chown: /bin/busybox: No space left on device"
> Same message occurs when trying "touch /whattheheck".
> Also thought that this should work! Any ideas?
Oh, it seems your "data" partition, where the mini-fo overlay
filesystem puts his files on, is full. That is bad. FreeWRT has no
real warnings about to big images. Your data partition needs to be
at least 5 eraseblocks (64 kb or 128kb, depends on your hardware)
big. If it is smaller or if it is nearly full, strange things will
happen! Did you install a lot of software after flashing?
The preffered way to install new software on squashfs root images is
via "new" image. With jffs2 as root you can install via ipkg most of
the software.
> relevant mount points (I guess):
> /dev/mtdblock/5 on /rom/jffs type jffs2 (rw)
> /jffs on / type mini_fo (rw)
> /jffs on /tmp/.fwcf/root type mini_fo (rw)
> fwcf on /etc type tmpfs (rw)
>
> > Normally this happens if you flash a bad image, where the busybox is
> > not corrected. This should never happen with a 1.0 svn checkout or
> > release and I have never seen it in 1.0.
> >
> I have checked out the sources and I am about to start a new build.
> Will give it a try tomorrow.
Yeah, better update.
bye
Waldemar
_______________________________________________
freewrt-users mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-users