Re: [DNG] Ethernet names revisited

2020-12-13 Thread terryc
On Sun, 13 Dec 2020 10:45:56 +0100 Antony Stone wrote: > On Sunday 13 December 2020 at 09:25:24, terryc wrote: > > > Just add the line > > hwaddress mac:add:dress:in:usual:format > > > > to match eth2 & eth3 to the desired card. > > I think that's entirely the wrong way round. > >

Re: [DNG] Ethernet names revisited

2020-12-13 Thread Ralph Ronnquist via Dng
On 13/12 22:22, Antony Stone wrote: > On Sunday 13 December 2020 at 21:42:50, Simon Hobson wrote: > > > Hendrik Boom wrote: > > > 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

Re: [DNG] Ethernet names revisited

2020-12-13 Thread Antony Stone
On Sunday 13 December 2020 at 21:42:50, Simon Hobson wrote: > Hendrik Boom wrote: > > 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

Re: [DNG] Ethernet names revisited

2020-12-13 Thread Antony Stone
On Sunday 13 December 2020 at 21:13:10, d...@d404.nl wrote: > It looks like systemd again is responsible for this mess. That is unexpected for me, since I am starting from a clean installation of Devuan Beowulf - no upgrade, no crossover from Debian - just a totally new install of Devuan

Re: [DNG] Ethernet names revisited

2020-12-13 Thread Simon Hobson
Hendrik Boom wrote: > 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. Not for the OPs reason, but a long time ago I started to use

Re: [DNG] What I learned at Distrowatch

2020-12-13 Thread Didier Kryn
Le 13/12/2020 à 03:15, Steve Litt a écrit : > 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

Re: [DNG] godaddy (was Your system is not supported by certbot-auto anymore.)

2020-12-13 Thread Simon Hobson
Hendrik Boom wrote: > Know any domain registrars that don't mess with the user? You could take a look at mythic-beasts.com or portfast.net When I left my last place, I decided to move my domains away from them (as an employee I got "cost price" domains and free hosting) - knowing that the

Re: [DNG] Ethernet names revisited

2020-12-13 Thread Didier Kryn
Le 13/12/2020 à 01:09, Ralph Ronnquist via Dng a écrit : > 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

Re: [DNG] Ethernet names revisited

2020-12-13 Thread d...@d404.nl
On 13-12-2020 14:20, Antony Stone wrote: > On Sunday 13 December 2020 at 13:02:45, Florian Zieboll via Dng wrote: > >> Am 13. Dezember 2020 12:01:39 MEZ schrieb Antony Stone > : >>> Well, here's the output from "dmesg | grep eth". It shows the r8169 >>> interfaces being given names eth0, eth1

Re: [DNG] Ethernet names revisited

2020-12-13 Thread Didier Kryn
Le 13/12/2020 à 00:01, Ralph Ronnquist via Dng a écrit : > 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 >>

Re: [DNG] Oldstable and Archive timing expectations?

2020-12-13 Thread golinux
On 2020-12-13 08:39, Hendrik Boom wrote: On Sat, Dec 12, 2020 at 09:31:48PM -0600, goli...@devuan.org wrote: 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: > > > >

[DNG] Linux kernel boot causing screen to become unreadable.

2020-12-13 Thread Edward Bartolo via Dng
Dear All, After the modesetting issue stopped manifesting itself for some days, it started again, and now, it is almost happening with every system boot. As the sceen is completely unreadable with unaligned pixels, I tried the modprobe command without a display and paying attention not to make

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

2020-12-13 Thread Martin Steigerwald
Martin Steigerwald - 13.12.20, 16:07:10 CET: > Hendrik Boom - 13.12.20, 15:52:31 CET: > > On Sun, Dec 13, 2020 at 09:29:26AM +0100, Martin Steigerwald wrote: > > > I do not care about all the automatic changes by package upgrades. > > > > I care about the automatic changes by package upgrades

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

2020-12-13 Thread Martin Steigerwald
Hendrik Boom - 13.12.20, 15:52:31 CET: > On Sun, Dec 13, 2020 at 09:29:26AM +0100, Martin Steigerwald wrote: > > I do not care about all the automatic changes by package upgrades. > > I care about the automatic changes by package upgrades when they > conflict with my own. Well, dpkg warns me

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

