[RULE] Re: Install Report (slinky 3.95 with Red Hat variant)

[Raymundo Q. Baquirin]

Hi, Michael, Jason and all,

On Tuesday 08 July 2003 00:27, rule-list-request at nongnu.org wrote:
> Send Rule-list mailing list submissions to
>       rule-list at nongnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>       
> or, via email, send a message with subject or body 'help' to
>       rule-list-request at nongnu.org
>
> You can reach the person managing the list at
>       rule-list-owner at nongnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Rule-list digest..."
>
>
> Today's Topics:
>
>    1. Re: Re: Install Report (slinky 3.95 with Red Hat variant)
>        (Michael Fratoni)
>    2. Re: Install Report (slinky 3.95 with Red Hat variant)
>        (Jason Bechtel)
>
>
> ----------------------------------------------------------------------
>
> Date: Sun, 6 Jul 2003 14:47:14 -0400
> From: Michael Fratoni <mfratoni at tuxfan.homeip.net>
> To: The main mailing list of the RULE project <rule-list at nongnu.org>
> Subject: Re: [RULE] Re: Install Report (slinky 3.95 with Red Hat variant)
> Message-ID: <200307061447.16130.mfratoni at tuxfan.homeip.net>
> In-Reply-To: <200307040828.07674.rayb at apc.edu.ph>
> References: <E19Y6bR-0000Qy-BZ at monty-python.gnu.org>
>       <200307040828.07674.rayb at apc.edu.ph>
> Content-Type: text/plain;
>   charset="iso-8859-1"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 8bit
> Precedence: list
> Reply-To: The main mailing list of the RULE project <rule-list at nongnu.org>
> Message: 1
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thursday 03 July 2003 08:28 pm, Raymundo Q. Baquirin wrote:
> > > The install log (attached) still shows a bunch of errors so I still
> > > have to see if the system is usable.
> >
> > He, forgot to attach the install log.  Here it is.
>
> I'd guess the packages listed with errors were not found/installed.
> Since one is glibc-common, and another is the kernel, I wouldn't expect
> the system to boot.
>
> - --
> - -Michael
That's true, but since the slinky install kernel is on my windows partition, I 
can use loadlin to boot into the installed system, provided the root file 
system is usable.

I did that, then I tried to install a kernel.  couldn't use the one on the 
slinky install floppy because I needed the corresponding moules.  I tried the 
one on the slinky iso, then the 2.4.20-18.9 kernel from Red Hat.  In the 
process, I managed to zap my regular boot partition and disable lilo (that 
was the long story that I cut short in my earlier post).  Anyway, I was able 
to recover and to install the Red Hat kernel. So, with kernel modules working 
I can expect to get netowking up and slowly get a functional system.  But 
there are still some errors in the boot log (attached).
 
> Date: Sun, 6 Jul 2003 22:34:17 -0400
> From: "Jason Bechtel" <jasonbechtel at care2.com>
> To: rule-list at nongnu.org
> Subject: [RULE] Re: Install Report (slinky 3.95 with Red Hat variant)
> Message-ID: <5BA0C5E5B6D473D4D846293B231E60B1 at jasonbechtel.care2.com>
> Content-Type: text/plain; charset=iso-8859-1
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Precedence: list
> Reply-To: jasonbechtel at care2.com, The main mailing list of the RULE project
>       <rule-list at nongnu.org>
> Message: 2
>
> Ray,
>
> I think you should try to use the Lorma i686
> packages as much as possible and I see no reason
> why you shouldn't be able to use them all.  The
> only thing it changes is that things won't run on
> anything less than a 686-compatible processor,
> but this was a given when you chose Lorma Linux
> to begin with.  These packages should run faster
> than i586 or i386 packages because they are
> compiled to take advantage of the architecture
> improvements over those older processors.
> Another reason is simply that you don't know what
> Lorma might have changed in those packages and it
> would be better if you just all packages from one
> source.
>
> You should be able to just do a global search and
> replace on the package lists to change them to 686:
>
> cat pkglist | sed -e 's/386/686/g' > pkglist.6
> mv pkglist.6 pkglist
>
> Jason
Sorry, I wasn't quite clear in my original post.  The Lorma Linux packages are 
mostly i386 but glibc, openssl, the kernel and some other packages (including 
the XFree86 packages) are i686. so updating the package lists is a tad more 
complicated than search and replace.

What I see as a problem is that manually installing an i686 package in the 
system fails with a "Wrong architecture" message. Can I just force rpm to 
install it, regardless?  Hmm, why don't I try?

Well, I just tried
    rpm -i XFree86-4.3.0-2.i686.rpm --root /dev/hd --force
and I got
    error: cannot open Packages index using db3 - No such file or directory 
(2)
    error: cannot open Packages database in /dev/hd/var/lib/rpm

I can try again after booting into the installed Red Hat 9 system. 

Thanks a zillion,

Ray

P.S. Resending with boot.log 'cause messages was too long--sorry!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boot.log
Type: text/x-log
Size: 15258 bytes
Desc: not available
URL: <http://lists.hellug.gr/pipermail/rule-list/attachments/20030708/4e2979f1/attachment.bin>
-------------- next part --------------
_______________________________________________
Original home page of the RULE project: www.rule-project.org
Original Rule Development Site http://savannah.gnu.org/projects/rule/
Original RULE mailing list: Rule-list at nongnu.org, hosted at http://mail.nongnu.org/mailman/listinfo/rule-list