HDTenEightyP/NetNews huggingface dataset:
From: jds@cs.umd.edu (James da Silva)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD & SCSI - Multiple file tapes
Date: 24 Jul 92 18:01:22 GMT
Organization: University of Maryland, Department of Computer Science

toreh@bootes.sds.no (Tore Haraldsen) writes:
>It IS possible to read multiple file tapes, if you do the following
>modifications to i386/isa/as.c:
>
>1) Change the definition of dev_rewind macro to use a mask outside the
>   other fields used by the scsi driver. Using the partition field for
>   no-rewind flags will not work, due to imprecise coding elsewhere in
>   the driver. Use 0100 for instance. Make a new kernel.

I didn't find this to be necessary.  I just commented out a test in
asopen() in as.c as follows:

*** /tmp/,RCSt1000161	Sat Jul 25 18:24:22 1992
--- as.c	Sat Jul 25 18:23:48 1992
***************
*** 429,438 ****
--- 429,440 ----
  		}
  	}
  	
+ /*
  	if (as->tape &&  dev_part(dev)) {
  		error = EIO;
  		goto done;
  	}
+ */
  
  	as->scsi_cdb_len = 10;
  	bzero(cdb, 10);


>2) Create a device with this capability:
>		mknod /dev/nras2a c 13 80

I did have to mknod a device with the partition field set to 1 as mentioned
in the instructions at the top of as.c.  For a tape at target 2:

	ln /dev/ras2a /dev/rst2		# rewind device
	mknod /dev/nrst2 c 13 17	# no-rewind device

Jaime
............................................................................
: Stand on my shoulders, : jds@cs.umd.edu  :		      James da Silva
: not on my toes.	 : uunet!mimsy!jds : Systems Design & Analysis Group
From: donaldh@cs.hw.ac.uk (Donald I. Hunter)
Newsgroups: comp.unix.bsd
Subject: Space required for bin01
Keywords: 386BSD bin01 bindist
Date: 24 Jul 92 09:28:02 GMT
Organization: Dept of Computer Science, Heriot-Watt University, Scotland

I'm trying to install the 386BSD bin01 distribution set.

How much disk space is required to extract bin01?  Am I right in thinking that 40Mb is enough for the kernel and the bin01 but more is required to actually execute the extraction?

If so, how much space  do I need? Or is there another way to extract - bit by bit for example?

Cheers, Donald.

-- 

 +--------------------------------------------------------+
 | Donald I. Hunter                   donaldh@uk.ac.hw.cs |
 +--------------------------------------------------------+
 | Hello. Just walk along and try NOT to think about your |
 |    INTESTINES being almost FORTY YARDS LONG!!          |
 +--------------------------------------------------------+
From: raeburn@cambridge.cygnus.com (Ken Raeburn)
Newsgroups: comp.unix.bsd
Subject: 386bsd nfs hang problem -- some data, temporary workaround
Date: 21 Jul 92 22:15:59 GMT
Organization: Cygnus Support, Cambridge MA

I reported previously that I was seeing problems reading files over
NFS using the ne2000 driver; timeouts would eventually be reported, no
data would be read.  Listing files and directories (small ones
anyways) were not a problem.

After playing with etherfind and kernel printfs, I've come to this
conclusion: Fragmented 8K UDP packets from the NFS server are not
reaching the UDP layer in 386bsd.  The Sun is sending them (according
to another Sun spying on the network), but the UDP input routine is
never called.  I don't know if the bug here is on the 386bsd or Sun
side, and won't have time to look into it in the next couple of days.

In the meantime, mounting NFS file systems with "rsize=1024" does get
rid of this problem.

(It does nothing about TCP being slow, though.)

Ken
From: osynw@warp.mhd.montana.edu (Nate Williams)
Newsgroups: comp.unix.bsd
Subject: Re: Beginner's problems with 386BSD
Date: 28 Jul 92 04:28:36 GMT
Organization: /usr/local/lib/MYORG

