On Sat 05 Apr 2014 at 19:29:51 -0400, Stephen Powell wrote:

> Thanks for your research, Brian.  None of the above surprises me, based

It's about all I can do because my understanding of how udev works is
sparse. Continuing:

8.  Observed there was a file, tmp-rules--70-persistent-net.rules, in
    /run/udev. It had entries for the machine's two interfaces.

9.  Updated the install, did a dist-upgrade and installed systemd. Deleted
    70-persistent-net.rules and rebooted with init=/bin/systemd.
    70-persistent-net.rules is not present afterwards.

10. Installed systemd-sysv and rebooted.

11. The 'ifconfig -a' output (without the 'lo' entry), is

    eth0      Link encap:Ethernet  HWaddr 00:40:f4:72:4e:e1
              BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    eth1      Link encap:Ethernet  HWaddr 00:19:d1:4d:2a:70
              inet addr:192.168.7.213  Bcast:192.168.7.255  Mask:255.255.255.0
              inet6 addr: fe80::219:d1ff:fe4d:2a70/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:433 errors:0 dropped:0 overruns:0 frame:0
              TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:44734 (43.6 KiB)  TX bytes:3036 (2.9 KiB)
              Interrupt:21 Memory:dffe0000-e0000000

12. 'cat /etc/udev/rules.d/70-persistent-net.rules' has

    # PCI device 0x10ec:0x8139 (8139too)
      SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:40:f4:72:4e:e1", \
          ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

    A reboot without an 'rm' doesn't get the other interface added. There
    is a tmp-rules--70-persistent-net.rules file containing the missing
    (e1000e) interface.

    The result above isn't obtained consistently; sometimes both
    interfaces are shown and there is no tmp-rules file. Coincidentally
    it seems to happen when the network cable to e1000e is unattached.


I have no idea what significance, if any, is to be attached to these
data. However, I'm now inclined to view the bugs in CUPS as more
tractable. :)

Regards,

Brian.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to