recently  I experienced with a slow boot issue on my fedora 16 (Verne)

Due to iscsi service , my boot load time takes more than 15 mins, earlier it use to boot in less than 2 mins.

In short, will help to improve boot time…
As long as you do not use iscsi , it can certainly be disabled to speed up boot time.
before we run a command , we can check ourself with chkconfig –list command, to verify the iscsi service, whether its on or not , as follows.

Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.

akmods             0:off    1:off    2:on    3:on    4:on    5:on    6:off
iscsi              0:off    1:off    2:on    3:on    4:on    5:on    6:off
iscsid             0:off    1:off    2:off    3:on    4:on    5:on    6:off
jexec              0:on    1:on    2:on    3:on    4:on    5:on    6:on
livesys            0:off    1:off    2:off    3:on    4:on    5:on    6:off
livesys-late       0:off    1:off    2:off    3:on    4:on    5:on    6:off
named              0:off    1:off    2:off    3:off    4:off    5:off    6:off
netconsole         0:off    1:off    2:off    3:off    4:off    5:off    6:off
netfs              0:off    1:off    2:off    3:on    4:on    5:on    6:off
network            0:off    1:off    2:on    3:on    4:on    5:on    6:off
pcp                0:off    1:off    2:off    3:off    4:off    5:off    6:off
pmie               0:off    1:off    2:off    3:off    4:off    5:off    6:off
pmproxy            0:off    1:off    2:off    3:off    4:off    5:off    6:off
rrdcached          0:off    1:off    2:off    3:off    4:off    5:off    6:off
sandbox            0:off    1:off    2:off    3:off    4:off    5:on    6:off
vnstat             0:off    1:off    2:off    3:off    4:off    5:off    6:off

To disable the isci initiator and daemon you can do the following as root,

That will prevent the daemons from starting on boot and stopping them if they have already started.

To remove it , run as root

# rpm -e kernel-version

in a terminal (Main Menu > System Tools > Terminal) where version is the full release number. Enter

# rpm -q  kernel

to get the installed kernels.

or

Run this command as root/super user,

# package-cleanup –oldkernels

After loading packages you will be promoting to enter an option,as below…

Dependencies Resolved

==============================================================================================
Package                                           Arch                         Version                                        Repository                         Size
==============================================================================================
Removing:
kernel                                            i686                         3.1.5-2.fc16                                   @updates                           92 M
kernel-devel                                      i686                         3.1.5-2.fc16                                   @updates                           26 M
Removing for dependencies:
kmod-wl-3.1.5-2.fc16.i686                         i686                         5.100.82.112-1.fc16.5                          installed                         2.5 M

Transaction Summary
===============================================================================================
Remove        3 Packages

Installed size: 121 M
Is this ok [y/N]: y
Downloading Packages:
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
Erasing    : kmod-wl-3.1.5-2.fc16.i686-5.100.82.112-1.fc16.5.i686                                                                                                1/3
Erasing    : kernel-3.1.5-2.fc16.i686                                                                                                                            2/3
Erasing    : kernel-devel-3.1.5-2.fc16.i686                                                                                                                      3/3

Removed:
kernel.i686 0:3.1.5-2.fc16                                                      kernel-devel.i686 0:3.1.5-2.fc16

Dependency Removed:
kmod-wl-3.1.5-2.fc16.i686.i686 0:5.100.82.112-1.fc16.5

Complete!
That’s it. you have removed your old/unused kernels.

First, if you dont have anything critically important on your computer, and you are satisfied with its speed, you dont need raid. If your computer is fast enough but has critical data, and you do backups regularly No.

Here is where it gets tricky: Raid 0 is just striping, it will give you extra speed in the hard drive reads/writes, BUT you lose reliability – there is no redundancy which is fine as long as you have good backups, and backup religiously(as in once a day, every day)!

IF your data is any kind of important, you need to back it up if you want to run Raid 0!

How important is the computer and its information? How critically important is the data? How fast do you need it? If you have a business(or just family data) with critical data on it you may prefer raid 1(duplication of data-high cost, fast read but slower write performance), Raid 1 doubles your HD costs, but increases the computers’ reliability.

Raid 5 is the next cheapest/reliable array, you need at least 3 disks for a Raid 5 array, but 4, or 5 disks are more reliable, but costs much more than just a single drive.

>>       zip – package and compress (archive) files

# zip silence silence.zip

or more concisely

# zip -r silence.zip silence

>> unzip – list, test and extract compressed files in a ZIP archive