In article <1992Jul27.123733.4507@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes:
>In article <1992Jul27.011712.27704@coe.montana.edu> osynw@warp.mhd.montana.edu (Nate Williams) writes:
>>>>I wish someone could tell me how to get my clock correct too.  I have tried
>>Yep, I have tried everything I could think of.  I removed /usr/share/zoneinfo
>>and remade everything from scratch.  My machine is still one hour faster
>>than my real time clock.  
>
>	I gave up, too.  So, I just changed the CMOS time so 386bsd
>	came out right. Worked great.
>

After changing my CMOS time, I decided to look at the zoneinfo stuff. 
Since my wife still used DOS, I didn't really want to leave it with the
clock incorrect.
 (She hasn't seen much of the machine since 386BSD got released :-)

I ended up copying the northamerica datafile and making a new RULE
called NATE that didn't have the Daylight savings time in it.  

My machine NOW has the correct time and offset.  I guess my BIOS is too
smart for 386BSD.  The only problem with this is I'm not sure how the
BIOS handles the time-change.  I may have to reboot, but that's a few months
away.


Nate
-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home.  Anyone  interested
work: (406) 994-5991         |  in a used Sys. Admin., which alot of 
home: (406) 586-0579         |  good hacks left?
Newsgroups: comp.unix.bsd
From: mbs@fungus.zso.dec.com (Michael Schmitz)
Subject: Adaptec SCSI bug?
Organization: Digital Equipment Corporation - DECwest Engineering
Date: Thu, 30 Jul 1992 21:00:37 GMT

In trying to figure out why my 386BSD 0.1 sometimes hangs during
heavy disk I/O, I noticed the following in the adaptec driver:

In i386/isa/as.c NSCATTER is set to 17, but the adaptec documentation
gives the maximum size for a scatter/gather array as 16.  Scatter/gather 
is always used, so that the data area pointed to by b_addr (in a struct
buf) may be backed by physically contiguous pages or not.  

Question:  Can the physical pages backing a struct buf ever be not
physically contiguous?  If contiguous, then scatter/gather is not
needed at all.

Question:  Are struct bufs (data area) limited to 8K?  In this case
(allowing for rounding) the loop that collects the scatter/gather
info would only execute at most three times anyway.

By the way, I'm using 32 Megs for swap, so it can be a swap resource
problem.

					--Michael--
					mbs@zso.dec.com	




Newsgroups: comp.unix.bsd
From: meissner@osf.org (Michael Meissner)
Subject: Re: AT&T sues BSDI
Organization: Open Software Foundation
	<1992Jul25.061414.3401@spcvxb.spc.edu>
Date: 28 Jul 92 14:14:02

In article <1992Jul25.061414.3401@spcvxb.spc.edu> terry@spcvxb.spc.edu
(Terry Kennedy, Operations Mgr.) writes:

|   If AT&T/USL wins this case, this means that any vendor can claim that they
| have rights of "intellectual ancestry" or some such balderdash over any pack-
| age found on the net. What would you think if they claimed that AT&T/USL had
| "rights" to GCC because the specification of C was originally developed by
| them?

In this specific case, AT&T cannot do this, because they specifically
gave up any rights to the "C" language as part of the ANSI (and now
ISO) standardization.  ANSI would not have allowed a standard
controlled in this fashion.  I believe that AT&T did do the same thing
for the interfaces that have become POSIX interfaces.
--
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.
Newsgroups: comp.unix.bsd
From: Brian.Chan@bbs.oit.unc.edu (Brian Chan)
Subject: X11 r5 binaries
Followup-To: bchan@ddn-eur.ddn.mil
Organization: Extended Bulletin Board Service
Date: Mon, 27 Jul 1992 11:28:00 GMT


Hello. I brought up 0.1 w/o any problem. Thx again to Bill, Lynn and
others. It was many times easier than installing my Esix. Kudos to Lynn!

I asked this question about a month ago. I received many inquiries but
no answer. Can someone please upload the binaries for X? Also if you
got virtual console working, can you upload your kernel too?

Thx a million,

Brian
Stuttgart, FRG
--
   The opinions expressed are not necessarily those of the University of
     North Carolina at Chapel Hill, the Campus Office for Information
        Technology, or the Experimental Bulletin Board Service.
           internet:  bbs.oit.unc.edu or 152.2.22.80
From: lidl@uunet.uu.net (Kurt J. Lidl)
Newsgroups: comp.unix.bsd
Subject: WD8013EPT performance and MFS
Date: 22 Jul 1992 01:16:43 -0400
Organization: AlterNet -- Falls Church, Virginia, USA
Distribution: world
NNTP-Posting-Host: rodan.uu.net

In light of the other performance problems that people have
been noting, I will give this ray of sunshine.  On my
386/33, with a WD8013EPT ethernet card, I get pretty good
transfers:

ftp> get xtank.sun4
200 PORT command successful.
150 Binary data connection for xtank.sun4 (192.111.45.22,1076) (2719744 bytes).
226 Binary Transfer complete.
2719744 bytes received in 13 seconds (2e+02 Kbytes/s)
ftp> get xtank.sun4
200 PORT command successful.
150 Binary data connection for xtank.sun4 (192.111.45.22,1077) (2719744 bytes).
226 Binary Transfer complete.
2719744 bytes received in 13 seconds (2.1e+02 Kbytes/s)

Obviously, 200 or 210 Kbytes/sec is not too bad!

This was, of course, going to an mfs /tmp directory.

Writing to a IDE disk drive (105megs), I got about 180 Kbytes/sec
throughput, on the same (unloaded) ethernet.

Since I haven't seen anyone else mention this tidbit, I will.
To get mfs working, you should "ln /sbin/newfs /sbin/mfs" and
add an "options MFS" to your favorite kernel config and re-compile
and install that kernel.

Then, in your /etc/rc file, add something like this:

mfs /dev/wd0b /tmp

This will help you out if you have a reasonable amount of ram
(ie, when I was running with 4 megs, it didn't seem to help much.
It definately helps out at 8 megs.  I'll let you know how it goes
at more than 8 megs when I find out.)

-Kurt
-- 
/* Kurt J. Lidl (lidl@uunet.uu.net)   | Unix is the answer, but only if you */
/*                                    | phrase the question very carefully. */
/* Don't even think of confusing my opinions with my employer's opinions!   */
From: sxjcb@orca.alaska.edu (Jay C. Beavers)
Newsgroups: comp.unix.bsd
Subject: SL/IP under 386 BSD 0.1
Date: 24 Jul 92 21:29:17 GMT
Followup-To: comp.unix.bsd
Organization: University of Alaska Computer Network

I would like to set up a SL/IP server or a PPP server on my machine and I
just
can't seem to find the information on how to do this.  If I have an
ethernet
adaptor configured on ec0 and a 9600 baud modem on /dev/com2, what do I
need to do to get /dev/com2 to answer and provide SL/IP service?

______________________________________________________________________________
                                        |
Jay C. Beavers                          |    sxjcb@orca.alaska.edu
University of Alaska Computer Network   |    sxjcb@alaska.bitnet
________________________________________|_____________________________________
Xref: sparky comp.unix.bsd:2795 comp.sys.laptops:2894
From: paigen@tfs.com (David Paigen)
Newsgroups: comp.unix.bsd,comp.sys.laptops
Subject: power conservation for laptos running unix?
Date: 24 Jul 92 17:50:13 GMT
Organization: TRW Financial Systems


I am interested in running unix on a laptop.  A major concern
is battery life.

So, my quetion is this:  what power conservation techniques work
while running unix, which ones don't work (panics?), and which ones
backfire (i.e. shorten battery life).

Obviously, the 30 sync cycle is likely to keep the disk powering
up & down all the time, or to keep it on all of the time.  However,
I believe that this can be tuned (esp. with source!).

What other aspects are there to consider?

        ====|====|====|====|====|====|====|====|====|====|====|====|====
David Paigen		      TRW Financial Systems		paigen@tfs.com
      "Lay on, McDuff, and damn'd be he who first cries, 'hold, enough!'"
NSA: Bush IRA assasination CIA terrorism Hussain PLO pipe bomb kill maim KKK
From: terry@npd.Novell.COM (Terry Lambert)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd security enhancements are needed before using INTERNET!
Date: 27 Jul 92 17:36:31 GMT
Organization: Novell NPD -- Sandy, UT

In article <l74ebkINN1sd@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
>As far as use of 'crypt' for password authentication -- i have been told
>by our local legal people that this is a permitted exception to the well
>known prohibition against unlicensed export of cryptographic codes.  The
>fact of the matter is that the precompiled password authentication codes
>present absolutely no risk to national security.

	The problem is the ability to distribute source.  One of the base
intentions of 386BSD, from what I have seen, is to make everything freely
redistributable *in source form*.  While it is certainly possible to do
this, and there are even previous postings telling how to do this, the fact
that you have to FTP a DES library makes any such soloutions gray.  In any
case, it is unlikely that the government would just stand by if the DES
code from Australia became part of the 386BSD distribution.

	Perhaps the poster of the original method would be willing to
provide a binary "install kit" as you suggest?

					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Disclaimer:  Any opinions in this posting are my own and not those of
my present or previous employers.
Newsgroups: comp.unix.bsd
From: dealwisb@cognos.com (Brian de Alwis)
Subject: Re: Do YOU think that this generates correct kernel ?
Keywords: kernel config
Organization: Cognos Incorporated, Ottawa CANADA
Date: Tue, 28 Jul 1992 22:19:39 GMT

In article <1992Jul28.151518.18102@lut.fi> ats@lut.fi (Ari Suutari) writes:
>	controller	wd0	at isa? ....
>	disk		wd0	at wd0 drive 0
>	disk		wd1	at wd0 drive 1
>
>	This file produces a working kernel. But if I look at the
>	wd.h (for example) file at /sys/compile/MY_HOST there is a 
>	line which states:
>
>	#define	NWD	3
>
>	I think that this is becouse the config utility ses three lines
>	containing "wd". This is incorrect, since I have only 2 disks
>	configured. Same problem, of course, exists for "fd" too.

I've found this problem too (I set aside tonight to look at it - you
jumped my gun :-) It's interesting that if you have a config of

