roger@zuken.co.jp (Roger Meunier) (04/22/91)
Simple question. We are running HP-UX 7.03 on our 9000/400's. But 'uname -a' displays the following: HP-UX NODENAME 7.03 B 9000/375 NODENAME ^^^ Is there some reason for making a 400 user think he's running on a 375? -- Roger Meunier @ Zuken, Inc. Yokohama, Japan (roger@zuken.co.jp)
chance@hpfcso.FC.HP.COM (Chance Brohm) (04/24/91)
/roger@zuken.co.jp (Roger Meunier)/ > Simple question. We are running HP-UX 7.03 on our 9000/400's. But > 'uname -a' displays the following: > > HP-UX NODENAME 7.03 B 9000/375 NODENAME > ^^^ > Is there some reason for making a 400 user think he's running on a 375? The primary reason (from what I've been told) is that many 7.x installation procedures rely on the "system type" field to determine the system CPU type. Historically, if the character following the slash is '3' then the CPU is a Motorola-MC680x0; otherwise it's a PA-RISC CPU (or maybe a S500, but that's just noise to this dicussion). The 375 internals are sufficiently similar to the 68030-based Series 400 systems that "backward compatibility" was deemed more important than "truth in advertising." It is my understanding that at HP-UX 8.0 the required effort to make install procedures aware of Series 400 systems has been spent, and therefore uname will return the correct system type (abbreviated to the 8-character limit). For example, a 9000/400t (desktop S400 with 68030 CPU) will return 9000/40T to a "uname -m" command, and a 9000/433s (deskside/server S400 with 33MHz 68040) will return 9000/43S. I'm not positive about these "facts" (or, in truth about ANY "fact") but I'm reasonably confident that this is the case. Hope that helped some, -Chance DISCLAIMER: I speak only for myself. My comments are most likely worth what you paid for them.
paul@eye.com (Paul B. Booth) (04/26/91)
In article <7370379@hpfcso.FC.HP.COM> chance@hpfcso.FC.HP.COM (Chance Brohm) writes: >/roger@zuken.co.jp (Roger Meunier)/ >> Simple question. We are running HP-UX 7.03 on our 9000/400's. But >> 'uname -a' displays the following: >> >> HP-UX NODENAME 7.03 B 9000/375 NODENAME >> ^^^ >> Is there some reason for making a 400 user think he's running on a 375? > >The primary reason (from what I've been told) is that many 7.x installation >procedures rely on the "system type" field to determine the system CPU type. >Historically, if the character following the slash is '3' then the CPU is >a Motorola-MC680x0; otherwise it's a PA-RISC CPU (or maybe a S500, but that's >just noise to this dicussion). The 375 internals are sufficiently similar >to the 68030-based Series 400 systems that "backward compatibility" was >deemed more important than "truth in advertising." > >It is my understanding that at HP-UX 8.0 the required effort to make install >procedures aware of Series 400 systems has been spent, and therefore uname >will return the correct system type (abbreviated to the 8-character limit). >For example, a 9000/400t (desktop S400 with 68030 CPU) will return 9000/40T >to a "uname -m" command, and a 9000/433s (deskside/server S400 with 33MHz >68040) will return 9000/43S. I'm not positive about these "facts" (or, in >truth about ANY "fact") but I'm reasonably confident that this is the case. > It is the case. We're running a "near-final" pre-release 8.0 that correctly identifies a 433s as 9000/43s. Note too, that uname -a now displays the following info: >> >> HP-UX NODENAME B.08.00 B 9000/43s LAN_LLA ^^^^^^^ Where LAN_LLA is the hex link-level address of the lan card. I believe this serves as a machine id which will be used to provide security for the new OS distribution procedures (DAT and CDROM). -- Paul B. Booth (paul@eye.com) (...!hplabs!hpfcla!eye!paul) ------------------------------------------------------------------------------- 3D/EYE, Inc., 2359 N. Triphammer Rd., Ithaca, NY 14850 voice: (607)257-1381 fax: (607)257-7335