HDTenEightyP/NetNews huggingface dataset:
From: meissner@osf.org (Michael Meissner)
Subject: Re: 386BSD's non-standard C library
Organization: Open Software Foundation
	<rcskb.718045970@minyos.xx.rmit.OZ.AU> <16591@ksr.com>
Date: Wed, 7 Oct 1992 03:16:39 GMT

In article <16591@ksr.com> dean@ksr.com (Dean Anderson) writes:

| In article <rcskb.718045970@minyos.xx.rmit.OZ.AU> rcskb@minyos.xx.rmit.oz.au (Kendall Bennett) writes:
| 
| >Oh? That is my problem? I assume that since this is a new standard (first
| >proposed back in what - 1983?), and it is not supported on all systems
| 
| The standard was not accepted until 1989 or so.  My unapproved draft copy 
| is dated December 1988.

ANSI C was approved in December of 1989.  ISO C was approved in 1990
(December again I think).  ANSI and ISO C are technically the same.
POSIX came out in 1988 (trail use I think), and again in 1990.

| >I should not use it, but write my code in pre-historic K&R C with lotsa
| >#defines since non K&R system is ever comapatable with another?
| 
| If you want to be portable(ie, run on lots of systems), this is what 
| you have to do. Maybe you should just stick with DOS.  There are a 
| lot of those systems.

Now that it is three or four years from the approval, I am less and
less enthused about the crutches of supporting systems whose vendors
are asleep at the wheel.

	...

| Go ahead and write ansi and posix only code.  It will be a while before
| it will run on vast numbers of systems.  I personally don't like ansi
| C because it violated its charter to document the existing language as
| a standard.  I don't think that all the decisions were correct, and I
| don't think the community was permitted to test out the ideas well
| enough.  Innovation by committee usually produces very bad results.

Documenting the existing language was only one of the goals.  Another
was to fix things.  You can't satisfy conflicting goals completely.

| The point here is that not everyone has an ansi compiler.  Very little 
| code will work with an exclusively ansi compiler.  Some people cannot
| have both -traditional and -ansi built into their compiler.

Then complain to the vendor, write your own compiler, and/or use GCC.
As a compiler writer (who by the way has written a C front end from
scratch), I seriously doubt providing both traditional vs.  ansi
support in any non-toy compiler is all that much code.  Yeah, there
are some dark corners, and such, and it may make you keep a tiny bit
more state than if you have a traditional compiler or an ansi compiler
alone, but if the compiler vendor can't hack it, they are obviously in
the wrong profession.

| >>Not shortcuts, exactly. The library *predates* the standard. For example,
| >>the ANSI standard changed the behaviour of tolower for most compilers.

Actually in this case, it depends on whether you came from the BSD
universe or System V (the standard picked System V for the most part).
--
Michael Meissner	email: meissner@osf.org		phone: 617-621-8861
Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142

You are in a twisty little passage of standards, all conflicting.
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.unix.bsd
Subject: Re: Wangtek 5150ES's for $349
Date: 1 Oct 92 05:38:03 GMT
Organization: St. Peter's College, US

In article <1992Sep30.054324.26194@msuinfo.cl.msu.edu>, paoletti@cps.msu.edu (David R. Paoletti) writes:
> The following ad was posted to misc.forsale.computers, and I've
> purchased one.  I am very satisfied with the drive (except maybe
> the black faceplate ;), and the person selling them was very prompt,
> courteous, and helpful when I had a slight problem (cause == me).

  I'll second this. I've purchased a bunch of these from him.

  If you really want a beige faceplate, call Wangtek at (805) 583-5255,
ask for Spare Parts Sales, and order part 30016-014. The 5150ES OEM man-
ual is part 63045-001, by the way.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Could the passwd/crypt changes be included in the patch kit?
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Mon, 5 Oct 1992 14:10:05 GMT

I was wondering if the passwd/crypt changes could be included in the patch
kit in a way that does not violate the goofy export restrictions (assuming
that they still apply, which I am told is not the case).  Perhaps a stub
module could be used or something, or an *imported* version of the crypt
code?

-- 
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA
Newsgroups: comp.unix.bsd
From: dvc@eagle.hr.att.com (David Van Cleef)
Subject: Re: 386BSD on an ESDI/SCSI sytem
Originator: news@cbnewsb.cb.att.com
Organization: AT&T Bell Laboratories
Date: Mon, 28 Sep 1992 17:59:52 GMT

>>>>> On Fri, 25 Sep 1992 23:20:06 GMT, jim@stargate.helios.nd.edu (Jim McCusker) said:

