HDTenEightyP/NetNews huggingface dataset:
From: burgess@hrd769.brooks.af.mil (Dave Burgess)
Newsgroups: comp.unix.bsd
Subject: [386bsd] Kernel builder
Date: 22 Jan 1993 11:34:25 -0600
Organization: Armstrong Lab MIS, Brooks AFB TX
NNTP-Posting-Host: hrd769.brooks.af.mil

  After going through the 'Idiot's Guide to Rebuilding your kernel' (his name
not mine), I decided that the process was reasonably well defined and could
stand to be put into a simple script.  I have done that.  It is included
below, and makes a new kernel using the existing software, Makefiles, etc.
The program defaults to GENERICISA as the configuration file to edit, or 
will accept an environment variable called CONFIG_NAME which should contain
the name of your configuration file, or will accept an argument which will
override the CONFIG_NAME variable.  I started using this when I was building
a new kernel for a friend of mine that needed to have different options
enabled than I needed.  also, since I am one of those folks that keeps a
bunch of weird kernels around, I decided that the last step should be
manual.  Check it out.  E-Mail me with improvements or questions.

TSgt Dave Burgess
NCOIC AL/MIS
Brooks AFB, TX
----------------------------- Cut Here -----------------------------------
# This is a shell archive.  Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file".  Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
#	/usr/local/bin/build.kernel
#
echo x - /usr/local/bin/build.kernel
sed 's/^X//' >/usr/local/bin/build.kernel << 'END-of-/usr/local/bin/build.kernel'
X:
X#
X#  Script to rebuild the kernel.
X#
Xif [ `whoami` != 'root' ] ; then
X  echo 'You must be root to proceed from this point'
X  exit 1
Xfi
X
X#
X# Rebuild Config
X#
X
Xcd /usr/src/usr.sbin/config
Xmake depend
Xmake
Xmake install
X
X#
X# Modify the local Configuration File
X#
X
Xif [ "X$CONFIG_NAME" = "X" ]; then
X  CONFIG_NAME=GENERICISA
Xfi  
X
Xif [ "X$1" != "X" ]; then
X  CONFIG_NAME=$1
Xfi
Xcd /sys/i386/conf
X
Xif [ ! -f $CONFIG_NAME ]; then
X  cp GENERICISA $CONFIG_NAME
Xfi
X
Xecho `tput clr`
Xecho "Modifying $CONFIG_NAME config file"
Xecho -n "Press return to continue"
Xread ans
X
Xvi $CONFIG_NAME
X
Xconfig $CONFIG_NAME
X
Xcd /sys/compile/$CONFIG_NAME
Xmake newvers
Xmake depend
Xmake
X
Xecho `tput clr`
Xecho ""
Xecho "  Manual Installation is recommended.  The following files should be"
Xecho "copied/linked/moved to the root directory.  The following steps are"
Xecho "suggested:"
Xecho ""
Xecho "	mv /386bsd /386bsd.old"
Xecho "	mv  386bsd /386bsd"
Xecho "	reboot"
Xecho ""
Xecho "Remember that the new kernel changes will not take place until you "
Xecho "re-boot the system."
END-of-/usr/local/bin/build.kernel
exit

Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: Re: [386BSD] Hang compiling xterm with patch kit 2
Organization: TRW Financial Systems, Berkeley, CA - 94704
Date: Tue, 26 Jan 1993 23:47:27 GMT

In article <C1HC8t.28n@world.std.com> hd@world.std.com (HD Associates) writes:
>I get a disk subsystem hang ld'ing xterm on 386bsd.  I've applied
>the new patch kit hoping it would fix things, but doesn't.  The system
>continues to run, and if I have things running in the background
>such as "leave" or the window manager they continue to function
>until they have to use the disk.
>
>I'm using Julian's SCSI system on a Micronics 486VL mother board, 16MB
>memory with Adaptec 1542B and two CDC/Seagate roughly 300 MB drives.
>
>I've copied the xterm directory onto my first drive, rebooted single user
>and verified it still hangs, eliminating the case of a funky file system
>and broken code.
>
>The first thing I ask myself is where the processes are sleeping.  Is there
>any way to dump the process table from the debugger?

