[BusyBox] BusyBox 1.0.0-pre1 + nfs mount

[Andrew Dennison]

If the kernel hasn't changed then it looks like your nfs and rtc support is
compiled as modules and the modules haven't loaded. You may not even have
the rtc driver at all as the kernel reads the rtc directly on boot (at least
on i386). Also the full hwclock app can access the rtc directly or via the
kernel driver, while the busybox implementation only uses the rtc driver in
the kernel. Maybe your kernel should change:)

I can reproduce your hwclock issue as follows:

BusyBox v1.00-pre1 (2003.07.15-23:00+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# hwclock
Thu Jul 17 09:10:50 2003  0.000000 seconds
# modprobe -r rtc
# hwclock
hwclock: Could not access RTC: No such file or directory
#

nfs mounting works fine for me too. I use:
mount -t nfs -o nfsvers=2,intr,nolock 192.168.0.1:/home /home

Andrew

> -----Original Message-----
> From: busybox-bounces at busybox.net [mailto:busybox-bounces at busybox.net]On
> Behalf Of Frank R Callaghan
> Sent: Thursday, 17 July 2003 2:57 AM
> To: Vladimir N. Oleynik
> Cc: busybox at busybox.net
> Subject: Re: [BusyBox] BusyBox 1.0.0-pre1 + nfs mount
>
>
> On Wednesday 16 July 2003 12:44 pm, you wrote:
> > Frank,
> >
> > > # mount -t nfs  -o nolock 192.168.1.128:/home/rtlinux/myapp /myapp
> > > RPC: sendmsg returned error 22
> > > nfs: RPC call returned error 22
> > > nfs_get_root: getattr error = 22
> > > nfs_read_super: get root inode failed
> > > mount: Mounting 192.168.1.128:/home/rtlinux/myapp on /myapp failed:
> > > Invalid argument
> >
> > Hmm. Support your kernel RPC?
> >
>
> Yup, The kernel has not been changed, only busybox !
>
> CONFIG_NFS_FS=y
> CONFIG_NFS_V3=y
> # CONFIG_ROOT_NFS is not set
> CONFIG_NFSD=y
> CONFIG_NFSD_V3=y
>
>
>
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/mailman/listinfo/busybox
>