Sponsored Content
Operating Systems Solaris Setting up a Solaris training Post 302248559 by Perderabo on Saturday 18th of October 2008 10:05:16 AM
Old 10-18-2008
We are trying to get people to upgrade away from Solaris 8. With the kind of "push back" we're getting, you'd think we had asked them to eat a bucket of worms. The new system start up is the big thing. You can ignore zfs and dtrace, but you can't ignore the changes to system start up. Even a simple thing like disabling (or re-enabling) sendmail freaks out most folks approaching 10 for the first time. You won't be comfortable with the os until you're comfortable with this. This is the main reason that a lot of people where I work have rejected Solaris 10.

Reason number 2 is no support for static linking, but this only requires a quick sentence or two in your class.
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

UNIX/solaris training

I am new to UNIX and somewhat familiar with Solaris. Can you suggest any good (simple English) books that can help me with understanding and learning UNIX? (1 Reply)
Discussion started by: iamnew2solaris
1 Replies

2. UNIX for Dummies Questions & Answers

Solaris for a training: PC vs Sparc

I need a computer to try Solaris. I'm learning with UNIX Academy training DVDs and after spending much time with Linux I want to try and learn on Solaris. I'll have to buy a computer for my training anyway. I found on ebay plenty of inexpensive Sun boxes. Would it be beneficial for learning to have... (26 Replies)
Discussion started by: newlinuxuser1
26 Replies

3. Solaris

Setting IP on Solaris 10 help

Hi all, So, I need to change the IP/netmask on 2 sun v240's running solaris 10. I seem to have done it correctly on one, it's holding the ip after a init 6 reboot. The other does not want to keep ip using same commands. I'm guessing I have to change some files I haven't yet, but have no... (7 Replies)
Discussion started by: kuriosity_prime
7 Replies

4. UNIX for Beginners Questions & Answers

Any Solaris training?

Good Afternoon, Does anyone know of any free or cheap SkillSoft type Solaris training, with an exam? (0 Replies)
Discussion started by: Stellaman1977
0 Replies
DH_INSTALLSYSTEMD(1)						     Debhelper						      DH_INSTALLSYSTEMD(1)

NAME
dh_installsystemd - install systemd unit files SYNOPSIS
dh_installsystemd [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [--no-enable] [--name=name] [unitfile...] DESCRIPTION
dh_installsystemd is a debhelper program that is responsible for enabling, disabling, starting, stopping and restarting systemd unit files. In the simple case, it finds all unit files installed by a package (e.g. bacula-fd.service) and enables them. It is not necessary that the machine actually runs systemd during package installation time, enabling happens on all machines in order to be able to switch from sysvinit to systemd and back. For only generating blocks for specific service files, you need to pass them as arguments, e.g. dh_installsystemd quota.service and dh_installsystemd --name=quotarpc quotarpc.service. FILES
debian/package.service, debian/package@.service If this exists, it is installed into lib/systemd/system/package.service (or lib/systemd/system/package@.service) in the package build directory. debian/package.tmpfile If this exists, it is installed into usr/lib/tmpfiles.d/package.conf in the package build directory. (The tmpfiles.d mechanism is currently only used by systemd.) debian/package.target, debian/package@.target If this exists, it is installed into lib/systemd/system/package.target (or lib/systemd/system/package@.target) in the package build directory. debian/package.socket, debian/package@.socket If this exists, it is installed into lib/systemd/system/package.socket (or lib/systemd/system/package@.socket) in the package build directory. debian/package.mount If this exists, it is installed into lib/systemd/system/package.mount in the package build directory. debian/package.path, debian/package@.path If this exists, it is installed into lib/systemd/system/package.path (or lib/systemd/system/package@.path) in the package build directory. debian/package.timer, debian/package@.timer If this exists, it is installed into lib/systemd/system/package.timer (or lib/systemd/system/package@.timer) in the package build directory. OPTIONS
--no-enable Disable the service(s) on purge, but do not enable them on install. Note that this option does not affect whether the services are started. Please remember to also use --no-start if the service should not be started. --name=name Install the service file as name.service instead of the default filename, which is the package.service. When this parameter is used, dh_installsystemd looks for and installs files named debian/package.name.service instead of the usual debian/package.service. Moreover, maintainer scripts are only generated for units that match the given name. --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). Note that this option does not affect whether the services are enabled. Please remember to also use --no-enable if the services should not be enabled. 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. SEE ALSO
debhelper(7) AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org 11.1.6ubuntu2 2018-05-10 DH_INSTALLSYSTEMD(1)
All times are GMT -4. The time now is 12:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy