[gobolinux-users] New startup problem

Tom Connell gobolinux at tjconnell.co.uk
Mon Apr 16 23:06:03 UTC 2007


On 16/04/07, Nick Matteo <kundor at kundor.org> wrote:
>
> On 4/16/07, Tom Connell <Gobolinux at tjconnell.co.uk> wrote:
> > Hi,
> >
> > I was recommended by Lucas to track down my Udev startup errors to
> > change the theme from ProgressII to one which permitted
> > more lines of output to show!
> >
> > So I edited /System/Settings/BootOptions using Kedit to change the theme
> > to one of the others (I chose split level) and save the file and
> rebooted!
>
> I would have chosen "Slack".  It does the most output with the least
> nonsense.


OK, But I didnt know I just selected one at random

> It booted OK to runlevel2 then I got a stack of errors about a missing
> > command ThemeBefore and nothing
>
> That's unusual.  Just editing BootOptions has always worked for me,
> but I've also never tried "split level" or whatever.  If you put in
> the name wrong, or a theme that's not installed, you might get that
> sort of error.


All I did was to comment the line showing ProgressII and uncoment the line
for the one I chose! Maybe the commented list in BootOptions doesnt actualy
match thos available??

> [...]
> > a) How do I restore the link in /System/Variables back to where it
> > should have been pointing?
>
> What link in /System/Variable ?


The BootOptions file is in /System/Variable, but it is a symlink  pointing
somewhere else! I edited it and then tried to back it out and realised it
was a link just before I overwrote it with the text!  I need to know the
Actual location of BootOptions so that I can edit that file and then restore
the link in /System/Variable

> b) What is the correct technique for changing the theme, editing
> > BootOptions on its own is clearly not sufficient!
>
> It's always worked for me, but you don't even need to do that,
> actually.  Just hit a key when the grub menu comes up while booting
> (to stop the automatic bootup countdown), then hit "e" to edit the
> boot entry, then append "BootTheme=Slack" to the end of the kernel
> command line (without quotes.)  That's handy for changing the theme
> for a single boot, but not changing the default.
>
> > c) Which of the themes is likely to maximise the number of lines visible
> > during that part of the boot or is it possible to disable the theme
> > completely temporarily
>
> Slack shows each command's normal and error output -- unlike Progress
> -- and doesn't do any colors or graphics or layout afaik.


OK, I will try that one Thanks

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gobolinux.org/pipermail/gobolinux-users/attachments/20070417/0b366f3f/attachment-0001.htm 


More information about the gobolinux-users mailing list