[ Guys, please stop quoting the Korean characters.  Non-ASCII data
  causes the messages to bounce (as potential spam) and require approval
  from the moderator (me), which delays their delivery to the list...
  Thanks, -allen ]

Woo.  I hate to say it like this, but I hope you're wrong.
Linux fits (with a root filesystem) in 4MB of flash with a whole bunch
left over.

not that there is anywhere near 4MB on a Sandpoint, mind you.

Is there anything like JFFS/JFFS2 on NetBSD (yet)?  Or do I need to
hire Wasabi to write it?  :-)

jim

Erik Anggard writes:
> Well, what you've made is an installation-kernel. Typing "s" will giv=
e
> you a shell with a limited set of commands (those listed in
> distrib/sandpoint/floppies/ramdisk/list).
>=20
> 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).
>=20
> 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 wo=
rk
> 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.
>=20
> 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 staticall=
y
> linked or you will have to include the libs they need and
> /usr/libexec/ld.elf_so.
>=20
> 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 ha=
ve
> the kernel mount the root filesystem from an NFS-fileserver. This wor=
ks
> very well and you will get a full blown NetBSD system.
>=20
> /Erik
>=20
>=20
>=20
> bgjung@etri.re.kr wrote:
>=20
> > 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?
> >
> >
> > =BF=F8=BA=BB =B3=BB=BF=EB:
> >
> > =BA=B8=B3=BD=BB=E7=B6=F7: Erik Anggard[erik.anggard@packetfront.com=
]
> > =B9=DE=B4=C2=BB=E7=B6=F7: Boo Geum Jung
> > =C2=FC=C1=B6:port-sandpoint@netbsd.org
> > =C1=A6=B8=F1: Re: floppyinstfs size
> > =B9=DE=C0=BA=B3=AF=C2=A5: 2002/03/17 =C0=CF 04:16
> >
> >
> > Are you trying to make an installation floppy disk or just a
> > "standalone" kernel? We use the following process to build "standal=
one"
> > kernels:
> > 1) configure and compile a kernel with options MEMORY_DISK_HOOKS,
> > MEMORY_DISK_IS_ROOT and MINIROOTSIZE (and optionaly
> > MEMORY_DISK_SERVER=3D0), see src/sys/arch/sandpoint/conf/RAMDISK
> > 2) set up a directory to contain the files for the ramdisk and poss=
ibly
> > 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 MINIROOTSIZ=
E 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=3Dfloppy:se#512:nt#1:rm#300:ns#64:nc#64:\
> > > :pa#4096:oa#0:ba#4096:fa#512:ta=3D4.2BSD:\
> > > :pc#4096:oc#0:

--=20
"The Tivo is a wrapper around a bad interface" -- Bruce Sterling



----- End forwarded message -----

-- 
 Allen Briggs                     briggs@wasabisystems.com
 http://www.wasabisystems.com/    Quality NetBSD CDs, Sales, Support, Service
NetBSD development for Alpha, ARM, M68K, MIPS, PowerPC, SuperH, XScale, etc...