stanonik@nprdc.navy.mil (Ron Stanonik) (05/19/89)
Someone just pointed out that the motd on our sun4's and sun3's all say "SunOS Release 4.0" rather than 4.0.1. Odd, installing the 4.0.1 upgrade (from 4.0) didn't upgrade the string in the kernel from which the motd is constructed? Or have we done something wrong? Thanks, Ron Stanonik stanonik@nprdc.navy.mil
ji@walkuere.altair.fr (John Ioannidis) (05/24/89)
In article <8905182140.AA16683@atlantic.nprdc.navy.mil> stanonik@nprdc.navy.mil writes: >X-Sun-Spots-Digest: Volume 7, Issue 299, message 12 of 13 > >Someone just pointed out that the motd on our sun4's and sun3's all say >"SunOS Release 4.0" rather than 4.0.1. Odd, installing the 4.0.1 upgrade >(from 4.0) didn't upgrade the string in the kernel from which the motd is >constructed? Or have we done something wrong? Well, you can't expect Sun's upgrade scripts to work perfectly! :-) The script should have changed the contents of ${SYS}/conf.common/RELEASE to 4.0.1 (in my case, 4.0.1_Export). (where SYS=/usr/share/sys, obviously). I did that by hand and it works fine. Here's my /etc/motd: SunOS Release 4.0.1_Export (WALKUERE) #16: Wed Apr 19 17:10:22 MET DST 1989 /ji #include <appropriate disclaimers> In-Real-Life: John Ioannidis E-Mail-To: <ji@cs.columbia.edu> (preferred), or <ji@walkuere.altair.fr> P-Mail-To: GIP-Altair, Dom de Voluceau BP105, Rocquencourt 78153 Le Chesnay, FR V-Mail-To: +33 1 39635227, +33 1 39635417 ... It's all greek to me
nao@cs.utexas.edu (Neil Ostroff) (05/24/89)
In X-Sun-Spots-Digest: Volume 7, Issue 299, message 12 of 13, stanonik@nprdc.navy.mil (Ron Stanonik) writes: >the motd on our sun4's and sun3's all say "SunOS Release 4.0" rather than >4.0.1. Odd, installing the 4.0.1 upgrade (from 4.0) didn't upgrade the >string in the kernel from which the motd is constructed? The file /usr/share/sys/conf.common/RELEASE contains the release id. The 4.0.1 upgrade did not change this file, but you can edit it yourself and then rebuild the kernel. Neil Ostroff Bell Communications Research | UUCP: bcr!maestro!nao 100 Schultz Dr. NVC-5J443 | ARPA: nao@maestro.bellcore.com Red Bank, NJ 07701 | PHONE: (201) 758-5741
ejs@goldhill.com (Eric Swenson) (05/24/89)
No, you did nothing wrong. The motd wasn't updated for either. We manually modified the file /sys/conf.common/RELEASE and rebuilt the kernel to get the right behavior. No clues why Sun didn't do this. -- Eric
james@druco.att.com (James B. Davis) (05/26/89)
In article <8905182140.AA16683@atlantic.nprdc.navy.mil>, stanonik@nprdc.navy.mil (Ron Stanonik) writes: > Someone just pointed out that the motd on our sun4's and sun3's all say > "SunOS Release 4.0" rather than 4.0.1. Odd, installing the 4.0.1 upgrade > (from 4.0) didn't upgrade the string in the kernel from which the motd is > constructed? Or have we done something wrong? > > Thanks, > > Ron Stanonik > stanonik@nprdc.navy.mil What I did to change this is instruct our SA's to edit the /usr/share/sys/conf.common/RELEASE file to have 4.0.1 instead of 4.0 and rebuild the kernel (after you have loaded the 4.0.1 upgrade tape of course). So there. James B. Davis (Jim), UNIX(tm) Systems Programmer UNIX Systems Support & Distributed Computing Group (Sun Support Team) AT&T Bell Laboratories 11900 North Pecos Street, 31G44 Denver, Colorado 80234 303/538-1647, Cornet 374-1647 Computing and Telecommunications Tech. Dept., Dept. XMRB50000 (DCTT) [sun|uunet|rice!uunet]!att!druco!james (or read the Email header!) UNIX is a registered TM of AT&T, UTS is a registered TM of Amdahl Corp. Everything else is a (TM) or (C) of whoever claims to own it. NOTE: My opinions are my own and not of my employer(s).
leres@helios.ee.lbl.gov (Craig Leres) (06/07/89)
Ron Stanonik writes: > Someone just pointed out that the motd on our sun4's and sun3's all say > "SunOS Release 4.0" rather than 4.0.1. Odd, installing the 4.0.1 upgrade > (from 4.0) didn't upgrade the string in the kernel from which the motd is > constructed? Or have we done something wrong? I also find this annoying. It's easy to fix, though; just edit /sys/conf.common/RELEASE to read "4.0.1" and config a new kernel. Craig
brent@uunet.uu.net (Brent Chapman) (06/08/89)
James B. Davis (james@druco.att.com) writes in v8n4:
# In article <8905182140.AA16683@atlantic.nprdc.navy.mil>, stanonik@nprdc.navy.mi\l (Ron Stanonik) writes:
# > Someone just pointed out that the motd on our sun4's and sun3's all say
# > "SunOS Release 4.0" rather than 4.0.1. Odd, installing the 4.0.1 upgrade
# > (from 4.0) didn't upgrade the string in the kernel from which the motd is
# > constructed? Or have we done something wrong?
#
# What I did to change this is instruct our SA's to edit the
# /usr/share/sys/conf.common/RELEASE file to have 4.0.1 instead of 4.0 and
# rebuild the kernel (after you have loaded the 4.0.1 upgrade tape of
# course).
I did this same thing once upon a time, when upgrading to 3.x.y, and
regretted it later. When I tried to do a later upgrade to 3.<x+1>, the
notoriously flaky upgrade scripts supplied by Sun wouldn't work because
they couldn't figure out what release of the OS I was already using (they
didn't recognize 3.x.y as a valid release).
-Brent
--
Brent Chapman Capital Market Technology, Inc.
Computer Operations Manager 1995 University Ave., Suite 390
brent@capmkt.com Berkeley, CA 94704
{cogsci,lll-tis,uunet}!capmkt!brent Phone: 415/540-6400james@druco.att.com (James B. Davis) (06/20/89)
Well I now have my 4.0.3 upgrade tapes and all worked fine (upgrading from "my" 4.0.1 RELEASE to 4.0.3). Apparently the new sunuprade script(s) didn't care as long as you had 4.x.x to start with. BTW: the sunupgrade scripts for SPARC are broken when the Sun4 is a server to Sun3's - it bombed loading the new kvm directory... See your Sun PA for details - I did, but I fixed it by hand before I called... It (sunupgrade on the SPARC tape) doesn't even match the documentation - as far as the questions/selections/display messages/etc... Not what I call a QUALITY product for an upgrade. This didn't really bother me but I don't want to think what Sun's non-tech customers will do with the upgrade! ----------------- James B. Davis (Jim), UNIX(tm) Systems Programmer UNIX Systems Support & Distributed Computing Group (Sun Support Team) AT&T Bell Laboratories 11900 North Pecos Street, 31G44 Denver, Colorado 80234 303/538-1647, Cornet 374-1647 Computing and Telecommunications Tech. Dept., Dept. XMRB50000 (DCTT) [sun|uunet|rice!uunet]!att!druco!james or james@druco.att.com UNIX is a registered TM of AT&T, UTS is a registered TM of Amdahl Corp. Everything else is a (TM) or (C) of whoever claims to own it. NOTE: My opinions are my own and not of my employer(s).