HDTenEightyP/NetNews huggingface dataset:
From: peter@taronga.com (Peter da Silva)
Newsgroups: comp.unix.bsd
Subject: Re: selling 386BSD (was Re: 386BSD on CD-ROM?)
Date: 23 Aug 92 13:06:44 GMT
Organization: Taronga Park BBS

In article <1992Aug23.060308.6392@nuchat.sccsi.com> kevin@nuchat.sccsi.com (Kevin Brown) writes:
>Say that a copyright, regardless of who owns it, states that what is being
>copyrighted (a) is freely redistributable (i.e., anyone can give it to
>anyone else), (b) can be put to whatever legal use someone wants to put
>it to [...] (c) any modified version *must* be distributed with source as
>part of the distribution, but other than being included with the
>normal distribution, can be distributed with any copyright provisions.

I'm not sure how this differs from the Copyleft. Could you provide an
example?
-- 
                                                                `-_-'
                         Have you hugged your wolf today?        'U`

Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032
From: rgp@mpd.tandem.com (Ramon Pantin)
Newsgroups: comp.unix.bsd
Subject: Re: ulimit()
Date: 20 Aug 92 05:25:00 GMT
Organization: Tandem Computers, Micro-Products Division

In article <10955@platypus.uofs.uofs.edu> bill@platypus.uofs.edu writes:
>In article <1992Aug13.091855.28615@rz.uni-karlsruhe.de>, walter@insu1.etec.uni-karlsruhe.de (Reiner Walter) writes:
>|> I want to port the system call ulimit() from INTERACTIVE to BSD/386.
>
>Why???
>Most people stuck on SYSV spend most of their waking hours trying to 
>find a way to do away with it.  What possible use could you have for 
>something as limiting (or dare I say brain-dead) as ulimit??
>
>bill

I agree, brain damaged.  Just as brain damaged as BSD's setrlimit(2),
readv(2), writev(2), job control, and all the other useless stuff.
Just as brain damaged as the sig*(2), priocntl(2) and all the other
madness in SVR4 or all the efforts of standardizing the heck out of
unimplemented stuff in POSIX, ANSI-C++, X/Open, OSI, ...
Not to mention editors and window managers that require megabytes
just to be able to crawl (they never seem to "run").

It would seem that nobody learned anything from UNIX (except for
the Plan 9 folks, of course).
Where did the thrive for simplicity, coherency and minimalism go ?

Ramon Pantin
From: guy@Auspex.COM (Guy Harris)
Newsgroups: comp.unix.bsd
Subject: Re: (386BSD) Modems and com ports
Keywords: internal or external?
Date: 22 Aug 92 06:39:53 GMT
Organization: Auspex Systems, Santa Clara

>2)	A UNIX write, once started, must run to completion before it may be
>	XOFed.

In what sense?

If the serial port device doesn't have DMA, and the main CPU hands it
each character to be transmitted, one at a time, the driver can, if it
receives a ^S, just stop handing the device characters until it gets a
^Q.

If the serial port device *does* have DMA, then, if a DMA operation can
be halt and restarted later, or can be aborted and restarted from
where it left off, the driver can, if it receives a ^S, just halt or
abort the transmission, and restart it when it gets a ^Q.

Take a look at the VAX BSD DZ11 driver for an example of the former, and
the VAX BSD DH11 driver for an example of the latter, if you have access
to the source to those drivers.  Other drivers that do the same can
probably be found if you don't....

>The problem shared by any flow control whatsoever is lockup on line drop.
>If the computer is ^s'ed, or !RTS or !CTS'ed, then the driver will wait
>for the condition to be cleared.  In most cases, this takes precedence
>over a little thing like DCD dropping because of call waiting or a bad
>connection.

If so, the driver is probably buggy.  It *should* manage - at least by
default - to flush pending output, and wake up anybody waiting for the
output queue to drain, if carrier drops.

Some tty subsystems are buggy in that fashion, but it is a bug....
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Sun, 16 Aug 1992 16:40:03 GMT

