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#31254 - [systemd] include static config network.service with default unit files

Attached to Project: Arch Linux
Opened by c (c) - Wednesday, 22 August 2012, 22:32 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 23 August 2012, 12:43 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The custom network.service unit file https://wiki.archlinux.org/index.php/Systemd/Services#Static_ethernet_network is super useful for all machines with static network config and no need for netcfg and its unused dependency of dhcpcd.
I'd like to see that (possibly with a more distinct name) included with the default arch unit files.
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 23 August 2012, 12:43 GMT
Reason for closing:  Won't implement
Additional comments about closing:  See comments
Comment by Dave Reisner (falconindy) - Wednesday, 22 August 2012, 22:43 GMT
What "default arch unit files"? This is a unit that will need to be overridden in /etc for 99.9% of the population no matter how it's written. I don't see a point to putting it somewhere else other than the wiki.
Comment by c (c) - Wednesday, 22 August 2012, 22:49 GMT
"default arch unit files" = systemd-arch-units. The sample /etc/systemd/system/network.service looks generic enough for the very common "single ethernet device static config" scenario. The other alternative is making dhcpcd an optional dependency of netcfg.
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 22 August 2012, 22:56 GMT
do you read the first four lines of the README from systemd-arch-units?

HOW TO CONTRIBUTE
----------------------------------------
As of 5/28/12, I am no longer accepting NEW unit files here. Please submit them
upstream, and failing that, to Arch Linux directly.
Comment by Dave Reisner (falconindy) - Wednesday, 22 August 2012, 23:00 GMT
> The sample /etc/systemd/system/network.service

Note that it's in /etc. This isn't something that systemd-arch-units provides. Also note that systemd-arch-units has shrunken considerably. The package won't exist soon enough.
Comment by c (c) - Wednesday, 22 August 2012, 23:01 GMT
Sorry, seems I was mislead by https://wiki.archlinux.org/index.php/Systemd#A_pure_systemd_installation to install that package. Maybe the wiki page should be updated.
Comment by c (c) - Wednesday, 22 August 2012, 23:03 GMT
/etc/systemd vs /usr/lib/systemd: Sorry, I'll rephrase the feature request to include static-network.service in /usr/lib/systemd/system. Does that make more sense?
Comment by Dave Reisner (falconindy) - Wednesday, 22 August 2012, 23:08 GMT
No, it doesn't make sense, because network.service doesn't exist in the package. I'm still not sure why this needs to be added to a package just to be overridden.
Comment by c (c) - Wednesday, 22 August 2012, 23:13 GMT
What would override it? static-network.service is universal for that very common scenario. If included in the systemd package you can just enable the service and create /etc/conf.d/network for a very efficient and trivial network config looking pretty much like the original rc.conf network config support.
Comment by Dave Reisner (falconindy) - Wednesday, 22 August 2012, 23:18 GMT
The user? Use of an EnvironmentFile is frowned upon (yo dawg, i heard you like config). Very few people are going to notice the random new unit attached to the package and it'll just need to be advertised, say, in the wiki.

I see nothing wrong with the status quo. There's future plans to include simple static network config in systemd anyways.
Comment by c (c) - Wednesday, 22 August 2012, 23:21 GMT
It could be advertised as a replacement for the rc.conf network config support and removed once systemd gains a sufficient built-in alternative.
Comment by Dave Reisner (falconindy) - Thursday, 23 August 2012, 12:43 GMT
Not implementing this. It definitely doesn't belong in systemd, and as far as I can tell, there's absolutely nothing gained by moving it from the wiki to a package. This sort of thing has a guaranteed limited lifetime and I don't want to have to deal with a plan to deprecate and remove this.

Loading...