Have any of you have been successfully in creating a Samba share on Fedora Silverblue?

I've been trying for days and have been impossible.

All I get is not enough permission to access share from client

`testparm

Load smb config files from /etc/samba/smb.conf

Loaded services file OK.

Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback)

Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

Global parameters

[global]

printcap name = cups

security = USER

usershare allow guests = Yes

usershare max shares = 100

workgroup = SAMBA

idmap config * : backend = tdb

cups options = raw

[homes]

browseable = No

comment = Home Directories

inherit acls = Yes

read only = No

valid users = %S %D%w%S

[printers]

browseable = No

comment = All Printers

create mask = 0600

path = /var/tmp

printable = Yes

[print$]

comment = Printer Drivers

create mask = 0664

directory mask = 0775

force group = @printadmin

path = /var/lib/samba/drivers

write list = @printadmin root

[Drive]

guest ok = Yes

path = /var/home/htpc/Drive

read only = No

valid users = htpc`

4 points · 12 comments · view on lemmy.world

12 Comments

sundaylab@lemmy.ml · 3 pts · 1y (2 replies)

Have you created the samba password for your user?

Try

sudo smbpasswd -a username

yumyumsmuncher@feddit.uk · 1 pts · 1y (1 reply)

same error

sundaylab@lemmy.ml · 2 pts · 1y

What's the exact error that you get?

that_leaflet@lemmy.world · 2 pts · 1y
[ removed ]
Telorand@reddthat.com · 1 pts · 1y (8 replies)

I don't know if these notes would help, but I believe you should be able to make this work in podman, rather than trying to muck about with the primary system files.

https://www.procustodibus.com/blog/2022/10/wireguard-in-podman/

It's about using wireguard, but I would imagine most of the concepts should be the same.

trbeach@lemmy.world · 3 pts · 1y (2 replies)

FWIW....

My 2 cents. I tried and tried to make samba work. Finally, I saw a post from someone that said, "samba is for windows, SSH is for Linux". Best post I ever read. SSH for me ever since.

The first thing I do after install is uninstall samba.

Happy days ever since.

yumyumsmuncher@feddit.uk · 1 pts · 1y

I gave up, ended up using SSH

Telorand@reddthat.com · 1 pts · 1y

I've never tried to set up Samba, so I think this is probably good advice

just_another_person@lemmy.world · 1 pts · 1y (4 replies)

This is the most convoluted use of basic services I've ever seen just to make Samba work 😂😂😂

Y'know, there's a MUCH simpler way to make this work by just using a regular distribution without these limitations.

Telorand@reddthat.com · 2 pts · 1y (3 replies)

What you call a limitation is a way to ensure uptime. Yes, it sometimes involves unique ways of solving problems, but that doesn't mean going with a traditional mutable system is the best option for people's needs.

I have Bazzite on a shared laptop, and knowing that the people who will use it won't have to worry about fucking up the system with a bad update is great peace of mind.

just_another_person@lemmy.world · 2 pts · 1y (2 replies)

I run thousands of servers and have never had a "bad update" take a node down. Not since the 00's at least.

Telorand@reddthat.com · 1 pts · 1y (1 reply)

Lucky you? I can't say the same.

Regardless, OP didn't ask if they should just switch, they asked how to solve their problem. They can decide for themselves if they want to try to use containers or just install traditional Fedora.

just_another_person@lemmy.world · 2 pts · 1y

Gave them an answer as well.