Re: SCO 5.0.4/5 stops at boot: prompt on a fresh install in a VMware workstation
- From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
- Date: Tue, 1 Jul 2008 00:21:52 -0700 (PDT)
On 1 Jul, 03:22, Bleve <carl.I.bre...@xxxxxxxxx> wrote:
Hello,
I'm a complete newbie with SCO, but not to UNIX. A client of mine has
an old SCO 5.0.5 server running a very small Progress database and the
hardware is finally dying. We're going to run it in a VMware
workstation, at the moment, with IDE disks, which seems to be working
after some simple hackery with 5.0.7 install floppy images... but it
works.
I've done a clean install into the VM, applied the licence keys, but
every time I try and boot the VM it stops at the boot: prompt.
Hitting return makes it boot, and it then asks to be licenced, and
then asks for the root password or ^d to continue into normal mode. I
can ^d in and it seems to run ok from then on.
Can anyone here point me at what I need to do to get it to boot up
multi user without needing user input on the (virtual) console?
What happens if you just *wait* for a few minutes? Under 5.0.6,
there's a lengthy pause at that stage: I think that it's a legacy of
what is basically a very antique operating system that thinks you
should reboot only in emergencies, and threefore you *MUST* want a
lengthy chance to have a talk with it at boot time.
Be warned: that IDE based installation works fine iwth VMware
Workstation, but VMware ESX doesn't support it. You have to use the
Buslogic emulated SCSI and 5.0.7 boot floppy, described at AP
Lawrence's website, to install on VMware ESX.
More background if it helps :
I have a CPIO archive of the existing system that I want to restore on
top of the VM once this is working, so I can get it working with a
minimum of fuss in a hurry. Any tips or caveats to doing this? I
expect the kernel might get upset, or maybe the licence will stop
moaning?
Restoring form cpio is begging for pain. It's likely to seriously
screw up your kernel and configuration if you simply restore on top of
it: this is AT&T SysV with SCO modifications on top of it, not Linux,
and that nutty symlinking all over the file system of your installed
software that OpenServer does is likely to present profound
difficulties.
.
- Follow-Ups:
- References:
- Prev by Date: SCO 5.0.4/5 stops at boot: prompt on a fresh install in a VMware workstation
- Next by Date: Re: SCO 5.0.4/5 stops at boot: prompt on a fresh install in a VMware workstation
- Previous by thread: SCO 5.0.4/5 stops at boot: prompt on a fresh install in a VMware workstation
- Next by thread: Re: SCO 5.0.4/5 stops at boot: prompt on a fresh install in a VMware workstation
- Index(es):
Relevant Pages
|
