Page MenuHomeSolus

Provide the ability to share folders over the network by default
Closed, ResolvedPublic


In Solus AFAIK there is no way to share folders over the network using graphical tools, I also believe this functionality should be provided in the default image. Using nautilus-share we can share folders using the samba usershare by simply right clicking the folder in nautilus and selecting sharing options.

Some manual configuration of samba is required to enable usershares to allow nautilus-share to work
In /etc/samba/smb.conf you'll need

   usershare path = /var/lib/samba/usershare
   usershare max shares = 100
   usershare allow guests = yes
   usershare owner only = no

Use testparm to test your smb.conf file for errors
Restart the smb service with systemctl restart smb
Use net usershare info to determine if usershares are enabled
You may need to manually create /var/lib/samba/usershare and set appropriate permissions on it (see ArchWiki samba usershares section)

I tested by sharing my Video folder and nautilus on my laptop as well as my Android device could see the share and play videos no problem. I still need to test accessing the share from Windows but I assume its working.

There is probably a more elegant way of enabling usershares that I haven't figured out, if you don't think this functionality should be provided by default,
at the very least could samba be configured to enable usershares by default, so nautilus-share would work after installation without any configuring.

Event Timeline

I just realized (kind of stupidly) that nautilus-share hasn't seen a release since 2011, so alternative graphical tools should be discussed.

Best if you close this, mate has decent samba support with caja-extensions and share-admin. It's kind of up to gnome if they want to maintain nautilus-share or gnome-user-share. I don't know of any maintained applications which provide a graphical tool for managing samba shares.

When Ikey talks about Solus as catering for the "home computing" market then providing the ability to share folders over the network by default becomes very relevant.

At the very least the Help Center should provide a "recipe" to achieve this functionality for normal users in the interim. "Won't fix" and "Samba is borked" just don't cut it.

I love Solus and admire the drive of the developers to make Solus better and understand the competition for limited resources. I however respectfully request that this bug deserves more consideration?

ermo added a subscriber: ermo.EditedDec 3 2017, 2:11 PM

@joebonrichie :

We're looking into how we can best configure this to work out of the box without any user intervention (see T5180).

Ikey recently added some ancillary functionality to qol-assist such that users will by default become members of the system group 'users' (which now has a known gid) -- this is needed for setting up samba and setting up the relevant usershare directory containing configuration snippets (see R3820:191162d8f2db ).

In short: We're on it. =)

ermo added a comment.EditedDec 3 2017, 2:40 PM

Documenting this here so it doesn't get lost:

# relevant smb.conf snippet

# Set up usershare functionality where users can set up shares themselves.
# The usershare path contains configuration snippets and is writable for
# members of the group 'users' by default (Solus-specific configuration).
# By default users can only edit their own shares (sticky bit is set on dir).
# Users can allow guest access to shares.
    usershare path = /var/lib/samba/usershare
    usershare max shares = 100
    usershare allow guests = yes
    usershare owner only = yes
    map to guest = Bad Password
# relevant samba.tmpfiles invocation for usershare functionality
d /var/lib/samba/usershare 1770 root 100 -

Note that qol-assist now sets up the users system group with gid=100 and adds human users to this group by default (per R3820:191162d8f2db + follow up commits)

ermo claimed this task.Dec 20 2017, 2:09 PM
ermo added a comment.Jan 8 2018, 11:54 PM

This was added with R3946:db5c0aff179d .

ermo closed this task as Resolved.Jan 22 2018, 4:22 PM

This was landed in stable more than a week ago and doesn't appear to have caused any issues so far.