HDTenEightyP/NetNews huggingface dataset:
From: alm@netcom.com (Andrew Moore)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] 16550 and rtscts patch
Date: 15 Dec 92 00:29:44 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest)

In article <1992Dec14.171834.7500@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>In article <Bz25Io.L40@ucunix.san.uc.edu> pmartin@eniac.san.uc.edu (Paul Martin) writes:
>>
>>I applied the rtscts flow control patch to the com driver that was
>>posted here sometime back.  Now I cannot send anything to the modem.  The
>>modem does not receive the characters, and the command:
>>echo ats0=1 > /dev/com2
>>seems to hang until I shut off the modem.  This worked before the patch.
>>I am using 16550's.  By the way, the mouse on com1 still works fine.
>>
>>Any Ideas?
>
>I haven't had a chance to look at the patch yet (I did save it off);

I thought Chris Demetriou mentioned that there were some additional
changes needed to make this patch work (?)  Anyhow,  it is
incorported into his multiport serial driver and works fine.
-Andrew Moore <alm@netcom.com>
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Gateway 2000 problems?
Organization: Weber State University  (Ogden, UT)
Distribution: usa
Date: Mon, 14 Dec 92 17:36:11 GMT

In article <1992Dec11.215721.10579@usasoc.soc.mil> ted@usasoc.soc.mil (Ted Nolan) writes:
>Hello folks,
>
>After getting some positive responses on the message I posted a few days ago
>about "How useful is 386BSD?", I've about decided to go for it.  However,
>one of the messages I got mentioned some problems with Gateway 2000 systems,
>which is one of the choices I have been strongly considering for my home
>computer.
>
>We happened to have a Gateway 2000 486DX-33 sitting in our lab, so I took
>the dist-fs floppy from the bootables directory and tried it out: no
>dice.  I also tried the new dist-fs from the unofficial/terry/new-bootables
>area on agate, but that didn't work either.  I think the floppy is OK, because
>I have tried it on another system here and it booted fine.
>
>Does this mean I have to stop considering Gateway, or does someone know what
>the problem is (and have a fix!)?  Also, if so, does anyone know if xfree86
>will work on the Gateway localbus VGA?

There are patched bootables on rachel for Compaq boxes; this is what you
probably need.  Internally (and I believe posted here) was a recent fix
that removed a register-clobbering NOP in the wdboot.  Initial returns
have pegged this as the Compaq problem; however, without a working
kernel, one can't rebuild wdboot and replace it on a boot disk.

I believe the some-time Gateway problem is the all-the-time Compaq
problem; thus the rachel Compaq bootables should be usable on Gateway
to get around the problem until the real fix can be applied and new
bootables created locally.


					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: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] 16550 and rtscts patch
Date: 14 Dec 92 18:15:08
Organization: Kernel Hackers 'r' Us
	<1992Dec15.002944.11215@netcom.com>
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: alm@netcom.com's message of 15 Dec 92 00:29:44 GMT

more changes are necessary that were in the patchkit the last time i checked...

however, i wouldn't guarantee that my driver works correctly;
i've seen some schtuff happening between my computer and modem that
would indicate to me that either it doesn't work properly (all the time),
or my modem is mis-configured...

Chris
who only has one final more to go...
--
Chris G. Demetriou                                    cgd@cs.berkeley.edu

"Sometimes it is better to have twenty million instructions by
        Friday than twenty million instructions per second." -- Wes Clark
Newsgroups: comp.unix.bsd,alt.suit.att-bsdi
Subject: Re: AT&T/USL CD-ROM Review Process
From: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats
Date: Wed, 16 Dec 1992 03:45:25 GMT
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)

In article <1992Dec15.033540.483@cheops.qld.tne.oz.au> pclink@cheops.qld.tne.oz.au (Rick) writes:
>terry@cs.weber.edu (A Wizard of Earth C) writes:
>
>>Second, Linux is arguably more like SVR3 (and by extension SVR4) than
>>386BSD; this, I believe, puts it in more danger of censure.  The thing
>>that has protected Linux so far is its international (non-US) origin.
>>This is not something USL has to worry about forever, it's simply an
>>inconvenience to prosecution, not a barrier.  If a judgement were given
>>regarding copyright infringement by Linux against USL's materials, it
>>wouldn't matter that the judgement occurred in the US; Linus' government
>>would be forced by the Berne convention to uphold the judgement.
>
>Forgive my density, but prosecution under what grounds?  It's my
>understanding that Linus has written Linux from scratch (with a leg-up
>from Minix).  Surely Andrew Tannenbaum would have more grounds for copyright
>infringement than USL?


