Sponsored Content
Full Discussion: Upgrading to FreeBSd 7.1
Operating Systems BSD Upgrading to FreeBSd 7.1 Post 302281251 by FloridaBSD on Wednesday 28th of January 2009 12:34:06 PM
Old 01-28-2009
Question Upgrading to FreeBSd 8.0

I have installed Free BSD 7.1 an would like to upgrade to 8.0 using theupgrade option under sysinstall. Is this posible?

Last edited by FloridaBSD; 01-29-2009 at 02:00 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Upgrading Sudo

Hi all I am trying to upgrade Sudo on my Redhat Linu 7.0 box. I have obtained the latest version of Sudo (1.6.6) from http://www.courtesan.com/sudo/. THis is in the form of a src.rpm file. I am confused about installing this. How can I install from a source rpm. It does not upgrade the... (1 Reply)
Discussion started by: skotapal
1 Replies

2. AIX

Upgrading from 5.1.0.0 to 5.2.0.0

As a fairly new Administrator to AIX i am a little leary of the OS upgrade I need to do on one of our servers. I have already upgraded the microcode to the lastest level and now need to do the OS. I have the docs and discs from IBM and have determined that I dont want to do a new installation but... (5 Replies)
Discussion started by: Target
5 Replies

3. Solaris

Upgrading SSH

Hi, I have a sun box with Solaris 9 installed on it. The SSH version is Sun_SSH_1.0 but I need to upgrade it to Sun_SSH_1.1. Do I have to remove the SSH packages totally or is there any other alternative. Thanks, rte (0 Replies)
Discussion started by: run_time_error
0 Replies

4. Solaris

upgrading java

Hi there I have been tasked with upgrading java on one of our boxes to version 6.0 or later (package version 1.5 or later someone told me). but ive been trying to find the SUNW package for this and cant see it, so I checked pkginfo for installed package and there isnt one ....even though java is... (4 Replies)
Discussion started by: hcclnoodles
4 Replies

5. Filesystems, Disks and Memory

Upgrading PC Memory

hello folks, I am planning to upgrade my PC's ram. currently the ram I have is 2x256MB=512MB/133MHz (DDR266) - DDR SDRAM, PC-2100. My guess is that it has 184 Pins. I would like to get a DDR2 with 667MHz, 240 pin. Is it possible, since pins don't match. Do they have to match? (there are 3... (4 Replies)
Discussion started by: milhan
4 Replies

6. Programming

Application crashes in FreeBSD 7.1 while working ok in FreeBSD 6.3

Hello there, My mulithreaded application (which is too large to represent the source code here) is crashing after installing FreeBSD 7.1-RELEASE/amd64. It worked properly on others machines (Dual Cores with 4GB of RAM - FreeBSD 6.2-RELEASE/i386). The current machine has 2x Core 2 Duo... (1 Reply)
Discussion started by: Seenquev
1 Replies

7. HP-UX

UNIX upgrading?

Right now we are using HP-UX 11i We are thinking of upgrading to 11i v3.. Questions: Why would we want to upgrade? Benefits? Do we need to install v2 and then v3 or can we just go straight to v3? I see we can get the following: HP-UX 11i v3 Operating Environment and applications... (10 Replies)
Discussion started by: nixie21
10 Replies

8. AIX

Upgrading AIX from 5.3 to 6.1

Hi, I am having 2 Hard disk one for os and another for data,I would like to know for Upgrading AIX 5.3 to 6.1,wheather I have to varry off datavg while upgrading, or any other files needs to be backup. Please suggest Regards, Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies

9. AIX

Upgrading OS from 5.2 to 5.3

We currently have test and production servers running AIX 5.2, DB2 8.1(Prod), DB2 8.2(Test),Websphere 6.1 on both. We need to upgrade to DB2 to version 9, but to do that we also need to upgrade the operating system to 5.3 and go from 32 bit kernel to 64 bit kernal. Looking for information on any... (3 Replies)
Discussion started by: jyoung
3 Replies

10. AIX

Upgrading Power5 from 5.3 to...

I have a power5 that I would like to update and bring everything forward. I am wondering about trouble-free upgrades. Is it better to go 5.3 -> 7 or 5.3 ->6 ->7? The power5 box is behind and hopefully can learn from experiences here. Thanks. (6 Replies)
Discussion started by: redi
6 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 11:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy