HDTenEightyP/NetNews huggingface dataset:
From: michael@gandalf.informatik.rwth-aachen.de (Michael Haardt)
Newsgroups: comp.os.minix
Subject: Re: Elvis 1.5 and PC ACK 1.3
Date: 6 Apr 92 21:46:12 GMT
Reply-To: u31b3hs@messua.informatik.rwth-aachen.de (Michael Haardt)
Organization: Gandalf - a 386-20 machine

From article <1992Apr04.141609.10662@crash.cts.com>, by cwr@pnet01.cts.com (Will Rose):
> Compiling Elvis 1.5 with PC ACK 1.3 isn't entirely straightforward.  This
> is problem with ACK, since Elvis compiles without difficulty under eg. SYSV.
Right, it compiled with only one change (wrong prototype) under LINUX.

> cc -i -S -O -DCRUNCH \
> 	-DNO_MKEXRC -DNO_CURSORSHAPE -DNO_CHARATTR -DNO_SHOWMODE \
> 	-DNO_MODELINE -DNO_OPTCOLS -DNO_DIGRAPH -DNO_EXTENSIONS \
> 	-DNO_ERRLIST -DNO_FKEY -DNO_VISIBLE -DNO_COLOR -DNO_POPUP tinytcap.c
> /usr/lib/opt: error on line 543: out of memory
Don't use -O

> make: Error code 256
Error code 256: Can someone tell me how such a code will be encoded in 8
bits? (May only be seven, I don't remember right).  It once was a problem,
because I got a shell script which run make and checked the error code, which
was 0!

> cc -i -S -O -DCRUNCH \
> 	-DNO_MKEXRC -DNO_CURSORSHAPE -DNO_CHARATTR -DNO_SHOWMODE \
> 	-DNO_MODELINE -DNO_OPTCOLS -DNO_DIGRAPH -DNO_EXTENSIONS \
> 	-DNO_ERRLIST -DNO_FKEY -DNO_VISIBLE -DNO_COLOR -DNO_POPUP tinyprnt.c
> "tinyprnt.c", line 64: (warning) conversion of long to pointer loses accuracy
I was used to get this warning, when using a long instead of int to index
arrays.

> The cmd1.c problem is due to ACK not understanding \" on lines 1755 and 1757.
> If these are removed it compiles correctly.  (The error message seems to be
> one of ACK's little witticisms).
cpp does not know it.  I had success with decus cpp for several programs.
Decus cpp also comes with source :)

> Asld gives an error: tio.s: _match multiply declared.  I couldn't find
> any match variable outside tio.c, so I named match to mat, and had no
> further problems.  (match is declared on line 314).  Presumably
> asld has a name space problem of some sort.
Hmm, there are also versions of asld which do not know static floating around.

> The elvis documentation seems to have been formatted with mroff, using
> macros peculiar to that formatter (XA and XS).  Does anyone have copies
> of these macros?  My early version doesn't include them.
Mine also only has XS *:-)  X[A-Z] macros are for tables of contents, and
there aren't any widespread standards on how they should be defined :(
Perhaps I will add a better support in the next version of mroff, perhaps
I will use groff and there will no new version of mroff, except for the
utilities.

Michael
From: osynw@giac1.oscs.montana.edu (Nate Williams)
Newsgroups: comp.os.minix
Subject: Re: klib386 mpx386 again
Keywords: n
Date: 16 Apr 92 17:06:18 GMT
Organization: Montana State University, Bozeman  MT

In article <1992Apr16.105059.1408@news.cs.indiana.edu> dmoffatt@peach.ucs.indiana.edu (David Moffatt) writes:
>I earlyer posted an a note asking people for these files.  When I posted 
>I forgot to give my e-mail address.  So ...
>
>If you have or know where I can find klib386 and mpx386 for minix 1.5 could 
>you please drop me a note.  Thanks
>
>dmoffatt@silver.ucs.indiana.edU


These files are not part of 'STANDARD' minix.  These files are part of 
Bruce Evans' 386-minix port.  If you really want them, get them on
the major minix archive sites.  Glen just posted the info sheet and the
FAQ, so all the important info should be in them.

