Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ulrik De Bie <ulrik@mind.be>
To: Kristoffer Gleditsch <toffer@ping.uio.no>
Cc: Guido Guenther <agx@debian.org>,
	debian-mips@lists.debian.org, linux-mips@oss.sgi.com
Subject: Re: Need an account on a Linux/Mips box
Date: Fri, 5 Oct 2001 12:33:00 +0200	[thread overview]
Message-ID: <20011005123300.C23786@mind.be> (raw)
In-Reply-To: <vzabsjnpftn.fsf@false.linpro.no>; from toffer@ping.uio.no on Thu, Oct 04, 2001 at 05:47:48PM +0200

On Thu, Oct 04, 2001 at 05:47:48PM +0200, Kristoffer Gleditsch wrote:
> [ Guido Guenther ]
> 
> > Toolchain update problem - recompiling fixes this. I've put recompiled
> > debs at:
> >
> > http://honk.physik.uni-konstanz.de/linux-mips/debian/ssl-tmp/
> 
> Thanks, they seem to work fine.
> 
> Concerning the other R4600 issues: Our R4600 Indy has 11 days of
> uptime now, and Bind 9 is still running fine.  When I switched back to
> ssh from ssh-nonfree just now, the calls to update-alternatives in the
> prerm-file segfaulted repeatedly.  I'm trying to gather the patience
> to debug it now.  :)

Quick and dirty hack that might work (I had quite a number of segfaults during
installation and this trick did work): change the /bin/sh between bash and
ash.

Kind regards,
Ulrik De Bie

      parent reply	other threads:[~2001-10-05 10:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-22 16:58 Need an account on a Linux/Mips box Emmanuel Dreyfus
2001-09-24 15:03 ` Kristoffer Gleditsch
2001-09-24 15:03   ` Kristoffer Gleditsch
2001-09-24 15:37   ` Raoul Borenius
2001-09-24 15:54     ` Guido Guenther
2001-09-24 16:24     ` Kristoffer Gleditsch
2001-09-29 10:20       ` Guido Guenther
2001-10-04 15:47         ` Kristoffer Gleditsch
2001-10-04 15:59           ` Installation instructions Petri Tapio Koistinen
2001-10-05 10:33           ` Ulrik De Bie [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=20011005123300.C23786@mind.be \
    --to=ulrik@mind.be \
    --cc=agx@debian.org \
    --cc=debian-mips@lists.debian.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=toffer@ping.uio.no \
    /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