nfs mount failed: mount 10.10.2.20:/tmp/nfsmount /mnt/nfs/ mount: wrong fs type, bad option, bad superblock on 10.10.2.20:/tmp/nfsmount, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount. helper program)  ........

sudo mount -a Unable to find suitable address. [35758.706993] CIFS VFS: Error connecting to socket. Aborting operation. [35758.707247] CIFS VFS: cifs_mount failed w/return code = -111 [35795.476160] CIFS VFS: Error connecting to socket. Aborting operation. [35795.476346] CIFS VFS: cifs_mount failed w/return code = -111 When the above happens "Unable eto find suitable address" it usually means the smb nam........

Add the following to fstab where 192.168.1.125/Media is the samba share and where /home/homeuser/Downloads is where you want to mount. Change user and pass to what is needed (if no pass is required it still works fine with the below). //192.168.1.125/Media /home/homeuser/Downloads cifs user=guest,pass=bla 0 0 mount: wrong fs type, bad option, bad superblock on //192.168.1.125/Media, &nbs........

This is obviously a bug in the r8169 kernel module and it seems to affect a lot of people. I upgraded to the latest kernel and hope this won't happen anymore, as it is a very serious error. This is especially serious for those who are running servers with this chipset, who can afford for the NIC to randomly go off-line for no apparent reason? [655548.189113] type=1505 audit(1277067560.902:5): operation="profile_load" name="/usr/bin/freshclam&q........

When trying to even cd or ls the mounted OCFS2 partition it crashes. Ithink this is a combination of VMWare Server's problem and the way I mounted and symlinked to it. More than anything this shows the problem and lack of forsight with VMWare, but also that OCFS2 is easily crashed if you do strange things. Output of /var/log/messages for OCFS2 Apr 10 15:57:45 localhost kernel: [84331.691258] Modules linked in: vmnet vmci vmmon ocfs2_stac........

This will give you the basic info needed to browse and connect to Samba shares from the command line. From the GUI of Gnome or KDE etc, it is pretty standard and straight forward. However, I've found very little guides on how to do it from the command line and if you're like me, a nerd who prefers command line for its simplicity and for remote use, this is the way to go. First get a list of all the Samba/SMB shares on the target. smbclient -L hostname........