HDTenEightyP/NetNews huggingface dataset:
From: terry@npd.Novell.COM (Terry Lambert)
Subject: Re: 386bsd-0.1: primary bootstrap (wdbootblk.c) problem & fix.
Keywords: 386bsd boot bootstrap wdbootblk.c
Organization: Novell NPD -- Sandy, UT
Date: Mon, 27 Jul 1992 19:25:02 GMT

In article <greg.712261295@hibp1.ecse.rpi.edu> greg@ecse.rpi.edu (Greg) writes:
>Terry, please reread my message. THIS IS NOT THE SAME BUG!!!!!!
>This problem is in wdbootblk.c. The code contained in wd.c has not
>even been loaded off the disk at the point when this hang occurs! 
>To understand what is going on, study wdbootblk.c.

	I think I goofed in recommending the wd.c fix for this problem;
however, the status register being polled after the delay is wd_status,
and I still believe that a canonical fix would be looking at wd_altsts
instead.

	Greg's delay loop will have the same effect -- that is, making sure
the controller has finished it's reset prior to using it.

	The confusion seems to have originated from the various paths in
the boot and non-boot sections of the kernel which lead to files of the
same name.  I would suggest that any future patches refrain from the use
of relative paths to identify the file being patched.  In particular, it
would be nice if they contained the full path from the root of the volume
("/") rather than something like "./xxx/yyy/zzz.c", which assumes they are
starting in the same directory that patch poster did.

	...This, of course, wouldn't have saved me from foot-in-mouth in
this particular case 8-(.

					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.
From: james@raid.dell.com (James Van Artsdalen)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD: Anyone using gcc-2.x on 0.1?
Date: 30 Jul 92 17:40:31 GMT
Reply-To: james@raid.cactus.org (James Van Artsdalen)
Organization: Dell Computer Co

In <1992Jul29.155631.21213@thyme.jpl.nasa.gov>, kaleb@thyme.jpl.nasa.gov (Kaleb Keithley) wrote:

> I'm highly interested in moving to the latest version of gcc-2.x,
> (currently 2.2.2) because:

> a) I'd like to take advantage of it's ability to emit 486 specific
>    code (instruction scheduling, primarily)

gcc 2 does no insn scheduling for the 386 / 486.  With -m486, it chooses
slightly different instruction sequences, and aggressively aligns loops
on cache line boundaries.

> b) Its ability to emit PIC (Position Independent Code) seems to be
>    a pre-requisite for shared libraries.

The PIC scheme it uses is intended for SysVr4, which I am told is
similar to the SunOS scheme.

> Has anyone else "bootstrapped" up to 2.2.2 yet?  Has anyone who
> has, rebuilt the kernel with it yet?

Compiling machdep.o with gcc2 causes the kernel to crash during
bootstrapping for some reason.  I hope to look into it this weekend.
-- 
-- 
James R. Van Artsdalen          james@bigtex.cactus.org   "Live Free or Die"
Dell Computer Co    9505 Arboretum Blvd Austin TX 78759         512-338-8789
Newsgroups: comp.unix.bsd
From: wutcd@hrz.tu-chemnitz.de (Joerg Wunsch)
Subject: Re: adding data encryption
Organization: tu-chemnitz
Date: Fri, 31 Jul 1992 16:56:55 GMT

Hi Holger;-)
i assume you'd understand German, too, but maybe it's interesting for
some non-German-speaking people (is there any?), too:-)
I also see this problem, and some weeks ago i took some DES sources
available on an ftp server (saturn.hrz.tu-chemnitz.de) nearby, and tried
to make use of that. Okay, i have a password encryption function, but
not THE passwd encryption. At least it seems to be as secure as the
original, but there should still be any way to use those packages
(which certainly have the same base as the USA DES). If there's some
more interest in what i do have, i could post it, or you can get it
via email. Maybe if i'll get enough time, they could be improved, so
the encryption will match the commonly used one.
About sense or nonsense of DES and the US export policy, refer to
Terry Lambert's (terry@npd.novell.com) article (article id:
1992Jul28.164752.7422@gateway.novell.com) posted here.

	Tschuess, J"org

--
J"org Wunsch		         joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de
Textil Computer Design GmbH
R"ahnitzgasse 18, D-O-8060 Dresden
                              If anything can go wrong, it will. (Murphy's Law)
From: pdac@quantime.co.uk (Peter Da'Costa)
Newsgroups: comp.unix.bsd
Subject: Help! 386BSD 0.1 won't boot off HD
Date: 22 Jul 92 13:35:46 GMT
Organization: Quantime Ltd, London


  I've just tried out the Tiny 386BSD disk in a Dell 325p and it worked
fine. However, after proceeding with the install (which seemed to go
through without a hitch), I pressed ENTER to reboot and got the following
messages just after my WD8003 was detected:


vm_fault (fe071c9c, 0, 1, 0) -> 1
   type c, code fe060000
trap type 12 code = fe060000 eip = fe0127a cs = 8 eflags = 10282 cr2 14 cpl 1a
panic: trap

The operating system is saving a copy of RAM memory to device 1, offset 0
(Hit any key to abort): [ amount left to save (MB) ] -- device bad
system rebooting


(I sat here for many reboots to get this message down!)
Anyway, can anyone give me any clues as to what goes on ?
The system is:

Dell 325p (386 25MHz)
4 MB RAM
190MB IDE drive.
On-board Paradise VGA (512Kb)
3.5"  HD floppy (0)
5.25" HD floppy (1)
COM1 + COM2 (On-board)

Also I have an SMC ethernet board (WD8003), but I took that out and it
didn't make any difference. The system seems to work fine off the floppy.

						...... Pete
-- 
--------------------------------------------------------------
Peter Da'Costa					Quantime Ltd
EMAIL: pdac@quantime.co.uk			67 Maygrove Rd
PHONE: +44 71 625 7222				London NW6 2EG
Newsgroups: comp.unix.bsd
From: rodeen@buddha.ncc.umn.edu (Rick Odeen)
Subject: Swap problems
Organization: Nutrition Coordinating Center, University of Minnesota
Date: Sun, 26 Jul 1992 03:56:57 GMT

When trying to recompile the kernel for the first time today I started
getting messages something like:

/386bsd: error 0 blkno xxxx sz 4096 swap_pager_finish: clear of page xxxxx failed.

I assume this has something to do with my swap space not being setup properly.
I have made an entry in the /etc/fstab file for the swap partition.
I installed my system using the provided install script that creates one
big partition and a 5 meg swap partition and disklabel -r wd0 shows that
this partition exists.  df /dev/wd0b gives somewhat bizarre results though
which I don't have written down at the moment.

Is there more that needs to be done to make swapping work?  Any suggestions?

Thanks!

-Rick Odeen


-- 
"MINIX costs $169, but the license allows  | Rick Odeen 
making two backup copies, so the effective | rodeen@buddha.ncc.umn.edu 
price can be under $60."                   | rutgers!umn-cs!buddha!rodeen
         - ast@cs.vu.nl (Andy Tanenbaum)   |
Newsgroups: comp.unix.bsd
From: terry@npd.Novell.COM (Terry Lambert)
Subject: Re: Installing 386BSD-0.1 ? (Q)
Keywords: 386BSD install
Organization: Novell NPD -- Sandy, UT
Distribution: comp
Date: Mon, 27 Jul 1992 17:06:02 GMT

In article <5356@ucsbcsl.ucsb.edu> 9531mide@ucsbuxa.ucsb.edu (Curt A. Mideiros) writes:
>I obtained the two files, "rawrite.exe" and "dist.fs" from    
>agate.berkeley.edu (via ftp-binary xfer).  I then ran rawrite to 
>transfer a bootable image to a 1.44MB formatted floppy disk.  The
>problem is, that it doesn't seem to boot.  I'm using a PS/2 Model 70
>w/ 8M ram and 120MB HD, with an 8514 adapter. Is there a hardware
>compatiblity problem with PS/2's ??

No, 386BSD will not boot on a PS/2.  It would require a seperate binary, and
a lot of work on MCA drivers.

					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: appel@xcf.Berkeley.EDU (Shannon D. Appel)
Newsgroups: comp.unix.bsd
Subject: 0.1 386BSD's stdio.h
Date: 28 Jul 92 05:49:23 GMT
Organization: csua
NNTP-Posting-Host: soda.berkeley.edu

Trying to compile MH for 386BSD 0.1.  Several minor problems, including
one with the FILE structure.  Apparently, MH is quite naughty, and uses
some of the internals of the FILE structure, namely:

ptr
base
cnt

Now, 386BSD has the internals of the FILE structure set up differently,
and I would most definitely prefer not to have to dig through the source
to figure out what correspondences [mostly because stdio.h files that I've
looked at in places OTHER than 386BSD are poorly documented].

Is there anyone who can tell me if there are direct correspondences to
the above internals in the 386BSD stdio.h file, and what they are?

Thanks.

Shannon
Newsgroups: comp.unix.bsd
From: roe@Unibase.SK.CA (Roe Peterson)
Subject: SCSI drive geometry woes...
Organization: Unibase Telecom Ltd.
Date: Thu, 30 Jul 1992 22:00:55 GMT

Well, 386BSD is up and running, and working well (except for the occasional
hangup which I'm attributing to the very small swap space).

I've just received a new fujitsu 640MB SCSI disk drive, and I'd like to take
full advantage of the UFS cylinder grouping scheme.

However, I'm having some major problems.  It seems that 386BSD does not
care about the disk geometry specified in the disk label during boot.

With an adaptek 1542B controller, the disk BIOS reports a geometry of
640 cylinders, 64 heads, and 32 sectors.  The _actual_ drive geometry
is 1658 cylinders, 15 heads, and 53 sectors/track, with 3 sectors/cylinder
spared for alternates, with 15 cylinders also spared (giving 1643 cylinders).

I've used a little fdisk-like utility (called pfdisk) to change the drive
geometry, and lay out partitions on cylinder boundaries.  I actually had
to lie through my teeth here, since the master disk partition table has
no concept of spares/cylinder;  hence, I've told the fdisk partition
table that the drive has 1642 cylinders of 24 heads with 33 sectors,
for a total of 792 blocks/cylinder ((15*53)-3).

Then, I've created a disktab entry with the same lie in place, and
created the disklabel for the driver.  Everything looks good so far.
When I run newfs, I override the defaults from the disklabel, and give
it the _real_ drive geometry, as well as the number of spares/cylinder.
Makes the file system OK, and the _sound_ seems to indicate that I've
got things laid out correctly on cylinder boundaries.

Mount the new disk (/dev/as1a), proceed to copy the whole distribution
from drive zero.  Everything looks just fine.

Then, I re-address the new drive to unit 0, and attempt to boot.  I get
as far as checkpoint e, and the whole system reboots.

My theory is that some (or all) of the bios drive geometry is being
paid attention to by boot, regardless of the information in the disk label.

Anyone got any comments or ideas?  I think this would be a big disk
performance win if I can get it working correctly.
From: donaldh@cs.hw.ac.uk (Donald I. Hunter)
Newsgroups: comp.unix.bsd
Subject: Using the second IDE drive
Keywords: IDE SECOND DRIVE
Date: 22 Jul 92 13:25:00 GMT
Organization: Dept of Computer Science, Heriot-Watt University, Scotland


I'd like to install 386BSD on my second IDE drive, possibly using a floppy
disk to boot the system. It's not my personal machine, so MSDOS has to stay
untouched on the first drive.

Is this possible ?   Could you send any responses by e-mail, 'cos I have an 
incoming news delay of several days. If I have any responses, and I'm successful, I'll post a summary to the net.

Cheers, Donald.
-- 
 Donald I. Hunter			donaldh@cs.hw.ac.uk
 +--------------------------------------------------------+
 | Hello. Just walk along and try NOT to think about your |
 |    INTESTINES being almost FORTY YARDS LONG!!          |
 +--------------------------------------------------------+
Newsgroups: comp.unix.bsd
From: roe@Unibase.SK.CA (Roe Peterson)
Subject: Re: Kernel Recompilation Problems
Organization: Unibase Telecom Ltd.
Distribution: na
Date: Mon, 27 Jul 1992 05:21:25 GMT

rivers@ponds.uucp (Thomas David Rivers) writes:

>  Just to add to the list of symptoms, usually when I recompile
> the kernel, everything locks up; forcing me to reboot.

>  I have a 20MHZ 386, 9megs of memory and an ULSI FPU, with
> a 240M IDE drive.

I've seen this on kernel rebuilds, and large compiles (for example, remaking
libc.a from scratch).

I'm running a 40 Mhz 486 with 16 Meg.  So far, I've theorized that this
problem is caused (somehow) by the fact that I've only got 5 MB available
for swap/page;  since I'm moving onto a new disk real soon now, I've just
lived with it until I can partition a 16M swap area on the new disk.

Mr. Jolitz:  Is this theory at least plausible?

Newsgroups: comp.unix.bsd
From: ugewa001@unibi.uni-bielefeld.de (0134)
Subject: serial Printer problem with 0.1
Summary: how can I stty /dev/lp
Date: Tue, 28 Jul 92 11:42:17 GMT
Organization: Fakultaet fuer Geschichte
Keywords: serial, Printer, stty

Hi there

I want to connect a LQ850 to com2. In fact I have done so, the only problem
is that i don't know how to tell lpd/lpr (?, or whatever) to use
cs8, - istrip and -parenb. I can cat to /dev/com2 after having done the
stty (stty -f /dev/com2 cs8 -strip -parenb) and everything is ok.
But when i use lpr, the output is corrupted. 
Is there an easy way to solve this? 
Or should I use the lpt-patches?

**********************************************************************;-)******
Folker Meyer                          /* in real life*/
folker@guphx2.uni-bielefeld.de        /* most of the time*/
   Microsoft, the company that brought us EDLIN.
-- 
------------------------------------------------------------------------
Folker Meyer                      * "God is real,
Universitaet Bielefeld            *  unless declared integer."
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Date: 24 Jul 1992 09:50:18 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

In article <1821@adagio.UUCP>, grog@adagio.UUCP (Greg Lehey) writes:
> ... an AT&T
> spokesman is quoted as saying that anybody who has had access to AT&T
> UNIX (tm) sources cannot develop operating system software which is
> not derived from it. ...

Hah !
Does that mean that anyone having seen a Ford and then goes off designing
hir own car will be sued by Ford for the reason of having been exposed
to Ford cars ?
How about journalists using words found in
<insert the name of your favourite dictionary here> will be sued by the
publishers of said item ?

Just a thought
	Bernard

P.S. How about anybody who has read the book by Brian & Dennis (who, as far
as I know, happen to be employed by a certain company) ?
-- 
Bernard Steiner, FB Informatik/IRB, Uni Dortmund,    vox +49 231 755 2444
Postfach 500500, D-W-4600 Dortmund 50, Germany       fax +49 231 755 2386
bs@Germany.EU.net          ...!uunet!unido!bs

*III  And they gave it Instructions, but knew it not. } From The Book of Nome,
*IV   It is, they said, a Box with a Funny Voice.     }      Mezzanine v.III-IV
From: michael@resonex.com (Michael Bryan)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Date: 21 Jul 92 06:45:25 GMT
Organization: Resonex Inc., Sunnyvale CA

In article <1992Jul21.030532.10307@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
>In other words (potentially *wrong* words, mind you, since I'm not a
>lawyer), *anything* based on the Net/2 tape, according to USL, requires an
>AT&T/USL license!! (EEEEP!)
>
>Comments, anyone?

Imminent death of free-UN*X systems predicted...

-- 
Michael Bryan        michael@resonex.com                     |     ,_,
"Pretenders I meet are making a trail along the way.         |    /oo \
They say that they know how to show me a path to guide my    |    <>__|
way to truth..." --- David York, "The Quiet of a Candle"     |    |  U|
From: jlu@cs.umr.edu (Eric Jui-Lin Lu)
Newsgroups: comp.unix.bsd
Subject: Where can I find Disk Manager???
Date: 22 Jul 92 18:25:23 GMT
Organization: University of Missouri - Rolla
Originator: jlu@mcs213i.cs.umr.edu

Where can I find the Disk Manager mentioned in INSTALL.NOTES?
Thanks in advance!!

--Eric

-- 
***************************************---       Grad. student 		---*
* Obviousness is always the enemy of  *   \     Jui-Lin Lu (Eric)      /   *
* correctness.  -- Bertrand Russell   *   /      jlu@cs.umr.edu        \   *
***************************************---   Univ. of Missouri-Rolla    ---*
From: pred@iitmax.iit.edu (Predrag S. Bundalo)
Newsgroups: comp.unix.bsd
Subject: ethernet connection not working.  Software bug?
Keywords: ethernet
Date: 31 Jul 92 06:54:39 GMT
Organization: Illinois Institute of Technology / Academic Computing Center

