HDTenEightyP/NetNews huggingface dataset:
From: wheeler@jeckle.mitre.org (Brien L. Wheeler)
Newsgroups: comp.unix.bsd
Subject: Re: patched bootables on agate...
Date: 22 Jul 92 19:12:15 GMT
Organization: The MITRE Corporation, Bedford, MA

In article <explorer.711733580@tbird.cc.iastate.edu>, explorer@iastate.edu (Michael Graff) writes:
> 
> I tried these disks, but I still can't install BSD 0.1 on my Zenith 
> Z-386/25.
> 
> Machine info:
> 	150M ESDI drive, wd ethernet card irq 2/9, vga, com 1, com 2.
> 	386DX 25Mhz, no fpu.
> 
> Install info:
> 	install using the patched and non-patched dist.fs disks.  When
> 	installing, it seems to write to the hard drive fine.  If I
> 	hit ^C when it wants to reboot, I can mount the filesystem and
> 	everything seems to work.  However, it locks during reboot.
> 	The keyboard lights flash, and the floppy light stays on.  It
> 	requires a power cycle to make it come back to life.

I too have had problems loading 386BSD onto the drive in my Zenith Z-386
PC.  Unfortunately, I don't know enough about the PC architecture to
adequately describe my system, but it includes a WD8013 Elite at IRQ 2,
5 MB RAM, a Paradise VGA card, a 387 FPU, and an 80 MB HD (don't know what
kind).  I have the same problems as Michael Graff -- It just won't boot
off the hard disk, even though it appears to be installed correctly.

I did some fooling around with defining the whole disk as an extended
DOS partition, changing the partition tag to A5 and attempting the install,
but it still did the exact same thing when attempting to boot off the HD.

     Brien
From: wheeler@heckle.mitre.org (Brien L. Wheeler)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 29 Jul 92 14:08:42 GMT
Organization: The MITRE Corporation, Bedford, MA

In article <1992Jul29.073959.3841@nebulus.ampr.ab.ca>, dennis@nebulus.ampr.ab.ca (Dennis Breckenridge VE7TCP) writes:
> joeg@gagme (joe grosch) writes:
> 
> >I urge all those on the net who have copys of either Net2, BSDI, or 386BSD
> >to start making copys and distributing them as far and wide as possible.
> ...
> Are you absolutely out of your mind? Distributing licensed sources is 
> not only immoral but totally illegal. A license is a privilege NOT a 
> right to deal with the sources that were supplied to you in the way
> that YOU feel is appropriate. This is a waste of bandwidth even flaming you!

Actually, neither Net2 nor 386BSD require the recipient to sign any sort of
license agreement.  I'm not sure what the restrictions are on redistribution,
but I would assume that since numerous FTP archives have been set up for
386BSD, that Bill Jolitz hasn't put any restrictions in place other than
retaining his copyright notice (Way to go,Bill :-).  Source code redistributions
of Net2 are also allowed if the copyright notices are retained.

BSDI code, however, is proprietary and cannot be redistributed without
permission from BSDI.  So we should spread around Net2 and 386BSD as much
as possible (although I think 386BSD has a good jumpstart already :-).

You really should make your points more clear or think before you speak.

    Brien

-----
     Brien L. Wheeler  |  I don't speak for MITRE, and they
     blw@mitre.org     |  don't speak for me.

"When I think back on all the crap I learned in high school..."
Newsgroups: comp.unix.bsd
From: explorer@iastate.edu (Michael Graff)
Subject: Z-386/25 and bsd 0.1
Organization: Iowa State University, Ames IA
Date: Thu, 23 Jul 1992 19:04:02 GMT

I finally got 386bsd to install on the z-386/25 in my office.  It
demands the entire hard drive, but it installs at least...

I have a bad sector @ 16217.  Now, I've tried damn near every form of
bad144 to remove this sector.  I think it might just happen to lie
within the kernel image, too...  

I panic with a vm_fault or some such trap when I "route add default
we0" so I'm stuck...

mread a:*.* . causes the vm_fault as well...

I still can't install in a partition, however...  Still working on
that.

--Michael




-- 
--
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
Newsgroups: comp.unix.bsd
From: hiller@fzi.de (Thomas Hiller)
Subject: disklabel problem with IDE drive
Organization: Forschungszentrum Informatik, Karlsruhe, FRG
Date: Thu, 30 Jul 1992 09:20:46 GMT


I have problems getting a disklabel on the HD, when I also have a DOS partition.
My BIOS parameters are different from those on the drive (a Seagate 3144). Is this
the problem ?
What must be changed, that always the BIOS parameters are used ?
Is this a general solution ?

Thanks Thomas
-- 
Thomas Hiller                                   email: hiller@fzi.de
Forschungszentrum Informatik
Abtl. Mikrorechnertechnik
Haid-und-Neu-Strasse 10-14                      Fax : +49-721-9654-809
D - 7500 Karlsruhe 1                            Tel.: +49-721-9654-832
From: gdt@ginger.lcs.mit.edu (Greg Troxel)
Newsgroups: comp.unix.bsd
Subject: Dell 325N notebook: 0.1 boots, power managegement seems ok, SLIP speed
Date: 29 Jul 92 19:48:48 GMT
Distribution: comp
Organization: /u/gdt/.organization

I booted the 0.1.cgd dist.fs floppy on a DELL 325N (386SL-25/4Mb
ram/60Mb disk) at a store; it seemed to run fine (I didn't try to
write onto the hard drive).  It took 102 seconds to boot from the
floppy (Ctl-Alt-Del to '#' prompt).

The "power management" features seemed to work under 386BSD; after a
while the screen blanked, and typing brought the system back.  The
suspend button caused the suspend light to flash and the display to
blank; after pushing it again 386BSD was still running.  I was able to
get to the "power managment control screen" (via Alt-F1) while running
386BSD, and return.  I haven't bought a 325N yet, though, and I'm not
completely sure I understand what is going on.

I have seen comments that (in the non-DOS world) only the Tadpole
Solaris supports "notebook power management".  However, from what I
can tell 386BSD already only writes the superblock on sync if the
filesystem has been modified (see
/usr/src/sys.386bsd/ufs/ufs_vfsops.c, procedure ufs_sync), and thus
doesn't need any "support" for disk/screen power saving, at least with
the Dell 325N.  Turning down the clock speed in the idle loop is
another matter, and this may be what is meant by OS support for power
management.

I am about to purchase a notebook on which to run 386BSD, and I have a
few questions/worries (the Dell 325N seems totally winning except 1)
it only has 1 serial port 2) it doesn't have a 16550 3) it doesn't
have an expansion bus connector):

1) Will SLIP under 386BSD will work at a reasonable speed (19200 or
   9600) on a 386sx-25 without a 16550A UART?  (More precisely, have
   you gotten it to work?)  A friend reports that 19200 works on a
   486dx-40, but 38400 doesn't.  Thus it seems that 9600 on a 386sx-25
   might not work very well.

2) Are there notebooks that have 16550A UARTs built in, or socketed
   8250s, and can be purchased with a 120 Mb (or bigger) disk?  Dell
   says that the UART on the 325N is soldered in place.  Zeos claimed
   that their notebook had a 16550 (is this true?), but the biggest
   disk they carry is 60 Mb.

3) Are the power management schemes of various notebooks dependent on
   DOS/BIOS, or will they work under 386BSD?

Please respond to me, and I will summarize and post.

	Greg Troxel (N1DAM)
	<gdt@ginger.lcs.mit.edu>
--
	73 de n1dam
	Greg Troxel
	<gdt@allspice.lcs.mit.edu>
From: rhealey@kas.helios.mn.org (Rob Healey)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 30 Jul 92 17:36:06 GMT
Organization: Rob's home system, Hopkins, MN

