Any comment that claims something is easy, or simple or obvious is fine,.... as long as it is followed by the actual instructions and explanations to complete the task.
Editing a .conf file is exactly one of those tasks where detailed instructions are required. KitchM 00:52, 28 September 2009 (EDT)
Major enhancements in Samba 3.4.0 include:
Configuration changes: The default passdb backend has been changed to 'tdbsam'!
The default passdb backend has been changed to 'tdbsam'! That breaks existing setups using the 'smbpasswd' backend without explicit declaration!
Please use 'passdb backend = smbpasswd' if you would like to stick to the 'smbpasswd' backend or convert your smbpasswd entries using e.g. 'pdbedit -i smbpasswd -e tdbsam'.
--Juanmah 09:52, 29 November 2009 (EST)
Removal of section regarding 3.4.3
I removed the section about downgrading due to problems with version 3.4.3 and afterwards realized this section had only just been added today. I don't mean to step on any toes here! However, as far as I know, there is no reason to downgrade now. The problem with browsing workgroups was fixed by a patch added to version 3.4.3-3 of the smbclient package. Please correct me if I am wrong!
- No worries; it was not added today. A note about changes in 3.4.0 was added today under the "3.4.3 issues" section; I merely split it into a separate section. The note about downgrading was added some weeks ago. -- pointone 17:11, 1 December 2009 (EST)
Possible omission in the Installation section
The Installation section states: "Installing only the client program is sufficient for systems that are not meant to share files, only access them". However installing just the smbclient package doesn't result in the creation of an /etc/samba/smb.conf file that apparently smbclient complains about if absent http://pastebin.com/f793e7a08 . An /etc/samba/smb.conf file is only created when one installs the 'samba' package as well. Please make the necessary edits. ~ erythrocyte Thu Feb 4 21:16:00 IST 2010
- The article is correct; smbclient warns about a missing smb.conf, but still works fine (at least on my system).
- Also, users only looking to access files will most likely be using mount.cifs that's included with the smbclient package (and doesn't complain about smb.conf).
- -- pointone 11:38, 4 February 2010 (EST)
- An interesting point. I have also been worried about these strange phrases popping up inappropriately. Do you think this should be mentioned upstream as a bug? - KitchM 12:59, 4 February 2010 (EST)
samba-client no longer exists as a seperate package. Edited the wiki to reflect that. Also fixed grammar to properly reflect changes. --Shoe - I like finding bugs. They make *Nix stronger. 04:02, 18 March 2010 (EDT)
Odd it didn't show up for me when I did Syu yesterday. Ah well. Correcting my correction. :) Thanks for pointing it out Pointone. :)--Shoe - I like finding bugs. They make *Nix stronger. 19:03, 18 March 2010 (EDT)
- I couldn't find it either. Perhaps using wrong name. It seems misleading to call one samba and the other smbclient. Why not samba-server and samba-client? Why must everything be confusing by not following standard naming conventions? Oh, well. - KitchM 11:44, 19 March 2010 (EDT)
The line states in part: "If xinetd was compiled with tcpwrapper flag enabled". Does anyone know how one might know if this is the case? - KitchM 00:18, 24 March 2010 (EDT)
Is the implication with the difference between KDE and Gnome on accessing shares that other DE's need special configurations as well? - KitchM 02:06, 7 May 2010 (EDT)
- As I read it, the difference is made between KDE and Gnome's graphical file managers (3.2) and from commandline (3.3). On the other hand, gvfs belongs to gnome - all a tad confusing. See my post below for a suggestion on how to rewrite that bit. Hokasch 12:02, 18 May 2010 (EDT)
- Thanks; very nice! I'm totally with you on this. In fact, what if someone uses a different file manager? Why are there so many different network browser mechanisms? Why so many different network protocols? Etc., etc.. I picked Ext3 only once when I installed the OS, and I didn't even have to configure that. I was able to connect to the Internet with little work. But to hook my computer to another one on my own LAN, I've got to jump thru hoops. That bugs the heck out of me. There's got to be a better way. - KitchM 01:43, 19 May 2010 (EDT)
With great wonder I just realized I can browse my (Windows) network in Nautilus (something I haven't managed to get working for years, despite following a lot of tips), by just running the Avahi-daemon. I never suspected "Avahi" to do such a thing, not sure why but the name sounded strange to me, more like a IM client or some browser search plugin spam.
Anyway, there is an Avahi page, but the only link to it is under "References" on the NFS page. I think this is information should be better integrated, as "browsing the network neighbourhood" is something rather basic you expect from your DE (or am I the only one not getting this?).
I suggest to rewrite the paragraph "Accessing a Samba share from Gnome or KDE" so it tells you how to browse Networks under these DE's - linking to the Avahi wiki page, and also give the tip that smb shares can be accessed "manually" through the pathbar. Xfce's Thunar has no in-build support for network browsing, but fusesmb and the like are already mentioned later on this page. "Accessing a Samba share from Nautilus or Konqueror" might be a better name.
Gnome/Nautilus: gvfs-smb, smbclient and runnning avahi (correct?)
KDE/Konqueror: don't know...
Hokasch 12:03, 18 May 2010 (EDT)