[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uclibc
Subject:    [uClibc] Error: " No space left on device" with root_fs-i386.tar.bz2
From:       tom () ceisystems ! com (tom () ceisystems ! com)
Date:       2003-07-30 7:40:12
Message-ID: 6D31D5429FA6884CBE9ECAB6C9B5E6A907E0AB () intel-srvr ! patcameron ! ne ! mediaone ! net
[Download RAW message or body]

Michael,
	I find that mounting the image, doing a `cp -a` of everything
inside it to a directory, and then chrooting to the new directory works
much better.  The image file is not meant to be a development
environment for anything large, and thus will run out of space very
quickly.

Good luck,
Thomas Cameron
CEI Systems


-----Original Message-----
From: Michael Rowley [mailto:os2doc@bellsouth.net] 
Sent: Tuesday, July 29, 2003 10:40 PM
To: uclibc@uclibc.org
Subject: [uClibc] Error: " No space left on device" with
root_fs-i386.tar.bz2


Hey, 

Using the latest root_fs, but I am having some real problems.  I
apologize if this is stupid... :(

I mount the fs with mount -o loop root_fs-i386 /home/michael/root_fs

then chroot into it, 

copy source code for grub to it, but when I try to configure, I get the
above error about half way through the configure...  Am I missing
somthing?  I have tried it with different packages, but get the same
error.  I had assumed that the root_fs was virtual, so would expand with
demand.... yeah, I know what happens when you assume ;q  but df shows

/home/michael/root_fs-i386
                        149461     98581     50880  66%
/home/michael/root_fs

this is after ./configure  

Any advice?

Michael
os2doc@bellsouth.net

_______________________________________________
uClibc mailing list
uClibc@uclibc.org
http://uclibc.org/mailman/listinfo/uclibc

[prev in list] [next in list] [prev in thread] [next in thread]