On Monday, September 2, 2002, at 11:48 AM, Gerardo Alvarez Le=F3n wrote:

> I am still trying to install on a Powerbook 150 with a 4.3 Gb IDE =
drive.
> My last try has been with 20020825-1.6F snapshot.
>
> I keep getting the same error whenever I try to newfs the disk:
> uid 0 comm newfs on /:file system full
> /: write failed, file system is full
> (See my prior mail called "sysinst error: uid 0 comm newfs on /:file
> system full" for more info)

This is actually a Machine Independent error that has been reported on=20=

some of the other ports as well.  I'm not that familiar with the MI part=20=

of sysinst but I'll take a look at the problem.  I have a 1.6G snapshot=20=

that I built last nite.

> As Frederik suggested, I have added wd0b as swap (256 Mb), with the
> same result, so that must not be the problem, I guess.

I'm assuming you are having this problem while running an Installation=20=

Kernel and I though in that case the file system was all in RAM.  I'm=20
curious how much RAM you have on your system.

> Incidentally, I noted a bug in sysinst: In the Edit Disk Partition
> Map screen the columns title "size" and "start" are swapped, which
> can lead to errors. (Is this list the right place to report this bug?)

This I can fix and thanks for spotting it!

-bob