[Top] [All Lists]

Re: The pre-release of Hard Hat Linux for SGI...

To: (Alex deVries)
Subject: Re: The pre-release of Hard Hat Linux for SGI...
From: Honza Pazdziora <>
Date: Thu, 16 Jul 1998 15:54:50 +0200 (MET DST)
In-reply-to: <> from Alex deVries at "Jul 15, 98 06:13:15 pm"
Phone: 420 (5) 415 12345
Alright, here are the steps I needed to do in order to have machine that
would allow me to log in. To repeat what I stared with, I installed
just the newtorked WS, did not select any aditional packages, did not
remove any from selection, just base and network.

The first problem: Unable to open initial console. Since you are able
to boot Upgrade from network and have the second console available
(do not start the upgrade, just boot it and hit twice Enter to get rid
of those messages about mount failing), you can create the entries
in the dev directory, that are missing and cause the trouble. I did

        cd /dev
        tar cf - * | ( cd /mnt/dev ; tar xvf - )

so you take the devices from the installation root (there are just
about 8 of them, but there is console ther and that's you need).
The install.log shows that the installation of the dev RPM failed,
so that's why we need to create the devices by hand (obviously, when
it says it fails, it really fails in some way ;-) So you have
console but do not have devices for disks, so Linux won't be able
to remount root, etc.

I've found device /tmp/sdb2 still on the second console of Upgrade,
numbers 8/18, so I created /mnt/dev/sdb2 and /mnt/dev/sdb1 with 8/18
and 8/17. You might be installing to different drives, but anyway,
look around and you'll find the numbers.

If you do not have /etc/passwd like I didn't, you can do

        echo 'root::0:0:root:/:/bin/bash' > /mnt/etc/passwd

to be able to log in after you reboot.

I think it's time to reboot, so do sync and reboot.

I had to boot with init=/bin/bash because first I forgot to create the
/etc/passwd, and second, the /bin/login said something about libraries
(it just blinked and returned the prompt but I saw something like .so
so I think that was it). So once you have bash# prompt, do

> > Some of the packages still complain about failing, on console 4 Unable
> > to load interpreter.

P.S.: I maybe did not stressed out that some of the packages failed
_and_ some gave the following message -- I do not know which gave the
message about ldconfig, but certainly not all that failed.

                During the install of 230 packages there were
> > about 20 messages
> >     ldconfig: Exception at [<88109534>] (8810960c)
> _THAT_ worries me a lot.
> If you have an existing install of linux on your SGI, do this:
> - install the ldconfig rpm that's in the distribution you have

It was installed fine already ...

> - run ldconfig

... so I did run ldconfig ...

> Does that still give the exception?

... and no, no exception, just some messages about some libraries
that I decided are harmless. Anyway, after this, I was able to log in
on prompt and start ncftp to get the dev RPM and install it and install
ssh to get to my mail and send this report.

Do you want the install.log, Alex? I thought you said that the problem
with failing packages was caused by csh and that it was harmless
(just a message). I'm affraid it really means some problem, because
it did not create the /dev entries and did not create the

More later,

 Honza Pazdziora | |
                   I can take or leave it if I please

<Prev in Thread] Current Thread [Next in Thread>