Well, I got "Tiny 386BSD" installed on my hard disk.  I had to use
the whole disk (100MB IDE drive) since it kept panicing and going
into an infinite reboot/panic loop.

This was the summary for those who wanted to know how the problem was
solved.

Onwards to the next problem:

I have installed an NE2000 Novel ethernet card.  BSD detects it fine, but
I'm unable to use it to ftp over the rest of the distribution.  I even
tested it on another card (an NE1000).  I know the line is fine because
we're currently using it on a NeXTstation.  So it seems the problem is
with either the user (me) not knowing how to get it working even though
he did follow TFM, or that there is something wrong with the software.

Can someone who's ftp'd the rest of the distribution in this way please
contact me and explain what they did and what I need to do?

As I've said before, this will be IIT's 386BSD testbed, serving as an
experience platform for our researchers, which I'm told is the goal of
386BSD.

Regards,

Pred Bundalo
-- 
:::  Predrag S. Bundalo                  Academic Computing Center     :::
:::  Illinois Institute of Technology    Chicago, Illinois             :::
..........................................................................
:::  Internet:  pred@{iitmax, elof}.iit.edu, syspredrag@minna.iit.edu  :::
:::  BITNET  :  syspredrag@iitvax.BITNET                               :::
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
From: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats
Date: Wed, 22 Jul 1992 15:18:00 GMT
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)

