Forcing the upgrade does not seem to break DHCP interfaces.
However, lo0 no longer works:
IMHO, the best way to solve this is to have os-specific set of
commands, which ifupdown execute.
It would allow us to stop wrapping ifconfig and route
and install them directly.
For previous problems
Hello,
On Sat, 18 Jun 2011 11:58:23 +0200 (CEST)
Petr Salinger petr.salin...@seznam.cz wrote:
Agree. The only problem is to find anyone
who can write such a .defn file
I do not know what is .defn file.
This is the file which describes which actions should be performed to
put some
On GNU/kFreeBSD ifconfig and route commands are available.
The syntax is (should be) the same as in upstream:
http://www.freebsd.org/cgi/man.cgi?query=ifconfig
http://www.freebsd.org/cgi/man.cgi?query=route
So it's mostly compatible with Linux ifconfig/route?
Mostly, but see [1], i.e.
Hello,
On Wed, 15 Jun 2011 13:32:38 +0200 (CEST)
Petr Salinger petr.salin...@seznam.cz wrote:
Forcing the upgrade does not seem to break DHCP interfaces.
However, lo0 no longer works:
IMHO, the best way to solve this is to have os-specific set of
commands, which ifupdown execute.
It
Forcing the upgrade does not seem to break DHCP interfaces.
However, lo0 no longer works:
IMHO, the best way to solve this is to have os-specific set of
commands, which ifupdown execute.
It would allow us to stop wrapping ifconfig and route
and install them directly.
For previous problems see
5 matches
Mail list logo
