Problem solved. Thank you *very* much to all who replied: Denys, Matthew, Yann, and Roland!
I was simply looking in the wrong place for my solution: once I knew that I had to load the nfs.ko module, it was just a matter of sorting out the dependencies. - Ken PS: Just FYI, what I'm doing is adapting a cloning process - via mkCDrec - that has been used here for distributing software. Instead of having the image disk spinning in a local drive, the machine to be imaged is grabbing the files over the network. -----Original Message----- From: Denys Vlasenko [mailto:[email protected]] Sent: Sunday, May 24, 2009 5:53 PM To: [email protected] Cc: Shelby, Ken (SEN US EXT) Subject: Re: NFS mount problem On Friday 22 May 2009 23:11, Shelby, Ken (SEN US EXT) wrote: > I need some help mounting an NFS file system on a Busybox 1.13.4 > machine. > > This is the error message: > > mount: 10.2.106.25:/export has wrong device number or fs type > nfs not supported > > This is the mount command that I gave Busybox: > > mount -t nfs -o ro 10.2.106.25:/export /mnt > > The file system is exported as "read-only" to the world from a Red Hat > 4.6 NFS server. The Busybox NFS client machine is running on an > "initrd.gz" that the machine successfully grabbed off my network via > pxelinux and tftp. Busybox has successfully run "insmod" to put the NIC > driver (e1000.ko) in the kernel, and Busybox can both ping and telnet to > the Red Hat NFS server. No idea yet. Does mount from util-linux work with the same command line? -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
