HDTenEightyP/NetNews huggingface dataset:
From: adlacy@vax1.tcd.ie
Newsgroups: comp.unix.sysv286
Subject: PD 286 UNIX ?
Date: 10 Apr 92 18:35:53 GMT
Organization: Trinity College Dublin

Beginner question.

Is there a PD version of Unix for a 286 PC ?
If so where can I get my hands on it ?
-- 
      
      cheers, Andy!
________________________________________________________________________________
Andrew Lacy,                          |  adlacy@vax1.tcd.ie 
Final year Computer Eng. Ugrad.,      |  adlacy@unix2.tcd.ie
Trinity College Dublin, Ireland.      |  adlacy@ashe.cs.tcd.ie
______________________________________|_________________________________________
From: knie2586@csd4.csd.uwm.edu (Robert Joseph Knier)
Newsgroups: comp.unix.bsd
Subject: mtools
Date: 14 Apr 92 20:40:54 GMT
Article-I.D.: uwm.1992Apr14.204054.19829
Organization: Computing Services Division, University of Wisconsin - Milwaukee


   Anyone have any luck with the mtools?  I tried the mdir command
and the system just gave me a couple of FD errors then stopped.

					Bob Knier
From: drg@bubba.ma30.bull.com (Daniel R Guilderson)
Newsgroups: comp.unix.bsd
Subject: Re: BSD names (was: BSD on floppies)
Date: 10 Apr 92 15:04:49 GMT
	<1992Apr8.110359.10948@pegasus.com> <148@adagio.UUCP>
	<VIXIE.92Apr9152242@cognition.pa.dec.com>
Organization: Bull World Wide Information Systems, Billerica MA USA

In article <VIXIE.92Apr9152242@cognition.pa.dec.com> vixie@pa.dec.com (Paul A Vixie) writes:

   How about "Jolitz 386BSD" and "BSDI BSD/386" ?
		^		 ^^^^^^^^^^^^^^-----BSDI controls that.
		|				    We have no choice.
		|
                Now this we can work on.  Jolitz himself is using
		386BSD so that is going to stick but since everyone
		seems to want a little more clarity, I propose we call
		it F-386BSD for "Free" 386BSD.  For the really serious
		hackers we can call it F-386BSD_w/30mm_Vulcan_Cannons.

Actually, since the 486 (and soon the 586) will be the cpus of choice,
we should probably call it F-x86BSD or for the rexp-nerds, F-[3-9]86BSD.
Newsgroups: comp.unix.bsd
From: ziegast@godzilla.UU.NET (Eric W. Ziegast)
Subject: Re: uugetty in BSD?
Organization: UUNET Technologies - Falls Church, VA
Date: Thu, 16 Apr 1992 04:53:41 GMT

thomasm@Ingres.COM writes:
|> Has anyone come up with anything that resembles the AT&T uugetty for BSD?
|> I've picked up the enable/disable [port] source from the comp.sources.unix
|> archives and this is very useful but still not quite as good as uugetty -
|> which respects the uucp locking convention (LCK..com1).

How about looking in the Taylor (GNU) UUCP code?
--
Eric Ziegast
From: rodeen@buddha.ncc.umn.edu (Rick Odeen)
Newsgroups: comp.unix.bsd
Subject: Re: The great BSD name-off...
Date: 14 Apr 92 21:32:10 GMT
Distribution: usa
Organization: Nutrition Coordinating Center, University of Minnesota

In article <id.EGVO.65F@ferranti.com> peter@ferranti.com (Peter da Silva) writes:
>OK, how about suggesting the other meaning of free: liberated? "Liberix",
>or "Openix" (Karl could go for that), or "Anarchix", or "Liberated Software
>Distribution" (LSD).

How about "Berkeley Free Distribution" (BFD).

-- 
"MINIX costs $169, but the license allows  | Rick Odeen 
making two backup copies, so the effective | rodeen@buddha.ncc.umn.edu 
price can be under $60."                   | rutgers!umn-cs!buddha!rodeen
         - ast@cs.vu.nl (Andy Tanenbaum)   |