controller wd0 at isa?
disk       dk0 at wd0 drive 0
disk       dk1 at wd0 drive 1

NWD is defined as 1 (which breaks the patches posted to support > 1 HD).
It seems that config is looking in the wrong places to figure out the
number of possibly-attached devices.

Another 'nifty' feature with the above config (using dk[01] instead of
wd[01]) is (as you also discovered) that the swap device is wrong! If you
look in your swap*.c (*=386bsd by default) in your /sys/compile/MACHINE,
you'll find a structure swdevs? which lists the available swap devices.
You'll have to change this to use the major/minor (in the form shown) of
your swap partition, until this gets sorted out. 
 
 +++BdA
-- 
+++BdA  Brian de Alwis. Brain on loan to Cognos Inc, Ottawa, Ontario.
	dealwisb@cognos.com, or bsdealwi@napier.{waterloo.edu,uwaterloo.ca}
	"Nine out of ten men who tried camels said they preferred women"
Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: problems bringing up 386BSD 0.1
Date: 21 Jul 92 10:00:33 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <1992Jul20.212320.20786@hemlock.cray.com> overby@cray.com (Glen Overby) writes:

>I, too, am a member of the "It Won't Boot" clan.

>System:
>Megatronics 386SX-16
>387SX (yup, bought one just for 0.0)
>4MB RAM
>VGA monitor (SEFCO is on the manual; Trident is the Copyright in the ROMs)
>Seagate ST-02 SCSI / Floppy
>1.44MB floppy