In article <1992Jul21.122530.23497@resonex.com> michael@resonex.com (Michael Bryan) writes:
>How long has the NET2 distribution (and other AT&T-void sources) been
>available?  If this is indeed the first legal action that AT&T/USL has
>taken, perhaps a point in BSDI's favor is that AT&T has waited until
>now to protest.  The NET2 distribution was no secret, nor were the
>various projects which are based upon it (especially Jolitz's 386BSD
>and BSDI's BSD/386).
>
>It obviously reeks of someone saying "Omigawd, these BSD systems are
>actually becoming popular, and we might lose our stranglehold!  Quick,
>do something!"  I certainly hope that the courts tell them where they
>can stuff it.
>
>Of course, I don't have a lot of faith in our legal system's ability
>to do sensible things in the realm of software...

There are two interesting things to consider here.

1.  Mt Xinu, NeXT, and others who are selling BSD on top of Mach or in
    some other form, are all doing it under AT&T licences.

2. AT&T is probably trying to clear a path for Destiny (SVR4.2) sales.

-- 

Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
Newsgroups: comp.unix.bsd
From: scott@pita.cns.ucla.edu (Scott Burris)
Subject: 386BSD 0.1: variable blocksize tape on SCSI bugfix
Reply-To: scott@pita.cns.ucla.edu (Scott Burris)
Organization: UCLA Campus Network Services
Date: 27 Jul 92 13:05:21 PDT

The SCSI driver is broken for variable length tape devices.  The problem
is that the data transfer length is computed by code which assumes a fixed
block tape drive.  This causes the computer to transfer less data than
the SCSI transaction calls for, which hangs the SCSI bus.  Context
diff's follow.  


*** as.c	Sun Jul 19 08:15:02 1992
--- as.c.orig	Sat Jul 18 20:10:32 1992
***************
*** 899,906 ****
  	n = 0;
  	sp = as->scatter_list;
  	nscatter = 0;
- 	if (as->tape && as->bs == 1)
- 		total = bp->b_bcount;
  	while (n < total && nscatter < NSCATTER) {
  		thistime = page_size - ((vm_offset_t)p - trunc_page (p));
  
--- 889,894 ----
--
----------
Scott Burris
UCLA Campus Network Services
cnetslb@oac.ucla.edu (213) 206-4860 - OR - scott@pita.cns.ucla.edu
Newsgroups: comp.unix.bsd
From: pjm@cshl.org (Pat Monardo)
Subject: Re: AT&T sues BSDI
Organization: Cold Spring Harbor Laboratory
Date: Thu, 23 Jul 92 18:05:14 GMT

In article <1992Jul23.173248@eklektix.com> rcd@raven.eklektix.com (Dick Dunn) writes:
>over the world.  USL hasn't moved against Net 2, which sure looks like
>tacit approval to me...so let's make sure it's everywhere.  My own opinion

didn't i read here that USL *IS* going after Net 2!?
I recall something to the effect that since BSDI is based on Net 2,
AT&T is challenging BSDI's claim that an AT&T license is not necessary.

-- 
-- Pat Monardo		What is the cause, what the reason
-- pjm@cshl.org		for the manifestation of a smile?
Newsgroups: comp.unix.bsd
From: juengst@boss1.physik.uni-bonn.de (Henry G. Juengst)
Subject: cksum for SYVR4 to check 386BSD 0.1 distribution
Keywords: cksum, MANIFEST, 386BSD, SYVR4, check sum, dist
Organization: Universit"at Bonn, Informatikinstitut, R"omerstr 154, W-5300 Bonn 1
Date: Tue, 21 Jul 1992 07:35:04 GMT

Hello,

  first, let's say thank you very much to Bill, Lynne, William Jolitz
and all other people working for 386BSD.

I had some little problems with the distributed files and the
file MANIFEST.

I have to use "swab" option on the Data General DG/UX 88K machines
here (nice things). But all files with odd numbers of bytes produce
errors and are left as they are. :-( I solved this problem on a
SUN sparc station.

I like tar much more, but it's not a 100% solution.

Another problem were the check sums in MANIFEST, because I didn't
know how to calculate these values and sum (with or without -r)
didn't work. A simple addition of all bytes didn't work, too.

I found cksum in srcdist and compiled it. Some definition problems
had to be resolved (quick hack). DG/UX 5.4.1 is a System V R4. Now
I can begin to verify all files here (first check done) and use 386BSD
for education (for no money) in an astronomical observatory
(SNH, Erkrath/Germany) which is open for everybody.

I hope this modified cksum will help anybody just to verify the
contributed files before moving them to anywhere. Use make.sh to
compile it. But have a look before you start. May be you have
to change _PROTO_ARGS in all *.c & *.h using
sed 's/_PROTO_ARGS/YOUR_PROTOTYPE_MACRO/g' file.c >file.new.c
(it was __P in the original source). If you are not sure you should
have a look into your /usr/include/stdio.h (for example).

THIS IS NO PATCH FOR 386BSD !

Henry
-------------------------------------------------------------------------------
Sorry, here should be the uuencoded .tar.Z file. But the nntp server
fails because out of disk space; 40 kbytes - mmmh. You can get it via
anonymous ftp from

boss1.physik.uni-bonn.de:~ftp/pub/386bsd/cksum_dgux/cksum_dg.uue
[131.220.221.30]

for the next two month. You won't waste your time if you have a look
into the other directories (e.g. ~ftp/pub/dcl) !

If you don't have ftp access you can mail me. I will send it to you.