How to Install Fuse-smb on Acer Aspire One Print

Information about fuse-smb is bit scarce and nothing I've found specific to the Acer. Installation isn't difficult and the result works well for me.
You don't need to have shares mounted when you switch on, so nothing slows down the normal startup. With a simple script and a desktop shortcut, you can browse your network when you need using the Thunar File Browser.

To install on the AAO, press Alt+F2 to open the Run dialog and check "Run in Terminal" or select Terminal from the Desktop menu, to open a terminal window. Type the following command:

[user@localhost ~]$ sudo yum -y install fuse-smb

Fuse is automatically loaded on the AAO, at least I didn't find I needed to use modprobe anywhere.

Now you need to set permissions to use fuse. Type the following:

[user@localhost ~]$ sudo lgroupmod -M user fuse

You'll need to reboot before these permissions are recognised, but do that later. Fuse-smb gets it settings from .smb/fusesmb.conf, which is not created automatically. Depending on your network, the default settings will probably work, but if some of your shared folders need passwords to gain access, then you will need to create a .smb/fusesmb.conf. In this situation do the following:

[user@localhost ~]$ cd ~
[user@localhost ~]$ mkdir .smb
[user@localhost ~]$ cp /usr/share/doc/fuse-smb-0.8.7/fusesmb.conf.ex .smb/fusesmb.conf
[user@localhost ~]$ chmod 600 .smb/fusesmb.conf
[user@localhost ~]$ mousepad .smb/fusesmb.conf

Look through the comments in the file, lines beginning with ; You should either enter your username and password in the [global] section or create entries for specific servers or shares. Save the file when done.

How to Use Fuse-smb

To be able to use the shares you must mount the fusesmb filesystem to an existing directory. I chose to create my mount point in the /media folder, as this is where Linpus mounts other removable media.

[user@localhost ~]$ sudo mkdir /media/network

Now the actual mounting of the shares:

[user@localhost ~]$ fusesmb /media/network
or
[user@localhost ~]$ sudo fusesmb /media/network -o allow_other
if you haven't rebooted yet.

To test if its working, browse /media/network with Thunar file manager or use the following:

[user@localhost ~]$ ls /media/network

If all is well, you should see your workgroup and be able to browse all the servers and shares that you have. It may take a few seconds the first time for machines to appear, but subsequently the information is cached and updated periodically.

Make it easy to use

So we can now access our network drives using the file manager, but its still hard to get up and running. There are suggestions for auto starting the process, but that's just going to slow down startup and with a mobile device like the AAO, you won't want your home network all the time anyway. My solution, a short script to run fusesmb if the folder is empty, then launch Thunar to display the netwok folder. All this wrapped up in a .desktop file and added to the files section of the desktop. Here's how:

First create the script...

[user@localhost ~]$ sudo mousepad /usr/sbin/network_start

#!/bin/sh
if [ `ls /media/network | wc -l` -eq 0 ]; then
fusesmb /media/network -o allow_other
fi
launch-thunar.sh /media/network

[user@localhost ~]$ sudo chmod a+x /usr/sbin/network/network_start

Next create the .desktop file.

[user@localhost ~]$ sudo mousepad /usr/share/applications/network.desktop

[Desktop Entry]
Version=1.0
Encoding=UTF-8
Name=Network Neigbourhood
Name[en_GB]=Network Neigbourhood
GenericName=My Network
Comment=Browse Network
Exec=network_start
Terminal=false
Type=Application
Icon=network

[user@localhost ~]$ sudo chmod a+r /usr/share/applications/network.desktop

Now add the icon to the desktop (13 is the Files section):

[user@localhost ~]$ dca add 13 "file='/usr/share/applications/network.desktop'"

The result looks like this:
I know it could do with a better icon. This is just the default network icon. If anyone can provide an icon to match the default colour scheme, I'll gladly host it here.

Comments   

0 #4 ThanksGuest 2010-06-30 09:48
Thanks Brian. Now I can't even see my shares in the network folder when I enter "sudo fusesmb /media/network -o allow_other". I haven't changed anything since I last posted. :sad:

I should probably try to get that fixed before I try anything else? I'm getting close to giving up with networking... Maybe even giving up with Linpus. How are you finding UNE? :-)
Quote
0 #3 Re: Connection timed outwebmaster 2010-06-11 09:51
Chris,

I will assume the share is accessible from other computers you have (if not, that's the first thing to check and resolve).

If the share is on a NAS device or is a Linux server, make sure you have configured anonymous access or the correct user id and password are in the fusesmb.conf file. It seems to be a good idea to have a default user and password set in fusesmb.conf anyway, even if they don't match users on the server.

I've found shares on Windows machines more problematic from linux. Not setting a password on the share has given me the most problems. What works for me is setting a user id/password in fusesmb.conf of a valid windows user for the machine with the share. Again, this works better when a password is set for the account on windows. Not having a password seems to confuse the whole process.

Windows 7 has tightened security and changed the rules where networking is concerned. Without being able to upgrade to the newest version of samba, I don't think this will work. I've now installed UNE 10.04 on my Acer, which doesn't need sbmfuse, so can't try the Win 7 set up with Linpus, and I still have difficulty with viewing my Win 7 shares and vice versa. Win 7 won't browse shares on old versions of samba. If you know the share, you can type the address and open it manually.

If you are still having problems, smbtree command should help. This will show what your netbook can see. Use the switches to set different user/passwords and see what difference this makes to the view. Also use the debug switch to see what may be going wrong (start with a low level).

Regards,
Brian
Quote
0 #2 Connection timed outGuest 2010-06-11 03:13
Hi. I'm wondering if you can help me. After creating the /media/network folder, I restarted my AA1. Then I opened up the terminal and entered "fusesmb /media/network
or", but got an error message saying something along the lines of "you do not have permission to write to this folder". I put the "sudo fusesmb /media/network -o allow_other" instead and it all seemed to work. I can see my shared folders. But when I click on them, I just get a "timed out" error message:

"Failed to open directory "Videos". Connection timed out."

I've tried restoring my AA1 and going through these instructions a couple of times, but always get the same error. Any idea how I can fix it?

Thanks for the great tutorial by the way. This is the furthest that I've ever managed to get to successfully networking my AA1!
Quote
0 #1 Minor typosGuest 2010-06-05 16:51
Many thanks for the very useful script. Two typos that I noticed:

sudo chmod a+x /usr/sbin/network
should have
"network_start" at the end

and in network.desktop entry, the executable needs to be:
Exec=network_start
(not start_network)
Quote
blocky