[DNG] obsoleting a login manager (was: What I learned at Distrowatch)
On Sat, 12 Dec 2020 21:15:32 -0500 Steve Litt wrote: > On Fri, 11 Dec 2020 15:53:35 +0100 > Didier Kryn wrote: > > > > I don't make it an argument against xdm. Just cheating about > > your own arguments (~: > > Didier, why didn't you make that suggestion to me 15 years ago? It's a > brilliant way to guarantee that if somebody logs out of X, they have > no logged in shell to make mischief with. > > I should have thought of that myself. 15 years ago :-). I'll make an argument against xdm and every login manager (for a single user): Just have the regular shell at certain TTYs launch X upon login. A snippet of it: \xinit /etc/X11/xinit/xinitrc -- /usr/bin/X :$(( tty_to_use - 1 )) \ vt"$tty_to_use" -auth "$( \tempfile --prefix='serverauth.' )" logout There's more code that makes the above work. See: https://github.com/spiralofhope/shell-random/blob/master/live/zsh/dot_zsh/4-login.sh It should work in dash. It's only kept in a zsh dotfile out of laziness. My method has always felt dirty and insecure, and I don't know why I haven't been using exec to remove the final process. Maybe I just didn't know any better. I'll explore the problem one day later. This notion is from my legacy days when I wanted to make Linux "lighter". ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On Sat, 12 Dec 2020 16:06:03 +0100
Antony Stone wrote:
> On Saturday 12 December 2020 at 15:27:08, d...@d404.nl wrote:
>
> > On 12-12-2020 14:15, Antony Stone wrote:
> > >
> > > According to https://wiki.debian.org/NetworkInterfaceNames the
> > > old 70- persistent-net.rules system _should_ still work in Buster
> > > / Beowulf, but I can't work out how to get it to do so.
> >
> > From what I understand after some research you need an additional
> >
> > /etc/udev/rules.d/10-network.rules as follows:
> > SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:00:01", NAME="eth0"
> > SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:00:02", NAME="eth1"
> > SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:20:01", NAME="eth2"
>
> Thanks, but no - it makes no difference.
>
> I tried:
>
> 1. Adding that file and keeping 70-persistent-net.rules as well
>
> 2. Adding that file and removing 70-persistent-net.rules
>
> 3. Both the above both with and without net.ifnames=0 in the kernel
> boot parameters.
>
> In every case I continue to get eth0 and eth1 as my PCI card, and the
> motherboard interface as eth2.
>
>
> Anyone else got any useful ideas?
You can create one or a few very simple shellscripts to turn stuff like
eno01y0u5uck02 into eth0, as long as the device isn't moved around,
which ports on a pci card wouldn't be. Another Devuaner and I wrote the
basics of such a script and posted it on this mailing list, several
years ago.
Sorry, but I'm on a tight deadline and can't research
anything more than this memory. Perhaps somebody else knows.
SteveT
Steve Litt
Autumn 2020 featured book: Thriving in Tough Times
http://www.troubleshooters.com/thrive
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Oldstable and Archive timing expectations?
On 2020-12-12 21:04, Adrian Zaugg wrote: On 04.12.20 19:43, goli...@devuan.org wrote: You might want to have a look at Debian's release schedule: https://wiki.debian.org/DebianReleases Does Devuan not follow the LTS schedule? https://wiki.debian.org/LTS Because when Debian Releases X as stable, Devuan needs some time to follow, as such Devuan stable stays for a while with Debian X-1, which is then under LTS as oldstable. At least it was with Jessie very much the case. With Jessie was this a coincidence or is that rather a rule? Regards, Adrian. Yes. That is correct. The lag between Debian stable and the corresponding Devuan stable release is why we recommend using the release name rather that the suite name in /etc/apt/sources.list Please see https://www.devuan.org/os/releases for more information. golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Oldstable and Archive timing expectations?
On 04.12.20 19:43, goli...@devuan.org wrote: > You might want to have a look at Debian's release schedule: > > https://wiki.debian.org/DebianReleases > Does Devuan not follow the LTS schedule? https://wiki.debian.org/LTS Because when Debian Releases X as stable, Devuan needs some time to follow, as such Devuan stable stays for a while with Debian X-1, which is then under LTS as oldstable. At least it was with Jessie very much the case. With Jessie was this a coincidence or is that rather a rule? Regards, Adrian. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Version control /etc (was Re: Ethernet names revisited)
Hi Hendrik, Hendrik Boom writes: > I wish everything user-configurable under /etc was under revision control. > then we might even be able to have a vendor branch and a local branch. Have a look at etckeeper. I've been using that for several years now on a variety of machines. The log for the machine I'm writing this on goes back all the way to its initial install on 2017-01-11 of Devuan's Jessie Official Beta2 :-) You may want to keep your sensitive /etc/ files out of the repository though, depending on your level of paranoia. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On 13/12 02:47, Antony Stone wrote: > On Sunday 13 December 2020 at 01:09:18, Ralph Ronnquist via Dng wrote: > > > Well, the kernel modules makes the first naming, and assigns them as > > eth0, eth1, eth2. That happens before udev starts. > > > > The kernel refuses any attempt to name an interface to, say, eth0 if > > that name is taken. > > > > Those "facts" have been in effect since last millenium, so whatever > > happened for you before would have happened within the eclipse of > > those "facts". > > So... what's the correct way, in a current Devuan release, to ensure > that each ethernet interface gets the name you want it to have, > based on its MAC address (which, as far as I know, is the only > uniquely identifiable thing about an interface, wherever it happens > to be found, and in whatever order it gets identified)? I wish I could tell you exactly: there are many different ways that turn out to work well for some range of situations, but then not for others. Generally the first step is to use a different, unused name series, say en0, en1, en2, with udev rules for mapping particular macaddress to particular name. If one could live with that, it would be a solution. To map back into ethN requires another udev rule, but this rule must not be in use until all the interfaces have been duly mapped (by the above rules). If you use initrd the root pivot make a "stage barrier"; you can arrange the rules such that this mapping-back rule is checked before the mapping forward rule for each interface, and thereby achieve that the back mapping only happens at the post-pivot /sys enumeration. I'm sure there may be other ways to achieve the "stage barrier"; udev is a programming language even if obscure. > > Antony. > > -- > Don't procrastinate - put it off until tomorrow. > >Please reply to the list; > please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What I learned at Distrowatch
On Fri, 11 Dec 2020 15:53:35 +0100 Didier Kryn wrote: > I don't make it an argument against xdm. Just cheating about your > own arguments (~: Didier, why didn't you make that suggestion to me 15 years ago? It's a brilliant way to guarantee that if somebody logs out of X, they have no logged in shell to make mischief with. I should have thought of that myself. 15 years ago :-). SteveT Steve Litt Autumn 2020 featured book: Thriving in Tough Times http://www.troubleshooters.com/thrive ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On Sunday 13 December 2020 at 01:09:18, Ralph Ronnquist via Dng wrote: > Well, the kernel modules makes the first naming, and assigns them as > eth0, eth1, eth2. That happens before udev starts. > > The kernel refuses any attempt to name an interface to, say, eth0 if > that name is taken. > > Those "facts" have been in effect since last millenium, so whatever > happened for you before would have happened within the eclipse of > those "facts". So... what's the correct way, in a current Devuan release, to ensure that each ethernet interface gets the name you want it to have, based on its MAC address (which, as far as I know, is the only uniquely identifiable thing about an interface, wherever it happens to be found, and in whatever order it gets identified)? Antony. -- Don't procrastinate - put it off until tomorrow. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On 13/12 00:40, Antony Stone wrote: > > If it worked for you previously then, a) there would have been rules > > for double renaming, > > Please point me at where I should find these. > > I only know that /etc/udev/rules.d/70-persistent-net.rules was the > *only* file I needed to edit if I wanted to rearrange the naming of > the interfaces under Jessie or earlier. Well, the kernel modules makes the first naming, and assigns them as eth0, eth1, eth2. That happens before udev starts. The kernel refuses any attempt to name an interface to, say, eth0 if that name is taken. Those "facts" have been in effect since last millenium, so whatever happened for you before would have happened within the eclipse of those "facts". > > and b) any network management would have kicked > > in late enough to let name fiddling happen before bringing up the > > interfaces. As you know, one of the joys with parallel boot is the > > random effects of things happening in parallel. > > I thought "parallel boot" was one of the evils that systemd was designed to > bring in. In what way does Devuan do "parallel boot"? afact 1) udev processes events (somewhat) in parallel, and 2) the post-pivot boot runs init scripts in as much parallelism as is allowed with respect to their declared dependencies. That latter thing is something newish (10 years?) but current default. > > The default installation (unfortunately?) have wicd as player to > > provide networking randomness, but network-manager is good at it too. > > I have neither of those installed on the machines in question. That's good. Then also avoid "allow-hotplug" declarations as otherwise udev will bring up interfaces in the pre-pivot boot. I think that should be enough for using ifrename. (It does come with the disadvantage of needing manual touch after plugging in cables) > Antony. > > -- > Perfection in design is achieved not when there is nothing left to add, but > rather when there is nothing left to take away. > > - Antoine de Saint-Exupery > >Please reply to the list; > please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited - a workaround (but the basic question still remains)
On Sat, 12 Dec 2020 23:11:52 +0100
Antony Stone wrote:
> On Saturday 12 December 2020 at 14:15:53, Antony Stone wrote:
>
> > Historically, I've been used to udev
> > and /etc/udev/rules.d/70-persistent- net.rules doing this, where I
> > can specify the name I want for each interface according to its MAC
> > address.
>
> > 1. how can I get 70-persistent-net.rules to carry on working under
> > Beowulf?
Hi,
enable predictable names (remove net.ifnames=0 or set it to 1
and update grub)
and use 70-persistent-net.rules with old names (maybe also
update initramfs if rules files are copied there)
Ciao,
Tito
> > 2. what's the "correct" way to get my interfaces named the way I
> > want, according to their MAC addresses, under Beowulf?
>
> So, I have found a workaround:
>
> 1. Create /etc/udev/rules.d/70-persistent-net.rules containing a set
> of rules such as:
>
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="78:ac:c0:f7:89:f7", ATTR{dev_id}=="0x0",
> ATTR{type}=="1", KERNEL=="eth*", NAME="xeth0"
>
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="00:e0:4c:80:21:6b", ATTR{dev_id}=="0x0",
> ATTR{type}=="1", KERNEL=="eth*", NAME="xeth1"
>
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="00:e0:4c:80:21:6c", ATTR{dev_id}=="0x0",
> ATTR{type}=="1", KERNEL=="eth*", NAME="xeth2"
>
> The names are in the order I want them, but prefixed with "x" so they
> don't conflict with what the kernel decided to call them as it booted.
>
> 2. Add some sections to /etc/network/interfaces:
>
> auto xeth0 xeth1 xeth2
>
> iface xeth0 inet manual
> up ip link set xeth0 down
> up ip link set xeth0 name eth0
>
> iface xeth1 inet manual
> up ip link set xeth1 down
> up ip link set xeth1 name eth1
>
> iface xeth2 inet manual
> up ip link set xeth2 down
> up ip link set xeth2 name eth2
>
> That re-renames the (already pseudo-renamed) interfaces to what I
> really want.
>
> I can then follow that with the standard:
>
> auto eth0
> iface eth0 inet static
> address 192.168.36.9
> netmask 255.255.255.0
> gateway 192.168.36.5
>
> etc.
>
>
> I would still *really like* to know:
>
> 1. how can I get 70-persistent-net.rules to carry on working as it
> used to, under Beowulf? (I never had to do this sort of workaround
> in Jessie or before.)
>
> 2. what's the "correct" way to get my interfaces named the way I want,
> according to their MAC addresses, under Beowulf, and therefore also
> Chimaera?
>
>
> Thanks,
>
>
> Antony.
>
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On Sunday 13 December 2020 at 00:01:06, Ralph Ronnquist via Dng wrote: > On 12/12 23:22, Antony Stone wrote: > > > > 1. Why is this so totally different from what I could previously do using > > /etc/udev/rules.d/70-persistent-net.rules under jessie and earlier > > releases? > > If it worked for you previously then, a) there would have been rules > for double renaming, Please point me at where I should find these. I only know that /etc/udev/rules.d/70-persistent-net.rules was the *only* file I needed to edit if I wanted to rearrange the naming of the interfaces under Jessie or earlier. > and b) any network management would have kicked > in late enough to let name fiddling happen before bringing up the > interfaces. As you know, one of the joys with parallel boot is the > random effects of things happening in parallel. I thought "parallel boot" was one of the evils that systemd was designed to bring in. In what way does Devuan do "parallel boot"? > The default installation (unfortunately?) have wicd as player to > provide networking randomness, but network-manager is good at it too. I have neither of those installed on the machines in question. Antony. -- Perfection in design is achieved not when there is nothing left to add, but rather when there is nothing left to take away. - Antoine de Saint-Exupery Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited - a workaround (but the basic question still remains)
On Sunday 13 December 2020 at 00:01:11, Florian Zieboll via Dng wrote: > On Sat, 12 Dec 2020 23:11:52 +0100 Antony Stone wrote: > > I would still *really like* to know: > > > > 1. how can I get 70-persistent-net.rules to carry on working as it > > used to, under Beowulf? (I never had to do this sort of workaround > > in Jessie or before.) > > Hallo Antony, > > do I understand correctly, that your issue is the order of the NICs > (not eth0 assigned to the onboard card, but eth1 or eth2) and not the > naming scheme (ethN vs. predictable) itself? Correct. > If so, have you double checked, that 'net.ifnames=0' is really not set / did > you remember to 'update-grub' after changing it? Both correct. > Did you check /lib/udev/rules.d/ for conflicting rules? There is nothing there which: a) references the names of my interfaces (eg: eth0) b) references the MAC addresses of my interfaces c) is more recent than January 1st 2020, on a machine I installed last week, therefore I don't believe the files there have any knowledge of my hardware. Antony. -- The Magic Words are Squeamish Ossifrage. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited - a workaround (but the basic question still remains)
On Sat, 12 Dec 2020 23:11:52 +0100 Antony Stone wrote: > I would still *really like* to know: > > 1. how can I get 70-persistent-net.rules to carry on working as it > used to, under Beowulf? (I never had to do this sort of workaround > in Jessie or before.) Hallo Antony, do I understand correctly, that your issue is the order of the NICs (not eth0 assigned to the onboard card, but eth1 or eth2) and not the naming scheme (ethN vs. predictable) itself? If so, have you double checked, that 'net.ifnames=0' is really not set / did you remember to 'update-grub' after changing it? Did you check /lib/udev/rules.d/ for conflicting rules? libre Grüße, Florian ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On 12/12 23:22, Antony Stone wrote: > On Saturday 12 December 2020 at 23:11:25, Ralph Ronnquist via Dng wrote: > ... > > 1. Why is this so totally different from what I could previously do using > /etc/udev/rules.d/70-persistent-net.rules under jessie and earlier releases? > > 2. https://wiki.debian.org/NetworkInterfaceNames clearly says that if you > upgraded a machine from jessie to stretch and to buster (which for these > purposes I regard as the same as jessie to ascii to beowulf), then it will > continue to work as before, so - what is the difference between doing those > upgrades, and doing a fresh buster / beowulf installation? What needs to be > changed on a beowulf machine to make it work the same as a jessie machine > upgraded to ascii, upgraded to beowulf? If it worked for you previously then, a) there would have been rules for double renaming, and b) any network management would have kicked in late enough to let name fiddling happen before bringing up the interfaces. As you know, one of the joys with parallel boot is the random effects of things happening in parallel. > > And, of course, finally: > > 3. Once /etc/udev/rules.d/70-persistent-net.rules no longer works at > all under Chimaera, what is the correct / official way of getting > interfaces named as you want them, according to their MAC addresses? Without being held awake by this issue myself, I can only suggest a two phase solution where you have 1) udev rules kicking in during pre-pivot boot to rename anything ethN onto say the xethN series, and then 2) an ifrename service for the post-pivot boot, to name the interfaces by macaddress. Howver, in order for that to work you must also make sure that your network management software stays inactive until after the ifrename activity. The easiest for that is to only rely the ifupdown networking which in the normal setting is a post-pivot activity subsequent to ifrename. The default installation (unfortunately?) have wicd as player to provide networking randomness, but network-manager is good at it too. Ralph > > Thanks, > > > Antony. > > -- > I bought a book about anti-gravity. The reviews say you can't put it down. > >Please reply to the list; > please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On Saturday 12 December 2020 at 23:11:25, Ralph Ronnquist via Dng wrote: > It really isn't that hard: > > when the kernel starts it will give its default names to the > interfaces as ethN numbering them in order it initializes them. In > your case it will use the names eth0, eth1 and eth2 that get assigned > in whatever time order the kernel discovers them in. > > Eventually(!) the hotplug handler (udev) kicks in to process your > rules, and at that time there are three interfaces named eth0, eth1 > and eth2, so it will be impossible to make, say, the eth2 interface > get the name eth0 without first making the eth0 interface be named > something else. It would here be nice with a name *swapping* program, > but there is none. It used to work, with udev and the rules.d files. > So, if you are not happy with those names being used the way they are > by the kernel, then you will have to arrange it to name them all > twice: first to some other name series (eg en0, en1, en2) and > thereafter back onto the original name series (eth0, eth1, eth2) on > the basis of some other adapter property (eg macadress). I think you have given an excellent description of what is going on. 1. Why is this so totally different from what I could previously do using /etc/udev/rules.d/70-persistent-net.rules under jessie and earlier releases? 2. https://wiki.debian.org/NetworkInterfaceNames clearly says that if you upgraded a machine from jessie to stretch and to buster (which for these purposes I regard as the same as jessie to ascii to beowulf), then it will continue to work as before, so - what is the difference between doing those upgrades, and doing a fresh buster / beowulf installation? What needs to be changed on a beowulf machine to make it work the same as a jessie machine upgraded to ascii, upgraded to beowulf? And, of course, finally: 3. Once /etc/udev/rules.d/70-persistent-net.rules no longer works at all under Chimaera, what is the correct / official way of getting interfaces named as you want them, according to their MAC addresses? Thanks, Antony. -- I bought a book about anti-gravity. The reviews say you can't put it down. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited - a workaround (but the basic question still remains)
On Saturday 12 December 2020 at 14:15:53, Antony Stone wrote:
> Historically, I've been used to udev and /etc/udev/rules.d/70-persistent-
> net.rules doing this, where I can specify the name I want for each
> interface according to its MAC address.
> 1. how can I get 70-persistent-net.rules to carry on working under Beowulf?
>
> 2. what's the "correct" way to get my interfaces named the way I want,
> according to their MAC addresses, under Beowulf?
So, I have found a workaround:
1. Create /etc/udev/rules.d/70-persistent-net.rules containing a set of rules
such as:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="78:ac:c0:f7:89:f7", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="xeth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:e0:4c:80:21:6b", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="xeth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:e0:4c:80:21:6c", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="xeth2"
The names are in the order I want them, but prefixed with "x" so they don't
conflict with what the kernel decided to call them as it booted.
2. Add some sections to /etc/network/interfaces:
auto xeth0 xeth1 xeth2
iface xeth0 inet manual
up ip link set xeth0 down
up ip link set xeth0 name eth0
iface xeth1 inet manual
up ip link set xeth1 down
up ip link set xeth1 name eth1
iface xeth2 inet manual
up ip link set xeth2 down
up ip link set xeth2 name eth2
That re-renames the (already pseudo-renamed) interfaces to what I really want.
I can then follow that with the standard:
auto eth0
iface eth0 inet static
address 192.168.36.9
netmask 255.255.255.0
gateway 192.168.36.5
etc.
I would still *really like* to know:
1. how can I get 70-persistent-net.rules to carry on working as it used to,
under Beowulf? (I never had to do this sort of workaround in Jessie or
before.)
2. what's the "correct" way to get my interfaces named the way I want,
according to their MAC addresses, under Beowulf, and therefore also Chimaera?
Thanks,
Antony.
--
These clients are often infected by viruses or other malware and need to be
fixed. If not, the user at that client needs to be fixed...
- Henrik Nordstrom, on Squid users' mailing list
Please reply to the list;
please *don't* CC me.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
It really isn't that hard:
when the kernel starts it will give its default names to the
interfaces as ethN numbering them in order it initializes them. In
your case it will use the names eth0, eth1 and eth2 that get assigned
in whatever time order the kernel discovers them in.
Eventually(!) the hotplug handler (udev) kicks in to process your
rules, and at that time there are three interfaces named eth0, eth1
and eth2, so it will be impossible to make, say, the eth2 interface
get the name eth0 without first making the eth0 interface be named
something else. It would here be nice with a name *swapping* program,
but there is none.
So, if you are not happy with those names being used the way they are
by the kernel, then you will have to arrange it to name them all
twice: first to some other name series (eg en0, en1, en2) and
thereafter back onto the original name series (eth0, eth1, eth2) on
the basis of some other adapter property (eg macadress).
Ralph.
On 12/12 15:27, d...@d404.nl wrote:
> On 12-12-2020 14:15, Antony Stone wrote:
> > Hi.
> >
> > I've just installed a couple of Beowulf systems, each of which has three
> > ethernet interfaces; one on the motherboard, and two on a PCI card.
> >
> > I'm trying to work out how to give those interfaces the names I want; the
> > motherboard as eth0, and the PCI card as eth1 / eth2.
> >
> > Historically, I've been used to udev and /etc/udev/rules.d/70-persistent-
> > net.rules doing this, where I can specify the name I want for each
> > interface
> > according to its MAC address.
> >
> > The file didn't exist (although the directory did) on my Beowulf system, so
> > I
> > created one with the appropriate contents, and I now get messages while the
> > kernel is booting:
> >
> > udevd[441]: Error changing net interface name eth2 to eth0: File exists
> > udevd[441]: could not rename interface '4' from 'eth2' to 'eth0': File
> > exists
> > udevd[438]: Error changing net interface name eth1 to eth2: File exists
> > udevd[438]: could not rename interface '3' from 'eth1' to 'eth2': File
> > exists
> > udevd[445]: Error changing net interface name eth0 to eth1: File exists
> > udevd[445]: could not rename interface '2' from 'eth0' to 'eth1': File
> > exists
> >
> > I've followed the entire thread on this list from July 2018 about this,
> > which
> > I've found _some_ of in the archives at
> > https://lists.dyne.org/lurker/message/20180715.200323.7a2473a2.en.html
> > however
> > that link shows only a very small proportion of the emails in the
> > discussion
> > for some reason (I have my own local copy in my mail client).
> >
> > According to https://wiki.debian.org/NetworkInterfaceNames the old 70-
> > persistent-net.rules system _should_ still work in Buster / Beowulf, but I
> > can't work out how to get it to do so.
> >
> > I _have_ tried adding "net.ifnames=0" to the kernel boot line; this makes
> > no
> > difference.
> >
> > So:
> >
> > 1. how can I get 70-persistent-net.rules to carry on working under Beowulf?
> >
> > 2. what's the "correct" way to get my interfaces named the way I want,
> > according to their MAC addresses, under Beowulf?
> >
> > (The above Debian wiki document indicates that Buster is the last release
> > which will continue to support this, so I'm assuming I'll need to do
> > something
> > else for Chimaera; what is it?)
> >
> >
> > Thanks,
> >
> >
> > Antony.
> >
> From what I understand after some research you need a additional
> /etc/udev/rules.d/10-network.rules as follow:
>
> |SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:00:01", NAME="eth0"
> SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:00:02", NAME="eth1"|
> ||SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:20:01", NAME="eth2" Hope
> this helps. Grtz Nick | |
>
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On Sat, Dec 12, 2020 at 02:15:53PM +0100, Antony Stone wrote: > Hi. > > I've just installed a couple of Beowulf systems, each of which has three > ethernet interfaces; one on the motherboard, and two on a PCI card. > > I'm trying to work out how to give those interfaces the names I want; the > motherboard as eth0, and the PCI card as eth1 / eth2. > > Historically, I've been used to udev and /etc/udev/rules.d/70-persistent- > net.rules doing this, where I can specify the name I want for each interface > according to its MAC address. > > The file didn't exist (although the directory did) on my Beowulf system, so I > created one with the appropriate contents, and I now get messages while the > kernel is booting: > > udevd[441]: Error changing net interface name eth2 to eth0: File exists > udevd[441]: could not rename interface '4' from 'eth2' to 'eth0': File exists > udevd[438]: Error changing net interface name eth1 to eth2: File exists > udevd[438]: could not rename interface '3' from 'eth1' to 'eth2': File exists > udevd[445]: Error changing net interface name eth0 to eth1: File exists > udevd[445]: could not rename interface '2' from 'eth0' to 'eth1': File exists > > I've followed the entire thread on this list from July 2018 about this, which > I've found _some_ of in the archives at > https://lists.dyne.org/lurker/message/20180715.200323.7a2473a2.en.html > however > that link shows only a very small proportion of the emails in the discussion > for some reason (I have my own local copy in my mail client). > > According to https://wiki.debian.org/NetworkInterfaceNames the old 70- > persistent-net.rules system _should_ still work in Buster / Beowulf, but I > can't work out how to get it to do so. > > I _have_ tried adding "net.ifnames=0" to the kernel boot line; this makes no > difference. > > So: > > 1. how can I get 70-persistent-net.rules to carry on working under Beowulf? I remember having this problem some years ago with some upgrade (I no longer know which one). It may not have been ascii -> beowulf. And it may have been an earlier Debian upgrade. In the past when eth0 and eth1 got misassigned I had fixed things by swapping the cables on the back of the machine. Since in those days things were consistend from boot to boot, it took care of the problem. However, this time things were no longer so consistent. I had to solve it by assigning new names to the interfaces (thus not eth0 or eth1) and modifying all the config files mentioning those interface names (I found them with grep) to use the new names instead. Apparently the eth0 file names were allocated a a low-level in the kernel and the kernel did not take kindly to having them changed. It should have been easier. Unfortunately I can no longer find the files where I did this. If you have ideas where I could look, I can try to figure out what I did. I wish everything user-configurable under /etc was under revision control. then we might even be able to have a vendor branch and a local branch. -- hendrik > > 2. what's the "correct" way to get my interfaces named the way I want, > according to their MAC addresses, under Beowulf? > > (The above Debian wiki document indicates that Buster is the last release > which will continue to support this, so I'm assuming I'll need to do > something > else for Chimaera; what is it?) > > > Thanks, > > > Antony. > > -- > Numerous psychological studies over the years have demonstrated that the > majority of people genuinely believe they are not like the majority of people. > >Please reply to the list; > please *don't* CC me. > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On Saturday 12 December 2020 at 16:28:04, Didier Kryn wrote: > Le 12/12/2020 à 14:15, Antony Stone a écrit : > > > > 1. how can I get 70-persistent-net.rules to carry on working under > > Beowulf? > > > > 2. what's the "correct" way to get my interfaces named the way I want, > > according to their MAC addresses, under Beowulf? > > Udev has made a big effort to hide its action to the administrator. > The rules have first been cached in /lib/udev; then the administerable > files in /etc have been removed. > > Eudev keeps a track of the names it has already assigned to > interfaces, in /lib/udev/rules.d . Ah, thanks, I didn't know about that directory (and indeed there are a *lot* of files in it - far more even than I'm used to seeing in old Debian machines' /etc/udev/rules.d/ directories). > Maybe you can find something concerning your ethernet interfaces in > one of these files and maybe your problem is just that Eudev doesn't > want to overwrite that file; therefore you might try to delete it > (rename it for safety). Hm; no. Firstly there are no references to eth0, eth1 or eth2 in any of those files, and secondly the files are all older than Jan 1 2020, so clearly nothing has been put there based on the hardware in this machine. > I don't grant it works; but this is one thing I would try. Thanks for the idea, and thanks for pointing me at something I didn't previously know about, even if it wasn't the solution to my problem. Antony. -- Never automate fully anything that does not have a manual override capability. Never design anything that cannot work under degraded conditions in emergency. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
Le 12/12/2020 à 14:15, Antony Stone a écrit : > Hi. > > I've just installed a couple of Beowulf systems, each of which has three > ethernet interfaces; one on the motherboard, and two on a PCI card. > > I'm trying to work out how to give those interfaces the names I want; the > motherboard as eth0, and the PCI card as eth1 / eth2. > > Historically, I've been used to udev and /etc/udev/rules.d/70-persistent- > net.rules doing this, where I can specify the name I want for each interface > according to its MAC address. > > The file didn't exist (although the directory did) on my Beowulf system, so I > created one with the appropriate contents, and I now get messages while the > kernel is booting: > > udevd[441]: Error changing net interface name eth2 to eth0: File exists > udevd[441]: could not rename interface '4' from 'eth2' to 'eth0': File exists > udevd[438]: Error changing net interface name eth1 to eth2: File exists > udevd[438]: could not rename interface '3' from 'eth1' to 'eth2': File exists > udevd[445]: Error changing net interface name eth0 to eth1: File exists > udevd[445]: could not rename interface '2' from 'eth0' to 'eth1': File exists > > I've followed the entire thread on this list from July 2018 about this, which > I've found _some_ of in the archives at > https://lists.dyne.org/lurker/message/20180715.200323.7a2473a2.en.html > however > that link shows only a very small proportion of the emails in the discussion > for some reason (I have my own local copy in my mail client). > > According to https://wiki.debian.org/NetworkInterfaceNames the old 70- > persistent-net.rules system _should_ still work in Buster / Beowulf, but I > can't work out how to get it to do so. > > I _have_ tried adding "net.ifnames=0" to the kernel boot line; this makes no > difference. > > So: > > 1. how can I get 70-persistent-net.rules to carry on working under Beowulf? > > 2. what's the "correct" way to get my interfaces named the way I want, > according to their MAC addresses, under Beowulf? > > (The above Debian wiki document indicates that Buster is the last release > which will continue to support this, so I'm assuming I'll need to do > something > else for Chimaera; what is it?) > > > Thanks, > > > Antony. Udev has made a big effort to hide its action to the administrator. The rules have first been cached in /lib/udev; then the administerable files in /etc have been removed. Eudev keeps a track of the names it has already assigned to interfaces, in /lib/udev/rules.d . Maybe you can find something concerning your ethernet interfaces in one of these files and maybe your problem is just that Eudev doesn't want to overwrite that file; therefore you might try to delete it (rename it for safety). I don't grant it works; but this is one thing I would try. -- Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On Saturday 12 December 2020 at 16:06:29, tito via Dng wrote:
> On Sat, 12 Dec 2020 14:15:53 +0100 Antony Stone wrote:
> > Historically, I've been used to udev
> > and /etc/udev/rules.d/70-persistent- net.rules doing this, where I
> > can specify the name I want for each interface according to its MAC
> > address.
> >
> > The file didn't exist (although the directory did) on my Beowulf
> > system, so I created one with the appropriate contents, and I now get
> > messages while the kernel is booting:
> >
> > udevd[441]: Error changing net interface name eth2 to eth0: File exists
> > udevd[441]: could not rename interface '4' from 'eth2' to 'eth0': File
> > exists
> > udevd[438]: Error changing net interface name eth1 to eth2: File exists
> > udevd[438]: could not rename interface '3' from 'eth1' to 'eth2': File
> > exists
> > udevd[445]: Error changing net interface name eth0 to eth1: File exists
> > udevd[445]: could not rename interface '2' from 'eth0' to 'eth1': File
> > exists
> > I _have_ tried adding "net.ifnames=0" to the kernel boot line; this
> > makes no difference.
> Hi,
> You can:
>
> 1) delete the persistent net names file and get the interfaces with
> old style names but eventually reordered (with net.ifnames=0).
I do not have a problem with the style of the names.
I am getting eth0 and eth1 on my PCI card and eth2 on the motherboard.
I want eth0 on the motherboard and eth1 and eth2 on the PCI card.
> 2) use a new net persistent names file using mac address or pci bus (use
> lspci to get it):
>
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="00:00:00:00:00:ea", ATTR{type}=="1", KERNEL=="?*",
> NAME:="eth0"
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="00:00:00:00:00:eb", ATTR{type}=="1", KERNEL=="?*",
> NAME:="eth1"
Sorry, how is that different from what I already did above?
Regards,
Antony.
--
I lay awake all night wondering where the sun went, and then it dawned on me.
Please reply to the list;
please *don't* CC me.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On Sat, 12 Dec 2020 14:15:53 +0100
Antony Stone wrote:
> Hi.
>
> I've just installed a couple of Beowulf systems, each of which has
> three ethernet interfaces; one on the motherboard, and two on a PCI
> card.
>
> I'm trying to work out how to give those interfaces the names I want;
> the motherboard as eth0, and the PCI card as eth1 / eth2.
>
> Historically, I've been used to udev
> and /etc/udev/rules.d/70-persistent- net.rules doing this, where I
> can specify the name I want for each interface according to its MAC
> address.
>
> The file didn't exist (although the directory did) on my Beowulf
> system, so I created one with the appropriate contents, and I now get
> messages while the kernel is booting:
>
> udevd[441]: Error changing net interface name eth2 to eth0: File
> exists udevd[441]: could not rename interface '4' from 'eth2' to
> 'eth0': File exists udevd[438]: Error changing net interface name
> eth1 to eth2: File exists udevd[438]: could not rename interface '3'
> from 'eth1' to 'eth2': File exists udevd[445]: Error changing net
> interface name eth0 to eth1: File exists udevd[445]: could not rename
> interface '2' from 'eth0' to 'eth1': File exists
>
> I've followed the entire thread on this list from July 2018 about
> this, which I've found _some_ of in the archives at
> https://lists.dyne.org/lurker/message/20180715.200323.7a2473a2.en.html
> however that link shows only a very small proportion of the emails in
> the discussion for some reason (I have my own local copy in my mail
> client).
>
> According to https://wiki.debian.org/NetworkInterfaceNames the old 70-
> persistent-net.rules system _should_ still work in Buster / Beowulf,
> but I can't work out how to get it to do so.
>
> I _have_ tried adding "net.ifnames=0" to the kernel boot line; this
> makes no difference.
>
> So:
>
> 1. how can I get 70-persistent-net.rules to carry on working under
> Beowulf?
>
> 2. what's the "correct" way to get my interfaces named the way I
> want, according to their MAC addresses, under Beowulf?
>
> (The above Debian wiki document indicates that Buster is the last
> release which will continue to support this, so I'm assuming I'll
> need to do something else for Chimaera; what is it?)
>
>
> Thanks,
>
>
> Antony.
>
Hi,
You can:
1) delete the persistent net names file and get the interfaces with
old style names but eventually reordered (with net.ifnames=0).
2) use a new net persistent names file using mac address or pci bus (use lspci
to get it):
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:00:00:00:00:ea", ATTR{type}=="1", KERNEL=="?*", NAME:="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:00:00:00:00:eb", ATTR{type}=="1", KERNEL=="?*", NAME:="eth1"
or
SUBSYSTEM=="net", ACTION=="add", KERNELS==":01:00.0", NAME:="eth0"
SUBSYSTEM=="net", ACTION=="add", KERNELS==":01:00.1", NAME:="eth1"
Ciao,
Tito
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On Saturday 12 December 2020 at 15:27:08, d...@d404.nl wrote:
> On 12-12-2020 14:15, Antony Stone wrote:
> >
> > According to https://wiki.debian.org/NetworkInterfaceNames the old 70-
> > persistent-net.rules system _should_ still work in Buster / Beowulf, but
> > I can't work out how to get it to do so.
>
> From what I understand after some research you need an additional
>
> /etc/udev/rules.d/10-network.rules as follows:
> SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:00:01", NAME="eth0"
> SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:00:02", NAME="eth1"
> SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:20:01", NAME="eth2"
Thanks, but no - it makes no difference.
I tried:
1. Adding that file and keeping 70-persistent-net.rules as well
2. Adding that file and removing 70-persistent-net.rules
3. Both the above both with and without net.ifnames=0 in the kernel boot
parameters.
In every case I continue to get eth0 and eth1 as my PCI card, and the
motherboard interface as eth2.
Anyone else got any useful ideas?
Antony.
--
"Linux is going to be part of the future. It's going to be like Unix was."
- Peter Moore, Asia-Pacific general manager, Microsoft
Please reply to the list;
please *don't* CC me.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ethernet names revisited
On 12-12-2020 14:15, Antony Stone wrote:
> Hi.
>
> I've just installed a couple of Beowulf systems, each of which has three
> ethernet interfaces; one on the motherboard, and two on a PCI card.
>
> I'm trying to work out how to give those interfaces the names I want; the
> motherboard as eth0, and the PCI card as eth1 / eth2.
>
> Historically, I've been used to udev and /etc/udev/rules.d/70-persistent-
> net.rules doing this, where I can specify the name I want for each interface
> according to its MAC address.
>
> The file didn't exist (although the directory did) on my Beowulf system, so I
> created one with the appropriate contents, and I now get messages while the
> kernel is booting:
>
> udevd[441]: Error changing net interface name eth2 to eth0: File exists
> udevd[441]: could not rename interface '4' from 'eth2' to 'eth0': File exists
> udevd[438]: Error changing net interface name eth1 to eth2: File exists
> udevd[438]: could not rename interface '3' from 'eth1' to 'eth2': File exists
> udevd[445]: Error changing net interface name eth0 to eth1: File exists
> udevd[445]: could not rename interface '2' from 'eth0' to 'eth1': File exists
>
> I've followed the entire thread on this list from July 2018 about this, which
> I've found _some_ of in the archives at
> https://lists.dyne.org/lurker/message/20180715.200323.7a2473a2.en.html
> however
> that link shows only a very small proportion of the emails in the discussion
> for some reason (I have my own local copy in my mail client).
>
> According to https://wiki.debian.org/NetworkInterfaceNames the old 70-
> persistent-net.rules system _should_ still work in Buster / Beowulf, but I
> can't work out how to get it to do so.
>
> I _have_ tried adding "net.ifnames=0" to the kernel boot line; this makes no
> difference.
>
> So:
>
> 1. how can I get 70-persistent-net.rules to carry on working under Beowulf?
>
> 2. what's the "correct" way to get my interfaces named the way I want,
> according to their MAC addresses, under Beowulf?
>
> (The above Debian wiki document indicates that Buster is the last release
> which will continue to support this, so I'm assuming I'll need to do
> something
> else for Chimaera; what is it?)
>
>
> Thanks,
>
>
> Antony.
>
From what I understand after some research you need a additional
/etc/udev/rules.d/10-network.rules as follow:
|SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:00:01", NAME="eth0"
SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:00:02", NAME="eth1"|
||SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:20:01", NAME="eth2" Hope
this helps. Grtz Nick | |
signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Ethernet names revisited
Hi. I've just installed a couple of Beowulf systems, each of which has three ethernet interfaces; one on the motherboard, and two on a PCI card. I'm trying to work out how to give those interfaces the names I want; the motherboard as eth0, and the PCI card as eth1 / eth2. Historically, I've been used to udev and /etc/udev/rules.d/70-persistent- net.rules doing this, where I can specify the name I want for each interface according to its MAC address. The file didn't exist (although the directory did) on my Beowulf system, so I created one with the appropriate contents, and I now get messages while the kernel is booting: udevd[441]: Error changing net interface name eth2 to eth0: File exists udevd[441]: could not rename interface '4' from 'eth2' to 'eth0': File exists udevd[438]: Error changing net interface name eth1 to eth2: File exists udevd[438]: could not rename interface '3' from 'eth1' to 'eth2': File exists udevd[445]: Error changing net interface name eth0 to eth1: File exists udevd[445]: could not rename interface '2' from 'eth0' to 'eth1': File exists I've followed the entire thread on this list from July 2018 about this, which I've found _some_ of in the archives at https://lists.dyne.org/lurker/message/20180715.200323.7a2473a2.en.html however that link shows only a very small proportion of the emails in the discussion for some reason (I have my own local copy in my mail client). According to https://wiki.debian.org/NetworkInterfaceNames the old 70- persistent-net.rules system _should_ still work in Buster / Beowulf, but I can't work out how to get it to do so. I _have_ tried adding "net.ifnames=0" to the kernel boot line; this makes no difference. So: 1. how can I get 70-persistent-net.rules to carry on working under Beowulf? 2. what's the "correct" way to get my interfaces named the way I want, according to their MAC addresses, under Beowulf? (The above Debian wiki document indicates that Buster is the last release which will continue to support this, so I'm assuming I'll need to do something else for Chimaera; what is it?) Thanks, Antony. -- Numerous psychological studies over the years have demonstrated that the majority of people genuinely believe they are not like the majority of people. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
