Re: [Bug-wget] Wget 1.13.4 on True64 OSF1 Beta

[Steven M. Schweda]

From: Tim Ruehsen

> He said, his system is
>         OSF1 V5.1 2650 alpha

   Which, I'll guess, is the output from "uname -a".  As I said, here:

>       sizer -v
>
> [...] As usual, showing actual
> commands with their actual output can be more helpful than vague
> descriptions or interpretations.

(The point in showing actual commands with their actual output is, of
course, to reduce the need for the reader to guess.)

   On Tru64, the popular "uname -a" is generally less informative than
"sizer -v".  (Note, for example, the lack of "B" in that "V5.1".)  But,
while my access to other versions is poor these days, these header files
don't seem to have been updated much lately, so I'd guess that the
precise OS version doesn't matter much for the problem at hand.  Also,
for the record, Tru64 "development" has slowed to the point where it's
unlikely that HP will ever again change the version string, so if you
want any detailed version info, then you probably need to do something
like the following to identify the last patch kit which has been
applied:

urtx# /usr/sbin/dupatch -track -type patch_level | grep -i 'patch kit'
Gathering details of relevant patch kits...
Patch Kit 5: T64V51BB26AS0005-20050502 OSF540
Patch Kit 6: T64V51BB27AS0006-20061208 OSF540
Patch Kit 7: T64V51BB28AS0007-20090312 OSF540

Extensive reading may find a marketing name like "V5.1B-3" attached to
Patch Kit 5, "V5.iB-4" for Patch Kit 6, and so on, but I'm unaware of
any way to extract a name like that from the software itself.

      http://h30097.www3.hp.com/unix/v51b5.html
      http://h30097.www3.hp.com/unix/v51b6.html
      http://tru64unix.compaq.com/tru64roadmap.pdf

(Maintaining binary compatibility is easier when you change nothing.)

------------------------------------------------------------------------

   Steven M. Schweda               address@hidden
   382 South Warwick Street        (+1) 651-699-9818
   Saint Paul  MN  55105-2547