Linus didn't do it all.  There has been lots of contributors, including
BSD source.

-- 

Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
Newsgroups: comp.unix.bsd
From: smace@nyx.cs.du.edu (Scott Mace)
Subject: [386BSD] lawsuit against BSDI
Organization: Nyx, Public Access Unix @ U. of Denver Math/CS dept.
Distribution: usa
Date: Mon, 14 Dec 92 02:56:31 GMT


Will the outcome of the pending lawsuit of USL vs. BSDI affect the
status of 386BSD?

Thanks

--
*********************************************************************
*    Scott Mace                internet:    smace@nyx.cs.du.edu     *
*                                           emace@tenet.edu         *
*********************************************************************
From: peter@chchp.ac.nz (Peter Ellens)
Newsgroups: comp.unix.bsd
Subject: [386bsd] Sendmail config problems.
Date: Mon, 21 Dec 1992 02:22:37 GMT
Organization: Christchurch Polytechnic
Distribution: world
NNTP-Posting-Host: peter.chchp.ac.nz
Summary: sendmail,mx records, Help!
Keywords: sendmail,mx records

How do you config sendmail, as suplied with 386bsd, to use MX records?
From: woakesd@logica.co.uk
Newsgroups: comp.unix.bsd
Subject: Can I use a Tape Streamer with 386bsd?
Date: 18 Dec 92 10:58:00 GMT

I'm thinking of installing 386bsd on a 486DX pc. I wanted to know if any tape
streamers would work with the system.

If anybody currently uses one could you let me know if I need any patches?
Newsgroups: comp.unix.bsd
From: ngai@nova.bellcore.com (John Ngai 21371)
Subject: Re: Jolitz Book & CD ROM
Organization: Bellcore
Date: Fri, 11 Dec 92 17:57:31 GMT

In article <1g9c3lINNh1n@neuro.usc.edu>, merlin@neuro.usc.edu (merlin) writes:
|> Does anyone have news of the status of the pre-announced
|> Jolitz book on 386bsd?  Would it be possible to include 
|> a bootable CDROM version of 386bsd up to current patch
|> level, source code, development tools, and X11R5.

I like to second his suggestion!! Of course, it would be nice if the version
included in the CDROM is more stable, perhaps V0.2??

|> CD ROM might be includable at minimal cost and enhance
|> book sales at minimal production cost increase.

Perhaps more importantly, it allows other curious PC users to try UNIX without
having to go through the trouble of down loading the codes/binaries from the
Internet (and what if they have no access to Internet??)

-- John
From: terry@uivlsisd.csl.uiuc.edu (Terry Lee)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD: Problem in wd.c (?) - affects swap, non-atatched drive(s)
Date: 11 Dec 92 20:52:08 GMT
Organization: Center for Reliable and High-Performance Computing, University of Illinois at Urbana-Champaign
NNTP-Posting-Host: uivlsisd.csl.uiuc.edu

Joseph,

	You might want to try the Norway wd driver by Tom Ivar Helbekkmo.  In
my opinion, it is definitely superior to even the patched stock wd driver.  It
fixes problems with bad block handling completely, supports 4 drives with 2
controllers.  I think the stock wd driver won't support secondary controllers
because the BIOS has no support for them (the stock wd driver still relies on
the BIOS tables for the initialization routines).  You can ftp the Norway
driver from barsoom.nhh.no.  Good luck!

----------
Terry Lee
terry@uivlsi.csl.uiuc.edu
Newsgroups: comp.unix.bsd,comp.os.linux
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: Dumb Americans (was INTERNATIONALIZATION: JAPAN, FAR EAST)
Keywords: Han Kanji Katakana Hirugana ISO10646 Unicode Codepages
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
Date: Sat, 19 Dec 1992 05:18:58 GMT

In article <1992Dec18.235809.15484@midway.uchicago.edu> goer@midway.uchicago.edu writes:
>messina@netcom.com (Tony Porczyk) writes:
>>
>>>One of the big criticisms leveled at US Engineers is that they are either
>>>too dumb or lazy to build into their software support for non-Western
>>>scripts.  Given that Linux originates in Europe, can we look forward to
>>>better support for Unicode and ISO10646?  At least for "long" charac-
>>>ter definitions?
>>
>>Yeah, that's probably why NT supports Unicode, it's those dumb US
>>Engineers...  Could we lay off idiotic generalizations and stick to
>>technical aspects of the software?  It's business that dictates what's
>>included in the package.  If it makes economic sense, it will be there.
>
>Don't be so quick to criticize.  The December issue of UNIX world has
>a few funny stories about American gaffes in Europe, and I've personally
>heard many stories from Europeans myself along the same lines.  I'd be
>willing to bet that less than 5% of US software engineers even speak a
>foreign language beyond the level of a few parlez vous.  One of the big
>problems we have is precisely the attitude that you display, namely that
>most localizations should be done on-site.  This is fine if multilingual
>support is built into the basic distributions, but really stupid if it
>isn't.
>
>As for economic sense, I have the same feeling about American's in the
>mid- and large-range computer business that I have about Detroit.  They
>simply aren't as aware as they should be about what their customers
>really want.  NT will be a welcome departure from the past, if in fact
>it offers true multilingual support.  We'll see.
>
>-- 
>
>   -Richard L. Goerwitz              goer%midway@uchicago.bitnet
>   goer@midway.uchicago.edu          rutgers!oddjob!ellis!goer

