Hey Mitul,

I'm still fighting to get a correct Nfs moun= ted root filesystem. So correct me if I'm wrong when I did the following :< BR>

--> I exported my newly built embedded (hardly,....its 20 M= B in size) rootfs from my host machine.

--> = This is thus my NFS server. I started portmap, nfs and mfslock services.

--> On my so called target ( I'm just using another i686 PC f= or trial purposes, before porting it on the actual machine), I started the = same services.

--> I have only a kernel on my client/target system= with NFS, Network block Devices and TCP netwroking options enabled.

= --> I'm still using Grub (for obvious reasons) and the entry is as follo= ws :

Title NFS-rootfs

root (hd0,4)

= kernel /bzImage-2.4.20 rw root=/dev/nfs

= ; nfsroot=<nfs-server-address>:<path-to-rootfs-on-server>

ip=<client ip>:<server ip>:<gateway ip&= gt;:<subnet mask>::eth0:off

Thats it !!!

See anything wrong?

Raseel.

&g= t;Its a bad idea as you can see, you need to hardcode this into the kernel = source

code for the command line (unless you have good boot loade= r,

grub is one, but i

didnt have success in putting up Grub, the = stages file size are

too big for

embedded systems ), and somethin= g that is hardcoded is certainly

not good.

But yes it = is a good idea if you have thin clients and that you

know the IP of

&= gt;NFS Server and the path is never going to change. Choice is yours :) =

[1] [ad=]

References

1. 3D"http://clients.rediff.=/