There is.
I am pleased to be able to tell you that the command
'call ddb_ps' will print out a ps-like listing. 

now the bad news:
the process you want is nearly always off the top of the screen.

the ddb docs on agate (in unofficial) intimate that there is a 'more mode'
but I don't know how to make it do that yet.

>

julian
+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\
	  v
From: bob@prepress.com (Robert Crowe)
Subject: Re: Adaptec 1542/386BSD compatible CD-ROM drives
Organization: Pre-Press Technologies, Carlsbad Ca.
Date: Thu, 21 Jan 1993 17:35:39 GMT

In article <19581@smoke.brl.mil> lesh@smoke.brl.mil (Steve Lesh) writes:
>
>	Any recommendations of CD-ROM drives which work with the Adaptec 1542
>under 386BSD 0.1 would be appreciated.  (I've already tried one "SCSI" drive
>which the Adaptec firmware -3.10- would not recognize -- an NEC CDR-25BJ.)

I got curious and pulled a toshiba XM-3301b off a sparcstation at work,
stuck it on my 486 w/ 1542b, and it worked just fine.  Note that I have
installed Jullian's scsi driver -- That probably makes a difference.  I have
not tested it a whole lot, since I didn't have too much time, but it seemed
to work just fine.

>	More generally, lots of people seem to have been collected information
>about 386BSD-compatible hardware but I haven't seen any posted lists.  Could
>someone provide a pointer?

Wish I knew...


Good luck,

Bob.
-- 
============================================================
Bob Crowe                      Voice:   (619) 931-2695
Pre-Press Technologies.        Email:    bob@prepress.com
2443 Impala dr.		       FAX:     (619) 931-2698
Xref: sparky comp.unix.bsd:11969 comp.sys.ibm.pc.hardware:37524
From: nan@matt.ksu.ksu.edu (Nan Zou)
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.hardware
Subject: Re: ATI Mach32 and Xfree86 or XS3?
Date: 28 Jan 1993 20:49:49 -0600
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

johng@informix.com (John Galloway) writes:
>hasty@netcom.com (Amancio Hasty Jr) writes:

>>The ATI Mach32 is based upon ATI's mach32 chipset.
>>for speed I suggest acquiring a 928 based card which is faster than the
>>ATI MACH32 by as much as 34% overall graphics performace, even on the ISA :-)

>Any info on cards that are using the 928 that are available?

I have a fax here from Diamond that gives some info on their Stealth Pro
card which is based on the S3 86C928.  It can take a maximum of 2 MB of
VRAM, resolutions of 640x480x24, 800x600x24, 1024x768x16, and 1280x1024
x8, all with 72 HZ non-interlaced refresh.  They quote 35 Million 
Winmarks on a 66 Mhz DX2, of course this is still quite far behind their
50 Million Winmark Viper card which is based on the Weitek P9000 chip,
but since the Weitek chip just appear I wouldn't expect a X server
being written for it any time soon, so for now, the 928 seems like the
best choice.  According to Amancio Hasty, the 928 should be able to do 
120K Xstones, versus the ATI Ultra Pro's 100K, this pretty much agrees 
with the Winmark ratio, 35M versus 28.5M for the ATI, now if there does
exist a positive correlation between Xstone ratios and Winmark ratios,
we can probably expect 170K Xstones from a Weitek P9000 based-card. WOW!

Of course, I will never recommend anyone to buy a Diamond product,
because of their use of variable clock synthesizer and refusal to
disclose programming info without much money.  Some Linux folks have
been complaining about unneeded hassles with Diamond video cards, so I'd
say stay away from them.

Now if you also want to run OS/2 then the ATI seems pretty attractive,
since it's register-compatible with IBM's 8514/A, you can expect at
least some support in OS/2, I don't think there's much support for the
S3 chips in OS/2 PM (other than standard VGA).

>>Going to a local bus card will not buy you significant performance 
>>improvement, at least with the S3 chipsets.

If I understand correctly, with smart graphics coprocessors like the S3
and ATI chips, the higher bandwidth of local bus won't help you much
unless you're doing offscreen to video memory copies, in which case the
local bus will gain significant advantage over an ISA bus.

-- Nan
From: gene@stark.uucp (Gene Stark)
Newsgroups: comp.unix.bsd
Subject: Patch00022 is still wrong
Date: 26 Jan 93 19:13:47
Organization: Gene Stark's home system
Distribution: world
NNTP-Posting-Host: stark.uucp

Patch00022 (a patch to init.c from back in the dark ages) is still wrong in
the new patchkit.  It was correct in the diffs originally posted last summer,
but it has never been correct in the patchkit.  In the lines:

--- 226,233 ----
  			_exit(127);
  		}
  		while(wait(&status) != pid)
+ 		while(drain)				/* 31 Jul 92*/
+ 			pause();
  		goto top;
  	}

The first "while" statement should end up having a semicolon at the end of the
line.  If it is not there, then if fsck fixes disk problems during boot up,
during the subsequent reboot, init starts to bring the system up multi-user,
resulting in a disk "sync" and an infinite reboot cycle.

							- Gene Stark
From: prang@du9ds4.fb9dv.uni-duisburg.de (Juergen Prang)
Newsgroups: comp.unix.bsd
Subject: Re: kernal switcher?
Date: 26 Jan 1993 10:30:12 GMT
Organization: Universitaet Duisburg GH
NNTP-Posting-Host: du9ds4.fb9dv.uni-duisburg.de
X-Newsreader: TIN [version 1.1 PL8]

In comp.unix.bsd Alex R.N. Wetmore (aw2t+@andrew.cmu.edu) wrote:
: Is there any sort bootstrap for 386bsd that will let me choose which
: kernel to boot up (so it would boot 386bsd by default, but I could make
: something like 386bsd.x if I wanted to run X).  I would like to run the
: pcvt console driver, but I also use X sometimes (rarely, but enough that
: I don't want to trash it).  So, it would be nice to have two kernels
: compiled, one that runs pcvt, and one that doesn't so that I can run X.

: Otherwise I guess I could write a shell script that just linked the
: appropriate kernel to 386bsd and rebooted, but this would be nicer.

Some months ago Julian Elischer posted a port of the Mach bootloader which
serves your needs.
One location where you may find this posting is

ftp.uni-duisburg.de:  /pub/unix/386bsd-0.1/unofficial/patches/boot.block
login: anonymous,  password: FULL e-mail address

Hope this helps
Juergen
--
   Juergen Prang           |     prang@du9ds4.fb9dv.uni-duisburg.de
   University of Duisburg  | 
   Electrical Engineering  |       (intentionally left blank)
   Dept. of Dataprocessing |          (no cookie available)
Newsgroups: comp.unix.bsd
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: Re: Can I boot from 3.5" 1.44 MB disks?
Organization: Nanyang Technological University - Singapore
X-Newsreader: TIN [version 1.1 PL8]
Date: Thu, 28 Jan 1993 02:18:27 GMT

Christoph Kukulies (kuku@acds.physik.rwth-aachen.de) wrote:

: I tried - to no avail - to produce a booatble 3.5" floppy
: because one of the next system I will feed with 386bsd only has 3.5" drives.
: Also I wanted to build a disk a la fixit.fs containing necessary 
: programs to bootstrap the rest of the system from a running node via
: rrestore (if anyone has a better idea how to automate and speedup
: remote installation of 386bsd in a network his/her ideas would be heartly welcome)

: Anyway - the essential question: Why does my 3.5" disk not boot? I make a disklabel and newfs on it and put a kernel and some stuff to live on it,
: but I would at least expect, that the bootstrap is entered - I tried with 
: both versions of fdboot (the original and Julians)

I was able to boot using 3.5" disk that contains an image of the 1.2Mbyte
dist.fs of the 386bsd 0.0 .

I've not tried the 0.1 version yet but I see no problem.

--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet
From: burgess@hrd769.brooks.af.mil (Dave Burgess)
Newsgroups: comp.unix.bsd
Subject: Re: Need answers to few questions not found in FAQ
Date: 28 Jan 1993 11:04:34 -0600
Organization: Armstrong Lab MIS, Brooks AFB TX
NNTP-Posting-Host: hrd769.brooks.af.mil

In article <0fNPCE600V8_83unxU@andrew.cmu.edu> "N. R. Natraj" <nn07+@andrew.cmu.edu> writes:
|I have a few questions that I was not able to get the answer out from
|the FAQ list and I am not a Unix pro. I have the following machine
|
|Gateway 2000 486 DX 33, 12M RAM, 325 meg hard drive (80 for DOS and the
|rest for 386BSD), MS serial mouse.
|
|1. How do I setup swap space? Do I just edit the fstab file to add the
|correponding device and use swapon in my config file? Do I have to edit
|the disklabel too?
|

  I can answer Question 1.

  You already answered this question in the rest of the question.
  Yes.
  Yes.

  I expect you will get an answer to the other two shortly.

-- 
------
TSgt Dave Burgess
NCOIC AL/Management Information Systems Office
Brooks AFB, TX
From: dgreen@sti.com (Dan R. Greening)
Newsgroups: comp.unix.bsd
Subject: [386BSD]  BUG in 0.1/0.2:  How to configure IRQ on NE1000 boards?
Date: 25 Jan 93 22:07:11 GMT
Organization: Software Transformation, Inc.
NNTP-Posting-Host: jeff.sti.com

I have 386BSD 0.1 running on my little 386, my initial kernel is from
dist.fs-patchkit-0.2, though dist.fs works the same way.  Unfortunately 
I cannot get it to run correctly on the NE1000 or NE2000 boards that 
I have tried.

Each time it comes up with 

ne0 ethernet address xx:xx:xx:xx:xx:xx at 0x300 irq 9 on isa

The xx:xx:xx:xx:xx:xx comes up with the correct number.  0x300 is right.
The IRQ number is crazy because ne1000 and ne2000 boards from Novell CANNOT 
be set to IRQ 9.  The default is IRQ 3, which is what we leave it at in 
every 386 we have (and we have tons).  

Is there a way to configure 386bsd to default to IRQ 3 for NE 1000/2000 
boards?  I have the bindist, and after hunting around I think that bindist
doesn't come with configuration files (at least not where "man config"
tells me they should be).