JM> Has anyone installed 386BSD on a 2 drive system using different controllers?

JM> My system is using an Ultra 12F ESDI HD/FLP controller and an Adaptec 1542B SCSI

JM> controller.  I use the ESDI controller to control the floppies currently.
JM> Anyway, the ESDI HD is 100Megs and the SCSI is 200Megs.  I'd like to setup 386BS
JM> i
JM> MS-DOS on the ESDI drive and 386BSD on the SCSI.

JM> Can this be done?  If so how...

1. Make sure to have the BIOS enabled on the 1542B.

2. To access the DOS drive, set the CMOS setting for the C: drive to
the appropriate setting for the ESDI drive type.

3. To access the BSD drive, set the CMOS setting to 'Not Installed'.

This is probably the only way to deal with this with stock hardware.
I have not tested it as yet, but will probably be doing so in the next
week on a system with a 200MB IDE for DOS, and a 200MB SCSI for BSDi/386.
--
David A. Van Cleef			AT&T Bell Laboratories
internet: dvc@eagle.hr.att.com		Red Hill Facility, Middletown, NJ
					+1 908 615 4906
From: gab10@cd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: Cross booting BSD <-> DOS
Keywords: Cross Booting,Partition Tables,DOS,BSD
Date: 2 Oct 92 07:30:20 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <ganter.717794149@milton>, ganter@milton.u.washington.edu (M.
Ganter) writes:
> I have BSD running on my 486DX-33.  I am impressed!  Thanks to all
> for more than a job well done.  I have my 200 MB partitioned with
> 80 MB for DOS and 120 MB for BSD.  I've read 386BSD.FAQ and BUGLIST
> so I understand that shutdown -todos does not work.  Currently, I've
> been using the boot off floppy technique (then FDISK to change active
> partitions).  Question: IS there a utility available which provides
> partition selection at boot time?  Do I have to re-install everything
> both DOS and BSD to use such a tool?    ...Mark

There is a pretty friendly program called OS-BS that should take care of your
problem.  I'm pretty sure it is on agate in the 386BSD subdirectory somewhere.
You do not have to reinstall the O/Ss to use it.
-- 
Gary Browning        | Exhilaration is that feeling you get just after a
		     | great idea hits you, and just before you realize
                     | what is wrong with it.
Newsgroups: comp.unix.bsd
From: eddy@aludra.usc.edu (George Edmond Eddy)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD's non-standard C library
Date: 29 Sep 1992 12:35:19 -0700
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: aludra.usc.edu

peter@ferranti.com (peter da silva) writes:

[...]
>Anyone with pretentions of writing portable code should be forced to port
>their code to (say) Xenix-286.

>That'll separate the men from the boys.

or perahps masocists, better yet why not insure portability to msdos,
or better still, mswindows :-).

- rusty

--

eddy@usc.edu

Don't worry about me i'm a nobody.
Newsgroups: comp.unix.bsd
From: andrick@sun.rhrk.uni-kl.de (Ulf Andrick [Biologie])
Subject: Mtools to manipulate C: (386BSD)
Organization: University of Kaiserslautern, Germany
X-Newsreader: Tin 1.1 PL4
Date: Tue, 6 Oct 1992 01:57:44 GMT

In order to get mdir to work I recompiled it. After that I was
able to do mdir A: and mdir B: successfully, but mdir C: still
doesn't work, though I set up a partition wd0d via disklabel,
which should correspond to my MS-DOS partition, which is the
first on the disc. My DOS partition table says that the
partition begins with offset 35 (2nd track) and I tried that as offset 
for the wd0d partion as well as 0. But the result is always mdir
complaining that it can't initialise the disc and suspecting it
is a non-MS-DOS disc. Apparently, my recompilation was in so
far successful, as there isn't a message about overlapping
with active partitions anymore. Before, it probably had used wd0c, 
which comprises both of my BSD partitions.

As I don't know C I have difficulties with interpreting the source
code and finding out what Mtools expect how the partition is
formatted. So I would appreciate some help. (I'm also
interested in the German kezboard question posed by someone
else.)

--
Ulf R. Andrick                                andrick@rhrk.uni-kl.de
FB Biologie - Tierphysiologie
Universitaet                             Was du nicht selber weiszt, 
D-W 6750 Kaiserslautern       das muszt du dir erklaeren (Tegtmeier)
Newsgroups: comp.unix.bsd
From: robinson@crash.cts.com (Alan Robinson)
Subject: BEST unix for a 486-d2 system?
Organization: CTS Network Services (crash, ctsnet), El Cajon, CA
Distribution: na
Date: 30 Sep 92 11:18:22 PDT