In article <CGD.92Aug14204505@agate.berkeley.edu>,
  cgd@agate.berkeley.edu (Chris G. Demetriou) writes:
> As a matter of fact, I had just reconsidered, and was about to take
> the copyright notice *OFF* the file, and lo, and behold, i got hit by N
> flames.

Not that I advocate this, but, of course, anyone could ``reverse engineer''
anything Chris does, and eliminate the copyright aspect.  I rather
doubt he has the resources to start a bunch of copyright infringement
actions, and besides, it would be humorous to listen to his councel
argue that he is entitled to intellectual property rights that that
USL isn't.

The sword cuts both ways...

-- 
---
 Robert Withrow, R.W. Withrow Associates, Swampscott MA 01907 USA
 Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
From: grog@adagio.UUCP (Greg Lehey)
Newsgroups: comp.unix.bsd
Subject: Re: "UNIX" is not the registered trademark of AT&T in Japan.
Date: 12 Aug 92 13:27:38 GMT
Organization: LEMIS, Schellnhausen 2, W-6324 Feldatal, Germany

In article <2759@tansei1.tansei.cc.u-tokyo.ac.jp> mhiroshi@tansei.cc.u-tokyo.ac.jp (H. Murakami) writes:
>A little fact that you might be interested in.
>
>In Japan, the word "UNIX" is not the registered trademark of USL nor AT&T,

I don't know the details in Germany, but next time you want to rent a
car in Germany, you might find it amusing to rent it from a company
called UNIX-Rent-Autovermietung-Beteiligungsgesellschaft mbH in
Frankfurt am Main (telephone +49-69-619054). No, I don't have any
connection with the company - I just found the name amusing.
-- 
Greg Lehey                       | Tel: +49-6637-1488              
LEMIS                            | Fax: +49-6637-1489
Schellnhausen 2, W-6324 Feldatal, Germany
*** NOTE ***: Headers are mangled - reply to grog%lemis@Germany.EU.net
Newsgroups: comp.unix.bsd
From: cl45@cunixf.cc.columbia.edu (Ching-Tse Liu)
Subject: Help on floppy drive access in 386bsd
Reply-To: cl45@cunixf.cc.columbia.edu (Ching-Tse Liu)
Organization: Columbia University
Date: Thu, 20 Aug 1992 16:18:01 GMT

Hi,
   I have installed 386bsd on my hard drive. When I tried to do
   mount /dev/fd0a /mnt, an error message would come out --

   "fd0: hard error (ST0 44 ST1 2 ST2 0 ST3 1C cyl 1 hd 7 sec 2) ."

   However, I could still do 'ls /mnt ' etc, but the error messages
   kept coming up. I didn't have any problem during the installation.
   When it boots, the following (reguarding to floppy) appears on the
   screen --

   "fd0 drives 0: 1.44M, 1: 1.2 M at 0x3f0 irq 6 drq 2 on isa ."

   Another question is: How do I read MS-DOS partitions and MS-DOS
   floppy disks. I don't know how to use those mtools.

   Thanks for any help.

       		                     	***********************
--cliu@merlin.appmath.columbia.edu	*   CLifton T. Liu    *
--cl45@cunixf.cc.columbia.edu		***********************

Newsgroups: comp.unix.bsd
From: volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt )
Subject: Re: Motif on X386???
Organization: Applied Math, University of Bonn, Germany
Date: Tue, 18 Aug 1992 10:45:11 GMT

In article <1992Aug17.223909.14604@athena.mit.edu> bri@pegasus.mit.edu (Brian D. Carlstrom) writes:
>What is the deal with site licenses and motif. i know mit has a bin/lib/src 
>license to cover everyone on campus. does this mean you can give it to me?
[...]
>what's the legal bit on this...

I would also be interested in an answer to this question.  Our university
computer center will not ever get a Motif license.  [They can't even get a
BSD license even though they *have* an AT&T license -- bah!]

Is there any chance of a binary distribution?  I wouldn't mind paying a
reasonable amount for Motif binaries, but the licensing fees that were
recently mentioned in comp.windows.x.motif were outrageous.

Thanks -- Volker
-- 
----------------------------------------------------------------------------
Bitnet:   UNM409@DBNRHRZ1                              Volker A. Brandt
UUCP:     ...!unido!DBNRHRZ1.bitnet!unm409             Angewandte Mathematik
Internet: volker@sfb256.iam.uni-bonn.de                (Bonn, Germany)
From: geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.unix.bsd
Subject: Re: PC-NFS
Date: 16 Aug 92 03:19:17 GMT
Organization: SunSelect
NNTP-Posting-Host: tyger.east.sun.com

Quoth Andrew.Michael@brunel.ac.uk (Andrew J Michael) (in <BsxvE7.84B@brunel.ac.uk>):
#
#I saw a question here recently concerning PC-NFS under 386BSD - I'm sorry,
#but I can't remember who posted it.
#
#I have the latest version of PC-NFS running.  This is the version supplied
#in source on the PC-NFS 4.0 floppies.  All is well except for a mount point
#bug.  This looks like a problem with mountd and long filenames - has anyone
#else come across such a thing.

Everything seemed to work under BSDI's BSD/386. I'll try 386BSD
next week.

#N.B. I think that the PC-NFS source is freely distributable, so it could
#possibly become a standard part of 386BSD.  Dell supply it with their SVR4,
#for example.  

WHOAH!!! Just a doggone minute..... I assume you're referring to the
source for the pcnfsd support daemon. I can assure you that the source
to PC-NFS 4.0 itself is *not* freely redistributable.  (Pauses while
heart palpitations fade away....) I've ported pcnfsd to BSD/386, and
copies are on the principal PC-NFS support archives (src.doc.ic.ac.uk
in the UK, bcm.tmc.edu in the US, and ftpserver.massey.ac.nz in the
Antipodes...) If people want to fold the sources to pcnfsd into
386BSD, BSD/386, Linux, whatever, that's just fine with me.

Geoff
--
Geoff Arnold, PC-NFS architect | In the years after WW2 it was said that Oxford
  (geoff.arnold@East.Sun.COM)  | philosophers had found a cure for atheism.
         SunSelect,            | Young people coming up as atheists soon found
  a Sun Microsystems Business  | that they no longer knew what to disbelieve...
Newsgroups: comp.unix.bsd
From: tih@barsoom.nhh.no (Tom Ivar Helbekkmo)
Subject: Re: 2nd drive file ... (Actually wd ESDI problems)
Organization: Norwegian School of Economics
Date: Thu, 13 Aug 1992 05:33:54 GMT

mjj@mlb.dmt.csiro.au (Murray Jensen) writes:

>The area bad144 uses is at the end of *partition C*. It is supposed to use
>only the last track + 126 sectors, but since you usually want filesystems
>to be whole numbers of cylinders you might as well leave the whole last
>cylinder free. The distributed disktab says you should leave 5 cylinders
>for bad sector stuff, but after looking at this a bit I decided it was
>wrong - can someone who knows for sure please comment?

You've got it right -- the last track plus the last 126 sectors before
that last track.  In practice, you just leave out the minimal number
of whole cylinders that will leave you with at least that many sectors
unused.

>My guess is that the BSD filesystem sector clustering code, which groups
>sectors together to form larger "logical blocks" (I was using 4096 byte
>logical blocks i.e. 8 sectors, in my filesystems - other people use 8192)
>is somehow avoiding the bad144 bad sector forwarding mechanism when it
>does the multiple sector read (or write).

Right again -- the bad sector handling code doesn't handle bad sectors
in any but the first of a multiple-sector I/O operation.  I'm already
working on the wd driver to make it correctly handle up to four disks
on two controllers (well, really any number, but that's the practical
limit on a PC), and I will be fixing the bad sector handling too while
I'm at it.  I just need to find and fix one timing and/or reentrancy
problem that shows up when wdopen() calls readdisklabel().

For those who have reported lockups and other errors when trying to
enable badsect on the second drive, while it works fine on the first,
one thing to try is to make sure the disks are not fsck'ed at the
same time from /etc/rc.  That is, change the call to fsck in there
from "fsck -p" to "fsck -p -l 1" (I *think* it was "-l", anyway, you
want the option that limits the number of simultaneous checks.  For
some controllers, this will work around the timing/reentrancy bug in
the driver.  Meanwhile, I'm still working on it...

-tih
--
Tom Ivar Helbekkmo, NHH, Bergen, Norway.  Telephone: +47-5-959205
Postmaster for domain nhh.no.   Internet mail: tih@barsoom.nhh.no
From: roth@ordin.cs.wisc.edu (Bill Roth)
Newsgroups: comp.unix.bsd
Subject: measuring memory usage
Date: 17 Aug 92 20:32:06 GMT
Organization: U of Wisconsin Madison - Computer Sciences

Hi.

Is there any simple way to measure the memory a process uses from
within the process at certain benchmark points? I do not want to set
up counters at every malloc. I merely want to see the change in memory
usage after some operation has occurred.

Please email your replies.
--

-------------------------------------------------------------------
Bill Roth, University of Wisconsin Computer Sciences Dept.
Internet: roth@cs.wisc.edu. BITNET: ROTH@WISCPSL. HEPNET: PSL::ROTH
Newsgroups: comp.unix.bsd
From: dawes@physics.su.OZ.AU (David Dawes)
Subject: Re: init, rc, signal handling (386BSD)
Organization: School of Physics, University of Sydney, Australia
Date: Thu, 13 Aug 1992 11:57:50 GMT

In article <1992Aug13.103235.25465@ucc.su.OZ.AU> dawes@physics.su.OZ.AU (David Dawes) writes:
>
>I've noticed that signal handling gets screwed up for commands run from
>/etc/rc.  One particular example is xdm.  When started from /etc/rc
>the signal handlers it installs don't work -- the signals get ignored.
>I checked the init source, and it resets the signal handling the SIG_DFL.
>
>I tried a simple program which checks this, and the default handler's are
>correctly set -- but signals are being ignored regardless of the default
>behaviour or if a handler is installed.
>
>This is making it impossible to shutdown xdm cleanly when it is started
>at boot time from /etc/rc.

I've just found the following workaround.  Run the command using

csh -c "command args"

Using sh instead of csh doesn't work.

David
--
------------------------------------------------------------------------------
 David Dawes (dawes@physics.su.oz.au)    DoD#210      | Phone: +61 2 692 2639
 School of Physics, University of Sydney, Australia   | Fax:   +61 2 660 2903
------------------------------------------------------------------------------
From: kew@timesink.spk.wa.us (Keith Walker)
Newsgroups: comp.unix.bsd
Subject: Problems with select() and serial ports
Date: 18 Aug 92 03:40:54 GMT
Organization: None that I'm aware of.


I recently got 386bsd 0.1 going on my machine and not too long after that
installed Chris Demetriou's serial driver, which really works good in spite
of the much maligned copyright :-)

But, the select() call doesn't seem to work right when calling the serial
ports.  The behaviour is easy to replicate; just press ESC when in vi.  The
escape will not be recognized until another character is received.  So, it
seems the timeout isn't working right when there's only one character to be
read.

Hmmm.

I am not a kernel guru, nor do I play one on the net.  I'm hoping someone
else out there (maybe cgd?) will have some idea of what the problem is or
maybe even have a fix.

Thanks again to Bill, Lynne *and* Chris.  Without cgd's serial driver, the
com ports are essentially unusable.

-- 
kew@timesink.spk.wa.us | Ah, the early space program: 
Keith Walker  	       | The moon, the planets, the stars!
                       | We were going to do *everything*!
(509) 466-9384         | Now, it's everything we can do. :-(
Newsgroups: comp.unix.bsd
From: peter@taronga.com (Peter da Silva)
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Organization: Taronga Park BBS
Date: Fri, 21 Aug 1992 12:05:46 GMT

