Bug 116651 - firstboot prints obnoxious and incorrect message at boot time
Summary: firstboot prints obnoxious and incorrect message at boot time
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot   
(Show other bugs)
Version: rawhide
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
Depends On:
Blocks: FC2Target
TreeView+ depends on / blocked
Reported: 2004-02-24 08:07 UTC by Alexandre Oliva
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-03-08 21:13:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Alexandre Oliva 2004-02-24 08:07:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040217

Description of problem:
After a kickstart install, firstboot prints on the first boot:

Firstboot has already been run once on this system.
In order to run firstboot from the command line, run the following
1) rm /etc/sysconfig/firstboot
2) /usr/sbin/firstboot
In order to run firstboot during system bootup, run the following
1) rm /etc/sysconfig/firstboot
2) chkconfig --level 5 firstboot on
3) reboot
                                                           [  OK  ]

Since this is right before rhgb completes, it's very difficult to tell
what the message says; I was worried it was some serious error message
the first few boots.  Then, when I finally managed to read it by
booting without rhgb, I realized it was a lie, since I'd never run
firstboot on that system, as it doesn't run with kickstart installs.

I understand the point of the message, but it's not a good idea to
print such a long message in every boot other than the first.  I'd
much prefer firstboot to be silent during boot.  Can it perhaps test
$2 = boot or something like that, like some network start scripts do?

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Do a kickstart install
2.Watch rhgb during the boot

Actual Results:  rhgb always switches to detail mode for me (I'm not
sure that's by design), so I always see this ugly message.

Expected Results:  I'd rather not.

Additional info:

Comment 1 Brent Fox 2004-03-08 21:13:56 UTC
I've nuked the print statements since they seem like more trouble than
they are worth.  I've also modified it so that if firstboot sees that
/etc/sysconfig/firstboot exists, it will turn off it's initscript so
that all subsequent boots will not try to start it at all.

Should be fixed in firstboot-1.3.7-1.  Thanks for your report.

Comment 2 Alexandre Oliva 2004-03-19 03:56:05 UTC
Confirmed, thanks!

Note You need to log in before you can comment on or make changes to this bug.