HDTenEightyP/NetNews huggingface dataset:
From: turtle@newshub.sdsu.edu (Andrew Scherpbier)
Subject: Re: To make 386bsd coexist with DOS partitions??
Organization: San Diego State University, College of Sciences
Date: Wed, 8 Apr 1992 14:26:45 GMT

michael@resonex.com (Michael Bryan) writes:
: In article <1992Apr7.053441.344@msus1.msus.edu> l00017@eeyore.stcloud.msus.edu (Networking Research) writes:
: >	I like the way that Mach 2.6 deals with this on the 386.  You have
: >only one Mach partition in the DOS partition table, but within that partition
: >you have a standard BSD style disklabel with it's own partition table.
: 
: This would be my preference.  This would allow, for instance, the creation
: of a small DOS partition, and a large BSD partition (say 95% of a disk?),
: so that you could boot either one by using an fdisk-like utility to change
: which partition was active (bootable).  This large BSD psuedo-disk could
: then be split into standard BSD partitions.

I like this as well, however, this fdisk idea is sort of dumb.  Why not change the
boot loader to behave similar to the one for SCO Xenix?  It provides a boot prompt
at which point one can decide from which partition to boot, but also from which kernel.
I do a lot of kernel hacking and I have to boot off floppy quite often because I
screwed up /386bsd and I can't seem to boot from /386bsd.old (eventhough the bootfd
source claims you should be able to...)
This boot loader would then have a timeout and a default way of booting so that it will
boot correctly after a power failure (heaven forbid!!!) or panic (never!!!) when
nobody is around to manually boot it.

I have been looking at the xxboot and bootxx code to see how easy/hard this would be,
but right now I am working on a new console driver.  So if someone else wants to take
on the task of writing a new boot loader, we should exchange some ideas.

____________________________________________________________________________
Andrew "Race Turtle" Scherpbier, SysMgr
College of Sciences
San Diego State University
WORK: turtle@sciences.sdsu.edu
HOME: turtle@kiwi.sdsu.edu
From: andrew@rnivh.rni.sub.org (Andrew Wheadon)
Newsgroups: comp.unix.bsd
Subject: toupper/tolower in libc.a and shell prb.
Keywords: toupper libc.a shell
Date: 13 Apr 92 10:09:22 GMT
Organization: Rhein-Neckar-Informationsdienst Viernheim

I think toupper/tolower should be made posix compliant.
ie they should islower the char first before making it
smaller. Lots of programs seem to know that BSD doesn't
do this, but they expect macros and no funktions in libc.a
because they normally undef the macros and use their own
functions.

I have a problem with the 386bsd shell:
  
LIST="HI HOW ARE YOU"
HI="hello joe"
HOW="have not"
YOU="seen you for quite some time"

I now want to do something like:
for v in $LIST
do echo "$v=$$v"
done

ie. I want the variables listed in LIST to be listed with their
values. This used to work on normal bourne shells but it doesn't
work with 386bsd-sh nor does it work with bash.

Seeya. Andrew
Newsgroups: comp.unix.bsd
From: cpetterb@javelin.sim.es.com (Cary Petterborg)
Subject: Re: BSD names (was: BSD on floppies)
Organization: Evans & Sutherland Computer Corp.
	<1992Apr5.173902.23415@zip.eecs.umich.edu>
	<1992Apr8.110359.10948@pegasus.com>
Date: Wed, 8 Apr 1992 22:28:58 GMT

In article <1992Apr8.110359.10948@pegasus.com> richard@pegasus.com (Richard Foulk) writes:

>   >
>   >BSDJ seems to be the natural choice as many people have independently
>   >suggested it.  I haven't seen anyone confuse BSDI and BSDJ, but several 
>   >people have "mixed up" 386BSD and BSD386. 
>   >
>
>   They both seem equally funky ... and confusion prone.
>
>   Besides, the I J sillyness makes it seem like BSD386 came before 386BSD ...

Just keep BSD/386 as it is since it is actually a trademarked name.

Then,...

What about FreeB (pronounced like Freebie) for Free Berkeley Unix for the
386BSD version?  Of course, there will be those that will shoot it down,...

I have heard worse names for things, and it speaks a lot faster that
386BSD.  GNU is using HURD as the name for it's OS and that is alot
easier to speak than GNU's OS.  So why not make it that simple as well?

I've also made the suggestion that FSF should stand for "Foundation for
Software Freedom" because of the confusion about the meaning of "free",
but that's gone nowhere as well.  ;-)

I kind of liked the "Jolix" name, because it is rather descriptive and
unique, but then it is also throwing it in with all the other *ix
named products, which could cause confusion as well.  Nothing is easy,
is it?

Cary
--
_______________
Cary Petterborg					   (801)582-5847 x6627
Evans & Sutherland Computer Corp.  Simulation Division   SLC, UT 84108
UUCP: ...!uunet!sim.es.com!cpetterb  *NET: cpetterb@javelin.sim.es.com
_______________
Not everything that counts can be counted.  Not everything that can be
counted counts.   - Charles Garfield
From: paradis@sousa.ltn.dec.com (Jim Paradis)
Newsgroups: comp.unix.bsd
Subject: 386BSD - I solved my boot problem
Date: 6 Apr 92 16:20:53 GMT
Organization: Digital Equipment Corporation, Littleton, MA

Just a data point for those of you having trouble booting 386BSD... I've
been waiting patiently for "real" 0.1 to appear so I could bring it over
to my PC and try it.  Earlier versions were all failing with the "hang at
pc<color>" problem.  Well, in preparation for getting 386BSD I recently
acquired a 500Mb ESDI drive and an ESDI controller.  After getting the
works up and running under DOS yesterday, I decided on a lark to try the
3/17 boot disk.  It booted!  Got to the single-user prompt, tried out a
few commands, and it works like a charm!

Today I'll bring over the rest and backup my DOS stuff and see how it
works... but in any case switching the hard disk controller may help.
(It may be of interest to note that my current HD controller had problems
at bus speeds > 10MHz.  I run my current bus at 8MHz and it works, but
my boot problems might've been due to marginal timings on the controller...)


-- 
Jim Paradis (paradis@tallis.enet.dec.com) 
Can you see the world in a grain of sand?  
If so, what are surreal estate prices like down there?
Newsgroups: comp.unix.bsd
From: dmuntz@dip.eecs.umich.edu (Daniel A Muntz)
Subject: Re: BSD names (was: BSD on floppies)
Organization: University of Michigan EECS Dept., Ann Arbor
Date: Sun, 5 Apr 1992 17:39:02 GMT

In article <24838.9204051603@thor.cf.ac.uk> spedpr@thor (Paul Richards) writes:
>I don't think BSDI and BSDJ are very good choices. If you think there's
>a tendency to mix up 386BSD and BSD386 then what do you think will
>happen when the names only differ by the last digit and they're
>consecutive letters of the alphabet.

BSDJ seems to be the natural choice as many people have independently
suggested it.  I haven't seen anyone confuse BSDI and BSDJ, but several 
people have "mixed up" 386BSD and BSD386. 

  -Dan
From: bmt3832@cs.rit.edu (Brendan M Tuck)
Newsgroups: comp.unix.bsd
Subject: Problems on install of 386BSD
Date: 16 Apr 92 00:10:49 GMT
Organization: Rochester Institute of Technology, Rochester, NY

I am having a problem installing 386BSD.
I have heard of the "color-then-hang" problem but
have not heard much about what causes it.  Currently, my
system initialises, finds out hardware addresses and system
interupts for various cards, tries to change control to
the disk drive and then hangs.  The only keys that work
afterwards are my ctr-alt-del, numlock, and function keys
6-8 (each of which adds some form of alpha-numerical list
to the screen).

My system consists of a i386/i387 25Mhrz combination,
Chips support chipset, Quantum 80MB IDE hard disk, AMI BIOS,
Teac 1.2 and 1.44 disk dirves, noname SVGA board, and 4MB RAM.

IF anyoune could give me any information on how to get past
this bug, I would be grateful for it.

Thanks,

Brenden.
From: mmitchel@digi.lonestar.org (Mitch Mitchell)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD 0.1 boot block mods.
Keywords: 386BSD wdbootblk.c
Date: 15 Apr 92 01:14:40 GMT
Organization: DSC Communications Corporation

After exchanging mail with several people about the change to the boot block,
Karl Lehenbauer (karl@sugar.NeoSoft.com) suggested that I post some additional
information about installing the rebuilt boot block.

Taken from my note to Karl:

  Note: when I rebuilt wdboot, it came out longer that 512 bytes because
  of some symbol info left after "strip" ran.  I used the supplied
  Makefile so I don't know what went wrong.  Anyway, I just copied
  trimhd.c to trimtl.c and rewrote it to copy the first 512 bytes of stdin
  to stdout, setting the last word to 0xaa55 for the BIOS ROM signature.
  
  I placed my new copy in /usr/mdec/wdboot.new on my boot floppy.
  So my disklabel command was:

  disklabel -w -r wd0 qp3200 virago /usr/mdec/wdboot.new /usr/mdec/bootwd

  "virago" is the optional packid, and "/usr/mdec/bootwd" will be found
  implicitly if ommitted.  "qp3200" is the entry I made in /etc/disktab.

-- Mitch Mitchell

-- 
* {letni | egsner | mic | supernet}!harlie!mitch     Mitch Mitchell      *
* {uunet | texsun | sulaco}!digi!mmitchel      Voice Mail (214) 519-3257 *
* mmitchel@digi.lonestar.org                     FidoNet: 1:124/4115.224 *
Newsgroups: comp.unix.bsd
From: brian@apt.bungi.com (Brian Litzinger)
Subject: Re: uugetty in BSD?
Organization: NoOrg
Date: Thu, 16 Apr 1992 20:34:03 GMT

In article <1992Apr15.220045.1477@pony.Ingres.COM> thomasm@Ingres.COM () writes:
>Has anyone come up with anything that resembles the AT&T uugetty for BSD?
>I've picked up the enable/disable [port] source from the comp.sources.unix
>archives and this is very useful but still not quite as good as uugetty -
>which respects the uucp locking convention (LCK..com1).
>
>Thanks in advance!

I believe agetty available from ftp.uu.net will work as uugetty.  It's
been compiled under SunOS, however, I haven't tried it on a real BSD
system.

brian@apt.bungi.com
From: jblst5@icarus.lis.pitt.edu (Jan B Larsen)
Newsgroups: comp.unix.bsd
Subject: od.c
Date: 9 Apr 92 23:59:42 GMT
Reply-To: jblst5@icarus.lis.pitt.edu
Organization: University of Pittsburgh


Isn`t od.c included in 386BSD? I searched through the filelist in the tar-file 
floppy.1, but couldn't find it.

- Jan
From: paradis@sousa.ltn.dec.com (Jim Paradis)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD - I solved my boot problem
Date: 7 Apr 92 03:45:54 GMT
Organization: Digital Equipment Corporation, Littleton, MA

james@raid.dell.com (James Van Artsdalen) writes:
: > (It may be of interest to note that my current HD controller had problems
: > at bus speeds > 10MHz.  I run my current bus at 8MHz and it works, but
: > my boot problems might've been due to marginal timings on the controller...)
: 
: I *strongly* encourage people not to change the ISA bus clock away
: from 8 MHz (or 6 MHz).  Very few peripherals actually work that fast.

Yeah... the reason I discovered that my HD controller was marginal was
way back a few years ago when I'd first upgraded my system from an
8MHz 8088 motherboard to a 12MHz 80286.  The 286 motherboard tied the
bus speed to the system clock, so when I tried to actually *run* it
at 12MHz all hell broke loose.  Running it in 6MHz non-turbo mode
fixed that problem, but I'd paid *extra* for that speed 8-)  Finally
I found that the motherboard had a (badly documented) 10MHz setting.
Strapping it for that got me the best of both worlds 8-)

(My current 386-33 has a separate bus clock, settable for 8 and 12 MHz.
I run the bus at 8 to be on the safe side...)

-- 
Jim Paradis (paradis@tallis.enet.dec.com) 
Can you see the world in a grain of sand?  
If so, what are surreal estate prices like down there?
From: mm@mentor.cc.purdue.edu (Mike MacKenzie)
Newsgroups: comp.unix.bsd
Subject: Re: mounting fd0
Summary: Copy the original boot floppy
Date: 14 Apr 92 00:14:28 GMT
Organization: Purdue University

In article <1992Apr13.210901.2384@uwm.edu>, knie2586@csd4.csd.uwm.edu (Robert Joseph Knier) writes:
> 
> 	How do you mount the floppy drive? - I would like to backup some of
> the new diffs and utils.  From what I could gander, one would use the 
> 'disklabel -r -w fd0 floppy5' command (5 1/4 drive) then a 'newfs fd0b'.
> This doesn't seem to work though.  Any suggestions?  Thanks in advance!
> 
> 

We also were not able to disklabel a floppy.  So what we did was:

cat /dev/fd0a > /tmp/floppy

Insert fresh MSDOS formatted 3 1/2 HD floppy then,

cat /tmp/floppy > /dev/fd0a

Since then, someone posted that there is a bug in disklabel that makes it
fail if there is no partition h.  I haven't tried adding an h partition
to the entry in /etc/disktab yet.

Our 5 1/4 driver didn't seem to work at all, however if it was the
boot device, I suspect it will work for you.

Michael MacKenzie	(Purdue University Unix Group)
mm@mentor.cc.purdue.edu
From: cproto@marsh.cs.curtin.edu.au (Computer Protocol)
Subject: parallel port device driver/physio problem
Summary: parallel port device driver - physio problem
Keywords: parallel port physio
Organization: Curtin University of Technology
Date: Thu, 9 Apr 1992 01:39:04 GMT

I was writing a parallel port device driver to be able to print
something. I used existing documentation for bsd 4.3 to write the
stuff. I discovered that physio has been changed. It now has a
different argument list as well as a somewhat different functionality.


Looking at the provided device drivers I discovered that none of
them is actually using physio. They all did use it in the original
NET-2 release!

Any ideas why ???
I understand that physio had to be rewritten because it was AT&T code.
But why was the interface changed ???

Once I sorted out all the problems with my driver, I will post it.
If someone else has got a parallel port driver working already let me know.

Regards -- Tibor Sashegyi
From: brown@vidiot.UUCP (Vidiot)
Newsgroups: comp.unix.bsd
Subject: Re: Which UNIX to buy for the PC
Keywords: n
Date: 15 Apr 92 21:06:00 GMT
Article-I.D.: vidiot.3252
Reply-To: brown@vidiot.UUCP (Vidiot)
Organization: Vidiot's Hangout

In article <1992Apr12.205354.24877@colorado.edu> ramzi@tigger.Colorado.EDU (Ramzi Al-Majid) writes:
<
<
<
<i need recommendation on which unix to buy for a 486-50 pc. 
<which unix has more software support? which has best features implemented?

You may wanna wait until Solaris 2.0 arrives, sometime soon.
-- 
      harvard\     att!nicmad\          spool.cs.wisc.edu!astroatc!vidiot!brown
Vidiot  ucbvax!uwvax..........!astroatc!vidiot!brown
      rutgers/            INTERNET:vidiot!brown%astroatc.UUCP@spool.cs.wisc.edu
                                   brown@wi.extrel.com
Newsgroups: comp.unix.bsd
From: karl@NeoSoft.com (Karl Lehenbauer)
Subject: Re: Missing Includes in 386BSD
Organization: NeoSoft Communications Services -- (713) 684-5900
Distribution: usa
Date: Fri, 17 Apr 1992 02:22:57 GMT

In article <195@bsts00.UUCP> gatech!sbmsg1!bsts00!rlb writes:
>Ther are several missing include files in the 386BSD floppy distb. Where 
>can I find them? One I am especially interested in is 
>/usr/src/sys.386bsd/i386/isa/wtreg.h
>
>Can someone tell me what ftp site has the complete include file set for 386BSD
>please.

The Net-2 release is available, unpacked, from ftp.uu.net.

wtreg.h, for example, can be found there in /packages/bsd-sources/sys/i386/isa
-- 
-- Email info@NeoSoft.com for info on getting Internet access.
     "Trust me.  I know what I'm doing." -- Sledge Hammer
From: mlanett@void.ncsa.uiuc.edu (Mark Lanett)
Newsgroups: comp.unix.bsd
Subject: Re: To make 386bsd coexist with DOS partitions??
Date: 8 Apr 92 15:08:18 GMT
Article-I.D.: ux1.1992Apr8.150818.11729
Organization: University of Illinois at Urbana

turtle@newshub.sdsu.edu (Andrew Scherpbier) writes:

>I like this as well, however, this fdisk idea is sort of dumb.  Why not change the
>boot loader to behave similar to the one for SCO Xenix?  It provides a boot prompt
>at which point one can decide from which partition to boot, but also from which kernel.
>I do a lot of kernel hacking and I have to boot off floppy quite often because I
>screwed up /386bsd and I can't seem to boot from /386bsd.old (eventhough the bootfd
>source claims you should be able to...)
>This boot loader would then have a timeout and a default way of booting so that it will
>boot correctly after a power failure (heaven forbid!!!) or panic (never!!!) when
>nobody is around to manually boot it.

An RT running AOS does all that, and I don't even need it because I'm not hacking the
kernal. Maybe soon, though...
-- 
Mark Lanett, Software Tools Group, NCSA           mlanett@uiuc.edu or  NCSA.STG
"People wander in and out of virtual rooms in virtual settings with virtual
characters and virtual money and virtual armor and virtual weapons, which is
virtually a good way to spend time, but not quite." -- Usenet Oracle
-- 
Mark Lanett, Software Tools Group, NCSA           mlanett@uiuc.edu or  NCSA.STG
"People wander in and out of virtual rooms in virtual settings with virtual
characters and virtual money and virtual armor and virtual weapons, which is
virtually a good way to spend time, but not quite." -- Usenet Oracle
Newsgroups: comp.unix.bsd
From: peter@ferranti.com (Peter da Silva)
Subject: Re: BSD names (was: BSD on floppies)
Organization: Xenix Support, FICC
Date: Sat, 11 Apr 1992 19:53:40 GMT

In article <CPETTERB.92Apr8152859@mickey.javelin.sim.es.com> cpetterb@javelin.sim.es.com (Cary Petterborg) writes:
> What about FreeB (pronounced like Freebie) for Free Berkeley Unix for the
> 386BSD version?  Of course, there will be those that will shoot it down,...

How about "FreeSD", pronounced like "BSD". This version would be "386 FreeSD".
-- 
/F{findfont exch scalefont setfont}def /S{moveto show}def /T{/Times-Roman F}def
8 T(Ferranti International Controls Corporation)24 28 S(+1 713 274 5180)24 12 S
(Sugar Land, TX  77487-5012)24 20 S 12 /Courier F(`-_-')320 32 S( 'U` )320 16 S
12 T(Peter da Silva)24 36 S 16 T(Have you hugged your wolf today?)358 24 S
From: system@asuvax.eas.asu.edu (Marc Lesure)
Newsgroups: comp.unix.bsd
Subject: Info needed on 4.4bsd
Date: 16 Apr 92 21:41:09 GMT
Organization: Arizona State University, Tempe, AZ

I need to plan for my next fiscal budget and need to get some info ASAP.
Does anyone know when 4.4bsd will be released (approx. time is fine).  Also,
anyone know the cost that will be involved.

Thanks-

-----------------------------------------------------------------------
Marc Lesure / Arizona State University / Tempe, AZ
"Between the world of men and make-believe, I can be found..."
"False faces and meaningless chases, I travel alone..."
"And where do you go when you come to the end of your dream?"

UUCP:       ...!ncar!noao!asuvax!lesure  
Internet:   lesure@asuvax.eas.asu.edu
From: garlangr@en.ecn.purdue.edu (Mark T Garlanger)
Newsgroups: comp.unix.bsd
Subject: Status of next release??
Date: 15 Apr 92 18:20:27 GMT
Organization: Purdue University Engineering Computer Network

It's been almost a month since the last release. Has anyone heard when the
next version is going to be released?  Any ideas whether or not it will
support partitions? (After trying to install the current version, I had
to do a low-level format to get rid of the 386bsd residue that prevented
me from booting Dos).  I don't mean to sound ungrateful or demanding, I just
was hoping like to get a functional version before school's out in 2 weeks.  
Any "insiders" know the status??


				Thanks,
				  Mark

-- 
/---------------------------\
|Mark Garlanger             |
|garlangr@en.ecn.purdue.edu |
\---------------------------/
From: hm@hcshh.hcs.de (Hellmuth Michaelis)
Newsgroups: comp.unix.bsd
Subject: Re: SCSI boot for 386BSD
Date: 17 Apr 92 13:36:51 GMT
Organization: HCS GmbH, Hamburg, Europe

In <PACE.92Apr11115211@blitz.com> pace@blitz.com (Pace Willisson) writes:

>I just posted the sources for my scsi boot programs to alt.sources
>with the subject "SCSI boot for 386BSD".  (I would have put them here,
>but someone complained the last time I posted a source file to this
>group.)

has someone gotten this to run with 0.0new ? pace's environment seems to be
pretty different (no conf.c in /sys/i386/stand).

also a io structure member i_buf is referenced in the code, how must one 
handle that ?

at last, i can disklabel & newfs the drive, but when booting from it, the
bios recognize the boot code on the scsi drive, but then the system hangs.

has anyone any hints ?

hellmuth
-- 
hellmuth michaelis    HCS Hanseatischer Computerservice GmbH   hamburg, europe
hm@hcshh.hcs.de              tel: +49/40/55903-170         fax: +49/40/5591486
From: keithe@sail.LABS.TEK.COM (Keith Ericson)
Newsgroups: comp.unix.bsd
Subject: Re: Extended Tcl 6.2a for 386BSD is now available
Date: 7 Apr 92 00:17:40 GMT
Organization: Tektronix, Inc., Beaverton,  OR.

In article <1992Apr04.085120.26792@NeoSoft.com> karl@NeoSoft.com (Karl Lehenbauer) writes:
>I've uploaded the Extended Tcl programming language, hacked a bit to run
>under 386BSD, to
>
>    ferkel.ucsb.edu	/pub/incoming	(don't worry, it's world-readable)
>    kirk.bu.oz.au	/pub/386bsd/public-upload
>
>I've also sent it to agate, but agate's 386BSD archive doesn't seem to
>have been updated for a while.

It's not on ferkel (anymore).  Agate's incoming is unreadable.
Ftp'ing to the US from Australia isn't too cool (it's almost a megabyte).
But you can find the full name of the file on kirk, and see if it's in
agate: and it is, in their incoming subdirectory:

	tcl6.2-386bsd.tar.Z

so you can get it even though the obviously over-busy folks at agate
haven't been able to put it wherever it belongs yet.

(help *) KEITHE()
Keith Ericson @ TekLabs
keithe@sail.labs.tek.com
Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: Re: List of known partition IDs
Organization: TRW Financial Systems
Distribution: comp
Date: Wed, 8 Apr 1992 20:23:49 GMT


To add to the list MACH uses 99 (0x63).

julian

We are running the MACH disk drivers in the net2 release.
They work fine after a little cleanup. (the scsi driver anyhow)
the MACH disk format with the DOS compatible feature mentioned earlier
works well.

The utilities SHOULD work directly under net2 as they ar just BSD4.3
and do nothing really fancy, just ioctls

basically there is one program called diskutil
which has 4 names

diskutil, fdisk,vtoc and badblock.

it sets up all the badblock tables and partition tables.

as the previous writer said,
they have a dos compatible partition
which they then divide up into unix partitions

I think all the stuff to do it is under CMU license and 
should therefor be available.

julian
From: eddy@aludra.usc.edu (George Edmond Eddy)
Newsgroups: comp.unix.bsd
Subject: kernel panic when doing a make depend
Date: 14 Apr 1992 19:18:13 -0700
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: aludra.usc.edu


Good News!  finally got 386BSD running after a *few* minor problems!

Bad News :( ... keep getting kernel panics when doing a "make depend"
while trying to build a kernel.  I get basically the following messages:

	vm_fault(...) -> 1
	  type c, code 2
	trap type 12 code = 2 ...
	panic: trap 
	syncing disks...

	dumping to dev 1, offset
	dump........

anyone had this problem and know how to fix it/get around it?

Thanx in advance,

- rusty

eddy@usc.edu