From: tinguely@plains.NoDak.edu (Mark Tinguely)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD vfork(), DELAY() and /sbin/init bugs
Date: 8 Apr 92 15:14:08 GMT
Article-I.D.: plains.16524
Organization: North Dakota State University, Fargo, ND


 There is another error in reaping of orphaned children that occurs
 in fork as well as vfork. No one will even pretend that init is complete.

 In init, orphaned children are supposed to be reaped by catching
 a SIGCHILD signal, which apparrently this signal is not always
 (or ever) getting raised and orphan children are zombies.

 Now we can either work hard and make sure the signal is raised to
 init, or we can start to think about re-writting init. What I did
 in the below patch is change the loop of pauses to a loop of waits

	--------------- Cut Here ---------------------
*** init-orig.c	Wed Apr  8 09:51:27 1992
--- init.c	Wed Apr  8 09:52:38 1992
***************
*** 49,54 ****
--- 49,57 ----
  #include <signal.h>
  #include <setjmp.h>
  
+ #include <sys/types.h>
+ #include <sys/wait.h>
+ 
  char *shargv[] = { /*"sh"*/ "-", 0 } ;
  char *shenv[] = { "HOME=/", "TERM=pc3", "USER=root", 0, 0 } ;
  char initarg[30];
***************
*** 58,63 ****
--- 61,67 ----
  main(argc, argv) char *argv[]; {
  	int n;
  	int off = 0;
+ 	int stat;
  	extern child();
  
  	/* did some idiot try to run us? */
***************
*** 112,122 ****
  		write("execve failed: /bin/sh\n");
  		exit(0xff);
  	}
! 	for(;;)pause();
  }
- 
- #include <sys/types.h>
- #include <sys/wait.h>
  
  child() {
  	int status;
--- 116,124 ----
  		write("execve failed: /bin/sh\n");
  		exit(0xff);
  	}
! 	while (1)
! 	 if (wait(&stat) == cpid) break;
  }
  
  child() {
  	int status;
Newsgroups: comp.unix.bsd,comp.unix.internals,comp.unix.questions,comp.lang.c
From: jik@athena.mit.edu (Jonathan I. Kamens)
Subject: Re: errno questions
Followup-To: comp.unix.questions
Organization: Massachusetts Institute of Technology
Date: Thu, 9 Apr 1992 21:10:14 GMT

In article <etxaax.702829519@falcon2> etxaax@falcon2.ericsson.se (Anders Axelsson) writes:

   Does anyone know if errno can be 0 after a Unix error?

Define "Unix error."

Do you mean, "An error in a UNIX system call whose documentation
claims that it sets errno when an error occurs?"  Or do you mean, "An
error in any UNIX library function?"

No system call or function which claims to set errno when an error
occurs should be setting it to 0.  If you check errno and find
it equal to 0, it can mean one of several things:

1) You're using errno when you shouldn't be, e.g. after calling a
function which does not claim to set errno upon error.

2) There is a bug in the system call or function you're calling -- it
forgot to set errno when it should have.

3) The system call or function knows that an error occurred, but it
doesn't think that any of the errors in <errno.h> are an adequate
description of the error, so it resorts to leaving 0 in errno.
(Actually, I've never actually seen this happen, so I don't know if
it's considered "OK" or not; I'm just postulating.)

   sys_errlist[0] does
   have a value, a cryptic message "Error 0".

This is to deal with problems of the type (3) listed above, and also
to deal with people doing bogus things like using sys_errlist[errno]
or perror() when errno hasn't been set properly.

   [two copies of signature]

Tsk, tsk.

-- 
Jonathan Kamens						jik@MIT.Edu
MIT Information Systems/Athena		    Moderator, news.answers
    (Send correspondence related to the news.answers newsgroup
	{and ONLY correspondence related to the newsgroup}
		 to news-answers-request@MIT.Edu.)
Newsgroups: comp.unix.bsd
From: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: prototyping
Date: 15 Apr 92 10:02:11 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

Ok, I've more or less got my system going and I've started looking at
the code. I agree that prototyping needs to be done and general
ansifying/standardising. I just tried to compile gnu grep and all sorts
of things are going wrong.

Right, enough complaining, I'll stick my kneck out and volunteer to do
this job if people really want it. I don't want to spend my time working
on this only to find the next official release doesn't use it. 

If this is desired then let me know. Some way of co-ordinating it will
be necessary. The only problem I have is that I don't have internet
access so uploading my changes will take time since I'll have to use
kermit. If anyone can get around this problem then let me know.

