Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!wuarchive!ukma!uflorida!mailer.cc.fsu.edu!sun13!sun8.scri.fsu.edu
From: nall@sun8.scri.fsu.edu (John Nall)
Newsgroups: comp.os.minix
Subject: Re: Minix-386 problem
Message-ID: <1540@sun13.scri.fsu.edu>
Date: 3 Dec 90 19:25:51 GMT
Sender: news@sun13.scri.fsu.edu
Organization: SCRI, Florida State University
Lines: 43

Newsgroups: comp.os.minix
Subject: Re: Minix-386 works! (was: Re: Minix-386 HELP!!)
Summary: 
Expires: 
References: <37483@nigel.ee.udel.edu> <2193@tuvie.UUCP>
Sender: 
Followup-To: 
Distribution: 
Organization: SCRI, Florida State University
Keywords: 

In article <2193@tuvie.UUCP> hp@vmars.tuwien.ac.at (Peter Holzer) writes:
>Last week I asked for help with my problems with Minix-386.
>The symptom was that init died before it could do anything.

>   (...good trouble-shooting story deleted for brevity...)

>John Nall wrote in his tutorial:
>
>cc -3 -D_MINIX -D_POSIX_SOURCE init.c -o /etc/system/init
>
>This links with the default startup code crtso.o . Init needs a special
>startup code instead, just like kernel, mm, and fs.
>The correct way to compile init is:
>
>cc -3 -c -D_MINIX -D_POSIX_SOURCE init.c
>ld -3 -i -o /etc/system/init /usr/local/lib/i386/head.o init.o	\
>	/usr/local/lib/i386/libc.a
>
>John, if you are listening, could you change this in your tutorial. I am
>sure others will fall into the same trap (Although not everybody will
>follow you as blindly as I did :-)

I'm listening, and also somewhat embarrassed.  Bruce Evans had pointed out
this error to me once before, and I meant to correct it in the tutorial.
And didn't.  I'll correct it this time for sure.  Thanks.



--
John W. Nall		| Supercomputer Computations Research Institute
nall@sun8.scri.fsu.edu  | Florida State University, Tallahassee, FL 32306
   WB4LOQ (why? I dunno....everyone else seems to be doing it.  _._)