Problems setting up a small LAN
Problems setting up a small LAN
I have looked around for a while now, but could not find a solution.
So I hope someone can help me.
ping 127.0.0.1 works fine, but
sh-3.00# ping localhost
PING localhost (7f00:1:70b7:e4bf::): 56 data bytes
ping: can't create raw socket: Address family not supported by protocol
sh-3.00#
Same problem for other names (for a LAN) in '/etc/hosts'. Seems a bit confused with IPV6 ?
Also when trying to mount a NFS share :
sh-3.00# mount -t nfs 192.168.0.11:/FILES /mnt/FILES
mount: mounting 192.168.0.11:/FILES on /mnt/FILES failed
or
sh-3.00# mount-FULL -t nfs 192.168.0.11:/FILES /mnt/FILES
mount: unknown filesystem type 'nfs'
I'm not really successful. Thanks for any help.
So I hope someone can help me.
ping 127.0.0.1 works fine, but
sh-3.00# ping localhost
PING localhost (7f00:1:70b7:e4bf::): 56 data bytes
ping: can't create raw socket: Address family not supported by protocol
sh-3.00#
Same problem for other names (for a LAN) in '/etc/hosts'. Seems a bit confused with IPV6 ?
Also when trying to mount a NFS share :
sh-3.00# mount -t nfs 192.168.0.11:/FILES /mnt/FILES
mount: mounting 192.168.0.11:/FILES on /mnt/FILES failed
or
sh-3.00# mount-FULL -t nfs 192.168.0.11:/FILES /mnt/FILES
mount: unknown filesystem type 'nfs'
I'm not really successful. Thanks for any help.
First. YOU FOUND A BUG!!!

Report it as a "bug" and not as a problem.
Please indicate what version of puppy (or pupplet) you are using.
If you are using a pupplet avise the pupplet author, If you are using an "official" puppy, then please indicate what puppy version.
I can certainly recreate the problem in wNOP. I haven't tried the Official puppy.
Second. Regarding NFS.
I suspect you are using a pupplet that does not have NFS. Contact the pupplet author

Report it as a "bug" and not as a problem.
Please indicate what version of puppy (or pupplet) you are using.
If you are using a pupplet avise the pupplet author, If you are using an "official" puppy, then please indicate what puppy version.
I can certainly recreate the problem in wNOP. I haven't tried the Official puppy.
Second. Regarding NFS.
I suspect you are using a pupplet that does not have NFS. Contact the pupplet author
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
Puppy Version
In fact I started using 'zebuntu-mini' puplet, but also got same results
for the official Puppy v3.0.1.
Is there a different procedure for bugs ?
Thanks.
for the official Puppy v3.0.1.
Is there a different procedure for bugs ?
Thanks.
Is there a localhost alias at the top of /etc/hosts?
Are you able to load the nfs module? modprobe nfs
dreamstogo posted an explanation of how she mounted an nfs share using teenpup
Are you able to load the nfs module? modprobe nfs
dreamstogo posted an explanation of how she mounted an nfs share using teenpup
hosts file
1) my '/etc/hosts' is :
127.0.0.1 localhost puppypc klbos
192.168.0.11 klbf.klb.net klbf
192.168.0.1 klbx.klb.net klbx
2) loading nfs module failes :
{~] modprobe nfs
FATAL: Error inserting nfs (/lib/modules/2.6.21.7/kernel/fs/nfs/nfs.ko): Unknown symbol in module, or unknown parameter (see dmesg)
and rhere are many messages in '/var/log/messages/ like :
Apr 10 07:39:50 (none) kern.warn kernel: nfs: Unknown symbol nlmclnt_proc
Apr 10 07:39:50 (none) kern.warn kernel: nfs: Unknown symbol rpc_proc_register
Seems I am missing other module(s), but which ?
127.0.0.1 localhost puppypc klbos
192.168.0.11 klbf.klb.net klbf
192.168.0.1 klbx.klb.net klbx
2) loading nfs module failes :
{~] modprobe nfs
FATAL: Error inserting nfs (/lib/modules/2.6.21.7/kernel/fs/nfs/nfs.ko): Unknown symbol in module, or unknown parameter (see dmesg)
and rhere are many messages in '/var/log/messages/ like :
Apr 10 07:39:50 (none) kern.warn kernel: nfs: Unknown symbol nlmclnt_proc
Apr 10 07:39:50 (none) kern.warn kernel: nfs: Unknown symbol rpc_proc_register
Seems I am missing other module(s), but which ?
My Summary
Thanks for your replies.
ping localhost was just an example. I cannot use any
name from /etc/hosts in any program (ftp, browser, ... ).
Current workaround for commandlines is to define symbols :
(not really a solution).
It is ok for me, when Puppy does not support NFS at all. Its an ancient,
complex concept based on RPC. Time now to switch to Samba.
ping localhost was just an example. I cannot use any
name from /etc/hosts in any program (ftp, browser, ... ).
Current workaround for commandlines is to define symbols :
Code: Select all
export PCNAME=192.168.0.x ; ping $PCNAME
It is ok for me, when Puppy does not support NFS at all. Its an ancient,
complex concept based on RPC. Time now to switch to Samba.
unable to modprobe module nfs
And I am having exactly the same problem, too, using Pupeee for Asus Eeepc... This was the only thread I could find that contained this problem. Surely, though, some users are successfully using nfs file sharing?Soupbean wrote:i'm having exactly the same problem with puppy 3.01loading nfs module failes :
{~] modprobe nfs
FATAL: Error inserting nfs (/lib/modules/2.6.21.7/kernel/fs/nfs/nfs.ko): Unknown symbol in module, or unknown parameter (see dmesg)
This quote taken from Puppy 3.01 final bugs report here

