HDTenEightyP/NetNews huggingface dataset:
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Correct values for float.h, compiling gcc-2.3.3
Organization: Weber State University  (Ogden, UT)
Date: Tue, 26 Jan 93 21:16:16 GMT

In article <1993Jan26.083016.13402@data.fls.dk> phk@data.fls.dk (P-HK/Poul-Henning Kamp) writes:
>bsd@yrloc.ipsa.reuter.COM (Brian de Alwis) writes:
>
>>What exactly are the correct values for <float.h>?
>
>>This problem has come up while attempting to compile gcc-2.3.3 (are
>>there any patches out there? I couldn't find any, with my limited
>>resources here). It seems that the build proceeds with no problems
>>until enquire.c is compiled with the new xgcc. On line 2307, it
>>craps out with a `floating point constant out of range'. I haven't
>>had too much time to look at any further.
>
>The problem lies with [efsv]printf and very small numbers, like the smallest
>normalised number 2.225073858507201383090232717332404064219e-308
>and the next smaller 2.22507385850720088902458687608585988765e-308 comming
>out the same.

This, in turn, is the result of the "round-up" being set on the float-to-int
conversion in the math library sources.  There have been patches for both
posted, but nothing definative has been done about testing how well they
work with the "correct" float.h values.

Volunteers, anyone?


					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
-------------------------------------------------------------------------------
Organization: Sophomore, Electrical and Computer Engineering, Carnegie Mellon, Pittsburgh, PA
Newsgroups: comp.unix.bsd
Date: Thu, 28 Jan 1993 02:37:12 -0500 
From: Peter William Wieland <pw1r+@andrew.cmu.edu>
Subject: [386BSD] Using bad144?


I'm trying to mark off all of the bad blocks on my MFM drive.  The
installation notes claim that BSD will give me some form of error
message whenever it trys to write to a bad block, but I haven't seen any
messages, and I'm almost certain the installation has used the bad areas.

So my question is:

Knowing the bad tracks on my drive (cylinder & head), how do I compute
the block number(s) that are bad.  

For example, if I wanted to mark track 101:4 (cylinder:head) as bad,
what are the block numbers that I want to feed to bad144.

Or is there a simpler way that I missed.  I looked through the FAQ, man
pages for bad144, fsck, badsect, and checked the installation notes.  Is
there a program which will check my drive for bad blocks and report
block numbers back to me?

Any help would be appreciated.
-peter wieland

****************************************************************************
None of the ideas expressed above are acutally mine.  They are told to
me by Luthor and Ferdinand, the five inch tall space aliens who live
under my desk.  In return for these ideas, I have given them persmision
to eat any dust bunnies they may find under there.
Peter Wieland               pw1r+@andrew.cmu.edu            dmonger+@cmu.edu
Newsgroups: comp.unix.bsd
From: veit@borneo.gmd.de (Holger Veit - SYDIS)
Subject: Re: su problems.
Organization: GMD
Date: Wed, 27 Jan 1993 17:11:14 GMT

In article <1993Jan27.070108.27600@ucsu.Colorado.EDU>, galbrait@rintintin.Colorado.EDU (GALBRAITH JOHN) writes:
|> Hi, 
|> 	On my 386bsd machine, nobody can su to root.  There is no
|> password (confirmed by checking the password file a hundred times), yet
|> it asks for one anyway.  I tried setting a password, but it would not
|> accept it.  The /etc/group file is ok too.
|> The only way to become root is from the login: prompt.  Then,
|> no password is needed.  Obviously, this is a pain.  Does anybody know
|> what is going on?  Thanks.
|> 
|> john galbraith
|> galbrait@rintintin.colorado.edu
|> 

You are aware that a user must be in the group wheel or may become member of
group wheel to sucessfully execute su, aren't you? Your
group file might need a line like the following:

wheel:*:1:root,bill,lynne,galbrait

or alike (provided your account is 'galbrait' as in your posting).

Hope that helps


-- 
         Dr. Holger Veit                   | INTERNET: veit@fanoe.gmd.de
|  |   / GMD-SET German National Research  | Phone: (+49) 2241 14 2448
|__|  /  Center for Computer Science       | Fax:   (+49) 2241 14 2342
|  | /   P.O. Box 13 16                    |    Three lines Signature space
|  |/    Schloss Birlinghoven              |    available for rent. Nearly
         DW-5205 St. Augustin, Germany     |    unused, good conditions
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [386BSD] Still trying to install...
Organization: Weber State University  (Ogden, UT)
Date: Sat, 23 Jan 93 23:55:53 GMT

In article <1993Jan20.075418.26319@Princeton.EDU> bkc@ernie.Princeton.EDU (Bruce Caruthers) writes:
>Booting from the floppy works fine for that basic level (20-30 secs
>until prompt), and shutdown -todos works fine, but warm boot from DOS
>(either after changing the active partition, or straight to a BSD
>floppy) hangs.

Compaq boot problem.  See numerous previous posts on the matter.  Fixed in
next patch kit.

1)	Get a Compaq boot file
2)	Wait for patchkit 0.2 and install the patch on another machine,
	make a boot disk, and boot your machine.
3)	Wait for patchkit 0.2 to be installed and a boot disk generated
`	by someone else, and boot your machine.


					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: beattie@agora.rain.com (Brian Beattie)