-- 
  Paul Richards at Cardiff university, UK.

  spedpr@uk.ac.cf.thor	Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk
  UUCP:     spedpr@thor.cf.UUCP or ...!uunet!mcsun!ukc!cf!thor!spedpr
+++
From: 2hsjaway@kuhub.cc.ukans.edu
Newsgroups: comp.unix.bsd
Subject: Need advice about book in BSD-UNIX
Date: 10 Apr 92 01:33:03 CDT
Organization: University of Kansas Academic Computing Services

Hi everybody,
	I feel very motivated to learn BSD-UNIX.  I am planning
to take a course in UNIX here at "KU - Kansas University" very soon.
In the meantime, I would like to start reading something, and maybe
doing some programming in "C" or practice exercises in order to get
acquainted with BSD-UNIX.  I heard that they have BSD-UNIX installed 
over here at the Engineering School, so I hope I will be able to do 
something.
	I would like to know from the BSD-UNIX experts out there,
which books or book you recommend for a beginner in the BSD-UNIX world.
	Thank you in advance for any help.
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rubens S. Gomes                                The University of Kansas
E-Mail : smpt%"RGOMES@tesla.ece.ukans.edu"     Department of Electrical
US-Mail: 6 Bagley Drive # 10                   and Computer Engineering
         Lawrence, KS 66044
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: jot@hera.ifi.unit.no (Jo Torsmyr)
Newsgroups: comp.unix.bsd
Subject: Re: Bug fix coordination
Date: 10 Apr 92 19:07:29 GMT
Organization: Dep. of Comp. Sci., Univ. of Trondheim

In article <1191@alderan.sdata.de>, chris@alderan.sdata.de (Christoph Splittgerber) writes:
|> In article <1992Apr3.141000.8354@ugle.unit.no> jot@zevs.ifi.unit.no (Jo Torsmyr) writes:
|> 
|> >I would appreciate any suggestions for organizing patchleves!
|> 
|> Maybe we should send our patches to somebody by email who is collecting
|> them. Then this somebody passes the patches to a few other people to
|> validate them and then put them together to an "official" patch assigning
|> a official patch-number and post it to this group.

I have been told that Bill Jolitz have got most of the patches posted
to this group and that they will be included in the next release. So
a coordination of patches may not be required (at least yet). I think
your scheme for organizing the patches looks good. "The few other people"
could have been a group of gurus responsible for patches to certain
parts of the sources (at least some kind of grouping of patches
could have been useful). There shouldn't be to difficult to create
such a group, there are already some who have posted several patches
and are good candidates... Do I hear any names?? :-)
|> 
|> IMHO it is a very important thing to get organized as fast as possible.

Agree, before the patches get too difficult to handle.
|> 
|>                   Chris

-jo

|> -- 
|> ******************** It's not a bug, it's a feature !!! ********************
|> Replies-To:  chris@alderan.sdata.de    UUCP: uunet!mcsun!unido!alderan!chris 
|> Phone:       +49 711 344375            Fax:  +49 711 3460684

-- 
Jo Torsmyr
Department of Computer Science
College of Arts and Sciences
University of Trondheim, Norway		FAX: +47 7 59 17 33
Email: jot@ifi.unit.no			Voice: +47 7 58 88 79
From: leendert@cs.vu.nl (Leendert van Doorn)
Newsgroups: comp.unix.bsd
Subject: Re: List of known partition IDs
Date: 7 Apr 92 16:24:03 GMT

In case you're interested, this is my list.

	Leendert
------------------------------------------------------------------------------

>From: leendert@cs.vu.nl (Leendert van Doorn)
Newsgroups: comp.sys.ibm.pc.misc,comp.os.minix,comp.unix.sysv{2,3}86
Subject: partition table - system indices revisited
Date: 18 Oct 90 10:55:12 GMT
Organization: Fac. Wiskunde & Informatica, VU, Amsterdam

