Thread View: cu.cs.general
1 messages
1 total messages
Started by Todd C Miller
Tue, 08 Aug 1995 00:00
newpiper -> piper switch
Author: Todd C Miller
Date: Tue, 08 Aug 1995 00:00
Date: Tue, 08 Aug 1995 00:00
129 lines
6183 bytes
6183 bytes
The following message was mailed out on Thu, July 27th but just
in case anyone missed it, here it is again.
- todd
Message-Id: <199507280435.WAA07510@suod.cs.colorado.edu>
To: csfaculty@suod.cs.colorado.edu
cc: csops-fyi@suod.cs.colorado.edu
Subject: "newpiper" going production
Date: Thu, 27 Jul 1995 22:35:16 -0600
From: Lynda McGinley <mcginley@suod.cs.colorado.edu>
Dear Faculty,
As part of our summer activities we are ready to move all faculty onto
your new server purchased by the CER grant over a year ago. This new
machine is an HP 9000/730 which has a faster processor than the existing
piper. HP-UX is a not the same as SunOS so some commands will be a
little different. At the end of this message is a list of possible
"gotchas." User programs that previously ran on piper will need
to be recompiled.
We are planning to make the new machine (currently called newpiper)
the "real" piper on Aug 14th. At this time the old piper (the SUN)
will be renamed "oldpiper." We will officially decommission oldpiper
(the SUN) on August 31, 1995.
You are encouraged to login to newpiper as soon as possible. We'd
like to fix any migration problems before the actual switch-over.
Note that newpiper uses the new filesystem layout (as will all
CSops machines in the near future). This means that many
things that you might expect to be in /usr/local/bin reside
in /Tools/bin and packages that used to live in /usr/local/PACKAGE
now live in /Tools/PACKAGE. Mail was sent out about this change
several weeks ago.
If you have any questions let us know.
thanks & good luck.
CSOps
-------------------------- FAQ ---------------------------------
The following is a list of potential problems/differences users
may encounter presented in a "question and answer" form.
Q) Why is the output of "df" different. It's a lot less useful.
A) This is an svr3-based "df". To get a BSD-style df, use
the "bdf" program.
Q) When I login to newpiper I get an error from "stty".
A) The "stty" command on HP-UX does not support some of the
flags the BSD "stty" supports. You will be unable to
use the following flags: dec new crt
In most cases you can remove these flags and not notice any
difference (when you remove the "dec" flag you may need
to add 'erase "^?"' to the stty line to get the same
erase character). For more info, do "man 1 stty" for
a list of valid options.
Q) When I try to run "vi" or "more" half the screen scrolls by.
A) This should only be a problem if you rlogin or telnet
to newpiper from an xterm window. You'll need to do
"eval `resize`" to set the window size correctly (HP-UX
does support SIGWINCH but the utilities only honor
LINES and COLUMNS environmental variables). You
may want to add the following to your .login file
(assuming your shell is csh):
if ( $term == "xterm" ) then
if (`uname` == "HP-UX" ) then
eval `resize`
else
resize
endif
endif
This will set the screen size correctly for HP-UX as
well as other versions of Unix.
Q) When I start up an xterm delete (or backspace) doesn't work
and neither does ^C (control-C).
A) You started up an xterm that is not set to be a "login shell."
The problem is that this means your .login file is not read
and the default erase, interrupt, and kill characters in
HP-UX are (probably) not what you want. You need to
either start all xterms with the "-ls" flag (means LoginShell)
or add the following line to your .Xdefaults file
XTerm*loginShell: true
which will make all xterms startup as login shells. This
is the easiest to do and is what we suggest.
Q) I can't get my programs to compile on the new piper. What
can I do?
A) HP-UX does provide a BSD compatibility library (-lBSD) but
it does not include many things. You should take a look
at /tools/cs/doc/Porting_BSD_to_HPUX.txt which has lots
of good info on porting programs to HP-UX from a BSD
environment (like SunOS).
Q) I can't find many of the programs I used to use on piper. Where
did they go?
A) As was mentioned earlier, newpiper follows the new CSops filesystem
layout. This means that most commands (with the exception of
those necessary for booting the machines and performing maintenance)
have moved out of /usr/local. Most of /usr/local/bin has moved
to /Tools/bin and packages that used to be /usr/local/PACKAGENAME
are now /Tools/PACKAGENAME. Also, links from /usr/local/bin
to binaries in other packages have been removed (they are impossible
to keep current). This means you may need to add packages to
your path. For instance, to get at emacs you need to have
/Tools/emacs/bin in your path. To get at rn, trn, or tin
your need to add /Tools/news/bin to your path. This was all
spelled out in mail sent a few weeks ago (and posted to netnews
as well). There is more info in the file
/csops/FAQ/new-tools-structure.howto. If you are interested in
more of the nitty-gritty details you may want to read
/csops/FAQ/new-tools-structure and take a look at
http://www.cs.colorado.edu/~mikef/rfc/host-localization.html.
Q) The "ps" command doesn't work like it used to.
A) The sysV-based "ps" HP-UX uses takes very different
flags and produces different output. Do "man 1 ps"
for more info. When you used to do "ps aux" you would
now do "ps -ef" and when you used to do "ps auxww" you
can do "ps -elf".
--
Todd C. Miller Sysadmin--University of Colorado Todd.Miller@cs.colorado.edu
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads