Every time I reboot, the splash screen that covers up the details has a moment when it displays "first boot startup" or something similar to that. My understanding of "first boot" is that it happens once just after install, not on every boot. If that is correct, then that segment of the startup is mislabeled.
Gerry
On Mon, 2006-02-27 at 22:58, Gerry Tool wrote:
Every time I reboot, the splash screen that covers up the details has a moment when it displays "first boot startup" or something similar to that. My understanding of "first boot" is that it happens once just after install, not on every boot. If that is correct, then that segment of the startup is mislabeled.
Nope, that is supposed to work that way. When the firstboot service starts it looks to see if it is the first boot, if so it asks those initial questions otherwise it does nothing.
I do wonder why it doesn't do a chkconfig firstboot off after it gets through running.
I do wonder why it doesn't do a chkconfig firstboot off after it gets through running.
Because I modified it to no longer do that. The problem here is that we have a variety of weird corner cases where firstboot is unable to run, but will try again a second time anyway. This comes up when X has problems and you change runlevels to fix it, for instance. In that case, the quick way to prevent firstboot from running again is to create a lock file and make it check to see if it's already "running".
- Chris
On Tue, 2006-02-28 at 15:21, Chris Lumens wrote:
Because I modified it to no longer do that. The problem here is that we have a variety of weird corner cases where firstboot is unable to run, but will try again a second time anyway. This comes up when X has problems and you change runlevels to fix it, for instance. In that case, the quick way to prevent firstboot from running again is to create a lock file and make it check to see if it's already "running".
Been there, done that. But when you click that last done button at the end of firstboot it is pretty safe to assume you really are done with it and at that point it could safely switch off the service. Sure it doesn't gain a lot on boot time but it would be one less thing to do every boot thereafter.
On Tue, 2006-02-28 at 22:39 -0600, John Morris wrote:
Been there, done that. But when you click that last done button at the end of firstboot it is pretty safe to assume you really are done with it and at that point it could safely switch off the service. Sure it doesn't gain a lot on boot time but it would be one less thing to do every boot thereafter.
They can also manually edit /etc/sysconfig/firstboot and change the setting to "no".
On 01.03.2006 09:21, Mike Chambers wrote:
On Tue, 2006-02-28 at 22:39 -0600, John Morris wrote:
Been there, done that. But when you click that last done button at the end of firstboot it is pretty safe to assume you really are done with it and at that point it could safely switch off the service. Sure it doesn't gain a lot on boot time but it would be one less thing to do every boot thereafter.
They can also manually edit /etc/sysconfig/firstboot and change the setting to "no".
it is called "firstboot" and not "everyboot" if firstboot is succesfully done at one time it should be off.
On Wed, 2006-03-01 at 09:53 +0100, shrek-m@gmx.de wrote:
On 01.03.2006 09:21, Mike Chambers wrote:
On Tue, 2006-02-28 at 22:39 -0600, John Morris wrote:
Been there, done that. But when you click that last done button at the end of firstboot it is pretty safe to assume you really are done with it and at that point it could safely switch off the service. Sure it doesn't gain a lot on boot time but it would be one less thing to do every boot thereafter.
They can also manually edit /etc/sysconfig/firstboot and change the setting to "no".
it is called "firstboot" and not "everyboot" if firstboot is succesfully done at one time it should be off.
I agree. When firstboot finishes successfully it should automatically turn itself off somehow - either as the service, or as the configuration file change.
-- shrek-m