Jim Anderson wrote:
> Jim Anderson wrote:
>>
>> I have 3 Kubuntu/Linux PCs running on my LAN. PC1 is my primary
>> PC that I do most of my work on. It runs the 'feisty' release
>> of kubuntu, which I believe is release 7.04. PC2 is on
>> the network mostly so I can use the disk space for backups.
>> It also runs the 'feisty' release. PC3 is a new PC on
>> which I plan to do a special project. From PC3 I would like
>> to mount files systems from PC1 so I have access to information
>> on my primary PC. PC3 runs the 'gutsy' release of Kubuntu
>> which is release 7.10.
>>
>> NFS is working fine when I mount the filesystem on PC2 on to
>> PC1. However, when I try to mount the filesystem on PC2 on to
>> PC3, or when I try to mount a filesystem from PC1 on PC3,
>> I get the following error.
>>
>> > mount -t nfs 192.168.2.100:/media/hdc2 /mnt/hdc2
>> > mount: wrong fs type, bad option, bad superblock on
>> > 192.168.2.100:/media/hdc2,
>> > missing codepage or helper program, or other error
>> > In some cases useful info is found in syslog - try
>> > dmesg | tail or so
>>
>> Can anyone guide me on how to handle this error message?
>>
>> When I run 'dmesg | tail -20', I get the following results.
>>
>> > [ 39.294153] ACPI: Sleep Button (CM) [SLPB]
>> > [ 41.412964] e100: eth0: e100_watchdog: link up, 10Mbps, half-duplex
>> > [ 43.024546] NET: Registered protocol family 10
>> > [ 43.025211] lo: Disabled Privacy Extensions
>> > [ 43.544453] ppdev: user-space parallel port driver
>> > [ 43.884688] audit(1216092777.003:3): type=1503
>> > operation="inode_permission" requested_mask="a" denied_mask="a"
>> > name="/dev/tty" pid=4651 profile="/usr/sbin/cupsd"
>> > [ 44.019415] apm: BIOS version 1.2 Flags 0x03 (Driver version
>> > [ 1.16ac) 44.019425] apm: overridden by ACPI.
>> > [ 45.357931] Failure registering capabilities with primary security
>> module.
>> > [ 45.848322] Bluetooth: Core ver 2.11
>> > [ 45.848560] NET: Registered protocol family 31
>> > [ 45.848565] Bluetooth: HCI device and connection manager
>> > [ initialized 45.848573] Bluetooth: HCI socket layer initialized
>> > [ 45.885916] Bluetooth: L2CAP ver 2.8
>> > [ 45.885925] Bluetooth: L2CAP socket layer initialized
>> > [ 46.110762] Bluetooth: RFCOMM socket layer initialized
>> > [ 46.110991] Bluetooth: RFCOMM TTY layer initialized
>> > [ 46.110996] Bluetooth: RFCOMM ver 1.8
>> > [ 50.941967] NET: Registered protocol family 17
>> > [ 64.799877] eth0: no IPv6 routers present
>>
>> I don't think the dmesg is meaningful, because if I run the
>> mount command again, the output from dmesg does not change
>> at all.
>>
>>
>> Jim Anderson
>
>
> Nevermind! I found the solution. I installed the nfs-common
> package on PC3 and I was then able to mount using nfs.
> I'm sorry I did not try that before posting.
Bewilderment, plea for help, inspiration, installation, success.
All this in 15 minutes. Another small step for Linuxkind.
We knew you could do it!
|
Similar Threads
Linear Mode
