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?
On 07/11/2014 10:35 AM, Les Mikesell wrote:
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?
If your typical install is via kickstart, there is a keyword
eula --agreed
Thomas
On Fri, Jul 11, 2014 at 12:48 PM, Thomas Eriksson thomas.eriksson@slac.stanford.edu wrote:
On 07/11/2014 10:35 AM, Les Mikesell wrote:
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?
If your typical install is via kickstart, there is a keyword
eula --agreed
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.
On Fri, 2014-07-11 at 10:48 -0700, Thomas Eriksson wrote:
On 07/11/2014 10:35 AM, Les Mikesell wrote:
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.
If your typical install is via kickstart, there is a keyword
eula --agreed
Don't remember this when installing C5 and C6. Is this an improvement for C7 ?
On 07/11/2014 03:56 PM, Always Learning wrote:
On Fri, 2014-07-11 at 10:48 -0700, Thomas Eriksson wrote:
On 07/11/2014 10:35 AM, Les Mikesell wrote:
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.
If your typical install is via kickstart, there is a keyword
eula --agreed
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.
On Sat, 2014-07-12 at 09:28 -0500, Johnny Hughes wrote:
On 07/11/2014 03:56 PM, Always Learning wrote:
On Fri, 2014-07-11 at 10:48 -0700, Thomas Eriksson wrote:
On 07/11/2014 10:35 AM, Les Mikesell wrote:
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.
If your typical install is via kickstart, there is a keyword
eula --agreed
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.
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.
On 07/11/2014 01:35 PM, Les Mikesell wrote:
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?
--
David P. Both, RHCE Millennium Technology Consulting LLC 919-389-8678
dboth@millennium-technology.com
www.millennium-technology.com www.databook.bz - Home of the DataBook for Linux DataBook is a Registered Trademark of David Both
This communication may be unlawfully collected and stored by the National Security Agency (NSA) in secret. The parties to this email do not consent to the retrieving or storing of this communication and any related metadata, as well as printing, copying, re-transmitting, disseminating, or otherwise using it. If you believe you have received this communication in error, please delete it immediately.
On Fri, Jul 11, 2014 at 1:29 PM, David Both dboth@millennium-technology.com wrote:
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.
-
Always Learning -
David Both -
Johnny Hughes -
Les Mikesell -
Thomas Eriksson