pwlconfig and LILO error

[Dr Jaime V. Miro]

Hi Ralph,

Thanks for the info. The reason for the error was, as suggested, not being able to locate lilo because I don't have /sbin on the PATH. However, setting PLILO did not help. I had to actually add it to the PATH env. variable to get it to work - I never bother doing that b4, pure laziness, always using /sbin/lilo when I was messing around with lilo :-)

With regards to other points of conflict, here is my experience in case it helps:

a) rc.sysinit not executable, but that has been raised b4 in the list. Nothing new there.

b) when the filesystem for the current project is extracted, I always get a tar error when ncurses.tar is untarred:
...
..
.
ncurses.tar   project_name/ncurses.list
tar:usr/bin/clear:Could not create file:File exists
tar:error exit delayed from previous errors
.
..
...

The file system is however untarred, and I can see the files I have selected from ncurses.tar in my root file system. It has also happened b4 that libncurses.so.X (in ncurses.tar) has not been untarred despite being selected, and I seem to remember (not sure though) being unable to log in (got the login/pwd prompt, but after properly typing the admin/admin or root/redhat login/pwd, it would give me the login prompt again :-o). Extracting the system again would not make a difference. I first
copied my own version of libncurses.so.4 from my dev. machine, and it worked. Then, I deleted the whole project filesystem, extracted it all again, and then extracted libncurses.so.X ok (also giving me the above mentioned error, though). And it all went fine after.

I'll keep you posted with my experiences. Thanks again,

Jaime



 	 

Ralph Stickley wrote:
> 
> Dr. Miro,
> Looks like the path thing is getting us here.  lilo doesn't show up
> on a standard path (which lilo says "no lilo in...")
> 
> The fix is to properly define the PLILO variable.
> 
> Use the standard version (RH path):
> PLILO="/sbin/lilo"
> 
> -- or the copy provided in the bin directory --
> PLILO="$baseprj/bin/lilo"
> 
> -- but not ---
> PLILO="lilo"  # oops doesn't work :(
> 
> This was setup originally to use the patched lilo from M-Systems
> which I am personally no longer using.  To finish the job, a default
> assigning the variable PLILO to a user specified location should be
> added.
> 
> Sorry for the confusion. Let me know if anything else doesn't quite
> work as expected.
> Thanks,
> Ralph
> 
> --- "Dr Jaime V. Miro" <j.v.miro@h2eye.com> wrote:
> > Hi,
> >
> > I've been playing aroung with PWL051 lately to get embedded linux into a CF.
> > I got the grips of it now, and I can make a linux system. If I make a ram
> > image of the fs, and flash it into the CF (an IDE on hdc1) with rd_dialog, it
> > works fine. However, if I want to install the fully fledged file system (not
> > ramdisk) into the flash with the help of the "Insatall LInux LOader (LILO) to
> > flash disk" option in pwlconfig, it comes back with the error: "Lilo not
> > found : lilo". And consequently the flash
> > does not boot since the images are not there. I know lilo, as a binary is
> > there, along with the rest of the packages (in RPM and tar).
> >
> > Any hints?
> >
> > Ta.
> >
> > Jaime
> >
> > ---------------------------------------------------
> > See the list archives at http://adis.on.ca/archives/
> > See the PWL homepage at  http://peeweelinux.com
> > ---------------------------------------------------
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
> http://photos.yahoo.com/
> ---------------------------------------------------
> See the list archives at http://adis.on.ca/archives/
> See the PWL homepage at  http://peeweelinux.com
> ---------------------------------------------------

---------------------------------------------------
See the list archives at http://adis.on.ca/archives/
See the PWL homepage at  http://peeweelinux.com
---------------------------------------------------