Samba access

[wavemop]

What exactly is the reason Samba releases
made in Dolphin do work permanently but
applications that want to open or save files (via this Dolphin dialog)
are not allowed to access the share in the same way?

Why does a share made in Windows Explorer work
permanently for all applications but not in Linux?
Do applications access with different user rights?
Would really like to understand it.

Yes , I’ve now entered it in the fstab but why does it have to be done like that?

Thanx for a Explanation.

[OttoPresser]

I currently have a Samba share that gets mounted to a folder in my home directory, it gets mounted every time I boot the system. I am able to access it using any application. So my question is how are you mounting it in fstab? And does your user have permissions to access all the files within the share? That would be something on the server side.

Here is an example of I have set up in fstab:

//‘server name or ip’/filer/ /home/‘username’/filer cifs credentials=/home/‘username’/.smbcredentials,uid=‘username’,gid=‘username’ 0 0

Obviously you will have to change some parameters to match your system but this works for me system wide.

Hope this helps.

[wavemop]

Hi Otto - as I wrote of course it is working system wide after putting it into fstab.
Also before i did that it wasn’t a problem to read and write in the share with Dolphin when only if it was mounted temporally via Dolphin.
But at that moment Apps like Keepass that accessed the share via a Dolphin dialog had no permission to do so.
I really would like to know “what’s phase” here and why editing files is a “have to” ?

[dalto]

@OttoPresser

//‘server name or ip’/filer/ /home/‘username’/filer cifs credentials=/home/‘username’/.smbcredentials,uid=‘username’,gid=‘username’ 0 0

You should really consider using a systemd-automount for cifs shares. They behave a lot better when the network isn’t available for some reason.

Something like this:

//<ip or hostname>/<share name> /path/to/mountpoint cifs x-systemd.automount,x-systemd.idle-timeout=1min,rw,user,credentials=/path/to/credentialsfile.cred,iocharset=utf8,vers=2.0 0 0

[dalto]

@wavemop

I really would like to know “what’s phase” here and why editing files is a “have to” ?

There is no real answer to this question other than “because Linux and Windows are different”.

In Linux, it is common to make changes by editing files or running commands at the terminal. Sometimes, people create GUI tools for various tasks. In most cases, those tools are simply editing the files or running the commands for you.

[OttoPresser]

Honestly never had an issue with the current setup, never failed to mount but I’m always up to improve. Will definitely take a look.

[wavemop]

Editing files is not a problem FOR ME → it is for the rest of my family!
So if I want them to use Linux, there will always be this hurdle they will never ever jump over!
Basic-stuff like this should be user friendly for everyone - but i ts like it is…

[dalto]

The reality is that most basic tasks can be done without editing files or running commands.

However, for things related to system administration, that is not always the case.

My wife has been using for Linux exclusively for years now and she has never edited a config file or run terminal commands. This is because I do that stuff for her and most of that work is done at initial setup. I would say I only touch her laptop once or twice a year.

[wavemop]

My wife is haunting me to find the “@-Key”
Imagine she wants to access the “family-share” on a fresh installed EndOs on her own!