Just wanted to chime in and say that this thread was very helpful to
me. I had the same issue with a mysterious eth0 entry showing up in
NetworkManager a minute or two every time after I woke up my laptop and
ruining connectivity. Very glad to have that working now!
--
Devrin Talen
Resending to the list
On Sun, Aug 24, 2014 at 2:12 PM, Erwan David er...@rail.eu.org wrote:
Le 24/08/2014 19:31, Tom H a écrit :
With v208, there's a generator,
/lib/systemd/system-generators/systemd-rc-local-generator, that
creates a symlink at boot in
On Sun, Aug 24, 2014 at 6:00 PM, Stephen Powell zlinux...@wowway.com wrote:
On Sun, 24 Aug 2014 15:44:26 -0400 (EDT), David Baron wrote:
On Sunday 24 August 2014 11:45:40 Stephen Powell wrote:
I have a static route command in my /etc/rc.local file to define
a route to another network. I
Hello, list.
I just thought I'd pass along something that I recently discovered.
When using sysvinit as the init system, if the file /etc/rc.local
exists and is executable, it will be invoked at the tail end of the
boot process. But under systemd, this file is not executed during
boot. Not by
On Sun 24 Aug 2014 at 11:45:40 -0400, Stephen Powell wrote:
I just thought I'd pass along something that I recently discovered.
When using sysvinit as the init system, if the file /etc/rc.local
exists and is executable, it will be invoked at the tail end of the
boot process. But under
On Sun, Aug 24, 2014 at 11:45 AM, Stephen Powell zlinux...@wowway.com wrote:
I just thought I'd pass along something that I recently discovered.
When using sysvinit as the init system, if the file /etc/rc.local
exists and is executable, it will be invoked at the tail end of the
boot process.
On Sunday 24 August 2014 11:45:40 Stephen Powell wrote:
Hello, list.
I just thought I'd pass along something that I recently discovered.
When using sysvinit as the init system, if the file /etc/rc.local
exists and is executable, it will be invoked at the tail end of the
boot process. But
On Sun, 24 Aug 2014 15:44:26 -0400 (EDT), David Baron wrote:
On Sunday 24 August 2014 11:45:40 Stephen Powell wrote:
...
Here is how I enabled it. (The following commands are
executed as root.)
cd /lib/systemd/system/multi-user.target.wants
ln -s ../rc-local.service rc-local.service
Stephen Powell zlinux...@wowway.com wrote:
I hate network-manager! Is there anything I can do to make it leave
eth0 totally in the control of ifupdown and to not touch it at all,
and to not create a stupid extra connection, and to leave my static
routes, that it did not create, alone?
On Sun, 24 Aug 2014 18:00:52 -0400 (EDT) Stephen Powell sent:
snip
The default installation of Debian for a
desktop system (XFCE in my case) installs both ifupdown and
network-manager. It allows ifupdown to manage only the local
loopback interface (lo) and allows network-manager to manage
On Sun, 24 Aug 2014 18:00:52 -0400 (EDT)
Stephen Powell zlinux...@wowway.com wrote:
network-manager! Is there anything I can do to make
it leave eth0 totally in the control of ifupdown and to not
touch it at all
The settings in /etc/network/interfaces are automatically used instead of
Am 25.08.2014 00:00, schrieb Stephen Powell:
simply eth0. (I have managed=true in the [ifupdown] section
of /etc/NetworkManager/NetworkManager.conf.) I then select
If you set managed=true, you actually tell NetworkManager to manage the
interface.
So I'm not sure why you are surprised that it
On Sun, 24 Aug 2014 19:05:52 -0400 (EDT), Michael Biebl wrote:
If you set managed=true, you actually tell NetworkManager to manage the
interface. So I'm not sure why you are surprised that it does.
In a previous release of network-manager, if I didn't set managed=true
in the [ifupdown]
13 matches
Mail list logo
