Being able to connect to the machine’s IP and able to validate the connection. Fun fact, Samba, as installed, has a blank /etc directory and the first direction given is to pull the default samba configs from the Samba github. Yeah, let’s apply that logic to SSH (we don’t), or XOrg (we don’t).
Also, great, you’re not using a DE. The functionality I was having issue with is not provided by Samba. It is provided by kdenetwork-filesharing which interfaces with Samba. Having a functional Samba is a prerequisite for what I need, but in no way impacts what you’re doing as the packages are properly split out.
Yes, but this is irrelevant to what my issue was. The problem was that my Android tablet was unable to connect to my main rig via SMB because Samba was broken. A 2nd portion of that was the ability to configure specific directories via the properties dialog in Dolphin also was not working. Neither of which is about Dolphin reaching out to another machine as that has nothing to do with Samba, but instead is smbclient.
So it’s blank? What exactly is the problem? Just follow the wiki and be done in a minute. I remember people whining on the arch forums, because the default config they shipped wasn’t working for their setup. Then they did this, so people have to actually think about what they are doing.
Other distros like Ubuntu have the luxury to always have the same “build”, while arch usually is build by the individual. Default configs can cause problems in these situations for arch users. That is the reality and the reason why some packages need you to set things up.
My god, how hard is this? This is a service being installed in a broken state. When other services are not installed in broken states. That is the problem. The wiki should be there to adjust from defaults but the defaults should have base functionality.
I’m not the one who necro’d the thread after 21 days of inactivity. My problem is solved. I solved it in spite of the elitists here. I’m only responding to people responding to me, not continuing to harp on.
See my edit for the reasoning of not including a default config. This is arch, not Ubuntu or other pre configured distros. It is hard, if you want to include a default in an ever changing environment.
edit:
Also, by just reading through the github config example, you can see that his encourages people to understand what exactly is happening. Especially considering samba not being the most secure thing in the world, this may also prevent some problems.
I did, and laughed, for three reasons. All of which I stated nearly a month ago.
Many other services are installed in a functional state. Please explain how those services could not similarly “cause problems in these situations for arch users.”
Base functionality for Samba doesn’t break anything. If you think it does, name it and convince me otherwise. Else you’re just floundering.
Samba is not installed by default. You have to choose to install it post install. That means any supposed “break” can be addressed in the Wiki. You don’t set up defaults for edge cases, especially not on user requested software to be installed. You set up defaults to the base functionality and then give directions to the user on how to to customize to taste.
That third point, about setting up defaults for the general case and not the edge case, is EXACTLY why every other service I listed (SSH, XOrg, Pipewire, Networking, XDG Portals, are all set up in a base functional state. Every one of those could “cause problems in those situations for arch users” - but those are edge cases and are left for those users to address.
Many other services are installed in a functional state. Please explain how those services could not similarly “cause problems in these situations for arch users.”
Many others, but not all. Samba is just one excpetion.
Samba is not installed by default. You have to choose to install it post install. That means any supposed “break” can be addressed in the Wiki. You don’t set up defaults for edge cases, especially not on user requested software to be installed. You set up defaults to the base functionality and then give directions to the user on how to to customize to taste.
I can just tell you what the people, doing all this arch stuff for free, felt about the config and the support questions in the forum. I can see why this seems to be the best option for them.
I think you are blowing this way out of proportion. Especially, because it’s pretty obvious what you need to do and it’s well documented(KDE, Samba). There are upsides if people need to dig deeper to use unsafe programs, like Samba sadly is, if used incorrectly.
Exactly… But it seems you’re barking up the wrong tree. This has been already suggested 20 times in this thread, but @Greyed does not seem to be interested in reading the wiki or doing any manual configuration. There is no point in continuing this conversation.
The only thing I can suggest is: use 'Buntu, Arch does not seem to be for you.
Can anyone explain why EnOS installing some things in a ‘usable’ state should somehow suggest that Arch should install something else in a state which OP thinks is usable?
BTW - I dumped samba after it’s ‘new’ protocols killed off compatability with Android - and I now just SSH as required…
Wise advice - from someone who loves the zsh config from Manjaro (I must admit, it was a boost for me) he thinks it needs to be in the AUR to continue using it…
Call me crazy (Ok, I can hear that!!!) but I still have remnants of various configs and conky files going back at least 2 years… and I’m not very clever at all.