Newsgroups: comp.unix.bsd
Subject: Need patch posted for lost physical pages (386BSD)
Date: 28 Jan 93 03:21:35 GMT
Organization: Open Communications Forum

I recal that somebody posted a patch to fix a bug that caused
the 386BSD kernal to lose track of physical pages of memory.

Could somebody be so kind as to mail me a copy of that posting?

Thanx beattie@agora.rain.com
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: [386bsd] 805 vs. 801
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
Distribution: comp.unix.bsd, comp.os.linux
Date: Thu, 28 Jan 1993 23:30:32 GMT


Actix has been kind to loan me one of their 805 local bus cards for two
weeks. So I should be able to compare my Actix GraphicEngine32 (S3 801) 
against the Actix GraphicEngine32 VLB (S3 805 Vesa Local Bus).


The 805 card which I have is from a different manufacturer.

I should be able to report back this weekend because I am getting
their Local Bus card tomorrow :-)

Cheers,
Amancio
-- 
This message brought to you by the letters X and S and the number 3
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: jh@efd.lth.se (Joergen Haegg)
Newsgroups: comp.unix.bsd
Subject: Problems with wt-driver, or rawwrite. (using QIC-02)
Date: 22 Jan 93 09:14:50 GMT
Organization: Lund Institute of Technology, Sweden

I have a Everex 831 QIC-02 with a QIC36 streamer.
Reading works OK, but writing is erroneous.

The problem seems to be that the wt-driver writes a record (512 byte)
when the computer fails to feed the driver with data. So far all good.
But it will write the record even if it is not completely filled with data!
The result is that records are filled with nulls up to 512 byte.

No data loss, instead a lot of extra nulls appear when I read from the tape.
Makes tar crazy...

It might also be the rawwrite-routine which is incorrect, I don't know.

The following program demonstrates the problem.
Try it and read the result back with dd. Examine with less.


#include <stdio.h>
#include <fcntl.h>

main()
{
	int	i, j, fd;
	char	buf[65], buf2[513];

	setbuf(stdout, NULL);
	if ((fd = open("/dev/rwt0", O_WRONLY)) < 0)
	{
		perror("open");
		exit(1);
	}

	for (i = 0; i < 1000; i++)
	{
		*buf2 = '\0';
		for (j = 0; j < 10; j++)
		{
			sprintf(buf, "%04d.%d.--AAAAAAAAAABBBBBBBBBBCCCCCCCCCC"
				"DDDDDDDDDD\n", i, j);
			strcat(buf2, buf);
		}
		write(fd, buf2, 500);

		printf("%4d\r", i);
		if (!(i % 100))
			sleep(1);
	}
	close(fd);
}