Newsgroups: comp.unix.questions
Subject: BEST UNIX for a 486-d2; BSD? SOURCES?
Summary: 
Followup-To: masc0037@rohan.sdsu.edu 
Distribution: na
Organization: CTS Network Services (crash, ctsnet), El Cajon, CA
Keywords: SCO, GNU, BSD 

FOR EVERYONE,

	Where do i find 386BSD by BSDI?


	I am looking for reliable BSD Unix for a 486-d2 system.

SCO is popular, and stable; but not BSD.  Is GNU BSD?, is it well

supported?; what other choices are there?  

	What about a communications program under Unix?

What should I make sure I have to have a complete system?

		alan
Newsgroups: comp.unix.bsd
Subject: [386BSD] can FIFO support be made to work?
From: scott@lopez.marquette.MI.US (Scott Reynolds,Insanity)
Date: Tue, 29 Sep 1992 01:55:43 EDT
Organization: Great White North/UPLink

I've added the necessary "options FIFO" to my configuration and done the
config, and I had to modify the .depend file manually to make sure that
the proper fifo.h file was picked up.  This was no real problem, and I
rebooted and made a fifo only to discover that opening the fifo for writing
caused the tty to hang.

A bit of investigation into the problem showed that the problem can happen
when opening the file for reading, also.  I made a couple minor changes to
no avail:  changed the priority parameter in each of the two tsleep() calls
to PSOCK | PCATCH and add a bzero(...) right after the memory allocation
when creating the fifo.

Liberal use of debug printf()'s traced the problem down to the fact that
the call to tsleep() never returns normally.  In fact, it appears to hang
every other process in the same sleep queue!  I have to admit that I am in
over my head here -- all I can say is that any process sleeping when I run
this program will sleep forever if I don't hit the interrupt key, and even
then it wouldn't wake up before I added PCATCH to the tsleep() call.

If anyone knows of the solution to this problem I'd be very grateful to
find out what it is.  If you have a patch, please mail it to the alternate
(BITNET) address below.  Any suggestions would be greatly appreciated even
if you don't know the solution...

Thanks in advance.
--
Scott Reynolds			scott@lopez.marquette.MI.US
Great White North/UPLink	alternate:  A094@NMUMUS.BITNET
	"Insufficient facts always invite danger." -- Spock
Xref: sparky comp.unix.bsd:6643 comp.sys.ibm.pc.rt:510 comp.unix.large:325
From: koblas@mips.com (David Koblas)
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.rt,comp.unix.large
Subject: Re: strdup
Date: 1 Oct 92 00:51:02 GMT
Organization: MIPS Computer Systems, Sunnyvale, California
NNTP-Posting-Host: ecstasy.mti.sgi.com

In article <br.pct.52.717898310@RLG.Stanford.EDU> br.pct@RLG.Stanford.EDU (Peter C. Tam) writes:
>
>	In BSD 4.3 C lib, there is no strdup that is provided in System 5,
>& I just happened to get a program that was supposed to be able to compile
>in BSD also. Can anyone tell me where I can get the strdup routine for
>BSD 4.3, especially, in ibm.pc.rt AOS.


Here's a copy (typed in off the cuff, so I won't say it is guaranteed to work):

	char *strdup(char *str)
	{
		char	*cp = (char *)malloc(strlen(str));
		return cp ? strcpy(cp, str), cp : NULL;
	}

-- 
name : David Koblas                        domain: koblas@mips.com
quote: If you have sex in your car, does that make it a recreational vehicle?
From: prbarick@cc.utah.edu (PATRICK ROBERT BARICKMAN)
Subject: need help in awk
News-Software: VAX/VMS VNEWS 1.4-b1  
Organization: University of Utah Computer Center
Distribution: usa
Date:  6 Oct 1992 21:20 MST  

Newsgroups: comp.unix.bsd
From: kapela@prism.poly.edu (Theodore S. Kapela)
Newsgroups: comp.unix.bsd
Subject: Re: Catch What They're Saying About Us...
Date: 29 Sep 92 13:28:08 GMT
Organization: Polytechnic University, New York

