Article 16445 of comp.unix.unixware: Path: ptdcs5.al.intel.com!ornews.intel.com!news.jf.intel.com!psinntp!psinntp!psinntp!sed.psrw.com!eff!news.umbc.edu!europa.eng.gtefsd.com!howland.reston.ans.net!newsserver.jvnc.net!netnews.summit.novell.com!netnews.summit.novell.com!sfgfd!gfd From: gfd@summit.novell.com (George F Demarest) Newsgroups: comp.unix.unixware Subject: Re: Is it supported by Novell? (was: Re: unixware on notebooks) Date: 5 Jan 1995 19:56:43 GMT Organization: Novell Lines: 53 Distribution: world Message-ID: <3ehitr$4qs@bird.summit.novell.com> References: <3dgc74$5f0@subway.echonyc.com> <3dgtk3$c1p@hustle.rahul.net> <3eeohe$5gc@jusdnews.fir.fbc.com> Reply-To: gfd@summit.novell.com NNTP-Posting-Host: sfgfd.summit.novell.com X-Newsreader: TIN [version 1.2 PL2] Kevin Brannen (kbrannen@fir.fbc.com) wrote: : Martin Sohnius (msohnius@novell.co.uk) wrote: : : Ronald F. Guilmette (rfg@rahul.net) wrote: : : : I'd just like to throw out a _general_ question and see if one of Novell : : : dudes (maybe Martin) will bite into it. : : : Does Novell _care_ if UW runs or does not run (or if it is useful or not : : : useful) on today's common notebooks? : : : If the answer is yes, they they had better get busy .... : : I am afraid the answer is "no". Apart from the odd UnixWare-specific : : sales person within Novell who like this for a demo, there seems to be : : absolutely NOBODY interested in UnixWare-on-the-laptop. We wouldn't want : : to contradict the Company Chairman, would we? And if it ain't for the : : desktop, then it ain't for the laptop, either. That's my reading of the : : runes, at least. Sorry. UnixWare 2.X *with* PCMCIA ethernet and FAX modem support will be available from third parties as of launch date. Specifically, SiO Technologies will ship UW 2.0 on their laptops with PCMCIA support. They can be contacted at: Sio Technology Inc. 380 Lafayette Street Suite 304 New York, NY 10003 (212) 473-6910 (212) 473-3717 sales@siotech.com As far as PCMCIA support from Novell, the answer is not quite "no" as much as "not yet". It is not a question about not caring about the issue or our users or any such thing. It is a question of development resources and market viability. While 3rd parties like Sio will fill a short-term gap, Novell will deal with the long term issue. Even if it means only modest hardware support at first. I know this is not the answer that many want to hear, but it is better than a plain "no". gfd : Kevin Brannen : -- : work: uunet!csfb1!kbrannen or csfb1!kbrannen@uunet.uu.net : home: kbrannen@metronet.com -- +x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x George Demarest gfd@summit.novell.com UnixWare Prod. Mktg. Mgr. (908) 522-6363 Novell, Inc. +x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x Article 16412 of comp.unix.unixware: Newsgroups: comp.unix.unixware Path: ptdcs5.al.intel.com!ornews.intel.com!ssd.intel.com!uunet!news.mathworks.com!news.kei.com!nntp.et.byu.edu!news.provo.novell.com!uel!andrew From: andrew@novell.co.uk (Andrew Josey) Subject: Re: Unixware and multiple processors Message-ID: Date: Thu, 5 Jan 1995 08:00:30 GMT References: Organization: Novell Europe. Lines: 35 In article , Raymond Shwake wrote: >msohnius@novell.co.uk (Martin Sohnius) writes: > > When might we start hearing about the specific system on which >UW 2.0 SMP is supportable? Martin has mentioned Compaq's ProLiant systems, >HP has suggested their NetServer LM and XU 5/90 will run it. What about >the NCR MP-RAS models? (I know, it's not Intel 1.1 MP compliant, has a >proprietary architecture, etc.) At beta time, Emily posted the following: UnixWare 2.0 (BETA supported hardware) Under Multiprocessor Hardware: AST Manhattan Compaq ProLiant 2000 Compaq ProLiant 4000 Compaq SystemPro XL Corollary Extended C-bus architecture Intel MPS Specification Version 1.1 architecture Olivetti LSX Model 5030 Olivetti LSX Model 5050 Tricord Model 30/40 Tricord PowerFrame ES5000 Unisys U6000/500 Model 20 Apparently there's a Tricord running with 12 CPU's ! -- Andrew Josey, #include Article 16441 of comp.unix.unixware: Path: ptdcs5.al.intel.com!ornews.intel.com!news.jf.intel.com!psinntp!psinntp!psinntp!sed.psrw.com!eff!news.duke.edu!news-feed-1.peachnet.edu!gatech!howland.reston.ans.net!math.ohio-state.edu!magnus.acs.ohio-state.edu!csn!boco.co.gov!not-for-mail From: swcxt@boco.co.gov (Shane Castle) Newsgroups: comp.unix.unixware Subject: Re: Guide to Fixing Man Date: 5 Jan 1995 11:52:05 -0700 Organization: Boulder County Tech Svcs, Boulder CO USA Lines: 625 Message-ID: <3ehf4l$1n37@bcx01.boco.co.gov> References: <199501051810.MAA10890@mail.cs.utexas.edu> Reply-To: swcxt@boco.co.gov (Shane Castle) NNTP-Posting-Host: bcx01.boco.co.gov X-Newsreader: TIN [version 1.2 PL2] In comp.unix.unixware, grass4@fred.fsl.wvnet.edu wrote: >I found out about this in the FAQ and send mail to >kbrannen@metronet.com, but haven't received a copy yet. Does anyone have it and is willing to mail or post. Thanks Here is what I got when I asked for the same thing. -- Shane Castle swcxt@boco.co.gov Boulder County Info Svcs Boulder CO USA -----------------8<----cut here----8<--------------------- Like many others I read about here, I too am used to man pages. However, they have not worked to my satisfaction; :( but in talking with Tech Support, and some work on my own, things are much better now. Thought I'd share... (my turn to give something to the group) My apologies to all you csh users, you'll need to do a little translating for problem 1. [Note: While this has been tested on my system and works there (a PE + SDK), the usual caveats apply: I make no warranties, you're responsible, etc.; though I will *try* to help you if you should get stuck. Also, you should be "familiar" with Unix and be able to be "root" on the system you'll be working on. My advice is to READ THRU THIS ENTIRE DOCUMENT *BEFORE* DOING ANY WORK.] [New note: Part 1 has been revised after consultation with, and much hard work by Martin Sohnius of Novell UK Labs, out the goodness of his heart (which we all deeply appreciate). I haven't tried this script personally, as my man pages work very nicely, but as it was based on my original work, which was based on Martin original Tech Flash, and it appears to cover all the bases, it should work. (Martin has tested it on his system.)] Problem 1: Can't find find all the man pages you think are there? There are 2 simple but important things to do. First, are you using correct "man" program? This is one place where the BSD version *is* the correct one to use. So be sure you're getting correct one. Make an alias, a symbolic link, whatever it takes for you to see the one in /usr/ucb before the one /usr/bin. Second, you need to set your MANPATH environmental variable. Unfortunately, the Tech Flash I was faxed has an error in it :( . The correct thing to do is: # add any of your dirs here too, I added /usr/local/man MANPATH="/usr/share/man /opt/man /usr/local/man `echo /usr/flib/books/*/man`" MANPATH=`echo $MANPATH | tr " " :` export MANPATH They suggested adding it your /etc/profile. The script below will do this automatically. If you don't want this, remove that part. Problem 2: Still can't find some man pages (though now you can see more). Man only recognizes man pages of the form "*.# or *.#?" (where # is a number 1-8 and the ? is a short list of letters). To fix this, they suggest running a small script to create hard links so man will *see* these files. [Now fixed in the script in the script below problem 3.] Problem 3: You have the SDK and you still can't find the Motif man pages. That's because Novell didn't expand the filenames. By default OSF ships them with short names so they can work on systems with the old 14 char filename limit. The files exist, they're just named wrong. [I'm sending this to a guy in the Development group too, so hopefully we won't have to do this next time.] Try doing the following (I just put the scripts in /tmp as I only had to do them once): [Notes from Martin: Anyway, I'll end this with a copy of my current manfix script, which incorporates all your ideas. Unfortunately, the MANPATH is now so long that it breaks the rules of ed(1) and ex(1), so I had to fiddle again. I also added a lot of progress report output to keep the users happy, and checks for man/man? pages as well (you'll have to put /usr/ucb/nroff into your PATH to get these).] ============================== cut here ======================== #!/bin/sh # First establish the complete MANPATH MANPATH="/usr/share/man" localman="/opt/man" ## add your own here (space-separated) for dir in $localman do [ -d $dir ] && MANPATH="$MANPATH $dir" done refman=`echo /usr/flib/books/*/man` # get rid of those which don't have cat? or man? subdirectories: for dir in $refman do [ -d $dir ] && ls $dir | egrep '^man[1-8]$|^cat[1-8]$' >/dev/null 2>&1 && MANPATH="$MANPATH $dir" done MANPATH=`echo $MANPATH | tr " " :` export MANPATH # Now edit /etc/profile accordingly # (this is tricky, because replacement strings for ed and ex must be < 256) # (also: csh users must do this for themselves!) [ -w /etc/profile ] && { if grep "^# MANPATH " /etc/profile >/dev/null 2>&1 then # remove what's there ex -s /etc/profile <<-!! /# MANPATH /-1 .,+4d w q !! fi echo >> /etc/profile "\n# MANPATH added on `date`:\n" echo MANPATH="$MANPATH\nexport MANPATH" >> /etc/profile echo New MANPATH written to /etc/profile\\n } # Create extra links for files with "bad" extensions list="1[!bcgmprsvw] 2[!bvw] 3[!bcfjklmnprsvwx] 4[!bfmnpsv] 5[!bv] 6? 7[!bv] 8[!bcsv]" echo Looking for bad extensions... for area in `echo $MANPATH | tr : " "` # watch those quotes do cd $area echo in $area for section in $list do for src in cat[1-8]/*.$section man[1-8]/*.$section do target=`expr $src : "\(.*\)."` [ -f $src -a ! -f $target ] && { echo $src "->" $target ln $src $target } done done done # Then expand the motifref stuff [ -d /usr/flib/books/motifref/man/cat3 ] || exit 0 echo \\nExpanding motif ref file names... cd /usr/flib/books/motifref/man/cat3 list=`echo *.3` for src in $list do target=`col -b < $src | nawk ' BEGIN { split(filename, ext, ".") } /X/ { split($1, name, "("); printf "%s.%s\n", name[1], ext[2]; exit; } ' filename=$src ` [ "$target" ] && if [ -f "$src" -a ! -f "$target" ] then echo $src "->" $target ln $src $target else printf "%-40s--- OK\n" $target fi done ============================== cut here ======================== While you're running this, if you see some errors like: "Error: can't move Core.3 to Core.3", this is because it already has the correct name. It's an error you can ignore. This is a use once and throw away script; no need to save it. (I hope! :-) Problem 4: While using man, you notice that some of the lines are cut. This is because you're using the PAGER "more". If you change PAGER to "pg" this problem will be fixed; but now you'll lose the the text attributes like highlighting, underlining, etc. It has been reported (though I haven't checked) that "less" will work properly in both areas. In a future installment, I'll give a script/program for creating the whatis database (I really miss apropos or man -k). I'll try to make it a script as I realize some folks don't have a compiler. Kevin =============================== This is part 2 of "Tips to make man pages better to use..." I had said part 2 would be how to create the whatis database, but that will be postponed for a short time. In this installment, I'll discuss putting the Xt and Xlib man pages in place (so these can be included in the whatis file). These man pages are not supplied, that I could find. If they are, would someone please tell me where (I could not find them anywhere under /usr/flib.) This fix assumes you have an X11R5 build tree; if not sorry, you have to get it first before you do the stuff below (see ftp.x.org or any of its mirrors). If you've done a build, you'll find a man dir (with the bin, lib, include, ...) at the same level as src (or at least it is for me :-). If you just have the source, you'll need to "build" the man pages. In this man dir, you'll find 2 dirs: man3, mann. Then I did the command below. Note: the XSRC below is the dir where that contains the man dir mentioned in this paragraph. Note: you need to be root to do this. =============================== cut here ============================== # I chose to add these in a dir called xintrinsics cd /usr/flib/books mkdir -p xintrinsics/man cd xintrinsics/man cp -r $XSRC/man . # You should now have the dirs like: /usr/flib/books/xintrinsics/man/man3 # and /usr/flib/books/xintrinsics/man/mann # But man doesn't recognize category n, which are really section 1 commands... mv mann man1 # make the cat dirs for later mkdir cat1 cat3 # yes, 777, this is a temporary "cache" type of dir chmod 777 cat? cd man1 # fix a couple of files... vi atobm.n bmtoa.n # or you favorite editor :-) # do this for both files change "mann" to "man1" change ".n" to ".1" # change their names so man can find them for f in * do m=`echo $f | sed -e 's/\.n//'` mv $f $m.1 # and force the expansion of the man pages to create the # whatis database later man $m > /dev/null done # force the expansion here too cd ../man3 for f in * do k=`echo $f | sed -e 's/\.3//'` man $k > /dev/null done =============================== cut here ============================== And you're done...add this dir to your MANPATH, or rerun the script from part 1, and you should now be able to do "man XCreateSimpleWindow", or "man XtSetValues". Part 3 to come shortly, will describe creating the whatis database file for apropos or ``man -k''. As before, feel free to pass this along to whomever, or post in other places. Kevin =============================== This is part 3 of "Tips to make man pages better to use..." This installment describes how to create the whatis database, so that you can use the "apropos" and "man -k" commands. Ideally, UW would have the nroff source for the man pages which would allow us to run the /usr/lib/mkwhatis script (or something like that, maybe it's in /usr/ucb, I'm too lazy to go look just now). However, we don't have that so here's a program to parse the "cat" files (the nroff output) and create the whatis database files from that. I started off trying to create a set of scripts to do this, but alas, the nroff'ed output file parsing was beyond my awk ability. I believe perl could handle it too, but I don't know perl at all. [If someone would like to convert this, I'll be glad to always keep a copy and send it to whomever.] I ended up with a ~200 line C file (source below). For those without a compiler, but who have man pages and want to do this, write me and I'll send you the uuencoded, compressed, executable (I could post it if people prefer, it's only 102 lines long in that form). I tested the program several times (in order to work out the formatting oddities); but did make 1 last change that had only partial testing. You can remove this if you like, but a few man pages will not be included if you do (the change is on line 35, I changed a strchr() to a strrchr(), see note there). The output is not perfect, but pretty close (FWIW, the Sun file I modeled mine after had the same type of formatting problems I did, so I don't feel so bad. :-) There is no makefile, the default rules suffice. There is no Imakefile, I only expect it to run on UnixWare, and the program is too simple. There is a controlling script again. Notes for it are in the first few lines. Unlike the scripts from part 1 that only ever need to be run once, you may want to keep this script and program for when you add new man pages later. [Note: I periodically rerun this. I set my MANPATH to be just "/usr/local/man" to skip all the system stuff that hasn't changed and get just the new stuff that has (because /usr/local is where *I* put all the software I download, your dirs may vary).] =============cut==============cut===============cut==============cut========= #!/bin/ksh # mymkwhatis script # Notes: # ------ # you need to be root # # you need your MANPATH to be as complete as possible # # any man page that has a "type" of more than 5 letters will be ignored # (e.g. 1m is 2 letters) # # any man page that doesn't have a description will be ignored (e.g. xsysstats # does not; the proper format (to add) would be: # NAME # xsysstats - show system statistics as a set of line graphs ### list=`echo $MANPATH | tr : " "` for d in $list do echo $d out=`dirname $d` out=`basename $out` # if you want to inspect a local copy of the output #mkwhatis $d 2> e.$out | sort -u > i.$out #cp i.$out $d/whatis mkwhatis $d 2> e.$out | sort -u > $d/whatis done =============cut==============cut===============cut==============cut========= The important part of the above script is the mkwhatis program. It reads a man dir, which should contain some cat? dirs, and creats the man/whatis file for each area from all the files in the cat? dirs. [I'm not sure why UW wants a bunch of whatis files instead of 1 big one, but that's what it wants; maybe that's the new SYSV4.2 way--I don't know. I'd love enlightenment :-] The program usage is "mkwhatis man-dir", with error messages and info messages coming to stderr, and the output going to stdout. Note: the "sort -u" is important, especially if you've fixed the Motif man dir from part 1, though other dirs have this problem too. There are 2 basic types of errors: "Broken pipe" is harmless and should be ignored (I do 'fgrep -v "Broken pipe" error_file' to see the real errors--sorry I couldn't get rid of them); and "couldn't process FILE". The program can't process reference files (like the lex[1-5] files) as they aren't man pages. It's also possible the man page has a syntax that it wasn't expecting, so it just throws it out and tries to go on. The important parts of the syntax that I look for are: command(type) command(type) NAME command_name [, more names] - description The program looks for the 2nd type (this last change did this as some of the X commands have very long names and overwrite the 1st); the "NAME" header for a location identifier; command_name(s), the first "-" (to separate the 2 pieces); the description; and a blank line afterwards. The command_name(s) and the description may span multiple lines. The program is "documented in ANSI-C" as a friend of mine would say; I didn't bother too much as it's pretty straight forward. There is a second usage: mkwhatis cat-dir man-page-file ; to check the output of a single file (or debugging :-). =============cut==============cut===============cut==============cut========= /* mkwhatis.c */ /* cc -o mkwhatis -O mkwhatis.c */ #include #include #include #include #include #include #include #include #define MAX_LINE_LEN 1000 /* max length of an input line */ #define MAX_EXT 5 /* max size of a man type extension */ #define NAME_LEN 32 /* normal chars for name on the left side of the output */ #define TAB_SIZE 8 /* normal size of a tab */ #define REASONABLE 20 /* max lines before we abort looking */ #define FALSE (0) #define TRUE (!FALSE) /* get the man page type, e.g. 1, 1m, 2, ..., or return NULL if we can't */ static char * find_type(FILE *fs) { char line[MAX_LINE_LEN + 1]; char *p, *c; int num=0; static char type[MAX_EXT + 1]; p = NULL; do { if (fgets(line, sizeof(line), fs) == NULL) return (NULL); if (++num > REASONABLE) return (NULL); } while ((p=strrchr(line, '(')) == NULL); /* line 35, used to be a strchr */ c = strchr(p, ')'); /* but some man pages would fail */ /* if we found ( and a ) and they're close, then we found it */ if (p && c && (c - p <= MAX_EXT + 1)) { p++; *c = NULL; strcpy(type, p); return (type); } else return (NULL); } /* find the name and description, or return NULL on error */ static char * find_name(FILE *fs, char **description) { char *dash=NULL, *name=NULL, *descr, *err, *p; int found_marker=FALSE; char line[MAX_LINE_LEN + 1]; int num=0, len; static char buffer[10 * MAX_LINE_LEN + 1]; /* buffer is where we store everything, and return pointer into */ buffer[0] = NULL; while ((err=fgets(line, sizeof(line), fs)) != NULL) { if (found_marker) { /* found the terminating blank line */ if (line[0] == '\n') break; /* remove the \n */ line[strlen(line) - 1] = NULL; /* try to make adustments before catting */ len = strlen(buffer); if (len > 0) { /* if we're past the 1st dash and find any more at the end of a line, remove the hyphenation that nroff added, so we don't have words like "chan- nel"; else append a space */ if (dash && (dash != buffer + len - 1) && (buffer[len - 1] == '-')) buffer[len - 1] = NULL; else buffer[len] = ' ' , buffer[len + 1] = NULL; } /* remove beginning whitespace & cat */ for (p=line ; *p && isspace(*p) ; p++) /* nothing */ ; strcat(buffer, p); /* store the position of the 1st dash */ if (dash == NULL) dash = strchr(buffer, '-'); } else if (strstr(line, "NAME")) found_marker = TRUE; if (++num > REASONABLE) return (NULL); } /* while */ if (err == NULL) return (NULL); /* change all tabs into spaces, I wish nroff didn't do this */ for (p=buffer ; p=strchr(p, '\t') ; ) *p = ' '; /* split the line into its parts */ name = buffer; descr = strchr(buffer, '-'); if (descr == NULL) return (NULL); *descr = NULL; *description = descr + 1; return (name); } /* parse a potential man file */ static void do_file(char *dirname, char *file) { char filename[MAXPATHLEN + 1]; char command[MAXPATHLEN + 1]; FILE *fs; char *type, *functions, *description; int tabs, len; /* run the file thru "col -b" to remove the attribute chars */ sprintf(filename, "%s/%s", dirname, file); sprintf(command, "col -b < %s", filename); /* fprintf(stderr, "%s\n", command); */ if ((fs=popen(command, "r")) == NULL) { fprintf(stderr, "couldn't open %s\n", filename); return; } /* if we can find all the parts, it a man page, so output something */ if (((type=find_type(fs)) != NULL) && ((functions=find_name(fs, &description)) != NULL)) { /* the format is "command (type) - description" */ len = printf("%s(%s)", functions, type); tabs = NAME_LEN - len; tabs = (tabs < 1) ? 0 : tabs / TAB_SIZE; while (tabs-- > 0) putchar('\t'); printf(" - %s\n", description); } else fprintf(stderr, "couldn't process %s\n", filename); pclose(fs); } /* process an entire cat dir */ static void process_cat_dir(char *path, char *dir) { char dirname[MAXPATHLEN + 1]; struct dirent *direntry; DIR *dirpointer; sprintf(dirname, "%s/%s", path, dir); if ((dirpointer=opendir(dirname)) == NULL) { fprintf(stderr, "couldn't open %s\n", dir); return; } /* for each file, try to process it */ readdir(dirpointer); /* . */ readdir(dirpointer); /* .. */ while ((direntry=readdir(dirpointer)) != NULL) do_file(dirname, direntry->d_name); close(dirpointer); } /* it's the one and only MAIN! :-) */ int main(int argc, char *argv[]) { char *mp, *dirname; struct dirent *direntry; DIR *dirpointer; /* check args, and jump to debugging if needed */ if ((argc < 2) || (argc > 3)) { fprintf(stderr, "usage:\t%s man-dir\n\t%s cat-dir man-file", argv[0], argv[0]); exit(1); } if (argc == 3) { /* debug by doing just this 1 file */ do_file(argv[1], argv[2]); exit(0); } dirname = argv[1]; fprintf(stderr, "doing %s\n", dirname); if ((dirpointer=opendir(dirname)) == NULL) { fprintf(stderr, "couldn't open %s\n", dirname); exit(1); } /* for each cat? dir entry, process it */ while ((direntry=readdir(dirpointer)) != NULL) { if ((strlen(direntry->d_name) == 4) && (strncmp(direntry->d_name, "cat", 3) == 0) && ((direntry->d_name[3] >= '1') && ((direntry->d_name[3] <= '8')))) { process_cat_dir(dirname, direntry->d_name); } } /* while direntry */ close(dirpointer); return (0); } =============cut==============cut===============cut==============cut========= I hope you enjoyed this, or at least found these installments useful. If you have more questions about "man's missing features", write and I'll answer what I can. Kevin Brannen ============= kbrannen@metronet.com Article 17086 of comp.unix.unixware: Newsgroups: comp.unix.unixware Path: ptdcs5.al.intel.com!ornews.intel.com!news.jf.intel.com!psinntp!psinntp!psinntp!sed.psrw.com!eff!usenet.ins.cwru.edu!howland.reston.ans.net!Germany.EU.net!EU.net!uknet!uel!mserv From: mserv@novell.co.uk (Andrew Josey) Subject: Overview of the Novell UK Mail-Server archive Summary: freeware/shareware, binaries/sources ready for UW Message-ID: Date: Sun, 15 Jan 1995 09:40:37 GMT Organization: Novell Europe. Lines: 451 Periodic Overview Posting of the novell.co.uk mail-server archive -------------------------------------------------------------- This is an overview posting describing the contents of the mail-server archive at novell.co.uk (the Novell USG Europe mail-server). The mail-server can be reached as mail-server@novell.co.uk, send a message containing the following text to received this overview document: begin send overview end Requests to the mail-server should be of the format begin end where is typically - send filename This archive contains ports of freely available software to UnixWare. The mail server is available to anyone who has email. FTP ACCESS TO THIS ARCHIVE The information is also periodically copied onto the ftp server in Germany (ftp.novell.de) in /pub/unix/unixware/usle [ftp.novell.de can be reached at 193.97.1.1] Another mirror can be found on ftp.demon.co.uk in /pub/mirrors/novell/unixware. The IP address is 158.152.1.44. Also as of Jan 15, a mirroring operation was underway to reproduce this archive onto netlab1.usu.edu, pub/mirror/usle UnixWare 1.1.2 machine (IP address 129.123.1.43) and netlab2.usu.edu, usle NetWare 3.12 server (IP address 129.123.1.44) These last two mirrors are not as up to date as the first two. [Please note that we don't maintain these ftp sites and can't control their accessibility, we hope to rectify this by putting up our own ftp site in the next 6-8 weeks.] The rest of this article describes the mail-server and its contents. What's Available? ---------------- i) BINARIES This directory mostly contains pre-ported and packaged up UnixWare binaries. Just request the files, read the README (and INTRO) file(s) and pkgadd the package. These software packages follow the ABI conventions for add-on packages and are installed in /opt. It is wise to change the default PATH setting to include /opt/bin in /etc/profile. PATH=$PATH:/opt/bin export PATH If you do not have a /opt, you can create it with the subdirectories /opt/bin, /opt/lib, /opt/man -- you could also use a symbolic link to some other part of disk if you like (for example /usr/local). To make the manual pages accessible to the /usr/ucb/man command set the MANPATH environment variable to include /opt/man, a typical MANPATH might be: MANPATH=/usr/share/man:/opt/man export MANPATH The packages are usually tar archives which should be installed as follows: 1. Extract the tar archive into /tmp. $ cd /tmp If compressed (.Z) then $ zcat package.tar|tar xvf - $ su # pkgadd -d `pwd` Many of the utilities include desktop icons for point and click operation: 2. Installing graphically To install graphically on UnixWare (after you have installed the package) Select the System_Setup icon from the Desktop. Select Application_Setup from System_Setup Wait while the system catalogs the applications Select the package icon from Application_Setup to get to Application_Setup:package_name Select the package icon and Finally click on the Install_to_desktop Selecting Applications from the Desktop you should then see the package icon. Here's a list of what is currently in the BINARIES directory :- Directory Name Description ------------------------------------------------------ agrep Approximate Grep axe-4.1 aXe - Text Editor for X11 bash-1.13.5 Bourne-Again-SHell benchmarks Benchmark Programs bison-1.1 bison - The GNU Compiler Compiler bootselector Utility to select which partition to boot. cnews Archive of Cnews distribution cshar-2.3 Shell Archive Utilities ctwm-2.2 Claude's version of TWM (a virtual window manager) elm-2.4pl23 The Elm Mail System Version 2.4 PL23 elmdocs-2.4pl23 The Elm Mail System User Documentation emacs-19.22 X Emacs Version 19.22 expect3 Expect Dialogue tool faces-1.6.1 faces, the visual list monitor flex flex - fast lexical analyzer generator fvwm-1.24n A Virtual Window Manager for X11 (With Motif-3D look and feel) gawk-2.14 GNU Awk gdb-4.11 GNU Debugger gnuchess-4.0pl65 Chess Game for X11 (GNU Chess and Xboard) gnudiff-2.0 GNU diff, diff3, sdiff and cmp programs gnufind-3.7 GNU find, locate and xargs programs gnumake-3.69 GNU make gnutar-1.11.2 GNU tar ghostview-2.4 Ghostview - front end to ghostscript gs-2.5.2 GhostScript - Postscript interpreter gs-2.6.1 GhostScript - Postscript interpreter Version 2.6.1 gzip-1.2.4 GNU Zip hpcdtoppm.0.3 Kodak Photo CD to PPM converter. httpd-1.1 Hypertext transfer protocol daemon indent-1.6 GNU indent ispell-2.0.02 FSF/GNU Interactive Spelling Checker ispell-4.0 Interactive Spelling Checker Version 4 kermit Kermit for UnixWare kit-2.0 The Ultimate Mailing Kit lynx Lynx 2.4 - text based WWW browser makepatch-1.6 Utility to generate a patch file metamail-2.7 Metamail - Multipurpose Internet Mail Extensions mosaic-2.4.mrun Mosaic 2.4 (requires motif run-time package) - GUI to the Wolrld Wide Web mpeg_play version 2.0.1. MPEG Video Software Decoder mtools-2.0.7 Mtools - tools to manipulate files on MSDOS filesystems mush-7.2.5 Mail Users Shell nettools Internet tools - archie, xgetftp and xarchie (all bundled) nntpd-1.5.11 Network News Transfer Protocol olvwm Open Look Virtual Window Manager oneko Cat chasing Mouse Cursor patch-2.0.12u8 Patch Utility pax-1.1 Portable Archive Exchange pbmplus10dec91 PBMPLUS - Extended Portable Bitmap Toolkit perl-4.0pl36 Practical Extensible Report Language (Version 4 PL36) perl-5.000 Perl Version 5.000 pine-3.91 Pine Mailer Version 3.91 pop3-2.0 POP3 Server - Post Office Protocol Version 3 plan-1.1.2 plan - an X/Motif day planner rxvt-1.93 A light weight XTerm (VT100 emulator) screen-3.2 Screen Window Manager seyon-2.0.6 X11 Telecommunications Package SML-0.93 Standard ML 0.93 sox SOX Audio converter tool syslog A sample package to setup syslogd logging on UnixWare 1.x tcl-6.4 Tool command language tcltools A collection of tcl-7.3, expect-5.12 and tk-3.6 tcpwrap TCP Wrappers for UnixWare 1.x tin-1.22 TIN NewsReader Client (also nntp capable binaries) transfig-2.1.6 Facility for Translating Fig code t3d-1.0 3D Clock uwdialer UnixWare X11 Comms Utility including z/y/z/modem voxware voxware 2.5 sound driver xaw3d-0.6B 3D Athena Widgets (give those old apps an up to date look) xbmbrowser-2.0 XbmBrowser - X Bitmap Browser Tool xcalendar-3.1 Calendar Accessory for X11 xcoral-1.76 XCoral C, C++ Browser xdiary Diary Accessory for X11 xditview X Window System Display ditroff DVI files xfig-2.1.7 Facility for Interactive Generation of figures under X11 xfishtank X11 Swimming Fish background xgrabsc-2.2 X Screen Grabber xgopher-1.3 X11 Gopher Client xinvaders-2.0 X Window System XINVADERS Game xjewel Jewel game for X11 xman X Window System Manual Page Display Program xmandel Mandelbrot and Julia set xmine-1.0.3 xmine game xmris-3.03 XMRIS Game for X11 xpaint-2.0pl3 Paint Tool for X11 xpm-3.2g X-Pixmap support xrn-6.17 X11 News Reader (built statically with xaw3d) xtimex-1.95 X Timesheet keeper xswarm2.3 XSwarm xsysstats-1.0.1 X Window System Status Display xv-2.20 XV - Interactive Image Display for the X Window System xv-3.00 XV - Interactive Image Display for the X Window System ii) DRIVERS/X This directory contains betaX, the latest cut of the video drivers. README.betaX betaX.pkg The DRIVERS directory contains the latest additional driver set (hba's and lan drivers) for UnixWare - this is mirror'd from ftp.novell.com. To get an index send DRIVERS/00Index iii) HINTS This is a directory of various and wide-ranging hints+tips. Please feel free to mail the mail-server administrators (mserv@novell.co.uk) if you wish to make an addition to this list. Some of the most popular hints file are listed below, together with the mail-server request to obtain the file(s): + FAQ This includes the most recent copy of the comp.unix.unixware frequently asked questions file: send HINTS/FAQ/comp.unix.unixware.FAQ + MAIL Various help files and technical tips for setting up and troubleshooting electronic mail on UnixWare send HINTS/MAIL/README send HINTS/MAIL/Howto_setup + Networking Various hints and tips on networking related topics: - How to setup UnixWare as an anonymous ftp server send HINTS/Networking/anon-ftp - Tips on setting up PPP send HINTS/Networking/ppp send HINTS/Networking/ppp-UW-solaris send HINTS/Networking/ppp.comp.u.unixware - Setting up serial communications on UnixWare send HINTS/Networking/serial-comms - Setting up DNS send HINTS/Networking/DNS/HOWTO.DNS send HINTS/Networking/DNS/dns.README send HINTS/Networking/DNS/dns.tar.Z send HINTS/Networking/DNS/dnstools.shar - Setting up a bootp server send HINTS/Networking/bootp/README send HINTS/Networking/bootp/bootptab.sample send HINTS/Networking/bootp/rfc1048.txt send HINTS/Networking/bootp/rfc951.txt + Faxback A snapshot of the current UnixWare faxback documentation is held on the mail-server. To get the index send HINTS/Faxback/INDEX + Uucp Uucp tips and hints send HINTS/Uucp/debugging send HINTS/Uucp/serial-comms send HINTS/Uucp/uucp.faq + Netnews Hints on setting up a netnews server using Cnews send HINTS/Netnews/netnews.readme send HINTS/Netnews/guide.ps.Z + Xwindows/Motif Various X Window System hints and sample configuration files send HINTS/Xwindows/sample.fvwmrc send HINTS/Xwindows/sample.mwmrc send HINTS/Xwindows/sample.olinitrc send HINTS/Motif/mwm + Papers Various technical white papers etc An extract of the desktop integration manual for developing GUI based applications with desktop icons and class databases. send HINTS/Papers/novuk/UWdesktop_int.ps.Z Some docs retrieved from the ui.org archive in 1993. These are "as is". Please read the copyright notices within the documents. dlpi.ps - Data Link Provider Interface Revision 2.0.0 Dated Aug 20 1991 dwarf.v2.d4.ps - DWARF Debugging Information Format V2 Draft 4 Oct 12,1992 (unapproved draft) npi.ps - Network Provider Interface Specification, Rev 2.0.0 (Aug17/1992) tpi.ps - Transport Provider Interface Rev 1.5 (Dec 10/1992) send HINTS/Papers/ui/dlpi.ps.Z send HINTS/Papers/ui/dwarf.v2.d4.ps.Z send HINTS/Papers/ui/npi.ps.Z send HINTS/Papers/ui/tpi.ps.Z + The full HINTS index can be obtained as follows: send HINTS/HINTS-INDEX iv) MIRRORS The mirrors directory contains copies of other sites which contain UnixWare related material. Be careful when requesting information from this tree since it is often not quite up-to-date with our sources and binaries. However, official fixes tend to get to ftp.novell.de (devnull.novell.de) before we do. v) SOURCES This contains the sources which created the packages in BINARIES plus some other sources which have not been packaged up. This currently contains :- Mosaic2.1.tar.Z patch-2.0.12u8.tar.Z xdaliclock.tar.Z README pax-1.1.tar.Z xdiary.tar.Z SML-0.93.tar.gz pbmplus10dec91.tar.Z xditview.tar.Z SOURCES-INDEX perl-4.036.tar.Z xdu.tar.Z XpoolTable1.2.tar.Z perl-4.0pl35.tar.Z xfaces-2.2.tar.Z aXe-4.1.tar.Z perl5.000-doc.ps.gz xfedor.tar.Z agrep.tar.Z perl5.000.tar.gz xfig-2.1.6.tar.Z archie.tar.Z pine-3.91.tar.gz xfig-2.1.7.tar.Z bash-1.13.5.tar.gz plan.tar.Z xfishtank.tar.Z bind-4.9.tar.gz popper.tar.Z xfractint-2.01.tar.Z bison psutils.tar.Z xfsm.tar.Z bison-1.22.tar.Z readline-1.1.tar.Z xgetftp-v2.0.tar.Z bootptest.tar.Z rxvt-1.93.tar.Z xgopher.1.3.tar.Z btoa.tar.Z saytime.tar.Z xgrabsc.2_2.tar.Z cnews.tar.Z screen3.2.tar.Z xinvaders2.0.tar.Z crashme.tar.Z seyon-2.0.6.tar.Z xjewel.tar.Z cshar-2.3.tar.Z sox.tar.Z xless-1.4.1.tar.Z ctwm.tar.Z startx.tar.Z xlock2.3.tar.Z diff-2.0.tar.Z sunclock.tar.Z xman.tar.Z elm-2.4.23.tar.Z swisswatch.tar.Z xmandel.tar.Z emacs-19.22.tar.gz t3d.tar.Z xmcd.tar.Z expect-5.12.tar.Z tarmail.tar.Z xmfm.tar.Z expect.tar.Z tcl.tar.Z xmine.1.0.3.tar.Z find-3.7.tar.Z tcl7.3.tar.Z xmoontool.UW.tar.Z flex-2.3.7.tar.Z tcpdump xmris3.03.tar.Z fvwm-1.24n.tar.Z texi2roff.tar.Z xpaint2pl2.tar.Z gawk-2.14.tar.Z timex-1.95.tar.Z xpaint2pl3.tar.Z gdb-4.11.tar.gz tin-1.20.tar.Z xpeg1.0.tar.Z gnuchess-4.0.pl60.tar.Z tin-1.22.tar.Z xpgs.tar.Z gnumake-3.69.tar.Z tk-3.0.tar.Z xphoon.tar.Z gs261.tar.Z tk3.6pl1.tar.Z xpm-3.2c.tar.Z gzip-1.0.7.tar.Z transfig-2.1.6.tar.Z xpm-3.2g.tar.Z gzip-1.2.4.tar.Z trn-3.4.1.tar.Z xpostit.tar.Z httpd_1.1-docs.tar.gz trn.tar.Z xrn-6.17.tar.Z httpd_1.1.tar.Z uemacs-3.7.1.tar.Z xroach.tar.Z indent-1.6.tar.Z uwdialer-1.0.tar.gz xrolodex.UW.tar.Z ispell-2.0.0.2.tar.Z wscrawl2.tar.Z xscreensaver-1.18.tar.Z ispell-4.0.tar.Z wu-ftpd-2.4.tar.Z xswarm-2.3.tar.Z kit-2.0.tar.Z x11fish.tar.Z xsysstats-1.0.1.tar.Z lsof_3.08.tar.gz xaniroc.tar.Z xtacho.tar.Z makepatch.tar.Z xarchie-2.0.9.tar.Z xteddy.tar.Z metamail-2.7.tar.Z xaw3d-0.6B.tar.Z xterm.tar.Z mosaic-2.4.tar.gz xbmbrowser2.0.tar.Z xv-2.20.tar.Z mpack-1.4.tar.Z xboard-2.0.pl25.tar.Z xv-3.00.tar.Z mtools-2.0.7.tar.Z xbomb.tar.Z xvi.tar.Z mush-7.2.5.tar.Z xcalendar-3.1.tar.Z xwave.tar.Z ncftp170.tar.Z xco.tar.Z xworm.tar.Z nntp-1.5.11.tar.Z xcolormap.tar.Z zoo.tar.Z nntp-t5.tar.Z xcoral173.tar.Z nov.tar.Z xcpustate.tar.Z vi) TET The TET directory contains documentation and sources for the Test Environment Toolkit (TET, dTET2 and ETET). The directory currently contains :- OLD_ETET_RELEASES etet1.10.3.kpl tetguide1.7.ps.Z README etet1.10.3.readme tetguide1.7.shar.Z dtet2pguide.ps.Z etet1.10.3.tar.Z tetguide1.7.troff.Z dtet2pguide.troff.Z etet_relnotes.ps.Z tetspec4.5.ps.Z dtet2uguide.ps.Z etetguide.ps.Z tetspec4.5.shar.Z dtet2uguide.troff.Z etetguide.troff.Z tetspec4.5.troff.Z etet.slides.tar.Z faq vii) UPDATES This directory is for UnixWare updates - check out the README Update Tree ----------- This update tree is a collection of the various updates which have been produced by Novell. Structure --------- Here you will see the following :- UW1.0 Updates suitable for UnixWare 1.0 only UW1.1 Updates suitable for UnixWare 1.1 only UW1.1.1 Updates suitable for UnixWare 1.1.1 only UW1.1.2 Updates suitable for UnixWare 1.1.1 only Inside the UW* directories you will see :- OFFICIAL Where Novell's official updates are keps DSE Updates released from Developer Services (Europe) - usually these updates fix a particular issue and will be incorporated into the next official update. Note that the updates are rather large and to facilitate download via email we suggest you read the HOWTO.DOWNLOAD file in each directory. viii) USENET This contains the comp.unix.unixware archive. Further comments. ---------------- If you have any comments to make on this service please contact the mail-server administrators at "mserv@novell.co.uk". Peter Lord. Andrew Josey. Novell USG Europe. Article 17313 of comp.unix.unixware: Path: ptdcs5.al.intel.com!ornews.intel.com!news.co.intel.com!uunet!pipex!howland.reston.ans.net!newsserver.jvnc.net!netnews.summit.novell.com!netnews.summit.novell.com!news.provo.novell.com!bikini!darrend From: darrend@bikini.USG.Sandy.Novell.COM (Darren R. Davis) Newsgroups: comp.unix.unixware,novell.general Subject: UnixWare BOF session at UniForum '95 Date: 18 Jan 1995 22:49:52 GMT Organization: Novell Inc. Lines: 23 Distribution: world Message-ID: <3fk5ug$bs2@grok.Provo.Novell.COM> NNTP-Posting-Host: bikini.usg.sandy.novell.com Subject: UnixWare Birds of a Feather Session Date: Wednesday, March 15, 1995 6:30 - 8:00 p.m. Room: TBD Chair: Darren R. Davis UnixWare Developer Support Engineer Novell Developer Support The UnixWare Birds of a Feather Session at Uniforum will be held on Wednesday, March 15, 1995, from 6:30 to 8:00 p.m. The meeting room is still to be determined, but will be in the main Uniforum conference area. This session will offer UnixWare users and developers an opportunity to meet with representatives from different UnixWare organizations within Novell, including Development, Marketing, and Developer Support. The session will be an open forum in which participants will be able to see a demo of UnixWare 2.0, ask questions, and discuss technical and non-technical issues pertaining to the product. Darren R. Davis UnixWare Developer Support Engineer Novell Developer Support