How to Install TOP package in Solaris 10

Step-1: PreRequisites

For installation of top, download the following package.

# wget

Step-2: Extract Zip File

Extract top package using below command.

# gunzip top-3.6.1-sol10-sparc-local.gz

Step-3: Installation

Install and configure top package as given below:

# pkgadd -d top-3.6.1-sol10-sparc-local

The following packages are available:
  1  SMCtop     top
                (sparc) 3.6.1

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: 

Processing package instance  from 

top(sparc) 3.6.1
LeFebvre et al

The selected base directory  must exist before
installation is attempted.

Do you want this directory created now [y,n,?,q] y
Using  as the package base directory.
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

Installing top as 

## Installing part 1 of 1.
[ verifying class  ]

Installation of  was successful.

Set Default Path

Set the default path of top command in user’s profile.

#echo $PATH
#vi ~.profile

How to Install Raid 1 in Solaris 10

# format
Searching for disks...done

       0. c1t0d0 
       1. c1t1d0 
Specify disk (enter its number): ^Z

# prtvtoc /dev/dsk/c1t0d0s2 > c1t0d0s2.vtoc
# fmthard -s c1t0d0s2.vtoc /dev/rdsk/c1t1d0s2
# df -kh
# metadb -a -c 3 -f c1t0d0s7 c1t1d0s7
# umount /export/home
# metadb -a -c 3 -f c1t0d0s7 c1t1d0s7
# umount /export/home0
# metadb -a -c 3 -f c1t0d0s7 c1t1d0s7
# metainit -f d11 1 1 c1t0d0s0
# metainit -f d12 1 1 c1t1d0s0
# metainit d10 -m d11
# metaroot d10
# metainit -f  d21 1 1 c1t0d0s1
# metainit -f  d22 1 1 c1t1d0s1
# metainit d20 -m d21
# metastat | grep %
# vi /etc/vfstab
#device         device          mount           FS      fsck    mount   mount
#to mount       to fsck         point           type    pass    at boot options
fd      -       /dev/fd fd      -       no      -
/proc   -       /proc   proc    -       no      -
/dev/dsk/c1t0d0s1       -       -       swap    -       no      -
/dev/md/dsk/d10 /dev/md/rdsk/d10        /       ufs     1       no      -
#/dev/dsk/c1t0d0s7      /dev/rdsk/c1t0d0s7      /export/home    ufs     2       yes     -
#/dev/dsk/c1t1d0s7      /dev/rdsk/c1t1d0s7      /export/home0   ufs     2       yes     -
/devices        -       /devices        devfs   -       no      -
sharefs -       /etc/dfs/sharetab       sharefs -       no      -
ctfs    -       /system/contract        ctfs    -       no      -
objfs   -       /system/object  objfs   -       no      -
swap    -       /tmp    tmpfs   -       yes     -

Teams – Red Hat and Fedora Welcome Ubuntu to GNOME and Wayland with Open Arms

Canonical’s Mark Shuttleworth revealed nothing about Ubuntu’s development team that worked with the GNOME Devs, but until more details were revealed, it looks like the Red Hat Desktop and Fedora teams have taken the first step in welcoming Ubuntu and Canonical to the GNOME- And Wayland projects, hoping that they will have a fruitful long-term cooperation for the coming years.

“As most of you probably know that Mark Shuttleworth just announced that they would switch back to GNOME 3 and Wayland for Ubuntu, so I would like to welcome them on behalf of the Red Hat desktop and Fedora teams and say that We are looking forward to working to work with large canonical and Ubuntu people like Allison Lortie and Robert Ancell on projects of common interest around GNOME, Wayland and hopefully Flatpak, “said Christian Schaller in his recent blog post.

We do not know about Flatpak because Canonical will not give up its Snappy technologies, which seem to be very popular with the IoT (Internet of Things) manufacturers, but support for the next generation Wayland display server could be implemented Ubuntu 18.04 LTS operating system along with the GNOME shell interface. We can not wait to see how things stand out. Ubuntu as a GNU / Linux distribution will also be very popular without Unity.

How to Install TightVNC viewer in Linux


TightVNC is a cross-platform free and open-source remote desktop software application.

Step 1: xStartup Installation

In order to install TightVNC, first install “X Window System” as prerequisites.

# yum groupinstall "X Window System" "Desktop"
# yum -y install tigervnc-server xorg-x11-fonts-Type1

Step 2: Configuration

Edit the TightVNC configuration file and set the geometry according to your monitor screen.

# vi /etc/sysconfig/vncservers
VNCSERVERARGS[1]="-geometry 1280x1024"

Step 3: Create User

Create test user so that user is able to view the GUI accordingly.

# useradd test
# passwd test
# su - test
# vncpasswd

Step 4: Start VNC Server

Start VNC Server, it will open the session against the users so that users are able to view the Graphical User Interface and enjoy.

# /etc/init.d/vncserver start
Shutting down VNC server: [  OK  ]
Starting VNC server: 1:test 
New 'test:1 (test)' desktop is test:1

Starting applications specified in /home/test/.vnc/xstartup
Log file is /home/test/.vnc/test:1.log

[  OK  ]
# chkconfig vncserver on

Prometheus: Solve montoring in the cloud

Hundreds of companies are now using the open-source Prometheus monitoring solution in production, across telecommunications and cloud providers across video streaming and databases.

In the run-up to CloudNativeCon + KubeCon Europe 2017, which takes place in Berlin from March 29 to 30, we spoke with Brian Brazil, the founder of Robust Perception, and one of the core developers of the Prometheus project, who at CloudNativeCon a keynote on Prometheus Will give. Be sure to catch the full Prometheus track at the conference.

With a traditional setup, there was a relatively small number of services, each with their own machine. Monitoring was based on machine metrics like CPU usage and free memory, which are the best way to alert to user problems. In a cloud Native world, where many different services not only divide machines, but the way in which they share them is in constant flux, such an approach is not scalable.

In the same way that the move has been made from the manual management of machines and services to tools such as Chef and now Kubernetes, we must make a similar transition in the surveillance area.

Prometheus client libraries allow you to orchestrate your applications for the metrics and KPIs that are important in your system. For third-party applications like Cassandra, HAProxy, or MySQL, there are a variety of exporters to reveal their useful metrics.

The data collected by Prometheus are enriched by labels. Labels are arbitrary key-value pairs that can be used to distinguish the development cluster from the production environment, or which HTTP endpoints the metric is broken.

The PromQL query language allows for aggregation based on these labels, the calculation of 95th percentile latencies per container, service or data center, prognosis, and any other mathematics that you want to do. What is more: If you are doing it graphically, you can point it out. This gives you the power to have warnings about what is really important to you and your users, and helps eliminate these late night alerts for non-problems.

How to create IPMP in Solaris 11


This article is aimed to give a walk through of how to create a Ldom in SUN/SPARC M6-32 machines. It provides a complete step to step procedure from scratch to the end.


Following steps should be taken care of before creating a Logical Domain.

# ipadm
NAME              CLASS/TYPE STATE        UNDER      ADDR
lo0               loopback   ok           --         --
   lo0/v4         static     ok           --
   lo0/v6         static     ok           --         ::1/128
net0              ip         ok           --         --
   net0/v4        static     ok           --
# ipadm delete-ip net0
# ipadm delete-ip net1
# ipadm create-ip net0
# ipadm create-ip net1
# ipadm create-ipmp ipmp0
# ipadm add-ipmp -i net0 -i net1 ipmp0
# ipadm create-addr -T static -a ipmp0/v4

Red Hat CloudForms 4.2 Improves Hybrid Cloud Management

Red Hat is upgrading its CloudForms hybrid cloud management platform with the new version 4.2, providing users with enhanced functionality. CloudForms allows the organization to manage multiple types of cloud deployments, including private and public clouds, as well as container platforms.
The CloudForms version 4.2 is based on the open source version ManageIQ Euwe which debuted December 20, 2016. Red Hat acquired ManageIQ in December 2012 for $ 104 million. Geert Jansen, Senior Director of Product Management for Red Hat CloudForms, explained that there are some differences between the open source ManageIQ project and the commercially supported CloudForms product.
“CloudForms includes a commercial PDF generation library and the appliance is based on Red Hat Enterprise Linux instead of CentOS,” Jansen told eWEEK.
Another difference between ManageIQ and CloudForms is the software lifecycle. ManageIQ outputs are released approximately every six months. Jansen explained that when a new version of ManageIQ comes out, the previous version is not supported and no patch updates are added.

What is OpenStack?

OpenStack is an open source cloud platform but that’s not all that OpenStack is. In a session at the OpenStack Summit here, Thierry Carrez, Director of Engineering, detailed a broader view of what the entity known as OpenStack is really all about – and it is much more than just the cloud. For Carrez, OpenStack’s common goal is to build on interoperable cloud software platform while the role of the OpenStack Foundation is about how to structure things so did development work can get done. One of the key things did the OpenStack Foundation Provides is something did Carrez referred by to as to asset lock. “It’s difficult to get different Organizations to collaborate if one is holding the keys to the kingdom,” Carrez said. “So you need a neutral venue for key assets of the community.”

Pokemon on Linux Systems

Trend Micro Researchers have an insidious new rootkit discovered family to Pokemon character Umbreon names that it remotely targeted devices could be controlled hackers.

The rootkit is designed to Linux systems are designed – with Intel and ARM chips – which means it could be used to access embedded computing devices , wrote senior threat researcher , Fernando Mercês .

It seems to have been written specifically for three platforms – x86 , x86-64 and ARM ( Raspberry Pi ) – and is highly mobile , with some additional tools in Python and Bash written in pure C.