HDTenEightyP/NetNews huggingface dataset:
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:17:44 GMT
Distribution: usa
Organization: Amdahl Corporation

In article <1992Dec18.233644.22493@rwwa.COM>, witr@rwwa.COM (Robert
Withrow) writes:
> In article <1992Dec18.223849.18131@jpl-devvax.jpl.nasa.gov>,
>  kaleb@swat (Kaleb Keithley) writes:
> | 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.
> 
> On the other hand, an OSF person told me that if someone took the AES
> and programmed a motif look/work alike from it, they would/could do
> nothing.
> 
> (not that I completely believe this)

But it is an interesting idea.

> And as much as I like Xaw3d, Motif as more going for it than just shadows...
> like more widgets, and more powerfull widgets, and traversal, and...

Not to mention that it makes the porting of Motif based applications a whole
lot easier ;-).

-- 
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.
Newsgroups: comp.unix.bsd,comp.sys.3b1
From: frank@halcyon.com (Frank Higgins)
Subject: Re: Need help with AT&T UNIX PC and DOS
Organization: The 23:00 News and Mail Service
Date: Mon, 21 Dec 1992 02:37:09 GMT

In article <1h18ilINNs4i@usenet.INS.CWRU.Edu> ptd2@po.CWRU.Edu (Palmer T. Davis) writes:
>
>In a previous article, tsai@evax12.eng.fsu.edu () says:
>>
>>     We have several AT&T UNIX PCs (PC7300) in our lab.  They have been
>>rarely used.  Recently, the chairperson wants them to run DOS and DOS
>>applications such as MATLAB.  Is anyone familier with the way to make it
>>work ?  Any help or advice is greatly appreciated.
>
>(First of all, comp.unix.bsd is the wrong group for this question;
>it really belongs in comp.sys.3b1, to which I'm redirecting followups.)
>The 7300 and 3b1 are based on the 68010, not the 8086 family.  There
>is a coprocessor board that was available (called DOS-73); if you don't
>have this board installed, you simply can't run DOS at all.  With the
>coprocessor board installed, the machine works more or less like a
>512K IBM XT with a monochrome display adapter, but DOS software has to
>be reasonably well-behaved to work.  (And you can simultaneously run
>UNIX software in other windows, a feature notably lacking on most XT
>clones....)
>
>-- PTD --
><ptd2@po.cwru.edu>   \X/   cthread.  cthread_fork().  Fork, thread, fork!

Underline "reasonably well behaved". There are debates about how much DOS
software the DOS board will actually run, but at the time I paid full
price for one of the things in the heyday of the 3B1 (pre 286, 386, 486), I
determined that there was darned little *preferred* software that would run
on it. An AT&T tech and I finally put a number to it and said that it was
about 50% compatible with the then existing DOS software. Later software
has become more elaborate, sophisticated and less likely to run on the DOS
board. What it does, it does well. What it doesn't is horrid.

Frank        

-------------------------------------------------------------------------   
|   Voice: 206-774-0956                       Data: frank@halcyon.com   |
-------------------------------------------------------------------------
| I've learned that the most important piece of equipment in my office  |
| is the wastebasket.                                                   |
-------------------------------------------------------------------------
Xref: sparky comp.unix.bsd:10437 comp.os.linux:21104
From: news@hrd769.brooks.af.mil (InterNet News)
Newsgroups: comp.unix.bsd,comp.os.linux
Subject: Re: Dumb Americans (was INTERNATIONALIZATION: JAPAN, FAR EAST)
Date: 19 Dec 1992 12:33:04 -0600
Organization: Armstrong Lab MIS, Brooks AFB TX
NNTP-Posting-Host: hrd769.brooks.af.mil
Keywords: Han Kanji Katakana Hirugana ISO10646 Unicode Codepages

  Having been involved in one of these Internationalization projects, I feel
that, as a dumb American Engineer (automated control software engineer)
that I should be offended.  Strangely enough, I am not.  I had to retrofit
a LOT of our code to use whatever language indicator was in the language
register.  It wasn't designed to do that very well.

  I have also been an American in Europe.   I have seen Europeans make 
complete idiots of themselves travelling within Europe.  I have seen 
Japanese make fools of themselves in the States.  It happens everywhere.
Give it a rest.  We are all localized.  It is the nature of people all
over.  We act the way we are trained to act.

  Ignorance of local customs can make anyone look pretty dumb.  Continuing with
stereotypes should be criminal (like it already is in the U.S. Military).
If I offered up half of these 'truths' as fact, I would be hammered, as
well I should.

So, I have a suggestion.  Change someone.  If you think internationalization
is a snap, try it.  Get convinced that it is hard to retrofit, but relatively
simple to design for and proceed from there.  If you think it is hard, try
to plan for it early in one of your designs and see what happens.  It could
be that you will also find that it is practically automatic, once you decide
how YOU want to do it (in the absence of a STANDARD, hallowed be its name).

  If you (individually) design your programs for possible Internationalization
at some future point, you will be better at your task.  This will reflect
positively on you, and others around you will start to see the good sense in
it.  From there it becomes a matter of choice.  Not only that, but it gives
everyone a chance to lord it over someone who produces an 'inferior' product,
although I know that none of you would do THAT... :-)