Nate
-- 
:-):-):-):-):-):-):-):_):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-)
:-)Inet: osynw@giac1.oscs.montana.edu  :-) Sys. Mgr. - GIS lab : Earth Sci.:-)
:-)Bnet: osynw@MTSUNIX (Painfully slow):-) The guy blamed for everything   :-)
:-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-)
Newsgroups: comp.os.minix
From: malx0156@steer.sdsu.edu (Michael Peay)
Subject: For Sale: MacMinix 1.5.10.0 (Patched to 1.5.10.7)
Summary: Selling Good 'ol friend
Organization: San Diego State University
Date: Mon, 6 Apr 1992 19:19:23 GMT

I am a student that is graduating next month.  Minix has helped me avoid many
hours in the labs in doing my assignments.  My need for the system a gone
and would like to give a good home to my friend.

It is the standard 1.5.10.0 version with box.  I patched it up to 1.5.10.7
which provides System 7.x compatability.  I've also added shh (sh with alias
and history), xlisp, man files, and minicom (although I haven't config. it yet).

I paid $180 +- but am perfectly willing to sell it for $125/best.  For those
who think this might be a little high, I figure that if you bought it off the
shelf, you would have to patch and debug the system yourself, which I have
done already for you.

Email me if interested,
Thank you,
Mike
malx0156@steer.sdsu.edu
Newsgroups: comp.os.minix
From: carlb@hardy.u.washington.edu (Carl Boernecke)
Subject: cron
Organization: University of Washington
Date: Wed, 15 Apr 1992 08:14:14 GMT

Ever since I preformed an upgrade on MINIX-PC, I haven't been able to
get cron to run correctly.  Is this a problem with 1.5.10.7, or a pro-
blem with the cron program itself?

I currently set-up cron with a line in my /etc/rc file.  My /usr/lib/
crontab file reads (for testing purposes):

	* * * * * * /usr/bin/date > /dev/tty0

Note that there really is not a tab at the beginning of the line in the
file -- just here to easy readibility.  I would like to get it running
correctly so I don't have to manually execute the UUCP program "uupoll"
every time I logon.

-- Carl Boernecke (carlb@inex.UUCP or carlb@u.washington.edu)
From: odiug@messua.informatik.rwth-aachen.de (Guido Muesch)
Newsgroups: comp.os.minix
Subject: Re: Haardt lpd package problem
Date: 13 Apr 92 11:55:19 GMT
Organization: RBI - RWTH Aachen

bls@cis.ksu.edu (Bryan L. See) writes:

>I've installed Michael Haardt's small lpd package.  Everything seems to
>work okay except that the actual print never happens.  Lpsig -c doesn't
>seem to help.  The spool files are created normally.  Any ideas.
>--
>   Bryan L. See                bls@cis.ksu.edu

Did you really start the program lpd. This one is the most important
part of the printer spooler package the deamon itself. You normally
put this in /usr/lib and start it in /etc/rc by just executing 'lpd'.
It will put itself in the background....
Hope that helps ....

Cheers Guido


-- 
    /\       bitnet: odiug%messua.informatik.rwth-aachen.de@unido.bitnet
   /  \      email:  odiug@messua.informatik.rwth-aachen.de
__/    \  ________________________________________________________________
        \/   snail: Guido Muesch, Ruetscher Str.165/1413, 5100 Aachen
From: mirons@ccs.northeastern.edu (michael a irons)
Newsgroups: comp.os.minix
Subject: Re: whereis.c
Summary: The BSD wheris code is available
Keywords: BSD whereis
Date: 16 Apr 92 22:35:40 GMT
Organization: Northeastern University, CCS Dept.


	As the subject line says, the code for whereis for the BSD system
is available. It's on ftp.uu.net:systems/unix/bsd-sources/usr.bin I think.
(I'm not posative about the last directory, the others are right)

					Mike Irons
				mirons@dworkin.ccs.northeastern.edu
Newsgroups: comp.os.minix
From: ralf@ptavv.ka.sub.org (Ralf Wenk)
Subject: Re: libc.a: changing it with ar
Organization: The known space
Date: Sat, 11 Apr 1992 09:47:42 GMT

es1@cunixb.cc.columbia.edu (Ethan Solomita) writes:
> [...]
> 	When I view the contents of libc.a, I notice that the
> files I added are different from the ones already in there. The
> unchanged ones have a 2/2 on them, but mine have a 0/0. As well,

This symply says that you are working as root (uid and gid) when
modifying libc.a an that the *.o modules in it were owned by bin/system
at creation time of libc.a.

> mine are RW for the creator, rather than just read as the older
> ones are.

You are using an different umask or omitted chown. But both items
can not cause the problem you describe.

-- 
-- 
Ralf Wenk -- ralf@ptavv.ka.sub.org
Newsgroups: comp.os.minix
From: gs53@cunixb.cc.columbia.edu (Gong  Su)
Subject: 'send' and 'receive' calls
Reply-To: gs53@cunixb.cc.columbia.edu (Gong  Su)
Organization: Columbia University
Date: Wed, 8 Apr 1992 23:46:23 GMT

Hi! there,
    It seems to me that 'send' and 'receive' calls are only used in MM, FS,
Kernel, and library routines. But they are in 'libc.a' so user program should
be able to use them. Is it ok for user program to call them directly? Are there
any points need to be pay attention to? The reason I ask this is that I'm doing
a class project which implements threads in Minix and I need pass messages bet-
ween threads from a user program.
    Any advice will be appreciated.


----------
Gong Su. Columbia University
gs53@cunixb.cc.columbia.edu
(212)854-2303
From: osynw@giac1.oscs.montana.edu (Nate Williams)
Newsgroups: comp.os.minix
Subject: Re: AST's New Book...
Keywords: n
Date: 8 Apr 92 15:33:04 GMT
Organization: Montana State University, Bozeman  MT

In article <13864@star.cs.vu.nl> ast@cs.vu.nl (Andy Tanenbaum) writes:
>In article <3666@tuegate.tue.nl> tgcpwd@urc.tue.nl writes:
>
>>It sounds interesting enough, but what about price, ISBN number, # of pages, 
>>availability? Perhaps the 'contents' could be given here, or perhaps an
>>abstract or summary? 
>
>I already posted that information.  If you missed it, you can get it by FTP
>from ftp.cs.vu.nl as ast/modern_op_sys (or I can email it to you upon request).
>
>Andy Tanenbaum (ast@cs.vu.nl)

I am going to ftp it, but when/what group did you post it to?  I have
been reading faithfully for the last 9 months, and I don't remember seeing
anything in comp.os.minix.


Nate
-- 
:-):-):-):-):-):-):-):_):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-)
:-)Inet: osynw@giac1.oscs.montana.edu  :-) Sys. Mgr. - GIS lab : Earth Sci.:-)
:-)Bnet: osynw@MTSUNIX (Painfully slow):-) The guy blamed for everything   :-)
:-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-)
Date: Fri, 10 Apr 92 15:41:26 +0200
From: Wolfram_Sauerteig@hippo.fido.de (Wolfram Sauerteig)
Subject: Re: Minix 1.5 for PCs with an IDE hard drive?
Newsgroups: comp.os.minix
X-Comment-To: chinkao@boole.seas.ucla.edu (Chin C. Kao)
Organization: Besser Minix als garnix! 


