From: Chen Qi
Previously, if there's a link config item in the config file like
l root root 1777 /tmp /var/tmp
and /tmp has existed, the symlink will not be created correctly.
Another example is the /run directory. If /run directory has been
created by some recipe or script before
On 02/20/2013 05:18 PM, Bernhard Reutner-Fischer wrote:
On 20 February 2013 08:16, ChenQi wrote:
On 02/20/2013 03:10 PM, Bernhard Reutner-Fischer wrote:
On 20 February 2013 06:55:33 wrote:
From: Chen Qi
Previously, if there's a link config item in the config file like
l root root
On 20 February 2013 08:16, ChenQi wrote:
> On 02/20/2013 03:10 PM, Bernhard Reutner-Fischer wrote:
>>
>> On 20 February 2013 06:55:33 wrote:
>>>
>>> From: Chen Qi
>>>
>>> Previously, if there's a link config item in the config file like
>>>
>>> l root root 1777 /tmp /var/tmp
>>>
>>> and
On 02/20/2013 03:10 PM, Bernhard Reutner-Fischer wrote:
On 20 February 2013 06:55:33 wrote:
From: Chen Qi
Previously, if there's a link config item in the config file like
l root root 1777 /tmp /var/tmp
and /tmp has existed, the symlink will not be created correctly.
Another exampl
On 20 February 2013 06:55:33 wrote:
From: Chen Qi
Previously, if there's a link config item in the config file like
l root root 1777 /tmp /var/tmp
and /tmp has existed, the symlink will not be created correctly.
Another example is the /run directory. If /run directory has been
c
From: Chen Qi
Previously, if there's a link config item in the config file like
l root root 1777 /tmp /var/tmp
and /tmp has existed, the symlink will not be created correctly.
Another example is the /run directory. If /run directory has been
created by some recipe or script before
