Then we'll suppose it got fixed by own of the numerous hardy Samba SRUs.
Thanks for your confirmation, Max-Ulrich.
** Changed in: samba (Ubuntu)
Status: Incomplete = Fix Released
--
Public shares not possible in home folder (Hardy 8.04)
https://bugs.launchpad.net/bugs/294728
You
I was not at home last week. Sorry for not answering sooner.
Thierry Carrez is right; the bug seemes to be fixed now. I have done
nothing else but installing the usual updates, and public shares now do
work in Hardy as well as in Intrepid.
Thanks, Max
--
Public shares not possible in home
I was not at home last week. Sorry for not answering sooner.
Thierry Carrez is right; the bug seemes to be fixed now. I have done
nothing else but installing the usual updates, and public shares now do
work in Hardy as well as in Intrepid.
Thanks, Max
--
Public shares not possible in home
** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
Public shares not possible in home folder (Hardy 8.04)
https://bugs.launchpad.net/bugs/294728
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
** Changed in: samba (Ubuntu)
Importance: Undecided = Medium
Target: None = ubuntu-8.04.2
--
Public shares not possible in home folder (Hardy 8.04)
https://bugs.launchpad.net/bugs/294728
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Can't reproduce this on hardy.
Starting from a virgin minimal install:
$ sudo apt-get install samba (3.0.28a-1ubuntu4.7 gets installed)
$ mkdir ~/Gemeinsam
$ chmod 0777 ~/Gemeinsam
and defining the [Gemeinsam] share as stated in comment 2: I can read/write to
the share alright.
Maybe you
** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
Public shares not possible in home folder (Hardy 8.04)
https://bugs.launchpad.net/bugs/294728
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: samba (Ubuntu)
Importance: Undecided = Medium
Target: None = ubuntu-8.04.2
--
Public shares not possible in home folder (Hardy 8.04)
https://bugs.launchpad.net/bugs/294728
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Can't reproduce this on hardy.
Starting from a virgin minimal install:
$ sudo apt-get install samba (3.0.28a-1ubuntu4.7 gets installed)
$ mkdir ~/Gemeinsam
$ chmod 0777 ~/Gemeinsam
and defining the [Gemeinsam] share as stated in comment 2: I can read/write to
the share alright.
Maybe you
I am surprised that the status of this bug report is still incomplete.
The bug must be known by the samba crew, because it is fixed in samba
3.2.3 implemented in Intrepid.
What I am asking for is to fix it in Hardy too because Hardy is LTS!
--
Public shares not possible in home folder (Hardy
@ Mathias Gug
Is that what you did need?
Perhaps that can help you: Public shares inside a directory (in this
case it is /home/farber/) are possible only if the access to the
*whole* directory is allowed for everyone. This is not normal. It should
be enough to allow access to the share. It had
@ Mathias Gug
Is that what you did need?
Perhaps that can help you: Public shares inside a directory (in this
case it is /home/farber/) are possible only if the access to the
*whole* directory is allowed for everyone. This is not normal. It should
be enough to allow access to the share. It had
What do you actually mean by configuration section? The few lines for
the share only or the [global] part also?
[Gemeinsam]
path = /home/farber/Gemeinsam
available = yes
browsable = yes
public = yes
writable = yes
The share is not accessible at all even if /home/farber/Gemeinsam is
set to mode
What do you actually mean by configuration section? The few lines for
the share only or the [global] part also?
[Gemeinsam]
path = /home/farber/Gemeinsam
available = yes
browsable = yes
public = yes
writable = yes
The share is not accessible at all even if /home/farber/Gemeinsam is
set to mode
14 matches
Mail list logo