About two weeks ago I send out a request for partition table system
indices, and here are the responses. If there is enough interest, I
will maintain this table.

	Mnemonic	ID	Description
	----------------------------------------------------------
	DOS-12		0x01	MS-DOS, 12-bit FAT
	XENIX / 	0x02	Xenix root
	XENIX /usr	0x03	Xenix user
	DOS-16		0x04	MS-DOS, 16-bit FAT
	DOS-EXT 	0x05	MS-DOS Extended
	DOS-BIG 	0x06	MS-DOS Large
	HPFS		0x07	OS/2 High Performance File System
	QNX		0x07	QNX
	AX		0x07	Advanced Unix
	AIX		0x08	A/IX
	AIX boot	0x09	bootable A/IX partition
	OPUS		0x10	Opus
	VENIX/286	0x40	Venix 80286
	NOVELL		0x51	possibly Novell
	CP/M		0x52	CP/M
	386/IX		0x63	386/IX
	UPORT/386	0x63	Microport's V/386
	NOVELL		0x64	Novell
	PC/IX		0x75	PC/IX
	MINIX-OLD	0x80	pre 1.4b Minix
	MINIX		0x81	Minix partition
	AMOEBA		0x93	Amoeba
	BADBLK		0x94	Amoeba's bad block partition
	CCP/M		0xDB	Concurrent CP/M
	DOS-SCND	0xF2	Second Dos partition, some 3.2 and all 3.3+
	BADTRK		0xFF	Bad track table

Having composed this list, I'm still stuck with the following questions:

The system index 0x07 seems to be very popular, at least three systems
are using it (OS/2, QNX, and AX). This seems weird, I would expect that
at least in these lower regions there would be some coordination.

If the system index 0x63 (386/IX and UPORT/386) actually a generic system
ID for V/386 ?

The DOS-SCND partition is odd, at least I've never seen it before. Could
somebody check this out, please ?

Does any body know the format of the bad track table (0xFF) ?

Thanks to ge@dutlru1.tudelft.nl, john@jwt.UUCP, mitchell@mdi.com,
stevesa@beaver.cs.washington.edu, and tmh@prosun.first.gmd.de.

Leendert


--
Leendert van Doorn 			   		<leendert@cs.vu.nl>
Vrije Universiteit / Dept. of Math. & Comp. Sci.	+31 20 5484477
Amoeba project / De Boelelaan 1081A
1081 HV Amsterdam / The Netherlands
From: ferrick@acsu.buffalo.edu (Patrick K. Ferrick)
Newsgroups: comp.unix.bsd
Subject: Re: The great BSD name-off...
Date: 13 Apr 92 16:47:09 GMT
Distribution: usa
Organization: UB


There's something that's been sort of bothering me about some of the name
suggestions I've seen posted lately, and I wonder if anyone else agrees: I'd
prefer that whatever name gets chosen doesn't include the word "free" or
suggest it.

Of course, the "freeness" is why we're all so excited about it, and that's
great.  But let's keep in mind that it's only free because a LOT of people
have put an enormous amount of work into creating it.  The Jolitz clan is at
the head of the list, and it is obvious that many other talented people are
keeping themselves quite busy also.

What I'm getting at is that calling it FreeB or whatever, while very clever,
tends to discount all this effort.  "Free" makes it sound like it isn't worth
much to begin with.  I think that most would agree that this is about as far
from a "you get what you pay for" situation as it possibly could be...we'll
all (hopefully) be using 386/BSD for a long, long while.  

IMHO,
pat
From: keithe@sail.LABS.TEK.COM (Keith Ericson)
Newsgroups: comp.unix.bsd
Subject: Re: To make 386bsd coexist with DOS partitions??
Date: 8 Apr 92 22:51:18 GMT
Organization: Tektronix, Inc., Beaverton,  OR.

In article <1992Apr8.142645.21143@newshub.sdsu.edu> turtle@newshub.sdsu.edu (Andrew Scherpbier) writes:

>I have been looking at the xxboot and bootxx code to see how easy/hard this
>would be, but right now I am working on a new console driver.  So if someone
>else wants to take on the task of writing a new boot loader, we should
>exchange some ideas.

Look on the SIMTEL20 archive machine (or a mirror) in the sysutl directory
for a file called bootany.zip.  It contains a complete system to re-groove
the boot record as you describe (hit a Function key to select the partition
you want to boot from), and source is included...

(help *) KEITHE()
Keith Ericson @ TekLabs
keithe@sail.labs.tek.com
From: james@raid.dell.com (James Van Artsdalen)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD - I solved my boot problem
Date: 6 Apr 92 23:21:26 GMT
Reply-To: james@raid.cactus.org (James Van Artsdalen)
Organization: Dell Computer Co

