02-21-2012
Redhat 9 is ancient. I suggest you upgrade to a release that is not approaching 10 years old if you would like to have current software that has current capabilities. It came out in 2003.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey all, No sorry I don't mean burning windows. Though it was a nice thought to think of that people :) Pat yourself on the back for thinking of burning Windows.
No really though here the real question.
I'm after burning software for Solaris 7 (or 8 if it has to be, perfer 7 though). I... (1 Reply)
Discussion started by: merlin
1 Replies
2. UNIX for Dummies Questions & Answers
I just installed Redhat Linux 8.0 and I do not know how to get to my GUI Desktop. Right now I'm just in the shell please help. (2 Replies)
Discussion started by: savagebeast
2 Replies
3. UNIX Desktop Questions & Answers
I want one that won't run too slugish on a slower system (p 200Mhz for example). I know kde is out, anybody think gnome will run ok (I got 128 megs ram on it btw...don't ask :))? (5 Replies)
Discussion started by: pudad
5 Replies
4. UNIX Desktop Questions & Answers
I got Linux 9 installed on my system with the GUI.
One fine day....the GUI wouldn't start.
How should i set it right? (2 Replies)
Discussion started by: preeya
2 Replies
5. Red Hat
hi,
Can someone help in trouble shooting why my RedHat linux 8.0 in not logging into the KDE screen.
Thanks (1 Reply)
Discussion started by: kayode
1 Replies
6. Solaris
Hi,
Can anyone please let me know if any installed software on solaris can be accessed with GUI on CDE. I just installed putty from sunfreeware.com and try accessing it but no way to access it's GUI.
Thanks,
Deepak (1 Reply)
Discussion started by: naw_deepak
1 Replies
7. Fedora
hi all,
this is my first post here...i hope that this is the correct section to write my question.
I have a distro linux without gui, only text mode.
So, it's possible run automatically a command or a program as "top" or "ping" and get the result on the main shell , after the boot and after... (6 Replies)
Discussion started by: gangiaemi
6 Replies
8. UNIX for Dummies Questions & Answers
I want to execute from a grub a very small linux that only has commands, so at startup it executes this shell script I wrote and after that the user has an option to go back to the grub.
I've heard of busybox but that doesn't seem to be helpful?
Can anyone recommend a non gui distro, that can... (1 Reply)
Discussion started by: jcnewton13
1 Replies
LEARN ABOUT MINIX
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)