In article <BtAA9F.5vw@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes:
>	novell 3.11 server.  All the dos machines have netware drivers, tcp/ip
>	drivers, cd-rom drivers, doskey, smartdrv, mouse, etc, etc.
>	All have over 600k free after this, and *never* crash unless the wife
>	says "what will *this* do??".

Well, they shouldn't crash then either.

>	DOS is not a real OS, true, but until someone ports Wing Commander
>	to BSD, I can't much do without it.

If you wanted a PC with a real-time OS you should have bought an Amiga.
-- 
                                                                `-_-'
                         Have you hugged your wolf today?        'U`

Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032
Newsgroups: comp.unix.bsd
From: peter@taronga.com (Peter da Silva)
Subject: Re: Restrictions on free UNIX / 386BSD (Re: selling 386BSD)
Organization: Taronga Park BBS
Date: Tue, 18 Aug 1992 13:09:22 GMT

In article <PHR.92Aug17195332@soda.berkeley.edu> phr@soda.berkeley.edu (Paul Rubin) writes:
>The FSF has stated in numerous publications that GCC *output* is
>not covered by the GPL.  I don't remember whether the GPL itself
>states this specifically; maybe it should.

The FSF is not the entity they're worried about. It's J Random pirate
who uses this argument as a defense.

>Note that some routines in the FSF-distributed C library are
>copylefted and can't be shipped linked into a binary-only product
>except in some conditions.

Hey, I thought they'd changed the library-GPL to avoid this! What's
the story here?
-- 
                                                                `-_-'
                         Have you hugged your wolf today?        'U`

Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032
Newsgroups: comp.unix.bsd
From: explorer@iastate.edu (Michael Graff)
Subject: Re: SUMMARY of answers to: "how to label partition to 386BSD?"
Organization: Iowa State University, Ames IA
Distribution: usa
Date: Fri, 14 Aug 1992 16:41:07 GMT

In <1992Aug14.150220.1560@rwwa.COM> witr@rwwa.COM (Robert Withrow) writes:

>WRT the standard single hard drive configuration:

>I don't understand why people what to go to all that *unnecessary* effort:
>just do what the instructions tell you to do!!!

[ wish-type instructions deleted ]

>That's it!!!  DON'T CREATE OTHER PARTITIONS using fdisk, DON'T RUN
>DISK EDITORS, or anything.  The install procedure will notice that
>you have free space on your disk that is not assigned to any partition, 
>and will do the right thing.

Funny...  It sure as hell didn't on my systems...  None of the 4 I've
tried to install went quite that well.  ;)

There's a lot of hardware differences out there, and assuming that it
worked for you so it'll work that way for everyone is unrealistic.
-- 
--
Michael Graff    Iowa State University Computation Center      Project Vincent
215 Durham                voice: (515) 294-4994           explorer@iastate.edu
Ames, IA  50010           fax:   (515) 294-1717           gg.mlg@isumvs.bitnet
From: Andrew.Michael@brunel.ac.uk (Andrew J Michael)
Newsgroups: comp.unix.bsd
Subject: PC-NFS
Date: 13 Aug 92 20:25:17 GMT
Organization: Brunel University, Uxbridge, UK


I saw a question here recently concerning PC-NFS under 386BSD - I'm sorry,
but I can't remember who posted it.

I have the latest version of PC-NFS running.  This is the version supplied
in source on the PC-NFS 4.0 floppies.  All is well except for a mount point
bug.  This looks like a problem with mountd and long filenames - has anyone
else come across such a thing.

N.B. I think that the PC-NFS source is freely distributable, so it could
possibly become a standard part of 386BSD.  Dell supply it with their SVR4,
for example.  


Andy Michael

