12-17-2018
Hi,
Here's my tuppence worth on the matter;
You'll almost certainly be able to do what you suggest, however a reboot is highly likely to cause lots of things to break - if I'm reading your intentions correctly.
I'd be tempted to clone the VM, bring it up without the legacy application and test the OS bit first - at least that way you'll be relatively sure that the OS is viable when you do it for real.
Attempting to sort out something like a legacy application in a VM is difficult enough, but adding the complexity layer of a potentially broken OS as well is a bit like persuading the Grandparents to tell their Grandchildren that Santa Clause has been assassinated - It's going to bring you a lot of grief from both sides.
Best to tackle these things one at a time.
I suppose if you are going to bring all the /etc/conf directory over, you could knock up a quick script and create a differences file - so what's missing what's added and any files that are different.
Regards
Gull04
Last edited by gull04; 12-17-2018 at 03:51 PM..
Reason: Some Additional Comments
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I've just installed Unix SCO OpenServer System v in an Intel PC and Everithing ok, except just one thing, in the begining of the installation the wizard asked me about the mouse , i have a generic 3 buttons mouse and i took a logitech and did not work
i need to change the mouse configuration, ... (2 Replies)
Discussion started by: jimmyvaldes
2 Replies
2. UNIX for Dummies Questions & Answers
hello!
when i try to make my system dual boot with both win98 & sco open server 5.5 it doesn't work at all.neither win98 take start nor sco open server boots.what should i do ?
kindly help me
thanks (1 Reply)
Discussion started by: buntty
1 Replies
3. UNIX for Advanced & Expert Users
I am doing some work for a customer that is running SCO 5.0.2 openserver and they have lost their cd. Is there anyplace I can download it? I have a replacement being shipped but it will not be here for two days and they are down. Any ideals? (3 Replies)
Discussion started by: SCOoT
3 Replies
4. UNIX for Dummies Questions & Answers
hello guys.
I just installed SCO 5.0.6 OpenServer it went all the way to the end of the installation and the first boot try it gave me this message.
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot (2 Replies)
Discussion started by: josramon
2 Replies
5. SCO
Which version of Ethereal can I use for SCO OpenServer 5.0.7??? (0 Replies)
Discussion started by: bean2
0 Replies
6. UNIX for Dummies Questions & Answers
Hi there guys.
I just got this new SCO version and i'm having some problem printing from shell,
This is what i'm typing at the # sign : lp -dHP /etc/hosts and it prints no problem but when i use any other user at the $ sign it gives me this error.
/dev/fd/7: /usr/lib/lp/sysv/7: not found.
... (1 Reply)
Discussion started by: josramon
1 Replies
7. UNIX for Dummies Questions & Answers
Hi guys,
I just got this new 6.0 version and i'm trying to setup a remote office to telnet to this server running sco 6.0, in previous version all i have to do is add this file under /etc/rc2.d call S99route and put the gate in that file and that was it, for some reason in 6.0 it does not... (1 Reply)
Discussion started by: josramon
1 Replies
8. SCO
Dear members
when i installed dual processor patch in openserver 5.0.7 in hp ML370 G4 server it hangs in sco at G_hd_config.
i tried MP4, EFS 5.64,5.70A but not solved the problem.. (0 Replies)
Discussion started by: M_farooqui
0 Replies
9. SCO
Hi,
I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone.
I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies
10. SCO
I need SCO Openserver 4.2. Please, give me distributive of that version SCO:eek: (0 Replies)
Discussion started by: caine
0 Replies
SHUTDOWN(8) System Manager's Manual SHUTDOWN(8)
NAME
shutdown - close down the system at a given time
SYNOPSIS
shutdown [ -k ] [ -r ] [ -h ] [ -f ] [ -n ] time [ warning-message ... ]
DESCRIPTION
Shutdown provides an automated shutdown procedure which a super-user can use to notify users nicely when the system is shutting down, sav-
ing them from system administrators, hackers, and gurus, who would otherwise not bother with niceties.
Time is the time at which shutdown will bring the system down and may be the word now (indicating an immediate shutdown) or specify a
future time in one of two formats: +number and hour:min. The first form brings the system down in number minutes and the second brings the
system down at the time of day indicated (as a 24-hour clock).
At intervals which get closer together as apocalypse approaches, warning messages are displayed at the terminals of all users on the sys-
tem. Five minutes before shutdown, or immediately if shutdown is in less than 5 minutes, logins are disabled by creating /etc/nologin and
writing a message there. If this file exists when a user attempts to log in, login(1) prints its contents and exits. The file is removed
just before shutdown exits.
At shutdown time a message is written in the system log, containing the time of shutdown, who ran shutdown and the reason. Then a termi-
nate signal is sent to init to bring the system down to single-user state. Alternatively, if -r, -h, or -k was used, then shutdown will
exec reboot(8), halt(8), or avoid shutting the system down (respectively). (If it isn't obvious, -k is to make people think the system is
going down!)
With the -f option, shutdown arranges, in the manner of fastboot(8), that when the system is rebooted the file systems will not be checked.
The -n option prevents the normal sync(2) before stopping.
The time of the shutdown and the warning message are placed in /etc/nologin and should be used to inform the users about when the system
will be back up and why it is going down (or anything else).
FILES
/etc/nologin tells login not to let anyone log in
SEE ALSO
login(1), reboot(8), fastboot(8)
BUGS
Only allows you to kill the system between now and 23:59 if you use the absolute time for shutdown.
4th Berkeley Distribution November 16, 1996 SHUTDOWN(8)