HDTenEightyP/NetNews huggingface dataset:
From: lampi@polari.online.com
Subject: Re: Third party disk drives on HP-UX
Organization: R Squared, Redmond, WA (206) 883-3116
Date: Fri, 4 Sep 1992 19:39:05 GMT

In article <1831f7INNsbb@sgi2.mathstat.uoguelph.ca> 
leonardz@sgi2.mathstat.uoguelph.ca writes:
>
>I am trying to install a disk & dat subsystem on an HP 720. It has an internal
>disk at scsi address 6. 
>[...stuff deleted...]
>	Howver, I modified /etc/disktab,/etc/master,/usr/sam/lib/disk_aliases
>	as follows:
>from disktab :
>
>###############################################
>#FUJITSU|M2266
>#   vendor:	FUJITSU
>#   product id: M2266
>#   bytes per block:	   1024
>FUJITSU_M2266_noreserve|FUJITSU_M2266_noswap|FUJITSU_M2266|FUJITSU_M2266_noreserve_noswap:\
>	:no swap or boot:ns#42:nt#15:nc#1644:\

-----I think you'll see better performance with ns#30 and nt#22

>	:s0#1035720:b0#8192:f0#1024:\
>	:se#1024:rm#3600:

Unless you have a fairly special version of this drive (or reformatted it
with 1K sectors), this is a 512-byte sector drive. Anyway, the value for
se# is ignored.

>
>[...stuff deleted...]
>
>	This added the required descriptions of the Fujitsu M2266 disk drive.
>	When I enter sam to add the disk, i go through the menus until i get
>	to the add a disk menu. When I press enter , the message working comes
>	up, lasts for 20-30 seconds, and then the system crashes.
>
>	1 ) Am I doing something oviously wrong ??
>	2 ) If not, how do I get to the system core dump to analyse it and see
>	    what is going wrong?? On some systems , the system memory dumps to
>	    a particular directory, and then upon reboot, you use dbx -?
>	    to analyse the core file. Is there a similar procedure here??

See if you can manually newfs the drive using your disktab entry. Also, check
the major & minor numbers of the device file /dev/rdsk/4s0 (or was that 2s0?--
it's off my screen :-() and make sure they are vali

If these fail, then your disk drive is having trouble.

>	While I am at it, the disk is supposed to be jumpered for asynchronous
>transfer mode. Does the HP 720 not support synchronous scsi, or is it the 
>combination of Fujitsu and HP that won't work in synchrous transfer mode?

The HP 720 doesn't like targets (i.e., disk drives, etc.) to initiate the
negotiations for synchronous transfers. Seems to hang the system. However,
this does NOT mean that the HP 720 doesn't do synchronous transfers with
the disk drives; rather, when the 720 is good and ready it sets up the
negotiations for synchronous transfers with its peripherals.

>--
>						Regards,
>						Len Zaifman
>
>Len Zaifman
>Information Technology Coordinator, College of Physical and Engineering Science
>University of Guelph, Guelph, Ontario. N1G 2W1
>phone : (519) 824-4747 xt 6566 
>email : leonardz@vm.uoguelph.ca , leonardz@Testarossa.cs.uoguelph.ca


-- 
-----
+-+  Michael Lampi       lampi@polari.online.com
|R|  R Squared           16398 NE 85th St., Suite 101, Redmond, WA 98052
+-+                      (206) 883-3116       fax (206) 883-2676
Newsgroups: comp.sys.hp
From: michael@resonex.com (Michael Bryan)
Subject: Re: modify the value of variables in XDB
Organization: Resonex Inc., Sunnyvale CA
Date: Mon, 14 Sep 1992 13:08:47 GMT

In article <ghsu.716481890@critical> ghsu@critical.nswc.navy.mil writes:
>
>   The subject says exactly what I want to do.   The man page for xdb
>does have a section on "Data Viewing and Modification Commands".   But
>there is no command to modify data described there at all.

Use the incredibly-well-documented-intuitively-obvious command:
<note the *heavy* sarcasm above>

        p varname = newvalue

Yes, that's really the "p" command, used for printing values.
Adding the "=" turns it into a modification command.  And it's
oh-so-nice that the "help data" command within xdb doesn't tell
you how to do this.  I forget where I found it, but it's somewhere
in the printed documentation.

We now return you to your regularly scheduled lack of sarcasm...

-- 
Michael Bryan  michael@resonex.com  "Milk and Cheese in '92!"  |     ,_,
"Lovers are like... dentures.  You don't want them in your     |    /oo \
mouth all night, but you sure as hell want them within arm's   |    <>__|
reach in the morning!"  --- Miss Elmira Gulch                  |    |  U|
Newsgroups: comp.sys.hp
From: jhd@irfu.se (Jan D.)
Subject: Re: /usr/prese... corrected.Sorry
Date: Sat, 5 Sep 1992 12:19:10 GMT
Organization: Swedish Institute of Space Physics, Uppsala, Sweden

In article <1992Sep4.104324.10412@vents.uji.es> Enrique Navarro Sanchis <navarro@pereiii.uji.es> writes:
>Hello:
>			I'm working with HP-UX 8.07.
>			There is a directory /usr/preserve.
>			Inside it there is a lot of files named Exaaa<five-digits>.
>			These files (in some cases) are very large.
>
>			Someone can say me something about these files ?
>			What about them ?
>
>			Can you help me,please ?
>			Thanks...

/usr/preserve is where vi and ex saves files when they are exited in
an ungraceful manner. These are the files you see when you do 'vi -r'.

Check who owns these files, and ask the owner to do 'vi -r' to see
if he want's them back. If he doesn't, just remove them.

	Jan D.

Newsgroups: comp.sys.hp
From: jhd@irfu.se (Jan D.)
Subject: Re: CC and /usr/lib/dld.sl
Date: Sat, 5 Sep 1992 12:14:44 GMT
Organization: Swedish Institute of Space Physics, Uppsala, Sweden

In article <7371285@hpfcso.FC.HP.COM> mjs@hpfcso.FC.HP.COM (Marc Sabatella) writes:
>In comp.sys.hp, jhd@irfu.se (Jan D.) writes:
>
>> Thanks for your answer. But I still get this from xdb:
>> 
>> <<<< XDB Version A.08.07 HP-UX >>>>
>> Child died due to: segmentation violation
>> Program died in unknown location (shared library), pc = 0x1000003
>> Ignoring core file "core".
>
>Try running the program under xdb, rather than simply using it to analyze the
>core file.  Then it should at least be able to tell you which library it died
>in.  If it indeed died in libdld.sl, there would seem to be a problem with the
>C++ and/or shared library implementation.  But 0x1000003 is a suspiciously
>bogus looking address; I suspect really the program just did something very bad
>and confused xdb into thinking it had something to do with shared libraries.
>

Yes it indeed did something very bad (actually very, very bad :-).
Found it at last. The error message from xdb got me looking in the wrong place.

Steve Taylor wrote:

        "(shared library)" is simply an 'a priori' best guess as to
        the cause of the problem.  All the debugger really knows is
        "unknown location" (i.e., not an address in the executable's
        text segment) and the value of the pc.

OK, from now on I'll take it to mean
  'you did something bad and the stack got messed up, please check your code'

What happend was that I added a variable to a class, but not all users
of the class was recompiled.

Thanks for your answers,

	Jan D.	(now heavy user of makedepend)
From: mchadwick@galaxy.gov.bc.ca
Newsgroups: comp.sys.hp
Subject: HP and windows NT
Date: 15 Sep 92 10:23:33 -0700
Organization: BC Systems Corporation

Does anyone have any information on what HP is planning to do about Windows NT.
Will Windows NT be able to  run on an HP9000 series as well as or instead of
UNIX ?
From: markd@cup.hp.com (Mark_Donohoe)
Newsgroups: comp.sys.hp
Subject: Re: Disk Array & 2GB HP-UX limit
Date: 14 Sep 92 23:39:27 GMT
Organization: Hewlett-Packard
X-Newsreader: Tin 1.1.3 PL5

lampi@polari.online.com wrote:
: In article <BuBwMI.MFC@cup.hp.com> markd@cup.hp.com (Mark_Donohoe) writes:
: >Raj PUBALA (klitd@hpsgm2.sgp.hp.com) wrote:
: >: Looking at the HP Disk Arrays data sheet, I see that with four disk drives
: >: in the array, we offer 5.4 GB of storage. 
: >: 
: >: I also read about the LVM (Logical Volume Manager) in HP-UX 9.0, which 
: >: says the size of a LV is still limited to 2GB which is the HP-UX
: >: system limitation.
: >: 
: >
: >Yes, I have configured the LVM to be a 3.9Gig file system on HP-UX
: >9.0.  BTW, 4gig is the bigest that HP-UX can support at this time,
: >(you actually end up with a little less than 4 gig because of LVM and
: >other over head.)  It will take 64 bit pointers to address more in the
: >file system.
: >
: Why would it take 64 bit pointers to address >4GB file systems? After all,
: we're not necessarily talking about >4GB *files* (which would require
: such pointers), we're talking about >4GB *volumes*. It's really a stupid
: limitation that should have nothing to do with the 32 bit limit of
: pointers. After all, we're not talking about a pointer based from the
: beginning of the logical volume when we address the contents of a given file.
: 
: Or are we? :-)
: 
I don't think it is reasonable to limit files as such.  If you need >4Gig
then you MIGHT just have a file bigger than 2gig, in which case you need the
larger pointer.  Secondly, as hinted at, it is IMHO better to have a general
solution that does not restrict things.  What you suggest is that you could
support a file system greater than 4gig, but no file could be bigger than
2gig....not very general if you ask me.  Especially since memory will be
greater than 2gig very soon (think of a >2gig OS core dump to wade through!).

anywho, that is what is supported now and possible.  Thought the original
poster might want to know.
--
Mark Donohoe (markd@cup.hp.com)
Newsgroups: comp.sys.hp
From: davidb@zeus.ce.washington.edu (David W. Barts)
Subject: Re: cable curiosity
Organization: University of Washington
Date: Wed, 9 Sep 1992 18:04:35 GMT

In article <1720035@hpbbi4.BBN.HP.COM>, tay@hpbbi4.BBN.HP.COM (#Michael Taylor) writes:
> > This is just a curiosity....
> > 
> > Why doesn't the power cable have screws/locks of sorts to hold
> > it in place?  
> 
> And this is just a guess, but I think it may be because we are using
> "standard" power cords which don't have such a feature.

No, no, no.  The real reason is The First Law of Connectors (FLC), which
states:  "The ease with which a connector can be accidentally dislodged
is directly proportional to the importance of the connection."

Thus, serial RS-232C cables (which only clobber one user if dislodged)
are equipped with screws that are capable of securing the connection
beyond the shadow of a doubt.

Parallel printer cables affect a system-wide service, and are thus more
important than serial cables.  So parallel cables use wire-spring
latches, which offer a slightly higher chance for accidental
disconnection.

SCSI connectors are also important, so they use plugs identical to
those on parallel printers, except for the socket on the back of the
CPU, which, because it is the most important connector, uses a
flimsier snap-latch mechanism to secure its miniature connector.

The BNC connectors used for thinwire Ethernet snap on securely, which
appears to violate the Law, but they are easily subject to damage by
cord strain.

The Ethernet AUI cables that connect thinwire repeaters to the backbone
will disrupt a number of machines if accidentally disconnected.  Thus,
they use pathetic little slide latches that do virtually nothing to
guard against accidental disconnection.  Moreover, they are on the ends
of heavy, stiff cable that exerts significant strain on the connection,
further increasing the chances of connection failure.

As someone has pointed out, the most important connector of all -- AC
power -- provides _no_ means for securing the connection.

			     ----------

Of course, some killjoy is bound to point out that HP-IB connectors
(which are often used for critical connections like disk drives)
completely violate the FLC.  Thankfully, these are being phased out for
use on important things like disk drives, in favor of FLC-compliant
SCSI connectors.

:-) :-) :-)

--
David Barts  N5JRN                      UW Civil Engineering, FX-10
davidb@ce.washington.edu                Seattle, WA  98195
From: shankar@sgi.com (Shankar Unni)
Newsgroups: comp.sys.hp
Subject: Re: that HPUX cc compiler
Date: 4 Sep 92 21:44:06 GMT
Organization: Silicon Graphics, Inc.

In article <3939@sicsun.epfl.ch> lecom@slhp1.epfl.ch (Claude Lecommandeur) writes:

>    I have seen this behaviour before, i mistakenly gave the actual structure
>instead of its address as a parameter to a function call and it worked when
>compiled without -O and broke with -O. (it's hard to debug because it works
>with -g). In this case, it is definetely not the optimiser which is broken,
>but the compiler itself. It looks like it tries to be too much clever.

No, it's not - it's doing a perfectly reasonable thing.

You are passing a struct by value to a function whose prototype is not
declared (I'm talking K&R compiles here for the moment). Since that's
a perfectly legal thing to do, the compiler does so. It just happens
that the way the HP compiler does it is to pass in the address of the
structure to the callee, *which is supposed to make a local copy
immediately* (automatically, that is, if the parameter is declared
correctly as a struct by value).

If the target declares it as a struct by reference, you *could* have a
situation where the struct passed by value gets modified by the callee.
As is the case with the fread call.

However, back at the point of call, the optimizer is pretty confident
that the struct is not modified by the call (hey, it was passed by
value, wasn't it?). Which is why it thinks the assignment is
loop-invariant.

In this case, I agree that it may have been wiser to make the copy at
the point of call rather than at the point of entry - that way, the
above program would not have worked either optimized or unoptimized,
and the user would have been alerted.

Still, all these are just ordinary implementation decisions, and just
happen to have odd consequences if you break the rules in a way that
the compiler can't detect.

Answer(s):

  - (pre-ANSI): Lint it once, Lint it twice, Lint it once again....
  - (brave new ANSI world): cc -Aa, *and use those **** prototypes!!*

--
Shankar Unni				E-Mail:	shankar@sgi.com
Silicon Graphics Inc.			Phone:	+1-415-390-2072
From: mike@hpwin052.uksr.hp.com (Mike Croom)
Date: Tue, 8 Sep 1992 08:18:35 GMT
Subject: Re: DAT file archives
Organization: HP PSO - London, England
Newsgroups: comp.sys.hp

Isn't this a task for an incremental?. Have another tape which saves all the
files created/modified since your first backup. I don't know that it deals
with deleted files ( ie remembering that a file had been deleted, it depends
on how directories are handled I guess )
Disadvantage is that you need more than 1 tape and more than 1 recover.

-------------------------------------------------------------------------------
| Mike Croom                       mike@hpwin052.uksr.hp.com                  -
| Financial Services PSO                                                      -
| London UK                        --------------------------------------------
| +44-71-583-6565  TELNET-31 57772 From the country that brought you cricket  -
| VoiceMail +44-344-367538  --------------------------------------------------- 
Newsgroups: comp.sys.hp
From: bell@EKBEXT.sps.mot.com (David Bell)
Subject: screendump for 9000/382 HP-UX 8.0
Reply-To: bell@ekbext.sps.mot.com
Organization: Motorola European Semiconductor Products Sector
Date: Mon, 14 Sep 1992 07:45:22 GMT

I am looking for a screen - saver for a 9000/382 HP-UX 8.0.

I know that when X windows is being run that it will blank out, but it would
appear not to do so under plain old UX. Is there such a beast ?

Whilst I am here , can anyone tell me why ...

> ekbhp5 62: w
>   8:37am  up 2 days, 19:07,  2 users,  load average: 1.00, 1.01, 1.01
> User     tty           login@  idle   JCPU   PCPU  what
> Segmentation fault

Dave

-- 

Disclaimer: "Probably"

***************************************************************************
David Bell,                                  Voice: 03552 - 40655
Motorola Semiconductor Products Sector,      Fax:   03552 - 65460	
East Kilbride,                               Email: bell@ekbext.sps.mot.com
Scotland
***************************************************************************
From: aaa@hpuerca.atl.hp.com (Simon Fowler)
Newsgroups: comp.sys.hp
Subject: Re: 9000/345:f77 depends on fileset C ??
Date: 9 Sep 92 17:50:30 GMT
Organization: Hewlett-Packard Company, Atlanta GA

In article <HUT61RL@mailgzrz.tu-berlin.de>, dieh1232@w251zrz.zrz.tu-berlin.de (Rolf Diehl) writes:
> Hi,
> I got my 9000/345 with hpux 7.0 and within the support contract we got an 
> upgrade to 8.0. This upgrade only contained the fileset C_min. When I upgraded
> the fortran compiler to 8.0 the installer complained, that the filetset
> depends on fileset C which is missing. Does anybody know what effect the
> missing fileset C will have? Do I have to buy C?
> Any hints apprteciated. thanks  rolf.

No, you don't have to have C - just go ahead and install. The information about required
filesets is incorrect in the FORTRAN file.

simon
From: stuart@TIVOLI.COM (Stuart Jarriel)
Newsgroups: comp.sys.hp
Subject: user-level threads and OS crashes
Date: 15 Sep 92 22:27:54 GMT
Organization: Tivoli Systems, Inc

Iam interested in the opinions of folks more knowledgeable than I about
what user-level programs should be able to knock out the OS.  I have an
application that runs user-level threads (which may/may not be solid),
and I can consistantly kill the OS with the application.  I am about to
get the core (/tmp/savecore) to see if I can get any more info, but I
really dont know if the OS is supposed to be fully protected from all
user-level programs or not.

Any experts?

stuart
From: aaronf@hpfcbig.SDE.HP.COM (Aaron Friesen)
Date: Thu, 10 Sep 1992 02:32:59 GMT
Subject: Re: Getting the [I]ndicator to watch something other than your mailbox
Organization: HP SESD, Fort Collins, CO
Newsgroups: comp.sys.hp

In comp.sys.hp, smr@hitkw14.pki-nbg.philips.de (S.Riehm) writes:

>One of the icons on the frontpanel is a mail flag. ( indicator )
>It watches your incoming mailbox.
>I wish to add another indicator, which watches for some different
>status files.

From /usr/lib/X11/vue/Vuewm/sys.vuewmrc, the minimum entry in vuewmrc
would look something like:

	<name> [I] @<bitmap1_filename> @<bitmap2_filename>

This will not associate an action with the button, but will provide
you with an indicator.  

Then, from /usr/lib/X11/app-defaults/Vuewm, the associated X resource
would look like:

	Vuewm*<name>*fileName:	<full_path_to_file>

Give it a try.  If you want more information, check "HP VUE System
Administration Manual" for details.  It has all of the details in one
location, instead of spread across man pages and configuration files.

Aaron

-- Standard Disclaimer:  This response does not represent the official
position of, or statement by, the Hewlett-Packard Company.  This
response is provided for informational purposes only and is supplied
without warranty of any kind.  --
From: mckee@fc.hp.com (Bret Mckee)
Newsgroups: comp.sys.hp
Subject: Re: Disk Cache is *disabled* in HPUX clusters. How to enable?
Date: 15 Sep 92 14:56:19 GMT
Organization: Hewlett-Packard Fort Collins Site
X-Newsreader: Tin 1.1.3 PL5

J.P.M. van der Jagt (jeanpaul@duteca.et.tudelft.nl) wrote:

: Is this a HPUX feature???
: Can a disk cache be enabled on HPUX in a cluster environment?
: And what does the kernel do with the many Mbytes of memory allocated for
: itself if it doesn't use that as disk cache?


This is not a "feature".  There are several possible explanations
for what is going on, and the correct one is definitely NOT "the buffer
cache does not work at all in a diskless environment".

First, you don't say what you are doing on the clients.  The hpux 
cache is fully coherent with respect to diskless, so if you are opening the
file read/write, and more than one machine has it open at the same time, 
then all I/O IS done synchronously to preserve the semantics of read/write.  
For normal applications this is not a common occurance (i.e. all executables
are opened read-only)

If that is not the case, you might have experienced an LRU problem.  If 
the two MB file just barely fit into the cache on your standalone machine, 
it is possible that configuring the machine as a diskless server made 
the cache (whose size is based upon the amount of FREE memory) enough 
smaller that the file won't fit.  And with LRU, if it won't fit then
sequential accesses are the worst case :-(.

Please provide more information about your machines (memory sizes,
dmesg, uname -a, a more detailed description of how you are running the
tests, ...)


Bret

---
Bret Mckee

Hewlett Packard 
HP-UX Workstation Development Lab
email: mckee@fc.hp.com
All Rights Reserved.
 
Of course, these are just my opinions...
From: shoe@hpcuhe.cup.hp.com (Jim Schumacher)
Date: Sat, 12 Sep 1992 00:20:12 GMT
Subject: Re: Is there a decent mail utility for HP700?
Organization: Hewlett Packard, Cupertino
Newsgroups: comp.sys.hp


>I'm using a HP720 these days and I love it except for one
>thing - ELM. I'm used to Sun's X version of mailtool and
>I wonder if anyone knows if something like this (i.e. a
>little more user-friendly than Elm) exists?

I use softbench mail. The interface is ok, but it does require
that you have softbench :) 

I have heard of a tool called xmail, but I haven't tried 
it. I was given an internal HP install point and don't know
of the availability outside of HP.

If you get any answers, I would like to hear about them as
well (a posting would be great). 

thanks,

jim shoe
Newsgroups: comp.sys.hp
From: rjn@FC.HP.COM (Bob Niland)
Subject: Re: HP-IB on 720
Date: Wed, 9 Sep 1992 14:30:21 GMT
Distribution: comp
Reply-To: rjn@FC.HP.COM
Organization: Hewlett-Packard/WSY Ft.Collins,CO,USA
X-Newsreader: Tin 1.1scd1 PL4

jeff@dsndata.uucp (Jeff Minnig) writes:
> After doing a little research,  I have come to find that although I
> can add a eisa-based HP-IB card to a 720, the 9127 5.25" diskette
> drive is not supported.  Along with a whole list of other stuff.

1. The 9127A floppy drive is discontinued.  HP no longer sells any 
   5.25-in HP-IB flexible disk drives.

2. If you already own a 9127A, try it.  The CS/80 driver for the EISA
   HP-IB card has been found to work with most CS/80 and SS/80 devices.
   The only known problems were seen on the 7936/37H hard disks.  This
   is not to imply any formal support.

> Does anyone have any pointers to SCSI-based 5.25" floppy drives?

The Apollo stand-alone floppy is still available as HP product number
AADDSFLPABA (really :-) and is SCSI.  I loaned one to the R&D engineer who
owns the Series 700 SCSI driver.  I'll ask him if he'd like to comment on
the state of it's functionality on s700 HP-UX (as I recall, it may not work
before 9.0).  I don't know if we're claiming formal support.

Regards,                                              Hewlett-Packard
Bob Niland      Internet: rjn@FC.HP.COM               3404 East Harmony Road
                CompuServe:  71044,2124               Ft Collins CO 80525-9599
From: vaughan@ewd.dsto.gov.au (Vaughan Clarkson)
Newsgroups: comp.sys.hp
Subject: HP's elm loses messages
Keywords: HP elm bug
Date: 9 Sep 92 19:26:09 GMT
Organization: Defence Science and Technology Organisation, Salisbury, South Australia

We are encountering an insidious bug in HP's implementation of elm (the default
mailer on our system).  It seems that if, after editing a message for delivery,
you hit the 's' button (for send), and then quit immediately, the mail never
gets sent even though the messages 'Sending mail...' and then 'Mail sent!'
appear to comfort the user.

This is an extremely annoying bug, and though I have warned people on our net
about quitting too quickly from elm, mail still gets lost this way.

We're running a cluster with a HP 730 as the server, and HP 720s as clients.
The OS is HP-UX 8.07, although we noticed the bug when we had 8.05 as well.

Has anyone else noticed this bug?  Or, better, know how to fix it?

Cheers
- Vaughan

-- 
Vaughan Clarkson                  ___________     Email: vaughan@ewd.dsto.gov.au
Computer Systems Engineer              |                   Phone: +61-8-259-6114
& Glider Pilot			       ^                     Fax: +61-8-259-5938
     ---------------------------------(_)---------------------------------
Newsgroups: comp.sys.hp