HDTenEightyP/NetNews huggingface dataset:
From: ujlh@pool.info.sunyit.edu (James Henrickson)
Subject: Re: [XFree86]  Help needed badly
Organization: State University of New York -- Institute of Technology
Date: Mon, 23 Nov 1992 00:03:09 GMT

In article <1992Nov21.063206.22717@ntuix.ntu.ac.sg> othman@ntrc25.ntrc.ntu.ac.sg (othman (EEE/Div 4)) writes:
>AZ7141633 (az7141633@v9001) wrote:
>
>: >   Mtools does not work,
>
>recompile a new one. get it from etcdist
>

I used an easier method:

su root
cd /dev
sh MAKEDEV fd0
sh MAKEDEV fd1
exit

Mtools apparently was trying to open nonexistent devices.

-- 
Jim H.
*
* James L. Henrickson  |  "I don't need a signature, I need a job!"
* ujlh@sunyit.edu      |  BSCS, December 1992
Newsgroups: comp.unix.bsd
From: masuda@rokugo.co.jp (Yoshihiro Masuda)
Subject: Re: [386bsd] can't deal with 8-bit input
Reply-To: masuda@babel.ics.nitech.ac.jp
Organization: Rokugo System ELC.,Co.,LTD.
Date: Mon, 16 Nov 1992 14:00:10 GMT

libove@libove.det.dec.com (libove@libove.det.dec.com) writes:
: In <1992Nov16.081801.15019@kum.kaist.ac.kr> jbkang@csking.kaist.ac.kr (Joongbin Kang) writes:
: >    % cat
: >    xxxx(entered korean characters -- it can be seen when typing)
: >    (but no echo to tty!)
: >    ^D (this DIDN'T work)
: >    ^C
: >    %
: >  So, what's the problem? If I cannot use hangul in 386bsd, it loses
: >  practicality...Help!
: 
: >				Joongbin Kang
: 
: Just a question: you have entered
: 	stty -istrip cs8
: didn't you?

May be,this should be work.

*** /sys/kern/tty_ring.c.orig	Sun Nov  8 18:44:44 1992
--- /sys/kern/tty_ring.c	Sun Nov  8 18:45:50 1992
***************
*** 155,161 ****
  catb(from, to)
  	struct ringb *from, *to;
  {
! 	char c;
  
  	while ((c = getc(from)) >= 0)
  		putc(c, to);
--- 155,161 ----
  catb(from, to)
  	struct ringb *from, *to;
  {
! 	register c;
  
  	while ((c = getc(from)) >= 0)
  		putc(c, to);
-- 
masuda@rokugo.co.jp
$@A}ED2BBY(J@$@O;9g%7%9%F%`EE;R9)6H(J
$@$^$9$@$h$7$R$m(J@$@$m$/$4$&$7$9$F$`$G$s$7$3$&$.$g$&(J
$@:#7n$N$*8@MU(J: $@J$?eK_$KJV$i$:(J($@2u$l$?(Jdisk $@$N%G!<%?$OLa$C$FMh$J$$(J;_;)
From: rich@Rice.edu (Richard Murphey)
Newsgroups: comp.unix.bsd
Subject: Re: [XFree86]  Help needed badly
Date: 20 Nov 92 15:53:28 GMT
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University

In article <20NOV199220254593@v9001> az7141633@v9001 (AZ7141633) writes:
   I am facing the same problem as what both Thanh Luu and S.X. Xue faced;  but I
   could not find any replies to their queries in comp.unix.bsd.
   I would appreciate if anyone could help us get started with XFree86 and 386BSD.
   Thanks in advance.

   Sok
   Internet addr:  az7141633@ntuvax.ntu.ac.sg
   With Love from Nanyang Technological Univ of Singapore


   >X-NEWS: ntuvax.ntu.ac.sg comp.unix.bsd: 7901
   >From: tpl20@pswd.amdahl.com (Thanh Luu)
   >Subject: Problem starting up X
   >Date: 13 Nov 92 17:46:56 GMT
   >
   >I installed XFree86 and the kernel patch.  When I tried to bring up X, using
   >xinit, I got the following message:
   >
   >   XIO: fatal IO error 32 (broken pipe) on X server ":0.0"
   >   after 0 requests (0 known processed) with 0 events remaining
   >   The connection was probably broken by a server shutdown or KillClient
   >
   >What did I miss to do?  Thanks in advance.

First try redirecting the output to a file so that you get all the
error messages:
	xinit >errs 2>&1
if you are using sh, or
	xinit >&errs
if you are using csh.

Then start looking at your Xconfig file.
From /usr/X386/lib/X11/etc/README.386BSD:


---------------- EDITING /usr/X386/lib/X11/Xconfig ----------------

You must edit /usr/X386/lib/X11/Xconfig to suit your hardware.  It
tells the X server what kind of monitor and adapter are present.  Read
the X386 man page and /usr/X386/lib/X11/Xconfig.sample first.

Once you understand the structure of Xconfig, try to find your
specific monitor and vga card in /usr/X386/lib/X11/etc/modeDB.txt.  If
your Clocks and ModeDB lines are there, grab the values there and put
them in your Xconfig.  If modeDB.txt does not have your hardware, read
/usr/X386/lib/X11/etc/XConfig.Notes for instructions on how to create
the video timing values given your vga card and monitor specs.  The
manual for your monitor and adapter should have these values.  To find
your clocks,  leave the Clocks line out of your Xconfig and run
'xinit >& xinit.out'.  If X386 can find your clocks, it will print
them out to xinit.out.  Given your clock frequency and horizontal
frequency of your monitor, the program xclk (on agate.berkeley.edu in
/pub/386BSD/0.1-ports/XFree86) can calculate a ModeDB line for you.

Unless you add more fonts, your Xconfig's FontPath line should be:
    FontPath "/usr/X386/lib/X11/fonts/misc/,/usr/X386/lib/X11/fonts/75dpi/"
If the FontPath includes non existant directories the server will exit
without any error messages which would give a clue to the cause.

Hope that helps!  Rich
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: m* and docs
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Fri, 20 Nov 1992 12:18:42 GMT

In article <By00HL.BJt@iat.holonet.net> richardl@iat.holonet.net (Richard Levenberg) writes:
   Are there docs or mans on the m group of executables (i.e. mread, 
   mwrite, mdir) I have used them successfully but it is a shot in the
   dark?

Look in /usr/src/othersrc/public/mtools-2.0.5/man/cat1/*.  mtools.0 is
an overview.  Rich

   richardl@holonet.net

Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: Beta/XFree86 patches, how to do both?
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Wed, 18 Nov 1992 19:52:30 GMT

In article <1992Nov18.144047.1061@udel.edu> mm@brl.mil (Mike Markowski) writes:
   After applying the Beta kernel patch kit, I tried to apply the patches 
   that come with XFree86 and ran into a patch clash of sorts (I forget
   which ones right now).

   Is there an easier way of adding X support than figuring out how to do
   the X patches by hand after having made the Beta patches?

Patches 28-31 in the patch kit were contributed by the XFree86 to
Terry and should be essentiall the same as the patches that come with
XFree86.  So skip one or the other.  Rich

   Thanks.
   -- 
   Mike Markowski
   mm@brl.mil
   (410)278-6674
From: jkh@whisker.lotus.ie (Jordan K. Hubbard)
Newsgroups: comp.unix.bsd
Subject: CODRV EXPERIENCES, Teil zwei.. (part II)
Date: 17 Nov 92 14:26:33 GMT
	<veit.721670337@du9ds3> <JKH.92Nov16095746@esel.lotus.com>
	<veit.721914354@du9ds3> <JKH.92Nov16125647@whisker.lotus.ie>
Distribution: comp
Organization: Lotus Development Ireland

Just to clear the air on CODRV - I made the correct patch to conf.c
that the documentation had incorrectly described and XFree86 1.1 came up
smiling.  I did not do anything to X except apply the provided patches
and remake a server.  Well done.

Now the bell works, but the TIOCCONS ioctl() is either broken or /dev/console
has changed device numbers (I should, in all fairness, look at this).

By and large, I'd say it was worth it just for the bell alone - now I
finally know when someone talk(1)s me in another window! (I run olvwm,
so they're not always visible).

Outstanding issues:

Figure out what happened to xterm -C / xconsole.

Figure out keycap(5) format well enough to remap my caps lock key
to a control key.  This is not as easy as it sounds since the obvious

jkh|jkhmap:My keyboard with deleted ctl key and ctl->caps_lock mapping:\
        :D30:t1#58:tc=default:

Doesn't seem to work.  I'm using the key down codes that keynum reports.

Herr Veit?  Hilfe?

				Jordan
From: osynw@gemini.oscs.montana.edu (Nate Williams)
Subject: Re: does the UMC chipset work with 386BSD?
Keywords: n
Organization: Montana State University
Date: Sun, 15 Nov 1992 21:12:14 GMT

>>In article <49432@shamash.cdc.com> pbd@runyon.cim.cdc.com (Paul Dokas x4629) writes:
>>>Has anyone heard of the UMC chipset?  
>>
>>Well, I have just removed a 486/50 with UMC from my machine, and gone
>>back to a 486/33 using an OPTI chip set. Nothing else changed - I had
>>a different 486/33 OPTI board (same design, though) in there before.
>>I'm running BSD/386.
>>
>>The OPTI board ran with no problems since March, and I installed the
>>UMC board last week. On average, it crashed 5 times a day. This could
>>be a defective board, of course, but I didn't have another board to
>>compare it with. 
>>

Well, I have been running a UMC board since day one that 0.1 came
out, and I have been very pleased.  Until I brought my machine
onto the local campus network, it was VERY stable, with uptimes
of weeks.  However, with the added load of NFS, remote logins and
such, it hasn't been quite a stable, but I doubt very much that
my chipset has anything to do with it.

Machine:
486/33 - 16MB memory
UMC chipset
Aha 1542B
..



Nate
-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home. 
work: (406) 994-5991         |  Keeper of the Unofficial 386BSD Bug Report
home: (406) 586-0579         |  Please send bugs and/or fixes you find.
Newsgroups: comp.unix.bsd
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Subject: Re: [386BSD] SCSI Bootstrap Method?
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Thu, 19 Nov 1992 13:35:36 GMT

tweten@wilbur.nas.nasa.gov (Dave Tweten) writes:

>In article <1c6BuB4w165w@student.business.uwo.ca> mark@student.business.uwo.ca (Mark Bramwell CS STAFF) writes:
>>tweten@wilbur.nas.nasa.gov (Dave Tweten) writes:
>>
[ text about problems with Adaptec 1740 on EISA and getting a boot-floppy
  deleted - NB.]

>My net conclusion is that I need a pair of bootable diskettes which use
>Julian Elischer's SCSI driver code.  Can anybody help?
I finally managed to put a fixit.fs for the EISA 1740 controller on a ftp-site
for anonymous ftp. This should enable you to boot on your system and to
install it, create (or get a new kernel) etc.

The boot-image can be found at
	hslrswi.hasler.ascom.ch:pub/386bsd-0.1/fixit.1742a.fs.Z
	The IP-Address is:  139.79.129.1
Just proceed in the same way is you would do with the normal fixit.fs disk, i.e.
copy it to a floppy, boot it, etc.
If you really need a dist.fs for the 174x, please tell me and I will prepare
one. However, other things (like the same for the 1542) have higher priority
because I promised those earlier than the latter.

I hope this helps you and others,

Norbert.

P.S.
I will try to put a dist.fs and fixit.fs for the 1542 SCSI controller at the
same site tomorrow (or maybe, sorry, not earlier than monday).
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt
Newsgroups: comp.unix.bsd
From: scm@uropax.contrib.de (Harald Schmidt)
Subject: [386BSD] lpd reboots system
Organization: Contributed Software GbR
Date: Tue, 17 Nov 1992 21:29:18 GMT

Hallihallo,

everytime I try to print binary data (generated by gs) 
on by Cannon BJ-300 my system makes a warm boot.
I applyed the lpr-patch but it seems that there is no
effect to my problem. 
I think the bug is in the lpt-driver.

Does anybody working with ghostscript/lpt without any problem
and can explain what I must do.

BTW: where can I find all these patches listed in FAQs (PATCHxxxxx)

Many thanks in advance,

	Harald
-- 
User:		scm (Harald Schmidt)
System:		AIware
E-Mail:		...!scuzzy!uropax!AIware!scm
Voice:		+49 030 815 75 90
Newsgroups: comp.unix.bsd
From: darryl@vfofu1.dco.dec.com (Darryl Wagoner)
Subject: Reading 720K 3 1/2 floppies on 1.44 drive
Reply-To: darryl@sai.com
Organization: Digital Equipment Corp., Washington ULTRIX Resource Center
X-Newsreader: TIN [version 1.1 PL6]
Date: Sun, 22 Nov 1992 23:51:24 GMT

Does this not work or am I doing something wrong?  I am trying to
use mtools.

-darryl
darryl@sai.com
From: ws@tools.de (Wolfgang Solfrank)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] A caution on using new man & gcc 2.3.1 notes.
Date: 17 Nov 92 13:54:38
Organization: TooLs GmbH, Bonn, Germany
Distribution: comp
	<1992Nov15.232902.5582@raid.dell.com>
NNTP-Posting-Host: kurt.tools.de
In-reply-to: james@raid.dell.com's message of 15 Nov 92 23:29:02 GMT

In article <1992Nov15.232902.5582@raid.dell.com> james@raid.dell.com (James Van Artsdalen) writes:

   > Of course, when I tried to compile libc with it, it coredumped on
   > ldexp.c, so it's not *that* robust either!

   I would bet that there is an asm statement in ldexp.c that tries to
   use 387 registers.  gcc 2.3.1 uses a different syntax for such
   expressions than gcc 1.39, and it's unlikely that any asm statement
   involving 387 regs will work without being rewritten.

That's correct. I changed ldexp for use with gcc 2.1 some time ago.
Here is the context diff for my version. It should compile with both
the new and the old version of gcc.

diff -c bsd/lib/libc/i386/gen/ldexp.c:1.1.1.1 bsd/lib/libc/i386/gen/ldexp.c:1.3
*** bsd/lib/libc/i386/gen/ldexp.c:1.1.1.1	Tue Nov 17 13:47:27 1992
--- bsd/lib/libc/i386/gen/ldexp.c	Tue Nov 17 13:47:27 1992
***************
*** 43,48 ****
--- 43,50 ----
   *
   * Written by Sean Eric Fagan (sef@kithrup.COM)
   * Sun Mar 11 20:27:09 PST 1990
+  * Modified by Wolfgang Solfrank (ws@tools.de) for GCC 2.1
+  * Tue Jun  9 12:56:33 MET DST 1992
   */
  
  /*
***************
*** 55,62 ****
--- 57,74 ----
  {
  	double temp, texp, temp2;
  	texp = exp;
+ #ifdef	__GNUC__
+ #if	__GNUC__ >= 2
+ 	asm ("fscale "
+ 		: "=u" (temp), "=t" (temp2)
+ 		: "0" (texp), "1" (value));
+ #else
  	asm ("fscale ; fxch %%st(1) ; fstp%L1 %1 "
  		: "=f" (temp), "=0" (temp2)
  		: "0" (texp), "f" (value));
+ #endif
+ #else
+ error unknown asm
+ #endif
  	return (temp);
  }

Hope this helps someone...
--
ws@tools.de     (Wolfgang Solfrank, TooLs GmbH) +49-228-985800
Newsgroups: comp.unix.bsd
From: mju@mudos.ann-arbor.mi.us (Marc Unangst)
Subject: Can 386BSD use a serial console?
Date: Mon, 23 Nov 1992 07:39:57 GMT
Organization: The Programmer's Pit Stop, Ann Arbor MI

I've got a "spare" 386SX/20 machine here with 140MB or so of hard disk
space that I'd like to play around with 386BSD on.  Unfortunately, I
don't have a spare keyboard, display board, or monitor, and I don't
particularly relish the thought of spending a hundred bucks or so for
those pieces of equipment.  However, I *do* have several serial
terminals sitting here unused, and it would be nice if I could use one
of them as the console.  Is this even remotely possible?

-- 
Marc Unangst, N8VRH         | "There are two ways to solve this problem:
mju@mudos.ann-arbor.mi.us   | the hard way, and the easy way.  Let's start
                            | with the hard way."
                            |   - W. Scheider, from a Physics lecture
Newsgroups: comp.unix.bsd
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Subject: Re: XView - how much of it is available?
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Mon, 16 Nov 1992 12:50:13 GMT

tdphette@mke.ab.com (Thad Phetteplace x4461) writes:

>kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes:
[questions about XView and availability for 386BSD deleted - NB]

>I managed to port the props program (executed by the Properties menu
>selection) a few weeks ago.  I'm currently working on the termsw bug
>(suggestions welcome).  I'll put the modified props source code and
>executable on my ftp server tinman.mke.ab.com sometime tommorow.  It
>will be in the /pub/386bsd/ports directory.  I will put my ported
>version of pcomm in there as well.  I will make an attempt at
>compiling xlock tonight and if that works I will finish porting
>Xlockup.
Hello everybody !

Yesterday I managed to get the xview client
	textedit
to run without a crash !
It seems to me that the bug you are looking for is not in the textsw part of
the xview library. In fact, there seems to be a bug in the optimization of the
GNU C-compiler included in the stock-386BSD, I think.

What I did to get textedit to run without a crash was:
	I undefined #OS_HAS_LOCALE (after a suggestion from the net).
	I compiled all the stuff, yes, the whole libxview.a with the "-g"
	option to be able to debug it with the wonderful X-debugger "ups"
	(thanks for this very nice and useful application whoever did it).

Imagine what happened, after I finished linking the textedit.o file (compiled
with "-g", too) and the libraries.
I started "ups textedit" for debugging textedit. I loaded a file into textedit
(that's where it crashed before) and it didn't crash this time !!
So, I thought, nothing new for me. I did see several applications run fine
with a debugger but not without it. So, I started textedit from the commandline.
Again, no crash while loading a file. I didn't test it a lot, but it seems to
work for me. I will try to compile the whole libxview.a library with "-O"
flag except the textsw (and perhaps the ttysw) part of it.

The "ups" debugger reported a "segmentation violation" in one of the
textsw functions in the version of the libxview.a compiled without "-g".
That's what I found out before I compiled all the stuff with "-g" (which will
disable optimization).

Oh yes, I am still using the gcc which was included in stock-386BSD.
I just have gcc 2.2.2 but didn't spend any time on porting it (or applying the
patches for 386bsd and just compile it) because now we have gcc 2.3.1 and I
will use that, anyway.

One thing is still bad. Trying to link "cmdtool" with the large (about 18MB)
libxview.a resulted in
	ld: got signal 10 (or something like this).
I have to work on this, too, I guess.

That's a report of my intermediate result.
Hope this saves somebody else at least some time.

Norbert.
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt
From: amurai@tama.spec.co.jp (Atsushi Murai)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Problem of New SCSI system for BT742A (In Japanese/Kanji)
Keywords: BT742A
Date: 19 Nov 92 13:59:35 GMT
Followup-To: comp.unix.bsd
Distribution: world, fj
Organization: System Planning and Engineering Co,.ltd

Dear Netters,

 Now a day, I could make a spare time to play around 386BSD with
private machine ;-) I've already recompiled the kernel with terry's
patch and it's up and running ISA machine with stable.  So I just try
to install the new scsi system for BT742A SCSI controler by 32bit
NATIVE mode. 

 Anyway, Original SCSI system bring up my machie without any problem
but whenever bringing up the new kernel that is installed "Julian's
New SCSI system beta 3" and "Oops Real bug!" patch, it booting and
doing disk checking and then display the follows message and fall into
debuger ( ddb ) mode ( if ddb Enabled ) before near the "starting
local demon" message. 

bt0:0 device timed out
bt0:0 not taking commands

And also I try to Displaying content's of ccb(s) by
tfs_print_active_ccbs before unlink it.  ( Always same and display
just one ccb )

   ccb: fe092780 op:2 cmdlen:10 senlen:34
   datlen:8 hstat:0 tstat:0 delta:500 falgs:1

Also ccb->mbx->cmd is 0x01

I notice binter routine ignore about 10times interrupts after probing 
start. ( int = 0x81,unit=0, ALL bt_mbx[unit].mbi[].stat is BT_MBI_FREE )

So it might be casuing with missing interrupter or just board is hung
by Firm Ware bugs or ? So any help I will appreciate and I hope not
"the board has gone south"... 

Thanks in advance.
--------------------------- Configuration -----------------------------
386BSD 0.1
   o All "Terry's patch" without Some other ether net driver relate one.
   o Julian's "Oops Real Bug" patch ( Just one is released )
   o OS-BS 134 with new boot block

Disk
    o"Maxtor LXT-340S   6.57" 1 drive
    o Using Translated mode and disktab
      ( 512 byes/sector, 32 sector/track, 64 track/Cylynder, 322 Cylynders)
      64M - DOS
      64M - root ( /dev/sd0a )
      32M - swap ( /dev/sd0b )
      32M - var  ( /dev/sd0g )
     128M - src  ( /dev/sd0h )

     root - src  ( /dev/sd0c )
     DOS  - src  ( /dev/sd0d )

   o From Newscsi system Probing
     sd0: 322MB, cyls 1546, heads 7, secs 61, bytes/sec 512
 
SCSI
    o "BIOS V4.50" - During Initailization and probe disk by Board
    o All Board setup is Default and default EISA I/O clock
    o Set/Reset 33Mbytes burst transfer mode, not realted

Mother Board
    o NICE EISA 486 33Mhz
    o 256KB External cache
    o 8 Mbytes 70ns DRAM

VGA
    o Diamond Speed Star +
    o Disable IRQ2

EtherNet
    o NE2000-T ( Novell? )
    o IRQ 2 ( IRQ9?)
    o Default I/O BASE

AT/IO
    o No name 2S 1P 1G enable with default I/O BASE and IRQ

# I don't permit send/receive a email from out side japan....
# Please follow up as This Article. Thank you.
--
Atsushi Murai                                      FAX: +81-3-3832-2779
System Planning & Engineering co,.                 TEL: +81-3-3833-5341
From: rpk@niagara.edu (Rich Kernin)
Newsgroups: comp.unix.bsd
Subject: Looking for Patches
Date: 22 Nov 92 23:52:00 GMT
Organization: University at Buffalo
News-Software: VAX/VMS VNEWS 1.41

Hello,

   I've installed most of the patches from the patchkit, but was wanted to
know if the patches that have been made since then, and posted, have been
archived anywhere?  I'm particulary looking for a patch that was posted to
fix a memory leak when ping and traceroute were used.  Since I've got our
386BSD machine on our local network/internet I'd really like to install
this patch.  I had it at one point, but I recently lost a partition... :-(

-Rich

---------------------------------------------------------------------------
Richard P. Kernin                  Internet: visnurpk@ubvmsc.cc.buffalo.edu
Niagara University                   BITNET: visnurpk@ubvmsc.BITNET
Administrative Computer Center
---------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: hackney@moxie.hou.tx.us (Greg Hackney)
Subject: Re: [BSD386] 'make' seems to take a long time - elm2.4
Organization: Home
Date: Thu, 19 Nov 1992 03:54:47 GMT

venkat@uxh.cso.uiuc.edu (Venkat) writes:

>I have been trying to install elm2.4 on my 386 running Bsd/386. After I answer
>all the config questions and elm instructs me to run make, when I do so it
>seems to take a long time. I have waited for about 4-5 mins and all the while
>there is no disk activity. Is this normal ? Does 'make' take this long ?

It won't compile right with the existing version of /bin/sh. You
need to copy 386BSD's bash onto /bin/sh.

Newsgroups: comp.unix.bsd
From: levinson@halcyon.com (Don Levinson)
Subject: [386bsd] NNTP or INN
Summary: where do I find INN?
Keywords: NNTP INN 386bsd
Organization: The 23:00 News and Mail Service
Distribution: comp.unix.bsd
Date: Wed, 18 Nov 1992 21:55:18 GMT

not too long ago someone posted that INN was a better news server than
NNTP as far as 386bsd is concerned, where do I find this program?

Don Levinson
-- 
-------------------------------------------------------------------------------
 Don Levinson	  levinson@halcyon.com	| 	Fatigue Technology Inc.
 "Stupid answers for stupid questions"	| 	100 Andover Park West
    ph:206-246-2010 fax:206-244-9886	| 	Seattle, WA 98188
From: pbd@runyon.cim.cdc.com (Paul Dokas x4629)
Newsgroups: comp.unix.bsd
Subject: Help ID some OLD disk drives
Date: 17 Nov 92 22:39:37 GMT
Organization: ICEM Systems, Inc.

While digging through the company closet, I found two 286 PCs, each
of which had an (apparently) functional hard drive in them.  But
I can't figure out what they are and how big they are.  If you
have heard of these beasts (or know of a disktab for them!) please
let me know.

  mystery drive #1:  Full height, 5 1/4, Seagate 4026
  mystery drive #2:  half height, 3 1/2, Miniscribe 8425

I'm guessing that both of these drives are MFM (or possibly IDE).

Correct answers will be rewarded with the "Guru of the Week" award. :-P

Thanks
-- 
#include <std.disclaimer>
#define FULL_NAME                          "Paul Dokas"
#define EMAIL                              "pbd@runyon.cim.cdc.com"
/*                     oh what the hell                     */
Newsgroups: comp.unix.bsd