On 8/21/20 12:25 AM, Eli Schwartz via arch-general wrote:
>> That might have been an interesting precautionary measure for netctl
>> 1.18, at least for printing a message advising people to reenable the
>> service.
> Oh, for the record -- it looks like netctl already did this:
>
>
On 8/17/20 5:56 PM, Eli Schwartz wrote:
>> Couldn't there also be a post install that does a reenable for each netctl
>> profile found in /etc/systemd/system as another option to avoid this SNAFU?
>
> That might have been an interesting precautionary measure for netctl
> 1.18, at least for
On 18/08/2020 07.29, Erich Eckner via arch-general wrote:
> Hi list,
>
> I got hit by this, too.
>
Me too. Fortunately I was doing update on-site for a box without a BMC.
Regards,
Łukasz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi list,
I got hit by this, too.
On Mon, 17 Aug 2020, Eli Schwartz via arch-general wrote:
On 8/17/20 5:25 PM, David C. Rankin wrote:
By "subservice" I think you mean ".include" stanzas?
Your analysis is correct, this got removed from
On 8/17/20 5:25 PM, David C. Rankin wrote:
> Archdevs,
>
> I have two computers using netctl, one for a static and one for a dhcp
> address. After the last update on May, 3,
>
> netctl (1.22-1 -> 1.23-1)
>
> all remained fine and old profiles generated as subservices in
> /etc/systemd/system,
Archdevs,
I have two computers using netctl, one for a static and one for a dhcp
address. After the last update on May, 3,
netctl (1.22-1 -> 1.23-1)
all remained fine and old profiles generated as subservices in
/etc/systemd/system, such as:
netctl\@rlf_network\\x2dstatic.service
continued
6 matches
Mail list logo
