HDTenEightyP/NetNews huggingface dataset:
From: crash@ckctpa.UUCP (Frank "Crash" Edwards)
Subject: Re: Broken term? sag?
Date: Mon, 31 Aug 1992 22:28:06 GMT
Distribution: usa
Reply-To: crash%ckctpa@tct.com (Frank "Crash" Edwards)
Organization: Edwards & Edwards Consulting

jose@kbsw2.UUCP (Jose Sousa 806 9999) writes:
>In article <1992Aug28.140829.4440@isc-br.isc-br.com> ricks@odin.isc-br.com (Rick Schaeffer 99) writes:
   [some deleted]
>Thus in your .profile do EDITOR=vi or EDITOR=emacs and export it.  Ksh will
>the use the specified editor. 
>( You may need to set EDITOR=/<path_to_editor>/vi )
>All this stuff is documented in the ksh man entry.

Errr, it should be pointed out that KSH does not "use" the editor.
KSH has built-in emulations for EMACS and VI _only_.  Don't expect to
be able to use wordstunt^H^H^Har keystrokes, or any other arbitrary editor.

>Jose A. Sousa
>Kentek Information Systems     jose@kentek.com

-- 
Frank "Crash" Edwards            King Marine Electronics, Inc.
Home: 813/786-3675               Work: 813/530-3411

    Finish the sentence below in 25 words or less:
	    "Love is what you feel just before you give someone a good..."
    Mail your answer along with the top half of your supervisor to:
	    Love is...
	    P.O. Box 35
	    Baffled Greek, Michigan 69069
From: tope@enea.se (Tommy Petersson)
Newsgroups: comp.unix.amiga
Subject: Re: 1.2 GB HD & Progressive Memory Card Question.
Date: 27 Aug 92 08:24:06 GMT
Organization: Enea Data AB

brianv@amiserv.chi.il.us (Brian Vargyas) writes:
- I am looking at buying the above items.  The Progressive 64MB Zorro III
- memory card for my 3000UX as well as a 1.2 or larger GB hard disk.  What
- I need to know is if anyone has used any of these items, and if so, do they
- work fine with Amix V2.1?  I already have 16MB of memory in system, and
- would like to have more due to my NFS usage going up.  I understand that
- using a Zorro III card and the motherboard memory would NOT see each other
- under Amix because the memory isn't contigous.  I am using the kernal compiled
- for machine=A3016 rather then reloc, since I have better luck with my TTY
- ports not dying on my 2232 in that mode.   So, I'm sure I can play a memory
- mapping game, and get it to work, I just want to know if anyone is currently
- using the PP 64MB Zorro III card..
- 
- 2nd, I really really need to purchase a larger HD because of the NFS volume
- that I expect to be doing shortly.   I know from experience with other large
- drives, drives that have SCSI-2 on board, and turned ON will NOT function with
- AMIX at all.   You must be able to DISABLE the scsi-2 command set on the drive
- in order for it to work with Amix.  Going on that information, WHAT drive
- out there allows me to turn off the Scsi-2 command set? I'm looking at Fujitsu, Maxtor, Wren and a few others.....is anyone currently using a large drive
- that works?  I've also found using a separate drive for your swap (52Q) works
- much better then using your root drive, as the head contention is MUCH less.
- 
- Please respond via E-Mail if you can, or via the newsgroup, as I'm sure others
- would welcome any response.
- 
- --
- brianv@amiserv.chi.il.us
- 
- -- 
- brianv@amiserv.chi.il.us    Amiga Network Information Systems
- 708-983-6678                AT&T SVr4 UseNet News/Mail Server

I have Amiga Unix on a Fujitsu 1,2GB HD, and it works fine.

-- 
=============================================================================
 Tommy Petersson              tope@enea.se              Enea Data AB, Sweden
=============================================================================
Newsgroups: comp.unix.amiga
From: wyk1@cunixa.cc.columbia.edu (Won Y Kim)
Subject: Re: Build the kernel with gcc v2.2.2?
Keywords: AmigaUNix
Reply-To: wyk1@cunixa.cc.columbia.edu (Won Y Kim)
Organization: Columbia University
Date: Sun, 23 Aug 1992 19:31:59 GMT

