Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Keith M Wesolowski <wesolows@chem.unr.edu>
To: "J. Scott Kasten" <jsk@tetracon-eng.net>
Cc: linux-mips@oss.sgi.com
Subject: Re: Simple Linux/MIPS 0.2b
Date: Wed, 19 Jul 2000 18:51:56 -0700	[thread overview]
Message-ID: <20000719185153.B24731@chem.unr.edu> (raw)
In-Reply-To: <Pine.SGI.4.10.10007191916250.7274-100000@thor.tetracon-eng.net>; from jsk@tetracon-eng.net on Wed, Jul 19, 2000 at 07:56:25PM -0300

On Wed, Jul 19, 2000 at 07:56:25PM -0300, J. Scott Kasten wrote:

> There is one thing at this point that would really really help.  I need to
> establish a reference point and follow someone elses procedures exactly to
> determine what the source of my problem is and why some of you are not
> seeing this to the extent that I am.  In this way, we can verify whether
> or not there is a bonified problem, and if it is with the tools, maybe get
> it fixed.

Before you get carried away with this, I should point out that I've
been looking at this problem in more detail. Many of my X programs
don't work either; they get SEGV, never bus errors. I suspect this is
a glibc bug. I can run a few programs, such as xhost and the server
itself. I did have a full X setup, including a working server, under
0.1. That was built exactly the same way I've done it under 0.2b. You
may wish to try both and see which works better.

If you like, I will return to 0.1 and duplicate my previous efforts. I
can then describe the exact procedure to you.

-- 
Keith M Wesolowski			wesolows@chem.unr.edu
University of Nevada			http://www.chem.unr.edu
Chemistry Department Systems and Network Administrator

  parent reply	other threads:[~2000-07-20  1:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-13  7:16 Simple Linux/MIPS 0.2b Keith M Wesolowski
2000-07-13 13:58 ` J. Scott Kasten
2000-07-13 22:51   ` Ralf Baechle
2000-07-13 22:39     ` J. Scott Kasten
2000-07-19 14:04     ` Maciej W. Rozycki
2000-07-19 14:19       ` Hiroshi Kawashima
2000-07-20 18:09         ` Maciej W. Rozycki
2000-07-19 14:54       ` J. Scott Kasten
2000-07-19 16:28         ` Andy Isaacson
2000-07-19 17:13         ` Keith M Wesolowski
2000-07-19 17:42           ` J. Scott Kasten
2000-07-19 22:56           ` J. Scott Kasten
2000-07-20  1:39             ` Keith M Wesolowski
2000-07-20  1:19               ` J. Scott Kasten
2000-07-20  1:51             ` Keith M Wesolowski [this message]
2000-07-20  1:43               ` J. Scott Kasten
2000-07-26 15:53         ` big endian Debian root image Chris Ruvolo
2000-07-26 17:10           ` J. Scott Kasten
2000-07-20 12:27       ` Simple Linux/MIPS 0.2b Ralf Baechle
2000-07-20 18:57         ` Maciej W. Rozycki
2000-07-21 10:21         ` Maciej W. Rozycki
2000-07-13 23:30   ` Keith M Wesolowski
2000-07-13 22:59     ` J. Scott Kasten

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=20000719185153.B24731@chem.unr.edu \
    --to=wesolows@chem.unr.edu \
    --cc=jsk@tetracon-eng.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox