Thanks to Phil Farrell, Gary George, Dr. Tom Blinn, Davis, and Roger
Picard for their responses to my question on what to use instead of
rc1.d.
There were a couple of suggestions to use "it", which is for one-time
installation tasks, it runs during the first boot after installation,
for instance. There is a man page for it.
There was another suggestion to add code onto /sbin/bcheckrc.
Finally, there was a suggestion to add either my script to inittab, or
create my own rc1/rc1.d and put that in inittab.
Meanwhile, I hacked dupatch to eliminate the check for single-user mode,
and called it in rc2.d.
Here was my original question:
Is there a substitute for rc1.d in Digital Unix 4.0D?
I am using RIS to install OS updates on my alpha workstations. I need
to install patchkits, as well. Patches normally have to be installed in
single user mode. A workaround has been posted here, which allows you
to automate the installation of patches as part of the RIS OS
installation. You install them during the postload, specifying the
client's root directory as an alternate root. This has a couple of
drawbacks. First, we install layered products after the OS, some of
which cannot be installed until after the client reboots and configures
itself. Patches to these products are necessarily omitted. Second, we
would like to be able to add patches remotely without going through a
full time-consuming OS installation. Finally, it is not supported by
DEC. I'm not sure why, but despite the obvious need to install patches
remotely and the evidence of its doability (by modifications of the
dupatch script and by other OS's) DEC still does not support it.
Perhaps they know of problems that I am unaware of.
The solution that I have tried to implement to this is to copy the patch
kit into /var/tmp on the client during a RIS installation. I then would
like to put a script into /sbin/rc1.d to install the patches, so that
when the client boots up, it will run my script to install the patches,
rebuild the kernel, delete that patches from /var/tmp, and reboot before
going into multiuser mode. Then, we could leave the script there, and
install new patches by copying (perhaps rdist'ing) them into /var/tmp on
the workstations and and rebooting.
However, there is no rc1.d. And scripts placed in rc0.d are not
executed on bootup. When I try to run dupatch from a script in rc2.d,
it complains that it needs to be in single-user mode.
So this raises two questions. First, how would I execute a script on
bootup before going into multiuser mode. Second, how do others manage
remote installation of patches?
Thank you,
David Ritch
Received on Fri Mar 26 1999 - 02:44:12 NZST