In article <1992Jul21.131433.16450@ntuix.ntu.ac.sg> eoahmad@ntuix.ntu.ac.sg (Othman Ahmad) writes:
=In article <1992Jul21.104627.3353@mel.dit.csiro.au> smart@wanda.mel.dit.CSIRO.AU (Robert Smart) writes:
=
=: This is insanity. Surely this will be thrown out of court.
=Who is going to defend NET/2?
=
	Just to remind the non-US audience, this legal action is being
	done in the US so by definition of the US legal system NOTHING
	is insane or absurd because the US "legal" system IS insane and
	absurd. This comes from lawyers controlling the legal, judicial,
	legistative and executive branches of the US government, i.e. a
	complete monopoly, to make the government and law infinitely complex
	and absurd.

	Be glad you don't have to deal with our excuse for a legal system...

		-Rob
From: terry@thisbe.npd.Novell.COM (Terry Lambert)
Newsgroups: comp.unix.bsd
Subject: Re: I wonder, did AT&T backstab BSDI?
Keywords: AT&T speculation lawsuit BSDI
Date: 29 Jul 92 17:44:37 GMT
Organization: Novell NPD -- Sandy, UT

In article <1992Jul29.144859.8222@bas-a.bcc.ac.uk>, ucacmsu@ucl.ac.uk (Mr Stephen R Usher) writes:
|> In article <1992Jul28.153750.8395@mintaka.lcs.mit.edu> knight@hal.gnu.ai.mit.edu (Knight of the Living Dead) writes:
|> >
|> >As I recall when System 5 Revision 4.0 was released, it was described
|> >(to me, anyway) as an attempt to gain "BSD Compatibility".  I'm wondering
|> >if the reason why AT&T held out sueing BSDI this long is so they could
|> >claim copyright of BSD's code/style/look/feel/etc while it was still
|> >popular, and then smash all the competition.
|> 
|> The only problem with this idea is that SYSVr4 (NOT System 5, that was
|> another Unix way back) doesn't look like BSD, it still looks like SYSV to
|> the normal user, ie you have horrid syntax for the ps utility where you need
|> to use a hyphen in front of the arguments and the devices... yuck!
|> 
|> The only real thing I've seen which is BSD is the socket library (not
|> complete) and the BSD compatibility library which is not complete either.

Things AT&T owes to Berkeley:

1)	UFS
2)	VFS
3)	Memory management strategies
4)	Job control
5)	csh
6)	TCP/IP
7)	telnet/ftp/finger/et al.
8)	mail/sendmail/smtp
9)	termcap
10)	pty's


	The top 10 list, to name a few.


					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.
Xref: sparky comp.unix.bsd:2844 comp.unix.sysv386:12419
From: grog@adagio.UUCP (Greg Lehey)
Newsgroups: comp.unix.bsd,comp.unix.sysv386
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!
Date: 25 Jul 92 11:29:43 GMT
Followup-To: comp.unix.bsd
Organization: LEMIS, Schellnhausen 2, W-6324 Feldatal, Germany

In article <jim.712001976@piggy> jim@ferkel.ucsb.edu (Jim Lick) writes:
>I had been planning on getting an upgrade from Esix 4.0.3A to the recently
>released Esix 4.0.4.  However, because of this action by USL/AT&T, I will
>not be purchasing an upgrade.  I have just sent off a note to Esix
>informing them of my action, and reasons.  Remember, long distance service
>isn't the only thing we can boycott.  Besides, I've never been an AT&T long
>distance customer, so I can't boycott that any more than I already am.
>If anyone else is considering the purchase of any AT&T or USL licensed
>product (which includes all the System V Unixes), you might consider holding
>off on the purchase.  But the important thing if you do is to tell your
>vendor and USL what you're doing and why.

