HDTenEightyP/NetNews huggingface dataset:
From: torek@horse.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.bsd
Subject: Re: a unix terminal question
Date: 12 Jan 1993 21:05:35 GMT
Organization: Lawrence Berkeley Laboratory, Berkeley CA
NNTP-Posting-Host: 128.3.112.15

(I note that this article would have gone to both comp.lang.c and
comp.unix.bsd.  It is rare for an article ever to belong in both
groups.  This particular stuff really should not be in comp.lang.c at
all, so I have redirected it.)

In article <uonuhjc@zola.esd.sgi.com> dps@delhi.esd.sgi.com (D.P. Suresh)
writes:
>select() or poll() in itself will not get you the desired result
>[because the O/S is doing line gathering and you must disable this too].

>	/* Create proper environment for select() */
>	FD_ZERO( &readfds );
>	FD_ZERO( &writefds );
>	FD_ZERO( &exceptfds );
>	FD_SET( fileno(stdin), &readfds );

Since no write or exception file descriptors will be used, none need be
provided.  Select() allows (fd_set *)NULL arguments, meaning `nothing
of interest here'.

>	/* We shall specify 0.5 sec as the waiting time */
>	timeout.tv_sec  = 0;	/*   0 seconds */
>	timeout.tv_usec = 500;	/* 500 microseconds */

tv_usec is indeed microseconds, so 500 us is 0.0005 seconds, not 0.5.
(Most current UNIX systems will round this up to their actual internal
timeout rate of 100 Hz, or .01 seconds.)

>	/* Put tty in raw mode */
>	ioctl(fileno(stdout), TCGETA, &otty);
	...
>	ioctl(fileno(stderr), TCSETAW, &ntty);

Here I have to wonder why the tty modes are obtained from stdout and
set on stderr when we are going to read stdin.  If the reading is to be
from fileno(stdin), the tty operations should be done there as well,
since their purpose is to affect this reading.

In more complex tty control programs (such as editors), the goal may be
both to affect input and output.  In this case it is a bit more
reasonable to try both stdin and stdout.  In any case it seems wrong to
touch stderr.  The wise and cautious programmer might consider:

	iocfd = STDIN_FILENO;		/* or simply 0 */
	if (ioctl(iocfd, TCGETA, &otty) < 0) {
		iocfd = STDOUT_FILENO;	/* 1---these should be in <unistd.h> */
		if (ioctl(iocfd, TCGETA, &otty) < 0) {
			/* disable tty operations, i/o is pipes or similar */
			ttycontrol = 0;
			return;
		}
	}
	...
	(void)ioctl(iocfd, TCSETAW, &ntty);

In this particular case (reading stdin only), the attempts using
STDOUT_FILENO are not advised.

On BSD systems, one should also use care lest code like this be stopped
(via, e.g., ^Z) between the `get' and `set' phases and the tty settings
be changed.  Careful use of signal handlers and, if necessary, setjmp
and longjmp can make tty alteration appear atomic.

>This feature should be used wisely. One could incur quite a lot of
>performance penalties as expressed by terry.

Indeed, particularly if the keyboard mode is changed twice on every call
to this checking function.

Incidentally, note that select() for reading returns true at EOF
(because reading EOF does not block).  Callers should be prepared for
this.
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 510 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov
Newsgroups: comp.unix.bsd
From: brian@panix.com (Brian Childs)
Subject: [386bsd] Is there a way to remap the keyboard
Organization: Panix Public Access Internet & Unix, NYC
Date: Wed, 6 Jan 1993 22:39:26 GMT


I have compiled emacs 18.59 on 386bsd, but I have noticed that no key
sends a nul character (ascii 0) which is a very important emacs command.

As a result I was wondering if there is a way to remap the keyboard ?

Thanks in advance,
Brian
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.unix.bsd
Subject: Re: INTERNATIONALIZATION: JAPAN, FAR EAST
Date: 4 Jan 93 19:04:41 GMT
Organization: Tokyo Institute of Technology

In article <1992Dec28.064029.24421@fcom.cc.utah.edu>
	terry@cs.weber.edu (A Wizard of Earth C) writes:

>|> True. But, it should be noted that they don't fit even in 16 bits.
>
>Work is already under way to adapt Unicode to 32 bits.  I would be interested
>in any similar work you know of in progress for XPG4/JIS.

Anyway, a program written for 16 bit Unicode can not be usable with 32 bit
Unicode.

>I am *not*
>interested in proposing or attempting to provide yet another standard, if
>that is what you believe is necessary.

Then, why you are interested in using yet non-existent standard?

BTW, can you explain what XPG4 is?

>Again, I want to stress that we are about the identification and adoption
>of an existing standard rather than the specification and ratification of
>a new one.

Then, the only standard available now for internationalization is ISO 2022.

It can, at least, differentiate Chinese and Japanese character.

Do you want to use it?

>We may invoke "tricks" to reduce storage requirements or to
>retrofit existing input mechanisms, but we are not attempting a new standard.

Again, existing input mechanism for Japanese is so large that even very
complex tranlation does not affect its performance.

						Masataka Ohta
Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: Re: questions of scsi tape driver.
Organization: TRW Financial Systems
Date: Wed, 6 Jan 1993 19:37:46 GMT

In article <1993Jan3.003448.2389@netcom.com> shawr@netcom.com (rich shaw) writes:
>Recently I bought a used tandberg TDC3640 scsi tape drive. I think it's
>a QIC150 drive. This drive works fine under dos (I am using aspitar).
>But when I boot 386bsd with julian's scsi drivers(Thanks julian), there 
>seem to be some problems recognize  or initialize the drive. Below are
>the messages on the screen.
>
>dev4,lu0: tape1 (sequential), removable 'unknownunknown????' SCSI0
>	st0: scsi tape drive:0 blocks of 512 bytes

wow a really old device... almost SASI not scsi!
>cmd fail
>cmd fail 
>...
>
>After I compiled with scsi_debug set to 1, I got the following message.
>
>aha_scsi_cmd <ccb0(0x23) cmd fail
>aha_done ccb0(0x33)> ccb0(0x23)> ahaintr scsi error rval=3
>code from driver 0x2

unfortunatly I need more information..
the scsi_debug word has many bits, each of which specify different debugging:\
set it to -1 for more info..

thanks
>
>-- rich
>-- shawr@netcom.com
>
julian
+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\            
          v
From: bs@qwerty.Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] more than 16MB?
Date: 7 Jan 1993 18:19:41 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: qwerty.germany.eu.net

|> > > Is anyone out there running 386bsd on an ISA-bus machine with more
|> > than
|> > > 16MB ram?
|> > 
|> > Yes. I've seen a machine with 20MB and heard of one with 64 MB
|> > (yes, sixty-four) No, not me...

In fact, as I pointed out earlier, the 64 meg machine is an EISA.
However, we have a claim here for yet another machine (486 ISA) running
32 megs.

Let me point out once again that these people only claim their machine is
up and running 386bsd; they don't claim any of their RAM above 16 meg is
actually used (is there a way to check this ?)

Cheers,
	Bernard
Newsgroups: comp.unix.bsd
From: rimkus@netcom.com (Mike Rimkus)
Subject: Re: [386bsd] Mach8 Programmer's Kit
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: comp.unix.bsd
Date: Mon, 11 Jan 1993 08:52:51 GMT

In article <1993Jan10.205016.17787@netcom.com> hasty@netcom.com (Amancio Hasty Jr) writes:
> I think that ATI is now selling their documentations for their 
> MACH 8 chipset, so for anyone interested in working on XBSD8514, here 
> is the e-mail for ATI:

ATI is (telling me that they are) charging me $50 for the set. It contains
four books:
  Programmer's Guide to the Mach-8 8514/A-Compatible Registers
  Programmer's Guide to the Mach-8 Extended Registers
  Programmer's Guide to the Mach-8 Extended Registers Supplement
  Programmer's Guide to the Mach 32 Adapter Interface

The first two books have the I/O port address and what they do/mean. I haven't
looked at the second two yet.

ATI has a fact sheet they seem to want you to read before ordering, probably
so that you know what you're asking for. They can fax it to you. Customer
service is 416-756-0711, keep trying.
Newsgroups: comp.unix.bsd
From: philsuth@mycroft.DIALix.oz.au (Phil Sutherland)
Subject: 386bsd on notebook machines - ethernet adaptors/drivers
Reply-To: philsuth@DIALix.oz.au
Keywords: notebook ethernet 
Date: Wed, 6 Jan 93 15:14:17 GMT

Gentle Netfolk,

I've been running 386bsd 0.1 on my home machine since its release, and
have been enjoying it immensely. I'm now looking to acquire a notebook
computer of some sort, and naturally I'd like to get my favorite
operating system running on it too. Thus, I'm seeking answers to the
following:-

1. Are there any pitfalls I should be aware of when choosing a notebook
   machine for 386bsd?  I intend to run a small DOS partition as well
   for compatibility reasons. :-(  Currently I'm looking at the 
   Sharp PC-7700 or PC-7750 notebooks - with 8Mb RAM and 120 Mb disk.
   Is anyone using one of these out there?

2. Has anyone written drivers for any of the parallel port connecting
   Ethernet adaptors, or gotten sufficient technical information about
   any of them to allow such a driver to be written? Which adaptors
   should I avoid (I remember comments regarding some companies being
   reluctant to release technical information about their devices).

Email, or post if you feel your comments will interest the 386bsd world
at large. I'll summarize as appropriate.

Thanks
phil

-- 
------------------------------------------------------------------------
Phil Sutherland        Perth, Western Australia    philsuth@DIALix.oz.au

Newsgroups: comp.unix.bsd
From: henan@nimios.eng.mcmaster.ca (Nan He)
Subject: 386bsd Installation
Organization: Communications Research Laboratory, McMaster Univ
Date: Thu, 7 Jan 1993 22:08:31 GMT

  Dear Netters: 

       I am installing the i386bsd to my system, which has the
  following features:
    386 25MH, 85MB hard disk, 1.2MB and 1.44MB floppy drives, SVGA,
    Running DOS5.0 now.
  The booting disk I used was got from the output of rawrite.exe,
  with the input "dist.fs".

  Now I have the following "funny" problem: Using the MSDOS FDISK
  command, I partitioned 40MB for dos, and leave the rest for BSD
  (it's more than 40MB, which should meet the requirement for BSD).
  Then I just followed the installation note, inserted the booting
  disk of BSD into drive A and boot the machine. I answered the 
  questions appeared on the screen one by one, so after waiting 
  about 1 min, the system require me to remove the floppy disk(booting
  disk) and hit return to boot off the machine. I did, but the machine
  just keep booting self again and again, without stop. A very short
  message appeared on the screen after each booting, which flash so 
  fast I cann't read it. I had to turn off the machine to stop it.

  Now I inserted the booting disk and booted the machine again. This
  time when the system ask me if I am going to use the entire disk 
  for 386bsd, I answered yes(in the previous one I answered no, which
  just use the rest 45MB for 386bsd). So after all, I removed the booting
  disk and hit the return, I got the system! I can start to extract the
  binary distribution disks now!

  Supected that I didn't leave enough space for 386bsd, I used my DOS
  to partition the disk again, but the DOS partition just took 5MB, the
  rest 80MB was left for 386bsd. I started installation again. However, 
  If I didn't choose use the entire disk for 386bsd, but rather, the 80MB
  partitioned for 386bsd, I got the same problem again! The machine just
  keep booting, never stop.

  I am sure I read the installation note very carefully and followed 
  its instruction exactly. I don't know if anybody met similar problem
  before. If anybody could give me some suggestion or solution, I would
  be greatly appreciate it. Please send the response to this account
  appeared at the head of this post, or send them to 
    henan@sscvax.cis.mcmaster.ca 
  or
    he@neuron.eng.mcmaster.ca

  I promise to post the solution to this news group after I got it.

  Thanks!

  --Nan He
    Dept. of Elec. Eng.
    McMaster Univ.
    Hamilton, Ont.   Canada
    L8S 4K1 
  
  
 
Newsgroups: comp.unix.bsd
From: g89s9112@hippo.ru.ac.za (Dirk Sturzebecher)
Subject: [386bsd] mtools (mread) PROBLEMS
Organization: Rhodes University, Grahamstown, South Africa
Date: Thu, 7 Jan 1993 13:57:43 GMT

Hi all,
can someone please explain the following to me.

with the original kernel I can read all files of a floppy or stiffy
except the last one,
with a recompiled kernel from another machine I can not read a single
file succesfully, 
while I can read ALL files under DOS without problems

WHY ? is there some setup file ? ...

Thanks, Dirk

-- 
-----------------------------------------------------------------------
Dirk Sturzebecher				g89s9112@alpha.ru.ac.za
Rhodes University Grahamstown			South Africa
Newsgroups: comp.unix.bsd
From: vpham@cs.ulowell.edu (vinh)
Subject: motif for 386bsd?
Organization: UMASS at Lowell
Date: Wed, 6 Jan 1993 05:40:33 GMT


hi,
does anyone have the address of the person who sells motif (or better
yet the article posted by this person?)
thanks.
vp
Newsgroups: comp.unix.bsd
From: chetal@is.morgan.com (Pradeep Chetal)
Subject: Where can I pick up the FAQ from?
Organization: Information Services, Morgan Stanley, NYC
Date: Mon, 11 Jan 1993 05:36:56 GMT


Thanks,

/Pradeep
--
----------------------------------------------------------------------------
Pradeep Chetal		UUCP:	...!uunet!is.morgan.com!chetal
Morgan Stanley		Internet: 	chetal@is.morgan.com
1633 Broadway,		Phone:		(212) 703-2220 (O)
NY, NY 10019				(212) 703-2371 (FAX)
            _______________    __o
        _________________     -\<,
                        ......O/ O
Newsgroups: comp.unix.bsd,comp.os.linux
From: wonge@fraser.sfu.ca (Edmund Wong)
Subject: Hostnames and named.
Organization: Simon Fraser University, Burnaby, B.C., Canada
Date: Thu, 7 Jan 1993 22:33:38 GMT

In article <C0I7K9.D2w@ns1.nodak.edu> tjon@plains.NoDak.edu (Christopher C. Tjon) writes:
>In article <1993Jan6.015924.21943@bradley.bradley.edu> brad@bradley.bradley.edu (Bradley E. Smith) writes:
>> does a wangtek and 60meg tape drive work?
>> if so how well (note: i am interested in both BSD and linux).
>> -- 
>> Bradley Smith			 brad@bradley.edu ---  309-677-2337
>> Network & Technical Services @ Bradley University, Peoria, IL
>> 
>> "It's amazing how much scrap metal you get from 4 cans of beer"
>
>Brad,
>	I have the same wangtek drive and 60meg tape.  Mine was stripped 
>from an AT&T box.  I read and write find.  I had some problems with it
>before but after getting my kernel majorly patched with all the patches that
>have come along it is working.  You must configure your kernel to recognize
>the drive.  Assuming you have the same controller as I and need to know
>I can provide you with Jumper settings to set your address to 0x300 and irq
>to whatever(5?)
>
>
>-- 
>Chris
>		tjon@plains.nodak.edu	 Christopher C. Tjon
>		uunet!plains!tjon (UUCP) Box 5224
>		tjon@plains (Bitnet)	 Fargo, ND 58105-5224
>This message brought to you by the letters X and S and the number 3.

-- 
InterNet: wonge@fraser.sfu.ca  |  "Fail not; Learn Not.
                               |  It is with failing, that one learns,
                               |  So by Learning, one must fail." - Edmund Wong
From: pbd@runyon.cim.cdc.com (Paul Dokas)
Newsgroups: comp.unix.bsd
Subject: XFree86 mouse problems solved
Date: 8 Jan 93 21:32:52 GMT
Organization: ICEM Systems, Inc.

The problems that I was having with X turned out to be in the hardware.
The serial ports on my IDE-IO (ide, fd, 2s 1p 1g) card are useless (no
surprise here :-| )

So I'm now down to 2 serial ports (a mouse and a terminal), but I need
3 (I've got a modem).  I've got a simple dual serial card (a 16450 and
a 16550 on board), but I'm considering getting another.  But I've got
a few questions first.  Does anyone know if the default com driver will
handle shared IRQs for serial ports?  For example, will the following
work:

  device         com1    at isa? port "IO_COM1" tty irq 4 vector comintr
  device         com2    at isa? port "IO_COM2" tty irq 3 vector comintr
  device         com3    at isa? port 0x3e8 tty irq 4 vector comintr
  device         com4    at isa? port 0x2e8 tty irq 3 vector comintr

com1 and com3 share IRQ 4 and com2 and com4 share IRQ 3.  Where com1
and com2 are on one board and com3 and com4 are on another.

If this won't work, then can someone recommend a multi-port serial
card.

-- 
#include <std.disclaimer>
#define FULL_NAME                          "Paul Dokas"
#define EMAIL                              "pbd@runyon.cim.cdc.com"
/*            Just remember, you *WILL* die someday.             */
Newsgroups: comp.unix.bsd
From: dfox@quack.sac.ca.us (David Fox)
Subject: Re: [386BSD] fp exception after 387 installation - help !
Keywords: 386BSD floating point 387
Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'.
Date: 5 Jan 1993 02:33:35 UTC

In article <1611@hcshh.hcs.de> hm@hcshh.hcs.de (Hellmuth Michaelis) writes:
>In <1610@hcshh.hcs.de> hm@hcshh.hcs.de (Hellmuth Michaelis) writes:
>
>[about installing an 387 and getting floating point exceptions after that]
>
>Thanks to everyone who replied to that article !
>
>But the problem stays ! There is (and was) a "double" declaration of getpcpu()
>in ps.c - it solved the problem of the ps-coredump on the virgin 0.1, ps ran
>fine after installing the patchkit until i installed the 387 ....
>
>anyone else who had such a problem ?

I did, with the ps.

>are all other 387's running fine after it's installation ?

I think this particular problem would affect all 387s, not just Cyrix (the
one I bought).

>ps: made new libm.c, libutil.c, libc.c, kvm_mkdb, dev_mkdb etc. etc ...

I also made a new libutil.c.  I haven't made kvm_mkdb or dev_mkdb and I'm
not sure if I need to.  I don't have the sources to those online right now
anyway.

With respect to libm.a:  you and others with NDPs would do well to get the
GNU mathlib 2.1.  It's 387-specific, and among other things, issues FSIN
and FCOS (among others) instructions directly, instead of emulating them
with 387 primitives.

I've also removed the math emulator from the kernel (don't EVER do this
unless you have an NDP), which cuts the size down a bit.

I'm trying to get gcc 2.3.3 now, so I will defer remaking the other lib
stuff for now.  I expect the new gcc to solve problems like these.

>-- 
>hellmuth michaelis    HCS Hanseatischer Computerservice GmbH   hamburg, europe
>hm@hcshh.hcs.de              tel: +49/40/55903-170         fax: +49/40/5591486
--
David Fox
dfox@quack.sac.ca.us


Xref: sparky comp.unix.bsd:11050 comp.os.linux:23273
From: ewerlid@ida.docs.uu.se (Ove Ewerlid)
Newsgroups: comp.unix.bsd,comp.os.linux
Subject: Locate/fast-find (Was: Re: Shared lib X for 386bsd?)
Date: 8 Jan 93 22:24:23
Organization: University of Uppsala, Sweden
Distribution: world
NNTP-Posting-Host: ida.csd.uu.se
In-reply-to: othman@ntrc25.ntrc.ntu.ac.sg's message of Fri, 8 Jan 1993 05:05:52 GMT


In article <1993Jan8.050552.11116@ntuix.ntu.ac.sg> othman@ntrc25.ntrc.ntu.ac.sg (othman (EEE/Div 4)) writes:
> I tried to compile X utilities especially xterm but I cannot even find the
> sources despite having the X11r5 distribution. Which directory does 
> xterm belong to? 

A very useful command is `locate' or `fast find'.
Just run `updatedb' at regular intervalls.

`locate' uses a data base built by `updatedb' to quickly
locate a particular file name.

E.g.

bash$ locate xterm
/usr/X11R5/usr/X386/bin/xterm
bash$

I don't have the full X11 dist so theres no source! 

(GNU'S locate/updatedb comes with the Linux SLS dist.)

Perhaps I'm stating the obvious here ...
Anyway, rather than asking the net where a file in my own filessytem
is I'd run a brute force 'find / -print | grep xterm'. :-)
To be fair, the question was just a fraction of the original posting.
From: sanner@track.physics.usfca.edu (Operator)
Newsgroups: comp.unix.bsd
Subject: [386bsd] Cannot Mount /  Err?
Date: 9 Jan 93 01:05:53 GMT
Organization: University of San Francisco
X-Newsreader: TIN [version 1.1 PL7]


I am trying to get 386bsd to run on my 486 with IDE drives.

I had no problem booting 386bsd off of a floppy and installing it
on my 40MEG partition.  (It only formatted to 36 Meg)

But, when I try to boot off of the HD it gets half way up - recognizes
the devices but cannot mount the root partition so it reboot and
starts looping and failing.

Has anyone else seen then? Could it be due to my WD8003E card has IRQ 3 set?
Could it be due to that my 40 meg partition formated to 36 meg?

Thanks for any help...  Getting started is sometimes the big hump....

(386bsd install is such a relief from LINUX - No binary editors!)


		Thanks,
--

                                    David Sanner   (sanner@usfca.edu)
                                    U of S.F. Physics Research Laboratory
                                    SF, CA 94117   (415) 666-2962
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.unix.bsd
Subject: Re: Dumb Americans (was INTERNATIONALIZATION: JAPAN, FAR EAST)
Keywords: Han Kanji Katakana Hirugana ISO10646 Unicode Codepages
Date: 6 Jan 93 19:24:56 GMT
Organization: Tokyo Institute of Technology

In article <1993Jan5.090747.29232@fcom.cc.utah.edu>
	terry@cs.weber.edu (A Wizard of Earth C) writes:

>>>This I don't understand.  The maximum translation table from one 16 bit value
>>>to another is 16k.
>>
>>WHAAAAT? It's 128KB, not 16k.
>
>Not true for designated sets, the maximum of which spans a 16K region.

Uuuurrrghhhh!!! Ia Ia!

>128k is only necessary if you are to include translation of all characters;
>for a translation involving all characters, no spanning set smaller than the
>full set exists.  Thus a 128k translation table is [almost] never useful

Then, don't say 16 bit. If you say 16 bit, it IS 128K.

>>>This means 2 16k tables for translation into/out of
>>>Unicode for Input/Output devices,

>In this particular case, I was thinking an ASCII->Unicode or Unicode->ASCII
>translation to reduce the storage penalty paid by Western languages for

ASCII <-> Unicode translation does not need any tables. PERIOD.

>>How can you "cat" two files with different file attributes?
>
>By localizing the display output mechanism.

Wow! Apparently he thinks "cat" is a command to display content of
files. No wonder he think file attributes good.

						Masataka Ohta
Newsgroups: comp.unix.bsd
From: g88d4938@giraffe.ru.ac.za (MR GE DOYLE)
Subject: [386bsd] disklabeling?
Keywords: disklabel, partition
Organization: Rhodes University, Grahamstown, South Africa
Date: Mon, 11 Jan 1993 10:14:06 GMT

Hi All
 I want to install MSDOS and 386bsd on the same disk. I need some help
 though getting the disklabel right: the a,b,c,d partitions. In particular
 the d and the c.
 Can anyone help me with these?

 Thanx in advance.
   Greg