| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The issue still needs proper fixing, but at least this makes things work again.
|
|
We need to make sure no the systemd services are only considered
started when the network is actually up. Otherwise, things relying
on the network don't know when they can start.
This means that we need to use Type=forking or Type=oneshot, and in
the case of ifplugd we must daemonize and wait for the daemon to be
ready before we continue.
Also do some minor cleanup:
- don't include env files that are not used
- don't ignore return values
Signed-off-by: Tom Gundersen <teg@jklm.no>
|
|
It is not enough to order ourselves Before network target, we must also
make sure it is pulled in. This means that anything that needs the network
to be up before they start can order themselves After=network.target.
Reported-by: Tobias Powalowski <tpowa@archlinux.org>
Signed-off-by: Tom Gundersen <teg@jklm.no>
|
|
It is once again possible to use NET= at the kernel command line when using net-profiles.
|
|
Configuration is done through /etc/conf.d/netcfg.
Compatibility with configuration through /etc/rc.conf is dropped.
|
|
The netcfg service provides support for the NETWORKS array in /etc/conf.d/netcfg through netcfg-daemon.
The netcfg@ service allows individual profiles to be treated as services. These services wait until a connection is established (the other service has support for backgrounding)!
|
|
The proposed script for net-auto-wireless has been reported as
non-working, change it to look like net-auto-wired.
Signed-off-by: Rémy Oudompheng <remy@archlinux.org>
|
|
Signed-off-by: Rémy Oudompheng <remy@archlinux.org>
|
|
Signed-off-by: Rémy Oudompheng <remy@archlinux.org>
|
