HDTenEightyP/NetNews huggingface dataset:
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Sendmail problems
Organization: Weber State University  (Ogden, UT)
Date: Wed, 30 Dec 92 18:59:32 GMT

In article <50932@shamash.cdc.com> pbd@runyon.cim.cdc.com (Paul Dokas) writes:
>I've been trying to get aliases to work properly with the distributed
>sendmail, but I've run into several problems.
>
>First of all, my alias file is pretty big (300+ aliases), it works great
>on all of the other platforms here (SUN, IBM, HP, SGI), but not on 386BSD.
>When I do a 'sendmail -bi' to initialize the alias dbase, sendmail stops
>with a segmentation fault.  I ran sendmail with gdb and found that it was
>breaking in some of the btree code (from libc).
>
>Ok, no problem get the latest version of the db code and rebuild libc,
>right?  Unfortunately no, the latest version of the db code (from
>okeefe.cs.berkeley.edu) doesn't have R_PUT and a couple of other things
>that the distribution sendmail needs.
>
>So I now have a slight broken sendmail, an old db library and the new db
>library.  Does anyone have any of the following:
>
>  1) working sendmail (patches or full source would be great)
>  2) the latest source for sendmail
>  3) working db routines (patches or source)
>  4) any other useful information...

Someone here (Paul Vixie?  Chris Torek?) posted the new db code here;
it's also available from archives.  I wasn't too interested in it at the
time, but I believe there was also a sendmail using the new db code in
the source tree the new db code came from.  Use archie to look for the
new db code; that's how I found it.  Sorry, but I can't remember the
archive it was on.

The db stuff is admittedly (in the comments) broken and crufty in the btree
code, but ok otherewise.  You really do need the new code.

Hope this helps.


					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: duplain@rtf.bt.co.uk (Andy Duplain)
Newsgroups: comp.unix.bsd
Subject: Re: Patch to allow ps(1) to identify console-controlled processes
Date: 23 Dec 92 09:12:29 GMT
Organization: BT Customer Systems, Brighton, UK

In article <1992Dec22.122813.28550@cnplss5.cnps.philips.nl> rooij@mozart.cft.philips.nl (G. van Rooij) writes:
>
>I ported ps a lonmg time ago (I think it was in version 0.0) but from
>what I remember, there was a much simpler "hack": If I remember well
>theer was a define (HP300 or so, it was definitely something with HP)
>that also fixed a wrong behaviour towards console entries. When you
>define this ps's output also is okay.

	Mmmm, I don't think so; the code I hacked had no #ifdefs etc., it
	was straight code.  Perhaps I should have mentioned that the hack
	was for the 386BSD version of "ps" (keep thinking this group is
	comp.unix.386bsd :-).

-- 
Andy Duplain, BT Customer Systems, Brighton, UK.           duplain@rtf.bt.co.uk
#define	DISCLAIMER      My views and opinions are my own, and not my company's
Newsgroups: comp.unix.bsd
From: is@groucho.dev.uga.edu (Bob Stearns)
Subject: Initial Install Failure
Organization: University of Georgia
Date: Wed, 23 Dec 1992 18:32:12 GMT

Newsgroups: comp.unix.bsd
Subject: Keyboard dies in initial install
Summary: 
Followup-To: 
Distribution: world
Organization: University of Georgia
Keywords: 

I was attempting to install BSD/386 v 0.9.4 on a generic 386/33 clone,
IDE 100 MB, 8MB no co-processor system. After booting BOOT1, I am unable
to respond to the "Root device?" prompt.  The entire system is locked up,
the keyboard is dead, the Ctrl-Alt-Del key in ineffective and I have no
choice but to re-boot via reset/power switch.

If you have experienced this and cured it, please drop me an E-mail note
since we are mostly going to be closed for over a week and my new feeder
will expire any news replies before I return.

Thanks for your attention to my problem.

-- 
Bob Stearns
University of Georgia
is@groucho.dev.uga.edu
(404)542-5110
From: mycroft@hal.gnu.ai.mit.edu (Charles Hannum)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] LPT port ???
Keywords: Printer, LPT
Date: 23 Dec 92 10:11:07 GMT
Article-I.D.: life.1h9dvrINNpv3
Organization: /etc/organization
NNTP-Posting-Host: hal.gnu.ai.mit.edu


In article <1992Dec22.200654.2494@umbc3.umbc.edu> banz@umbc7.umbc.edu
(Robert Banz) writes:
>
> I've been running 386BSD for a few weeks now, and the one thing I
> haven't been able to use is my parallel port!  How does one go about
> setting up to print through the lpt port with 386BSD.

