We don't have a drakx-net maintainer, yet

Last time you did a network install (Mageia 1 rc or Mageia 1), did it still not work the way you wanted?

CC: (none) => m.van.waes

Yes, "Assign hostname" never comes up checked.

I don't think this is a drakx-net issue.  It requires install stage 1 to "remember" that a hostname was returned, and the part of stage 2 that creates the initial ifcfg (which may be drakx-net) to set NEEDHOSTNAME based on the saved boolean.

CC: (none) => ftg

(In reply to comment #2)
> Yes, "Assign hostname" never comes up checked.
> 
> I don't think this is a drakx-net issue.  It requires install stage 1 to
> "remember" that a hostname was returned, and the part of stage 2 that creates
> the initial ifcfg (which may be drakx-net) to set NEEDHOSTNAME based on the
> saved boolean.

@ Thierry: WDYT?

I think you'd better ask blino which was the maintainer for both drakx-net and stage1

CC: (none) => mageia

(In reply to comment #3)
> (In reply to comment #2)
> > Yes, "Assign hostname" never comes up checked.
> > 
> > I don't think this is a drakx-net issue.  It requires install stage 1 to
> > "remember" that a hostname was returned, and the part of stage 2 that creates
> > the initial ifcfg (which may be drakx-net) to set NEEDHOSTNAME based on the
> > saved boolean.
> 
> @ Thierry: WDYT?

(In reply to comment #4)
> I think you'd better ask blino which was the maintainer for both drakx-net and
> stage1

@ Blino:

Is this a stage 1 issue?

Created attachment 1696 [details]
Blino, any reason not to apply this patch?

Hostname isn't given since dchaumette made it so on Jan 31 2003:
    "don't save hostname if intf->boot_proto == BOOTPROTO_DHCP"

(In reply to comment #7)
> Hostname isn't given since dchaumette made it so on Jan 31 2003:
>     "don't save hostname if intf->boot_proto == BOOTPROTO_DHCP"

I get the idea of that test, but it's flawed for two reasons.  First, if you're looking to disqualify automatically generated DHCP hostnames, it should only discard it if the name contains a reverse IP address.  Second, the checkbox in drakconnect says "Obtain hostname from DHCP (or generate one)", so the checkbox includes the auto-generated case anyway.

But I can understand not pre-checking the checkbox for an auto-generated name under the assumption that most people who install under an auto-generated DHCP hostname would probably want to set a fixed one.

Well, wait a minute.  The intent of that change was probably not to pre-set an auto-generated DHCP hostname as a fixed hostname, and that makes sense.

What needs to be remembered is that a hostname was received at all, not what it was.  Not pre-setting a fixed hostname in a DHCP environment is perfectly reasonable.  But pre-checking the "Obtain hostname" box if DHCP supplied one (subject  to the filtering test above) is the issue here.

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

If you can still reproduce it, can you attach the following files?
- /tmp/network
- /tmp/ifcfg-*
- /tmp/stage1.log
- /tmp/ddebug.log
Just wait for stage2 to show up, go to tty2, mount some USB key, ...

Keywords: (none) => NEEDINFO

Fresh install today, generated eth0 ifcfg-enp6s0 has only DEVICE, BOOTPROTO=DHCP and METRIC.  No NEEDHOST.

I'll attach the requested 4 files in a second.

Created attachment 5357 [details]
ddebug.log

Created attachment 5358 [details]
ifcfg-*

Created attachment 5359 [details]
network

Created attachment 5360 [details]
stage1.log

Hmm the unselecting might be remembered in urpmi {state} and thus prevent the later installation to actually occurs (when configuring network in summary)

This is much more current than it would seem from the header fields.

Keywords: NEEDINFO => (none)
Whiteboard: MGA2TOO => MGA2TOO, 5 alpha2

Someone knows if this applies to MGA6TOO??

CC: (none) => neoser10