SCIENTIFIC-LINUX-USERS Archives

May 2006

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Connie Sieh <[log in to unmask]>
Reply To:
Connie Sieh <[log in to unmask]>
Date:
Thu, 11 May 2006 16:21:11 -0500
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (31 lines)
On Thu, 11 May 2006, John Rowe wrote:

> > > 
> > > The fix in our case was to download and compile up Lilo as an RPM.
> > > Include this in your install media (NFS share).
> > > Then at the end of the install process, in the post-install script
> > > rpm install lilo, create a good /etc/lilo.conf
> > > and run lilo.
> > > 
> > > 
> > > You won't find an 'official' Lilo anywhere for the Upstream Vendor's
> > > release. Well worth rolling your own if you come across this problem.
> > > Lilo almost always works.
> 
> Although it's immensly confusing it's an easy one-off fix and for me
> grub has always worked flawlessly after that. The beauty of yum is that
> it reads the file-system so you only need to install it once.
> 
> Is yum on the rescue image BTW? I seem to remember having to get it from
> the 'installed' system. 

I suspect no, but a really good idea.  So will research putting it on.  
Note that if you have a "installed" partition you could always "chroot" to 
it and run the yum that is overthere.

> 
> John
> 

-Connie Sieh

ATOM RSS1 RSS2