On Sun, May 15, 2005 at 05:52:54PM +0200, platanthera wrote:
On Saturday 14 May 2005 23:30, Ross Adams Lippert wrote:
I'm sorry I was not more specific.
/var has 256MB
/tmp has 256
/ has 256
/usr has 4500MB
newfs had been run on everything.
ftp was passive.
Since base is
On Saturday 14 May 2005 23:30, Ross Adams Lippert wrote:
I'm sorry I was not more specific.
/var has 256MB
/tmp has 256
/ has 256
/usr has 4500MB
newfs had been run on everything.
ftp was passive.
Since base is about 46MB of material, it seems it could put it
anywhere.
This occurs 3%
It was extracting the distribution into / over ftp and said
/: write failed, filesystem is full
this was after doing a newfs on /. Has anyone run into this problem?
I am not subscribed. If I should be tell me. If not, put me
in the cc-line.
-r
On Sat, May 14, 2005 at 12:54:53PM -0400, Ross Adams Lippert wrote:
It was extracting the distribution into / over ftp and said
/: write failed, filesystem is full
this was after doing a newfs on /. Has anyone run into this problem?
Only when I made / too small.
Kris
pgpkWFG7WRMo8.pgp
It was extracting the distribution into / over ftp and said
/: write failed, filesystem is full
this was after doing a newfs on /. Has anyone run into this problem?
You are going to have to give more information.
What do your file systems look like?
Sure I have had that happen when
I'm sorry I was not more specific.
/var has 256MB
/tmp has 256
/ has 256
/usr has 4500MB
newfs had been run on everything.
ftp was passive.
Since base is about 46MB of material, it seems it could put it anywhere.
This occurs 3% of the way into the extration of base into / via
ftp. I did burn