Completely independently of this lawsuit, but certainly in keeping
with the sentiments expressed here, you should consider dropping
System V and getting BSD/386 instead: it's *better*. I've been using
it since March of this year, had been using Interactive and SCO
before, and was expecting a beta version (still the current BSDI
status) to be correspondingly more flaky. In fact, it's more robust
and a *damn* sight easier to install, use and configure than any
System V I've used. In addition, both tape and Ethernet performance
run rings round ISC 2.2. Now's an ideal time to try it!

-- 
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
From: atsuo@harl.hitachi (Atsuo Kawaguchi)
Newsgroups: comp.unix.bsd
Subject: Re: Partial success installing 386BSD 0.1
Date: 23 Jul 92 01:40:30 GMT
Distribution: comp
Organization: Advanced Research Laboratory, Hitachi, Ltd
In-reply-to: dvs@ze8.rz.uni-duesseldorf.de's message of 22 Jul 1992 19:50:55 JST

In article <dvs.28@ze8.rz.uni-duesseldorf.de>, dvs@ze8.rz.uni-duesseldorf.de (Wolfgang R. Mueller) writes:
>>   # install
(stuff deleted)
>>   ...
>>   Installing files from installation floppy.
>>   Extracting the distribution utilities from the installation floppy.

>> For a minute or so there are some floppy accesses and some to harddisk,
>> but then there does not happen anything else (I waited 10 to 15 minutes).
>> Taking out the boot floppy triggers no reaction.
I think I had the same problem. In my case, the problem went away by
changing BIOS setup so that shadowing was disabled. For example, my
machine has AMI BIOS. I disabled all shadowing in the ADVANCED CMOS
SETUP (I havn't tried any combination of the shadowing).

--
Atsuo, Kawaguchi
Advanced Research Laboratory, Hitachi, Ltd.
atsuo@harl.hitachi.co.jp
Newsgroups: comp.unix.bsd
From: fredw@mks.com (Fred Walter)
Subject: Re: Q: QIC-02, mountain tape 150 Mbyte
Keywords: QIC-02, mountain tape, file safe
Organization: Mortice Kern Systems Inc., Waterloo, Ontario, CANADA
Date: Tue, 28 Jul 1992 01:03:52 GMT

juengst@boss1.physik.uni-bonn.de (Henry G. Juengst) writes:
>  I've got a problem with a Mountain tape - I think it's a file safe 7160
>(it's not here, but sure it's a 150 Mbyte tape) - with a QIC-02 interface.
>
>I use I/O address 300H, IRQ 5 and DMA channel 1 as described in INSTALL.NOTES,

Your controller card isn't (currently) supported by 386BSD 0.1.
Not all 'QIC-02' controller cards are the same - the supported unit
(EG. Wangtek's version) is different than the Mountain controller card.

	fred
-- 
Disclaimer: everything I write is my *personal* opinion and does not represent
or reflect the opinion of the company which employs me.
Newsgroups: comp.unix.bsd
From: faldor@seq.uncwil.edu (Faldor Inglorion)
Subject: how to get 386bsd to boot using OS/2 boot manager
Organization: Univ. of North Carolina @ Wilmington
Date: Sat, 25 Jul 1992 20:46:14 GMT

Currently I have gotten the OS system up and co-existing with
OS/2 and MS-DOS on my little 386/25 120Mb IDE-HD.  Does anybody
know how to get 386bsd0.1 to boot thru OS/2's boot manager...
I currently have it bootable and and named... It seems to attempt
a boot but by doing so it reboots the boot manager.. Kooky huh!?

Thanx in advance,
Faldor

.___________________________________________________________________.
|               University of North Carolina at Wilmington          |
|                          Faldor Inglorion                         |
|                        faldor@seq.uncwil.edu                      |
|-------------------------------------------------------------------|
|  Alien Invasion Division : Integration/Substitution Group. (ISG)  |
.___________________________________________________________________.
Newsgroups: comp.unix.bsd
From: rhealey@kas.helios.mn.org (Rob Healey)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Keywords: AT&T 'Death Star' rises over BSDI's horizon [Tel. 1-800-800-4BSD
Date: 30 Jul 92 17:44:14 GMT
Organization: Rob's home system, Hopkins, MN

In article <1992Jul21.152007.1126@news2.cis.umn.edu> rodeen@buddha.ncc.umn.edu (Rick Odeen) writes:
=I don't think this is a valid claim, Linus Torvalds developed the Linux
=system in less than one year from scratch.
=
	Where did Linus get 99% of his MODELS for Linux? Ans: USL and BSD
	UNIX. "We stand on the shoulders of giants..."

	In other words, he used models for OS concepts that originated
	in UNIX(tm). The system calls, the library calls, the utility
	names, the program names, the memory models, the networking, the
	file systems, the concepts of UID,GID,SUID,SGID, sticky bits,
	mountable filesystems on a tree, etc. These are all basic
	features of UNIX(tm) that he used when creating Linux. You'd
	be VERY hard pressed to find OS concepts these days that HAVEN'T
	passed through a UNIX(tm) kernel at some time in the past. For no other
	reason than UNIX(tm) is the OS most researchers work with on
	a day to day basis and what they tend to hack on. Even micro kernels
	like MACH and probably NT borrow QUITE a bit from the UNIX(tm) system
	in system call names and symantics as well as utility and program
	names. Hell, even that pathetic MSDOG lifts I/O redirection and
	directory command names from UNIX(tm), amongst other things.

		-Rob
Newsgroups: comp.unix.bsd
From: overby@cray.com (Glen Overby)
Subject: It Boots (Re: problems bringing up 386BSD 0.1)
Organization: /dev/null
Date: 21 Jul 92 09:04:45 CDT

/* yes, a folowup to my own posting */
In article <1992Jul20.212320.20786@hemlock.cray.com> overby@cray.com I wrote:
>I, too, am a member of the "It Won't Boot" clan.

No longer!

Last night I woke up with an idea in my head.  A WD controler that isn't 
really there; a poorly documented jumper in the Seagate  manual.  Could it
be...

The Seagate ST01, ST02 controlers have a "compatability" register that emulate
the AT disk controler's register at 0x1F4.  This is documented in Section 3.5
in the ST01, ST02 SCSI Host Adapter Product Manual, Seagate pub number
36027-002 Rev G.  When JP6 is enabled, the controler responds to I/O address
0x1F4 as an AT controler would.

This jumper describes the register very poorly; it talks about both hard disk
controlers and 360K floppies at the same time.

When I moved this jumper to the "disabled" position, the 386BSD 'install' disk
booted fine.

Now to recompile with my ST02 driver, and I'll be up and running!

And to think that just maybe I could have had 0.0 up two months ago...

Glen Overby
From: lidl@rodan.UU.NET (Kurt J. Lidl)
Newsgroups: comp.unix.bsd
Subject: Re: Beginner's problems with 386BSD
Date: 26 Jul 1992 09:30:22 -0400
Organization: AlterNet -- Falls Church, Virginia, USA
Distribution: world
NNTP-Posting-Host: rodan.uu.net

In article <712169547snx@rama.demon.co.uk> steve@rama.demon.co.uk (Steve Entwistle) writes:
>1) How do I talk to my printer ? A /dev/lp device was not created when
>   I installed the binary distribution. Is it just a simple matter of
>   doing a mknod ? If so, what are the relevant major and minor devices
>   numbers ?

I don't think that an unpatched 0.1 release will work for you.
Someone has posted a parallel port driver for 0.0 that most likely
will work for 0.1 also.  (I have not tried this, so I have no *real*
idea if it works with 0.1)

>2) Should Mtools work straight out of the box ? If for example I issue
>   mdir a:  it produces the message init: open: No such file or directory.
>   Most of the other mtools commands produce similar messages.

Due to a couple of niggling things, it will not work.  Remove the
/dev/rfd0a and /dev/fd0a devices, then MAKEDEV fd0.  As it turns
out, mtools wants /dev/rfd0c, not the "a" partition on the floppy
drives.  Alturnatively, you can re-compile mtools to use
/dev/rfd0a instead of /dev/rfd0c (I found that creating the correct
devices was more expediante.)

>3) When I try and use ktrace, it just says Bad System call - core dumped.

Don't know.

>4) How do I configure the system for UK local time ? I tried symlinking
>   /etc/localtime to /usr/share/zoneinfo/GB-Eire, but this puts the clock
>   about 8 hours ahead.

Well, to configure the system for Eastern daylight time, I just
made /etc/localtime a sym-link to /usr/share/zoneinfo/localtime,
which I then hardlinked to /usr/share/zoneinfo/US/Eastern.
It seems to work for me.  (I also changed the timezone in the
kernel I built, but did not see any obvious change from that
alone.  I forget exactly what that value is used for -- it predates
the zoneinfo way of doing things, I think...)

Good luck.

-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: hudgens@SCRI.FSU.EDU (Jim Hudgens)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd 0.1 - Advice on bootstrap debugging needed.
Date: 24 Jul 92 15:16:26 GMT
Organization: SCRI, Florida State University
In-reply-to: jbh@aii.com's message of 24 Jul 92 13:25:19 GMT