>When I boot, 386bsd thinks it recognises a WD controler out there (there is 
>none) and hangs after mounting /dev/fd0a as root.  It's my guess that it's
>waiting for the non-existant ISA disk to respond.  I've pulled all cards but
>the Seagate and VGA.  I think I'll try recompiling without a WD controler at
>all (that didn't work under 0.0, but this ISN'T 0.0) or hard-code the driver
>to ignore what it thinks is a controler.

>Glen Overby

I never read something about ST-02 SCSI support, the installation file
reads:
"....This release supports a 386/486 SX/DX ISA (ATBUS)	sys-
tem,  with  the	traditional hard and floppy disk controller
(MFM, ESDI, IDE, SCSI - Adaptec 1542, RLL).  Also, the usual
                 ^^^^^^^^^^^^^^^^^^^

display adapters (MDA/CGA/VGA/HGC) are supported, along with
the serial communications ports (COM1 and COM2) and parallel
..."

Not a help, but a hint

Holger

-- 
|  |   / Holger Veit             | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
From: cgd@agate.berkeley.edu (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: made patches for 0.1 (READ THIS!)
Date: 22 Jul 1992 00:16:45 -0700
Organization: Kernel Hackers 'r' Us
Distribution: world
NNTP-Posting-Host: agate.berkeley.edu
Summary: if you've made changes to 0.1 to fix bugs, i want to know.
Keywords: patches, much mail, unofficial

Have you made a patch, etc. for 386bsd 0.1?

if so: Please send it to me...

For files of moderate size, please uuencode and send them to me...
(or, you can just "mail" the diff output, etc...)

For large things, please put them up in ~ftp/pub/incoming
on agate.berkeley.edu and send me mail about it...

I'd appreciate it if the mail were titled (minimally)
PATCHES or IN INCOMING (all caps for that part, please),
and gave a description of what you're sending/have put up...

If you put some stuff up elsewhere on the net (boot disks, etc),
please put them in incoming as well, and send mail -- i spend several
hours per day answering 386bsd mail alone, and i'm a full time student,
with a part time job (*NOT* this -- read, i don't have much time...)


thanks,

Chris Demetriou
cgd@agate.berkeley.edu
-- 
                            Chris G. Demetriou
                             cgd@berkeley.edu

     I'm not from the computer center, and I'm *NOT* here to help *YOU*!
From: torek@horse.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.bsd
Subject: Re: STDIO Mode "a+" screwed up
Date: 28 Jul 1992 00:47:22 GMT
Organization: Lawrence Berkeley Laboratory, Berkeley
Reply-To: torek@horse.ee.lbl.gov (Chris Torek)
NNTP-Posting-Host: 128.3.112.15

In article <39897@gremlin.nrtc.northrop.com> dec@lazarus.nrtc.northrop.com
(Dwight E. Cass) writes:
>   I have just spent the weekend trying to find out why rogue crashes
>when it attempts to update its score file and have found the problem:

>   In: /usr/src/lib/libc/stdio/flags.c - Mode "a+" translates to an
>       open flag with O_APPEND (in __sflags()).  This means that if
>       you seek the file to the beginning and start writting, all the
>       written will be APPENDED to the end of the file - rather than
>       updating the top of the file as specified by the plus sign.

This is not a bug.  ANSI C standard, section 4.9.5.3, pp. 126--127,
l. 39 ff.:

	Opening a file with append mode ('a' as the first character in
	the mode argument) causes all subsequent writes to the file to
	be forced to the then-current end-of-file, *regardless of
	intervening calls to the fseek function*.

[emphasis mine]

>   What's the cure - ouch.

Fix rogue.  It should use "w+" mode.
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 510 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov
From: terry@npd.Novell.COM (Terry Lambert)
Newsgroups: comp.unix.bsd
Subject: Re: partition booter uploaded to agate (select OS to boot on startup)
Date: 27 Jul 92 21:21:08 GMT
Distribution: comp
Organization: Novell NPD -- Sandy, UT

In article <TMH.92Jul27210553@keks.first.gmd.de> tmh@keks.first.gmd.de (Thomas Hoberg) writes:
>Hi folks!
>
>For those of you who want to select which OS to boot on system
>startup, I have uploaded a repleacement for the master boot block that
>allows you to choose from a menu on boot. It comes complete with
>source and a small installation program. It works on all PCs and OSs
>that I have encountered. I have put it on agate.berkeleay.edu into the
					   ^^^^^^^^^^^^^^^^^^^
					   agate.berkeley.edu


>/pub/incoming directory. I don't know whom I should inform about it
>and hope that it will move eventually wherever it belongs.
>
>If you have any problems with it, contact me.
>If you don't have FTP access, I could mail it to you. If you think it
>should be posted, I will (it's not *that* big).

Tell us the name of the file; you can download files from the incoming
directory by cd'ing there if you know their exact name (and thus do not
need to read the directory entries, which you will be unable to do!).  For
instance, you can download the unofficial FAQ by downloading the file
'386bsd.FAQ'.  Not that you must cd to the incoming directory before you
can do this.

					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Disclaimer:  Any opinions in this posting are my own and not those of
my present or previous employers.
Newsgroups: comp.unix.bsd
From: cs481a07@umbc5.umbc.edu (cs481a07)
Subject: Questions/problems with 386BSD 0.1
Organization: University of Maryland Baltimore Campus, Academic Computing Services
Date: Wed, 29 Jul 1992 04:22:44 GMT


	I've been trying to get RNto compile on 386BSD 0.1. It dies on
linking with a undefined _stty and _gtty. I've dug through everything I
can think of and can't find a way around/fix for this. Has anyone gotten
RN to work?

problem 2: Elm. I got it compiled and am able to read mail, but when you
try to mail a message all it sends are the headers. (And you have to type
a S instead of s when you get the the send/forget/edit prompt.)

problem 3: I noticed that anyone could run shutdown. the permissions were

-rwsr-x--- owner root group operator. I changed the permissions to
-r-x------ and anyone can still run it. (you get the shutdown: NOT super-user)


Any help is appreciated...

	Later, Matt
Xref: sparky comp.unix.bsd:3133 gnu.misc.discuss:2576
From: sxjcb@orca.alaska.edu (Jay C. Beavers)
Newsgroups: comp.unix.bsd
Subject: NFS mount of /usr
Date: 29 Jul 92 17:59:19 GMT
Followup-To: comp.unix.bsd
Organization: University of Alaska Computer Network

I've been playing around with NFS and such and it's working just fine, so
I've
tried to take NFS to it's next logical step on my 39 MB system -- NFS
mounting
/usr.  However, 386BSD seems to think that this is just a horrible idea and
I've had no end of trouble.

If I leave the rc file intact, I get a system hang after 'starting system
logger'.

If I edit the rc file and remove all but the very basest of network
commands, I get a hang after the rc file finishes.  /usr is mounted
correctly (as a ls /usr shows from the rc file) and the script does reach
the exit 0 (as an echo statement shows) but it hangs after that.  Once I
did get a kernal panic error message after about 2-3 minutes of nothing,
other times it just seems to hang forever.

If I edit the rc file to hardcode my old usr directory (/oldusr) to every
file located in /usr I get a hang after the rc file ends.  

I've copied /usr/distbin/mount & umount to /bin and I'm running the 0.1
patched
kernal from agate.  Other than initial setup for various /etc/* files to
get
networking and NFS running, no other mods have been made to the system.

______________________________________________________________________________
                                        |    jay@seaspray.uacn.alaska.edu
Jay C. Beavers                          |    sxjcb@orca.alaska.edu
University of Alaska Computer Network   |    sxjcb@alaska.bitnet
________________________________________|_____________________________________