Announcement

**sithlord48** · Nov 03, 2011, 07:01 AM

Re: You can only select local files

the shares have to be mounted. gnome will automount just about anything it sees. kde does not do this, the ezest way is prolly to use SMB4k to do it for you, or set up your /etc/fstab to mount the files as cifs or smbfs

this is not a bug but an intended feature. automounting and autorunning of things is a security issue. kde does not automout anything (unless you tell it to , might want to check system settings-> removeable devices. you might be able to have it mount the smb shares from there since it shows them in places already)

**pudsy** · Nov 07, 2011, 10:00 AM

[SOLVED]

Hi Sith,

Many thanks for your answer - I never realized the shares didn't get mounted but are accessed through some other means - silly me

I still think it's a bug though - not a feature

If I can browse the network shares with dolphin, copy and delete files, open files with the likes of kate and save them again and than next run into trouble trying to do the same from other applications, I call it a bug, not a security feature.

If this is the way usage of samba shares is "designed" to work for the ignorant user, the design team should rethink their perception of the capabilities of ignorant users :-X

There are no obvious hooks to "start using a SAMBA share properly" or even just "Mount SAMBA share" to be found anywhere except for the obvious browsing the network with Dolphin and adding them to places. But that doesn't work. Or at least not without the problems mentioned.

Instead, apparently by design, the ignorant user is expected to maybe:

open a terminal
sudo mkdir /media/somename
sudo smbmount //whatever
find out smbmount isn't installed
make sure an internet connection is open, which may not be the case, after all we want to connect to a LAN not WAN!
sudo apt-get install smbfs
try mounting the easy way:
sudo smbmount //server/share /media/somename -o rw
realize that (of course) the system can't find the server by its name and, not wanting to bother with other setup issues, resort to using the ip for now:
sudo smbmount //10.0.0.1/share /media/somename -o rw
rejoice in seeing the dir listing appear under /media/somename in Dolphin
curse the system again for not letting you actually use the files (opening a textfile results in an empty page in kate - even without warning/errors; trying to open from within kate at least produces an error message)
search the internet for more/other proper options
try some and fail because the ones found (dmask, fmask) are deprecated
RTFM man smbmount to find out about the new options and get totally bored and frustrated with technical issues about permissions on client and server that the ignorant user really doesn't want to know about, just wanting to read/write the files on the NAS just the way it always worked.
finding, well hidden in the 1000 words of text, a little note that if you do not want to mess with permissions you may want to try the option noperm
finally go back to the command prompt and type:
sudo smbmount //10.0.0.1/share /media/somename -o rw,noperm
...
now rember to do stuff like this for every share on the network every time the system starts and/or spend another day cursing at finding out how to automate this at startup without trying to load things before the kernel is good and ready for it and without hickups when on a different LAN etc etc.

Yai - those designers really must think highly of me and other ignorant users

Hope it helps some others with the same problem

Anyway - thanks again for pointing me in the right direction Sithlord - consider this [SOLVED]
Cheers :P

Announcement

You can only select local files [SOLVED]

You can only select local files [SOLVED]

Comment

Comment