-- 
Andy Michael                                     "You might think that.  I
85 Hawthorne Crescent                             couldn't possibly comment."
West Drayton					    - `House of Cards'
Middlesex            email: eesrajm@brunel.ac.uk                             
UB7 9PA           or Andrew.Michael@brunel.ac.uk
Newsgroups: comp.unix.bsd,comp.protocols.nfs
From: schneck@Physik.TU-Muenchen.DE (Bernhard Schneck)
Subject: Re: 386BSD: 16550's vs. NFS
Organization: Leibniz-Rechenzentrum, Muenchen (Germany)
Date: Wed, 12 Aug 1992 20:25:59 GMT

>> Try increasing the timeout value for nfs mounts.  Something like
>> 
>> 	mount -t nfs -o timeo=T ... remote-dir mount-point
>> 
>> where # is timeout value in 0.1 sec intervals.

>It can alos help to reduce the block sizes.
>And radically bloat the attribute cache expirations.

... and use ppp or nfs over TCP or turn on UDP checksums ... you might 
loose big with NFS otherwise, even with MNP4/V.42!

\Bernhard.
--
Bernhard Schneck        Internet: Bernhard.Schneck@Physik.TU-Muenchen.DE
TU Muenchen Physik
8046 Garching           "There is no problem so big that it cannot be
Germany                 run away from"                  Illusions, Richard Bach
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: Restrictions on free UNIX / 386BSD (Re:
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Wed, 19 Aug 1992 01:18:31 GMT

In article 32@rmkhome.UUCP, rmk@rmkhome.UUCP (Rick Kelly) writes:
>Software houses such as Lotus and Wordperfect want complete assurance that
>their product is secure under the law when it goes out the door.  There is
>no court record to show what happens when the buyer of a commercial software
>product demands source from the author because it was compiled using GCC,
>and should fall under the GNU Copyleft.  

Compiling a program with GNU C does not automatically place it under the
GNU General Public License.  It might help cut down on the bandwidth here
if people actually read the GPL before posting.

	Chris Flatters
	cflatter@nrao.edu
Newsgroups: comp.unix.bsd
From: cyber@ecst.csuchico.edu (Erik Berls)
Subject: Re: Does 386BSD work with other SCSI controllers?? specifically a DTC 3280?
Summary: dtc 3280 working with 386BSD
Organization: California State University, Chico
Date: Wed, 19 Aug 1992 00:43:38 GMT

In article <1992Aug18.151434.18370@elroy.jpl.nasa.gov> Minh Lang <minh@inst-sun1.jpl.nasa.gov> writes:
[parts deleted to save bandwidth]
>Is there a 
>patch so that I can install 386bsd on my scsi drive. It's
>a Quantum 210S,
>  == Minh ==

Im kinda of in the same boat, does anyone know if it will work with a
DTC 3280 SCSI controller?
thanks,
-=erik.
From: osynw@warp.mhd.montana.edu (Nate Williams)
Newsgroups: comp.unix.bsd
Subject: Unofficial Bug Report, #2 0/1
Summary: info on list
Keywords: 386BSD bugs
Date: 13 Aug 92 05:07:54 GMT
Organization: We don't need no Steeenkin organization.


Following this article is the second release of the 386BSD bug
report.  Since there have been some formatting additions to the list
(addition of bug report tracking numbers) I will not make a diff
from the first version to the last version.  However, when the
format stabilizes, I will post the Bug Report and a diff file
from the previous version, so you can see what has changed.

Comments, suggestion, bug reports, bug fixes, etc can be sent
to:

osynw@terra.oscs.montana.edu

Please use a subject line of - 386BSD BUGS when sending in reports,
as it makes my lif easier.  Also, if you can make the report in the
same format as the individual entries in the list, it would also make
it easier for me.


Thanks everyone who has sent in bug reports and bug fixes,


Nate

ps. I will be leaving for a week to get away from electronic devices, so
if you send me email, I may not respond to it until next week.  No, I'm
really not ignoring you, but I haven't logged on. :-)

-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home.  Anyone  interested
work: (406) 994-5991         |  in a used Sys. Admin., with alot of 
home: (406) 586-0579         |  good hacks left?
Newsgroups: comp.unix.bsd