In article <1992Jul24.132519.7656@pixie.aii.com> jbh@aii.com writes:
>In article <greg.711922033@hibp1.ecse.rpi.edu> greg@ecse.rpi.edu (Greg) writes:
>>I seem to have a problem booting that is timing dependant. My machine will
>>boot off wd0 about 95 % the time when in low speed mode. In high speed (33MHz)
>>it boots only about 20% of the time.
>Greg,
>  I think you'll find if you pick up either the latest bootwd (patched) or
>grabbed the diff's or uuencode we posted to this group, your problems will
>go away. 

I'll second this.  Tried everything to get 0.1 to boot off of the hard
drive, and then grabbed the patched dist.fs, and it now works fine.  
[[[ 386/25, AMI Bios, IDE with 525M Fuji ]]]

On another note, anyone have a kernel with an ethernet driver for 
an 3COM 3c501?  Anyone working on one?  

By the way, 386BSD looks better and better and better the more I play
with it.  

Thanks,
JHH

--
Jim Hudgens 			Supercomputer Computations Research Institute
hudgens@sun13.scri.fsu.edu      

Newsgroups: comp.unix.bsd
From: tholo@amanda.bbb.no (Thorsten Lockert)
Subject: Primary and secondary boot blocks for AHA154xA needed
Summary: Have proper kernel; managed to erase primary & secondary boot blocks
Keywords: AHA1540A AHA1542A SCSI boot Adaptec primary secondary
Organization: Bergen By Byte A/S
Date: Tue, 28 Jul 1992 20:53:39 GMT

I managed to retrieve a dist.fs patched to work properly with an Adaptec
1542A from ftp.uu.net and installed the system using that.  I also got the
patched isa/as.c driver, so that I was able to recreate the kernel as needed.
However, I was not satisfied with the disk layout as created by install, and
make new boot floppies (dist.fs and fixit.fs) with my recompiled kernel that
were able to use the AHA154xA...

However, I had not gotten a  new verion of stand/as.c and stand/asbootblk.c,
so as of now I'm able to install to my harddisk, but not to boot from it.

Are there anyone out there that could supply me with uuencoded versions of
/usr/mdec/asboot and /usr/mdec/bootas patched to work with the 154xA?  And
preferrably also the stand/as.c and stand/asbootblk.c files?

Thanks in advance,
-- 
Thorsten Lockert       |  postmaster@bbb.no  |
Ibsensgate 122         |  hostmaster@bbb.no  |  Universe, n.:
N-5037 Solheimsviken   |  tholo@bbb.no       |          The problem.
Norway                 |                     |