From: Jakub Jelinek <jakub@redhat.com>
To: ultralinux@vger.kernel.org
Subject: Re: Problem with UltraPenguin 1.2 ?
Date: Mon, 29 Nov 1999 22:34:31 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-94391589410854@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-94367026724482@msgid-missing>
On Mon, Nov 29, 1999 at 10:05:41PM +0100, Bosko Radivojevic wrote:
>
> On Sat, 27 Nov 1999, Jakub Jelinek wrote:
>
> > Don't use UltraPenguin, it has been superceeded by Red Hat 6.0 /SPARC and
> > Red Hat 6.1 /SPARC which has been released lately.
> > Most of the features (with the exception of tape install I guess noone
> > besides myself used) were rolled into RH6.0/RH6.1, plus there are numerous
> > newer bugfixes and new features.
>
> I've tried first with RH 6.0 for SPARC, but with that I couldn't even boot
> up my SPARC.
If you download 6.1, then this should be a non-issue.
>
> Something is wrong in script that installs silo, or I missed something
> with partitioning my disk. I tried to install silo by myself... :
> (pressed ctrl-z in install script to switchto shell)
>
> # /mnt/sbin/silo -r /mnt
> Fatal error: Cannot open superblock on /dev/sda1
Do:
/mnt/usr/sbin/chroot /mnt
/sbin/silo
instead, because it tries to access /dev/sda1 outside of /mnt which probably
does not exist.
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jakub@redhat.com | http://sunsite.mff.cuni.cz/~jj
Linux version 2.3.18 on a sparc64 machine (1343.49 BogoMips)
___________________________________________________________________
next prev parent reply other threads:[~1999-11-29 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-27 2:39 Problem with UltraPenguin 1.2 ? Bosko Radivojevic
1999-11-27 7:40 ` Jakub Jelinek
1999-11-29 21:05 ` Bosko Radivojevic
1999-11-29 22:34 ` Jakub Jelinek [this message]
1999-11-29 22:45 ` Bosko Radivojevic
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=marc-linux-ultrasparc-94391589410854@msgid-missing \
--to=jakub@redhat.com \
--cc=ultralinux@vger.kernel.org \
/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