-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/24/2012 12:39 PM, Christian PERRIER wrote:
> Quoting Nikolaus Rath (nikol...@rath.org):
>
>> Hmm. I think defaulting to /etc/samba/private now, only to have
>> another transition once we've convinced upstream to comply with
>> FHS is inviting tr
Quoting Nikolaus Rath (nikol...@rath.org):
> Hmm. I think defaulting to /etc/samba/private now, only to have another
> transition once we've convinced upstream to comply with FHS is inviting
> trouble.
>
> If we have to obey FHS, wouldn't it be much easier to just replace
> fhs-filespaths.patch w
On 04/24/2012 12:42 AM, Christian PERRIER wrote:
>>
>> If think the proper solution is to drop the fhs-filespaths.patch and
>> make "private dir" default to upstreams layout, both in the installed
>> smb.conf and in the binary.
>
> Yes. However, if we could avoid adding something to smb.conf, it w
Quoting Nikolaus Rath (nikol...@rath.org):
> Hi,
>
> I'd like to help fix this, but I'm not quite sure what kind of patch
> you'd like to see here.
Thanks for your offer. I was planning to try fixing that bug myself as
I'm hit by it on some servers of mine (which I would like to set as
domain con
Hi,
I'd like to help fix this, but I'm not quite sure what kind of patch
you'd like to see here.
If think the proper solution is to drop the fhs-filespaths.patch and
make "private dir" default to upstreams layout, both in the installed
smb.conf and in the binary.
For migration, there would be a
5 matches
Mail list logo
