Hello,

I did it as per the link below and got a panic.
http://www.bsdnewsletter.com/2003/09/Features102.html

The distro seems to prepare a huge set of files,
whereas I want a minimal set to get a login prompt.
Can someone confirm if the article above is not
misleading?

Why does the system panic saying there is no init and
then stop in init? Do we need an /sbin/oinit and
/sbin/init.bak too in the crunch file?

Pasted below is info about the panic.
-------------------------------
root on md0a dumps on md0b
mountroot: trying ffs...
root file system type: ffs
cpu_lwp_fork: 0xc0732a1c 0xc2a4207c 0xc0732a1c
0xc0732a1c
l1->procaddr=0xc01ed000 l1->procaddr->u_pcb=0xc01ed000
pid=1 pmap=0xc07366c8
l2->procaddr=0xc2a46000 l2->procaddr->u_pcb=0xc2a46000
pid=0 pmap=0xc07366c8
cpu_lwp_fork: 0xc0732a1c 0xc2a420f8 0xc0732a1c
0xc0732a1c
l1->procaddr=0xc01ed000 l1->procaddr->u_pcb=0xc01ed000
pid=1 pmap=0xc07366c8
l2->procaddr=0xc2a48000 l2->procaddr->u_pcb=0xc2a48000
pid=0 pmap=0xc07366c8
cpu_lwp_fork: 0xc0732a1c 0xc2a42174 0xc0732a1c
0xc0732a1c
l1->procaddr=0xc01ed000 l1->procaddr->u_pcb=0xc01ed000
pid=1 pmap=0xc07366c8
l2->procaddr=0xc2a4a000 l2->procaddr->u_pcb=0xc2a4a000
pid=0 pmap=0xc07366c8
init: copying out flags `-s' 3
init: copying out path `/sbin/init' 11
exec /sbin/init: error 8
init: copying out flags `-s' 3
init: copying out path `/sbin/oinit' 12
exec /sbin/oinit: error 2
init: copying out flags `-s' 3
init: copying out path `/sbin/init.bak' 15
exec /sbin/init.bak: error 2
init: not found
panic: no init
Stopped in pid 1.1 (init) at    0xc02d884c:     bx    
 r14
db> trace
0xc02760bc
        scp=0xc02760bc rlv=0xc0241498 (0xc0241498)
        rsp=0xc2a39ed4 rfp=0xc2a39fb0
        r7=0xbfffffec r6=0x00000000
        r5=0xc03112bc r4=0xbfffffe8
0xc0241264
        scp=0xc0241264 rlv=0xc02e06a0 (0xc02e06a0)
        rsp=0xc2a39fb4 rfp=0x00000000
        r10=0x00000000 r9=0x00000000
        r8=0x00000000 r7=0x00000000 r6=0x00000000
r5=0xc2a42000
        r4=0xc0241258
----------------------------------------

thanks
-kamal

--- Allen Briggs <briggs@netbsd.org> wrote:

> On Mon, Jan 10, 2005 at 07:48:26AM -0800, Kamal R.
> Prasad wrote:
> >  Thanks for the help. The md pseudo-device was
> already
> > enabled when I reported the problem. I commented
> out
> > the MFS option and enabled the FFS_EI option. But
> the
> > end result is still the same. It looks like the
> ffs
> > module does not know how to create / on the
> ramdisk
> > (md0a) AND/OR expects a filesystem to be ready
> when it
> > accesses the device.
> 
> Umm..  Yes.  If you're doing 'root on md,' then you
> need
> to embed the root filesystem in the kernel image
> with
> mdsetimage (or equivalent).  Perhaps you've
> overlooked
> this step?
> 
> -allen
> 
> -- 
>                   Use NetBSD! 
> http://www.netbsd.org/
> 



		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com