Can you give me a way to patch the kernel to stick the NE1000/2000 at IRQ 3?
Could someone actually fix this in the next release so at least the IRQ 
number used is feasible?  (Really you *ought* to put the NEx000 at IRQ 3
address 0x300, where it is set at the factory.)  As far as I'm concerned,
this is a bug (and a very annoying one, at that, since you can't use the
network to download the rest of your distribution).

Thanks for your help.
-- 
____
\  /Dan Greening    Software Transformation   1601 Saratoga-Sunnyvale Rd, #100
 \/dgreen@sti.com   (408) 973-8081 x313       Cupertino, CA 95014
Newsgroups: comp.unix.bsd
From: sl@wimsey.bc.ca (Stuart Lynne)
Subject: Re: [386BSD] Problem with WD8013 card!
Organization: Wimsey Information Services
Date: Thu, 28 Jan 1993 09:14:06 GMT
Keywords: 386BSD ethernet 8013 problem bug

In article <C18MwH.5Aq@rot.qc.ca> captain@rot.qc.ca (Andrew Webster) writes:
>Hi...
>Just a little backgroud:
>I'm tring to get 386BSD to talk to my ISC3.0 box but so far only slip works!
>
>I just recently aquired 386BSD, and have been installing it.  The documentation
>mentions that it supports western digital (SMC) network cards.  I have such
>a beast, and 386BSD does indeed detect the card upon boot-up.  However
>after configuring it with:
>ifconfig we0 192.1.1.2 netmask 255.255.255.0 broadcast 192.1.1.255
>and: route add default 192.1.1.1 
>ping 192.1.1.1 does nothing (NADA) the activity lights on the card don't
>even flash.  Going the other way (ISC3.0->386BSD ping makes the RX light
>flash on the card but it seems to be ignoring the packets.)

I have a similiar problem using an older WD8003. The card is configured to
the default address and is detected on boot. 

I've tried the above ifconfig and route command (with my IP address) and 
variations with little success. Ftp reports a timeout.

I do get a message on the BSD machines console "reject 65531" repeated
as it see's pings or other packets addressed to it.

-- 
Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software
Wimsey Information Technologies ................... moderator biz.sco.binaries
uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z
PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.hardware
From: adhir@wam.umd.edu (Al Dhir)
Subject: Re: ATI Mach32 and Xfree86 or XS3?
Organization: University of Maryland, College Park
Date: Wed, 27 Jan 1993 04:48:56 GMT

So are there any 928 S3 adapters with an EISA bus interface and (here's the
catch) with OS/2 drivers?

Any info is appreciated...

Oh, another question - do the newer S3 cards have faster DOS & VGA speed or
are they still notoriously slow?  If they're still slow, will it be possible
for me to continue using my Orchid PDiis card for VGA and use the S3 for
SVGA?

Thanks
-- 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Al Dhir                      			   Technical Consulting Staff
 Internet: adhir@cygnus.umd.edu	  	 University of Maryland, College Park
 Bitnet:   adhir%cygnus.umd.edu@Interbit      (301) 405-1500 * (301) 405-3014
Newsgroups: comp.unix.bsd
From: ac116@city.ac.uk (Tarkan)
Subject: [386BSD] how do i get gcc to work on 386BSD
Summary: how do you compile a compiler?????
Keywords: gcc 386BSD compile help
Organization: The City University
Distribution: comp
Date: 21 Jan 93 14:22:51 GMT

Can anyone help me get gcc working on my 386BSD Box,,
I've got gcc-2.3.3 source but Have no idea on how you are meant to 
install ,compile, or how to get a compiler to compile it,,
After reading all the Documentations
and could anyone suggest how i could compile gcc-2.3.3 using
a sparc 1 running gcc,,,,and can anyone recommend how to setup
the Makefile and The configure file to get to work painlessly

Tarkan


-- 
************************************************
* if you haven't guessed yet...                *
*         				       *
*  Tarkan....(or Bambi )                       *
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Install Via SLIP and FTP
Organization: Weber State University  (Ogden, UT)
Date: Thu, 28 Jan 93 17:48:26 GMT

In article <nizar.728176011@loki.ECE.Concordia.CA> nizar@loki.ECE.Concordia.CA (Nizar Sabra) writes:
>>ifconfig sl0 128.173.19.25 128.173.16.1 netmask 255.255.252.0
>
>	This might be daft, but is that 252 supposed to a 255?

Only on a Class C.  This is probably a Class B with subnetting -- the
implication being a 6-bit primary address and a 10-bit subnet address.
Note that 252 is the upper 6 bits set and the lower 2 bits not set.  This
could make some hardware puke, but it's not all that unusual a configuration;
there will be a problem, however, with domain-based MX records -- I believe
sendmail.mx expects it divisions to be on 8-bit boundries.  Not a problem
if a domain mail gateway is used.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: hackney@twisto.eng.hou.compaq.com (Greg Hackney)
Subject: Re: 386BSD work with Compaq Fast-SCSI-2 controller ?
Organization: Compaq Computer Corp.
Date: Tue, 26 Jan 1993 21:47:36 GMT

fontenot@ravl.rice.edu (Dwayne Jacques Fontenot) writes:

> Does 386BSD work with the Compaq Fast-SCSI-2 controller as available in
> the new ProSignia server?

I don't know about the ProSignia. So far I haven't been able to get 386BSD
to work FAST-SCSI-2 on a Compaq 486/50 XL, but am still trying. My problem
is that the SCSI-2 controller can't be configured as a primary controller
(yet), so you can't boot off it.

I think I will be able to use the floppy boot from ref.tfs.com to specify
the SCSI device to boot from.

