From: Martin Costabel <costabel@wanadoo.fr>
To: Hollis R Blanchard <hollis+@andrew.cmu.edu>
Cc: Sam Quigley <osquigle@cs.uchicago.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: FTP Problems
Date: Mon, 04 Jan 1999 09:14:19 +0100 [thread overview]
Message-ID: <3690785B.34A0CB72@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.3.96L.990103184911.3513C-100000@unix49.andrew.cmu.edu
Hollis R Blanchard wrote:
>
> On 3 Jan 1999, Sam Quigley wrote:
>
> > > OK, so it can't open the RPMS database, right? Can you switch to virtual
> > > console 3 (Cmd-F3) or 4 and see if there's a specific error listed? That
> > > might be a little more helpful than the installer errors message.
> >
> > I have this problem too: the error reported is, on console 3:
> >
> > * ugFindUpgradePackages() ...
> > * failed opening /mnt/var/lib/rpm/packages.rpm
> >
> > the installer warns that 'an error occurred during step "Choose
> > packages to upgrade"', but also has a stray line reading
> > "/mnt/var/lib/rpm/nameindex.rpm:" on the background. (this is,
> > presumably, an error message from something other than the installer)
> >
> > I can cat packages.rpm fine from the console.
I saw such error messages when the installer had some mount problems. I
think they went away with the glibc-2.0.108 libraries. But I am not sure
about this.
> Hmm. I am *not* an expert on the RedHat installer, but what's in packages.rpm?
> And how about nameindex.rpm?
>
> I expect we'll get a little help once people get settled after MacWorld. Which
> reminds me, I was hoping I could get a list of the various people working on
> R5 and what they're doing. Just curious, plus it would make it easy to have a
> dialogue with the person(s) working on the RedHat installer.
This might be a good idea, but seeing how they have worked in the past,
my guess is that they already have some (almost) finished perfectly
working installer sitting around somewhere but didn't have the time to
copy it to the right place. So we shouldn't get heated up too much about
this question.
> Martin's ramdisks don't *fix* anything, they just give you the tools you need
> so *you* can fix it.
Yes, thank you, Hollis, that's what I intended. I am just a dumb user
like everyone else here in this thread. I just happened to spend some of
my Xmas holidays on trying to figure out how these ramdisk images are
constructed. And I managed to install pre-R5 some time ago using the
supp.img floppy.
But now holidays are over, I have to go back to work.
See you later
--
Martin
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
prev parent reply other threads:[~1999-01-04 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <o9un240gfbb.fsf@yeenoghu.cs.uchicago.edu>
1999-01-04 0:31 ` FTP Problems Hollis R Blanchard
1999-01-04 8:14 ` Martin Costabel [this message]
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=3690785B.34A0CB72@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=hollis+@andrew.cmu.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=osquigle@cs.uchicago.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).