https://bugzilla.novell.com/show_bug.cgi?id=422830 User lmuelle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422830#c1 Lars Müller <lmuelle@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |alpha096@virginbroadband.com.au --- Comment #1 from Lars Müller <lmuelle@novell.com> 2008-09-04 06:44:28 MDT --- The reason to do it the current 'read only' way is Samba. By default Samba uses read only for any share not configured as 'read only = no'. But how about allowing the YaST-user to overwrite this default and set _only_ inside YaST a special flag to add any new share with a read only or writeable default setting? By default this setting would be _read only_ to follow the Samba.org default. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=422830 User boyang@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422830#c3 Yang Bo <boyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |alpha096@virginbroadband.com.au --- Comment #3 from Yang Bo <boyang@novell.com> 2008-09-04 07:27:48 MDT --- resetting needinfo state....... -- 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.

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#c5 --- Comment #5 from Scott Couston <alpha096@virginbroadband.com.au> 2008-09-05 02:44:15 MDT --- Created an attachment (id=237774) --> (https://bugzilla.novell.com/attachment.cgi?id=237774) selt titled -- 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.

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#c7 --- Comment #7 from Scott Couston <alpha096@virginbroadband.com.au> 2008-09-05 02:45:01 MDT --- Created an attachment (id=237776) --> (https://bugzilla.novell.com/attachment.cgi?id=237776) selt titled -- 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.

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.

https://bugzilla.novell.com/show_bug.cgi?id=422830 Jiří­ Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsuchome@novell.com AssignedTo|jsuchome@novell.com |locilka@novell.com -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=422830 User lmuelle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422830#c12 --- Comment #12 from Lars Müller <lmuelle@novell.com> 2008-09-24 10:01:04 MDT --- I had a general setting for a newly created shares in mind. Something like a template. By default - not modified by the administrator - this would define any new share as read only. But this template setting would allow an administrator to define any newly created share as write able. -- 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.

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#c14 --- Comment #14 from Scott Couston <alpha096@virginbroadband.com.au> 2008-09-24 22:40:01 MDT --- The other issue is Kcontrol with its File Sharing Features. Right Clicking on a KDE desktop on any foler will take you straight there - and a user can change/dictate/mess-up just about everything, but they cannot remove the Read Only Default. In Principal we start a Samba Server to share Windows files - Its a great problem when having to Print OR Fine the Linux Printer via HTTTP-CPU OR Kcontrol OR Yast configuration, becuse you will never write to the printer Network Printing will not work unless you remove the default only and/or add Browsable Flags. If we Use a Linux Samba Server as a file Server/Mass Backup unit the read only default flag renders it useless with the Read-only Flag Now When it comes to the "browsable" flag, if you select "Allow User to share their home directories, WHY is the Browsable Flag set to = NO. I think you may need to revisit the default masks that are accessed when adding a directory, an more over the default ReadOnly that exists when the application is started in Yast. Further thought needs to be given to the role of Kcontrol Sharing options with are somewhere between subservient/submersive to Many Yast Services. Samba being the first. Could you also let me know the value of the Yast Network Services - Windows Domain Membership as it appears it can operate in opposition to many others and most of this information is already contained in Samba Server and Kcontrol Much more work needs to be done in this area of 3 x confusion. Wait for CPU's Enhancements - It only has 4 different areas of confusion -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=422830 User locilka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422830#c16 Lukas Ocilka <locilka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka@novell.com AssignedTo|locilka@novell.com |anschneider@novell.com --- Comment #16 from Lukas Ocilka <locilka@novell.com> 2008-09-26 04:01:58 MDT --- (In reply to comment #15 from Andreas Schneider)

I'm reassigning this bug as it is a YaST enhancement.

I'm sorry but in such case, please, file a FATE entry. We can't add it now. -- 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.

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#c17 Scott Couston <alpha096@virginbroadband.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #17 from Scott Couston <alpha096@virginbroadband.com.au> 2009-02-09 13:50:42 MST --- This has already been fixed by new wizard and the default shares are R/W and the Wizard gives the user the ability to control Read/Write access to shares newly created Reporter happy to close as fixed in 11.0 -- 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.