Grab the stuff in unofficial/terry/lpt-driver.  It works for me.

-- 
 \  /   Charles Hannum, mycroft@ai.mit.edu
 /\ \   PGP public key available on request.  MIME, AMS, NextMail accepted.
Scheme  White heterosexual atheist male (WHAM) pride!
Newsgroups: comp.unix.bsd
From: gary@mama.minmet.uq.oz (Gary Roberts)
Subject: Re: [386BSD] How do I know what's on the etc disks?
Organization: Prentice Centre, University of Queensland
Date: Tue, 29 Dec 1992 05:42:18 GMT

rich@Rice.edu (& Murphey) writes:

>>>>>> In article <Bzqnq0.8ut@ais.org>, draper@ais.org (Patrick Draper) writes:

>P> Is there an index to the etc distribution that is on wuarchive? There's over
>P> 90 of them now, and I can't really take to the time to sift through them all
>P> to find the good stuff.

>yes, on agate.berkeley.edu (128.32.136.1):
>/pub/386BSD/386bsd-0.1/filesystem/MANIFEST.etc01.files
>Rich

Only problem is that this file seems *exactly* the same as the .src01. file.
I noticed this when I recently installed the bin01 src01 and etc01
distributions on my 486DX33 notebook and casually started to glance through
these manifests out of interest.  I just looked on agate and sure enough,
both src01 and etc01 manifests are still identical in size.  It would be
nice if some kind soul could put up the correct manifest.

As a longtime Unix user (BSD2.9 on 11/34, BSD4.2 on Vax 11/730, Sunos 4.x on
4/110, 1+ and IPC), I must heartily congratulate William and Lynne Jolitz and
all others concerned (Terry's patchkit is superb) on a marvellous package.
It has been up on my notebook for four days now and is very impressive.
I've ported the InfoZip stuff (zip19, unzip50) and written two shell scripts
(taz and untaz) which allow me to save a lot of space by storing stuff as
zipped tarfiles.  For example othersrc/contrib (isode and tcpdump) which I
will not look at for some time, compresses from over 13 meg to just over 3.

Cheers,  Gary.
Gary Roberts		   |  Ph:    +617-3654176
Mining & Met Engineering   |  Fax:   +617-3654377
University of Queensland   |  Internet: gary@minmet.uq.oz.au
Brisbane. 4072 AUSTRALIA   |
From: tjon@plains.NoDak.edu (Christopher C. Tjon)
Newsgroups: comp.unix.bsd
Subject: Using compressed man pages?
Date: 1 Jan 93 23:06:23 GMT
Article-I.D.: ns1.C076un.Fro
Organization: North Dakota Higher Education Computing Network


I know that about a month ago someone did a zman or something like that
to allow man pages to reside on the system compressed and be retreived.
Can anyone tell me where to find this program.

thanks

-- 
Chris
		tjon@plains.nodak.edu	 Christopher C. Tjon
		uunet!plains!tjon (UUCP) Box 5224
		tjon@plains (Bitnet)	 Fargo, ND 58105-5224
This message brought to you by the letters X and S and the number 3.
From: hlu@eecs.wsu.edu (H.J. Lu)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] GNU malloc in favor of BSD malloc in libc - shall we vote?
Date: 1 Jan 93 00:13:32 GMT
Article-I.D.: serval.1993Jan1.001332.15123
Organization: School of EECS, Washington State University

In article <1hvu79INNjqq@ftp.UU.NET>, sef@Kithrup.COM (Sean Eric Fagan) writes:
|> "comp" is not a valid distribution.  By putting "Distribution: comp" in your
|> header, you have caused or allowed a growing number of sites around the
|> world to drop your article on the floor.  If you don't care whether or not
|> people see your article, please feel free to continue using invalid dis-
|> tributions.
|> 
|> In article <JKH.92Dec31154004@whisker.lotus.ie> jkh@whisker.lotus.ie (Jordan K. Hubbard) writes:
|> >I say we petition Bill to use GNU malloc in preference.
|> 
|> GNU malloc is copylefted.  Using it in a library means that every program
|> compiled using that library is copylefted.  That is almost certainly the
|> reason why it is not used, and I cannot fault anyone for that.

