Bug 235005 - yaboot.conf needs quotes in init-message entry
Summary: yaboot.conf needs quotes in init-message entry
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: booty
Version: rawhide
Hardware: powerpc
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-04-03 08:03 UTC by Robert Allerstorfer
Modified: 2008-03-31 14:58 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-03-31 14:58:07 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Robert Allerstorfer 2007-04-03 08:03:59 UTC 
Description of problem:

Shipped "/etc/yaboot.conf" misses quotes in init-message entry

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

all so far released, including those coming with FC5, FC6, ...

How reproducible:

always

Steps to Reproduce:
1. Boot your ppc based computer into Linux (by pressing "l" at the first yaboot
prompt)
2. Watch the first lines on the new screen
  
Actual results:

Welcome

Expected results:

Welcome to Fedora Core!
Hit <TAB> for boot options

Additional info:

To solve this bug, "/etc/yaboot.conf" has to be changed:

currently (not correct):
init-message=Welcome to Fedora Core!\nHit <TAB> for boot options

properly:
init-message="Welcome to Fedora Core!\nHit <TAB> for boot options"
Comment 1 Red Hat Bugzilla 2007-08-21 05:32:56 UTC 
User pnasrat's account has been closed
Comment 2 Roman Rakus 2008-03-26 14:10:54 UTC 
FC5 and FC6 are EOL. Is still problem in FC-7 and above?
Comment 3 Robert Allerstorfer 2008-03-26 14:53:12 UTC 
Yes, nothing changed since I submitted this bug one year ago.
Comment 4 Roman Rakus 2008-03-27 12:30:47 UTC 
Yes. I have take a deeper look at the problem and probably it's anaconda's
cause. Adding anaconda-maint-list to CC.
Comment 5 Chris Lumens 2008-03-31 14:58:07 UTC 
This will be fixed in the next build of booty.
Note You need to log in before you can comment on or make changes to this bug.