> (It may be of interest to note that my current HD controller had problems
> at bus speeds > 10MHz.  I run my current bus at 8MHz and it works, but
> my boot problems might've been due to marginal timings on the controller...)

I *strongly* encourage people not to change the ISA bus clock away
from 8 MHz (or 6 MHz).  Very few peripherals actually work that fast.
Perhaps some hard disk controllers do, but that's only one of a dozen
things hanging off of that bus (keyboard controller, VGA, etc).

As the clock speed increases, things will gradually begin to fail.
The system won't just work or not work: it is a question of how many
failures per hour, how long after power is applied before the parts
warm up an start to fail more often, and so forth.  This is no magic
sign that says that the system is within tolerance on the clocks or
not.

This is especially true of IDE drives.  Many IDE drives (Connor,
Maxtor) are technically out of spec at 8 MHz, and work only because
the CPU & local bus aren't able to do back-to-back ISA cycles.  If you
have a really fast local bus, and a fast CPU, it's likely that IDE
drives will have trouble.

(On the outermost tracks, where the data rates are fastest on IDE
 drives, most IDE drives need about 550 ns to 600 ns per read.  But a
 33 MHz 486 with a fast local bus might only give you 500 ns per read
 during a "rep insw" on an 8 MHz ISA bus)

I haven't looked at specsheets on seagate or quantum - perhaps they're
faster if they use different chipsets on the drive.  I would check the
datasheet first.
-- 
-- 
James R. Van Artsdalen          james@bigtex.cactus.org   "Live Free or Die"
Dell Computer Co    9505 Arboretum Blvd Austin TX 78759         512-338-8789
Newsgroups: comp.unix.bsd
From: jfc@athena.mit.edu (John F Carr)
Subject: Re: What happens if you have both BSD/386 and 386BSD?
Organization: Massachusetts Institute of Technology
Distribution: usa
Date: Wed, 8 Apr 1992 13:40:46 GMT

In article <1992Apr7.224109.7413@pony.Ingres.COM>
	thomasm@Ingres.COM (tom markson) writes:

>Furthermore, I believe that BSDI CANNOT tell you that you can't
>redistribute code copyrighted by the regents, only the original code
>produced at BSDI.

I see nothing in the Berkeley copyright notice that prevents restrictions on
redistribution, so you are bound by the license you signed when you bought
the source from BSDI.  You won't be violating copyright if you copy a file
that BSDI did not modify, but you might be violating your license agreement.

--
    John Carr (jfc@athena.mit.edu)
Newsgroups: comp.unix.bsd
From: karl@NeoSoft.com (Karl Lehenbauer)
Subject: Re: 386bsd & NFS??
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Fri, 10 Apr 1992 20:44:38 GMT
Keywords: 386bsd NFS

We're running NFS under 386BSD here at NeoSoft, and it's working great.

The NFS option needs to be defined in the configuration file, as you've
done.  Then look at /etc/rc -- you need to run some of the commands in
there to get the network and NFS daemons fired up.  

Note that the default shell doesn't recognize the "if [ ]" syntax.  You'll
have to use bash or modify the script to do "if test ..." instead.

-- 
-- Email info@NeoSoft.com for info on getting Internet access.
     "Trust me.  I know what I'm doing." -- Sledge Hammer
Newsgroups: comp.unix.bsd
From: radel@ravel.udel.edu (Todd Radel)
Newsgroups: comp.unix.bsd
Subject: No 80387???  Any hope?
Date: 17 Apr 92 13:06:56 GMT
Organization: University of Delaware

I remember reading a while back that the only two programs requiring a 387
on the distribution floppy were fsck and newfs.  If I were to recompile
those 2 utilities, could I get 386BSD installed?  Does anything else require
a 387?  And assuming the answers are "yes" and "no", how would I create
a new distribution floppy with the new versions of fsck and newfs?

AdvTHANKSance to all who respond...

-- Todd


-- 
* Todd Radel                      Sysop, Dickinson Domain BBS                *
| CIS/English                     FidoNet: 1:150/160; VirtualNET @3023       |
| University of Delaware          REGISTERED Alpha Colony VI!                |
*         "You don't need to be crazy to be a sysop, but it helps!"          *
Newsgroups: comp.unix.bsd
From: thomasm@Ingres.COM ()
Subject: uugetty in BSD?
Date: 15 Apr 92 22:00:44 GMT

Has anyone come up with anything that resembles the AT&T uugetty for BSD?
I've picked up the enable/disable [port] source from the comp.sources.unix
archives and this is very useful but still not quite as good as uugetty -
which respects the uucp locking convention (LCK..com1).

Thanks in advance!
--
Tom Markson					Unix Systems
email: thomasm@ingres.com			Ingres Corp
From: acmrlb@gsusgi1.gsu.edu (Ronald L. Bolin)
Newsgroups: comp.unix.bsd
Subject: Need wtreg.h for 386BSD
Keywords: Missing 386BSD Header File
Date: 15 Apr 92 02:46:01 GMT
Distribution: usa
Organization: Georgia State University

Would someone who has the /usr/src/sys.386bsd/i386/isa/wtreg.h header file from
the 386BSD sources please e-mail me the header file.  I can't find
it anywhere even on the 3-17-92 floppies.  Or tell me where I can FTP it.

Thank's in advance.

Ron
From: pk@cs.few.eur.nl (Paul Kranenburg)
Newsgroups: comp.unix.bsd
Subject: Re: ps/sps
Date: 10 Apr 92 20:35:48 GMT
Reply-To: pk@cs.eur.nl
Organization: Erasmus University Rotterdam

In <1992Apr8.201650.18412@ugle.unit.no> jot@zevs.ifi.unit.no (Jo Torsmyr) writes:

>I dare ask this questions even though they're simple to
>answer (when you know the answer...).

>I've 'ps' and 'sps' up and running. So far all well, but
>'ps' gives me this warning message every time:

>warning: no device database /var/run/dev.db

>And that's correct, I have no such file. So -- how do one create
>this file?

Run `/usr/sbin/dev_mkdb'.

>'sps' says:

>sps - Can't read struct pgrp for ttypX

>where X is any number 1,2,3... I have initialize 'sps' with
># sps -i -s /386bsd
>(or something like that), any idea anyone?

You probably have a kernel with only a few pty's (2 or 4), but
more than that number as entries in /dev. This causes sps to try
and read the tty structs of pty's which aren't there.

[BTW. I wasn't able to boot a kernel with more than a few pty's (like 32)
Is there a limit to the BSS segment of the kernel as all of those statically
allocated ring-buffers take up a lot of space?]

-Paul.
From: torek@horse.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.bsd
Subject: scheduling (was Experiences with 386BSD)
Date: 11 Apr 1992 04:52:08 GMT
Organization: Lawrence Berkeley Laboratory, Berkeley
Reply-To: torek@horse.ee.lbl.gov (Chris Torek)
NNTP-Posting-Host: 128.3.112.15
Keywords: 386BSD

In article <dirkst.702913777@rama> dirkst@rama.informatik.rwth-aachen.de
(Dirk Steinberg) writes:
>I found out that the following program locks the machine ...
>null.c:		main () {while (1) ;}
>... The scheduling seems to be non-preemptive!?

This suggests that ASTs are (still) broken.

The BSD kernel calls for rescheduling from interrupt handlers (such as
the scheduling clock) using the macro

	need_resched()

which is typically defined as something like

	/*
	 * Preempt the current process if in interrupt from user mode,
	 * or after the current trap/syscall if in system mode.
	 */
	extern int want_resched, want_ast;
	#define need_resched() (want_resched = 1, want_ast = 1)

On the VAX, instead of `want_ast = 1', you use `mtpr(ASTLVL,
ASTLVL_USER)' to get a hardware AST before returnign to user mode.
Then, on the way out of trap(), the kernel can check want_resched
(atomically!) and call swtch() if appropriate.

The Jolitz 386BSD code probably does something like this, that code
having been cloned from the VAX.  On the SPARC, I simulate ASTs in the
`return from kernel mode to user mode' code in locore.s (the SPARC
needs only one path out, as all traps look the same); this lets me code
`just like a VAX'.  This is simple, effective, and reasonably efficient.
There are other ways as well, and maybe someday I will get around to
trying more of them.  (I tried using software interrupts and it came
out less efficient and messier.)
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 510 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov
Newsgroups: comp.unix.bsd