1stboot Stuff?
Will anything break if you never log into the console after the initial reboot? I just installed my first copy in a VM, and connected over SSH as I normally would for all access after the install. But I
just happened to leave the console window open and later noticed that it was prompting for license acceptance which I didn’t see in the ssh login. On a more typical install, no one will ever log in at the console after the network is up. Will that matter, and is there a way to keep it from confusing operators that might need to log in with a crash cart much later?
7 thoughts on - 1stboot Stuff?
If your typical install is via kickstart, there is a keyword
eula –agreed
Thomas
My typical install will be arranging for an operator in some other location to pop in a minimal iso, run the install, and give it an IP
address out of his range that I can reach. If SSH connects to it after the reboot, he’s done.
Nothing breaks. Nothing stops working. I do this all the time. I almost never login to a local console after the initial reboot of a newly installed system, either Fedora or CentOS.
In fact I have a post-install script that turns off the firstboot service and terminates it if it is already running – that in addition to many other customization tasks that I perform on every Linux box I install. You could then uninstall the firstboot RPM if you choose.
Thanks – if for some reason the network subsequently breaks and the remote operators have to revive it from the console I’d rather not have them think missing that step might have been the problem with the box.
Don’t remember this when installing C5 and C6. Is this an improvement for C7 ?
It is how first boot now works. Whether or not it is an improvement at all is questionable .. but it is what it is. We didn’t add it to CentOS
on purpose, its like upstream.
Thanks for the clarification, and for your much appreciated CentOS work.