HDTenEightyP/NetNews huggingface dataset:
From: sitongia@ozzel.hao.ucar.edu (HAO Computer System Managment Group)
Subject: SUMMARY: [386bsd] tape drives
Keywords: 386bsd tape drives SCSI
Reply-To: sitongia@ozzel.hao.ucar.edu (HAO Computer System Managment Group)
Organization: High Altitude Observatory/NCAR, Boulder CO
Distribution: usa
Date: Sun, 20 Dec 1992 04:10:02 GMT

Here is a summary of the responses I received regarding by request for
what tape drives people are using in their 386bsd systems.  A good list of
SCSI tape drives is part of the hardware list that has been posted to this
group before.

------------------------------

From meidinge@ps2zenger1.informatik.tu-muenchen.de (Thomas Meidinger)
I am using a Tandberg TDC 3660 and I am pretty happy with it.
BTW: The TDC 3660 is a QIC-150 tape drive.

From: conklin@talisman.kaleida.com (J.T. Conklin)
I'm using a SCSI WangDAT 3200.

From: ejh@slustl.slu.edu (Eric J. Haug)
i would suppose that most sensible SCSI tape drives would work.
I have an archive 2150 that works well with both the driver
in the distribution kernel and julians' SCSI drivers.
eric

From: ejh@slustl.slu.edu (Eric J. Haug)
Yes, Archive is a brand name, it formerly was a company.
I believe the company was purchased by another company
named Maynard.
eric

From: berry@max.IN-Berlin.DE (Stefan Behrens)
I use a Wantek 5150ES SCSI tape drive on an Adaptec 1542B.
It streams constantly and works without any errors.

My system:
No name i386/i387 33 Mhz AT clone with 177MB and 245MB IDE drive.
The tape drive is the only device on the SCSI bus.

Usually I use the tape drive in single user mode with dump(8) and
restore(8). Dumping it streams for at least 10 minutes without a break even
for the partitions I spool News and keep my comp.unix.bsd archive (~12 MB
since september).
My cartriges are all 250MB ones and I checked the correct writing alot, no
errors yet.
--
--Leonard E. Sitongia           HAO System Manager                 
sitongia@ncar.ucar.edu          voice: (303)497-1509   fax: (303)497-1589
High Altitude Observatory       P.O. Box 3000 Boulder CO  80307
From: ujlh@pool.info.sunyit.edu (James Henrickson)
Subject: Re: 386BSD INGRES ???
Keywords: x
Organization: State University of New York -- Institute of Technology
Date: Sat, 19 Dec 1992 05:37:44 GMT

In article <1gorf6INN8ls@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
>I read somewhere recently that INGRES was available on 386BSD.  Where is it
>possible to acquire this package?  Does it seem pretty reliable?  Would the
>sources possibly compile without problems under SCO UNIX 3.2r2.0 ODT 1.1 ??

I have some additional questions about the 386BSD version.

1. Is there an FAQ for it?

2. What are the disk space and memory requirements for building it?

3. Is it available in binary form?

4. What are the disk space requirements for the binaries?

Thanks in advance,

-- 
Jim H.
*
* James L. Henrickson  |  "I don't need a signature, I need a job!"
* ujlh@sunyit.edu      |  BSCS, December 1992
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] need motif
Keywords: motif 386bsd
Date: 19 Dec 92 06:13:31 GMT
Organization: Amdahl Corporation

The PD Motif mentioned here earlier (I think it was referred to as mxmf or
similar), seems to be just a Motif application - a file manager program.
At least what I found using archie was not a PD version of Motif itself.

Please tell me I wrong!

-- 
Gary Browning        | Exhilaration is that feeling you get just after a
		     | great idea hits you, and just before you realize
                     | what is wrong with it.
From: andrick@sun.rhrk.uni-kl.de (Ulf Andrick [Biologie])
Newsgroups: comp.unix.bsd
Subject: [386bsd] pcnfsd?
Date: 14 Dec 92 18:14:08 GMT
Organization: University of Kaiserslautern, Germany
X-Newsreader: Tin 1.1 PL4

I'd like to access a 386bsd machine with a pcnfs client, but there are problems
with the authentication. Has anyone ported pcnfsd to 386bsd?

--
Ulf R. Andrick                                andrick@rhrk.uni-kl.de
FB Biologie - Tierphysiologie
Universitaet                             Was du nicht selber weiszt, 
D-W 6750 Kaiserslautern       das muszt du dir erklaeren (Tegtmeier)
Xref: sparky comp.unix.bsd:10357 comp.os.linux:20931
From: veit@du9ds3.fb9dv.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd,comp.os.linux
Subject: Re: INTERNATIONALIZATION: JAPAN, FAR EAST
Date: 18 Dec 92 08:06:40 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.fb9dv.uni-duisburg.de
NNTP-Posting-Host: du9ds3.fb9dv.uni-duisburg.de
Keywords: Han Kanji Katakana Hirugana ISO10646 Unicode Codepages

In <id.M2XV.VTA@ferranti.com> peter@ferranti.com (peter da silva) writes:

>In article <mathias.724467456@sune.stacken.kth.se> mathias@stacken.kth.se (Mathias Bage) writes:
>>   Has anyone in this newsgroup ever heard of the Unicode/ISO10646
>> (UCS) standard?

>You know, if 386BSD could be made to support NET-UTF (the Plan 9 version
>of the 10646 standard) that would be a major advantage over commercial
>Unices...

Please tell me where I can get a document describing NET-UTF, preferably
electronically.

>-- 
>Peter da Silva                                            `-_-'
>Ferranti International Controls Corporation                'U` 
>Sugar Land, TX  77487-5012 USA
>+1 713 274 5180                            "Zure otsoa besarkatu al duzu gaur?"

Holger
-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.fb9dv.uni-duisburg.de
|__|  /  University of Duisburg  |
|  | /   Dept. of Electr. Eng.   |          "Understand me correctly:
|  |/    Inst. f. Dataprocessing |     I'm NOT the WIZARD OF OS" (Holger)
Newsgroups: comp.unix.bsd
From: g88d4938@alpha.ru.ac.za (Gregory Doyle)
Subject: NFS bsd
Keywords: bsd, nfs
Organization: Rhodes University, Grahamstown, South Africa
Distribution: ?
Date: Thu, 17 Dec 1992 09:49:13 GMT


Hi all
I am new to this group so if this a frequently asked one join the club who thinks most of a my brain cells are on a permanent holiday.
I've got bsd installed on a 386 with 150 MB SCSI. We have a file server
which already got everything on it. What I want to do it to call as much
of the stuff needed of the server. Stuff that if not there will still allow
me to do some work on the machine. 
So far I've got X sitting on it (yeah, some may disagree on how vital it is
to not have it on the server) and everything under /usr/share.
Even if the server is down I (which happens seldom) I can still boot up
and do some work.
Question: What else can I put on the server - so far I am using about 23 MB
           of stuff local and want to reduce it below 20 MB.
           Any suggestions?

 Any suggestions/help will be much appreciated.
 
 Thanx
  Greg
--
G.E. Doyle - email = g88d4938@alpha.ru.ac.za or g88d4938giraffe.ru.ac.za 
Disclaimer: Views of above person is  |   
            strictly his own. (Can be |   "The SUNs never sets at Rhodes"
            bought at $0.01 each).    |
From: kaleb@jpl-devvax.jpl.nasa.gov (Kaleb Keithley)
Newsgroups: comp.unix.bsd
Subject: Re: Choosing DOS or BSD at boot time?
Keywords: BSD,  DOS
Date: 15 Dec 92 17:09:12 GMT
Organization: Jet Propulsion Laboratory (NASA)

In article <ali.724425416@barney> ali@cs.city.ac.uk ( Ali Syed) writes:
>I've MSDOS-5 and BSD Installed on my Hard-disc, the first 120MB for BSD and 
>remaining 80MB for DOS.  When I switch the PC on, the BSD boots ok. However, 
>if I want to switch to DOS, the 'shutdown -todos' fails. I've tried using 
>the 'OS-BS' program,  but that doesn't work either - choosing  DOS is ok, but
>loops if I choose BSD.
>
>Any suggestions as to how I can easily choose either DOS or BSD at boot time?
>

I would like to to take this opportunity, as 386BSD moves toward 0.2, to 
lobby for a change in the 386BSD bootstrap loading process.  

Every commercial version of U*IX manages to live within the constraints of 
the "default" Master Boot Record, e.g. SVRx/386 has a "boot partition" which
contains an intermediate boot record with the logic to allow for selecting
a kernel file to execute.

I run OS/2 HPFS, (MS-DOS? Just say no!), therefore 'shutdown -todos' doesn't
work.  (Yes, I *could* "fix" shutdown, but...)  I can't use the OS/2 boot 
manager, which wants its own partition to be bootable, and it handles the 
rest; but because 386BSD doesn't conform to the convention, it can't boot 
386BSD.  I suspect users of other boot managers are suffering the same 
problem.

I like 386BSD despite this shortcoming; but I'd really like to get rid of
the @#$%^& DOS floppy I have to keep around just so that I can switch 
between OS/2 and 386BSD....

-- 

Kaleb Keithley                               kaleb@jpl-devvax.jpl.nasa.gov
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: Dumb Question: Why 512 byte block?
Date: 19 Dec 92 15:31:19
Organization: Kernel Hackers 'r' Us
	<1992Dec18.235623.27538@fcom.cc.utah.edu> <1gvv8gINN80e@menudo.uh.edu>
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: wjin@cs.uh.edu's message of 19 Dec 1992 20:04:32 GMT

In article <1gvv8gINN80e@menudo.uh.edu> wjin@cs.uh.edu (W. Woody Jin) writes:
>BTW, could anyone clarify whether 386BSD uses the Fast Unix File System
>which is described in "A Fast File System For Unix" by McKusick, Joy, Leffler,
>and Fabry (1984 ACM Tran. on Computer System) ?

yes, it does.  this is the stuff you see in /sys/ufs (but excluding
/sys/ufs/mfs* -- the _old_ mfs (memory filesystem) stuff)...

random fun:  the mfs in 386bsd cares about disk layout...  <chuckle>

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

"Sometimes it is better to have twenty million instructions by
        Friday than twenty million instructions per second." -- Wes Clark
Newsgroups: comp.unix.bsd
From: kaleb@swat (Kaleb Keithley)
Subject: Re: [386bsd] need motif
Keywords: motif 386bsd
Organization: Jet Propulsion Laboratory (NASA)
Date: Fri, 18 Dec 1992 22:38:49 GMT

In article mattb@sdd.hp.com (Matt Bonner) writes:
>In article tjon@plains.NoDak.edu (Christopher C. Tjon) writes:
>|> 
>|> BTW, If there is enough interest I could begin to maintain an archive here
>|> on plains.nodak.edu.  I am sure that this package will need some porting
>|> to 386bsd.  I was planning to do it over the holidays.  Feed back is 
>|> welcome
>|> 
>
>Well, I stand corrected, I guess there is a version of Motif available,
>although 1.1.2 is fairly old at this point.  I think 1.2.1 came out
>recently or will be out soon.  Unfortunately, the licensing got much
>steeper as of 1.2.  Which leads to my feedback.
>
>I would be quite interested in a PD version of Motif, but I'm also 
>curious what version of Motif they are claiming compliance with.
>Both the documentation and the functionality of the code have
>changed and continue to change.  Not to mention the correctness of
>OSF/Motif...

Chris,
I'm curious to know just what you intend to keep in this archive?  Motif
is proprietary, and if you talk to the OSF people at the various X get-
togethers like Xhibition, X Technical Conference, etc. they'll tell you 
just how vigorously they go after people who put Motif (libraries, program 
files, source, etc.) onto anonymous ftp sites.

Matt,
It's possible to get a "Full Distribution" license for 1.0.x and 1.1.x
for $1000.  The "Full Distribution" license is the magic key to selling
Motif libraries and programs.  A "Full Distribution" license for 1.2.x
however is $15,000.

I'm not sure what you're asking/saying about in terms of "version 
compliance".  Delta bugs, all versions of Motif are compliant with whatever
specification exists.  But it's in pplications development where compliance,
in particular, compliance with the Style Guide becomes an issue.  It's 
possible to write non-compliant applications with any version of Motif.  
It's also possible to write compliant applications without the Motif Widget 
Set.

If you have more questions about what you can and cannot do with Motif,
I suggest that you contact OSF directly.  Their address, email and other-
wise, are in the comp.windows.x and comp.windows.x.motif FAQs.

I also once again humbly submit, that if you want the 3D look and and most 
of the feel of Motif, without the licensing hassles, try Xaw3d.  The current 
version is 0.5, and it's on export.lcs.mit.edu (18.24.0.12) in the file 
~/ftp/contrib/Xaw3d/R5/Xaw3d-0.5.tar.Z

-- 

Kaleb Keithley                               kaleb@jpl-devvax.jpl.nasa.gov

Newsgroups: comp.unix.bsd
From: serini@ghost.dsi.unimi.it (Piero Serini)
Subject: Re: More on pccons/XFree86 problems (keyboard hangs)
Keywords: 386BSD X11 XFree86 console pccons
Organization: Computer Science Dep. - Milan University
Date: Tue, 15 Dec 1992 00:39:44 GMT

More on this:

$ echo foo > /dev/console

hangs the keyboard. Obvioulsy, X is running.

Bye
Piero

------------------------------------------ Piero Serini -----------------
Piero Serini	                  E-mail: serini@ghost.dsi.unimi.it   
Computer Science Dept.            or: piero@strider.st.dsi.unimi.it
Univ. Statale - Milano - ITALY      ** mail me your .signature **
-------------------------------------------------------------------------
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: Occasional system hangs
Keywords: n
Date: 12 Dec 92 00:04:37 GMT
Organization: Amdahl Corporation