Although not a major player in the market Unisys did offer 
internalization on many of their applications.

The part that few US software engineers speak another language is 
strange to me at least around here in Silicon Valley. What is strange
is to find a software engineer who only speaks english.


I speak Spanish and was raised in Puerto Rico :-)

Amancio Hasty

-- 
Amancio Hasty           |  
Home: (415) 495-3046    |  ftp-site depository of all my work:
e-mail hasty@netcom.com	|  sunvis.rtpnc.epa.gov:/pub/386bsd/incoming
From: pbd@runyon.cim.cdc.com (Paul Dokas)
Newsgroups: comp.unix.bsd
Subject: bug in $SRC/libc/db/btree?
Date: 18 Dec 92 21:13:42 GMT
Organization: ICEM Systems, Inc.

I've been trying to get aliasing working with sendmail on 386BSD 0.1 pl58
and it works, unless I have more than ~75 aliases in /etc/aliases.  When
there are more than ~75, then sendmail stops with a segmentation violation.

I've run it through gdb and found the following:

  % gdb ./sendmail
  Reading symbol data from /usr/obj/usr.sbin/sendmail/src/sendmail...done.
  (gdb) run -bi
  Starting program: /usr/obj/usr.sbin/sendmail/src/sendmail -bi

  Program received signal 11, Segmentation fault
  Reading in symbols for storage.c...done.
  0x12461 in _bt_getpage (t=(BTREE_P) 0xfbbee458, pgno=0x00000001) (storage.c line75)
  75      (storage.c)
  (gdb) where
  #0  0x12461 in _bt_getpage (t=(BTREE_P) 0xfbbee458, pgno=0x00000001)
                 (storage.c line 75)
  #1  0x1218d in _bt_search (t=(BTREE_P) 0xfbbee458, key=(DBT *) 0xfbbee450)
                 (search.c line 157)
  #2  0x113af in bt_put (dbp=(struct __db *) 0x38f00, key=(DBT *) 0xfbbee450,
                 data=(DBT *) 0xfbbee448, flag=0x00000004) (btree.c line 437)
  #3  0x11b55 in _bt_insert (t=(BTREE_P) 0x38f00, item=(struct BTITEM *) 0x27825,
                 key=(DBT *) 0xfbbee450, data=(DBT *) 0xfbbee448, flag=4)
                 (insert.c line 115)
  #4  0x11453 in bt_put (dbp=(struct __db *) 0x38ec0, key=(DBT *) 0xfbbee450,
                 data=(DBT *) 0xfbbee448, flag=0x00000004) (btree.c line 454)
  #5  0x98a in readaliases (aliasfile=(char *) 0x30180 "/etc/aliases", init=1)
                 (/usr/src/usr.sbin/sendmail/src/alias.c line 602)
  #6  0x4a2 in initaliases (aliasfile=(char *) 0x30180 "/etc/aliases", init=1)
                 (/usr/src/usr.sbin/sendmail/src/alias.c line 353)
  #7  0x7ce7 in main (argc=2, argv=(char **) 0xfbbef000, envp=(char **) 0xfbbef00c)
                 (/usr/src/usr.sbin/sendmail/src/main.c line 533)

So it's breaking in the btree code.  I'm not familiar with this code, so I
thought that I'd ask if anyone has seen similar problems with this code.
And if so, are there any patches?

Some other possibly important info:
  - the ordering of the /etc/aliases file is not important, it's only the
    length of /etc/aliases

  - I have rebuilt libc (I'm not using the distribution libc)

-- 
#include <std.disclaimer>
#define FULL_NAME                          "Paul Dokas"
#define EMAIL                              "pbd@runyon.cim.cdc.com"
/*            Just remember, you *WILL* die someday.             */
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: SLIP for 386bsd
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Sat, 12 Dec 1992 04:39:56 GMT

In article <92346.144917CALT@SLACVM.SLAC.STANFORD.EDU> <CALT@SLACVM.SLAC.STANFORD.EDU> writes:

   Where can I get SLIP for 386bsd? Thanks!

   Ching Shih
   shih@cithex.bitnet
   shih@cithex.caltech.edu

It's in the binary distribution.  try 'man slattach'.

I don't know of any introduction or user's guide for slip.  Can anyone
suggest something which might be useful to first time slip users?
Rich
Newsgroups: comp.unix.bsd
From: michaelv@iastate.edu (Michael L. VanLoon)
Subject: Which DDJ articles for 386BSD?
Organization: Iowa State University, Ames IA
Date: Wed, 16 Dec 1992 22:27:33 GMT

Would some nice soul kindly email me a list of all the dates for the
386BSD series in Dr. Dobb's Journal so I can run to my friendly
University Library and get a copy of all the articles about the design
and building of 386BSD.  Any other really juicy articles by Bill
Jolitz would be appreciated, also.

Thanks so much!

				--Michael

-- 
------------------------------------------------------------------------------
  Michael L. VanLoon                           Project Vincent Systems Staff
  michaelv@iastate.edu              Iowa State University Computation Center
------------------------------------------------------------------------------
From: steve2@genesis.nred.ma.us (Steve Gerakines)
Newsgroups: comp.unix.bsd
Subject: [386bsd] kernel image not found
Date: 16 Dec 92 13:25:43 GMT
Organization: Genesis Public Access Minix  +1 508 664 0149

Hi there.  I really hate asking newbie questions, but I've pretty much
run out of ideas.  

My system is a 486DX250 with a Maxtor 535SY drive and an UltraStor 24F
running in ISA mode.  I'm using the first 120Mb for DOS, and the rest
for 386BSD.

The problem is that the bootstrap program cannot find the 386bsd kernel
image within the root directory.  The system boots up off the hard drive
and I receive messages like:

File not found - couldn't load 386bsd, will try 386bsd.old
File not found - couldn't load 386bsd.old, will try vmunix
   .
   .

And I'm forced to reboot.

What's strange is that when I install 386bsd so that it owns the whole
drive, things work great.  The system boots and runs without a hitch.
If anyone has any thoughts as to what might be going on I'd appreciate it.
Also, if the bootstrap source (wdboot and bootwd) is available I'd love to
get my hands on it.  Might shed some light as to what's going on.

I should probably add that I've set the disk up using my own disktab.  I
set up the a and c partitions so that they begin at cyl 244, sector 0,
head 0 while using DOS-- when using the whole drive they were at cyl 0.
 
Thanks for anything!  :-)
Steve
--
Steve Gerakines           |
steve2@genesis.nred.ma.us |  "I have a three user 386BSD TV license." - me
+1 (508)664-0149          |
From: irviner@yvax.byu.edu
Newsgroups: comp.unix.bsd
Subject: HELP mread (again)
Date: 18 Dec 92 20:53:39 -0700
Organization: Brigham Young University


I've been working in version 0.0 since day one and finally took
the big jump to 0.1.  Everything has gone well with the installation
except when I try to load the bin01.xx from dos floppys with 'mread'.
When I do  mread a:*.*  I get  a message like:

        Probably not a MSDOS floppy
        cannot initialize

and then back to the # prompt.

I know this has probably been all hashed over here but being as I'm
kinda late I sure would appreciate a tip.

                Thanx all
                Ron Irvine
                irviner@yvax.byu.edu
From: news@hrd769.brooks.af.mil (InterNet News)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD wd.c timeout problem during autoconfig
Date: 16 Dec 92 05:33:59 GMT
Article-I.D.: hrd769.1gnpa7INN2u1
Organization: Armstrong Lab MIS, Brooks AFB TX
NNTP-Posting-Host: hrd769.brooks.af.mil

In article <1992Dec16.002542.6959@moxie.hou.tx.us> hackney@moxie.hou.tx.us (Greg Hackney) writes:
}
}We found a timeout problem in the wd.c code that occurs when the
}system trys to autoconfigure the disk drives at boot time.
}
}In wdcommand() there is a declaration:  int timeout = 1000000;
}
}This is a loop counter that runs while the disk controller
}registers are being probed. For a Conner 510MB IDE drive on a Compaq
}SystemPro 486/33, that value is not large enough for the controller
}to respond in time. (It's only short by a count of about 3,000 on
}this system).
}
}As a result, booting the dist.fs floppy indicates you have no hard
}disk drives.
}
}The fix was to increase the value of timeout. We used 1,500,000.
}--
}Greg Hackney   hackney@compaq.com
}Mike Busby     mcb@compaq.com
}
}
  I apologize for not looking at the code closely before I jump into this,