2020-12-13 Thread Hendrik Boom
On Sun, Dec 13, 2020 at 09:29:26AM +0100, Martin Steigerwald wrote: > > I do not care about all the automatic changes by package upgrades. I care about the automatic changes by package upgrades when they conflict with my own. It would also be useful to have a tool that compares a the

Re: [DNG] Oldstable and Archive timing expectations?

2020-12-13 Thread Hendrik Boom
On Sat, Dec 12, 2020 at 09:31:48PM -0600, goli...@devuan.org wrote: > 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 > > > > > > >

Re: [DNG] Ethernet names revisited

2020-12-13 Thread Antony Stone
On Sunday 13 December 2020 at 14:25:37, tito via Dng wrote: > On Sun, 13 Dec 2020 10:45:56 +0100 Antony Stone wrote: > > > > From Ascii onwards I get the errors: > > > > udevd[441]: Error changing net interface name eth2 to eth0: File > > exists udevd[441]: could not rename interface '4' from

Re: [DNG] Ethernet names revisited

2020-12-13 Thread tito via Dng
On Sun, 13 Dec 2020 14:25:37 +0100 tito via Dng wrote: > On Sun, 13 Dec 2020 10:45:56 +0100 > Antony Stone wrote: > > > On Sunday 13 December 2020 at 09:25:24, terryc wrote: > > > > > On Sat, 12 Dec 2020 14:15:53 +0100 > > > > > > Antony Stone wrote: > > > > Hi. > > > > > > > > I've just

Re: [DNG] Ethernet names revisited

2020-12-13 Thread tito via Dng
On Sun, 13 Dec 2020 10:45:56 +0100 Antony Stone wrote: > On Sunday 13 December 2020 at 09:25:24, terryc wrote: > > > 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

Re: [DNG] Ethernet names revisited

2020-12-13 Thread Antony Stone
On Sunday 13 December 2020 at 13:02:45, Florian Zieboll via Dng wrote: > Am 13. Dezember 2020 12:01:39 MEZ schrieb Antony Stone : > > Well, here's the output from "dmesg | grep eth". It shows the r8169 > > interfaces being given names eth0, eth1 (the ones I want as eth1 and > > eth2), then the

Re: [DNG] Ethernet names revisited

2020-12-13 Thread Florian Zieboll via Dng
Am 13. Dezember 2020 12:01:39 MEZ schrieb Antony Stone : > Well, here's the output from "dmesg | grep eth". It shows the r8169 > interfaces being given names eth0, eth1 (the ones I want as eth1 and eth2), > then the tg3 interface gets called eth2 (which I want as eth0). > > At 6 seconds in,

Re: [DNG] Ethernet names revisited

2020-12-13 Thread Antony Stone
On Sunday 13 December 2020 at 11:23:21, Florian Zieboll via Dng wrote: > Am 13. Dezember 2020 10:45:56 MEZ schrieb Antony Stone: > > From Ascii onwards I get the errors: > > > > udevd[441]: Error changing net interface name eth2 to eth0: File exists > > udevd[441]: could not rename interface '4'

Re: [DNG] Ethernet names revisited

2020-12-13 Thread Florian Zieboll via Dng
Am 13. Dezember 2020 10:45:56 MEZ schrieb Antony Stone : > From Ascii onwards I get the errors: > > 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 > > and so on. Does the bootlog give a

Re: [DNG] Ethernet names revisited

2020-12-13 Thread Antony Stone
On Sunday 13 December 2020 at 09:25:24, terryc wrote: > 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

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

2020-12-13 Thread Martin Steigerwald
Martin Steigerwald - 13.12.20, 09:29:26 CET: > The history on this laptop dates back till May 2011. And I have older > machines where I used it. It may be that for this laptop I just cloned > the bzr branch of the older laptop, then did a diff to see which > files to adapt and continued with the

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

2020-12-13 Thread Martin Steigerwald
Olaf Meeuwissen via Dng - 13.12.20, 03:48:23 CET: > 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

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

2020-12-13 Thread Dimitris T. via Dng
Olaf Meeuwissen via Dng wrote: > > Have a look at etckeeper. > was using it for years, but not anymore.. too much disk i/o, too many files, `git gc` never ran (only by hand), and it never really came handy during those years... maybe storing etckeeper repo it in a different backup disk makes

Re: [DNG] Ethernet names revisited

2020-12-13 Thread terryc
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