Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#50476 - [netctl] 90s boot delay because network.target and network-online.target are treated as one

Attached to Project: Arch Linux
Opened by Liam (networkimprov) - Sunday, 21 August 2016, 18:28 GMT
Last edited by Jouke Witteveen (jouke) - Tuesday, 13 December 2016, 10:19 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture All
Severity Medium
Priority High
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

Problem and workaround described here
https://bbs.archlinux.org/viewtopic.php?pid=1632295#p1632295

Discussion on Arch BBS pinned blame on a systemd change, but they pin it on netctl.
https://github.com/systemd/systemd/issues/4010

I have this netctl profile; the usb0 interface only appears if a usb-gadget is configured. This worked until systemd 230.

Description='Usb Networking'
Interface=usb0
Connection=ethernet
IP=static
Address=('192.168.99.2/30')
This task depends upon

Closed by  Jouke Witteveen (jouke)
Tuesday, 13 December 2016, 10:19 GMT
Reason for closing:  Fixed
Additional comments about closing:  e43a822
Requires systemd v233 which will be released in the beginning of 2017.
Comment by Jouke Witteveen (jouke) - Tuesday, 23 August 2016, 13:43 GMT
I disagree with the systemd change and have asked for more information at the systemd bug.
Comment by Liam (networkimprov) - Saturday, 27 August 2016, 20:05 GMT
Did you file a new bug on systemd? If so can you link here?
Comment by Jouke Witteveen (jouke) - Saturday, 27 August 2016, 21:17 GMT
No, I have not file a bug concerning ordering dependencies.
However, note that I did include a response to this bug:

For the usb gadget, I fail to see why you would want to enable a profile when the presence of the device is not certain at boot time. Maybe you are better off with a udev rule that runs `netctl start <profile>` whenever the device is plugged in.
Comment by Liam (networkimprov) - Saturday, 27 August 2016, 21:24 GMT
Yes, I fixed by adding this to my unit that creates the gadget:

Before=netctl@ethernet\x2dusb.service
Wants=netctl@ethernet\x2dusb.service # netctl profile "ethernet-usb"
Comment by Jouke Witteveen (jouke) - Sunday, 25 September 2016, 15:14 GMT

Loading...