Package: udev
Followup-For: Bug #787364
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
As of version 220-6, the bug no longer appears on my amd64 machine.
* What exactly did you do (or not do) that was effe
Arthur: if the bug is still unresolved, you should reopen this report.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: udev
Followup-For: Bug #787364
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
I am getting ifup working automatically with udev 218-10 but udev 219-10 fails
to do an automatic ifup.
*** End of the template - remove these template lines
Package: udev
Version: 220-5
Followup-For: Bug #787364
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Any of udev 220-? releases in Debian so far, including 220-5.
Upon rebooting, interface eth0 gets an IPV6 ad
Package: udev
Version: 220-4
Followup-For: Bug #787364
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
As previously reported, udev 220-2, 220-3 and 220-4 fail to do an ifup on this
amd64 machine, whilst working
Package: udev
Version: 215-18
Followup-For: Bug #787364
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
udev 220-2, 220-3, 220-4 result in ifup service not running on my amd64
machine, but I have not had this pr
Package: udev
Version: 220-1
Severity: serious
ifupdown "allow-hotplug" interfaces are not being triggered any more
through /lib/udev/rules.d/80-networking.rules -> net.agent ->
ifup@.service with udev 220.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (ww
7 matches
Mail list logo