Is that under GLGPL? Another `feature' in GNU malloc is malloc (0) returns
NULL.

H.J.
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.unix.bsd
Subject: Re: questions of scsi tape driver.
Date: 3 Jan 93 21:54:41 GMT
Organization: Silicon Graphics, Inc.  Mountain View, CA

In <1993Jan3.003448.2389@netcom.com> shawr@netcom.com (rich shaw) writes:

| Recently I bought a used tandberg TDC3640 scsi tape drive. I think it's
| a QIC150 drive. This drive works fine under dos (I am using aspitar).

QIC120; unfortunately the Tandberg engineers returned the
same inquiry string for the 3620 (QIC24), 3640, and 3660 (QIC150) drives,
which is a pain if you need to know which drive it is...

| dev4,lu0: tape1 (sequential), removable 'unknownunknown????' SCSI0
| 	st0: scsi tape drive:0 blocks of 512 bytes

Looks like it wants an inquiry string to match, or the like.
--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   olson@sgi.com
Newsgroups: comp.unix.bsd
From: shawr@netcom.com (rich shaw)
Subject: questions of scsi tape driver.
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Sun, 3 Jan 1993 00:34:48 GMT

Recently I bought a used tandberg TDC3640 scsi tape drive. I think it's
a QIC150 drive. This drive works fine under dos (I am using aspitar).
But when I boot 386bsd with julian's scsi drivers(Thanks julian), there 
seem to be some problems recognize  or initialize the drive. Below are
the messages on the screen.

dev4,lu0: tape1 (sequential), removable 'unknownunknown????' SCSI0
	st0: scsi tape drive:0 blocks of 512 bytes
cmd fail
cmd fail 
...

After I compiled with scsi_debug set to 1, I got the following message.

aha_scsi_cmd <ccb0(0x23) cmd fail
aha_done ccb0(0x33)> ccb0(0x23)> ahaintr scsi error rval=3
code from driver 0x2

Could anyone tell me what this error is? The tape drive is fairly old (1987)
, so I think that's why the driver recognized it as scsi0. However, since
it works fine under dos's ASPITAR, there should be a way to make it work under
386bsd, right? Anyway, is there any fix for this or hints that can help me
to fix it? Thanks and happy new year.

-- rich
-- shawr@netcom.com
From: reink@hpuamsa.neth.hp.com (Reinier Kleipool)
Newsgroups: comp.unix.bsd
Subject: [386 BSD] Manpage for /etc/init?
Date: 28 Dec 92 12:57:28 GMT
Organization: HP-Sales Office-The Netherlands

Hello,

   Does anyone has a manpage of init (/etc/init). I cannot find it anyware
on my system?


Thanks in advance..
Reinier Kleipool.


  /\
-(  )-/##---------------------------------------------------------------------
  }{/   ##    One has to look out  -- Overschie ------------------------------
.====.        for engineers- they  -- Reinier Kleipool  ----------------------
| [] |   begin with sewing machi-  -- Mail -----------------------------------
|    |   nes and  end up with the  -- X400: C=nl A=400net P=hp O=hp S=Kleipool
|    |   atomic bomb.....          -- desk: Reinier Kleipool/ hpitcb/75     --
| [] |              Marcel Pagnol  -- unix: reink@hpuamsa.neth.hp.com       --
------------------------------------------------------------------------------
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: ref.tfs.com routing (JULIAN --- READ THIS)
Date: 21 Dec 92 07:17:45
Organization: Kernel Hackers 'r' Us
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: adrian@rachel.ibmpcug.co.uk's message of Mon, 21 Dec 1992 13:06:34 GMT

In article <BzM1qz.9MI@ibmpcug.co.uk> adrian@rachel.ibmpcug.co.uk (Adrian Hall) writes:
>It seems that packets for ref.tfs.com from Pipex (and presumably, anyone
>on the AlterNet too) get continually bounced between the following two
>routers :- [ ... ]

is this a 'permanent' condition, or one that occurs only occasionally?

the reason that i ask is that i've noticed the UCB has occasionally
had trouble routing to ref (and TFS in general), and TFS is sitting
directly off UCB, i believe, on BARRNet...

BARRNet's had a bunch of routing problems lately...

cgd
--
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
From: jkh@whisker.lotus.ie (Jordan K. Hubbard)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] GNU malloc in favor of BSD malloc in libc - shall we vote?
Date: 3 Jan 93 16:55:28 GMT
	<1i0cnoINNiu2@life.ai.mit.edu> <C05wCD.Bp0@demon.co.uk>
Organization: Lotus Development Ireland

It's unfortunate that GNU ld relies on malloc(0) to work.  I've modified
GNU malloc to round zero size requests to 1, if STRICT_MALLOC isn't
defined.  It's not a good solution, by any means, but it beats (for the
moment) tracking down the erroneous behavior in GNU ld.

					Jordan
--
Jordan Hubbard		Lotus Development Ireland	jkh@whisker.lotus.ie
I DO NOT SPEAK FOR LOTUS - IT HAS PLENTY OF LAWYERS TO DO THAT FOR IT ALREADY
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [386bsd] GNU malloc in favor of BSD malloc in libc - shall we vote?
Organization: Weber State University  (Ogden, UT)
Distribution: comp
Date: Fri, 1 Jan 93 10:20:32 GMT

In article <JKH.92Dec31154004@whisker.lotus.ie> jkh@whisker.lotus.ie (Jordan K. Hubbard) writes:
>I say we petition Bill to use GNU malloc in preference.  Most folks aren't
>going to know enough (or dare) to replace malloc in libc themselves, but
>they will notice the very painful state of affairs that trying to work
>in a low memory environment brings; why not spare them the pain?

If we are going to vote, I vote for one of the PD malloc implementations
as opposed to the GNU copyleft implementation.  There are many reasons,
some stated by Lynne and Bill, for keeping 386BSD salable without sources;
GNU copyleft ruins this.


					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: veit@du9ds3.fb9dv.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] How do I know what's on the etc disks?
Date: 29 Dec 92 11:15:31 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.fb9dv.uni-duisburg.de
NNTP-Posting-Host: du9ds3.fb9dv.uni-duisburg.de

In <gary.725607738@mama> gary@mama.minmet.uq.oz (Gary Roberts) writes:

>rich@Rice.edu (& Murphey) writes:

>>>>>>> In article <Bzqnq0.8ut@ais.org>, draper@ais.org (Patrick Draper) writes:

>>P> Is there an index to the etc distribution that is on wuarchive? There's over
>>P> 90 of them now, and I can't really take to the time to sift through them all
>>P> to find the good stuff.

>>yes, on agate.berkeley.edu (128.32.136.1):
>>/pub/386BSD/386bsd-0.1/filesystem/MANIFEST.etc01.files
>>Rich

>Only problem is that this file seems *exactly* the same as the .src01. file.
>I noticed this when I recently installed the bin01 src01 and etc01
>distributions on my 486DX33 notebook and casually started to glance through
>these manifests out of interest.  I just looked on agate and sure enough,
>both src01 and etc01 manifests are still identical in size.  It would be
>nice if some kind soul could put up the correct manifest.

>Cheers,  Gary.
>Gary Roberts		   |  Ph:    +617-3654176


Get the CONTENTS.CPIO.Z files in the /pub/unix/386bsd-0.1/{src,bin,etc}dist
directories at ftp.uni-duisburg.de (134.91.100.14). Perhaps some admins
of other archives should get them as well and add them to their dist dirs.
This is the list of files you get with cpio -itv.

Happy new year

Holger

-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.fb9dv.uni-duisburg.de
|__|  /  University of Duisburg  |
|  | /   Dept. of Electr. Eng.   |          "Understand me correctly:
|  |/    Inst. f. Dataprocessing |     I'm NOT the WIZARD OF OS" (Holger)
Newsgroups: comp.unix.bsd
From: scott@pita.cns.ucla.edu (Scott Burris)
Subject: Re: Does 386BSD work on systems with 20 megabytes of memory! HELP!
Distribution: comp.unix.bsd
Date: 29 Dec 92 11:03:56 PST

gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart) writes:

>In article <1992Dec29.082629.3222@convex.com> grefen@convex.com writes:
>>In article <287902vW30DE01@JUTS.ccc.amdahl.com>, tjw00@zombie.uucp (Tom Wye) writes:
>>|> Does 386BSD work on machines with 20 megabytes of memory or more? HELP!!!!
>>|> 
>>|> The system slowly crashs and burns when I boot with 20 megabytes of storage     
>>|> installed. The same kernel runs ok with 4 megabytes.
>[...]
>>|> Memory in bank 0 - 4 x 1m sims for 4M 
>>|> Memory in bank 1 - 4 x 4m sims for 16M 
>>|> Adaptec 1542BB
>>This is it, the Adaptec can only DMA into the lower 16M of RAM ... you loose.
>>You need an  Adaptec 174x (EISA) or change the code in the driver to use a 
>>buffer and copy the data for requests outside the first 16M.

>I had the same problem and heard about the problem with first 16M and the 1542.
>So I put only 16M to my box. Now my question is, does Julian's SCSI-Kit
>handle that correctly, e.g. does it use such buffers to avoid direct access
>to memory above the 16M ?

>Ralf

I had thought I had seen a message about Julian's drivers using buffers
for the over 16M problem, but I foolishly brought my system up to 20M on
the weekend and had all sorts of problems.  I'm running Julian's drivers
and the patches from the patchkit.  So I guess the answer is no or its
broken.


-- 
----------
Scott Burris
UCLA Campus Network Services
cnetslb@oac.ucla.edu (310) 206-4860 - OR - scott@pita.cns.ucla.edu
From: rgrimes@agora.rain.com (Rodney Grimes)
Newsgroups: comp.unix.bsd
Subject: Re: New kernel on rachel.ibmpcug.co.uk
Date: 26 Dec 92 11:40:00 GMT
Article-I.D.: agora.Bzv72p.2F1
Organization: Open Communications Forum

[stuff deleted]

>This driver is now currently set up as major device 16 in the kernel
>on rachel.ibmpcug.co.uk.

>Anyone think there is a call for a central "person" who gives out
>major device numbers to those developing device drivers?

Absolutely, and here is my request for a dev number for the fd device
(All the support is there it is just missing from the cdev table and
the /dev/MAKEDEV has it at 53 wich is way wrong (unless you are running
BSD4.3 on a vax!!)  I have assigned it a number on my system and it works
fine (fixes make tags in the source tree and things that use /dev/stdin,
/dev/stdout)

-- 
Rod Grimes						rgrimes@agora.rain.com
Accurate Automation Company          All opinions belong to me and my company!
From: rdr@cl4.alliant.com (Roger Roles)
Subject: Re: WD8003E ethernet card compatibility
Keywords: AKCL Common LISP Kyoto Austin 386BSD
Organization: Alliant Computer Systems, Littleton, MA
Date: Tue, 22 Dec 1992 00:18:05 GMT

In article <1gorbsINN8ku@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
>Has anyone managed to get 386BSD to work correctly with the WD8003E ethernet
>card?

I managed (after long debugging sessions :-) to get a WD8003E ethernet card
working. The first step was to configure a kernel without the Isolan driver,
which is configured to the same I/O address in the standard config. The symptom
before this was done was a lot of "reject 32..." (I can't remember the exact
number) messages whenever the interface was configured up.

After getting past that problem, I discovered that most of the transmissions
were being garbled, as evidenced by checksum errors on remote machines which
were receiving the packets, and no replies being received. I am not sure what
the cause of this was, unless the machine (a 486/33) was trying to load data
into the board's buffer too fast, but the symptom was that immediately after
doing a bcopy of the data onto the board, a comparison between the mbuf and
the buffer showed numerous differences. I "fixed" this (a truly gross hack,
probably with significant speed impact, but it works fast enough for my
purposes) by comparing every byte and rewriting it until the correct value
appeared in the board buffer. I limited the attempts to store the correct
value to the board to 10, so as to avoid an infinite loop if the board was
truly unable to receive the correct value. So far, the count of 10 limit
has never been reached.

I now know that there are versions of the dist.fs floppy image available
on agate.berkeley.edu (/pub/386BSD/386bsd-0.1/unofficial/newbootables/cgd)
which are built without the isolan driver, for those who can't build new
configs until the ether is clear :-).

-- 
Roger D. Roles		OS Development
RR77, rdr@alliant.com, alliant!rdr	508.486-1211
Xref: sparky comp.unix.bsd:10548 comp.os.linux:21398
From: kankkune@klaava.Helsinki.FI (Risto Kankkunen)
Newsgroups: comp.unix.bsd,comp.os.linux
Subject: Re: Dumb Americans (was INTERNATIONALIZATION: JAPAN, FAR EAST)
Date: 22 Dec 92 01:04:23 GMT
Organization: University of Helsinki, Department of Computer Science

>Problem is that programs have to be started through windowing system. Therefore
>this schema doesn't suit for Linux, even though it could be possible to make
>an special window manager for X+Linux to support full localization, but this
>would make Linux incompatible.

X has already support for automatically selecting resources based on
users language, so you don't need any special window managers for this.

For non-X programs, much can be done with extensive use of the locale
functions and using some configuration files to contain the texts the
program outputs.

By the way, the X resource manager is a separate module, which can be
used by non-X programs, too. I think it would be nice to use it in text
based programs, so all the configuration files would have the same
syntax. And if you have a text and window version of a program, they
could share the same configuration file.

-- 
                                         A witty signature proves nothing
Newsgroups: comp.unix.bsd