-- 
Joergen Haegg				jh@efd.lth.se
System manager @ efd			Phone: international +46 46 107492
Lund Institute of Technology		Snailmail: DDG, Maildelivery 7, BOX 118
Fax: +46 46 104013			S-221 00 LUND, Sweden
From: dittman@skitzo.dseg.ti.com (Eric Dittman)
Newsgroups: comp.unix.bsd
Subject: [386bsd] Always IN-2000 supported?
Date: 22 Jan 93 18:53:38 CDT
Organization: Texas Instruments Component Test Facility

Does 386BSD support the Always IN-2000 SCSI controller?
-- 
Eric Dittman                  Texas Instruments - Component Test Facility
dittman@skitzo.dseg.ti.com    (214) 578-3575
Disclaimer:  Not even my opinions.  I found them by the side of the road.
From: lessen@axion.bt.co.uk (Lee Essen)
Newsgroups: comp.unix.bsd
Subject: [386BSD] 386bsd, the universe and everything
Date: 28 Jan 93 11:47:36 GMT
Reply-To: lessen@axion.bt.co.uk (Lee Essen)
Organization: British Telecom Research Labs



I'm not yet running a 386bsd system and have only recently got the
distributions sets. I've written the new dist.fs.pk-0.2 filesystem
to a floppy (from a Sun - dd if=dist.fs.pk-0.2 of=/dev/rfd0c bs=9k),
in an attempt to test this I booted a portable (which happened to be
close at the time [don't know the spec]) with the disk. It came up
with no problem (better than most commercial releases!!!) I was just
having a quick look round and I typed 'pwd' which obviously does not
exist on the floppy, I got the 'cant exec /bin/pwd' (or something
close) message. After this every directory appears empty!! Is this
normal?


This may be a question that's been asked before but I can't find any
references...

I'm looking at getting a SCSI card for my PC, the price of these varies
quite dramatically from about 20 pounds for an ST01/02 up to about 180
pounds for an Adaptec 154x, with the Future Domain ones in the middle.

I have read somewhere (I can't remember where) that the Seagate ST01/02
cards ONLY work with DOS and ONLY support drives up to 100MB. Is this
true? Do they have an external SCSI connector for CD-ROM etc...

What kind of SCSI card support is there for 386BSD now! - I have read
the messages in the SCSI source directory and there are references to
both the Seagate and Future Domain controllers, with a note that says
something like there are just a bit more than a dream!! - is that up
to date?


Another question i'm sure's been asked!!

I've currently got a IDE controller, i've also got a MFM controller
and drive! - can I get these to co-exist!

And...

A while ago there were some mutterings about DOS emulation from within
386BSD, did anything come of this?  Are there any implementations?


Thanks,

Lee Essen
Newsgroups: comp.unix.bsd
From: ac116@city.ac.uk (Tarkan)
Subject: [386BSD] how to get 386BSD from a tar tape
Summary: anyway of getting 386BSD without using cpio
Keywords: tape tar 386BSD
Organization: The City University
Distribution: comp
Date: 24 Jan 93 17:23:18 GMT

I Have FTP'd 386BSD 0.1 and placed it on a QIC150 format tape
with the unix TAR command,,,as tiny 386BSD has no TAR command 
is it possible for me to get the TAR binary from anywhere which 
will work on my machine ,,so I could take the distrubtion off
the tape using TAR,,


-- 
************************************************
* if you haven't guessed yet...                *
*  Tarkan....             at: ac116@city.ac.uk *
********************************auto*signature**
From: vax@ccwf.cc.utexas.edu (Vax)
Newsgroups: comp.unix.bsd
Subject: [386bsd] Setting up a slip connection
Date: 21 Jan 1993 23:38:02 GMT
Organization: The University of Texas at Austin, Austin, Texas
Distribution: world
Reply-To: vax@ccwf.cc.utexas.edu (Vax)
NNTP-Posting-Host: bashful.cc.utexas.edu

I think it would be a good idea to show new users how to set up a slip
connection in a FAQ-type way.  As far as I know, there is a slipup.perl
which is a modified version of larry wall's on a ".jp" computer
(I archied for it).  It seems to work extremely well.  But the named is
a tricky
and complicated beast; especially if you just want to connect one machine to a
dial-in slip connection!!!
It would be nice if someone showed how to set up a sample file to do this.
Nothing fancy; no primary domain servers, just a forward line, etc....

I see the following files as important:
	/etc/hosts
	/etc/named.boot
	/etc/named.local (?)
	/etc/hosts.equiv (?)

For example, we probably don't want to call our machine localhost, so how
do we set up these files?  With what should we prime the root cache?

How do we set up the route stuff, as well?  I used to use
ifconfig net host local -hopcount 1
route add default host -metric 1

with dialup-slip, but I don't think slipup uses this...  it seems to mess up
the routing in this case...  Whassup with this?

Thanks in advance, and reply by news if possible!

--
Protect our endangered bandwidth - reply by email.  NO BIG SIGS!
VaX#n8 vax@ccwf.cc.utexas.edu - finger for more info if you even care.
Newsgroups: comp.unix.bsd
From: bde@runx.oz.au (Bruce Evans)
Subject: [386BSD] Bug + fix: getcwd off by one
Organization: RUNX Un*x Timeshare.  Sydney, Australia.
Date: Fri, 22 Jan 93 18:52:11 GMT

getcwd() has two off-by-one bugs in 386BSD-0.1:

1. getcwd(buf, size) fails when the size is just large enough.
2. getcwd(buf + 1, 1) incorrectly succeeds when the current directory
   is "/".  buf[0] and buf[2] are clobbered.

This program demonstrates the bug:

---
#include <stdlib.h>
#include <string.h>
#include <stdio.h>
#include <unistd.h>

int main(void)
{
    char buf[5];
    int errors;

    errors = 0;
    if (chdir("/tmp") != 0) {
	perror("chdir");
	abort();
    }
    if (getcwd(buf, 5) == NULL) {
	perror("oops, getcwd failed for buffer size = size required");
	++errors;
    }
    if (chdir("/") != 0) {
	perror("chdir");
	abort();
    }
    buf[0] = 0;
    buf[2] = 1;
    if (getcwd(buf + 1, 1) != NULL) {
	fprintf(stderr,
		"oops, getcwd succeeded for buffer size = one too small\n");
	++errors;
    }
    if (buf[0] != 0) {
	fprintf(stderr,
		"oops, getcwd scribbled on memory before start of buffer\n");
	++errors;
    }
    if (buf[2] != 1) {
	fprintf(stderr,
		"oops, getcwd scribbled on memory after end of buffer\n");
	++errors;
    }
    exit(errors == 0 ? 0 : 1);
}
---

This might be a fix:

---
*** /usr/src/lib/libc/gen/getcwd.c~	Wed May  1 10:35:50 1991
--- /usr/src/lib/libc/gen/getcwd.c	Tue Jan 19 22:22:38 1993
***************
*** 74,78 ****
  	if (pt) {
  		ptsize = 0;
! 		if (!size) {
  			errno = EINVAL;
  			return((char *)NULL);
--- 74,78 ----
  	if (pt) {
  		ptsize = 0;
! 		if (size < 2) {
  			errno = EINVAL;
  			return((char *)NULL);
***************
*** 186,190 ****
  		 * leading slash.
  		 */
! 		if (bpt - pt <= dp->d_namlen + (first ? 1 : 2)) {
  			size_t len, off;
  
--- 186,190 ----
  		 * leading slash.
  		 */
! 		if (bpt - pt < dp->d_namlen + (first ? 1 : 2)) {
  			size_t len, off;
  
---
-- 
Bruce Evans  (bde@runx.oz.au)
From: gene@stark.uucp (Gene Stark)
Newsgroups: comp.unix.bsd
Subject: Busmouse and patch00061 (FIX)
Date: 26 Jan 93 08:52:24
Organization: Gene Stark's home system
Distribution: world
NNTP-Posting-Host: stark.uucp

These diffs are for Rick Macklem's 386bsd-busmouse driver, which can be
found at host snowhite.cis.uoguelph.ca.  There are some prior minor fixes it
needed to work with a Microsoft bus mouse.  I posted such fixes a few months
ago, but I don't know if they got incorporated into his sourcs.

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/mse.c.pl1	Sun Nov  1 01:13:00 1992
--- /sys/i386/isa/mse.c	Tue Jan 26 07:48:14 1993
***************
*** 51,57 ****
  struct mse_softc {
  	int	sc_flags;
  	int	sc_mousetype;
! 	struct	proc *sc_selp;
  	u_int	sc_port;
  	void	(*sc_enablemouse)();
  	void	(*sc_disablemouse)();
--- 51,57 ----
  struct mse_softc {
  	int	sc_flags;
  	int	sc_mousetype;
! 	pid_t	sc_selp;
  	u_int	sc_port;
  	void	(*sc_enablemouse)();
  	void	(*sc_disablemouse)();
***************
*** 289,295 ****
  	 * Since this is an exclusive open device, any previous proc.
  	 * pointer is trash now, so we can just assign it.
  	 */
! 	sc->sc_selp = p;
  	splx(s);
  	return (0);
  }
--- 289,295 ----
  	 * Since this is an exclusive open device, any previous proc.
  	 * pointer is trash now, so we can just assign it.
  	 */
! 	sc->sc_selp = p->p_pid;
  	splx(s);
  	return (0);
  }
***************
*** 301,307 ****
  	int unit;
  {
  	register struct mse_softc *sc = &mse_sc[unit];
! 	struct proc *p;
  
  #ifdef DEBUG
  	static int mse_intrcnt = 0;
--- 301,307 ----
  	int unit;
  {
  	register struct mse_softc *sc = &mse_sc[unit];
! 	pid_t p;
  
  #ifdef DEBUG
  	static int mse_intrcnt = 0;
***************
*** 324,330 ****
  		}	
  		if (sc->sc_selp) {	
  			p = sc->sc_selp;	
! 			sc->sc_selp = (struct proc *)0;	
  			selwakeup(p, 0);	
  		}	
  	}
--- 324,330 ----
  		}	
  		if (sc->sc_selp) {	
  			p = sc->sc_selp;	
! 			sc->sc_selp = (pid_t)0;	
  			selwakeup(p, 0);	
  		}	
  	}
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: telnetd without login check
Organization: Weber State University  (Ogden, UT)
Date: Sun, 24 Jan 93 00:34:30 GMT

In article <br.pct.13.727678893@RLG.Stanford.EDU> br.pct@RLG.Stanford.EDU (PCT) writes:
>
>Hi,
>
>  I have a special situation where I want to have the 386/Sun Sparc-2 
>running 386BSD/SunOS 4.1.1 to be a telnet server front end to a mainframe 
>telnet server.But I only want to login once, so I have to find out how to 
>disable loginbanner & all from the front end telnet server, so that the 
>telnet connectiongoes all the way thru, then the mainframe generate a login 
>banner instead.
>
>  Is it possible in 386BSD? Without getting the telnetD code & hack it, 
>by just  fixing the inetd.conf to run telnetD with -a none or ttytab or 
>whatever?

Nope.  You have to hack telnetd.  The best way to do this would be to hack
it to take arguments of what to run, and a flag to determine if you need to
run code that you will steal from rlogind as well (ie: the device setup
normally done by login).  This will let you run bbs software or any other
software you want to by specifying a line in /etc/inetd.conf with your
new telnetd with it's arguments.  For backward compatability, the lack
of arguments should cause it to run as it currently does.

An alternative might be to get the "socket" code ("socket" is a program to
allow shell-level manipulation of sockets) and put it on the port you will
telnet to for this service.  This assumes that you aren't running the old
telnet code on the originator or the old telnetd code on the target, and
that the target is always a telnetd.  If this is the case, then options
negotiations can ake place normally; otherwise they will fail.


					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: curt@toad.com (Curt Mayer)
Newsgroups: comp.unix.bsd
Subject: floating point exceptions
Date: 26 Jan 93 02:54:26 GMT
Distribution: world
Organization: Ethnopharmacological Disneyland
Keywords: signal 6, gcc2.3.3

alright, so i reinstalled from ground zero for the 4th time, installed
the latest patch kit from agate, recompiled the world, so why do i
still get these signal 6's all over the place when trying to recompile ?

do I have a defective 486? 
am i the only one that gets these? 
should I disable the on-chip fpu? 

i see complaints on here about gcc2.3.3 not building
enquire.c with 'out of range double' or something. gcc2.3.3 detects
these by catching signal 6. some people cryptically write "just tweak
the DBL_MAX and DBL_MIN values in this here magic include file".
and then what? rebuild the compiler? libc? reinstall from ground zero?

	confused.

p.s. except for floating point, 0.1 with patchset 0.2 is pretty solid.


-- 
	curt mayer
        curt@toad.com
        415-387-0217 home
From: cs170501@vtaix.cc.vt.edu (Someone Interesting)
Newsgroups: comp.unix.bsd
Subject: Kernel Panicking
Date: 27 Jan 93 00:11:34 GMT
Organization: Virginia Tech, Blacksburg, VA

Subject: Problems with kernel crashing.

About one or two times per day I get a core dump, and system panic with the
following message:

panic: kmem_malloc: kmem_map too small


-----------

I know this is to do with the kmem and mem files for accessing the memory
directly and for using swap space on disk.  Is there a problem with these
files that I can somehow correct?  Or is there something else that I need
to do.  Please respond via email, as this is sort of urgent.  Thanks!



Matthew C. Mead

Newsgroups: comp.unix.bsd
From: dvc@eagle.hr.att.com (David Van Cleef)
Subject: Re: [386BSD] Advice on System Wanted
Originator: news@cbnewsb.cb.att.com
Organization: AT&T Bell Laboratories
	<1993Jan21.083507.17269@ucsu.Colorado.EDU>
Distribution: na
Date: Thu, 21 Jan 1993 16:23:35 GMT

>>>>> On Thu, 21 Jan 1993 08:35:07 GMT, galbrait@rintintin.Colorado.EDU (GALBRAITH JOHN) said:
>>What kind of monitor should I get.  I want a 14" NI .28 pitch...what 
>>manufacturers are good?
>
>I got a "CTX" monitor.  It looks OK, but I've only had it for 6 weeks,
>so I can't talk about reliability.
>
GJ> I can.  My CTX 1560 monitor broke while using XFree86.  Although I think
GJ> that it was because I had abusive settings in the Xconfig file, but
GJ> I can't say for sure. (I got a replacement monitor and duplicated the
GJ> MS windows retrace signals exactly with the oscilloscope in XFree86.  So
GJ> far, I have had no problems.)
GJ> 	However, if you read recent computer mags they all hate the CTX
GJ> due to fuzzy corners (confirmed by me.)  Also, tech support is weak, with
GJ> a turnaround time of over 2 weeks for a broken monitor. (Most other companies
GJ> are 48 hours or less.)
GJ> 	My advice : look at something else.  (However, there are some things
GJ> I like, but I don't think these features are unique to CTX.)

Seconded.  I lost a CTX 1561NI while trying to get 1152x900 interlaced
mode (which I calculated the numbers for using the specs in the back
of the monitor's manual: they weren't exceeded.)  The picture wouldn't
fit on the screen (about 1/4" of rollover), and shortly thereafter,
the screen cut out completely.  (This was with the X386 1.3 included
with BSDI gamma 0.9.4.)
--
David A. Van Cleef			AT&T Bell Laboratories
internet: dvc@eagle.hr.att.com		Red Hill Facility, Middletown, NJ
					+1 908 615 4906
Newsgroups: comp.unix.bsd
From: adasal@netcom.com (Salvatore Collora)
Subject: NN
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Tue, 26 Jan 1993 00:03:38 GMT

Hello all.

I got the NN sources from UUnet.  I set everything up on my machine.
I compiled it using BSD4.3 M file, and a Sun386 S file. (the 386 file
didn't even compile so I figured Sun386 would be closest.)  It compiled 
with a few warnings, but it did finish.

I ran the program, and it said: BUS ERROR (core dumped)

I am no C Expert, but I am pretty sure that it is related to
the S file.  What I need to know is if ANYONE has gotten
NN compiled on 386BSD and had it work?

Any help, as always is appreciated.  please reply by mail and not
through news.  Sometimes I don't get a chance to check the news and
it purges.

Sal