On Mon, 14.04.14 01:07, Djalal Harouni (tix...@opendz.org) wrote:
Currently systemctl set-default will fail to change the default target
due to the 'default.target' being a symlink which is always the case.
Humm, no? Normally default.target should not exist in /etc, only in
/usr. This means
On Tue, Apr 22, 2014 at 08:01:43AM +0200, Lennart Poettering wrote:
On Mon, 14.04.14 01:07, Djalal Harouni (tix...@opendz.org) wrote:
Currently systemctl set-default will fail to change the default target
due to the 'default.target' being a symlink which is always the case.
Humm, no?
On Mon, Apr 14, 2014 at 01:07:52AM +0100, Djalal Harouni wrote:
Currently systemctl set-default will fail to change the default target
due to the 'default.target' being a symlink which is always the case.
To work around this, the user must specify the --force switch to be
able to overwrite
On Thu, Apr 17, 2014 at 01:41:51AM +0100, Djalal Harouni wrote:
On Mon, Apr 14, 2014 at 01:07:52AM +0100, Djalal Harouni wrote:
Currently systemctl set-default will fail to change the default target
due to the 'default.target' being a symlink which is always the case.
To work around
On Mon, Apr 14, 2014 at 01:07:52AM +0100, Djalal Harouni wrote:
Currently systemctl set-default will fail to change the default target
due to the 'default.target' being a symlink which is always the case.
To work around this, the user must specify the --force switch to be
able to overwrite
Currently systemctl set-default will fail to change the default target
due to the 'default.target' being a symlink which is always the case.
To work around this, the user must specify the --force switch to be
able to overwrite the existing symlink.
This is clearly a regression that was
