https://bugzilla.novell.com/show_bug.cgi?id=422830 User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=422830#c9 Scott Couston <alpha096@virginbroadband.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alpha096@virginbroadband.com.au Status|NEEDINFO |NEW Info Provider|alpha096@virginbroadband.com.au | --- Comment #9 from Scott Couston <alpha096@virginbroadband.com.au> 2008-09-05 02:48:38 MDT --- For added information I have initialed a Samba Server Wizard from Yast control interface. Yast provides these defaults from the default masks to provide the following. default shares are read only from the default shares. I would strongly change the default share mask as read, into read write ability on all Samba Defaults. Incorrect default 'read only" becomes a massive thou in the idea of the user further action would be to change the KDE Default staring. The Directory Option on any right click properties on any file,helps to change file seatings yet an further conflicts and more changes that appear must be set. Setting up a Samba Server via Yast should be the simple guided setup and placing other Samba directories helpful with the default mas a read= on NOT read only as in correct default make. I can find no logic is providing Samba or any file rights that are controlled by 'KDE File Sharing' and this functions, which are controlled by different Yasts Server of ant type. The KDE file sharing needs to be removed as the serves no purpose functionally, expect to confuse everyone. ALL Network File Sharing of such services have place except with one single machismo defines the shares right from the beginning and get rid of all this confusion. I would like to suggest that ALL your developers use the GUI facility to accomplish a task and leave the command prompt to a last resort. I makes this suggest because these simple GUI tasks that have arise in no developer use mostly all GU Tolls. have issues but the developer never user the HUI when working. To survive all analysis need to use the HUI facilities to accomplish most issues, it is early evident that the GUI functionality,was never been used much as at the beginning of every new release there so many HUI error...Not Per say if you never leave a console prompt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.