but shouldn't we be using a time value instead of a processor speed
dependent for loop?  Something like usleep(3) comes to mind, but I could be
mistaken.

  As an example:

  while(((stat = inb(wdc + wd_status)) & WDCS_BUSY) && timeout-- > 0)
    usleep(n);

  Where n is some reasonable number of milliseconds to pause and
    timeout is the number of pauses before there is an actual error.

  If we sleep for 1 millisecond, and the timeout value is 1 second,
then timeout would be 1000.  This way, the code doesn't break on fast
'486 machines (assuming that usleep works).

  What kind of problems would this cause?

TSgt Dave Burgess
NCOIC AL/MIS
Brooks AFB, TX
From: mattb@sdd.hp.com (Matt Bonner)
Newsgroups: comp.unix.bsd
Subject: [386bsd] Building Motif 1.2
Date: 16 Dec 1992 01:44:03 GMT
Organization: Hewlett-Packard, San Diego Division
Distribution: world
NNTP-Posting-Host: hpsdlg16.sdd.hp.com
Keywords: Motif hang 386bsd

Has anyone out there had problems with building Motif 1.2 for
386bsd?  During the makedepends for libXm, the system always
seems to hang.  I've tried waiting a long time to make sure I'm
just not being too impatient.  I can't even figure out a way to
recover, I have to reboot.  I can rebuild the kernel but I'm
not very familiar with configuration of said thing.  Originally
I was trying to build with the straight kernel, lately I've
started applying the patch kit.  No difference.

If anyone has modified Makefiles or Imakefiles for this problem,
I'll gladly accept those too.

System: Orchid 486/33 Superboard, Adaptec 1542b, Fujitsu 520MB 3 1/2" HD

Thanks,
Matt
-- 
Matt Bonner                  |  Email: mattb@sdd.hp.com
Hewlett-Packard Company      |  Snail: 16399 West Bernardo Drive
Ink-jet Components Division  |         San Diego, CA  92127-1899
Newsgroups: comp.unix.bsd
From: tlukka@lk-hp-8.hut.fi (Tuomas J. Lukka)
Subject: Re: tip & screen (NOT!!! REALLY TIP & TERM)
Organization: Helsinki University of Technology, Finland
Date: 14 Dec 92 04:21:27 GMT

In <tlukka.724239227@snakemail.hut.fi> tlukka@lk-hp-8.hut.fi (Tuomas J. Lukka) writes:

>Has anyone hacked screen to work on 386BSD? I get it to compile
>but have not yet gotten it to actually work.

ARGH!!! That's what comes when I write something when tired!
I meant Michael O'Reilly's program 'term' which multiplexes several
connections on a single serial line.
The program is quite clever but also not too easy to get to work.

>Also, what do I need to make tip work with sz etc, there was a patch,
>is it in the kit?

Yes, and with this, also with term.

	TJL
Newsgroups: comp.unix.bsd
From: kapela@prism.poly.edu (Theodore S. Kapela)
Subject: Re: [386BSD] Disklabel for MAXTOR LXT340S
Summary: LXT340 uses ZBR
Organization: Polytechnic University, New York
Date: Tue, 15 Dec 92 16:50:13 GMT

In article <1992Dec12.100620.16224@tfs.com> julian@tfs.com (Julian Elischer) writes:
>In article <1992Dec10.080231.10747@email.tuwien.ac.at> mbirgmei@email.tuwien.ac.at (Martin BIRGMEIER) writes:
>>Hello netters,
>>
>>MAXTOR LXT340S 6.20
>>
>>cylinders: 324              <=========================== (!)
>It used the BIOS's idea of the geometry which is different.
>(The adaptec sets it up to LOOK LIKE 32sec, 64heads, 324CYL)
>
>in fact since the disk MAY have Zone recording we may BOTH be wrong!

YES!  The drive *DOES* use Zone-Bit Recording (I have the IDE version 
[ an LXT-340A ] that I am temporarily using for 386bsd.  I called
Maxtor's fax-back service to get the specs on the drive and found
that it does in fact use zone-bit recording.  All error-correction and
bad-sector mapping is handled by the drive itself.  Your best choice is
to probably use the suggestions for DOS (Ugh!).

The spec sheets list all the specs for both interfaces (SCSI and IDE).
The physical drive is the same - just the interface is different.

-- 
..............................................................................
 Theodore S. Kapela				kapela@poly.edu
 Center for Applied Large-Scale Computing	
 Polytechnic University
Newsgroups: comp.unix.bsd