CC> Can anyone tell me if Minix 1.5 will work on a 486 with an IDE hard drive?
CC> Thanks.

If it works, depends on the Types of Your Harddisk and Controller, and (seldom) 
Your Motherboard.
My combination is:
Motherboard 386sx20 / 387sx
IDE Contr.  Seagate ST08
Harddisk    Quantum LPS240AT
partitionned 32_MB + 165_MB DOS
           +  7_MB Minix ram disk image
           + 32_MB Minix /usr
and it works.
Problems are known with Quantum LPS52AT and LPS105AT and ROM versions less than 
2.6 (ROM is located in the middle of the PCB downside).

maybe, You should tell, what Harddisk etc. You are going to use, and someone 
running the same devices may reply...

hope, this helps

bye
    Wolfram
From: gryphon@brchh43.BNR.CA (Joe Widows)
Newsgroups: comp.os.minix
Subject: Looking to fill in the blanks with PH 1.5.10 ST code
Keywords: Minix Source Code
Date: 6 Apr 92 07:30:21 GMT
Reply-To: gryphon@bnrrch43.bnr.rich
Organization: BNR


 I have been debugging and converting the code to the system to MWC
 I can now compile and assemble everything.  However, I cannot find all
 all the sources.  While I am at the point I expect to
 find more errors I do know that RECEIEVE and RDY_HEAD are not
 implementation defined.  I cannot find
 their code.  I have ALL the sources on my disk set.  If it is
 there, please tell me where.

 Please tell me where these things are defined.  I cannot build
 even a prototype kernel until I can resolve the names.

 And for the record, I exported the code so that I could use the greater
 resources of my ST. I will not boot a system with at teaspoon. I do this
 for a living, and I don't have time to spoonfeed the process.	I discovered
 that the sources were very dirty.  Shady code practices and outright bugs.

 I'm not terribly angry, yet.  Please, in the next release, sanitize the code.
 and build the system with THAT CODE, and the published compiler.  This is
 only reasonable.  We are given sources that supposedly match the system.
 I am pretty sure my sources do not; however, that remains to be proven.

 I have a 4meg 1040st with 1.0 roms , a 4meg MEGAst with 1.2 roms and
 an ICD fast scuzzi-plus (22ms) and 200 megs of hard drive.  Currently,
 I cannot compile the system enough to fix the harddisk fault. I have
 patches, but I cannot patch non-working code.	Without that code, I
 could not even compile the system inside Minix.

 As an ambition, I think I can install virtual memory with that disk drive.
 Certainly, I am planning on porting the system into a 68030 with virtual
 memory (from ICD).  So I am anxiously looking for these sources.

 DISCLAIMER: BNR builds telephones, not opinions.
 ANTIDISCLAIMER: the wrong stuff is mine ( the right stuff, too)