In article <1992Sep25.021813.2369@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
>BSDi is actually benefited, to some degree, by 386BSD.  BSD/386 is stabler,
>better supported, and commercial (and proprietary; one need not follow from

Better supported?  A few techies compared to thousands of readers of this
newsgroup?  And what happens if BSDI goes out of business?

Is *any* package necessarily "superior" becuase it is a "commercial" release?
I'm sure lots of readers of this newsgroup could site examples of just 
the opposite.

>the other); 386BSD is newer, still flaky in some cases, and, as far as I
>know, not a commercial product from anyone.
>
>If I needed an OS to do work, it would probably be BSD/386.  If I were going
>to install an OS on a machine for the express purpose of playing, it would
>be either Linux or 386BSD (probably the latter, at least until networking is
>available and stable in Linux).
>

A quote from "INSTALL.NOTES" of the 386BSD distribution:

     386BSD is intended to foster new research and  develop-
     ment  in operating systems and networking technology by pro-
     viding this base technology in a broadly accessible  manner.
     As  such, like its predecessor, 386BSD Release 0.1 is freely
     redistributable and modifiable.

Nowhere in the distribution is any mention made that 386BSD is a production
system.  In fact, the notes emphasize that the release is targeted for
research/education, not the commercial sector.


-- 
..............................................................................
 Theodore S. Kapela				kapela@poly.edu
 Center for Applied Large-Scale Computing	
 Polytechnic University
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject: ftpd -l (inetd.conf) 
Keywords: inetd ftpd 
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Wed, 30 Sep 92 11:00:49 GMT


I'm running ftpd as an anonymous ftp server on my 386BSD box and although
ftpd -l is enabled in /etc/inetd.conf I never see any FTP log messages
in /var/log/messages. Is this a bug of inetd?

--
--Chris
Christoph P. U. Kukulies
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.
From: spel@hippo.ru.ac.za (Dr. Eberhard W. Lisse)
Newsgroups: comp.unix.bsd
Subject: archive controller supported ?
Date: 28 Sep 92 09:56:01 GMT
Article-I.D.: hippo.1992Sep28.095601.16134
Organization: Katatura State Hospital, Windhoek, Namibia

Hi,

pursuant to my previous posting I learned that my tape won't
work because it has an archive and not a wangtek controller.

I found someone willing to cook me a new tinybsd if I can tell
him how to install the /dev file(s).

Does it support an archive (ft-60) controller? The drive works
very nicely under ms-dos.

regards, el

-- 
Dr. Eberhard W. Lisse    \          /                   (spel@hippo.ru.ac.ZA)
Katatura State Hospital   \        |                            (el@lisse.NA)
Dept of Obstetrics & Gyn   \ *    /                         Private Bag 13215
Windhoek, Namibia           ;____/ (postmaster@uonamib.NA) Postmaster NAmibia
Newsgroups: comp.unix.bsd
From: mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Subject: interesting binaries for 386bsd
Organization: University of Western Ontario
Date: Sat, 26 Sep 1992 18:47:01 GMT

I was wondering if there is a site for uploading/downloading interesting
binaries for 386bsd.

I am sure alot of people are porting stuff both successfully and unsuccessfully.

For example:  I have3 simple programs that I think are great, and I would
upload/ftp to the proper site (to save porting time for others).

xbiff++   I have changed the dirs to work with 386bsd.  The xbiff that came
	  with X386 doesn't seem to detect new mail.  This one does work ok.

xgif      Display up to 256 color gif graphic images on your X11 screen.

xgifroot  Make the gif image your root window background.  Very nice!!
	  I have some nature scenes that look really nice as an X11
	  background.

PS:  I am using the OpenLook window manager and like it alot.
     Has anyone ported any other X apps for bsd?
     An X11 ftptool would be nice!

     I also have xgopher running on this machine.

mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Western Business School  --  London, Ontario
Newsgroups: comp.unix.bsd
From: terry@thisbe.Eng.Sandy.Novell.COM (Terry Lambert)
Subject: Re: FAQ questions: X386.
Organization: Novell NPD -- Sandy, UT
Date: Wed, 30 Sep 1992 21:37:11 GMT

In article <1992Sep30.073852.15094@netcom.com> hasty@netcom.com (Amancio Hasty Jr) writes:
>There is a reason why there are two separate releases of X386.
>From an X11R5 besides the xconsole problem, all the questions/problems
>with X386 have been answered with the release in
>agate.berkeley.edu:/pub/incoming/X386. The /pub/incoming/X386 release
>is waiting for kernel changes. Please, don't ask me for what kernel changes!
>I know that is sounds strange...
>
>For questions such as the now famous "/dev/vga", please read the
>readme file in /pub/incoming/X386. If you are experiencieng problems
>with your mouse behavior such as in microsoft mode, just get
>the release on /pub/incoming/X386. 
>
>We  will prepared a FAQ before the week is  over and I will be
>more than happy to send it to Terry.