To  use unzip to extract all members of the archive letters.zip into the current directory and subdirectories below it, creating any subdirectories as
necessary:

# unzip silence.zip

To extract all members of letters.zip into the current directory only:

# unzip -j silence.zip

mydear friend , hope this link  will be bookmarked by you ;)

Type the following command to find out USB pen partition name:

[root@thiyag]# df
Filesystem     1K-blocks     Used Available Use% Mounted on
rootfs          51606140  6148584  44933428  13% /
devtmpfs          953540        0    953540   0% /dev
tmpfs             961808     1000    960808   1% /dev/shm
tmpfs             961808    40612    921196   5% /run
/dev/sda3       51606140  6148584  44933428  13% /
tmpfs             961808    40612    921196   5% /run
tmpfs             961808        0    961808   0% /sys/fs/cgroup
tmpfs             961808        0    961808   0% /media
/dev/sda5      251747076 83478108 155480900  35% /home
/dev/sda1         495844    78680    391564  17% /boot
/dev/sdb1        7898008        4   7898004   1% /media/2E3E-D0DE

We can use fdisk as well to get to know the USB partition,

[root@thiyag]# fdisk -l

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x9c68a144

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     1026047      512000   83  Linux
/dev/sda2         1026048     8759295     3866624   82  Linux swap / Solaris
/dev/sda3         8759296   113616895    52428800   83  Linux
/dev/sda4       113616896   625142447   255762776    5  Extended
/dev/sda5       113618944   625141759   255761408   83  Linux

Disk /dev/sdb: 8103 MB, 8103395328 bytes
196 heads, 32 sectors/track, 2523 cylinders, total 15826944 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc3072e18

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          32    15826943     7913456    7  HPFS/NTFS/exFAT

Once identified the partition name type the following command to format the usb pen in Linux
(caution you must select correct usb partition name, otherwise you will loss all the data on hard disk)

[root@thiyag]# mkfs.vfat /dev/sdb1
mkfs.vfat 3.0.12 (29 Oct 2011)
mkfs.vfat: /dev/sdb1 contains a mounted file system.

here we are getting an error as, “mkfs.vfat: /dev/sdb1 contains a mounted file system.”
So it asking us to unmount before we format the USB
here we go for unmount the mounted usb.

[root@thiyag]# umount /dev/sdb1

We havn’t get any error, so we unmounted it ;)

finally, use the following command to format your pendrive/usb drive.

# mkfs.ext3 /dev/sda1

To format as VFAT/FAT32 file system type the following command:

[root@thiyag]# mkfs.vfat /dev/sdb1
mkfs.vfat 3.0.12 (29 Oct 2011)
[root@thiyag]#

hope it works for you too ! :-)

Enable Google YUM repository

Add following to /etc/yum.repos.d/google.repo file:
32-bit

[google-chrome]
name=google-chrome - 32-bit
baseurl=http://dl.google.com/linux/chrome/rpm/stable/i386
enabled=1
gpgcheck=1
gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub

64-bit

[google-chrome]
name=google-chrome - 64-bit
baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
enabled=1
gpgcheck=1
gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub

Note: Both 32-bit and 64-bit repos can be placed in the same file.

Install Google Chrome with YUM (as root user)

Install Google Chrome Stable Version

## Install Google Chrome Stable version ##
yum install google-chrome-stable

Install Google Chrome Beta Version

## Install Google Chrome Beta version ##
yum install google-chrome-beta

Install Google Chrome Unstable Version

## Install Google Chrome Unstable version ##
yum install google-chrome-unstable

[ source ]

Install VLC Media Player
#1..First you need to configure RPM Fusion Repos so click here to download (After download right click and install this file)or Open the Treminal and issue the following command to root login and next command to install RPM Fusion Repos

 $ su - 

 #> rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release
 -stable.noarch.rpm

#2…Now Issue this command to install VLC Media Player

 #> yum install vlc

VLC Media Player is installed you can now access it from Applications.

[ Souce ]

1. Install the RPM Fusion repos…
   

   http://rpmfusion.org/Configuration

2. Install the akmod version of the 64-bit driver…
   

   su
   yum install akmod-wl

3. Reboot or restart NetworkManager and check the panel applet icon for available networks.

Some of you who recently switched to linux or who are planning to switch to linux, are may be looking for a good media player which will play every thing on Linux, or looking for how to install VLC, This post is a step to step guide about installing VLC on Fedora 12/13/14
So, just follow the steps or copy – paste them to install vlc on your machine. It does not matter what architecture you are using – x86_64 or i686 or i386

