From: Ben Kohler <bkohler@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH 05/10] livecdfs-update.sh: remove net.eth[1234] symlinks
Date: Wed, 29 Mar 2023 14:51:09 -0500 [thread overview]
Message-ID: <CANSUr=JuZdiDtNK7OZJtCrmg5v9qXxFV0sxMD9htuio8j0_bcg@mail.gmail.com> (raw)
In-Reply-To: <CAHhAHvg48toFP1r9A1T2Ai+qrpRukguasjLHiEPBAmXgcsm--g@mail.gmail.com>
On Wed, Mar 29, 2023 at 2:40 PM Christian Iwata Nilsson
<nikize@gmail.com> wrote:
>
> Don't know if it applies, but I always start systems (and livecds) without the (un)predictablenetworknames brokenness. So that it is always ethx and nothing else.
>
> So before removing this, I would like to ask to please ensure that scenario keeps working.
Replying from my other email address here due to firewall issues--
I'm not stopping you from using ethX interface names.
By default our livecds start a dhcpcd instance to autoconfigure any
interface with a link detected, my change won't affect that behavior.
If dhcpcd autoconfig is not suitable, our docs point you to net-setup
for manual configuration, my change won't affect that behavior either.
If you decide to go a 3rd route and use netifrc, you will need to
manually create the net.ethX link(s). Users with
default/"predictable" interface names already would have to do this.
Are you sure you're actually affected by my change?
Thanks,
Ben
next prev parent reply other threads:[~2023-03-29 19:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 19:30 [gentoo-catalyst] [PATCH 01/10] remove gamecd motd file Ben Kohler
2023-03-29 19:30 ` [gentoo-catalyst] [PATCH 02/10] reorganize motd files Ben Kohler
2023-03-29 19:30 ` [gentoo-catalyst] [PATCH 03/10] livecdfs-update.sh: remove code obsoleted by sys-apps/hwids package Ben Kohler
2023-03-29 19:30 ` [gentoo-catalyst] [PATCH 04/10] livecdfs-update.sh: remove old devfsd code Ben Kohler
2023-03-29 19:30 ` [gentoo-catalyst] [PATCH 05/10] livecdfs-update.sh: remove net.eth[1234] symlinks Ben Kohler
2023-03-29 19:40 ` Christian Iwata Nilsson
2023-03-29 19:51 ` Ben Kohler [this message]
2023-03-29 19:30 ` [gentoo-catalyst] [PATCH 06/10] livecdfs-update.sh: remove confusing "reduce tmpfs usage" hack Ben Kohler
2023-03-29 19:30 ` [gentoo-catalyst] [PATCH 07/10] livecdfs-update.sh: replace local handbook with wiki handbook Ben Kohler
2023-03-29 19:30 ` [gentoo-catalyst] [PATCH 08/10] livecdfs-update, livecd-bashrc: remove archaic X autostarting setup Ben Kohler
2023-03-29 19:30 ` [gentoo-catalyst] [PATCH 09/10] livecdfs-update: remove old evms code Ben Kohler
2023-03-29 19:31 ` [gentoo-catalyst] [PATCH 10/10] Remove obsolete universal cd target Ben Kohler
2023-03-30 12:54 ` Matt Turner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANSUr=JuZdiDtNK7OZJtCrmg5v9qXxFV0sxMD9htuio8j0_bcg@mail.gmail.com' \
--to=bkohler@gmail.com \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox