Always thank you very much!
I made netbsd using mdsetimage and ramdisk.fs, and "no file system on md0"
error was passed.
But next step, "mount" was failed.
/dev/md0 should be exist in ramdisk.fs, I guess...?

=================
.....
NetBSD 1.5ZA (RAMDISK) #0: Wed Mar  6 14:08:23 KST 2002

bgjung@bgjung15.etri.re.kr:/usr/user/bgjung/20020224/src/sys/arch/sandpoint/
compile/RAMDISK
total memory = 32768 KB
avail memory = 25404 KB
.....
md0: internal 2048 KB image area
boot device: <unknown>
root on md0a dumps on md0b
root file system type: ffs
erase ^H, werase ^W, kill ^U, intr ^C, status ^T
mount: cannot open `/dev/md0a': No such file or directory
Terminal type? [vt100]
.....
===============


----- Original Message -----
From: "Allen Briggs" <briggs@wasabisystems.com>
To: "Boo Geum Jung" <bgjung@etri.re.kr>
Cc: <port-sandpoint@netbsd.org>
Sent: Wednesday, March 06, 2002 10:21 AM
Subject: Re: netbsd RAMDISK failure of 20020224 tar_files


> On Wed, Mar 06, 2002 at 10:16:42AM +0900, Boo Geum Jung wrote:
> > I built NetBSD/sandpoint from 20020224 tar_files.
> > I donwloaded netbad on sys/arch/sandpoint/compile/RAMDISK directory as
just
> > below.
> > But it seems not to be working properly.
> > The following error message occurred - "no file system for md0 (dev
> > 0x1100)".
>
> You will still need to generate a filesystem image to include in your
> kernel.  The RAMDISK kernel configuration simply builds a kernel with
> space inside of it for a RAM disk image to be inserted.  There are tools
> for creating a ramdisk.fs in src/distrib/sandpoint.  The ramdisk.fs may
> be inserted with the mdsetimage (or
$TOOLDIR/bin/powerpc--netbsd-mdsetimage
> if you're cross-building) utility.
>
> Pax,
> -allen
>
> --
>  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...
>