[DNG] obsoleting a login manager (was: What I learned at Distrowatch)

2020-12-12 Thread spiralofhope
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 >

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Steve Litt
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_

Re: [DNG] Oldstable and Archive timing expectations?

2020-12-12 Thread golinux
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

Re: [DNG] Oldstable and Archive timing expectations?

2020-12-12 Thread Adrian Zaugg
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

[DNG] Version control /etc (was Re: Ethernet names revisited)

2020-12-12 Thread Olaf Meeuwissen via Dng
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

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Ralph Ronnquist via Dng
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

Re: [DNG] What I learned at Distrowatch

2020-12-12 Thread Steve Litt
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

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Antony Stone
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. > >

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Ralph Ronnquist via Dng
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

Re: [DNG] Ethernet names revisited - a workaround (but the basic question still remains)

2020-12-12 Thread tito via Dng
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

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Antony Stone
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

Re: [DNG] Ethernet names revisited - a workaround (but the basic question still remains)

2020-12-12 Thread Antony Stone
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

Re: [DNG] Ethernet names revisited - a workaround (but the basic question still remains)

2020-12-12 Thread Florian Zieboll via Dng
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

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Ralph Ronnquist via Dng
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.

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Antony Stone
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

Re: [DNG] Ethernet names revisited - a workaround (but the basic question still remains)

2020-12-12 Thread Antony Stone
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

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Ralph Ronnquist via Dng
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

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Hendrik Boom
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 >

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Antony Stone
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

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Didier Kryn
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

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Antony Stone
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

Re: [DNG] Ethernet names revisited

2020-12-12 Thread tito via Dng
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

Re: [DNG] Ethernet names revisited

2020-12-12 Thread Antony Stone
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

Re: [DNG] Ethernet names revisited

2020-12-12 Thread d...@d404.nl
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,

[DNG] Ethernet names revisited

2020-12-12 Thread Antony Stone
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