On Tue, Jan 30, 2024, at 11:11, Tomasz Torcz wrote:
> On Tue, Jan 30, 2024 at 10:58:19AM -0600, Major Hayden wrote:
> I'm curious, why not systemd-networkd? It's mentioned once in
> the bug, but there's not explanation about the choice later.
That might be possible, but upstream cloud-init only
On Tue, Jan 30, 2024 at 10:58:19AM -0600, Major Hayden wrote:
> Hey there,
>
> For those of you who use Fedora often on public cloud providers where
> cloud-init handles the initial configuration, there's a change coming for
> the very early DHCP request during the boot. ☁️
>
> [0]
On Wed, 7 Feb 2024 at 09:25, Major Hayden wrote:
> On 2/7/24 07:36, Petr Menšík wrote:
> > I am interested why two DHCP clients are required inside a single tool.
> > Why it could not use NetworkManager in both times, but with some
> > different settings? Maybe alternative service? If there is
On 2/7/24 07:36, Petr Menšík wrote:
I am interested why two DHCP clients are required inside a single tool.
Why it could not use NetworkManager in both times, but with some
different settings? Maybe alternative service? If there is missing
ability to change behaviour, it may make sense to fix
I am dhcpcd maintainer and okay, dhcpcd is not bad choice. But its
maintenance might fall into our team in RHEL.
I am interested why two DHCP clients are required inside a single tool.
Why it could not use NetworkManager in both times, but with some
different settings? Maybe alternative
Once upon a time, Stephen Gallagher said:
> On Tue, Feb 6, 2024 at 3:30 PM Chris Adams wrote:
> > Once upon a time, Major Hayden said:
> > > Stephen Gallagher pointed out that ELN doesn't have busybox, but it does
> > > have dhcpcd, and that should work fine. I've reverted the switch to
> > >
On Tue, Feb 6, 2024 at 3:30 PM Chris Adams wrote:
>
> Once upon a time, Major Hayden said:
> > Stephen Gallagher pointed out that ELN doesn't have busybox, but it does
> > have dhcpcd, and that should work fine. I've reverted the switch to udhcpcd
> > and I'm waiting on upstream cloud-init to
Once upon a time, Major Hayden said:
> Stephen Gallagher pointed out that ELN doesn't have busybox, but it does have
> dhcpcd, and that should work fine. I've reverted the switch to udhcpcd and
> I'm waiting on upstream cloud-init to have a new release with the recently
> added dhcpcd support.
On Tue, Feb 6, 2024, at 13:56, Petr Menšík wrote:
> I think this is stupid anyway. Why does cloud-init need 2 separate DHCP
> clients anyway? Can we gather what exactly they use it for and why
> alternative dhcp client is required?
It looks like a small, basic, DHCP client is needed during the
Hello Major,
I think this is stupid anyway. Why does cloud-init need 2 separate DHCP
clients anyway? Can we gather what exactly they use it for and why
alternative dhcp client is required?
It seems to me NetworkManager should be able to use just different
configuration for "pre-connection"
Hey there,
For those of you who use Fedora often on public cloud providers where
cloud-init handles the initial configuration, there's a change coming
for the very early DHCP request during the boot. ☁️
As reported in BZ 2247055[0], the existing dhclient binary comes from
ISC's dhcp and it
11 matches
Mail list logo
