setting milestone leads to maintenance mode
- From: aaron@xxxxxxxxxxxxxxxx
- Date: Fri, 25 Apr 2008 23:25:45 -0700 (PDT)
Hi there. I've looked for this one without much luck, so I'd be much
obliged if someone could provide some information.
We have a custom software package on top of Solaris 10 and it requires
2 DVDs to install - don't ask why so big; it's not under my control.
The first DVD installs the base OS and the database, etc. The second
DVD has additional packages that we install via a simple pkgadd.
One of the startup scripts installed in the base package kicks off the
installation of the second DVD after the initial reboot - it's just an
'S' script in /etc/rc2.d that gets removed after successful
installation. Originally, it appeared to work Ok, except it was
kicked off in run-level 2 (milestone/multi-user), but the /dev/
console, which we were using to prompt for user input to control the
install, got clobbered by other programs that came along later in run-
level 3 (milestone/multi-user-server), as well as the X server,
itself. Not good.
This is question #1: Is there a better way to do a 2 DVD install, like
have the first DVD eject before rebooting, and then have the system
prompt for the second DVD to continue the install, and _then_ reboot?
We've been told it's "too difficult."
Barring that, I'll continue the story... So within the second DVD
install script, one of the first things it now does is call "svcadm
milestone milestone/multi-user" to keep the system temporarily in run-
level 2. This works - sort of, since the run level 3 scripts don't
execute.
However, when the svcadm command executes, it actually puts the
milestone in "maintenance mode," and prompts for the root password to
enter system maintenance, like when a partition is hosed and needs an
fsck. This login prompt interferes with our /dev/console prompts;
it's like they take turns reading. If this product were for geeks,
that might be somewhat acceptable - you just have to know which prompt
is for our input, and which is for the console login - but it's for
non-geeks, and they won't like it.
Question #2: How does the Solaris installation routine take control of
the screen as it does so all user input is channeled to the
installation routine, rather than whoever grabs /dev/console for the
moment?
Question #3: Barring a reasonable solution to either questions #1 or
2, how can we keep the system in run level 2 without having it drop to
system maintenance mode?
Or, if there's an approach that I haven't considered, feel free to
suggest it.
As I said, I'd be very grateful for any input on this.
Thanks,
Aaron
.
- Follow-Ups:
- Re: setting milestone leads to maintenance mode
- From: Darren Dunham
- Re: setting milestone leads to maintenance mode
- From: Reginald Beardsley
- Re: setting milestone leads to maintenance mode
- Prev by Date: Re: Problems with new Solaris Developers Express x86
- Next by Date: hi
- Previous by thread: UFS on Zvol Performance Query
- Next by thread: Re: setting milestone leads to maintenance mode
- Index(es):
Relevant Pages
|