In other words; talk is cheap.  Just do it...

TSgt Dave Burgess
NCOIC AL/MIS
Brooks AFB, TX
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Occasional system hangs
Organization: University of Utah Computer Center
Date: Tue, 15 Dec 92 03:42:35 GMT

In article <1992Dec12.223932.15096@runx.oz.au>, bde@runx.oz.au (Bruce Evans) writes:
|> In article <1992Dec12.073053.2721@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
|> 
|> >RAM isn't a problem; I have run a sufficiently stripped kernel on a 640K
|> >(no extended or expanded memory!) 386 Box with an NE2K card for periods
|> >in excess of 4 days with moderate usage (20 Meg swap on a 30 Meg drive
|> >and /usr remote mounted).  Moderate usage is 3 users curious about it and
|> >beating on the compiler.  Obviously, no X  8-).
|> 
|> How fast does it run?  I have run a fairly large kernel on a 386 system with
|> 1664K.  It runs OK until it starts swapping.  (Actually it runs dismally
|> because the disks are slow MFM 2:1 interleave and the system has to go to the
|> disk for almost everything.)  When it starts swapping, the disk light stays
|> on all the time and it takes several minutes to run the shell script
|> 'umount -af; sync'.  The shell is bash (definitely too big).  All known
|> patches related to memory leaks and disk activity are installed.

Well, this is pretty much to be expected... swapping kills, especially on
slow spindles.  The small box I played around with (above) has a fast disk;
swapping isn't that big a problem as long as the image you run plus the
kernel size fits in ram, or you have a moderately fast disk.


					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: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: 386BSD - Bug in UFS file system + proposed fix
Organization: Weber State University  (Ogden, UT)
Date: Wed, 16 Dec 92 21:14:22 GMT

In article <1992Dec16.012248.8123@moxie.hou.tx.us> hackney@moxie.hou.tx.us (Greg Hackney) writes:
>[ I posted this once, but I'm reasonably sure it didn't make it out ]
>
>There is a major bug in the 386BSD UFS code relating to file permissions.
>The major symptom is:
>
>   Can't read most files that you don't own on a remote NFS 386BSD system,
>   although there is public read permission, i.e.:
>
>-r--r--r--   1 root     other          5 Dec 15 19:15 /tmp/hell
>
>A very minor symptom is you can't read some LOCAL files, although
>there is public read permission, i.e. a file that looks like:
>
>-------r--   1 root     other          5 Dec 15 19:15 /tmp/hell
>
>[ This functionality seems broken on SunOS 4.1 too, but not on USL S5R4. ]

[ ... fix deleted ... ]

This fix seems a bad thing.  In particular, you *don't* want to allow a
file which is world read or world execute to be read/executed by someone
who is a member of a group denied access.

For instance, the group png (personna non grata) could be the group owner
of telnet, ftp, and other outgoing  network utilities.

If the permisssion on the file are:
-r-x---r-x   1 root     png        42610 Nov 10 20:10 telnet

Then people in the group png will be denied the ability to run telnet.  This
idea is called an exclusion group, and is correct behaviour.

Perhaps the reason you are having NFS problems is because unknown users
and root users from a remote system are translate to UID -1 and -2 unless
you specify that root access is allowed on the remote machine in the
/etc/exports file (your example seems to indicate you were logged in as
root when you tried this).

Admittedly, there are some permission comparison problems, but these are
pretty well isolated, and will probably be more tha a one or two line fix.


					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
-------------------------------------------------------------------------------
From: trown@ecst.csuchico.edu (Nick Trown)
Newsgroups: comp.unix.bsd
Subject: BSD on HP3500s?
Date: 18 Dec 92 21:44:03 GMT
Organization: California State University, Chico
NNTP-Posting-Host: periprism.ecst.csuchico.edu


	We are thinking of switching our HP3500s from Domain to BSD. 
Has this been done by anyone yet? If so, could you please point me
in the right direction for source, installation notes, etc. Any
help would be appreciated. Thanks...

--Nick Trown
Chico State University, Chico, California
Newsgroups: comp.unix.bsd
From: peter@wiesel.cosy.sbg.ac.at (Peter Burgstaller)
Subject: Soundkit, Soundtools?
Organization: University of Salzburg / Austria
Date: Mon, 14 Dec 1992 08:58:23 GMT

Hi!
Has anyone ported any soundtools for 386bsd?
I just ask this because I saw the sources for 
SoundBlaster support and I didn't see any code for
recording, playing, editing ... of sounds!

- Peter 8*)

--
/--------------------------------------------------------\
| Peter Burgstaller| Student of Computerscience		 |
| (peter@cosy.sbg.ac.at)| in Salzburg, Austria (Europe)	 |
| "So Long, and Thanks for All the Fish" (Douglas Adams) |
\--------------------------------------------------------/
Newsgroups: comp.unix.bsd
From: dawes@physics.su.OZ.AU (David Dawes)
Subject: Re: XFree86 and Fixed Fonts Errors
Organization: School of Physics, University of Sydney, Australia
Date: Mon, 21 Dec 1992 01:27:45 GMT

In article <RICH.92Dec8011413@omicron.Rice.edu> Rich@rice.edu writes:
>In article <BywoI7.K64@ucunix.san.uc.edu> leecs@ucunix.san.uc.edu (Christopher A Lee) writes:
>   I am setting up a PC with 386BSD 0.1 and XFree86.  
>   When i start up X, the following messages are generated:
>
>   XFree86 Version 1.1 / X Window System
>[...]
>   VGA256: SpeedUp mode selected (Flags=0x30)
>   failed to set default font path '/usr/X386/lib/X11/fonts/misc/,/usr/X386/lib/X11/fonts/Speedo,/usr/X386/lib/X11/fonts/75dpi/'
>   Fatal server error:
>   could not open default font 'fixed'
>
>The problem turns out to be in the server.
>
>The solution is to add the following to your Xconfig:
>
>FontPath"/usr/X386/lib/X11/fonts/misc/"
>FontPath"/usr/X386/lib/X11/fonts/Type1/"
>FontPath"/usr/X386/lib/X11/fonts/Speedo/"
>FontPath"/usr/X386/lib/X11/fonts/75dpi/"
>FontPath"/usr/X386/lib/X11/fonts/100dpi/"
>
>You can leave all of them in. The server will ignore the font
>directories that don't exist.

This will *not* work in version 1.1, because that version doesn't do any
fontpath verification -- or accept multiple FontPath lines.

The solution for now is to make sure that each directory specified in
your FontPath exists and contains a file called fonts.dir.  If you don't
have some directories (like /usr/X386/lib/X11/fonts/Speedo) then
remove them from the FontPath.

>In Xfree86 1.1 the server does not
>verify the font path if you don't have a FontPath line in your
>Xconfig.  Missing font directories can then cause the server to fail.
>This will get fixed in the next release.

The support for multiple FontPath lines and full fontpath verification is
planned for the next release (version 1.2).  We don't have a firm date for
that release yet -- but it should be out early in '93.

>Rich, XFree86 team

David
--
------------------------------------------------------------------------------
 David Dawes (dawes@physics.su.oz.au)    DoD#210      | Phone: +61 2 692 2639
 School of Physics, University of Sydney, Australia   | Fax:   +61 2 660 2903
------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: tlukka@lk-hp-8.hut.fi (Tuomas J. Lukka)
Subject: tip & screen
Organization: Helsinki University of Technology, Finland
Date: 13 Dec 92 09:33:47 GMT

Has anyone hacked screen to work on 386BSD? I get it to compile
but have not yet gotten it to actually work.

Also, what do I need to make tip work with sz etc, there was a patch,
is it in the kit?

	TJL
Newsgroups: comp.unix.bsd
From: f80204@cad.ee.ntu.edu.tw (Hung-Chi Chu)
Subject: [386BSD] gcc-2.3.2 compiling error
Reply-To: f80204@cad.ee.ntu.edu.tw
Organization: Department of Electrical Engineering, National Taiwan University
Date: Mon, 21 Dec 1992 06:26:06 GMT

Hello,

   I tried to port gcc-2.3.2 to 386BSD, but it failed. The compiling process

stopped at "enquire.c: floating constant out of range".

   Did anyone encounter the same problem?  Any sugestion?

   Please mail your answer to f80204@cad.ee.ntu.edu.tw

Thanks in advance.

			--- Chu ---

Newsgroups: comp.unix.bsd,comp.windows.interviews
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: [386bsd] need motif
Keywords: motif 386bsd
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Fri, 18 Dec 1992 23:36:44 GMT

In article <1992Dec18.223849.18131@jpl-devvax.jpl.nasa.gov>,
 kaleb@swat (Kaleb Keithley) writes:
| 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.

On the other hand, an OSF person told me that if someone took the AES
and programmed a motif look/work alike from it, they would/could do nothing.

(not that I completely believe this)

And as much as I like Xaw3d, Motif as more going for it than just shadows...
like more widgets, and more powerfull widgets, and traversal, and...

-- 
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA
Newsgroups: comp.unix.bsd,comp.os.linux
From: goer@kimbark.uchicago.edu (Richard L. Goerwitz)
Subject: Dumb Americans (was INTERNATIONALIZATION: JAPAN, FAR EAST)
Keywords: Han Kanji Katakana Hirugana ISO10646 Unicode Codepages
Reply-To: goer@midway.uchicago.edu
Organization: University of Chicago Computing Organizations
Date: Fri, 18 Dec 1992 04:30:33 GMT

>> 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...

One of the big criticism leveled at US Engineers is that they are either
too dumb or lazy to build into their software support for non-Western
scripts.  Given that Linux originates in Europe, can we look forward to
better support for Unicode and ISO10646?  At least for "long" charac-
ter definitions?

Incidentally, although it's true that US Engineers often have really
terrible language skills, this is due more to geographical isolation
than to organic stupidity.  There's just no need for multilingualism
here in the states, the way there is in Europe, esp. in the low coun-
tries and Scandinavia.

-- 

   -Richard L. Goerwitz              goer%midway@uchicago.bitnet
   goer@midway.uchicago.edu          rutgers!oddjob!ellis!goer
Newsgroups: comp.unix.bsd
From: mark@yarra.pyramid.com.au (Mark Goodwin)
Subject: 386BSD Bustek SCSI drivers : available from where?
Organization: Pyramid Technology Corp PL, Melb., Australia
Date: Wed, 9 Dec 1992 02:05:39 GMT

I have a 486/EISA/Bustek and want to install 386BSD. Can I ftp/get
the appropriate drivers, or preferably dist.fs/fixit.fs for this
system configuration? Or wont it work?

The FAQ says ithat only ISA/IDE systems/controllers are supported.



Mark Goodwin,
R&D Software Engineer,
Systems Technology Laboratory,
Pyramid Technology Corporation,
Melbourne, Australia.

Phone: +61-3-521-3799
Email: mark@yarra.pyramid.com.au
[Disclaimer: I always speak only for myself].
From: veit@du9ds3.fb9dv.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: OS-BS & Codrv (was:Re: Want info on German Boot Manager thingy please)
Date: 15 Dec 92 10:34:07 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.fb9dv.uni-duisburg.de
NNTP-Posting-Host: du9ds3.fb9dv.uni-duisburg.de

In <veit.724405437@du9ds3> veit@du9ds3.fb9dv.uni-duisburg.de (Holger Veit) writes:

>In <6051@rosie.NeXT.COM> sam_s@NeXT.com (Sam Streeper) writes:

>>ricky@lindblat.cc.monash.edu.au (Mr RS Mcconachy) writes:
>>> A few months back (not long after the release of 0.1 386BSD in fact)
>>> a German getleman posted a note to this group about his boot manager
>>> program.  

>One "German" site for this code is ftp.uni-duisburg.de in
>/pub/unix/386bsd-0.1/unofficial/patches/os-bs134.uu (extract from c.u.bsd).
>Admitted, this site *is* slow, but not because of sloppy management here,
>but because of the gateway 'Germany.Eu.Net' which is constantly overloaded.
>If you find Germany.eu.net in your traceroute, go buying a coffee in Colombia.
>(Sorry, no smiley here!)

>Holger

Some addendum to a possible problem between the partition switcher OS-BS
mentioned above and my console driver CODRV:

(excerpt from BUGLIST.151292, only bug added since BUGLIST.011292):

-------
BUG 14:	The old pccons worked. Codrv hangs after showing the Copyright
	message. I use Thomas Wolfram's "os-bs" (osbs-132/134) 
	partition switcher.

FIX 14:	os-bs is broken in that way that the keyboard character to be
	entered is not correctly removed from the keyboard queue. 
	OS-BS does not use, for some unknown reasons, BIOS Interrupt 16h, 
	but fiddles with the keyboard controller itself. This causes a 
	release code to be left in the keyboard queue, when a selection 
	key is pressed. This code irriates the codrv attach routine and 
	causes 386bsd to hang. The problem (with a different effect) also
	occurs with OS/2 2.0 with the first keyboard request.

	Fix: This should be fixed in OS-BS, but it is unknown whether the
	author is still available.
	The next version of codrv will address this problem for 386bsd.
	Workarounds:
	1. Make 386bsd the default partition, and let it timeout.
	   The effect in other (DOS-type) OS versions is not so extreme
	   (mostly additional character at first keyboard access). The
	   effect on Linux or other UNIX versions is unknown.
	2. Use the Mach-Kernel switcher that was posted some time ago
	   by Julian (a copy available from e.g. ftp.uni-duisburg.de
	   in /pub/unix/386bsd-0.1/unofficial/patches/boot.block). This
	   will catch the surplus scancode and has more benefits.
-----

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)
From: bs@qwerty.Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: Re: bad blocks
Date: 16 Dec 1992 16:21:08 GMT
Organization: EUnet Deutschland
Distribution: world
NNTP-Posting-Host: qwerty.germany.eu.net

In article <9212161445.AA23123@deepthought.cs.utexas.edu>, pmcgilla@hp.uwsuper.edu (Patrick L. McGillan) writes:
|>   I am getting bad blocks showing up in my root drive. I tried reading
|>   the stuff on bad144 but it didn't make sense. Is there some way to 
|>   flag blocks bad on the fly so I don't have to take my system down.

No.
You will have to re-boot your system after using bad144.
BTW if I recall this correctly, the information bad144 gives you on its
usage (bad144 w/o arguments) tells you to put the drive in the wrong place
(I don't recall the correct order now)
Try bad144 -v -a -c wd0 <blocknumbers> (or the wd0 in front of the -v)
For the changes to take effect, re-boot your system.

Greetings,
	Bernard
-- 
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
Newsgroups: comp.unix.bsd
From: dosburn@cwis.unomaha.edu (Don Osburn)
Subject: Re: Linux boots on Tandon but 386BSD doesn't 
Keywords: Hardware, Tandon, Architecture, install, boot
Organization: University of Nebraska at Omaha
Date: Thu, 17 Dec 1992 20:19:16 GMT

Since I was having no luck with the 386BSD boot, I decided to switch
over and try the Linux boot for kicks.  It worked right off.

Can anyone tell me why the Linux system will boot on my hardware, 
but the BSD won't?  Does anyone think there is any value to be 
gained by porting the BSD to a Tandon? (Other than my own educational
value.)  If so, please let me know, else I may switch over to the Linux
project.  :-|  Thanks in advance.

@	@
    ?
---------

Newsgroups: comp.unix.bsd