Newsgroups: comp.os.minix
From: sss6270@tamsun.tamu.edu (Syama Sunkara)
Newsgroups: comp.os.minix
Subject: Demo version of minix - Help!!!
Date: 11 Apr 92 21:28:34 GMT
Followup-To: sunkara@tamu.edu
Organization: Texas A&M University, College Station

I anonymous FTPed the eleven .Z files from wuarchive.wustl.edu
Could someone tell me how to put them together to make the
demo version of minix.

Please reply to :       sunkara@tamu.edu

Thank you
Newsgroups: comp.os.minix
From: archetyp@uxh.cso.uiuc.edu (Joseph R Pickert)
Subject: Re: /usr/src/test, some fail under 1.5.10.7 MacMINIX
Organization: University of Illinois at Urbana
Date: Wed, 15 Apr 1992 13:43:42 GMT

test18 should run as root, mode 4755 (see makefile).

I was unable to get this to happen, either under sys 6 or sys 7.
Anyone else see this?
From: dmoffatt@banana.ucs.indiana.edu (David Moffatt)
Newsgroups: comp.os.minix
Subject: Help amoeba has fallen and can't get up
Keywords: amoeba no work
Date: 6 Apr 92 18:12:09 GMT
Article-I.D.: news.1992Apr6.131216.1212
Organization: Computer Science, Indiana University

We are working on updateing from minix 1.3 -> 1.5.  We have compiled
minix without amoeba and it works.  Now we are trying to get amoeba up.
We have run into some strange problems.  All of amoeba compiles.  We are
able to link it but we have found that the ordering of the linking changes
the size of the program.  amoeba kernel is 48k when linked in one order
and 52k when linked in another order.  The program does not run in either
order.  We can't link it in the order that the Makefile that came with our 
update kit specifies becuase it runs out of memory. We have used chmem on
asld and we given it as much memeory as chmem allows.

My question is this: DOES AMOEBA WORK?  Has anyone used it?  Did you 
encounter any problems like the ones I am haveing?  If anyone has any info
please send mail.

Thanks  dmoffatt@silver.silver.ucs.indiana.edu
From: tgcpwd@rw7.urc.tue.nl (Wim van Dorst)
Newsgroups: comp.os.minix
Subject: Re: I tested minix once..
Date: 17 Apr 92 06:30:46 GMT
Reply-To: tgcpwd@urc.tue.nl
Organization: Eindhoven University of Technology, The Netherlands

