04-07-2015
SCO sold upgrade licenses from one release to the next for several hundred dollars. However due to an oversight, you can install any version from 502 to 506 with any license (the only exception is that Compaq had their own series of serial numbers). But when you go to upgrade to 507 or 600, using a 502-506 serial number, SCO knows which version it was originally sold for, and price the upgrade accordingly.
This User Gave Thanks to jgt For This Post:
6 More Discussions You Might Find Interesting
1. IP Networking
The problem I am facing now is that the QNX host could not ping the SCO host and vice versa. They are in the same domain, ie, 172.20.3.xx. As I am very new to Unix, I guess I must have missed out some important steps. Pls help... Thanx alot (2 Replies)
Discussion started by: gavon
2 Replies
2. UNIX for Dummies Questions & Answers
Hi guys i have a unix server SCO 5.0.4 and i'm trying to install and intel pro 100 and for some reason it wont see it , i tried to install a 3 com card and same thing.
I know that if i had 5.0.6 it will see any of those cards.my questions is ( if i upgrade to 5.0.6 i have a computone card... (4 Replies)
Discussion started by: josramon
4 Replies
3. SCO
SCO OpenServer 6.0.0 License is required for testing purpose. If anyone have, please help me at the earliest. (2 Replies)
Discussion started by: rakeshkumar9919
2 Replies
4. Shell Programming and Scripting
Hi,
how to check when was the linux upgrade has been done to this host.
below command show the RHEL version.
cat /etc/redhat-release
Red Hat Enterprise Linux AS release 3 (Taroon Update 6)
i want to know when it was upgraded..
is there any command available for that ? or anywhere we... (3 Replies)
Discussion started by: mail2sant
3 Replies
5. Shell Programming and Scripting
Hi All,
I have a XML file : System.xml in which I want to update the license tag with the new data from file licence.xml.
The content of files is in following format:
System.xml:
<?xml version="1.0"?>
<!DOCTYPE Configuration SYSTEM "SystemVariables.dtd">
<usageConfiguration... (2 Replies)
Discussion started by: Pramod_T
2 Replies
6. SCO
Xinuos (SCO) discontinued Merge 5.3 on 1.31.16. I'm looking to buy from someone their Merge license. Please contact 1234567@optonline.net (0 Replies)
Discussion started by: Scott Tinker
0 Replies
LEARN ABOUT CENTOS
dh_systemd_start
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1)
NAME
dh_systemd_start - start/stop/restart systemd unit files
SYNOPSIS
dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]
DESCRIPTION
dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
sysv init script is available.
As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because
invoke-rc.d performs the stop/start/restart in that case.
OPTIONS
--restart-after-upgrade
Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10.
In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
--no-restart-after-upgrade
Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to
be stopped in the prerm script and started again in the postinst script.
-r, --no-stop-on-upgrade, --no-restart-on-upgrade
Do not stop service on upgrade.
--no-start
Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
corresponding init script).
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.
Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.
SEE ALSO
debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)