HDTenEightyP/NetNews huggingface dataset:
From: gram@aim1.aztec.co.za (Graham Wheeler)
Subject: USL's crap manuals
Organization: Aztec Information Management
Date: Wed, 29 Jul 1992 14:42:21 GMT

This is just a gripe I want to get off my chest. I am seriously questioning
the whole idea of UNIX being an open system. For one thing, you have this
great concept of virtual file systems under SVR4. All very well, but let's
say you now want to write code to support a new file system type. Good luck.
It isn't documented in any of the manuals. There are a number of other
examples, but file systems in particular should be documented (especially
as there are glaring omissions, like no ISO9660 CD-ROM file system type).

My personal gripe is the STREAMS manual. Close on 200 pages that could 
be chopped down to probably about 50. You have to really search for
information, because it is so scattered around the place. Unless you're
writing really trivial stuff, the manual isn't going to have half the
information you need (maybe it does, but try to find it without resorting
to re-reading the whole thing). And how publishers manage to get typos into
source code in this day and age I don't know. The STREAMS manual has an
appendix on debugging that is seriously in need of debugging itself. Take
just one page as an example (D-12):

	cmn_err(CE_CONT,"^DUMP: 0 len data msg %s.0,
			(dir==D_OUT)?"OUT":"IN");

	...
	cmn_err(CE_CONT,"^0UMP: non-data b_cont0);

These are the obvious ones, but it makes one wonder just how much you can
trust these manuals.

GrumbleGrumbleGrumbleGrumbleGrumbleGrumbleGrumbleGrumbleGrumble!!!!!!

Hoo, boy, it's been a bad day 8-(.

-- 
Graham Wheeler                     | "That which is weak conquers the strong,
Software Systems Engineer/Student  | that which is soft conquers the hard."
Aztec Information Management/UCT   | 		Lao Tzu - Tao Te Ching Ch. 78
gram@aim1.aztec.co.za / gram@cs.uct.ac.za 
Newsgroups: comp.unix.programmer
From: dwthoma1@eos.ncsu.edu (DAVID W THOMAS)
Subject: Re: Better way to find out the number of lines in a file
Originator: dwthoma1@c00081-100lez.eos.ncsu.edu
Reply-To: dwthoma1@eos.ncsu.edu (DAVID W THOMAS)
Organization: North Carolina State University, Project Eos
Date: Fri, 31 Jul 1992 04:54:01 GMT


I tried e-mail to you, but it bounced.

You can find out the number of _characters_ with the following code, but
there is no way to count the number of lines except to loop through
the characters and count which are '\n' characters.  All files look
like data to unix.  Unless you store the number of lines at the top or
in another index file, unix is not going to store it for you.  

If your big file has a constant number of  characters per line, then
you could use the following code and divide by the characters per line.


#include <stdio.h>

main()
{
    FILE *fptr;
    int size;

    fptr = fopen("big_file", "r");
    fseek(fptr, 0, SEEK_END);
    size = ftell(fptr);

    printf("the size is %d\n", size);
}

David W. Thomas
dwthoma1@eos.ncsu.edu
Newsgroups: comp.unix.programmer,comp.unix.sysv386
From: erica@wariat.org (Lady of the BitMode)
Subject: I/O of login shell
Organization: Akademia Pana Kleksa, Public Access Uni* Site
Distribution: usa
Date: Wed, 29 Jul 1992 22:01:16 GMT

Hi.

I'm running SVR4. First a very very brief to help along the way.
When a person logins into a unix system the system must first:
1) spawn a getty from teriminal
2)  getty runs login
3) then getty exec users specified shell, resorting to default, usually bourne,
if none specified. 
4) user gets 3 basic file handles:
   stdout 0, stdin 1, stderr 2.

Now, what I  want to do is run a background process that's basically 
listens to file des #1 for a specified key sequence it will then 
wakeup specific processes, that are sleeping in background, and 
susend whatever the user is doing.

I know that the suspensions and wakeups are straight forward but the is
there a nice way for a process to hang around in the background and
listen to file descript. #1 for specific key sequence. I think that
the following code might doit:

#include <stdio.h>
void main( void ) ;
void main( void )
  {
  int fd_in = 1 ;
  for ( ;; ) 
    {
    TOP:
    if ( (read( fd_in, &c, 1 )) && (c  == KEY1) ) 
      {
      /* do whatever */
      }
    }
  }

Then run from command shell like :
$ peekaboo & # run in background

Will this do the job or is there another function,  technique already
proven, or is it just impossible. 

PS: I'm gonna go try the above. I know it's not going tobe a trivial task! :(

Thankyou:

Erica C. Ramsey

QuickBits & Turbo Nets Vroommmmmmmm!!!!
From: 6500mack@ucsbuxa.ucsb.edu (Michael P. Mack)
Newsgroups: comp.unix.programmer
Subject: Re: Better way to find out the number of lines in a file
Date: 30 Jul 92 19:59:50 GMT

In article <1992Jul27.203700.5953@news.eng.convex.com> tchrist@convex.COM (Tom Christiansen) writes:

>From the keyboard of bcschu@skws02.monsanto.com (Brett Schultz):
>:This is kind of similar to the how many files in a directory question, but
>:is there a trick to find the number of lines in a file?
>:
>:The files are big so I don't really want to do a gets loop with a counter
>:unless I have to.

>Well, SOMEBODY has to do it!  

>--tom
>-- 
>    Tom Christiansen      tchrist@convex.com      convex!tchrist

Somebody has done it.  On our system (HPUX 8.0) we have a command
called 'wc' which counts the lines, words, and characters in a file.

This command can also be used to count the number of files in a 
directory using the pipe:    ls | wc


Mike Mack
6500mack@ucsbuxa.ucsb.edu
Newsgroups: comp.unix.programmer
From: etxmesa@eos.ericsson.se (Michael Salmon)
Subject: Re: Better way to find out the number of lines in a file
Reply-To: etxmesa@eos.ericsson.se (Michael Salmon)
Organization: Ericsson Telecom AB
Date: Tue, 28 Jul 1992 08:50:37 GMT

In article <1992Jul27.195754.26812@tin.monsanto.com>, bcschu@skws02.monsanto.com (Brett Schultz) writes:
|> This is kind of similar to the how many files in a directory question, but
|> is there a trick to find the number of lines in a file?
|> 
|> Thanks
|> 
|> Brett
|> 
|> PS
|> 
|> The files are big so I don't really want to do a gets loop with a counter
|> unless I have to.

You certainly shouldn't use gets or fgets for that matter, use read or
mmap and count the number of newlines.

-- 

Michael Salmon

#include	<standard.disclaimer>
#include	<witty.saying>
#include	<fancy.pseudo.graphics>

Ericsson Telecom AB
Stockholm
Newsgroups: comp.unix.programmer
From: nagel@Cigna.COM (Mark Nagel)
Subject: Re: expanding ~'s in a directory name.
Organization: CIGNA FIRST, Irvine, CA
Date: Fri, 31 Jul 1992 18:48:17 GMT

In <1992Jul31.151135.25775@prism.poly.edu> kapela@prism.poly.edu (Theodore S. Kapela) writes:

>In article <MJN.92Jul31043705@pseudo.uucp> mjn@pseudo.uucp (Murray Nesbitt) writes:
>>
>>In article <1992Jul29.012629.14000@gucis.cit.gu.edu.au> aroll@gucis.cit.gu.edu.au (Ashley Roll) writes:
>>
>>>My problem is how do I expand ~'s. I want to expand then the way that csh does
>>
>>I don't care^H^H^H^Hknow about the csh, but the following should work
>>with sh and ksh:
>>
>>#include <stdlib.h>
>>
>>char *expanded_tilde;
>>
>>    expanded_tilde = getenv("HOME");

>What about ~user instead of just ~?  With csh, I can do something
>like cd ~joeuser/tmp to cd to joeuser's $HOME/tmp.  What your function
>needs to do is check what follows the ~ and act appropriately.  You still
>need to check /etc/passwd for other users.

Try the following:

#include <stdio.h>
#include <pwd.h>
#include <sys/errno.h>

int
tilde(file, exp)
  char *file, *exp;
{
  *exp = '\0';
  if (file)
  {
    if (*file == '~')
    {
      char user[128];
      struct passwd *pw = NULL;
      int i = 0;
      
      user[0] = '\0';
      file++;
      while (*file != '/' && i < sizeof(user))
        user[i++] = *file++;
      user[i] = '\0';
      if (i == 0)
      {
        char *login = (char *) getlogin();
	
        if (login == NULL && (pw = getpwuid(getuid())) == NULL)
	  return (0);
	if (login != NULL)
	  strcpy(user, login);
      }
      if (pw == NULL && (pw = getpwnam(user)) == NULL)
        return (0);
      strcpy(exp, pw->pw_dir);
    }
    strcat(exp, file);
    return (1);
  }
  return (0);
}
-- 
Mark Nagel <nagel@cigna.com>	| DISCLAIMER: Any resemblence of these
Network Administrator		| opinions to those of CIGNA are purely
CIGNA/FIRST			| coincidental.
          (Don't start vast projects with half-vast ideas)
Newsgroups: comp.unix.programmer
From: merritt@climate.gsfc.nasa.gov (John H. Merritt)
Subject: NAWK - ?Diff. printf output order when using a pipe.
Organization: Climate and Radiation Branch
Date: Sun, 26 Jul 1992 03:38:11 GMT

Explain why the following 'nawk' program produces:

---- cut ----
This is the BEGIN section
a b c
1 2 3
x y z
This is the END section
---- cut ----

When run as: 'nawk -f test.nawk test.dat', whereas it produces

---- cut test.out ----
a b c
1 2 3
x y z
This is the BEGIN section
This is the END section
---- cut test.out ----

when redirected to a file, as in: 'nawk -f test.nawk > test.out'

Here is the program:
---- cut test.nawk ----
BEGIN {
	printf("This is the BEGIN section\n");
}

	{ printf("%s %s %s\n",$1,$2,$3) | "cat" }

END {
	close("cat")
	printf("This is the END section\n");
}
---- cut test.nawk ----

Oh, if it isn't obvious, the contents of test.dat are:
-- cut test.dat --
a b c
1 2 3
x y z
-- cut test.dat --

Now, I guess that there must be some sort of buffering of output
akin to that of the beginner C programming problem of missing '\n' in
printf statements.  I would like to have the contents of the file
that I redirect the output to to be identical to that of the terminal;
that's the confusing part -- they aren't the same.

There is no problem when the pipe is removed.

I want the 'BEGIN' prints to happen before the body prints and
the 'END' prints to happen last -- the order that I programmmed them.
If it is a simple matter of the right 'close' statement, then please
let me know what it is; I've tried 'close(1)' and 'close(stdout)'.

Computer: IRIS 4D/70GT workstation.
OP/SYS  : IRIX 4.0.1
Program : nawk


-- 
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
John H. Merritt --> merritt@climate.gsfc.nasa.gov
"I am generally intolerant of ignorance,
but I have made an exception in your case."
Newsgroups: comp.unix.programmer
From: obi@gumby.ocs.com (Kuryan "Obi" Thomas)
Subject: Re: I am stumped on this one!!!
Reply-To: obi@gumby.ocs.com
Organization: Online Computer Systems, Inc.
Date: Sat, 25 Jul 1992 19:41:20 GMT

In article <Brx394.4qL@undergrad.math.waterloo.edu>,
bbobak@undergrad.math.waterloo.edu (Brad Bobak) writes:
> In article <1992Jul24.204944.18516@cbfsb.cb.att.com>
> rajeev@cbnewsf.cb.att.com (rajeev.dolas) writes:

< Bunch of code deleted >
> 
>  You're allocing the sizeof an int, which is likely four bytes.
>  You also forgot to alloc space for the '\0'. Try it again with:
> 
> 	cp_line = (char*)malloc(sizeof(strlen(pars_wbuf) + 1));
> 

I believe it should read

	cp_line = (char*) malloc(strlen(pars_wbuf) + 1);

that is, leave out the sizeof. I think this is what Brad intended to say;
leaving the sizeof in there results in an allocation of 4 bytes.
Newsgroups: comp.unix.programmer
From: kevinb@dev1.csg.ssd.fsi.com (Kevin Bonifield)
Subject: Re: Mail expiration program needed
Date: Fri, 24 Jul 1992 18:13:23 GMT
Organization: FlightSafety Simulation Systems Division - Tulsa


> I am looking for a mail expiration program to scan each user's system mail
> box and delete the mail which is older than some certain length of time.
> Any input will be appreciated. 

I use a program call "expire" that came from comp.sources.misc a while
back to expire old mail messages on a weekly basis under SUNOS4.1 via cron.
It works quite well.  The sources (current?) are available from ftp.uu.net
under /usenet/comp.sources.misc/volume1/expire.8.Z  -- I do not know
if this is the most current version or not.

//Kevin

----------------------------------------------------------------------------
Kevin Bonifield                        |  Phone: 918-251-0500 x520
Avionics Interface Computer Design     |  Email: kevinb@fsi.com
FlightSafety - Simulator Systems Div   |  
----------------------------------------------------------------------------
From: ratner@ficus.cs.ucla.edu (David Ratner)
Newsgroups: comp.unix.programmer
Subject: Re: bool_t
Date: 23 Jul 92 00:55:50 GMT
Organization: UCLA, Computer Science Department

elan@tasha.cheme.cornell.edu writes:

>Help!  Where's the def of bool_t?  Thanks!!

>--
>--------------------------------------------------------------------------
>|  Elan Feingold       |  I got in trouble for my harmless little .sig   |
>|  CS/EE Depts.        |  "virus," so until the computing dept. here at  |
>|  Cornell University  |  Cornell learns to appreicate a joke and stops  |
>|  Ithaca NY 14850     |  being so paranoid, I will have no .sig :(      |
>--------------------------------------------------------------------------

I have the following:

/usr/include/rpc/types.h:#define   bool_t  int

Dave

--
* *  ***  *     *    |   Dave "Van Damme" Ratner
* *  *    *    * *  / \  ratner@cs.ucla.edu
* *  *    *    ***  \ /  
***  ***  ***  * *   |   "Wham Bam, thank you Van Damme!"
From: jmp@moscom.UUCP (Joe Palumbos)
Newsgroups: comp.unix.programmer
Subject: Re: SIGIO & sockets.  is this right?
Date: 28 Jul 92 16:11:09 GMT
Organization: Moscom Corp., Pittsford, NY
X-Newsreader: Tin 1.1 PL3

kwang@zeus.calpoly.edu (Kevin Wang aka The Scarecrow) writes:
: I am trying to use fcntl() to turn on O_ASYNC so that my program
: will receive a SIGIO when any data comes in across any of its sockets.
: However, it doesn't seem to be working.
: 
: system is AIX (yes, yes, I know) V 1.2.1
: 
: Here's how I turn it on:
:  void SIGIO_ON(int sock)
: {
:     int hold;
: 
:     hold = fcntl(sock, F_GETFL, 0);
:     hold = fcntl(sock, F_SETFL, hold | O_ASYNC);
:     if (-1 == hold)
:         {
:         perror("SIGIO_ON");
:         }
:     return;
: }
: 
: 
: and here's the code that's supposed to be interrupted by the SIGIO:
: [.....]


After your fcntl() call to make the socket Async, you need
another call: 

		fcntl (sock, F_SETOWN, getpid());

This will allow your pid (or group; see fcntl(2)) to receive SIGIO.  
-- 
Joe Palumbos	jmp@moscom.com		{rit,tropix,ur-valhalla}!moscom!jmp
From: volpe@bart.NoSubdomain.NoDomain (Christopher R Volpe)
Newsgroups: comp.unix.programmer
Subject: Re: fdclose function? Or something like it?
Date: 21 Jul 92 14:40:58 GMT
Article-I.D.: crd.1992Jul21.144058.18201
Reply-To: volpe@ausable.crd.ge.com
Organization: GE Corporate Research & Development

In article <JWA5Y3@geminix.in-berlin.de>, gemini@geminix.in-berlin.de (Uwe Doering) writes:
|> 
|> You could dup() the file descriptor at the beginning of your routine,
|> then associate this duplicated fd with a stream via fdopen(). At the
|> end of your routine you can fclose() this stream without closing the
|> socket connection because the original fd still holds it open. So
|> after this you can continue to write to the socket from elsewhere
|> in your program via the original fd that was before passed to your
|> routine.

Yep. Why I didn't see this at first I'll never know. 

|> 
|> Hope that helps.

It does. Thanks. And thanks to everyone else who responded via
posts/email.

|> 
|>       Uwe
|> -- 
|> Uwe Doering  |  INET : gemini@geminix.in-berlin.de
|> Berlin       |----------------------------------------------------------------
|> Germany      |  UUCP : ...!unido!fub!geminix.in-berlin.de!gemini

-- 
==================
Chris Volpe
G.E. Corporate R&D
volpecr@crd.ge.com
From: nedele#s@cicb.fr ( Thierry Nedelec - stagiaire CICB (resp. R. Poezart))
Newsgroups: comp.unix.programmer
Subject: Re:How to get GrpName by UsrName ?
Date: 30 Jul 92 07:10:08 GMT
Organization: CICB - Universite' de Rennes I - FR

It now OK for that, I thank all guys who email me.

See ya ...

     ///
__  ///      __  _
\\\/// |\ | |_  | \
 \XX/  | \| |__ |_/  Heaven is where there Amiga is.
From: kapela@prism.poly.edu (Theodore S. Kapela)
Newsgroups: comp.unix.programmer
Subject: Re: expanding ~'s in a directory name.
Date: 31 Jul 92 15:11:35 GMT
Organization: Polytechnic University, New York

In article <MJN.92Jul31043705@pseudo.uucp> mjn@pseudo.uucp (Murray Nesbitt) writes:
>
>In article <1992Jul29.012629.14000@gucis.cit.gu.edu.au> aroll@gucis.cit.gu.edu.au (Ashley Roll) writes:
>
>>My problem is how do I expand ~'s. I want to expand then the way that csh does
>
>
>I don't care^H^H^H^Hknow about the csh, but the following should work
>with sh and ksh:
>
>#include <stdlib.h>
>
>char *expanded_tilde;
>
>    expanded_tilde = getenv("HOME");
>

What about ~user instead of just ~?  With csh, I can do something
like cd ~joeuser/tmp to cd to joeuser's $HOME/tmp.  What your function
needs to do is check what follows the ~ and act appropriately.  You still
need to check /etc/passwd for other users.

-- 
..............................................................................
 Theodore S. Kapela				kapela@poly.edu
 Center for Applied Large-Scale Computing	
 Polytechnic University
Xref: sparky comp.unix.programmer:3947 comp.sys.sun.misc:3357 comp.unix.questions:9464 comp.unix.wizards:3331
From: bjv@shasta.tivoli.com (Brian Vetter)
Newsgroups: comp.unix.programmer,comp.sys.sun.misc,comp.unix.questions,comp.unix.wizards
Subject: register windows and setjmp/longjmp
Date: 27 Jul 92 23:01:31 GMT
Followup-To: comp.unix.programmer
Organization: TIVOLI Systems

I am working on a program that creates its own lightweight threads (must manage
the stacks).  To detect stack overflow, I am using the mprotect() system
call to create a guard page at the end of the stack.  Instead of just dumping
core when the stack overflows, I want to exit the failed thread (the others
get to keep running).

My idea is to use setjmp() at the beginning of each thread to provide a "place"
to come back, and to call longjmp() from the bus error handler.  To do this,
I have to have a separate signal stack (using sigstack() and sigvec()).

The guard page works (I get my bus error), but I can't unwind the stack
using longjmp().  I'm doing this on a Sun4 (ELC), and I suspect that there
is some register window weirdness going on.

The function calling setjmp gets control after the longjmp but it gets a
bus error as soon as it returns to its caller.  The $i7 and $fp registers
are foobar when the function calling setjmp() gets control.  I tried the
#pragma unknown_control_flow for my function but it still doesn't get
the correct $i7 and $fp.  (If I set them to their correct values by hand
in the debugger, everything works ok).

After disassembling the setjmp/longjmp code in the library, I'm wondering
how they ever work with long stack depths with the register windows.

Does anyone know what I'm doing incorrectly?  Or am I faced with a
bug in SunOS (the rev. is 4.1.1)?

Thanks in advance for any help,

Brian Vetter
bjv@tivoli.com
From: moi@icbl.hw.ac.uk (Hakim Dario Nyangamoi Moi)
Newsgroups: comp.unix.programmer
Subject: Mathematical characters/symbols
Date: 29 Jul 92 10:11:42 GMT
Distribution: uk
Organization: ICBL, Heriot-Watt University, Edinburgh



 If you are an experienced X programmer, UNIX programmer, Font developer or are familiar with the   problem of using mathematical symbols in the UNIX system: HP, X Windows etc., could you please give me some suggestions on the following problems:

    a) extracting symbols and characters from a font for use  with other
        write-operations and inclusion in text files. The object of this is 
        to allow mixed-mode typing of text ...

   b) How to assemble bitmap characters into a bitmap distribution format
      (.bdf) font before converting the user-derived font into a server
      natural format or font ( .snf ). The bitmap characters are themselves
      user-derived ...

  NB. There are some fonts in the fonts directory in X Windows which contain
      a range of mathematical characters and symbols. Two examples of these
     are symb24 and math.18x30 fonts.

    Any ideas and suggestions are most welcome, I would be greatful indeed.

    Cheers!
               Moi.

 

 
Newsgroups: comp.unix.programmer
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Better way to find out the number of lines in a file
Originator: tchrist@pixel.convex.com
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
Date: Mon, 27 Jul 1992 20:37:00 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of bcschu@skws02.monsanto.com (Brett Schultz):
:This is kind of similar to the how many files in a directory question, but
:is there a trick to find the number of lines in a file?
:
:The files are big so I don't really want to do a gets loop with a counter
:unless I have to.

Well, SOMEBODY has to do it!  

--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist


Emacs is a fine operating system, but I still prefer UNIX. -me
Newsgroups: comp.unix.programmer
From: cotrozzi@ghost.dsi.unimi.it (Massimo Cotrozzi)
Subject: u_area
Organization: Computer Science Dep. - Milan University
Date: Tue, 28 Jul 1992 11:35:36 GMT

Hi , I need to read the u structure from /dev/kmem.
I tried to find out how to do it but several books didn't help out too
much. Any suggestions ?
thanx 	Massimo
-- 
--------------------------------------------------------------------------------
  /|/|  /| \ /  ! Massimo Cotrozzi  Computer Science Dept. Milan Italy         !
 /   | /-|  \   ! cotrozzi@ghost.sm.dsi.unimi.it      			       !
/    |/  | / \  ! massimo@cdc835.cdc.polimi.it	                               !
Newsgroups: comp.unix.programmer
From: bcschu@skws02.monsanto.com (Brett Schultz)
Subject: Re: Better way to find out the number of lines in a file
Organization: Monsanto Company
Date: Fri, 31 Jul 1992 11:55:31 GMT

dwthoma1@eos.ncsu.edu (DAVID W THOMAS) writes:
: 
: If your big file has a constant number of  characters per line, then
: you could use the following code and divide by the characters per line.
: 
Thanks for the input but unfortunately it doesn't have the same number of
chars per line.


--Brett
From: mlevin@forte.cs.tufts.edu
Newsgroups: comp.unix.programmer
Subject: help me get the HP/UX equivalents of these SunOs calls!
Date: 24 Jul 92 16:09:55 GMT
Article-I.D.: athena.1992Jul24.160955.18581
Distribution: usa
Organization: Tufts University


    I have a huge program written for BSD systems (it runs fine on
SunOs and Ultrix). I want to port it to HP/UX; when I tried to
recompile, I got several problems. I do not have a HP doc set (yet),
so if anyone would email me (at mlevin@presto.cs.tufts.edu) any
information on the HP/UX equivalents to the following BSD issues, I
would be very grateful. Here goes:

1. The macros for the wait3() call don't seem to work. On BSD, I used
an argument of union wait *; it appears that on HP/UX the argument is
an int. Can someone provide an example of a wait3() call on HP/UX
followed by an example of the use of those WT* macros that extract the
status from the wait3() result?

2. What is the deal with openlog() on HP/UX? How does it differ from
openlog() on SunOs?

3. There doesn't seem to be a TIOCNOTTY constant for the ioctl() call.
On SunOs, this constant tells the system you don't want to have a
control terminal for this process. How do you do that on HP/UX?

4. There doesn't seem to be a flock() function. What is it's
equivalent on HP/UX?

5. The constant HO doesn't seem to be defined in curses.h (it should
contain the string which homes the cursor on a particular terminal).
Where is it on HP/UX?

6. There doesn't seem to be a sys_siglist[] (a char ** array with the
names of signals in it). Is there one?

7. There doesn't seem to be a setpriority() call. What is its
equivalent on HP/UX?

8. What function does one use under HP/UX to test for the CPU type (in
order to make sure a program is used only on the CPU for which it is
intended)? What .h file contains the possible CPU type constants?

If anyone knows the answers to any of these questions, please email me
at mlevin@presto.cs.tufts.edu.


Mike Levin
Newsgroups: comp.unix.programmer