Meanwhile, my system will definitely run 386BSD SCSI with an Adaptec 1542B
controller thrown in it.
--
Greg Hackney
hackney@compaq.com

Disclaimer: These are my personal views & not necessarily Compaq's.

-- 
Signature line 1
Signature line 2
Signature line 3
Signature line 4
Signature line 5
Signature line 6
Signature line 7
Signature line 8
From: lessen@axion.bt.co.uk (Lee Essen)
Newsgroups: comp.unix.bsd
Subject: BSD Books
Date: 22 Jan 93 11:33:14 GMT
Reply-To: lessen@axion.bt.co.uk (Lee Essen)
Organization: British Telecom Research Labs


Can anyone give me some details on the following books, I've tried getting
hold of them but the book shop says they can't find any reference to them.

Design of the Unix Operating System (Bach)

Design and Implementation of 4.2BSD (Leffler?)

I'de like to know UK publisher, ISBN, or better still a UK source where
I can get hold of them.

Thanks in advance,

Lee Essen.
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Any 386BSD FAQ???
Organization: Weber State University  (Ogden, UT)
Date: Sun, 24 Jan 93 00:12:35 GMT

In article <1993Jan21.183107.10692@lth.se> dat92bro@ludat.lth.se (Bjarne Rosengren) writes:
>I haven't found any FAQ file. 
>Does it exist???

Check my signature.  It's on agate,berkeley.edu.

I am in the rocess of updating it and will have a new one soon (note that
"soon" is a relative term, and I'm not giving a date).


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.

-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
From: gene@stark.uucp (Gene Stark)
Newsgroups: comp.unix.bsd
Subject: Xten and patch00061 (FIX)
Date: 26 Jan 93 08:53:43
Organization: Gene Stark's home system
Distribution: world
NNTP-Posting-Host: stark.uucp

These patches are for my "tw" X-10 driver, which can be found on ref.tfs.com
in directory /usr/src/sys.extras/stark-xten.

You MUST apply these diffs if you have installed patch00061 in patchkit-0.2.
DON'T apply them if you didn't install that patch.


*** /sys/i386/isa/tw.c.pl1	Wed Dec  2 09:31:20 1992
--- /sys/i386/isa/tw.c	Tue Jan 26 07:56:30 1993
***************
*** 199,205 ****
  struct tw_sc {
    u_int sc_port;		/* I/O Port */
    u_int sc_state;		/* Current software control state */
!   struct proc *sc_selp;		/* Process sleeping on select */
    u_char sc_xphase;		/* Current state of sync (for transmitter) */
    u_char sc_rphase;		/* Current state of sync (for receiver) */
    u_char sc_flags;		/* Flags for current reception */
--- 199,205 ----
  struct tw_sc {
    u_int sc_port;		/* I/O Port */
    u_int sc_state;		/* Current software control state */
!   pid_t sc_selp;		/* Process sleeping on select */
    u_char sc_xphase;		/* Current state of sync (for transmitter) */
    u_char sc_rphase;		/* Current state of sync (for receiver) */
    u_char sc_flags;		/* Flags for current reception */
***************
*** 411,416 ****
--- 411,417 ----
       struct proc *p;
  {
    struct tw_sc *sc;
+   struct proc *pp;
    int s, i;
  
    sc = &tw_sc[TWUNIT(dev)];
***************
*** 419,428 ****
      splx(s);
      return(1);
    }
!   if(sc->sc_selp && sc->sc_selp->p_wchan == (caddr_t)&selwait) {
      sc->sc_state |= TWS_COLL;
    } else {
!     sc->sc_selp = p;
    }
    splx(s);
    return(0);
--- 420,430 ----
      splx(s);
      return(1);
    }
!   if(sc->sc_selp && (pp = pfind(sc->sc_selp))
! 	&& pp->p_wchan == (caddr_t)&selwait) {
      sc->sc_state |= TWS_COLL;
    } else {
!     sc->sc_selp = p->p_pid;
    }
    splx(s);
    return(0);
Newsgroups: comp.unix.bsd