In article <abeech.714491471@kraken> abeech@kraken.itc.gu.edu.au (Adrian Beech) writes:
>Has anyone re-compiled the kernel using the gcc v2.2.2 compiler?  I have 
>just re-built the thing but for some reason I can't seem to be able to 
>make a test boot floppy.  I get "unbound sym[xxx]" errors when I issue
>the "make floppy KERNEL=/usr/sys/unix" command.
                                             ^^^^^^^^^^

Did you have any problems getting gcc 2.2.2 running in your machine?

Do you have any hints or tips on installing it??

Thanks.

					-Won Kim.
Please send all replies to won@cs.columbia.edu
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Won Kim. Programmer ReProgrammer.
"I am the SuperGrunt. The *Orginal* SuperGrunt. Perhaps you have heard of me?"
						- The Orginal SuperGrunt
From: ag@cogsci.Berkeley.EDU (Keith Gabryelski)
Newsgroups: comp.unix.amiga
Subject: Re: Audio Device in 2.03
Date: 25 Aug 1992 16:54:15 GMT
Organization: Institute of Cognitive Studies, U.C. Berkeley
NNTP-Posting-Host: cogsci.berkeley.edu

In article <1992Aug24.164828.13577@kas.helios.mn.org> rhealey@kas.helios.mn.org (Rob Healey) writes:
>
>	The audio driver has to play a tricky game with DMA timing and
>	I think it's tripping up, especially when other things are
>	using DMA. Say the SCSI interface for example... Can't prove
>	this but it seems like a likely candidate.

The audio device driver that I posted mostly works.  I have not seen
a panic with it even under heavy use (like 20 separate streams pushing
data at it at the same time).

I have noticed that soem of the streams will `hang' and must be interrrupted
but that is not a bad as a panic.

Pax, Keith

Ps, And this `proof of concept' stuff is a bunch of crap.
Newsgroups: comp.unix.amiga,comp.unix.questions,comp.sys.amiga.hardware
From: vrr@cbnewsj.cb.att.com (veenu.r.rashid)
Subject: HELP with fixing corrupted tape
Organization: AT&T
Distribution: usa
Date: Wed, 26 Aug 1992 02:28:22 GMT
Followup-To: poster


I am trying to read a Unix tape onto the hard drive,
but the same thing happens every time:  the drive starts
grinding near the beggining of the 'man' package, and
displays a UDE WRP 1 error and 'dd: error reading tape.'

I tracked down the files in /usr/share/catman/1 that had
been read in okay - it went up to 'split.Z' - 'srchtxt.Z'
which is the next file in the line is where the error is
occuring..

Is there a way for the tape drive to detect where it is and
read a track at a time, reporting errors until it encounters
a good block?  Using 'mt' or 'dd' would be a first guess, but
I don't have the man pages for those commands ;)  There are
some files in the /tmp directory which seem to contain file
information for each package.


/tmp:

List
Version
.
.
man.cont
.
.
.
other files correspoding to the packages on tape


Apparently the cont file contains a list of the files in each package stored
on the tape in the form of the line below:


/usr/share/catman/1/srchtxt.Z f none 0644 root root 3497 5371 700442356 man

where 3497 is the size of the file and I don't know what the 5371 is (checksum?)
I won't even guess what the large number is.. (block number on tape ?), but it
seems fairly consistently the same number for a number of files, and then
changes every 130k (128k ?) or so bytes in the file size(s).

Any step by step method to do the above:  (a) ascertain the position on tape
where the problem occurs (b) read bad tracks until finding a good one and
(c) taking the difference and writing 0s on a second (good) tape  will be
appreciated.  C source code with low-level scsi commands will be appreciated
even more :)

Last but not least, the tape needs to be able to read past the bad track.
If this were the case, I could load the rest of the packages.  However,
'amixpkg' refuses to read past the position on the tape where the media
defect occurs.  :<



Please email suggestions to vrr@cbnewsj.att.com


Thanks very much,
Veenu

vrr@cbnewsj.att.com



Newsgroups: comp.unix.amiga
From: abeech@kraken.itc.gu.edu.au (Adrian Beech)
Subject: The Domain Name Service (DNS)?
Keywords: AmigaUNIX, DNS
Organization: ITC, Griffith University, Brisbane, Australia
Date:  1 Sep 92 04:51:38 GMT

Has anyone managed to get the DNS hostname resolver to work?  I've
tried to setup my machine as a server/client according to the info
in the AT&T SVR4 Networking book, however the machine takes a long
time warm/cold boot.  I also get messages like "Connection refused"
when I try doing such things as telnet, ftp and rlogin.  The messages
appear even when I trying to "telnet localhost".

Can anyone help.


-- 
Adrian V. Beech                              E-MAIL: A.Beech@ext.gu.edu.au
Newsgroups: comp.unix.internals
From: mstehr@lascar.puc.cl (Martin Stehr)
Subject: Monitoring ethernet segment using PROMISC mode
Organization: Pontificia Universidad Catolica de Chile
Date: Tue, 25 Aug 1992 21:37:23 GMT


Hi,

	I' am currently working on my thesis constructing some kind of
active network monitoring system. Actually the system is collecting 
information from multiple hosts, obtaining about each host kernel info
like job queues, disk I/O, context switches, device interrupts, page 
faults, swapping, etc. Also it can get info about for exampe TCP bytes 
and packets I/O on that host. The active part of the system is going to
be used experimentally in order to create some loads on some hosts or
between two of them, laying on the same or different ethernet segments.
The whole is going to be used remotely by other people for tuning or 
testing different configurations for hosts and connections.

	Now I'm searching for some method to obtain general info about
some ethernet segment, so as the *total* number of packets and bytes sent on 
the segment (not only to the specific host where the monitor daemon is
installed), considering all packets at the IP layer.

	I wonder if this could be possible opening a raw socket, setting
the corresponding ethernet device on *promisc* mode and using recvfrom()
to get all the incoming packets.

	I'll appreciate any info about:

1) if that's really possible
2) how does it affect system performance (more device interrupts ?)
3) some simple (?) method of doing the task by some kind of daemon
   installed on the system (I don't want to rebuild part of the kernel !)

	Our system runs a 4.3BSD Unix.

Any help would be appreciated !

Greetings from Chile - Southamerica :)


mstehr@lascar.puc.cl

Newsgroups: comp.unix.internals
From: root@candle.uucp (Bruce Momjian)
Subject: Re: select()/poll() source code posting
Organization: a consultant's basement
Date: Mon, 31 Aug 1992 05:09:50 GMT
X-Newsreader: Tin 1.1 PL5

* UPDATE *

I now have a 9k patch that works in both canonical and raw mode, and
works with the public domain pseudo-tty device driver, as well as the
console, async, and sxt terminal device drivers and pipes.

I don't think this thing has the demand I once thought, so I will not
post the patch.  I ask anyone interested in using or reviewing this to
please e-mail me and I will gladly send it to you.  

I believe the package is basically ready for general use.  I have tested
it with pcomm 2.0 and ptyshl, and both work well.  I do not plan to post
this to a source group because I have not received much interest so far.

Please excuse my use of the bandwidth.

-- 
Bruce Momjian                      |  830 Blythe Avenue
root%candle.uucp@bts.com           |  Drexel Hill, Pennsylvania 19026 
                                   |  (215) 353-9879(w)  853-3000(h)
From: ericb@sierra.com (Eric Blood "intern")
Newsgroups: comp.unix.internals
Subject: SOWEUPC - ???
Date: 27 Aug 92 16:00:05 GMT
Organization: Sierra Geophysics Inc.,  Kirkland, Wa

Going through the man page on ps, I came across a section about flags
dealing with a process.  One of the flags was SOWEUPC with an
explanation of, "Process is owed a profiling tick."

My first question, what is a profiling tick?  My second, why not just
have the scheduler just adjust the priority to move it to the begining
of the queue?

Thanks.

EVB
ericb@sierra.com
Newsgroups: comp.unix.internals
From: sergei@is.morgan.com (Sergei Poliakoff)
Subject: Re: psignal()
Organization: Morgan Stanley - IS
Date: Fri, 28 Aug 1992 14:46:08 GMT

In article <46520025@hpcupt3.cup.hp.com>, aakash@hpcupt3.cup.hp.com (Aakash Sahai) writes:
> boyd@prl.dec.com (Boyd Roberts) writes :
> 
> Signals are intended to kill processes, and are
> not an interprocess communication primitive, although they are often
> misued in this way.

Any device  driver that has a STREAM head sitting atop of it can 
send signal to a process willing to take it.
Sockets are perfectly willing to send signals.
Better non-STREAMS drivers of pre-STREAMS era were notifying
processes with signals.
In the context  of the original posting, signals are used for asynchronous
event notification, rather then IPC .


Sergei
From: guy@Auspex.COM (Guy Harris)
Newsgroups: comp.unix.internals
Subject: Re: SunOS 4.1: can you find out if EMOREIPCS is on?
Date: 25 Aug 92 19:41:38 GMT
Organization: Auspex Systems, Santa Clara

>EMOREIPCS increases the amount of memory allocated to SysV shared memory
>stuff. I'm 100% positive it is NOT a CMU hack because it is in the
>instructions for the postgres installation.

Then maybe it's a Postgres hack, or something, 'cuz I rooted through the
SunOS 4.1 source *and* the SunOS 4.1.1 source, and there ain't no such
option in it....

>You have to make sure you have a kernel with extra-big shm stuff
>allocated in it.

*Definitely* sounds like *somebody's* local hack.  If all you're trying
to do is crank up the number of various SV IPC items, the standard SunOS
way of doing that is to put "options <name>=<value>" lines into the
"config" file, such as

	options	MSGPOOL=N	# message pool size in kilobytes
	options	MSGMNB=N	# default max # of bytes on a queue
	options	MSGMNI=N	# # of message queue identifiers
	options	MSGTQL=N	# # of system message headers

	options	SEMMNI=N	# # of semaphore identifers
	options	SEMMNS=N	# # of semaphores in system
	options	SEMUME=N	# max # of undo entries per process
	options	SEMMNU=N	# # of undo structures in system

	options	SHMSIZE=N	# maximum shared memory seg size in kilobytes
	options	SHMMNI=N	# # of shared memory identifiers

That should be documented somewhere in the SunOS manual set.

It sounds as if somebody hacked up the <sys/{msg,sem,shm}.h> header
files, or "conf.common/param.c", to have one Big Magic Switch to crank
many of those numbers up from their default values; if so, that somebody
doesn't appear to have been Sun....

If you want to know how big any of those *individual* items are, you can
"adb" your "/vmunix" and look at the "msginfo", "seminfo", and
"shminfo" structures to see what the values were set to.  See
"conf.common/param.c", and the aforementioned header files, to see where
you should be looking.
From: mike@pacsoft.com (Mike Stefanik)
Newsgroups: comp.unix.internals
Subject: Re: looking for a way to tell a machines current state.
Date: 26 Aug 92 18:05:16 GMT
Organization: Pacific Software Group, Riverside, Ca.

In article <14272@auspex-gw.auspex.com> guy@Auspex.COM (Guy Harris) writes:
>Err, that assumes you have a system that *has* run levels.  If you don't
>- e.g., if you have a system with a V7-ish or BSD-ish "init" - there
>*is* no current run level to check....

Actually, there are two "runlevels" (ie: single-user, multi-user, and
sometimes there is a third "maintenance mode"), but the catch is that the
init may not record it's state in /etc/utmp.  For those desperate, you
always can resort to trickery (a quick scan through the process table can
give you a clue as to what state you're in... an empty /etc/utmp can also
provide a clue towards this end.)

Is there a portable, consistent, bullet-proof way to check for the current
runlevel, regardless of implementation?  No.  But then it wouldn't be UNIX
if you could, now would it? :-)

-- 
Mike Stefanik  mike@pacsoft.com  ...!uunet!pacsoft!mike
Pacific Software Group, Riverside, CA
Newsgroups: comp.unix.internals
From: cariapa@Tied-House.Stanford.EDU (Sandeep Cariapa)
Subject: Re: How does the command 'ps' work?.
Followup-To: comp.unix.internals
Keywords: ps,kernel addresses.
Organization: EECF, Stanford University
Distribution: na
Date: Fri, 28 Aug 92 22:21:31 GMT

In article <1992Aug21.164844.23113@hubcap.clemson.edu>, rsaripa@venus.cs.clemson.edu (Saripalli Ramakrishna) writes:
|> Hi,
|> 
|> 	I would like to know how the 'ps' command is written.
|> 	I know it probes the kernel addresses.
|> 
|> 	More precisely,I would like to write my own version of 'ps'.
|> 
|> 	What files do I have to open to do this?.
|> 	What are the include files I have to include in my C program?.
|> 

	One good way to get started on this would be to look at some public 
domain programs that do some of the same stuff that ps does. Try a program called 
top. It is a systems monitoring tool, and should be available from uunet, or try 
archie. 

-- 
 Sandeep Cariapa, cariapa@eecf.stanford.edu, (415) 723-1004 (work address)
 System programmer, EECF, Stanford University. 
 Hardware, n.: The parts of a computer system that can be kicked.
Newsgroups: comp.unix.internals
From: boyd@prl.dec.com (Boyd Roberts)
Subject: Re: psignal()
Organization: Digital Equipment Corporation - Paris Research Laboratory
Date: Wed, 26 Aug 1992 10:09:21 GMT

In article <1992Aug25.200550.1862@msuinfo.cl.msu.edu>, jhl@eecae.msu.edu (John Lawitzke) writes:
> I am working on a project which consists of a SCO UNIX device driver and
> a daemon.  The device driver is monitoring for two events within the
> hardware.  When either event occurs, the device driver attempts to send
> a signal to the daemon to inform it of the occurence.
> 

Using signals to communicate events to processes from device drivers
is just a bad idea.  Signals are intended to kill processes, and are
not an interprocess communication primitive, although they are often
misued in this way.
From: jordan@IMSI.COM (Jordan Hayes)
Newsgroups: comp.unix.internals
Subject: Re: psignal()
Date: 31 Aug 92 20:26:38 GMT
Organization: Investment Management Services Inc., NYC

Sergei Poliakoff <sergei@is.morgan.com> writes:

	Sockets are perfectly willing to send signals.

Yes, but they should be "discouraged" from actually delivering them
ie., through SIG_IGN (didn't we have this discussion a few months ago?).

/jordan
From: C.R.Ritson@newcastle.ac.uk (C.R. Ritson)
Newsgroups: comp.unix.internals
Subject: Re: looking for a way to tell a machines current state.
Date: 1 Sep 92 11:06:48 GMT
Organization: University of Newcastle upon Tyne, UK, NE1 7RU

mike@pacsoft.com (Mike Stefanik) writes:

>Actually, there are two "runlevels" (ie: single-user, multi-user, and ...
>For those desperate, you
>always can resort to trickery (a quick scan through the process table ...)

>Is there a portable, consistent, bullet-proof way to check for the current
>runlevel, regardless of implementation?  No.  But then it wouldn't be UNIX
>if you could, now would it? :-)

What I did, as I have a machine with two hard wired terminal ports,
was to look for the existance of the getty (or any other process) with
tty01 (in my case) as its controling terminal. This seemed ok to me.

Chris Ritson.
EMAIL: C.R.Ritson@newcastle.ac.uk       Chris Ritson,
PHONE: +44 91 222 8175                  Department of Computing Science
FAX  : +44 91 222 8232                  University of Newcastle upon Tyne,
TELEX: uk+53654-UNINEW_G                UK, NE1 7RU
Newsgroups: comp.unix.internals
From: jhl@eecae.msu.edu (John Lawitzke)
Newsgroups: comp.unix.internals
Subject: psignal()
Date: 25 Aug 92 20:05:50 GMT
Organization: Michigan State University, East Lansing
Originator: jhl@eecae.ee.msu.edu

I am working on a project which consists of a SCO UNIX device driver and
a daemon.  The device driver is monitoring for two events within the
hardware.  When either event occurs, the device driver attempts to send
a signal to the daemon to inform it of the occurence.

The events being monitored for are few and far between, therefore
signals will work fine.

Now the problem, my testing indicates that the device driver is
functioning properly and the signals are being sent.  The daemon
receives signals fine when I send them via "kill" from the command line.
However, the signals from the device driver never arrive. The daemon is
using sigaction() for signal handling setup.

The device driver functions as follows:

The daemon opens the device and writes an identifying string. 
When the device driver receives the id string, it saves the value of
u.u_procp for future use.
The daemon closes the device.  The daemon now sits in:
	for (;;)
		pause();
When an event being monitored for occurs, the device driver uses the
saved value of u.u_procp to send a signal.

I have throughly tested everything.  Algorithms and coding are correct.
Why doesn't the signal appear at the process?

-- 
John Lawitzke
Manager of Product Management
Dale Computer Corp.
Internet: jhl@frith.egr.msu.edu
From: guy@Auspex.COM (Guy Harris)
Newsgroups: comp.unix.internals
Subject: Re: looking for a way to tell a machines current state.
Date: 25 Aug 92 19:43:21 GMT
Organization: Auspex Systems, Santa Clara

>If your particular box doesn't have the getut(3) suite, it's pretty
>trivial to implement.

Err, that assumes you have a system that *has* run levels.  If you don't
- e.g., if you have a system with a V7-ish or BSD-ish "init" - there
*is* no current run level to check....
From: aakash@hpcupt3.cup.hp.com (Aakash Sahai)
Date: Thu, 27 Aug 1992 17:32:59 GMT
Subject: Re: psignal()
Organization: Hewlett Packard, Cupertino
Newsgroups: comp.unix.internals

> boyd@prl.dec.com (Boyd Roberts) writes :
> 
> Signals are intended to kill processes, and are
> not an interprocess communication primitive, although they are often
> misued in this way.

Oh boy ! I always thought it was the other way round. I wouldn't not have been
able to write several programs without SIGALRM, SIGUSR1 and SIGUSR2. How about
the following signals -

      SIGCLD        death of a child
      SIGPWR        power fail
      SIGVTALRM     virtual timer alarm
      SIGPROF       profiling timer alarm
      SIGIO         asynchronous I/O signal
      SIGWINCH      window size change
      SIGSTOP       stop
      SIGTSTP       stop signal generated from keyboard
      SIGCONT       continue after stop
      SIGTTIN       background read attempted from control terminal
      SIGTTOU       background write attempted to control terminal
      SIGURG        urgent data arrived on an I/O channel

What should a program receiving such signals do ? Get killed :-?

-- Aakash
Newsgroups: comp.unix.internals
From: asw2s@uvacs.cs.Virginia.EDU (Alex S. Waterman)
Subject: Finding the state of a process from a DD.
Followup-To: asw2s@virginia.edu
Organization: University of Virginia Computer Science Department
Distribution: usa
Date: Fri, 4 Sep 1992 13:42:42 GMT

All,
	I have written a device driver for a sun-4, (SunOS 4.1.1),
that communicates between a user and an attached Motorola MVME167
board.  The communication between the sun and the 167 is through
a shared queue structure that resides in vme memory on the 167.
	When the 167 has some data for the sun it places it in
our shared queue and sends an interrupt to the sun.  This all works
fine.  When the sun receives the interrupt he sends a psignal() to
the process who owns this data, the process will then do a read()
to receive it.  
	This is all fine except when the process for one reason or
another has died and therefor can't except the signal.  This data
then sits at the front of the queue waiting to be read from a process
that will never read it.  

	Is there a way to tell if the process that this data is intended
for is alive??  I have saved the pointer to the proc structure, and from
this can get the pid..  Right now, I am just checking to make sure that
this pid is the same as the pid of the process that initiated the first
call to the 167 (that initiated the processing).  It seems there must
be an easier way.  Thanks!


Also, a related question: the device driver manuals state that peek()
and poke() are only to be used from the DD's probe routine.  Is there
a similiar call that can be used to read/write a location from the
other areas of the DD?  Thanks again.

  - Alex Waterman 
Newsgroups: comp.unix.internals