Well, what you've made is an installation-kernel. Typing "s" will give
you a shell with a limited set of commands (those listed in
distrib/sandpoint/floppies/ramdisk/list).

If you want a full blown NetBSD system you will of course need to
include all the binaries, libs and other files in the ram-image which
means that the image will be very large (and if you're booting of a
flash it will probably not be big enough to hold that kernel).

Otherwise you will have to figure out what binaries, libs and other
files you need for your specific application and then make an image
containing those. This usually requires a bit of work to get it to work
correctly. (You have to figure out what libraries, config files etc.
that your binaries need to run). If your bootloader/monitor can
decompress (e.g. gzip or bzip2) an elf-image before booting it you
should be able to make a useful system that will fit in 2Mb.

If your application only requires a few processes you can replace
/sbin/init with your own that will only fork of those specific
processes. The binaries for those processes will have to be statically
linked or you will have to include the libs they need and
/usr/libexec/ld.elf_so.

If your sandpoint-system has a network interface you can instead use the
kernel option NFS_BOOT_BOOTP or NFS_BOOT_DHCP, see options (4), to have
the kernel mount the root filesystem from an NFS-fileserver. This works
very well and you will get a full blown NetBSD system.

/Erik



bgjung@etri.re.kr wrote:

> Thank you for your reply.
> I'm trying to make a "standalone" kernel.
> I used sys/arch/sandpoint/conf/RAMDISK and
> distrib/sandpoint/floppys/ramdisk/ramdisk.fs.
> But it didn't live "standalone".
> It just ask (I)nstall, (S)hell, (H)alt?
> So, I 'm wondering it needs to setup all tgz fles (base,tgz and
> etc.tgz), it almost 80M bytes, not 8M byte.
> What is missing on distrib/sandpoint?
> Or what I should add some lines on conf/RAMDISK?
> 2M is sufficient for "standalone" image?
>
>
> ¿øº» ³»¿ë:
>
> º¸³½»ç¶÷: Erik Anggard[erik.anggard@packetfront.com]
> ¹Þ´Â»ç¶÷: Boo Geum Jung
> ÂüÁ¶:port-sandpoint@netbsd.org
> Á¦¸ñ: Re: floppyinstfs size
> ¹ÞÀº³¯Â¥: 2002/03/17 ÀÏ 04:16
>
>
> Are you trying to make an installation floppy disk or just a
> "standalone" kernel? We use the following process to build "standalone"
> kernels:
> 1) configure and compile a kernel with options MEMORY_DISK_HOOKS,
> MEMORY_DISK_IS_ROOT and MINIROOTSIZE (and optionaly
> MEMORY_DISK_SERVER=0), see src/sys/arch/sandpoint/conf/RAMDISK
> 2) set up a directory to contain the files for the ramdisk and possibly
> an mtree-file and use makefs (8) to create an image-file of the
> directory (use "-s"-flag to set the size to the same as MINIROOTSIZE in
> step 1).
> 3) use mdsetimage (8) to copy the image-file into the kernel built in
> step 1
> /Erik
> Boo Geum Jung wrote:
> >2M seems to be insufficient to execute standalone on RAM, I don't
> know the
> >exact resean now.
> >So I'd like to extent the size of floppyinstfs from 2M to 8M.
> >What should I change?
> >Should I change disktab?
> >
> >floppyinstfs|NetBSD floppy install filesystem:\
> > :ty=floppy:se#512:nt#1:rm#300:ns#64:nc#64:\
> > :pa#4096:oa#0:ba#4096:fa#512:ta=4.2BSD:\
> > :pc#4096:oc#0: