On Wed, Dec 8, 2010 at 12:15:02 -0400, Joey Hess wrote:
Michael Biebl wrote:
Please also note that e.g. if you setup your (ethernet) connection using a
static IP configuration, we do not comment such interface configurations
either.
So the issue about NM not managing certain devices
found 606268 0.6.6-3
thanks
Hi Joey
On 08.12.2010 00:19, Joey Hess wrote:
Are you suggesting to create a keyfile connection based on the configuration
from /etc/network/interfaces?
I'm suggesting that network-manager needs to deal with standard
interfaces files as generated by d-i, and
Michael Biebl wrote:
Could you please post further examples of such interfaces files generated by
d-i, especially wireless configurations.
Why? Here is the code that generates them:
if ((fp = file_open(INTERFACES_FILE, a))) {
fprintf(fp, \n# The primary network interface\n);
Michael Biebl wrote:
Please also note that e.g. if you setup your (ethernet) connection using a
static IP configuration, we do not comment such interface configurations
either.
So the issue about NM not managing certain devices extends to ethernet
interfaces as well and this behaviour has
On 08.12.2010 00:19, Joey Hess wrote:
Michael Biebl wrote:
Upgrading from which version?
0.8.1-4
I also don't understand why you say that the network is taken down.
Because it was taken down, when the postinst stopped network-manager,
and did not come back up when the postinst started
Michael Biebl wrote:
The network being taken down on upgrades from prvious 0.8.x versions under
certain circumstances is an issue.
Afaics this won't affect fresh installs though or upgrades from lenny.
This is wrong for reasons I explained in
20101207234147.ga3...@gnu.kitenet.net.
--
see shy
On 08.12.2010 00:51, Joey Hess wrote:
Michael Biebl wrote:
The network being taken down on upgrades from prvious 0.8.x versions under
certain circumstances is an issue.
Afaics this won't affect fresh installs though or upgrades from lenny.
This is wrong for reasons I explained in
7 matches
Mail list logo
