Andrei POPESCU wrote:
> On Mi, 03 iul 19, 18:22:30, Michael Biebl wrote:
>> Usually ethernet interfaces are name eth* and wifi interfaces are named
>> wlan*, so yeah, if you have a single ethernet interface which is named
>> eth0 and a single wifi interface that is named wlan0, then you are safe
Back from my walk in the lovely warm pouring rain...
Justin B Rye wrote:
> Michael Biebl wrote:
>> Am 29.06.19 um 15:09 schrieb Justin B Rye:
>>> [...] A file in
>>> + /lib/modprobe.d can be overridden by one with
>>> the
>>> + s
Michael Biebl wrote:
> Am 29.06.19 um 15:09 schrieb Justin B Rye:
>> + configure a machine as a router, may encounter problems upgrading to
>> buster.
>> + New versions of udev install a
>
> That modprobe config file is shipped by the systemd packag
Justin B Rye wrote:
> Okay, back to the drawing board:
I attach a slightly rephrased version with markup.
> [...]
>
> It sounds as if we should also be adding something to the effect that
>
> With systemd it may be simpler to configure virtual network devices
> using
Baptiste BEAUPLAT wrote:
>> Do we have any idea what their use case would be? Apparently a
>> different one from Baptiste's, if it's true that he needed to
>> explicitly configure "numdummies=1"...
>
> In my case, I didn't need to specify the "numdummies=1" as it is the
> default (when systemd
Michael Biebl wrote:
> Afaiu, the kernel default is to create one dummy device by default when
> the module is loaded.
> I assume there might be cases where users rely on that default behaviour
> without having explicitly configured anything.
Do we have any idea what their use case would be?
Justin B Rye wrote:
> Okay, so here's a first rough idea of what the release-notes might
> say.
Properly formatted patch attached.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff --git a/en/issu
Michael Biebl wrote:
> Am 26.06.19 um 21:39 schrieb andreimpope...@gmail.com:
>> On Mi, 26 iun 19, 20:23:59, Baptiste BEAUPLAT wrote:
>>> The only way to force modprobe to use local configuration is to rename
>>> the /etc/modprobe.d/dummy.conf file to /etc/modprobe.d/systemd.conf.
>>
>> Is this
