All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Seth Mos <knuffie@xs4all.nl>
Cc: linux-mips@oss.sgi.com
Subject: Re: Updates on RedHat 7.1/mips
Date: Wed, 18 Jul 2001 17:36:09 -0700	[thread overview]
Message-ID: <20010718173609.A21139@lucon.org> (raw)
In-Reply-To: <Pine.BSI.4.10.10107182218050.23958-100000@xs4.xs4all.nl>; from knuffie@xs4all.nl on Wed, Jul 18, 2001 at 10:53:22PM +0200

On Wed, Jul 18, 2001 at 10:53:22PM +0200, Seth Mos wrote:
> 
> I am having trouble getting the mipsel packages installed using the
> installer provided for 7.1.
> 
> 
> I have hooked up a second disk to my i386 workstatition that will house
> the filesystem for my mipsel box. Once everything is installed I will put
> this disk back in my Qube2 for testing. In the worst case scenario I will
> need to boot with the 2.0 kernel that came with the cube.
> 
> I have the original disk for the Qube2 so it isn't a big problem if it
> takes 50 attempts. I have a lot of patience ;-)
> 
> Am I correct to assume that I need to use the install.i386.hd on my
> workstation to install the mipsel packages on the second harddrive (hdd in
> my case)

No. It should be install.mipsel.nfs. install.mipsel.hd is for the
native mipsel machine install.

> 
> Traceback (innermost, last):
>   File "./findrpm", line 5, in ?
>     import rpm
> ImportError: No module named rpm
> 
> Does this ring any bells?

You need to install the rpm-python rpm.

> The mipsel packages are located in the RPMS directory which is in the same
> directory as the installer and I edited the Makefile and changed ROOT and
> REDHAT-ROOT

Sure.

> 
> I wonder if anyone can provide a basic root tarbal which I can use to set
> up the basics after which i can start adding stuff.
> 

install.mipsel.nfs is used to create a NFS root tree for mipsel. If
you tar it up, you get what you are asking for.



H.J.

  reply	other threads:[~2001-07-19  0:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-06  8:15 Illegal instruction Carsten Langgaard
2001-07-06  9:27 ` Houten K.H.C. van (Karel)
2001-07-06 11:42   ` Maciej W. Rozycki
2001-07-06 13:26 ` Dan Aizenstros
2001-07-06 22:04 ` Jun Sun
2001-07-10 11:14   ` Carsten Langgaard
2001-07-10 17:31     ` H . J . Lu
2001-07-16 11:26       ` Carsten Langgaard
2001-07-16 21:28         ` Updates on RedHat 7.1/mips H . J . Lu
2001-07-17 19:16           ` Carsten Langgaard
2001-07-17 19:29             ` H . J . Lu
2001-07-17 19:50               ` Daniel Jacobowitz
2001-07-17 19:57                 ` H . J . Lu
2001-07-17 20:09                   ` Ilya Volynets
2001-07-17 20:11                     ` H . J . Lu
2001-07-18  3:52                       ` Arnaldo Carvalho de Melo
2001-07-18  4:01                         ` Ilya Volynets
2001-07-18  7:13               ` Carsten Langgaard
2001-07-18 15:11                 ` H . J . Lu
2001-07-18 15:23                   ` Carsten Langgaard
2001-07-18 20:53                     ` Seth Mos
2001-07-19  0:36                       ` H . J . Lu [this message]
2001-07-19 21:03                         ` Seth Mos
  -- strict thread matches above, loose matches on Subject: below --
2001-07-18 12:07 Gleb O. Raiko
2001-07-18 13:26 Ralf Baechle
2001-07-18 16:48 ` Daniel Jacobowitz
2001-07-18 22:23   ` Ralf Baechle
2001-07-19 13:29     ` Florian Lohoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010718173609.A21139@lucon.org \
    --to=hjl@lucon.org \
    --cc=knuffie@xs4all.nl \
    --cc=linux-mips@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.