Step 1:
$su -c ‘yum localinstall –nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm’

Step 2: now run
$su -c ‘yum clean all’

Step 3: $su -c ‘yum install vlc’

All set to go. VlC is installed successfully.

When you have a website or a network, it’s helpful to be aware of any issues as soon as they occur. There are open source and freeware server/network monitoring tools that will supervise your infrastructure for any issues that may arise. These tools are meant to aid you in avoiding being taken offline and evaluating if your resource needs has outgrown your infrastructure.

In this article, we review our top 10 server/network monitoring tools. You will see a variety of server applications here so that you might find the tool (or tools) for your needs.

1. Monit

Monit not only monitors your server, but also attempts to remedy problems by taking predefined actions for certain situations. For example, if your database server crashes, Monit can automatically restart the service if this is the action that you want to take (hint: it usually is).

If you have more than one server that you need to monitor, then you can useM/Monit- an extended version of Monit that provides a simple way to monitor multiple machines.

There’s also an iPhone app available for M/Monit to help you conveniently check on your network without lugging around a laptop around.

2. Ganglia

When you have a cluster of machines, it’s difficult to see how the whole cluster is doing all at once. Ganglia, instead, presents an overview of the whole cluster. This is a great tool to have set up when you’re working with a server cluster; with that said, it may be overkill for single-machine set-ups.

3. Munin

Munin monitors and graphs system performance metrics. It can automatically produce daily/weekly/monthly/yearly performance graphs and reports of many important metrics. It comes with the ability to monitor core system resources, such as memory, disk space, CPU usage, server applications such as MySQL, Apache, and Squid.

One of Munin’s greatest strengths is how simple it is to extend. With just a few lines of code, you can write a plugin to monitor almost anything. Being so easy to extend means that Munin is also a good choice for graphing things unrelated to server performance, such as the number of user signups or website popularity.

4. Cacti

Cacti is similar to Munin in many ways. What is makes Cacti different though–and where it stands out in relation to Munin–is that it allows you to resize your graphs and view data for an arbitrary range. Whereas Munin has fixed daily, weekly, monthly and yearly graphs (unless you write a custom extension), Cacti lets you view your data however you want to: last 2 hours, last 4 days, last 6 months, out of the box. You can even visually select and zoom into regions on your graphs.

5. Nagios

Nagios is “the industry standard in IT infrastructure monitoring,”–well, at least that’s what it says on their website. Nagios can be complicated to install and configure, but its wealth of features are unmatched by any tool out in the market and is geared for the experienced IT network administrator. Nagios supports monitoring of multiple hosts and can send out alerts via email, pager (if you still use this ancient technology) or SMS/text messaging. Like Monit, it can also be configured to automatically respond to problems.

6. Zabbix

Zabbix is a feature-packed monitoring tool. It has great visualization support including user-defined views, zooming, and mapping. It can send out alerts via email, SMS or instant message. It also provides audible alerts, which can be useful when you’re physically near the monitoring machine.

7. Observium

Observium is geared towards Linux, BSD and Cisco networks. It supports auto discovery of your network infrastructure, finding the networks that you’re likely interested in monitoring; this feature can be compared to how your Wi-Fi software automatically finds signals in range that you can jack into. Observium provides detailed graphs, and can be set up alongside Nagios to provide alerts. It also integrates well with Collectd (featured below) for a more robust interface.

8. Zenoss

Zenoss is an open source version of the commercial server monitoring tool Zenoss Enterprise, written entirely in Python. It supports the Nagios plugin format, so many existing Nagios plugins can be used in Zenoss. One of the main highlights of Zenoss is its powerful yet simple to use user interface.

9. Collectd

Collectd is similar to Munin and Cacti in that it focuses on graphing system metrics. Where it excels in is that it is designed specifically for performance and portability; this ultimately means it’s great on rugged systems, low-end systems, and embedded systems. Being designed for performance and low-system resource use means that Collectd can gather data every 10 seconds without interfering with your server processes, providing extremely high-resolution statistics. You can write extensions for it in C, Perl or Java.

10. Argus

Argus focuses on the monitoring of network services, and supports IPv4 and IPv6. It has a nice alert escalation procedure: after sending out an alert and the problem still isn’t resolved within a fixed amount of time (because the systems admin is at home enjoying his sleep), another alert will be sent out to someone else.

Source