Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!romp!auschs!awdprime!snap.austin.ibm.com!moody
From: moody@snap.austin.ibm.com
Newsgroups: comp.unix.aix
Subject: Re: Upgrade????? Was: Why does this fail?
Message-ID: <8371@awdprime.UUCP>
Date: 11 Jun 91 18:05:27 GMT
References: <1991Jun6.004449.21833@siia.mv.com> <19371@rpp386.cactus.org> <1991Jun11.120248.18730@bellcore.bellcore.com>
Sender: news@awdprime.UUCP
Organization: IBM AWD, Austin
Lines: 29

In article <1991Jun11.120248.18730@bellcore.bellcore.com> jona@iscp.Bellcore.COM (Jon Alperin) writes:
[stuff deleted]

>p.p.s. Now that I think about it, I do have one gripe with these fixes. Why does AIX Defect Support always want me to reboot a machine after applying a fix. Don't they realize that people can just enter the commands from the .rc files and apply most of th
>e fixes without having to get everyone to log off and then reboot a machine? If IBM is serious about supporting distributed computing, then they better realize that rebooting machines to apply fixes is not the way to go.
>(just wanted to get my two sense in...) 

It is always necessary to reboot after installing an update, because updates have always
included a new kernel (/unix).  That is a true statement at this time.  The new kernel
will not be running on the machine until reboot time.  You will probably  have many 
problems if you don't reboot.

If you get an emergency fix that does not include /unix, it is almost certainly not
necessary to reboot.

>Jon Alperin
>Bell Communications Research
>
>---> Internet: jona@iscp.bellcore.com
>---> Voicenet: (908) 699-8674
>---> UUNET: uunet!bcr!jona
>
>* All opinions and stupid questions are my own *


-- 
James Moody				aixnet:moody@moody.austin.ibm.com
Personal Systems Programming Austin	VNET:MOODY@AUSVMQ
AIX Field Support - Level 3		internet:moody@aixwiz.austin.ibm.com