In article <1992Dec11.210430.17335@coe.montana.edu>,
osynw@gemini.oscs.montana.edu (Nate Williams) writes:
> In article <1gaclpINN84v@hrd769.brooks.af.mil>
> news@hrd769.brooks.af.mil (InterNet News) writes:
> >-Time for more RAM I guess!
> >>
> >
> >  I don't think more RAM will help.  I have 32M of RAM and and 32M
> swap 
> >partition.  It still hangs.  nroff is the usual culprit for me.
> 
> The fix for this is to fix G++, re-compile it, and then recompile
> groff
> with the fixed GCC.  The patch for g++ will be in the next patchkit.
> [If I ever get it finished :-(]

This might be a problem but are you sure it is not simply masking another?
A bum compile of a user level program should never cause the system to hang.

Shouldn't Andrew still be able to ping his system?
-- 
Gary Browning        | Exhilaration is that feeling you get just after a
		     | great idea hits you, and just before you realize
                     | what is wrong with it.
From: rjkm@ph-cip.uni-koeln.de (Ralph Metzler)
Newsgroups: comp.unix.bsd
Subject: Adaptec 1542b - bad dirs, panics
Date: 14 Dec 92 20:05:02 GMT
Distribution: comp
Organization: Institute of Theoretical Physics, University of Cologne, F. R.
	Germany
NNTP-Posting-Host: sun.ph-cip.uni-koeln.de

Hi 

I am having prolems with 386BSD on a Fujitsu 2266S-512 1GB SCSI-drive
with an adaptec 1542b-controller.
Installing and unpacking the bin01-distribution works fine. But after 
the first real shutdown and reboot the filesystem starts to 'fade away'.
I get 'bad dir'-messages and panics. 
After every reboot more and more directories disappear.

I used the distributed kernel without any patches and another one with
all patches from the patchkit, which works fine with two other computers
using IDE-drives. But both kernels lead to the same errors.


Any idea?
--

------------------------------------------------------------
Ralph Metzler                       rjkm@ph-cip.uni-koeln.de
============================================================
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Dumb Question: Why 512 byte block?
Organization: University of Utah Computer Center
Date: Sun, 20 Dec 92 03:13:24 GMT

In article <1gvv8gINN80e@menudo.uh.edu>, wjin@cs.uh.edu (W. Woody Jin) writes:
|> In article <1992Dec18.235623.27538@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
|> >
|> >You can't split blocks between files.  
|> 
|> Yes, you can.
|> For example, you may have 4K size block with 512 byte fragment size.

Mixed up blocks and frags in the context of the original post (re: the "df"
command).  You are, of course, right.

|> BTW, could anyone clarify whether 386BSD uses the Fast Unix File System
|> which is described in "A Fast File System For Unix" by McKusick, Joy,
|> Leffler, and Fabry (1984 ACM Tran. on Computer System) ?

Yes, it does.

...

My point was that disk allocation was quantized at larger than 1 byte
increments, and the larger those increments, the more space is actually
used by a 1 byte file.  My examples were correct for 4k blocks with 8
frags per block.

The summation of this being that upping the size of a block will up the
size of the _fragments_ of that block unless the number of fragments per
block is also increased (isn't 8 the limit?).  The problem here being,
the disk will disappear faster with 8k/8 block frags than it will with
4k/8 blocks frags because of the number of files whose lengths aren't on
block boundries.

A smaller absolute fragment size (however it is arrived at) will result in
less absolute disk real estate being take up for odd-sized files.

					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: bsellers@cabsparc.larc.nasa.gov (Bill A. Sellers)
Newsgroups: comp.unix.bsd
Subject: Compiled kernel available ftp for lp?
Date: 19 Dec 1992 01:48:06 GMT
Organization: NASA Langley Research Center, Hampton, VA  USA
Expires: 20days
NNTP-Posting-Host: cabsparc.larc.nasa.gov
Keywords: bsd unix lpt printer


Does anyone have a compiled kernel available for ftp access that 
supports the lpt.c patches?  I know that there are serveral people
that would want this, as not everyone has the know-how or the 
resources (diskspace, etc) to recompile the kernel.  Thanks
for your help!

Bill Sellers

bsellers@cabsparc.larc.nasa.gov
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: Dumb Question: Why 512 byte block?
Date: 17 Dec 92 19:58:55
Organization: Kernel Hackers 'r' Us
	<1992Dec18.030833.7395@fcom.cc.utah.edu>
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: terry@cs.weber.edu's message of Fri, 18 Dec 92 03:08:33 GMT

[terry's reasoning for the utilities reporting things in 512b blocks deleted]

Terry, your description is more or less accurate, but i think there's
a bit more behind it...

from the du(1) man page:
=>     -k      By default, du displays the number of blocks as returned by the
=>             stat(2) system call, i.e. 512-byte blocks.  If the -k flag is
=>             specified, the number displayed is the number of 1024-byte
=>             blocks.  Partial numbers of blocks are rounded up.

and from the stat(2) man page:
=>STANDARDS
=>    The stat() and fstat() function calls are expected to conform to IEEE Std
=>    1003.1-1988 (``POSIX'').


I believe you can blame this change on the POSIX people...
(I'm pretty sure that du w/.5k blocks is POSIX, as well...)


chris
--
Chris G. Demetriou                                    cgd@cs.berkeley.edu

"Sometimes it is better to have twenty million instructions by
        Friday than twenty million instructions per second." -- Wes Clark
Newsgroups: comp.unix.bsd
From: gtoal@robobar.co.uk (Graham Toal)
X-Mailer: Mail User's Shell (7.2.4 2/2/92)
Subject: [386bsd] Notice to 386bsd ftp maintainers, and ftpd author
Date: Thu, 17 Dec 1992 21:15:39 +0000


Thanks to pauls@umich, we now know the reason for occassional problems
with the new ftp server that allows you to fetch whole directories as
.tar files.  What happens is that if the tar finds an unreadable file,
it skips it and outputs an error message to the 'screen' - unfortunately
because of the way the job is piped into ftp this ends up in the tar
file which then fails to unpack properly.

The interim solution is to make sure all your files are permitted!
The long-term solution is to fix the ftpd code so that error messages
are directed somewhere else, and if possible reported to the ftp client.

Graham
Newsgroups: comp.unix.bsd
From: levinson@halcyon.com (Don Levinson)
Subject: [386bsd] drivers for DEC ethernet DEPCA,DE201,DE101
Organization: The 23:00 News and Mail Service
Distribution: comp.unix.bsd
Date: Sat, 19 Dec 1992 17:09:38 GMT

a while back I got the sources to  a DE200 driver from this newsgroup.
I was wondering if the individual who wrote this driver (sorry I forgot
your name) has updated this driver since then.

-- 
-------------------------------------------------------------------------------
 Don Levinson	  levinson@halcyon.com	| 	Fatigue Technology Inc.
 "Stupid answers for stupid questions"	| 	100 Andover Park West
    ph:206-246-2010 fax:206-244-9886	| 	Seattle, WA 98188
Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: Re: Easy way to create unix man pages?
Keywords: unix manual hypertext
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
Date: Fri, 18 Dec 1992 04:05:14 GMT

In article <1992Dec17.165257.9439@oakhill.sps.mot.com> wcl@oakhill.sps.mot.com (Wayne Long) writes:
>
>I'm looking for a filter, utility, or editor that
>will take normal, what-you-see-is-what-you get
>text, and convert it into a unix man page with
>minimal hassle.
>
>I realize that some of the major sections and headings
>would have to be delimeted in some way, but I'd like to
>be able to do this editing with a normal text editor
>(or framemaker or MacIntosh Word) in as minimally
>cryptic way as possible.

One route is GNU texinfo -> texi2roff. I think texi2roff is not
finished yet/ever.  It was  not part of texinfo, last I looked.

Probably easier is just using an existing troff document as skeleton.
-Andrew Moore <alm@netcom.com>
Newsgroups: comp.unix.bsd
From: ted@usasoc.soc.mil (Ted Nolan)
Subject: Gateway 2000 problems?
Organization: SRI International, Ft. Bragg NC
Distribution: usa
Date: Fri, 11 Dec 1992 21:57:21 GMT

Hello folks,

After getting some positive responses on the message I posted a few days ago
about "How useful is 386BSD?", I've about decided to go for it.  However,
one of the messages I got mentioned some problems with Gateway 2000 systems,
which is one of the choices I have been strongly considering for my home
computer.

We happened to have a Gateway 2000 486DX-33 sitting in our lab, so I took
the dist-fs floppy from the bootables directory and tried it out: no
dice.  I also tried the new dist-fs from the unofficial/terry/new-bootables
area on agate, but that didn't work either.  I think the floppy is OK, because
I have tried it on another system here and it booted fine.

Does this mean I have to stop considering Gateway, or does someone know what
the problem is (and have a fix!)?  Also, if so, does anyone know if xfree86
will work on the Gateway localbus VGA?


				Thanks,

				Ted Nolan
				ted@usasoc.soc.mil
Newsgroups: comp.unix.bsd