How do I make Anaconda ask for hostname?

PryGuy · #1 16th December 2010, 06:50 PM

Good day everyone!
I build a Fedora server install (not live!) CD that uses a kickstart for an automated install. The question is, is it possible to make Anaconda ask for a hostname during the install?

Thanks in advance!

AndrewSerk · #2 16th December 2010, 08:14 PM

Hello,
This is just a guess but, have you tried something like this in the %post section:

Code:

cat >> /etc/network << FOE
NETWORKING=yes
HOSTNAME=$host.$domain
FOE

PryGuy · #3 17th December 2010, 05:52 AM

$host.$domain are variables hard coded by me? That's not what I want to. I want Anaconda to ask for it, like it does during the ordinary install.

AndrewSerk · #4 17th December 2010, 01:05 PM

yep, I miss read your post and gave a bad answer since the proper way to set a hostname in a ks is with the --hostname= directive.

I wonder if you use the asknetwork directive if it asks for hostname

asknetwork
Prompt for network configuration in the first stage of installation regardless of installation method.

I bet the info is here somewhere: http://fedoraproject.org/wiki/Category:Anaconda

PryGuy · #5 17th December 2010, 05:27 PM

It asks for network settings, not a hostname...

Thanks for this tip though.

AndrewSerk · #6 17th December 2010, 05:52 PM

There should be a way to make Anaconda ask for a hostname during a ks install instead of setting it in the ks, but I can't seem to find the way. The only other option I know of is to use the interactive directive. Not really what you want but may give you the option to set/change hostname.

interactive (optional)
Uses the information provided in the kickstart file during the installation, but allow for inspection and modification of the values given. You are presented with each screen of the installation program with the values from the kickstart file. Either accept the values by clicking Next or change the values and click Next to continue. Refer to the autostep command.

PryGuy · #7 17th December 2010, 05:59 PM

Yes, you are right. I've filled a bug. There seems to be a fix for RHEL.

PryGuy · #8 18th December 2010, 02:10 PM

AndrewSerk, just read the comments to the bug I filled. I wonder why Fedora team does this?

---------- Post added at 05:10 PM ---------- Previous post was at 05:10 PM ----------

'interactive' didn't work for me

AndrewSerk · #9 18th December 2010, 03:42 PM

Quote:

Originally Posted by PryGuy

interactive' didn't work for me

Have you tried to set a hostname in your ks and use the interactiive directive. I was hopping that if the hostname was set in the ks file that the interactive directive would give you a chance to change/modify it.

Dang test-bed distro's! You never know what you will get.

PryGuy · #10 18th December 2010, 03:55 PM

The 'nteractive' option didn't work for me at all. I have a feeling they've removed it. It's pity to see how they ruin this great distro. I really see no logic in the Chris Lemens' (the guy who answered me on bugzilla) words. That's probably 'cause they are devs and we are admins. They are certain us admins always have ability (right, resources) to install DHCP servers and stuff and perform rollouts the way they want us to.

That's not freedom if you ask me, that's inflexibility.

AndrewSerk · #11 18th December 2010, 04:30 PM

Make sure you don't have the autostep directive in your ks as that might keep interactive from working
The interactive directive is still in the kickstart options of f14's documentation. http://docs.fedoraproject.org/en-US/...2-options.html

Fedora is locking us out of more and more setting every release in a attempt to make it more user friendly for noobs.

I am looking forward to the day the Centos Devs finish 6.

PryGuy · #12 19th December 2010, 04:14 PM

No, I didn't use the autostep option. Should I just put 'interactive' in the ks file like I used to do?

---------- Post added at 07:14 PM ---------- Previous post was at 03:22 PM ----------

Okay, Chris said:

Quote:

Interactive kickstart installs have been deprecated, given this and other
similar difficulties. Note that this only applies to use of the "interactive"
command. Omitting information from a kickstart file will still cause anaconda
to stop and prompt for it.

Pay attention to last sentence. How does it fit with the things he said about my problem?

AndrewSerk · #13 19th December 2010, 04:23 PM

Quote:

Originally Posted by PryGuy

No, I didn't use the autostep option. Should I just put 'interactive' in the ks file like I used to do?

---------- Post added at 07:14 PM ---------- Previous post was at 03:22 PM ----------

Okay, Chris said: Pay attention to last sentence. How does it fit with the things he said about my problem?

So what use ;
network --bootproto= --ip= --netmask= --gateway= --nameserver= --hostname=

leaving everything blank to cause it to ask? I guess you will have to do some testing to figure out how/if this is going to work. Let us know if you get it figured out.

PryGuy · #14 19th December 2010, 04:40 PM

Quote:

Originally Posted by AndrewSerk

So what use ;
network --bootproto= --ip= --netmask= --gateway= --nameserver= --hostname=

leaving everything blank to cause it to ask? I guess you will have to do some testing to figure out how/if this is going to work. Let us know if you get it figured out.

I think I've tried putting it with --hostname alone (network --dootproto=dhcp --hostname=). Didn't work.

According to Chris:
1. Interactive option doesn't work anymore (though it's still present in the F14's manual)
2. Anaconda should stop and ask if there's not enough information. So, according to Chris, my bug is a bug, though he denies it.

AndrewSerk · #15 19th December 2010, 04:50 PM

Andrew kicks at the ground, his dog takes off running, while Andrew throws his hands up in the air and mumbles something incomprehensible about devs, progress, and steps backwards.