Hello managers,
my original question (see below) was solved by Dr. Tom Blinn (who else?):
he bet (and won) that a "netsetup" would solve my problem; it does.
The underlying reason seems to be that CDE "knows" about the hostname
and burries it somewhere in its files (see the answer of Dave Cherkus).
Thanks a lot for your help!
"Dr. Tom Blinn, 603-881-0646" <tpb_at_ZK3.DEC.COM>
Dave Cherkus <cherkus_at_UniMaster.COM>
GLADNEY_at_stsci.edu
with regards,
Bernt Christandl
-------------------------------------------------------------------------
- Bernt Christandl / Max Planck Institut fuer Extraterrestrische Physik -
- D-85740 Garching / Phone: +49/89/3299-3342 / Fax: +49/89/3299-3569 -
- Internet: beb_at_mpe-garching.mpg.de -
-------------------------------------------------------------------------
tpb_at_ZK3.DEC.COM said:
> CDE is VERY sensitive to the network configuration. I bet you need
> to do a netsetup for the new disk to make it match the system's IP
> address, etc.
> You will probably need to do this with file systems mounted, so run
> bcheckrc and update from single-user mode, then use the old character
> cell setup to get to netsetup, or just run netsetup. Should fix it.
> Tom Dr. Thomas P. Blinn, UNIX Software Group, Digital Equipment
> Corporation 110 Spit Brook Road, MS ZKO3-2/U20 Nashua, New
> Hampshire 03062-2698 Technology Partnership Engineering
> Phone: (603) 881-0646 Internet: tpb_at_zk3.dec.com Digital's
> Easynet: alpha::tpb
> Worry kills more people than work because more people worry than
> work.
> My favorite palindrome is: Satan, oscillate my metallic sonatas.
> -- Phil Agre, pagre_at_ucsd.edu
> Opinions expressed herein are my own, and do not necessarily
> represent those of my employer or anyone else, living or dead, real
> or imagined.
cherkus_at_UniMaster.COM said:
> CDE does bury the hostname in its config files somewhere. I presume
> your 255/233 has a new hostname, but because CDE buries the hostname
> in its config files it doesn't know that it is now running on a new
> host.
> My solution was to use xsetup to use the old 'xdm' login Sequence -
> it solved two problems at once!
> -- Dave Cherkus ----- UniMaster, Inc. ----- Contract Software
> Development Specialties: UNIX TCP/IP X OSF/1 AlphaAXP AIX RS/6000
> Performance ISDN Email: cherkus_at_UniMaster.COM Tel: (603) 888-8308
> Fax: (603) 888-4598 The Internet runs on its programmers, and
> programmers run on coffee!!!
my original question was:
> Hello managers,
> i have a new alpha 255/233 with a factory installed du-4.0a on a rz26
> (!) and a graphics console. Everything seems to work fine.
> Then i have another du-4.0a system-disk (copied from a decstation
> 3000/400) which i want to be my *real* new system-disk. After
> changing the config-file and the rc.config, my 255/233 boots fine
> with this disk. Also i can login via "failover" or with dxsession.
> But when i try to login "normal" (CDE), the login is hanging after
> running dthello... (the screen is showing the welcome and the
> sand-glass)
> This remains true even after i copied from the "FIS"-system (where i
> can login) the directory-trees /usr/var/.dt, /usr/var/dt and /usr/dt
> and removed the /.dt to avoid problems...
> Now i can't figure out any other differences in the CDE-part of the
> systems or what to try next...
> Do i really have to install the system again from scratch...?
> With regards,
> Bernt Christandl
Received on Thu Nov 28 1996 - 09:07:09 NZDT