Quoting Steve Litt (sl...@troubleshooters.com):
> As you know, I was asking many Qemu LAN-peer questions on this list a
> week ago. My documentation on the subject has finally achieved
> first-draft status. If you'd like to see it, go to:
>
> http://troubleshooters.com/linux/qemu/nobs.htm
This i
Quoting Ralph Ronnquist via Dng (dng@lists.dyne.org):
> I think Lewis Carroll had a stab at this issue as well in "Through The
> Looking Glass" where the name of the Black Knight was called
> something... or how it was.
The White Knight, but yes, exactly -- Carroll playing with what we now
call t
On Thu, 4 Mar 2021 07:24:50 +0100
aitor wrote:
> Hi tito,
>
> On 4/3/21 0:47, tito via Dng wrote:
> > In my young years I used to tinker with linux distros on floppy
> > disks and there still where eth0, eth1 and so on but no udev,
> > so where did the names came from?
>
> They were assigned by
Hi tito,
On 4/3/21 0:47, tito via Dng wrote:
In my young years I used to tinker with linux distros on floppy
disks and there still where eth0, eth1 and so on but no udev,
so where did the names came from?
They were assigned by the kernel, i think.
Aitor.
On Sun, 2021-02-28 at 17:29 +0200, Dimitris via Dng wrote:
> haven't been in any online key signing parties, only a handful of
> physical ones so far (makes more sense seeing/confirming/trusting in
> person...). but all that, pre-covid...
> to work around the pandemic somehow, i'd probably start
On Wed, 03 Mar 2021 21:44:30 +
g4sra via Dng wrote:
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, March 3, 2021 7:54 PM, tito via Dng
> wrote:
>
> > On Wed, 03 Mar 2021 16:15:10 +
> > g4sra via Dng dng@lists.dyne.org wrote:
> >
>
>
> > >
>
> > > Your 'predictable' names name a
>What is the netiquette on this list for changing subject lines.
>I hate hijacking threads but I also hate breaking them.
>Which is the lesser of the two evils ?
>
:-)
My 2 cents: When the stuff I'm discussing no longer is apropos to the
OP's post, I change the subject line. I typically do it li
Quoting g4sra via Dng (dng@lists.dyne.org):
> What is the netiquette on this list for changing subject lines.
> I hate hijacking threads but I also hate breaking them.
> Which is the lesser of the two evils ?
Standards-compliant mailers' threading doesn't get broken by altering
the Subject header
What is the netiquette on this list for changing subject lines.
I hate hijacking threads but I also hate breaking them.
Which is the lesser of the two evils ?
publickey - g4sra@protonmail.com - 0x42E94623.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signatur
‐‐‐ Original Message ‐‐‐
On Wednesday, March 3, 2021 7:54 PM, tito via Dng wrote:
> On Wed, 03 Mar 2021 16:15:10 +
> g4sra via Dng dng@lists.dyne.org wrote:
>
> >
> > Your 'predictable' names name are being assigned by what ?
>
> By the kernel, I suppose as you can pass a kerne
On Wed, 03 Mar 2021 16:15:10 +
g4sra via Dng wrote:
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, March 3, 2021 3:21 PM, tito via Dng
> wrote:
>
> > On Wed, 03 Mar 2021 14:52:57 +
> > g4sra via Dng dng@lists.dyne.org wrote:
> >
>
> > > <-- huge snip -->
> > > Just for completenes
‐‐‐ Original Message ‐‐‐
On Wednesday, March 3, 2021 3:21 PM, tito via Dng wrote:
> On Wed, 03 Mar 2021 14:52:57 +
> g4sra via Dng dng@lists.dyne.org wrote:
>
> > <-- huge snip -->
> > Just for completeness should someone dig this thread up trying to
> > solve an issue...such as a 1
On Wed, 03 Mar 2021 14:52:57 +
g4sra via Dng wrote:
> <-- huge snip -->
>
> Just for completeness should someone dig this thread up trying to
> solve an issue...such as a 12 port router
>
> The kernel's FDT determines the order of detection for built-in
> interfaces. Learn how to make t
<-- huge snip -->
Just for completeness should someone dig this thread up trying to solve an
issue...such as a 12 port router
The kernel's FDT determines the order of detection for built-in interfaces.
Learn how to make them, then don't change it and the interfaces will always
come up the s
On Wed, 3 Mar 2021 15:07:14 +0100
John Hughes wrote:
> On 03/03/2021 14:01, tito wrote:
> > On Wed, 3 Mar 2021 10:16:13 +0100
> > John Hughes wrote:
> >
> >> On 02/03/2021 15:57, tito via Dng wrote:
> >>> I would add that renaming of multiple cards/ports works
> >>> only if you rename all of the
Le 03/03/2021 à 14:18, Antony Stone a écrit :
> I agree that "eth0" is less stupid than "enp0s0p1" etc., however I too like
> the use of descriptive names such as "CableModem", "Clients", "Servers" etc.
In case people like ethX names, which is my case, I just came with
the idea to use letters
On Wednesday 03 March 2021 at 14:03:46, tito via Dng wrote:
> On Wed, 3 Mar 2021 10:16:13 +0100 John Hughes wrote:
> >
> > Just avoid the "ethX" names (because of race conditions and because
> > they're stupid). Use something descriptive.
>
> they are less stupid than enp0s0p1 or the like and m
On Wed, 3 Mar 2021 10:40:20 +0100
Florian Zieboll via Dng wrote:
> On Wed, 3 Mar 2021 08:04:19 +0100
> tito via Dng wrote:
>
> > you can set the device names by MAC addresses at boot
> > and in the past it worked as udev/eudev net-persisent-name.rules
> > (but seems to be broken, optimized out
On Wed, 3 Mar 2021 10:16:13 +0100
John Hughes wrote:
> On 02/03/2021 15:57, tito via Dng wrote:
> > I would add that renaming of multiple cards/ports works
> > only if you rename all of them to a different intermediate name
> > and then back to wanted name and order otherwise renaming
> > can fai
On Wed, 3 Mar 2021 12:13:04 +0100
Florian Zieboll via Dng wrote:
> Sure, it is more error prone to work with enx"$mac" NIC names, but as
> it's probably too late for complaining, I just made my router "future
> proof":
>
> backup /etc/:
> $ cp -a /etc /etc.bkp
>
> cd to /etc/:
> $ cd /etc/
>
On Wed, 3 Mar 2021 10:49:19 +0100
Antony Stone wrote:
> On Wednesday 03 March 2021 at 10:40:20, Florian Zieboll via Dng wrote:
>
> > On Wed, 3 Mar 2021 08:04:19 +0100
> >
> > tito via Dng wrote:
> > > you can set the device names by MAC addresses at boot
> > > and in the past it worked as udev
On Wednesday 03 March 2021 at 10:40:20, Florian Zieboll via Dng wrote:
> On Wed, 3 Mar 2021 08:04:19 +0100
>
> tito via Dng wrote:
> > you can set the device names by MAC addresses at boot
> > and in the past it worked as udev/eudev net-persisent-name.rules
> > (but seems to be broken, optimized
On Wed, 3 Mar 2021 08:04:19 +0100
tito via Dng wrote:
> you can set the device names by MAC addresses at boot
> and in the past it worked as udev/eudev net-persisent-name.rules
> (but seems to be broken, optimized out nowadays).
Thanks, Tito, for the clue! I am using udev (resp. eudev) rules to
Of course the code was wrong; I've corrected it below...
On 03/03 19:24, Ralph Ronnquist wrote:
> On 03/03 01:06, Steve Litt wrote:
> >
> > Am I hearing correctly when I think you two are saying I can make
> > multiple network devices have determinate names (even if I don't select
> > those names
On 03/03 01:06, Steve Litt wrote:
>
> Am I hearing correctly when I think you two are saying I can make
> multiple network devices have determinate names (even if I don't select
> those names) by doing something with their MAC addresses? If so, how do
> I do it?
Since you do networking setup via
25 matches
Mail list logo