You actually ought to just keep it seperate.  It is (I hope!) a natural
division of labor, just like Nate is the guy you bug report to and
Mike is the guy you send lists of working hardware to.

The X FAQ ought to go in the /pub/386BSD/386bsd-0.1/unofficial directory
on agate and get itself mirrored everywhere (just like the unofficial FAQ
and the patches and ported software, etc, etc. is mirrored).


On a side note, the kernel changes required to get the X386 in /pub/incoming
running are in that directory, as is a patched kerenl (which mostly works).
These patches are included in the patch kit as well, which is still on
scedule and should be released at the end of 01 Oct 92 (tomorrow night).
X386 from the /pub/incoming directory works fine for me on a kernel built
from a virgin kernel with the patch kit applied.

If there are new "magic" patches, I would like to include them or any changes
to the patches in /pub/incoming/X386, but time is running out.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com

---
Disclaimer:  Any opinions in this posting are my own and not those of
my present or previous employers.
From: brian@ucsd.edu (Brian Kantor)
Newsgroups: comp.unix.bsd
Subject: Re: Catch What They're Saying About Us...
Date: 29 Sep 92 16:43:24 GMT
Article-I.D.: network.1aa13cINNeag
Organization: The Avant-Garde of the Now, Ltd.
NNTP-Posting-Host: ucsd.edu

In article <16291@ksr.com> dean@ksr.com (Dean Anderson) writes:
>That being said, it would appear to me that there are a lot of 
>egotistical, perhaps megalomanical people who cannot take criticism 
>or any sort.

It is precisely this kind of person who does great things.

The artistic temperment goes with the artistic territory.
	- Brian
Newsgroups: comp.unix.bsd
From: robinson@crash.cts.com (Alan Robinson)
Subject: BEST UNIX for a 486-d2 system?
Organization: CTS Network Services (crash, ctsnet), El Cajon, CA
Distribution: na
Date: 30 Sep 92 11:26:36 PDT


FOR EVERYONE,

	Where do i find 386BSD by BSDI?


	I am looking for reliable BSD Unix for a 486-d2 system.

SCO is popular, and stable; but not BSD.  Is GNU BSD?, is it well

supported?; what other choices are there?  

	What about a communications program under Unix?

What should I make sure I have to have a complete system?

		alan

Newsgroups: comp.unix.bsd
From: colin@cs.curtin.edu.au (Colin Manning)
Subject: DDJ June+July '92
Organization: Curtin University of Technology
Date: Mon, 5 Oct 1992 09:46:52 GMT

Hi,
	Has anyone in Western Australia (or for that matter Australia) seen
June or July's copy of DDJ?  Our library has August and Sept, and up to May,
but no June or July.  Neither have been in the newsagents either as far as I
know.  Is there any 386BSD stuff in them?

Colin.

-- 
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Corruption in BIN01.56?
Organization: Weber State University  (Ogden, UT)
Date: Thu, 1 Oct 92 15:55:15 GMT

In article <adam.717861382@marsh> adam@cs.curtin.edu.au (Adam Sawyer) writes:
>
>Has anyone else had problems when trying to extract the BIN01.(1-56) 
>distribution?
>
>When I go to extract the files (after mread b:*.* /tmp) for all 56 BIN01.X
>files, I am always getting the error :
>
>Corruption in BIN01.56
>
>And I've already b) recopied the file onto a new disk
>                 c) re-ftped the file from kirk.bu.oz.au
>                 d) (re-ftped ensuring that I was in BINARY mode)
>                 d) re-ftped from agate.berkeley.edu
>
>
>And now I'm lost for ideas, its only this one last file *sigh*

This problem is popping up too much.  It seems that the MANIFEST file has
been corrupted.  This is the file which "install" users to check for
corruption.  Since you are the fourth person to report a "corrupted"
bin01.56, I suspect that the site you got the "MANIFEST" file from has a
corrupted copy.  Please notify them so that they can take corrective action.

NB: There is a rare chance that, in your case, you are rewriting the same
bad sectors with the file.  This would be the case if you are running a drive
without bad sector forwarding and didn't "mv bin01.56 bad.file.1" before
downloading.  Otherwise, the same file is likely to get the same sectors.

In any case, there is at least one corrupt "MANIFEST" file out there, in m
opinion, and archive administrators should check for it.  Since a lot of
us *know* the agate distribution works,  I would suggest checking against
that one.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd