Installp and reboot.
Hernan Schiavi
after I apply this I need to reboot the machine. For example I know that if
I apply and update for bos.up or bos.mp the boot image is reconstructed and
I need to reboot the machine to make the changes. I need to know what thing
can tell me to me that after I install this I need a reboot.
Saludos.
Hernan.
Joel Becker
>I need to reboot the machine to make the changes. I need to know what thing
>can tell me to me that after I install this I need a reboot.
If bosboot runs, you usually need to reboot the machine.
Joel
--
--
"Kick the tires and light the fires, boys!"
Joel Becker
IBM Global Services South - AIX Server Support
Internal E-Mail: jlbec@IBMUSM21
External E-Mail: jl...@us.ibm.com
(919) 486-2689; T/L 526-2689
Dale Talcott
>I need to know which filesets or what needs to be inside of the fileset that
>after I apply this I need to reboot the machine. For example I know that if
>I apply and update for bos.up or bos.mp the boot image is reconstructed and
>I need to reboot the machine to make the changes. I need to know what thing
>can tell me to me that after I install this I need a reboot.
I have often wanted to know *ahead of time* whether applying a given patch
would require a reboot afterward. It's unfortunate that installp -p
doesn't tell you this.
My current guess, and I'm probably wrong, is that you can extract the
"lpp_name" file from each .bff archive with, for example:
restore -xqf bos.mp.4.3.2.2.bff lpp_name
Next, look at the beginning of the file:
$ head -2 lpp_name
4 R S bos.mp {
bos.mp 4.3.2.2 01 b U en_US Base Operating System Multiprocessor Runtime
------------------^
I think the 'b' means you should reboot after applying the patch, but
this is a wild guess.
Another file of interest is /usr/lib/boot/rs6k.disk.proto, where 'rs6k'
might also be 'chrp' or 'rspc'. This file lists the files that are used
by bosboot when constructing the RAM filesystem in the boot image.
Presumably, whenever any of those files is modified, you'll need to run
bosboot. Of course, just because you update the boot image doesn't
mean you need to boot from it right away.
If anyone knows the real answer, I'd sure like to hear it.
--
Dale Talcott, Purdue University Computing Center, a...@quest.cc.purdue.edu
http://quest.cc.purdue.edu/~aeh/
Joel Becker
>I have often wanted to know *ahead of time* whether applying a given patch
>would require a reboot afterward. It's unfortunate that installp -p
>doesn't tell you this.
>
>My current guess, and I'm probably wrong, is that you can extract the
>"lpp_name" file from each .bff archive with, for example:
>
>
This will work, but isn't the best way to do it. The 'b' is
indeed the flag to mark a bosboot. However, instead of restoring the
lpp_name file, you can just look in .toc. The .toc file contains a
listing of all filesets in that directory. Basically, it is a
compilation of all their lpp_name info.
Joel
Dale Talcott
>I have often wanted to know *ahead of time* whether applying a given patch
>would require a reboot afterward. It's unfortunate that installp -p
>doesn't tell you this.
Mark Martin of cetia.fr pointed me to the -l option of installp. If you
check the Q column, it shows a 'b' or 'B' when a bosboot is required by
the fileset. Moreover, if it shows a 'Y', you should quiet the system
before applying the patch. Just the kind of information I was looking for.
John Jaszczak
It would seem to me that the appropriate way to deal with this issue
would be for IBM to plainly state on the documentation that comes with
the patch media whether or not the machine needs to be rebooted.
Whoever is publishing the patch knows if the machine should be rebooted,
so why not state this in plain English?
I have always resorted to calling the AIX support line for every patch
installation. This seems an awful waste of resources, both mine and
IBM's. Either a disclaimer should be posted with the media documentation
or a message should be displayed when the patch is installed in "test"
mode.
IBM should make this process better!
-JAZZ
Joel Becker wrote:
>
> On 12 Feb 99 09:33:40 EST, Dale Talcott <a...@quest.cc.purdue.edu> wrote:
> >I have often wanted to know *ahead of time* whether applying a given patch
> >would require a reboot afterward. It's unfortunate that installp -p
> >doesn't tell you this.
> >
> >My current guess, and I'm probably wrong, is that you can extract the
> >"lpp_name" file from each .bff archive with, for example:
> >
> >Next, look at the beginning of the file:
> >
> > bos.mp 4.3.2.2 01 b U en_US Base Operating System Multiprocessor Runtime
> >
> > ------------------^
>
> This will work, but isn't the best way to do it. The 'b' is
> indeed the flag to mark a bosboot. However, instead of restoring the
> lpp_name file, you can just look in .toc. The .toc file contains a
> listing of all filesets in that directory. Basically, it is a
> compilation of all their lpp_name info.
>
> Joel
>
> --
>
> "Kick the tires and light the fires, boys!"
>
> Joel Becker
> IBM Global Services South - AIX Server Support
> Internal E-Mail: jlbec@IBMUSM21
> External E-Mail: jl...@us.ibm.com
> (919) 486-2689; T/L 526-2689
--
John Jaszczak
ja...@musicland.com
Musicland Group, Inc.
Phone (612)932-7907 Fax (612)932-7475
Laurenz Brein
> Whoever is publishing the patch knows if the machine should be
> rebooted, so why not state this in plain English?
> I have always resorted to calling the AIX support line for every
Well, it IS in plain English.
Just look at the output of the installp command.
Without straining your eyes too much you'll see whether there is a
message 'creating bosboot image' or not.
This is the message that shows you that a new kernel image is created.
This is English as plain as you could wish for, isn't it?
Hoping to save you and the AIX support line some trouble,
yours,
Laurenz Brein
--
* Every day I see the morning come on in the same old way. *
* I tell myself tomorrow brings me things I would not dream today. *
* I've ceased to see where I'm going - I don't want to. *
--- Jethro Tull ---
Udo Beckmann
Laurenz Brein wrote:
> Without straining your eyes too much you'll see whether there is a
> message 'creating bosboot image' or not.
This message appears AFTER having applied PTFs. That's not what the
original poster asked for.
Try
# inutoc <lppdir>
# installp -L -d <lppdir>
There is a field in the output of the last command, explaining whether
running processes are affected or a bosboot is needed due to applying
PTFs. Running installp with some different parameters (can't remember
which ones) can also deliver the same information in a better readable
format.
Best regards
Udo