Ralph Jambert O.

Padilla

Bt203A

What is gcc?

>The GNU Compiler Collection (GCC) is an optimizing compiler produced by the GNU
Project supporting various programming languages, hardware architectures and
operating systems. The Free Software Foundation (FSF) distributes GCC as free
software under the GNU General Public License (GNU GPL). GCC is a key component of
the GNU toolchain and the standard compiler for most projects related to GNU and the
Linux kernel. With roughly 15 million lines of code in 2019, GCC is one of the biggest
free programs in existence.[4] It has played an important role in the growth of free
software, as both a tool and an example.

What is emac?

>The EMAC Operations System (EOS) is the online system state emergency
management agencies use to request, offer and track resources for deployments
through the nationally adopted Compact. The EOS is only accessible by State
Emergency Management Agencies.

What is httpd?

>httpd is the Apache HyperText Transfer Protocol (HTTP) server program. It is designed
to be run as a standalone daemon process. When used like this it will create a pool of
child processes or threads to handle requests.

How to install package?

>Use RPM in Linux to install software

RPM (RPM Package Manager) is a popular utility for installing software on Unix-like
systems, particularly Red Hat Linux. The following is an example of how to use RPM:

Log in as root, or use the su command to change to the root user at the workstation on
which you want to install the software.

Download the package you wish to install. The package will be named something like
DeathStar0_42b.rpm.
To install the package, enter the following command at the prompt:

(Rpm -I DeathStar0_42b.rpm)

If you are upgrading from an earlier version of the software package, run RPM in
upgrade mode, as in the following example:

(Rpm -U DeathStar0_42b.rpm)

How to update/upgrade package?

>To upgrade Ingres RPMs

1.Make sure the Ingres instance you want to upgrade is completely shut down and that
you have taken a backup, as described in the Upgrade Guide.

Note: Files that you have customized will be lost during the upgrade. Copy your
customized files to a safe place. For more information, see the Upgrade Guide.

2.Issue the following command to see the list of Ingres RPM packages installed for the
instance to be upgraded:

Rpm -q –whatrequires core_pkg_name

Where core_pkg_name is the core package name for the release.

Note: If you are upgrading an instance that was installed using RPMs that were
renamed to embed an instance ID, then use “core_pkg_name-XX” instead of the core
package name.

Note: All packages must be upgraded at once. Any attempt to perform an upgrade on a
single or smaller group of packages will fail.

3.Log in as root and CD to the directory containing the RPM to be used to perform the
upgrade. Make sure variable II_CONFIG is not set.

4.Run rpm -ivh to install the new RPM packages over the existing instance.

If the instance was originally installed using –prefix to change II_SYSTEM from the
default, then this parameter must also be used for the upgrade.

For default instance location:

Rpm -ivh –replacefiles –replacepkgs \

Complete list of RPM files to be installed

Rpm -ivh –replacefiles –replacepkgs –prefix <II_SYSTEM> \

Complete list of RPM files to be installed

5.Remove the RPM package information for the old instance, as follows:

a.Find the correct packages:

rpm -q –whatrequires old_core_pkg_name-x.y.z

b.If the list returned is satisfactory, remove the packages:

rpm -q –whatrequires old_core_pkg_name-x.y.z | xargs rpm -e –justdb

c.Remove the RPM package information for the old core package. Include the version
and the package name, for example:

rpm -e –justdb core_pkg_name-x.y.z

where x.y.z is the version number (for example 9.0.4).

6.Run the service script to configure and start the instance:

/sbin/service ingresXX start

Where XX is the instance ID.

Note:

•If you used rpm -Uvh with –prefix to upgrade an instance, binary and other installed
files (for example, iimerge) may be removed. Should this occur, simply re-run the same
command using the additional flags ‑‑replacefiles and –replacepkgs, and all the missing
files will be replaced. Database or configuration files will not be affected.

•For the special case where you are upgrading from a non-NPTL build to a NPTL build
with the same version number, you must upgrade using the following command:

Rpm -ivh –replacefiles –replacepkgs new-package-list

Upgrade an ingbuild Installation Using RPM

To use the RPM command to upgrade an instance that was installed using the ingbuild
program, follow these steps:

1.Create a file /tmp/upg.rsp and add the following lines:

II_HOSTNAME=hostname

II_INSTALLATION=XX
Where hostname is the value returned by running “hostname” and XX is the value
returned by “ingprenv II_INSTALLATION” for the instance to be upgraded.

2.Set the variable II_RESPONSE_FILE to point to the newly created file:

Export II_RESPONSE_FILE=/tmp/upg.rsp

3.Install Ingres using the RPM command:

Rpm -Uvh –prefix=$II_SYSTEM /path/to/rpms/*.rpm

4.Run the setup:

/etc/init.d/ingresXX configure

Where XX is the instance ID.

How to delete and unistall package?

>1.Uninstall any RPMs or DEBs that depend on the CCA RPM or DEB packages. If you try
to uninstall the CCA RPM or DEB and dependent RPMs or DEBs are still installed, the
uninstall RPM or DEB command will fail and list the names of dependent packages.
Therefore, you can skip to Step 2 and come back to this step if Step 2 fails for that
reason.

2.Uninstall the CCA RPM or DEB.

Login as root. You must be root to uninstall the RPM or DEB.

You must use the full name. You can find the name by issuing one of the following
commands.
Note:

Groups are no longer deleted during the uninstall of CCA RPM or DEB. If you created any
users with one of the groups created by the package install as their primary (note that
the package install does NOT create any users, just groups), you can delete those
users/groups yourself after uninstall, or remove such users before the uninstall of the
RPM or DEB. This will remove any potential security holes.

Card master keys (and other state information) are untouched by the host-side uninstall
of the RPM or DEB.

Key storage files are not deleted by the uninstall. All default and non-default key storage
files are left as is. If you reinstall or install an upgraded package and load any new cards
with the same master keys, you still can use your old key storage (old cards still have
the old keys, see step 7.b of Install and configure the RPM or DEB).
Reference :

Gcc -
https://en.m.wikipedia.org/wiki/GNU_Compiler_Collection#:~:text=The%20GNU%20Co
mpiler%20Collection%20(GCC,Public%20License%20(GNU%20GPL).

Emac -

https://www.emacweb.org/index.php/learn-about-emac/the-emac-operations-system-
eos

Httpd -

https://httpd.apache.org/docs/2.4/programs/httpd.html#:~:text=httpd%20is%20the%2
0Apache%20HyperText,or%20threads%20to%20handle%20requests.

Install rpm

https://kb.iu.edu/d/aheo

Upgrare rpm -
https://docs.actian.com/ingres/10s/Installation/How_You_Upgrade_Using_RPM.htm

Uninstall -

https://www.ibm.com/docs/en/linux-on-z?topic=instructions-uninstall-rpm-deb