Bug 180520 - setting RUN_FIRSTBOOT=yes doesn't work
Summary: setting RUN_FIRSTBOOT=yes doesn't work
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: rawhide
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Chris Lumens
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-08 19:14 UTC by Nalin Dahyabhai
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-08 21:06:39 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Nalin Dahyabhai 2006-02-08 19:14:46 UTC 
Description of problem:
If a sysadmin decides to set firstboot to run at boot-time, and finds
/etc/sysconfig/firstboot with "RUN_FIRSTBOOT=no" as its contents, it's not
unreasonable to expect that setting "RUN_FIRSTBOOT=yes" will do the job.

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

How reproducible:
Always

Steps to Reproduce:
1. echo RUN_FIRSTBOOT=yes > /etc/sysconfig/firstboot
2. unset DISPLAY
3. /usr/sbin/firstboot --reconfig
  
Actual results:
Nothing.

Expected results:
Firstboot's TUI, in all its glory.

Additional info:
It looks like there's no "return True" statement to be called if "FIRSTBOOT=no"
isn't found and we fall out of the "for" loop.
Note You need to log in before you can comment on or make changes to this bug.