Wolfram Sauerteig writes:
>Every Minix, which is setup first time, has two logins:
>'ast'  for normal usage with password 'Wachtwoord'.
>'root' for becoming superuser and do some System administration (be careful,

Both passwords, for ast as well as for root are Dutch. I thought it
opportune to mention this. Andy lives in the Netherlands, although
he is reachable just as easily from elsewhere.

As for posting the information referred to, I'd prefer the method used
for that information in the Minix Information Sheet, by Glen Overby.

Met vriendelijke groeten, Wim `Blue Baron' van Dorst
-- 
---------------------------------------------------------------------
Blue Baron = Wim van Dorst, Voice (+31) 074-443937, (+31) 02152-42319
(-:       baron@wiesje.hobby.nl           tgcpwd@urc.tue.nl       :-)
---------------------------------------------------------------------
From: waltje@minixug.mugnet.org (Fred 'The Rebel' van Kempen)
Newsgroups: comp.os.minix
Subject: Re: Minix filesystem questions
Date: 30 Mar 92 06:12:58 GMT
Organization: MINIX User Group Holland (NLMUG)   -  MUGNET  -

rickr@virtech.uucp (Rick Rodman) wrote:
> 1. I have heard it said that the Atari ST Minix and the IBM PC Minix are not
> file-system-compatible and cannot exchange disks.  I do not have the ability
> to check this out.  If true, this is an incredible design blunder.  Does anyone
> know if this is true, and if so, why?
I vaguely recall some rumor about Intel and Motorola disagreeing about
what byte order to use for storing 'words' and 'doublewords'. Since MINIX
had to run on SLOWWWWW XT's in the beginning, Andy decided to implement
the file system superblock and the inode tables by writing complete
structures to disk, without any regard to byte ordering.

MINIX 1.6 and up have FS2, which have a simple solution for this. One
can now read and write file systems of the native format, _and_ one
can now read file systems of the 'otther sexe'...

Speaking about incredible design blunders.. did you ever try to write
an endian-independent file system that was also fast enough to acually
use it? I bet not...

> 2. A friend is trying to use dosread to access a DOS partition larger than
> 64 megabytes, and the utility can't go beyond 64 megabytes within the
> partition; it wraps around.  Does anyone know why this is?  I've heard there's
> a 64 megabyte partition limit for Minix filesystems, but what in the world
> does this have to do with a DOS partition?
Hahahaha.
MS-DOS has a limit of 32Mb per partition. Only the newer 4.x and 5.x
versions of DOS have several silly solutions for this problem, like
sub-partitioning a partition ("logical devices") and such...

The MINIX 'dosXXXX' program only knows about DOS-file systems <= DOS 3.30,
so its limits equals that of DOS 3.30 !!

The 64M limit of MINIX partitions is caused by the fact that

	a) FS uses the 'int' type for zone && block numbers,
	   so only 2^^16 blocks (== zones) can be addressed...
	   Set zone_shift to 4 and you get a limit of 256Mb !

	b) The disk drivers (WINI, FLOPPY, RAM) also do block
	   I/O in 'int' variables. See above.

The MS-DOS limit of 32Mb (== 64M sectors of 512 bytes) is caused
by the fact that the MS-DOS 'abs_read' and 'abs_write' (interrupts
26h and 27h, I believe- it has been a while :-) expect thes sector
numbers to be of length 'register', i.e. 16 bits. So, only 2^^16
sectors can be addressed within a certain partition. Since MS-DOS
uses _these_ calls to do sector I/O to the BIOS.....

> "A closed mouth gathers no foot." -- Anon.
It also makes less noise.

Fred.
From: waltje@minixug.mugnet.org (Fred 'The Rebel' van Kempen)
Newsgroups: comp.os.minix
Subject: Re: lharc ported to minix1.5
Date: 30 Mar 92 05:59:14 GMT
Organization: MINIX User Group Holland (NLMUG)   -  MUGNET  -

abgrall@aurora.unice.fr (Jean-Paul Abgrall) wrote:
>  Having never seen lharc for minix (maybe I should give a better look :) ,
> I have ported Y.Tagawa & K.U.Rommel's lharc (which is compatible with 
> lharc on PC and AMIGA (LZ) ) ...
That is funny. I ported LHarc over 1,5 years ago, and it is heavily
used on MUGNET. I have posted it on the net twice, so it should be
available somewhere (plains? sirius?)...

Fred.
From: tgcpwd@rw8.urc.tue.nl (Wim van Dorst)
Newsgroups: comp.os.minix
Subject: Re: AST's New Book...
Date: 8 Apr 92 09:18:13 GMT
Reply-To: tgcpwd@urc.tue.nl
Organization: Eindhoven University of Technology, The Netherlands

Marcelo W Mourier writes:
>the prolific AST has a _new_ book on Operating
>Systems out there.  If I remember correctly the title is "Modern Operating
>Systems", the cover is blue, and has a drawing of a bunch of starving
>phylosophers fighting for some spaghetti  :-)

It sounds interesting enough, but what about price, ISBN number, # of pages, 
availability? Perhaps the 'contents' could be given here, or perhaps an
abstract or summary? 

nb: Andy, if you send me a copy I shall most willingly promote the book
    here on the net (Marter 13, 1273 KD Huizen) :-)

Met vriendelijke groeten, Wim `Blue Baron' van Dorst
-- 
---------------------------------------------------------------------
Blue Baron = Wim van Dorst, Voice (+31) 074-443937, (+31) 02152-42319
(-:       baron@wiesje.hobby.nl           tgcpwd@urc.tue.nl       :-)
---------------------------------------------------------------------
Newsgroups: comp.os.minix
From: archetyp@uxh.cso.uiuc.edu (Joseph R Pickert)
Subject: Re: MacMinix status from Joe.
Organization: University of Illinois at Urbana
Date: Fri, 10 Apr 1992 14:11:07 GMT


paul@max.uk.mugnet.org (Paul Wood) writes:

>Joe Pickert writes:
>> Ok, things fall into three major areas:
>> 	1. Fixes
>> 	2. Enhancements
>> 	3. Keeping up with the IBMers.
>Excellent - some news at last!

More news. I got my net connection back.

>> Here are my plans on each.
>>
>> 1. Fixes. I am down to one or two problems that are not fixed with the
>>    version on Plains, but only affect System 7 users anyway. These are
>>    currently fixed, but haven't been released because I haven't
>>    run System 7 enough to test them.
>I wonder what these one or two problems are? I use System 7 with
>almost no problems. (Just the occasional system hang, which are
>very rare; and the occasional error message when using the serial
>port, but serial i/o works anyway).
Entirely VM related.
>> 3. Keeping up with IBMers. I have said this before but I will say it again.
>>    I don't plan on anything here until 2.0.
>Why?
Because it is extremely time consuming to try to update each
intermediate version. I like to do it all at once. I don't understand why,
if people want to run 1.6.16 or whatever, someone out there just
doesn't do it. 99% of the code is exactly the same between all the
versions, and it follows that 99% of the update will work just fine.
The only problem is the kernel. Just use the st version as a
starting point.
>Also is the work currently being done on STMinix useful for MacMinix?
I look pretty carefully at whatever is posted and bring in those things
I can use.
>>    I need to
>>    send him a Mac compatible disk but I wanted to put the new
>>    7.0 mac/include files on it so I haven't sent it back yet.
>What are these files to do with the new compiler? I assume they
>are for System 7 compatibility, and could be issued via this news
>group.
All of the include files are part of the new compiler system since they 
have the ansi prototype information in them. The include/mac files too,
for the mac version of the compiler. Actually, it was just a bad assumption
on my part. I didn't think Andy was going to make the new compiler
available until 2.0. Anyway, it is now on its way to him.

Joe Pickert
Newsgroups: comp.os.minix
From: meggin@epas.utoronto.ca (David Megginson)
Subject: Re: vfork
Organization: University of Toronto - EPAS
Distribution: comp
Date: 9 Apr 92 21:29:04
Originator: meggin@epas.utoronto.ca
	<MEGGIN.92Apr2151504@epas.utoronto.ca> <meulenbr.702830202@cstw18>

In article <meulenbr.702830202@cstw18> meulenbr@cst.prl.philips.nl (Frans Meulenbroeks) writes:

   Forgot to react on the previous postings.
   But: there is a vfork for minix ST. It was posted nov 1991 by
   jens kaemmerer (jens@dtro.e-technik.th-darmstadt.de)
   Check the archives for a copy. 
   I haven't looked at it so I cannot comment on the quality.

I have it in my 1.6.16 kernel -- I was able to apply the patches with
only minor changes, and it passed all the tests. I cannot wait to try
out an emacs binary which uses it, as soon as someone has time to make
a new port, probably after we agree on the syscall number for vfork (I
currently use 45 in minix/callnr.h).


David


--
#################################################################
David Megginson                  meggin@epas.utoronto.ca
Centre for Medieval Studies      david@doe.utoronto.ca
University of Toronto            39 Queen's Park Cr. E.
#################################################################
Newsgroups: comp.os.minix