Hi,
My tentative to build a complete release failed with the following error.
Any idea?
SNIP
PAX=/usr/tools/bin/nbpax sh / -i
"/usr/tools/bin/nbinstallboot -mi386 @IMAGE@
/" -p -m 2 -s .fs boot 2880
boot netbsd
Running instboot: /usr/tools/bin/nbinstallboot -mi386 floppy.25252.tar
/
Free space in last tar block: boot 188, netbsd 315,
buildfloppies.sh: Image is 3387 bytes (3 KB) too big to fit on 2 disks
Failed target: boot1.fs
Failed command: PAX=/usr/tools/bin/nbpax sh
/ -i "/usr/tools/bin/nbinstallboot
-mi386 @IMAGE@ /" -p -m 2 -s .fs
boot 2880 boot netbsd
Error code 1
Stop.
nbmake: stopped in /
Failed target: all-bootfloppy
Failed command: _makedirtarget() { dir="$1"; shift; target="$1"; shift;
case "${dir}" in /*) this="${dir}/"; real="${dir}" ;; .)
this="etc/i386/floppies/"; real="/usr/src/distrib/i386/floppies" ;; *)
this="etc/i386/floppies/${dir}/";
real="/usr/src/distrib/i386/floppies/${dir}" ;; esac; show=${this:-.}; echo
"${target} ${show%/}${1:+ (with: $@)}"; cd "${real}" &&
/usr/tools/bin/nbmake _THISDIR_="${this}" "$@" ${target}; }; _makedirtarget
bootfloppy all
Error code 1
Stop.
nbmake: stopped in /usr/src/distrib/i386/floppies
Failed target: all-floppies
Failed command: _makedirtarget() { dir="$1"; shift; target="$1"; shift;
case "${dir}" in /*) this="${dir}/"; real="${dir}" ;; .) this="etc/i386/";
real="/usr/src/distrib/i386" ;; *) this="etc/i386/${dir}/";
real="/usr/src/distrib/i386/${dir}" ;; esac; show=${this:-.}; echo
"${target} ${show%/}${1:+ (with: $@)}"; cd "${real}" &&
/usr/tools/bin/nbmake _THISDIR_="${this}" "$@" ${target}; }; _makedirtarget
floppies all
Error code 1
SNIP
Konstantin K. KABASSANV
LIP6/CNRS
8, rue du Capitaine Scott
75015 Paris, France
Phone: +33 (0) 1 44 27 71 26
Fax: +33 (0) 1 44 27 74 95
E-mail: konstantin (AT) kabassanov (DOT) com
Web: http://www.kabassanov.com
IMPRTANT! If you have tried to reply to this mail and you received a
stupid message, announcing that the mail had been rejected as spam,
please, resend your reply to the address above.
The certificate used to sign this e-mail can be verified at:
Mediocrity is the worst kind of failure

Mon, 8 May 2006, Garrett D'Amore wrote:

Frederick Bruckman wrote:
>>
>I propose removing "bad144" from the i386 installation media.
>>
>I find that "bootfloppy" and "bootfloppy-com" *just* *fit* into
>2880 KB with 0K padding, after commenting out "bad144" from
>"ramdisk-big/list". Does anyone have a better idea? Would anyone
>really miss "bad144"? Is that even enough, or will it just fill
>up again in a day or two?
>
>
Hmm it strikes me that we are fighting a never ending battle with the
1.44 media. Maybe its time to rethink this?

Sure, every time this happens

The floppies, as such, aren't really the issue, since we could just
make three, or five

Don't like ~99% just use network or CDRMs as the way they install now?
Is it worth spending a huge amount of effort to try to make things
slightly easier for that last 1%?

The CDRMs -- likely the most popular install media -- are the
problem. The El Torrito emulation section must be no more than
2880kb, and that's what's overfilling now (ramdisk-big).

It's been suggested that we forego the emulation, but older BIS's
likely won't be able to deal with that. I think the idea was to have
a small El Torrito section with just a bootloader, to load a kernel
out of the IS image. Does the current bootloader support that?
(Don't answer that. I just built a current CDRM -- I'll try to load
one of the compressed kernels right now.)

Frederick

In article <000e01c671b0$3bf347e0$0100a8c0@gargamel>,
"Konstantin KABASSANV" <Konstantin.Kabassanov (AT) lip6 (DOT) frwrites:

PAX=/usr/tools/bin/nbpax sh / -i
"/usr/tools/bin/nbinstallboot -mi386 @IMAGE@
/" -p -m 2 -s .fs boot 2880
boot netbsd
Running instboot: /usr/tools/bin/nbinstallboot -mi386 floppy.25252.tar
/
Free space in last tar block: boot 188, netbsd 315,
buildfloppies.sh: Image is 3387 bytes (3 KB) too big to fit on 2 disks

Failed target: boot1.fs
Failed command: PAX=/usr/tools/bin/nbpax sh
/ -i "/usr/tools/bin/nbinstallboot
-mi386 @IMAGE@ /" -p -m 2 -s .fs
boot 2880 boot netbsd
Error code 1

Stop.
nbmake: stopped in /

"Me too."

I propose removing "bad144" from the i386 installation media.

I find that "bootfloppy" and "bootfloppy-com" *just* *fit* into
2880 KB with 0K padding, after commenting out "bad144" from
"ramdisk-big/list". Does anyone have a better idea? Would anyone
really miss "bad144"? Is that even enough, or will it just fill
up again in a day or two?

Frederick

Mon, 8 May 2006, Frederick Bruckman wrote:

The CDRMs -- likely the most popular install media -- are the problem. The
El Torrito emulation section must be no more than 2880kb, and that's what's
overfilling now (ramdisk-big).

It's been suggested that we forego the emulation, but older BIS's likely
won't be able to deal with that. I think the idea was to have a small El
Torrito section with just a bootloader, to load a kernel out of the IS
image. Does the current bootloader support that? (Don't answer that. I just
built a current CDRM -- I'll try to load one of the compressed kernels right
now.)

So close. "dev" and "ls" seem to be broken, by the way. "boot
" actually spins the CDRM
(as does cd0d:), but says "No file found". Was that supposed to
work?

It occurs to me that anyone who wants to work on this might need to
actually build a release, so again, what to toss out? IM, "bad144"
stands out as the most useless thing on the list, and "bootfloppy" and
"bootfloppy-com" just fit without it, but it's not big enough to buy
us much time before this happens again.

Frederick

Mon, 8 May 2006, Frederick Bruckman wrote:
So close. "dev" and "ls" seem to be broken, by the way. "boot
" actually spins the CDRM (as does
cd0d:), but says "No file found". Was that supposed to work?

No, and it was brought up before.
Someone even posted a patch, but I didn't get it to work.
Feel free to dig the archives and work on that, I'd appreciate it!

It occurs to me that anyone who wants to work on this might need to actually
build a release, so again, what to toss out? IM, "bad144" stands out as the
most useless thing on the list, and "bootfloppy" and "bootfloppy-com" just
fit without it, but it's not big enough to buy us much time before this
happens again.

See my reply to Garrett's mail.

- Hubert

Tue, 9 May 2006, Frederick Bruckman wrote:
It sounds like a good plan, but it doesn't sound like it'll be
ready this week. What'll we do about the broken "make release", in
the meantime?

My changes won't touch that anyways.

Possible fixes are
* remove e.g. bad144
* go to three floppies for bootfloppy and bootfloppy-com
* ?

Someone decide, I don't care.

- Hubert

Mon, 8 May 2006, Garrett D'Amore wrote:

Hubert Feyrer wrote:
>Tue, 9 May 2006, Frederick Bruckman wrote:
It sounds like a good plan, but it doesn't sound like it'll be
ready this week. What'll we do about the broken "make release", in
the meantime?
>>
>My changes won't touch that anyways.
>>
>Possible fixes are
>* remove e.g. bad144
>* go to three floppies for bootfloppy and bootfloppy-com

"bootfloppy" is the El Torrito image, so that's currently not an
option.

>* ?
>>
>Someone decide, I don't care.

Sorry if my ignorance of the install process is showing. But would
going to three floppies create a new situation where systems with small
memories (think 4MB) cannot function?

I've got NetBSD running in 8MB, and I can tell you, it isn't much fun.
Losing even more space to an MD is likely to make 4MB systems (even
more) unusable.

do we just not care about systems with memories less than X (FSV X)?

course we care. You should be using bootfloppy-small (two 1.2MB
floppies) or even bootfloppy-tiny (one) -- that's what they're for.
(Can you really run NetBSD in 4MB?)

Frederick

Mon, 8 May 2006, Garrett D'Amore wrote:
Sorry if my ignorance of the install process is showing. But would
going to three floppies create a new situation where systems with small
memories (think 4MB) cannot function?

I've got NetBSD running in 8MB, and I can tell you, it isn't much fun.
Losing even more space to an MD is likely to make 4MB systems (even
more) unusable.

Well, just because you split something on 3 floppies instead of 2 sure
won't make it smaller. So either take out some drivers, take something
from the ramdisk, or have it grow.

do we just not care about systems with memories less than X (FSV X)?

I think we should.

You can use Qemu to see what's the minimum amount of RAM needed to run
stripped down kernels (GENERIC/INSTALL_SMALL/TINY).

- Hubert

I have removed bad144 from the bootfloppy-{big,small} images; the floppies
now successfully build.
Flame on!

May 8, 2006, at 5:56 PM, Frederick Bruckman wrote:

The CDRMs -- likely the most popular install media -- are the
problem. The El Torrito emulation section must be no more than
2880kb, and that's what's overfilling now (ramdisk-big).

What about hard drive emulation that El Torrito also supports?
-- thorpej

Mon, 8 May 2006, Jason Thorpe wrote:

May 8, 2006, at 5:56 PM, Frederick Bruckman wrote:
>
>The CDRMs -- likely the most popular install media -- are the problem. The
>El Torrito emulation section must be no more than 2880kb, and that's what's
>overfilling now (ramdisk-big).
>
What about hard drive emulation that El Torrito also supports?

Whoo Hoo! It works! I made an 11MB ffs image, did "fdisk" (no
disklabel), did "installboot", copied in "/boot" and "/netbsd.gz", and
installed it into the CDRM the usual way, adding "-hard-disk-boot" to
${MKISFSPTIN}. "ls" from the bootloader works, and "boot
hd0e:netbsd.gz" boots into the installer.

I used a "vnd". I'll have to look at how to do it the new way.

Seems like the way to go?

Frederick

Frederick,

Tue, 9 May 2006, Frederick Bruckman wrote:
Seems like the way to go?

not to spoil your enthusiasm,
but may I please ask you to have a look at the proposal that I've sent
out, and comment on that? It has been up for some time, and re-doing all
this from the start seems counterproductive to me.

- Hubert

Tue, 9 May 2006, Hubert Feyrer wrote:
>Seems like the way to go?
>
not to spoil your enthusiasm,
but may I please ask you to have a look at the proposal that I've sent out,
and comment on that? It has been up for some time, and re-doing all this from
the start seems counterproductive to me.

, and using our shiny new makefs -t cd9660 would also be very nice
instead of a mkisofs that we don't have in-tree.

- Hubert

Mon, 8 May 2006, Frederick Bruckman wrote:
Possible fixes are
* remove e.g. bad144
* go to three floppies for bootfloppy and bootfloppy-com

"bootfloppy" is the El Torrito image, so that's currently not an option.

Wrong.
bootfloppy are two 1.44MB floppy images. bootfloppy-big is a 2.88MB floppy
image which can be turned into a IS image that uses floppy emulation.

- Hubert

Tue, May 09, 2006 at 06:27:07PM +0100, David Laight wrote:
very useful feature of the current 'kernel+ramdisk' is that you can
pxeboot (or equiv.) the install kernel, then continue the install
using ftp (etc) to load the sets.

I don't think that requiring the 'root' filesystem come from another
device gives anything like the same flexibility. Indeed I suspect
it would require extra kernels (etc) to be built over and above the
'too many' that are built today.

Do you think it would work to netboot a kernel and then use NFS root?

the other hand, I once did an install on an old laptop with only a
floppy and a serial port. It is nice to have slattach and a shell on
hand.

Ben