you might be able to pm llevet and ask him if he could upload the missing modules, or you could try compiling them yourselfllevet wrote:Hi,
I have resolved my problem of nfs.
In fact, it missing in release 3.01 the module sunrpc.ko and module lockd.ko![]()
Recompiling kernel and modules solve the pb.
Ludo.

NFS
SoapBean, thank you for your investigations. NFS now also works for me (after expanding the modules and running 'depmod'). Great.
The '/etc/hosts' issue is still unresolved. It seems to be a busybox problem, as 'ping', 'telnet' et.al. programs are busybox-commends.
After installing 'telnet' fron Slackware, 'telnet' is working as usual.
The '/etc/hosts' issue is still unresolved. It seems to be a busybox problem, as 'ping', 'telnet' et.al. programs are busybox-commends.
After installing 'telnet' fron Slackware, 'telnet' is working as usual.
ping
I forgot to memtion that 'ping' works ok with option '-4', like
where pcname is defined in '/etc/hosts'
Code: Select all
ping -4 pcname
Re: NFS
Hi Sprotte,Sprotte wrote:SoapBean, thank you for your investigations. NFS now also works for me (after expanding the modules and running 'depmod'). Great.
The '/etc/hosts' issue is still unresolved. It seems to be a busybox problem, as 'ping', 'telnet' et.al. programs are busybox-commends.
After installing 'telnet' fron Slackware, 'telnet' is working as usual.
how may I install the missing nfs module? I have the same problem with puppy 4.00 .
thanks, woddy
Linux und Dreambox - Fan
Puppy Anfänger :?
Puppy Anfänger :?
Hi Mark
I tried like your post and it seems to work, but I can't mount my Dreambox.
It must be a Puppy 4.0 problem; with Muppy 2.12 it works without problems.
Edit: It works now !!! Mounting my Dreambox is realy fast.
Gruss, Manni
I tried like your post and it seems to work, but I can't mount my Dreambox.
Code: Select all
mount -t nfs -o rw 192.168.178.12:/hdd /dream
mount: 192.168.178.12:/hdd: can't read superblock
Edit: It works now !!! Mounting my Dreambox is realy fast.
Gruss, Manni
Linux und Dreambox - Fan
Puppy Anfänger :?
Puppy Anfänger :?
Hello Woddy,
I did exactly the same on a 4.0 and got exactly the same error message "can't read superblock ". Still stuck there. May I ask how you actually solved this issue?
Best regards,
PS: thanks to all of you, Puppy masters: my old Sony Vaio (Celeron 366, 160 MB RAM, 4GB HDD) is (almost) back!!!
I did exactly the same on a 4.0 and got exactly the same error message "can't read superblock ". Still stuck there. May I ask how you actually solved this issue?
Best regards,
PS: thanks to all of you, Puppy masters: my old Sony Vaio (Celeron 366, 160 MB RAM, 4GB HDD) is (almost) back!!!
Dans Linux il y a un noyau. Dans Windows il y a des pépins.
nfs share problems
Hi, thanks for the info, but having difficulties. I loaded the modules from the last page, loaded nfs, and am getting this:
My command is this:
Any thoughts on this?
~dinky
Code: Select all
mount: RPC: Program not registered
Code: Select all
mount-FULL -t nfs 192.168.0.4:/home/curious/Documents /root/Desktop/share
~dinky
trouble=solved
maybe you need -o nolock so
mount-FULL -t nfs -o nolock 192.168.0.4:/home/curious/Documents /root/Desktop/share
i have a same problem. But solved.
rinovan.co.cc
internet cafe
mount-FULL -t nfs -o nolock 192.168.0.4:/home/curious/Documents /root/Desktop/share
i have a same problem. But solved.
rinovan.co.cc
internet cafe