[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] kernel on a 68000?

To: mint@fishpool.com (MiNT mailing list)
Subject: Re: [MiNT] kernel on a 68000?
From: Guido Flohr <gufl0000@stud.uni-sb.de>
Date: Fri, 19 Nov 1999 17:32:20 +0100
In-reply-to: <Pine.MNT.4.10.9911191655110.214-100000@rakas>; from Martin-Eric Racine on Fri, Nov 19, 1999 at 04:58:59PM +0200
Mail-followup-to: mint@fishpool.com (MiNT mailing list)
References: <Pine.BSF.3.95q.991119152036.23734Q-100000@antyk.obta.uw.edu.pl> <Pine.MNT.4.10.9911191655110.214-100000@rakas>
Sender: owner-mint@fishpool.com

On Fri, Nov 19, 1999 at 04:58:59PM +0200, Martin-Eric Racine wrote:
> On 19.11.1999, Konrad M. Kokoszkiewicz <draco@obta.uw.edu.pl> wrote:
> > This is weird. How error codes can have an influence on ST, while they
> > haven't on Falcon? I haven't had any problems switching to new (1.15.4
> > that time) kernel.
> 
> 1.15.4 broke several application's behavior, on every machine.
> That's predictable, when return codes are not what's expected
> anymore.  I have reverted back to 1.15.3 on the TT for the same
> reason.  

I'm still waiting for an example.

The only one I know of was ECHILD instead of ENOENT in waitpid which was a
typo in the 1.15.4 beta (!) kernel and is now fixed (at least it should
be, Frank?)

Ciao

Guido
-- 
http://stud.uni-sb.de/~gufl0000/
mailto:gufl0000@stud.uni-sb.de

Follow-Ups:
- Re: [MiNT] kernel on a 68000?
  - From: Frank Naumann <fnaumann@prinz-atm.CS.Uni-Magdeburg.De>

References:
- Re: [MiNT] kernel on a 68000?
  - From: "Konrad M. Kokoszkiewicz" <draco@obta.uw.edu.pl>
- Re: [MiNT] kernel on a 68000?
  - From: Martin-Eric Racine <q-funk@pp.fishpool.fi>

Prev by Date: Re: [MiNT] Pgetauid/Psetauid
Next by Date: [MiNT] kernel 1.15.5
Previous by thread: Re: [MiNT] kernel on a 68000?
Next by thread: Re: [MiNT] kernel on a 68000?
Index(es):
- Date
- Thread