Michael Biebl (2015-04-23):
> Am 23.04.2015 um 22:22 schrieb Cyril Brulebois:
> > Michael Biebl (2015-04-23):
>
> >> netboot install writes duplicate entries to 70-persistent-net.rules
> >> ~~~
> >
> > It might be better not to emb
Am 23.04.2015 um 22:22 schrieb Cyril Brulebois:
> Michael Biebl (2015-04-23):
>> netboot install writes duplicate entries to 70-persistent-net.rules
>> ~~~
>
> It might be better not to embed the “netboot install” information here,
Hi!
Michael Biebl (2015-04-23):
> I talked to the release team and they prefer to postpone a fix to 8.1.
> I therefor would like to see a short paragraph added to the d-i 8.0
> errata [1].
>
> Afaics, the issue so far only happened for automated installations.
> There is no real solution/workaro
Hi everyone!
I talked to the release team and they prefer to postpone a fix to 8.1.
I therefor would like to see a short paragraph added to the d-i 8.0
errata [1].
Afaics, the issue so far only happened for automated installations.
There is no real solution/workaround ttbomk besides rebuilding d
Am 30.03.2015 um 04:56 schrieb Michael Biebl:
> Looks like a found a simple reproducer (this is on my work laptop) done
> during normal runtime of the system:
>
> $ rm /etc/udev/rules.d/70-persistent-net.rules
> $ while true ; do echo add > /sys/class/net/eth0/uevent ; done
>
> I let this run fo
Control: tags -1 confirmed
Am 18.03.2015 um 19:50 schrieb Michael Biebl:
> Am 18.03.2015 um 18:52 schrieb Michael Biebl:
>> Am 18.03.2015 um 18:15 schrieb Faidon Liambotis:
>>> Another less arbitrary/racy workaround I suggesed was a grep near the
>>> top of write_net_rules' write_rule() function.
Processing control commands:
> tags -1 confirmed
Bug #765577 [udev-udeb] netboot install writes duplicates to
70-persistent-net.rules
Bug #777126 [udev-udeb] udev: duplicate eth? entries
Added tag(s) confirmed.
Added tag(s) confirmed.
--
765577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
Am 18.03.2015 um 18:52 schrieb Michael Biebl:
> Am 18.03.2015 um 18:15 schrieb Faidon Liambotis:
>> Another less arbitrary/racy workaround I suggesed was a grep near the
>> top of write_net_rules' write_rule() function. Since write_rule()
>> operates under a lock, this would completely eliminate a
8 matches
Mail list logo
