I'll offer up a few methods to collect important information from the system you may need to verify, troubleshoot, or give to remote support.
First, let's gather information about the processor. This is easily done as follows:
# cat /proc/cpuinfo
This command gives you information on the processor speed, quantity, and model. Using grep in many cases can give you the desired value.
A check that I do quite often is to ascertain the quantity of processors on the system. So, if I have purchased a dual processor quad-core server, I can run:
# cat /proc/cpuinfo | grep processor | wc -l
Another piece of information I may require is disk information. This can be gotten with the df command. I usually add the -h flag so that I can see the output in gigabytes or megabytes. # df -h also shows how the disk was partitioned
And to end the list, here's a way to look at the firmware of your system—a method to get the BIOS level and the firmware on the NIC.
To check the BIOS version, you can run the dmidecode command. Unfortunately, you can't easily grep for the information, so piping it is a less efficient way to do this. On my Lenovo T61 laptop, the output looks like this:
#dmidecode | less
...
BIOS Information
Vendor: LENOVO
Version: 7LET52WW (1.22 )
Release Date: 08/27/2007
...
This is much more efficient than rebooting your machine and looking at the POST output.
To examine the driver and firmware versions of your Ethernet adapter, run ethtool:
# ethtool -i eth0
driver: e1000
version: 7.3.20-k2-NAPI
firmware-version: 0.3-0
That’s it……
Sunday, June 28, 2009
Saturday, June 27, 2009
Getting back the root password
You forgot your root password. Now you'll just have to reinstall the entire machine. I've seen more than a few people do this. But it's easy to get on the machine and change the password. This doesn't work in all cases (like if you made a GRUB password and forgot that too), but here's how you do it in a normal case with a Cent OS Linux example.
First reboot the system. When it reboots you'll come to the GRUB screen. Move the arrow key so that you stay on this screen instead of proceeding all the way to a normal boot.
Grub screen after reboot:
CentOS-4 i386 (2.7.5-42.ELsmp)
CentOS-4 i386-up (2.7.5-42.EL)
Next, select the kernel that will boot with the arrow keys, and type E to edit the kernel line.
Ready to edit the kernel line:
Root (hd0,0)
Kernel / vmlinuz-2.7.5-42.ELsmp ro root=LABEL= / rhgb quiet
initrd / initrd-2.7.5-42.ELsmp.img
Use the arrow key again to highlight the line that begins with kernel, and press E to edit the kernel parameters. When you get to the screen, simply append the number 1 to the arguments.
Append the argument with the number 1:
grub edit > kernel / vmlinuz 2.7.5-42 ELsmp ro root = LABEL = / rhgb quiet 1
Then press Enter, B, and the kernel will boot up to single-user mode. Once here you can run the passwd command, changing password for user root:
sh-3.00# passwd
New UNIX password:
Retype new UNIX password:
passwd: all authentication tokens updated successfully
Now you can reboot, and the machine will boot up with your new password.
First reboot the system. When it reboots you'll come to the GRUB screen. Move the arrow key so that you stay on this screen instead of proceeding all the way to a normal boot.
Grub screen after reboot:
CentOS-4 i386 (2.7.5-42.ELsmp)
CentOS-4 i386-up (2.7.5-42.EL)
Next, select the kernel that will boot with the arrow keys, and type E to edit the kernel line.
Ready to edit the kernel line:
Root (hd0,0)
Kernel / vmlinuz-2.7.5-42.ELsmp ro root=LABEL= / rhgb quiet
initrd / initrd-2.7.5-42.ELsmp.img
Use the arrow key again to highlight the line that begins with kernel, and press E to edit the kernel parameters. When you get to the screen, simply append the number 1 to the arguments.
Append the argument with the number 1:
grub edit > kernel / vmlinuz 2.7.5-42 ELsmp ro root = LABEL = / rhgb quiet 1
Then press Enter, B, and the kernel will boot up to single-user mode. Once here you can run the passwd command, changing password for user root:
sh-3.00# passwd
New UNIX password:
Retype new UNIX password:
passwd: all authentication tokens updated successfully
Now you can reboot, and the machine will boot up with your new password.
Unmounting the unresponsive DVD drive
when we pushes the Eject button on the DVD drive of a server running a certain Redmond-based operating system, it will eject immediately. He then complains that, in most enterprise Linux servers, if a process is running in that directory, then the ejection won't happen. For too long as a Linux administrator, I would reboot the machine and get my disk on the bounce if I couldn't figure out what was running and why it wouldn't release the DVD drive. But this is ineffective.
Here's how you find the process that holds your DVD drive and eject it to your heart's content: First, simulate it. Stick a disk in your DVD drive, open up a terminal, and mount the DVD drive:
# mount /media/cdrom
# cd /media/cdrom
# while [ 1 ]; do echo "All your drives are belong to us!"; sleep 30; done
Now open up a second terminal and try to eject the DVD drive:
# eject
You'll get a message like:
umount: /media/cdrom: device is busy
Before you free it, let's find out who is using it.
# fuser /media/cdrom
You see the process was running and, indeed, it is our fault we can not eject the disk.
Now, if you are root, you can exercise your godlike powers and kill processes:
# fuser -k /media/cdrom
Boom! Just like that, freedom. Now solemnly unmount the drive:
# eject
That’s it…
Here's how you find the process that holds your DVD drive and eject it to your heart's content: First, simulate it. Stick a disk in your DVD drive, open up a terminal, and mount the DVD drive:
# mount /media/cdrom
# cd /media/cdrom
# while [ 1 ]; do echo "All your drives are belong to us!"; sleep 30; done
Now open up a second terminal and try to eject the DVD drive:
# eject
You'll get a message like:
umount: /media/cdrom: device is busy
Before you free it, let's find out who is using it.
# fuser /media/cdrom
You see the process was running and, indeed, it is our fault we can not eject the disk.
Now, if you are root, you can exercise your godlike powers and kill processes:
# fuser -k /media/cdrom
Boom! Just like that, freedom. Now solemnly unmount the drive:
# eject
That’s it…
Friday, June 26, 2009
Dynamic Host Configuration Protocol(DHCP) Server Configuration
Instal your DHCP server using
#yum -y install dhcp
Configure the dhcp.conf
#vi /etc/dhcpd.conf
ddns-update-style interim;
ignore client-updates;
#Network For DHCP
subnet 192.168.0.0 netmask 255.255.255.0 {
# — Router IP
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
#Option For Domain
option nis-domain “domain.org”;
option domain-name “domain.org”;
#Option for DNS Server
option domain-name-servers 192.168.1.1;
option time-offset -18000; # Eastern Standard Time
# Range Ip For DHCP
range dynamic-bootp 192.168.0.128 192.168.0.254;
default-lease-time 21600;
max-lease-time 43200;
#yum -y install dhcp
Configure the dhcp.conf
#vi /etc/dhcpd.conf
ddns-update-style interim;
ignore client-updates;
#Network For DHCP
subnet 192.168.0.0 netmask 255.255.255.0 {
# — Router IP
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
#Option For Domain
option nis-domain “domain.org”;
option domain-name “domain.org”;
#Option for DNS Server
option domain-name-servers 192.168.1.1;
option time-offset -18000; # Eastern Standard Time
# Range Ip For DHCP
range dynamic-bootp 192.168.0.128 192.168.0.254;
default-lease-time 21600;
max-lease-time 43200;
5 Useful Linux / Unix Commands
1). Show installed but unused linux headers, image, or modules:
dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d'
If you would also like to purge them too:
dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' | xargs sudo apt-get -y purge
2). Rip audio from a video file:
mplayer -ao pcm -vo null -vc dummy -dumpaudio -dumpfile
You can also extract the sound from a flv and make an mp3 with:
ffmpeg -i input.flv -f mp3 -vn -acodec copy ouput.mp3
3). Stream YouTube URL directly to mplayer:
mplayer -fs $(echo "http://youtube.com/get_video.php?$(curl -s $youtube_url | sed -n "/watch_fullscreen/s;.*\(video_id.\+\)&title.*;\1;p")")
(Replace $youtube_url with any youtube URL)
4). Purge configuration files of removed packages on debian based systems:
sudo aptitude purge `dpkg --get-selections | grep deinstall | awk '{print $1}'`
5). Convert images to a multi-page pdf:
convert -adjoin -page A4 *.jpeg multipage.pdf
dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d'
If you would also like to purge them too:
dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' | xargs sudo apt-get -y purge
2). Rip audio from a video file:
mplayer -ao pcm -vo null -vc dummy -dumpaudio -dumpfile
You can also extract the sound from a flv and make an mp3 with:
ffmpeg -i input.flv -f mp3 -vn -acodec copy ouput.mp3
3). Stream YouTube URL directly to mplayer:
mplayer -fs $(echo "http://youtube.com/get_video.php?$(curl -s $youtube_url | sed -n "/watch_fullscreen/s;.*\(video_id.\+\)&title.*;\1;p")")
(Replace $youtube_url with any youtube URL)
4). Purge configuration files of removed packages on debian based systems:
sudo aptitude purge `dpkg --get-selections | grep deinstall | awk '{print $1}'`
5). Convert images to a multi-page pdf:
convert -adjoin -page A4 *.jpeg multipage.pdf
Sunday, June 21, 2009
How to restore Grub from a live cd
This will restore grub if you already had grub installed but lost it to a windows install or some other occurence that erased/changed your MBR so that grub no longer appears at start up or it returns an error.
This how to is written for Ubuntu but should work on other systems. The only thing to take note of, when you see "sudo" that will mean to you that the following command should be entered at a root terminal.
Boot into the live Ubuntu cd. This can be the live installer cd or the older live session Ubuntu cds.
When you get to the desktop open a terminal and enter.
Code:
sudo grub
This will get you a "grub>" prompt (i.e. the grub shell). At grub>. enter these commands
Code:
find /boot/grub/stage1
This will return a location. If you have more than one, select the installation that you want to provide the grub files.
Next, THIS IS IMPORTANT, whatever was returned for the find command use it in the next line (you are still at grub>. when you enter the next 3 commands)
Code:
root (hd?,?)
Again use the value from the find command i.e. if find returned (hd0,1) then you would enter root (hd0,1)
Next enter the command to install grub to the mbr
Code:
setup (hd0)
Finally exit the grub shell
Code:
quit
That's it. Grub will be installed to the mbr.
When you reboot, you will have the grub menu at startup.
This how to is written for Ubuntu but should work on other systems. The only thing to take note of, when you see "sudo" that will mean to you that the following command should be entered at a root terminal.
Boot into the live Ubuntu cd. This can be the live installer cd or the older live session Ubuntu cds.
When you get to the desktop open a terminal and enter.
Code:
sudo grub
This will get you a "grub>" prompt (i.e. the grub shell). At grub>. enter these commands
Code:
find /boot/grub/stage1
This will return a location. If you have more than one, select the installation that you want to provide the grub files.
Next, THIS IS IMPORTANT, whatever was returned for the find command use it in the next line (you are still at grub>. when you enter the next 3 commands)
Code:
root (hd?,?)
Again use the value from the find command i.e. if find returned (hd0,1) then you would enter root (hd0,1)
Next enter the command to install grub to the mbr
Code:
setup (hd0)
Finally exit the grub shell
Code:
quit
That's it. Grub will be installed to the mbr.
When you reboot, you will have the grub menu at startup.
Saturday, June 20, 2009
How can access Windows NTFS partition from Linux
Access Windows NTFS partition from Linux
Step 1.
Install rpmforge-release package. Download it from DAG (http://dag.wieers.com/rpm/packages/rpmforge-release/).
Step 2.
yum install fuse fuse-ntfs-3g dkms dkms-fuse
Step 3.
Mount your ntfs volume. /dev/sdc5 is my ntfs partition.
mount -t ntfs-3g /dev/sdc5 /mnt/win_c
Step 1.
Install rpmforge-release package. Download it from DAG (http://dag.wieers.com/rpm/packages/rpmforge-release/).
Step 2.
yum install fuse fuse-ntfs-3g dkms dkms-fuse
Step 3.
Mount your ntfs volume. /dev/sdc5 is my ntfs partition.
mount -t ntfs-3g /dev/sdc5 /mnt/win_c
Fedora 10 Installation Guide
Installation Media
Fedora 10 is provided as either CD-ROM's or DVD-ROM's for installation. You can either download the multiple CD sets or single DVD for installation. The DVD-ROM disk is preferred and recommended method of installation. Booting the DVD or booting from CD#1 will start the installer which will allow Fedora to be installed on your computer or for you to upgrade an existing Fedora on your machine. The following steps were done with the single DVD installation.
There are also "LiveCD's" which can be booted and will run a basic Fedora 10 in memory while also providing a simpler method of installation (not as complete at the DVD or multi-CD method). The default LiveCD ships with Gnome (ex: F10-i686-Live.iso). There is a specific LiveCD that ships with KDE. Both provide an installer however they come with significantly less software than the DVD. Also they require more memory in order to be usable. The LiveCD may be useful for demonstration.
Note: To upgrade an existing Fedora installation you cannot use a Live disk.
Physical Installation
It is highly recommended you read the Fedora Release Notes and official Installation Guide before installing Fedora.
An additional recommendation is to read Common Problems before installing.
Obtain the Fedora 10 DVD image or multi-CD set images from a Fedora mirror (or use the torrent) and burn to DVD. (For more information on how to download Fedora CD's or DVD).
Boot from the DVD. If you choose to use a LiveCD please note that the following steps will differ.
NOTE: The Fedora 10 Installer (anaconda) is very minimal and most configuration steps will need to be done post-installation.
I did a Custom Install of Fedora 10.
* Network Setup
Fedora 10 uses NetworkManager for automatically configuring the network for installation. Users will only be prompted to set their 'hostname' (e.g. 'mycomputer').
* Root password
This is your "Administrator" or "Superuser" password that lets you access everything on your system. Pick a good password and remember it.
* Partitioning
o If you have an empty hard drive or wish to delete the entire contents of your drive, then let the installer automatically partition or remove everything and partition.
o If you wish to dual-boot or save some contents on your drive, then select custom partitioning. I recommend at least 3 partitions: an 8-12GB / main partition, a 10+GB /home partition and a 1-2GB partition. The main partition is where your applications will be installed. The /home partition will hold all your personal data (make this as large as you can). The should be at least as large as your physical memory (if you wish to support things like ACPI hibernate).
* Boot Loader
o If you have a blank harddrive or wish Fedora to be your Primary Operating System, then leave the default options here. This also works for dual booting with other systems (ex: Windows).
o If you wish to preserve Windows as your primary operating system, then install Grub on the / partition, NOT the MBR. To do this, select Change device on the Install boot loader screen and install to First sector of boot partition. I use Bootpart from Windows 2000/XP to load Linux. An alternative to Bootpart is the NT OS Loader + Linux mini-HOWTO (also Grub Win2K Howto). I recommend this so you do not corrupt your Windows installation in a Dual-Boot environment. [NOTE] There is an example configuration available. This does take more work, and the default option on the MBR will also work. This will also work for users who are triple booting Vista/XP/Fedora (as I do).
* General Package Selection
The primary options for installation are the following. You can select these and skip individual package selection (next step) if you plan to install most of your software from online (via YUM). It is recommended you at least pick certain applications.
o Office and Productivity - [Highly Recommended]
o Software Development - [Highly Recommended / Required]
o Web Server - [Optional (useful for web developers)]
Add Additional Software Repositories - [NOT Recommended at Install time]. You do have the option of adding helpful repositories during install. This will give access to MANY more applications than included on the CD's or DVD. However this requires a high-speed internet access that is detected by the Fedora Installer. This will also significantly increase the installation time.
If you select Customize now you will be taken to the Individual Package Selection. The Fedora installer will usually have most of the necessary defaults, properly selected. You may skip this step.
* Individual Package Selection - apx 4.5-5.5GB. - It is significantly helpful to grab a some specific important packages (to reduce unnecessary downloading later). You are free to select whatever you want. The following in my experience are common useful suggestions:
o Desktop Environments
+ [Highly Recommended] - Select both GNOME Desktop Environment and KDE (K Desktop Environment)
o Applications - The default selection of applications is sufficient. Note the following:
+ [Recommended] - Graphical Internet - Add thunderbird as an email client.
+ [Recommended] - Sound and Video - Add k3b for CD/DVD creation.
o Development
+ [Recommended] - Select GNOME Software Development, KDE Software Development and X Software Development.
+ [Recommended/Optional] - Select Fedora Packager - Useful for some software building/administration.
o Servers
+ [Recommended] - Add Server Configuration Tools.
+ [Required] - Add Windows File Server (required to share files with Windows computers).
o Base System
+ [Recommended] - Add System Tools.
+ [Optional] - Deselecting some items in Dial-up Networking Support, Fonts (lots of foreign fonts) and Hardware Support (lots of various WiFi), and Input Methods may reduce unwanted/unusable software depending on your location and hardware.
Install the selected packages and reboot.
For users who opted to install grub on the first sector of the / partition instead of the MBR, you will be required to setup NTLDR to boot Linux.
For the first boot:
* License - Accept any licenses for Fedora
* Create User - Create at least 1 user account for yourself. Always use that account. DO NOT use root as your personal account. The root account will NOT be permitted to login into the graphical desktop.
* Date and Time - Network Time Protocol - Enable this ONLY if you have an active working internet connection that is on (ex: broadband, T1, DSL). You do not need to check the time server every time the service starts.
* Hardware Profile - Fedora uses smolt to provide basic non-intrusive information on your specific installation. While this may be helpful to Fedora developers, some may consider it a privacy issue. Please understand what information is being sent before you allow it to do so. I personally do not sent profile information.
Setup sudo
Fedora, like all other Linux distributions, has a root user and has individual users. The root is the "superuser", somewhat similar to "Administrator" in Windows.
Use the personal account you created at First Boot for daily use root only for administration/configuration. To run as 'root' use su or sudo commands. However sudo requires setup. As root run:
echo 'loginname ALL=(ALL) ALL' >> /etc/sudoers
Where 'loginname' is your user account.
Use 'ALL=(ALL) NOPASSWD:ALL' if you don't want to be prompted a password.
If you are prompted for a password with 'sudo' it is the user password, not root.
Example:
[anoop@home ~]$ su
Password: <--- Enter root password
[root@home anoop]# echo 'mirandam ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers
[root@home anoop]# exit
exit
The following is an example of how sudo lets you execute root commands:
[anoop@home ~]$ du -sh /root
du: `/root': Permission denied <--- Fails!!!
[anoop@home ~]$ sudo du -sh /root
163M /root <--- Works!!!
NOTE: Every command provided on this page will work if you remove sudo from the command. However this requires you must be logged in as 'root'. An alternative to using sudo is to use su to login as root, before executing a command.
Graphical Bootloader - Plymouth
Fedora 10 replaces the previous graphical bootup system (which used the X-server) with a simpler system that uses kernel modesetting. However modesetting drivers are not available for all hardware yet. Please see: Plymouth.
Note: The following is optional. If no kernel modesetting is available a simple text based scroll bar should show up with booting Fedora.
In order to see the graphical boot, you must enable a mode setting for your video. Most users will find vesafb allows most standard VGA resolutions. Some examples are in Linux Kernel Documentation / fb / vesafb.txt and also here. You must have a proper Kernel mode number. For example I selected: 0x318 for 1024x768x16M resolution on a desktop CRT monitor.
As 'root', edit /boot/grub/grub.conf, and add 'vga=0x318' to the end of the kernel line. For example:
title Fedora (2.6.27.5-117.fc10.i686)
root (hd0,9)
kernel /boot/vmlinuz-2.6.27.5-117.fc10.i686 ro root=UUID=bb061789-157b-4cb2-85c8-633026e8df1e rhgb quiet vga=0x318
initrd /boot/initrd-2.6.27.5-117.fc10.i686.img
The next time you reboot, you should see the Plymouth graphical booter.
NOTE: You may use vga=ask instead. Follow the instructions you see on the screen and remember the number you used. Replace the number with the proper value in grub.conf as I did above.
NOTE: The resolution you select only applies to the graphical boot. You may use different resolutions/settings when you are using Fedora. It is acceptable to select a lower resolution for booting.
Setup yum
Fedora uses yum to install and update its software. When connected to the internet it will automatically determine application dependencies.
Fedora Repositories
Fedora typically has 2 repositories enabled by default: fedora (the same packages that come on any combination of the CD's or DVD's) and updates (updated packages, newer than fedora repository).
Third Party Repositories
For applications that are against Fedora policies (MP3, DVD, MPEG, Binary Drivers, etc), a third party repository should be used. The recommended repository for Fedora is: RPMFusion. For the purpose of this guide, (most) all needs are met by the RPMFusion repository, other requirements are stated.
To set up the RPMFusion repositories:
[anoop@home ~]$ sudo rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
[anoop@home ~]$ sudo rpm -ivh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm
[anoop@home ~]$ sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-*
Install Nvidia Driver
In order to provide more complete information on the Nvidia driver, please see: Fedora Nvidia Driver Install Guide ( http://www.mjmwired.net/resources/mjm-fedora-nvidia.html).
Network Management
Fedora 10 uses NetworkManager by default. The primary settings for any network devices will be automatically selected at installation time. Since there is no screen for selecting networking options, most devices will default to using DHCP.
Using NetworkManager has greatly improved networking for many wireless and some less common devices (mobile broadband, GSM, etc.), it may still have problems with some configurations. NetworkManager development and integration into Fedora is still an ongoing effort.
NOTE: The following steps do NOT apply to all users. NetworkManager is highly recommended for Laptop users, especially using wireless with security.
Disabling NetworkManager and Enabling network Service
On machines with a fixed networking device and a fixed IP address (e.g. desktop, server, appliance), it might be more practical to disable NetworkManager and use the older network service. Additionally users requiring virtual device types (bridging, bonding, or VLANs) will also need to use the network service.
Note that the Fedora 10 installer disables the network service by default. To switch to using the network service:
First disable NetworkManager and prevent it from automatically loading:
[anoop@home ~]$ sudo /etc/init.d/NetworkManager stop
Stopping NetworkManager daemon: [ OK ]
[anoop@home ~]$ sudo /sbin/chkconfig --level 35 NetworkManager off
Next, configure your network settings:
[anoop@home ~]$ sudo system-config-network
You should have an eth0 device already showing. To configure the IP settings click on Edit. Do not forget to set DNS on the DNS tab (if you're using fixed IP's). Make sure the eth0 is selected as Active. Then File > Save and quit.
Next, enable the service and make sure it loads at next boot:
[anoop@home ~]$ sudo /etc/init.d/network start
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
[anoop@home ~]$ sudo /sbin/chkconfig --level 35 network on
While it may be possible to re-activate your network without a reboot, it may be recommended to reboot.
Startup Applications Requiring Network
Some applications require the network to be initialized during boot. If you are using NetworkManager and having these problems, edit /etc/sysconfig/network as 'root' and add the following line:
NETWORKWAIT=1. Or run:
[anoop@home ~]$ sudo su -c 'echo NETWORKWAIT=1 >> /etc/sysconfig/network'
Install RealPlayer
Note: Currently these instructions only apply to Fedora 32-bit.
Download RealPlayer 11.0 GOLD from: http://www.real.com/linux/.
Select: "Advanced Installation Options RedHat Package"
Install RealPlayer:
[anoop@home Download]$ sudo rpm -ivh RealPlayer11GOLD.rpm
RealPlayer/HelixPlayer Forums: https://helixcommunity.org/projects/player/forums
NOTE: Totem issues: If the Totem-Mozilla-Plugin tries to load RealPlayer content instead of RealPlayer, try removing the plugin:
[anoop@home ~]$ sudo yum remove totem-mozplugin
Install MP3 Players
Fedora ships without any form of MP3 playback. In order to add MP3 playback you must install from a 3rd party. The following requires the use of the RPMFusion repositories.
XMMS: simple, older GUI, minimalistic features (but still popular)
* Installation through yum:
[anoop@home ~]$ sudo yum install xmms xmms-mp3 xmms-faad2 xmms-pulse xmms-skins
Audacious: (A fork of Beep Media Player - BMP). XMMS rebuilt to be a little bit more modern. Still basic but much better than XMMS.
* Installation through yum:
[anoop@home ~]$ sudo yum install audacious audacious-plugins-freeworld*
NOTE: There is a '*' at the end.
Rhythmbox/Gstreamer - A simple audio application similar to iTunes layout.
* Most of Rhythmbox and the Gstreamer system should be installed when installing Gnome (mentioned above). The missing components are just the MP3 (and other media) plugins.
* Installation through yum:
[anoop@home ~]$ sudo yum install rhythmbox gstreamer-plugins-ugly gstreamer-plugins-bad gstreamer-ffmpeg
Amarok - A modern feature rich media player application.
* It is helpful to have KDE installed first as this will reduce the download.
* Installation through yum:
[anoop@home ~]$ sudo yum install amarok xine-lib-extras-freeworld
K3B CD-Burner MP3 Audio Decoding:
* If you wish to make audio CD's in K3b from MP3's, install the following:
* Using yum:
[anoop@home ~]$ sudo yum install k3b-extras-freeworld
Note: PulseAudio - I was able to run most all these applications with either their default settings or using PulseAudio plugins enabled.
Install Media Players
Fedora ships with a limited set of media player for both audio and video. For audio please read the MP3 player notes. For video and other multimedia (DVD, etc.) we will also be making use of a 3rd party repository: RPMFusion. Make sure to have the RPMFusion repositories configured before executing the following. Note that many "dependancies" in libraries, plugins and codecs are shared between these applications and also the MP3 player applications.
The most popular media players (in order) are: MPlayer, Xine and VLC. Each has its own strengths. Install whichever you prefer although the first 2 are recommended.
MPlayer - MPlayer comes in a command line only interface (mplayer) or skinable GUI and it also has a powerful encoding tool MEncoder (also great for ripping or compressing audio/video). Additionally there is a highly functional web plugin allowing for many popular formats in Firefox/Mozilla (WMV, QuickTime, etc.).
* Installation through yum with RPMFusion enabled:
[anoop@home ~]$ sudo yum install mplayer mplayer-gui gecko-mediaplayer mencoder
* Note that mencoder is optional but provides many encoding functions.
* Binary Codecs: Please install the Binary Codecs for further support of formats that MPlayer does not directly support.
* MPlayer should work automatically defaulted to PulseAudio.
Xine - Xine is similar to MPlayer in many ways however lacking the command line application and encoder. However has fully supported DVD playback with proper navigation.
* Installation through yum with RPMFusion enabled:
[anoop@home ~]$ sudo yum install xine xine-lib-extras xine-lib-extras-freeworld
* Binary Codecs: Please install the Binary Codecs for further support of formats that Xine does not directly support.
* DVD Playback: To properly play DVDs please see DVD Playback.
* Xine Crashing: If you are experiencing Xine crashing immediately after loading please read this: Xine F10 Crash.
Binary Codecs - The MPlayer projects maintains a package full of binary codecs for which no directly open source option exists, some of these files include Windows DLL's. These are shared by both Xine and MPlayer. NOTE: There is significant variation depending on your architecture (i386, x86_64, ppc). The 32bit i386 works the best.
* Navigate to: http://www.mplayerhq.hu/MPlayer/releases/codecs/
* Select the package (.tar.bz2) best matching your version of Fedora/Architecture. Generally 32-bit users will use: all-20071007.tar.bz2.
* Install the codecs (32-bit for example):
[anoop@home Download]$ sudo mkdir -p /usr/lib/codecs
[anoop@home Download]$ sudo tar -jxvf all-20071007.tar.bz2 --strip-components 1 -C /usr/lib/codecs/
VLC - VLC is a simpler media player with an easy to use interface. It also supports DVD playback. While most needs should be met with Xine and MPlayer some prefer VLC.
* Installation through yum with RPMFusion enabled:
[anoop@home ~]$ sudo yum install vlc
* DVD Playback: To properly play DVDs please see DVD Playback.
DVD Playback - Due to non-technical reasons, the libdvdcss package currently exists in the Livna repository. Either use the Livna repository for this single package, or manually download and install it:
* Setup the Livna Repository:
[anoop@home ~]$ sudo rpm -ivh http://rpm.livna.org/livna-release.rpm
[anoop@home ~]$ sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-livna
* Installation through yum with Livna enabled:
[anoop@home ~]$ sudo yum install libdvdcss
SELinux Issues - The package ffmpeg-libs gave at least 2 SELinux AVC denials, the fix from the Troubleshooter was:
[anoop@home ~]$ sudo chcon -t textrel_shlib_t '/usr/lib/sse2/libpostproc.so.51.2.0'
[anoop@home ~]$ sudo chcon -t textrel_shlib_t '/usr/lib/sse2/libswscale.so.0.6.1'
Install Microsoft Truetype Fonts
The official source for the package is http://corefonts.sourceforge.net/.
There is a request for RPMFusion to package this. From that I am providing an updated SPEC file.
You have to build the RPM using the chosen SPEC file. For convenience I have created the RPM (please do not link directly to this file):
msttcore-fonts-2.0-3.noarch.rpm
[anoop@home Download]$ sudo rpm -ivh msttcore-fonts-2.0-3.noarch.rpm
Note: If have upgraded from Fedora 8 or some a previous version of Fedora. Please see Fedora 8 - Truetype Fonts on removing the older packages.
Note: Fedora encourages the use of the Liberation Fonts. These should be installed by default (and included on the DVD), however if not, please run:
[anoop@home ~]$ sudo yum install liberation-fonts
Disable Unneeded Services/Daemons
Information regarding services and their functions can be found on: Services in Fedora 10 (http://www.mjmwired.net/resources/mjm-services-f10.html).
For information on how to manage services in Fedora please read: Managing Services in Fedora (http://www.mjmwired.net/resources/mjm-fedora-manage-services.html).
Adobe Flash Plugin
The Adobe Flash plugin is available from Adobe's website. Users can install the RPM directly or use Adobe's YUM repository (recommended). Please note the plugin will not work directly on 64-bit browsers without some re-configuration.
For yum users (RECOMMENDED):
Install the Adobe YUM repository, and install through yum:
[anoop@home Download]$ sudo rpm -ivh http://linuxdownload.adobe.com/adobe-release/adobe-release-i386-1.0-1.noarch.rpm
[anoop@home Download]$ sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-adobe-linux
[anoop@home Download]$ sudo yum install flash-plugin
For manual installation: For users without yum:
Go to Install a different version of Adobe Flash Player and select:
Select an operating system: Linux
Select an installer type: .rpm for Linux.
Download the .rpm file (.rpm for Linux (x86)) and save it to disk.
Install:
[anoop@home Download]$ sudo rpm -ivh flash-plugin-10.0.12.36-release.i386.rpm
Installation on Fedora 64-bit
The following steps are required for Fedora 64-bit users.
First install the Adobe YUM repository, as stated above:
[anoop@home Download]$ sudo yum install nspluginwrapper.{i386,x86_64} alsa-plugins-pulseaudio.i386
[anoop@home Download]$ sudo yum install flash-plugin
Java Runtime Environment
The standard installation of Fedora 10 should install OpenJDK (based off of Sun Java). However if not, it can be installed using YUM:
[anoop@home ~]$ sudo yum install java-1.6.0-openjdk java-1.6.0-openjdk-plugin
With OpenJDK installed, Java application and Web applets should automatically work. Unfortunately some applets may not run properly and the OpenJDK might have some limitations. Majority of user should find OpenJDK perfect for everyday use.
Using Sun Java Instead
If you require Sun Java or if OpenJDK does not work properly, you can download Sun Java and use it in Fedora.
Download the Java package from:
http://java.sun.com/javase/downloads/index.jsp
Select: Java SE Runtime Environment (JRE) 6 Update 12 (the JDK is for developers)
On the next page, for Platform select "Linux" for 32-bit users, and "Linux x64" for 64-bit users.
For Language select "Multi-language". Also accept the license agreement, and hit "Continue".
On the next page, select the RPM option:
Java SE Runtime Environment 6u12
jre-6u12-linux-i586-rpm.bin 18.72 MB (32-bit users)
jre-6u12-linux-x64-rpm.bin 18.20 MB (64-bit users)
To install (32-bit example):
[anoop@home Download]$ sudo sh jre-6u12-linux-i586-rpm.bin
You will need to hit 'space' till it reaches the end, then type 'yes'. You should see the RPM installing. If you do not, manually install it via sudo rpm -ivh.
When running the java command, Fedora will default to using OpenJDK. In order to use Sun Java, use the alternatives command.
To setup the Java runtime, perform the following (applies to both 32-bit and 64-bit users):
[anoop@home Download]$ sudo /usr/sbin/alternatives --install /usr/bin/java java /usr/java/default/bin/java 20000
The Mozilla/Firefox browser plugin for 32-bit users:
[anoop@home Download]$ sudo /usr/sbin/alternatives --install /usr/lib/mozilla/plugins/libjavaplugin.so \
libjavaplugin.so /usr/java/default/plugin/i386/ns7/libjavaplugin_oji.so 20000
For 64-bit users:
[anoop@home Download]$ sudo /usr/sbin/alternatives --install /usr/lib64/mozilla/plugins/libjavaplugin.so \
libjavaplugin.so.x86_64 /usr/java/default/lib/amd64/libnpjp2.so 20000
Note: If you wish to switch back to OpenJDK you can run the following commands one by one to switch between the OpenJDK and Sun Java:
[anoop@home ~]$ sudo /usr/sbin/alternatives --config java
[anoop@home ~]$ sudo /usr/sbin/alternatives --config libjavaplugin.so
(or for 64-bit)
[anoop@home ~]$ sudo /usr/sbin/alternatives --config libjavaplugin.so.x86_64
To update: If you wish update the JRE package, simply download the newest RPM package and install it as above. You will NOT need to reset alternatives, as those settings should remain intact.
Install Adobe Acrobat
To view PDF files, Fedora includes evince, however this application is very basic and may not work with every feature of some PDF files.
For yum users:
Install the Adobe YUM repository, and install through yum:
[anoop@home Download]$ sudo rpm -ivh http://linuxdownload.adobe.com/adobe-release/adobe-release-i386-1.0-1.noarch.rpm
[anoop@home Download]$ sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-adobe-linux
[anoop@home Download]$ sudo yum install AdobeReader_enu
NOTE: The above uses the English version: enu. To see which languages are supported by Adobe's YUM repository, run the following command:
[anoop@home Download]$ yum list AdobeReader\*
Other languages are installed similar to english for example: AdobeReader_fra, if you are unsure which package is correct, run:
yum info AdobeReader_fra for more information. Otherwise install manually as described below. (Note: 64-bit users are recommended to use yum to resolve all the 32-bit i386 dependancies.)
For manual installation: For users without yum:
Download Acrobat from: http://www.adobe.com/products/acrobat/readstep2_allversions.html
Select:
Operating system: Linux
Version: Linux - x86 (.rpm)
Your language.
The version of Adobe Acrobat Reader currently is 8.1.3 and the download size is between 40-60MB depending on your language. Not all languages are supported under Linux.
[anoop@home Download]$ su -c 'rpm -ivh AdobeReader_enu-8.1.3-1.i486.rpm'
Note: Do NOT use sudo when installing the RPM. Either install it when logged in as root or use the su -c command.
Setup Samba - Filesharing with Windows
If you have other Windows computers on your LAN and want to share files from Linux with them, you must setup Samba.
To setup Samba you must (1) install samba, (2) add you 'shares', (3) add users, (4) start Samba service and (5) manage security options (Firewall and SELinux).
1. Install Samba
It is best to have Samba installed in the installation process. If not < style="color: rgb(51, 255, 51);">[anoop@home ~]$ sudo yum install samba samba-client
2. Add Shares
You must edit /etc/samba/smb.conf as root: (use nano instead of gedit if you do not have a GUI)
[anoop@home ~]$ sudo gedit /etc/samba/smb.conf
Set your Windows Workgroup name in [global] section.
Added shares at the end of the file. Example:
[c_drive]
path = /media/c_drive
public = yes
writable = no
[netshare]
path = /data/
public = yes
writable = yes
If 'writable' the location must be writable in Linux first. Additionally permissions must match (for example: drw-rw-rw-).
If home data (all personal files under /home/username) is to be accessible, then set 'browseable = yes' under [homes] (~line 250). This configuration file is very descriptive, read through it to get more ideas or information.
3. Add Users
To access shares, you must be a valid user. Add valid users AND passwords using the smbpasswd command.
This login name WILL be the login name and password you use from Windows to access your Linux computer. The password does NOT need to match your Linux password.
[anoop@home ~]$ sudo smbpasswd -a username
New SMB password:
Retype new SMB password:
account_policy_get: (warnings ignored)
Added user username.
(Note: 'username' MUST be a valid account on the Fedora machine)
4. Start Samba Service
Run samba and check for any errors:
[anoop@home ~]$ sudo /etc/init.d/smb start
Starting SMB services: [ OK ]
Use chkconfig or serviceconf to enable samba (smb) in both runlevels 3 and 5. This will make sure to run Samba each time Fedora boots.
[anoop@home ~]$ /sbin/chkconfig --list smb
smb 0:off 1:off 2:off 3:off 4:off 5:off 6:off
[anoop@home ~]$ sudo /sbin/chkconfig --level 35 smb on
[anoop@home ~]$ /sbin/chkconfig --list smb
smb 0:off 1:off 2:off 3:on 4:off 5:on 6:off
Restart Samba for every change to users/passwords or 'smb.conf'
[anoop@home ~]$ sudo /etc/init.d/smb restart
Shutting down SMB services: [ OK ]
Starting SMB services: [ OK ]
5. Managing Security for Samba
Firewall
The Firewall will by default block Samba, to allow access run:
[anoop@home ~]$ system-config-firewall
To allow Samba access to work through the firewall you must set 'Samba' as a 'Trusted Service' and hit 'Apply'. Alternatively if you are only using the shell and do not have access to a graphical X-server, you can run:
[anoop@home ~]$ sudo system-config-firewall-tui
To allow Samba access to work through the firewall, use to go to Customize. In the Trusted Services: scroll down to Samba, hit and use again to go to Close, then finally to OK.
SELinux
SELinux has significant control over restricting different parts of Samba. Run system-config-selinux. Please read lines #23 - #51 in /etc/samba/smb.conf for a better explanation. Alternatively, you can run:
[anoop@home ~]$ system-config-selinux
Go to Boolean and type 'samba' in the Filter (without quotes).
The following is NOT complete and is NOT recommended but is a quick enable to allow Samba to work permissively through SELinux.
[anoop@home ~]# sudo /usr/sbin/setsebool -P samba_export_all_rw on
Alternatively, you can ignore SELinux at this point and try to access your shares in Windows and SELinux TroubleShooter should give an automatic pop-up in GNOME explaining what is wrong. If you follow those recommendations you most likely will be more secure.
For any changes made above to the SELinux settings or smb.conf, it is recommended to restart Samba.
Fedora 10 is provided as either CD-ROM's or DVD-ROM's for installation. You can either download the multiple CD sets or single DVD for installation. The DVD-ROM disk is preferred and recommended method of installation. Booting the DVD or booting from CD#1 will start the installer which will allow Fedora to be installed on your computer or for you to upgrade an existing Fedora on your machine. The following steps were done with the single DVD installation.
There are also "LiveCD's" which can be booted and will run a basic Fedora 10 in memory while also providing a simpler method of installation (not as complete at the DVD or multi-CD method). The default LiveCD ships with Gnome (ex: F10-i686-Live.iso). There is a specific LiveCD that ships with KDE. Both provide an installer however they come with significantly less software than the DVD. Also they require more memory in order to be usable. The LiveCD may be useful for demonstration.
Note: To upgrade an existing Fedora installation you cannot use a Live disk.
Physical Installation
It is highly recommended you read the Fedora Release Notes and official Installation Guide before installing Fedora.
An additional recommendation is to read Common Problems before installing.
Obtain the Fedora 10 DVD image or multi-CD set images from a Fedora mirror (or use the torrent) and burn to DVD. (For more information on how to download Fedora CD's or DVD).
Boot from the DVD. If you choose to use a LiveCD please note that the following steps will differ.
NOTE: The Fedora 10 Installer (anaconda) is very minimal and most configuration steps will need to be done post-installation.
I did a Custom Install of Fedora 10.
* Network Setup
Fedora 10 uses NetworkManager for automatically configuring the network for installation. Users will only be prompted to set their 'hostname' (e.g. 'mycomputer').
* Root password
This is your "Administrator" or "Superuser" password that lets you access everything on your system. Pick a good password and remember it.
* Partitioning
o If you have an empty hard drive or wish to delete the entire contents of your drive, then let the installer automatically partition or remove everything and partition.
o If you wish to dual-boot or save some contents on your drive, then select custom partitioning. I recommend at least 3 partitions: an 8-12GB / main partition, a 10+GB /home partition and a 1-2GB
* Boot Loader
o If you have a blank harddrive or wish Fedora to be your Primary Operating System, then leave the default options here. This also works for dual booting with other systems (ex: Windows).
o If you wish to preserve Windows as your primary operating system, then install Grub on the / partition, NOT the MBR. To do this, select Change device on the Install boot loader screen and install to First sector of boot partition. I use Bootpart from Windows 2000/XP to load Linux. An alternative to Bootpart is the NT OS Loader + Linux mini-HOWTO (also Grub Win2K Howto). I recommend this so you do not corrupt your Windows installation in a Dual-Boot environment. [NOTE] There is an example configuration available. This does take more work, and the default option on the MBR will also work. This will also work for users who are triple booting Vista/XP/Fedora (as I do).
* General Package Selection
The primary options for installation are the following. You can select these and skip individual package selection (next step) if you plan to install most of your software from online (via YUM). It is recommended you at least pick certain applications.
o Office and Productivity - [Highly Recommended]
o Software Development - [Highly Recommended / Required]
o Web Server - [Optional (useful for web developers)]
Add Additional Software Repositories - [NOT Recommended at Install time]. You do have the option of adding helpful repositories during install. This will give access to MANY more applications than included on the CD's or DVD. However this requires a high-speed internet access that is detected by the Fedora Installer. This will also significantly increase the installation time.
If you select Customize now you will be taken to the Individual Package Selection. The Fedora installer will usually have most of the necessary defaults, properly selected. You may skip this step.
* Individual Package Selection - apx 4.5-5.5GB. - It is significantly helpful to grab a some specific important packages (to reduce unnecessary downloading later). You are free to select whatever you want. The following in my experience are common useful suggestions:
o Desktop Environments
+ [Highly Recommended] - Select both GNOME Desktop Environment and KDE (K Desktop Environment)
o Applications - The default selection of applications is sufficient. Note the following:
+ [Recommended] - Graphical Internet - Add thunderbird as an email client.
+ [Recommended] - Sound and Video - Add k3b for CD/DVD creation.
o Development
+ [Recommended] - Select GNOME Software Development, KDE Software Development and X Software Development.
+ [Recommended/Optional] - Select Fedora Packager - Useful for some software building/administration.
o Servers
+ [Recommended] - Add Server Configuration Tools.
+ [Required] - Add Windows File Server (required to share files with Windows computers).
o Base System
+ [Recommended] - Add System Tools.
+ [Optional] - Deselecting some items in Dial-up Networking Support, Fonts (lots of foreign fonts) and Hardware Support (lots of various WiFi), and Input Methods may reduce unwanted/unusable software depending on your location and hardware.
Install the selected packages and reboot.
For users who opted to install grub on the first sector of the / partition instead of the MBR, you will be required to setup NTLDR to boot Linux.
For the first boot:
* License - Accept any licenses for Fedora
* Create User - Create at least 1 user account for yourself. Always use that account. DO NOT use root as your personal account. The root account will NOT be permitted to login into the graphical desktop.
* Date and Time - Network Time Protocol - Enable this ONLY if you have an active working internet connection that is on (ex: broadband, T1, DSL). You do not need to check the time server every time the service starts.
* Hardware Profile - Fedora uses smolt to provide basic non-intrusive information on your specific installation. While this may be helpful to Fedora developers, some may consider it a privacy issue. Please understand what information is being sent before you allow it to do so. I personally do not sent profile information.
Setup sudo
Fedora, like all other Linux distributions, has a root user and has individual users. The root is the "superuser", somewhat similar to "Administrator" in Windows.
Use the personal account you created at First Boot for daily use root only for administration/configuration. To run as 'root' use su or sudo commands. However sudo requires setup. As root run:
echo 'loginname ALL=(ALL) ALL' >> /etc/sudoers
Where 'loginname' is your user account.
Use 'ALL=(ALL) NOPASSWD:ALL' if you don't want to be prompted a password.
If you are prompted for a password with 'sudo' it is the user password, not root.
Example:
[anoop@home ~]$ su
Password: <--- Enter root password
[root@home anoop]# echo 'mirandam ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers
[root@home anoop]# exit
exit
The following is an example of how sudo lets you execute root commands:
[anoop@home ~]$ du -sh /root
du: `/root': Permission denied <--- Fails!!!
[anoop@home ~]$ sudo du -sh /root
163M /root <--- Works!!!
NOTE: Every command provided on this page will work if you remove sudo from the command. However this requires you must be logged in as 'root'. An alternative to using sudo is to use su to login as root, before executing a command.
Graphical Bootloader - Plymouth
Fedora 10 replaces the previous graphical bootup system (which used the X-server) with a simpler system that uses kernel modesetting. However modesetting drivers are not available for all hardware yet. Please see: Plymouth.
Note: The following is optional. If no kernel modesetting is available a simple text based scroll bar should show up with booting Fedora.
In order to see the graphical boot, you must enable a mode setting for your video. Most users will find vesafb allows most standard VGA resolutions. Some examples are in Linux Kernel Documentation / fb / vesafb.txt and also here. You must have a proper Kernel mode number. For example I selected: 0x318 for 1024x768x16M resolution on a desktop CRT monitor.
As 'root', edit /boot/grub/grub.conf, and add 'vga=0x318' to the end of the kernel line. For example:
title Fedora (2.6.27.5-117.fc10.i686)
root (hd0,9)
kernel /boot/vmlinuz-2.6.27.5-117.fc10.i686 ro root=UUID=bb061789-157b-4cb2-85c8-633026e8df1e rhgb quiet vga=0x318
initrd /boot/initrd-2.6.27.5-117.fc10.i686.img
The next time you reboot, you should see the Plymouth graphical booter.
NOTE: You may use vga=ask instead. Follow the instructions you see on the screen and remember the number you used. Replace the number with the proper value in grub.conf as I did above.
NOTE: The resolution you select only applies to the graphical boot. You may use different resolutions/settings when you are using Fedora. It is acceptable to select a lower resolution for booting.
Setup yum
Fedora uses yum to install and update its software. When connected to the internet it will automatically determine application dependencies.
Fedora Repositories
Fedora typically has 2 repositories enabled by default: fedora (the same packages that come on any combination of the CD's or DVD's) and updates (updated packages, newer than fedora repository).
Third Party Repositories
For applications that are against Fedora policies (MP3, DVD, MPEG, Binary Drivers, etc), a third party repository should be used. The recommended repository for Fedora is: RPMFusion. For the purpose of this guide, (most) all needs are met by the RPMFusion repository, other requirements are stated.
To set up the RPMFusion repositories:
[anoop@home ~]$ sudo rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
[anoop@home ~]$ sudo rpm -ivh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm
[anoop@home ~]$ sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-*
Install Nvidia Driver
In order to provide more complete information on the Nvidia driver, please see: Fedora Nvidia Driver Install Guide ( http://www.mjmwired.net/resources/mjm-fedora-nvidia.html).
Network Management
Fedora 10 uses NetworkManager by default. The primary settings for any network devices will be automatically selected at installation time. Since there is no screen for selecting networking options, most devices will default to using DHCP.
Using NetworkManager has greatly improved networking for many wireless and some less common devices (mobile broadband, GSM, etc.), it may still have problems with some configurations. NetworkManager development and integration into Fedora is still an ongoing effort.
NOTE: The following steps do NOT apply to all users. NetworkManager is highly recommended for Laptop users, especially using wireless with security.
Disabling NetworkManager and Enabling network Service
On machines with a fixed networking device and a fixed IP address (e.g. desktop, server, appliance), it might be more practical to disable NetworkManager and use the older network service. Additionally users requiring virtual device types (bridging, bonding, or VLANs) will also need to use the network service.
Note that the Fedora 10 installer disables the network service by default. To switch to using the network service:
First disable NetworkManager and prevent it from automatically loading:
[anoop@home ~]$ sudo /etc/init.d/NetworkManager stop
Stopping NetworkManager daemon: [ OK ]
[anoop@home ~]$ sudo /sbin/chkconfig --level 35 NetworkManager off
Next, configure your network settings:
[anoop@home ~]$ sudo system-config-network
You should have an eth0 device already showing. To configure the IP settings click on Edit. Do not forget to set DNS on the DNS tab (if you're using fixed IP's). Make sure the eth0 is selected as Active. Then File > Save and quit.
Next, enable the service and make sure it loads at next boot:
[anoop@home ~]$ sudo /etc/init.d/network start
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
[anoop@home ~]$ sudo /sbin/chkconfig --level 35 network on
While it may be possible to re-activate your network without a reboot, it may be recommended to reboot.
Startup Applications Requiring Network
Some applications require the network to be initialized during boot. If you are using NetworkManager and having these problems, edit /etc/sysconfig/network as 'root' and add the following line:
NETWORKWAIT=1. Or run:
[anoop@home ~]$ sudo su -c 'echo NETWORKWAIT=1 >> /etc/sysconfig/network'
Install RealPlayer
Note: Currently these instructions only apply to Fedora 32-bit.
Download RealPlayer 11.0 GOLD from: http://www.real.com/linux/.
Select: "Advanced Installation Options RedHat Package"
Install RealPlayer:
[anoop@home Download]$ sudo rpm -ivh RealPlayer11GOLD.rpm
RealPlayer/HelixPlayer Forums: https://helixcommunity.org/projects/player/forums
NOTE: Totem issues: If the Totem-Mozilla-Plugin tries to load RealPlayer content instead of RealPlayer, try removing the plugin:
[anoop@home ~]$ sudo yum remove totem-mozplugin
Install MP3 Players
Fedora ships without any form of MP3 playback. In order to add MP3 playback you must install from a 3rd party. The following requires the use of the RPMFusion repositories.
XMMS: simple, older GUI, minimalistic features (but still popular)
* Installation through yum:
[anoop@home ~]$ sudo yum install xmms xmms-mp3 xmms-faad2 xmms-pulse xmms-skins
Audacious: (A fork of Beep Media Player - BMP). XMMS rebuilt to be a little bit more modern. Still basic but much better than XMMS.
* Installation through yum:
[anoop@home ~]$ sudo yum install audacious audacious-plugins-freeworld*
NOTE: There is a '*' at the end.
Rhythmbox/Gstreamer - A simple audio application similar to iTunes layout.
* Most of Rhythmbox and the Gstreamer system should be installed when installing Gnome (mentioned above). The missing components are just the MP3 (and other media) plugins.
* Installation through yum:
[anoop@home ~]$ sudo yum install rhythmbox gstreamer-plugins-ugly gstreamer-plugins-bad gstreamer-ffmpeg
Amarok - A modern feature rich media player application.
* It is helpful to have KDE installed first as this will reduce the download.
* Installation through yum:
[anoop@home ~]$ sudo yum install amarok xine-lib-extras-freeworld
K3B CD-Burner MP3 Audio Decoding:
* If you wish to make audio CD's in K3b from MP3's, install the following:
* Using yum:
[anoop@home ~]$ sudo yum install k3b-extras-freeworld
Note: PulseAudio - I was able to run most all these applications with either their default settings or using PulseAudio plugins enabled.
Install Media Players
Fedora ships with a limited set of media player for both audio and video. For audio please read the MP3 player notes. For video and other multimedia (DVD, etc.) we will also be making use of a 3rd party repository: RPMFusion. Make sure to have the RPMFusion repositories configured before executing the following. Note that many "dependancies" in libraries, plugins and codecs are shared between these applications and also the MP3 player applications.
The most popular media players (in order) are: MPlayer, Xine and VLC. Each has its own strengths. Install whichever you prefer although the first 2 are recommended.
MPlayer - MPlayer comes in a command line only interface (mplayer) or skinable GUI and it also has a powerful encoding tool MEncoder (also great for ripping or compressing audio/video). Additionally there is a highly functional web plugin allowing for many popular formats in Firefox/Mozilla (WMV, QuickTime, etc.).
* Installation through yum with RPMFusion enabled:
[anoop@home ~]$ sudo yum install mplayer mplayer-gui gecko-mediaplayer mencoder
* Note that mencoder is optional but provides many encoding functions.
* Binary Codecs: Please install the Binary Codecs for further support of formats that MPlayer does not directly support.
* MPlayer should work automatically defaulted to PulseAudio.
Xine - Xine is similar to MPlayer in many ways however lacking the command line application and encoder. However has fully supported DVD playback with proper navigation.
* Installation through yum with RPMFusion enabled:
[anoop@home ~]$ sudo yum install xine xine-lib-extras xine-lib-extras-freeworld
* Binary Codecs: Please install the Binary Codecs for further support of formats that Xine does not directly support.
* DVD Playback: To properly play DVDs please see DVD Playback.
* Xine Crashing: If you are experiencing Xine crashing immediately after loading please read this: Xine F10 Crash.
Binary Codecs - The MPlayer projects maintains a package full of binary codecs for which no directly open source option exists, some of these files include Windows DLL's. These are shared by both Xine and MPlayer. NOTE: There is significant variation depending on your architecture (i386, x86_64, ppc). The 32bit i386 works the best.
* Navigate to: http://www.mplayerhq.hu/MPlayer/releases/codecs/
* Select the package (.tar.bz2) best matching your version of Fedora/Architecture. Generally 32-bit users will use: all-20071007.tar.bz2.
* Install the codecs (32-bit for example):
[anoop@home Download]$ sudo mkdir -p /usr/lib/codecs
[anoop@home Download]$ sudo tar -jxvf all-20071007.tar.bz2 --strip-components 1 -C /usr/lib/codecs/
VLC - VLC is a simpler media player with an easy to use interface. It also supports DVD playback. While most needs should be met with Xine and MPlayer some prefer VLC.
* Installation through yum with RPMFusion enabled:
[anoop@home ~]$ sudo yum install vlc
* DVD Playback: To properly play DVDs please see DVD Playback.
DVD Playback - Due to non-technical reasons, the libdvdcss package currently exists in the Livna repository. Either use the Livna repository for this single package, or manually download and install it:
* Setup the Livna Repository:
[anoop@home ~]$ sudo rpm -ivh http://rpm.livna.org/livna-release.rpm
[anoop@home ~]$ sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-livna
* Installation through yum with Livna enabled:
[anoop@home ~]$ sudo yum install libdvdcss
SELinux Issues - The package ffmpeg-libs gave at least 2 SELinux AVC denials, the fix from the Troubleshooter was:
[anoop@home ~]$ sudo chcon -t textrel_shlib_t '/usr/lib/sse2/libpostproc.so.51.2.0'
[anoop@home ~]$ sudo chcon -t textrel_shlib_t '/usr/lib/sse2/libswscale.so.0.6.1'
Install Microsoft Truetype Fonts
The official source for the package is http://corefonts.sourceforge.net/.
There is a request for RPMFusion to package this. From that I am providing an updated SPEC file.
You have to build the RPM using the chosen SPEC file. For convenience I have created the RPM (please do not link directly to this file):
msttcore-fonts-2.0-3.noarch.rpm
[anoop@home Download]$ sudo rpm -ivh msttcore-fonts-2.0-3.noarch.rpm
Note: If have upgraded from Fedora 8 or some a previous version of Fedora. Please see Fedora 8 - Truetype Fonts on removing the older packages.
Note: Fedora encourages the use of the Liberation Fonts. These should be installed by default (and included on the DVD), however if not, please run:
[anoop@home ~]$ sudo yum install liberation-fonts
Disable Unneeded Services/Daemons
Information regarding services and their functions can be found on: Services in Fedora 10 (http://www.mjmwired.net/resources/mjm-services-f10.html).
For information on how to manage services in Fedora please read: Managing Services in Fedora (http://www.mjmwired.net/resources/mjm-fedora-manage-services.html).
Adobe Flash Plugin
The Adobe Flash plugin is available from Adobe's website. Users can install the RPM directly or use Adobe's YUM repository (recommended). Please note the plugin will not work directly on 64-bit browsers without some re-configuration.
For yum users (RECOMMENDED):
Install the Adobe YUM repository, and install through yum:
[anoop@home Download]$ sudo rpm -ivh http://linuxdownload.adobe.com/adobe-release/adobe-release-i386-1.0-1.noarch.rpm
[anoop@home Download]$ sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-adobe-linux
[anoop@home Download]$ sudo yum install flash-plugin
For manual installation: For users without yum:
Go to Install a different version of Adobe Flash Player and select:
Select an operating system: Linux
Select an installer type: .rpm for Linux.
Download the .rpm file (.rpm for Linux (x86)) and save it to disk.
Install:
[anoop@home Download]$ sudo rpm -ivh flash-plugin-10.0.12.36-release.i386.rpm
Installation on Fedora 64-bit
The following steps are required for Fedora 64-bit users.
First install the Adobe YUM repository, as stated above:
[anoop@home Download]$ sudo yum install nspluginwrapper.{i386,x86_64} alsa-plugins-pulseaudio.i386
[anoop@home Download]$ sudo yum install flash-plugin
Java Runtime Environment
The standard installation of Fedora 10 should install OpenJDK (based off of Sun Java). However if not, it can be installed using YUM:
[anoop@home ~]$ sudo yum install java-1.6.0-openjdk java-1.6.0-openjdk-plugin
With OpenJDK installed, Java application and Web applets should automatically work. Unfortunately some applets may not run properly and the OpenJDK might have some limitations. Majority of user should find OpenJDK perfect for everyday use.
Using Sun Java Instead
If you require Sun Java or if OpenJDK does not work properly, you can download Sun Java and use it in Fedora.
Download the Java package from:
http://java.sun.com/javase/downloads/index.jsp
Select: Java SE Runtime Environment (JRE) 6 Update 12 (the JDK is for developers)
On the next page, for Platform select "Linux" for 32-bit users, and "Linux x64" for 64-bit users.
For Language select "Multi-language". Also accept the license agreement, and hit "Continue".
On the next page, select the RPM option:
Java SE Runtime Environment 6u12
jre-6u12-linux-i586-rpm.bin 18.72 MB (32-bit users)
jre-6u12-linux-x64-rpm.bin 18.20 MB (64-bit users)
To install (32-bit example):
[anoop@home Download]$ sudo sh jre-6u12-linux-i586-rpm.bin
You will need to hit 'space' till it reaches the end, then type 'yes'. You should see the RPM installing. If you do not, manually install it via sudo rpm -ivh.
When running the java command, Fedora will default to using OpenJDK. In order to use Sun Java, use the alternatives command.
To setup the Java runtime, perform the following (applies to both 32-bit and 64-bit users):
[anoop@home Download]$ sudo /usr/sbin/alternatives --install /usr/bin/java java /usr/java/default/bin/java 20000
The Mozilla/Firefox browser plugin for 32-bit users:
[anoop@home Download]$ sudo /usr/sbin/alternatives --install /usr/lib/mozilla/plugins/libjavaplugin.so \
libjavaplugin.so /usr/java/default/plugin/i386/ns7/libjavaplugin_oji.so 20000
For 64-bit users:
[anoop@home Download]$ sudo /usr/sbin/alternatives --install /usr/lib64/mozilla/plugins/libjavaplugin.so \
libjavaplugin.so.x86_64 /usr/java/default/lib/amd64/libnpjp2.so 20000
Note: If you wish to switch back to OpenJDK you can run the following commands one by one to switch between the OpenJDK and Sun Java:
[anoop@home ~]$ sudo /usr/sbin/alternatives --config java
[anoop@home ~]$ sudo /usr/sbin/alternatives --config libjavaplugin.so
(or for 64-bit)
[anoop@home ~]$ sudo /usr/sbin/alternatives --config libjavaplugin.so.x86_64
To update: If you wish update the JRE package, simply download the newest RPM package and install it as above. You will NOT need to reset alternatives, as those settings should remain intact.
Install Adobe Acrobat
To view PDF files, Fedora includes evince, however this application is very basic and may not work with every feature of some PDF files.
For yum users:
Install the Adobe YUM repository, and install through yum:
[anoop@home Download]$ sudo rpm -ivh http://linuxdownload.adobe.com/adobe-release/adobe-release-i386-1.0-1.noarch.rpm
[anoop@home Download]$ sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-adobe-linux
[anoop@home Download]$ sudo yum install AdobeReader_enu
NOTE: The above uses the English version: enu. To see which languages are supported by Adobe's YUM repository, run the following command:
[anoop@home Download]$ yum list AdobeReader\*
Other languages are installed similar to english for example: AdobeReader_fra, if you are unsure which package is correct, run:
yum info AdobeReader_fra for more information. Otherwise install manually as described below. (Note: 64-bit users are recommended to use yum to resolve all the 32-bit i386 dependancies.)
For manual installation: For users without yum:
Download Acrobat from: http://www.adobe.com/products/acrobat/readstep2_allversions.html
Select:
Operating system: Linux
Version: Linux - x86 (.rpm)
Your language.
The version of Adobe Acrobat Reader currently is 8.1.3 and the download size is between 40-60MB depending on your language. Not all languages are supported under Linux.
[anoop@home Download]$ su -c 'rpm -ivh AdobeReader_enu-8.1.3-1.i486.rpm'
Note: Do NOT use sudo when installing the RPM. Either install it when logged in as root or use the su -c command.
Setup Samba - Filesharing with Windows
If you have other Windows computers on your LAN and want to share files from Linux with them, you must setup Samba.
To setup Samba you must (1) install samba, (2) add you 'shares', (3) add users, (4) start Samba service and (5) manage security options (Firewall and SELinux).
1. Install Samba
It is best to have Samba installed in the installation process. If not < style="color: rgb(51, 255, 51);">[anoop@home ~]$ sudo yum install samba samba-client
2. Add Shares
You must edit /etc/samba/smb.conf as root: (use nano instead of gedit if you do not have a GUI)
[anoop@home ~]$ sudo gedit /etc/samba/smb.conf
Set your Windows Workgroup name in [global] section.
Added shares at the end of the file. Example:
[c_drive]
path = /media/c_drive
public = yes
writable = no
[netshare]
path = /data/
public = yes
writable = yes
If 'writable' the location must be writable in Linux first. Additionally permissions must match (for example: drw-rw-rw-).
If home data (all personal files under /home/username) is to be accessible, then set 'browseable = yes' under [homes] (~line 250). This configuration file is very descriptive, read through it to get more ideas or information.
3. Add Users
To access shares, you must be a valid user. Add valid users AND passwords using the smbpasswd command.
This login name WILL be the login name and password you use from Windows to access your Linux computer. The password does NOT need to match your Linux password.
[anoop@home ~]$ sudo smbpasswd -a username
New SMB password:
Retype new SMB password:
account_policy_get: (warnings ignored)
Added user username.
(Note: 'username' MUST be a valid account on the Fedora machine)
4. Start Samba Service
Run samba and check for any errors:
[anoop@home ~]$ sudo /etc/init.d/smb start
Starting SMB services: [ OK ]
Use chkconfig or serviceconf to enable samba (smb) in both runlevels 3 and 5. This will make sure to run Samba each time Fedora boots.
[anoop@home ~]$ /sbin/chkconfig --list smb
smb 0:off 1:off 2:off 3:off 4:off 5:off 6:off
[anoop@home ~]$ sudo /sbin/chkconfig --level 35 smb on
[anoop@home ~]$ /sbin/chkconfig --list smb
smb 0:off 1:off 2:off 3:on 4:off 5:on 6:off
Restart Samba for every change to users/passwords or 'smb.conf'
[anoop@home ~]$ sudo /etc/init.d/smb restart
Shutting down SMB services: [ OK ]
Starting SMB services: [ OK ]
5. Managing Security for Samba
Firewall
The Firewall will by default block Samba, to allow access run:
[anoop@home ~]$ system-config-firewall
To allow Samba access to work through the firewall you must set 'Samba' as a 'Trusted Service' and hit 'Apply'. Alternatively if you are only using the shell and do not have access to a graphical X-server, you can run:
[anoop@home ~]$ sudo system-config-firewall-tui
To allow Samba access to work through the firewall, use
SELinux
SELinux has significant control over restricting different parts of Samba. Run system-config-selinux. Please read lines #23 - #51 in /etc/samba/smb.conf for a better explanation. Alternatively, you can run:
[anoop@home ~]$ system-config-selinux
Go to Boolean and type 'samba' in the Filter (without quotes).
The following is NOT complete and is NOT recommended but is a quick enable to allow Samba to work permissively through SELinux.
[anoop@home ~]# sudo /usr/sbin/setsebool -P samba_export_all_rw on
Alternatively, you can ignore SELinux at this point and try to access your shares in Windows and SELinux TroubleShooter should give an automatic pop-up in GNOME explaining what is wrong. If you follow those recommendations you most likely will be more secure.
For any changes made above to the SELinux settings or smb.conf, it is recommended to restart Samba.
configure Linux machine to Router.
Here is a tutorial to configure your linux machine to Router.
System Config:
Operating System: CentOS 4..5
Kernel : 2.6.22-4
Specs: 1 Gb RAM, Intel D845 Motherboard with Intel Processor 2.4
We will be configuring our linux machine to act as a Failover for Internet along with Load balance and upon then you can configure any firewall (i would suggest Squid). Now lets get into it, we will be achieve this through these steps.
1.Configure the kernel with latest stable one along with some patches
2.Configure the Internet to act as a Failover Server
3.Configure the Internet to control Load Balance.
1. Compiling the kernel
Download your desired kernel to /usr/src from www.kernel.org and select the kernel you want to install, e.g. linux-2.6.22.4.tar.bz2 (you can find all 2.6 kernels here: http://www.kernel.org/pub/linux/kernel/v2.6/). Then you can download it to /usr/src like this:
Code:
cd /usr/src
wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.4.tar.bz2
Then we unpack the kernel sources and create a symlink linux to the kernel sources directory:
Code:
tar xjf linux-2.6.18.3.tar.bz2
ln -s linux-2.6.18.3 linux
cd /usr/src/linux
Modify /etc/modprobe.conf
Now you must comment out the mptscsi module in /etc/modprobe.conf because you will get a warning like this in future:
WARNING: No module mptscsi found for kernel 2.6.22.4, continuing anyway
when we build our new kernel.
vi /etc/modprobe.conf
Code:
alias eth0 pcnet32
alias scsi_hostadapter mptbase
# alias scsi_hostadapter1 mptscsi
alias scsi_hostadapter2 mptfc
alias scsi_hostadapter3 mptspi
alias scsi_hostadapter4 mptsas
alias scsi_hostadapter5 mptscsih
Apply Patches To The Kernel Sources
Download the patches for routes from this site http://www.ssi.bg/%7Eja/ for ur respective kernel and give the file read, write, execute permission for root. apply the patch by issuing the command in Konsole. Download these files in /usr/src/
Code:
bzip2 -dc /usr/src/routes-2.6.22-15.diff | patch -p1 --dry-run
bzip2 -dc /usr/src/routes-2.6.22-15.diff | patch -p1
if the file path is missing then give the file path manually. the first command will only test the patch and the second command will patch the kernel. So if your not sure how to do it then donot issue the second command but I strongly suggest to patch the kernel with these route patch.
Configure The Kernel
Code:
make clean && make mrproper
Then we run
Code:
make xconfig
this will bring up a X window, alternately u can use menuconfig instead of xconfig this will bring a command line Gui window.
the Window will have kernel configuration menu. Now go into the Network tab (on the left if your using xconfig or in the window if your using menuconfig) and select all the options to be on a safe side do not select those option for which “EXPERIMENTAL”
is mentioned in brackets without the quotes. Take special care for all netfilter options as we require it, these need to be enabled except those for which “EXPERIMENTAL” is mentioned.
Build And Install The Kernel
To build and install the kernel, execute these three commands:
Code:
make all
make modules_install
make install
Now be patient, the kernel compilation can take some hours, depending on your kernel configuration and your processor speed. The last command will also automatically create a ramdisk for you as well as configure /boot/grub/menu.lst.
Now edit /boot/grub/menu.lst. You should find a stanza for your new kernel at the top of the list, but to make sure that the new kernel gets booted instead of your old one, you must set the value of default to 0.
vi /boot/grub/menu.lst
My menu.lst looks like this:
Code:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.22.4)
root (hd0,0)
kernel /vmlinuz-2.6.22.4 ro root=/dev/VolGroup00/LogVol00 enforcing=0
initrd /initrd-2.6.22.4 .img
title CentOS (2.6.9-42.0.3.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.3.EL ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.9-42.0.3.EL.img
title CentOS-4 i386 (2.6.9-42.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.EL ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.9-42.EL.img
do not forget to add that “enforcing=o” without quotes otherwise it will throw “kernel panic” error at the time of booting and your new installed kernel will not boot.
Now reboot the system:
Code:
shutdown -r now
If everything goes well, it should come up with the new kernel. You can check if it's really using your new kernel by running
Code:
uname -r
This should display something like
Code:
2.6.18.3
If the system doesn't start, restart it, and when you see thecountdown of grub trying to boot press
Code:
e
and goto ur old kernel n press
Code:
b
or just press enter and try to compile again.
2.Failover
Now lets configure the system for failover Internet, in the network configuration add the network ip's and gatways along with dns. My setup was like this
Internal Lan Eth0=192.168.1.0 - 192.168.1.255 with netmask 255.255.255.0
ISP1 Eth1=202.61.19.29 with netmask 255.255.255.0
ISP2 Eth2= 202.63.89.45 with netmask 255.255.255.248
You can do these configurations using Xwindow from Start>System Settings>Network. This will open a network configuration window, which will show all the network card on your system. Double click on the LAN card icon you want to configure, select the ‘Statically set IP address’ radio button and assign the IP address with subnet mask.
After this, enable IP forwarding on the Linux box. For this, open the file /etc/sysclt.conf from a terminal window. Here, you’ll find an entry ‘net.ipv4.ip_forward = 0’. Set its value to 1 and save the file. Now execute a command in Konsole
Code:
sysctl –p
Next, you need to set the IP table so that the internal network can route packets to the Internet. For this, issue the following commands from a terminal window.
Code:
# iptables –t nat –A POSTROUTING –o eth1 –j MASQUERADE
(Routing packets to Internet connected to first ISP)
# iptables –t nat –A POSTROUTING –o eth2 –j MASQUERADE
(Routing packets to Internet connected to second ISP)
# iptables –A FORWARD –s 192.168.1.0/24 –j ACCEPT
(Forwarding from Internal lan)
# iptables –A FORWARD –d 192.168.1.0/24 –j ACCEPT
# iptables –A FORWARD –s ! 192.168.1.0/24 –j DROP
# iptables-save > /etc/sysconfig/iptables
(saving the IP tables)
# /etc/init.d/network restart
(restarting the network)
# /etc/init.d/iptables restart
(restarting the IP tables)
If you would like to have Failover + Load balance then skip this otherwise goahead.
Now you need to configure failover routing, wherein if the first route dies, then it will look for an alternative route path. For this, you’ll need to add default gateway routes (provided by your ISP) for both network cards. This is done as follows.
Code:
# route add default gw 202.61.19.1 dev eth1
# route add default gw 202.63.89.1 dev eth2
(202.61.19.1 is a gateway IP given by first ISP and 202.63.89.1 is a gateway IP given by second ISP)
Add these commands in /etc/rc.d/rc.local file, otherwise the routes will vanish every time you reboot the system.
Finally, open /proc/sys/net/ipv4/ route/gc_timeout file from a terminal window and set the value from 300 to 10 and save this file. The gc_timeout file contains some timeout value, after which the kernel declares a route to be dead and automatically switches to other route. Your system will now automatically switch to the second route every time the primary route fails.
Your done with Failover now the next section deals with load balance, if you don't want load balance then stop right here (so that you don't confuse others and yourself).
3. Load balance
Now in order to configure load balance issue this command in Konsole
Code:
#ip route del default
#ip route add default equalize nexthop via 202.61.19.1 dev eth1 nexthop via 202.63.89.1 dev eth2
Add these commands in /etc/rc.d/rc.local file, otherwise the route will vanish every time you reboot the system.
Finally, open /proc/sys/net/ipv4/ route/gc_timeout file from a terminal window and set the value from 300 to 10 and save this file. The gc_timeout file contains some timeout value, after which the kernel declares a route to be dead and automatically switches to other route. Your system will now automatically switch to the second route every time the primary route fails.
To load balance outbound network connections from the internal network, the CONFIG_IP_ROUTE_MULTIPATH kernel option is used, which allows you to have multiple default gateways. It is set up by removing the default gateway from the /etc/sysconfig/network file and setting up the default gateway using advanced routing features with the command we issued.
Congrats now your Linux machine is configured as a Router.
System Config:
Operating System: CentOS 4..5
Kernel : 2.6.22-4
Specs: 1 Gb RAM, Intel D845 Motherboard with Intel Processor 2.4
We will be configuring our linux machine to act as a Failover for Internet along with Load balance and upon then you can configure any firewall (i would suggest Squid). Now lets get into it, we will be achieve this through these steps.
1.Configure the kernel with latest stable one along with some patches
2.Configure the Internet to act as a Failover Server
3.Configure the Internet to control Load Balance.
1. Compiling the kernel
Download your desired kernel to /usr/src from www.kernel.org and select the kernel you want to install, e.g. linux-2.6.22.4.tar.bz2 (you can find all 2.6 kernels here: http://www.kernel.org/pub/linux/kernel/v2.6/). Then you can download it to /usr/src like this:
Code:
cd /usr/src
wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.4.tar.bz2
Then we unpack the kernel sources and create a symlink linux to the kernel sources directory:
Code:
tar xjf linux-2.6.18.3.tar.bz2
ln -s linux-2.6.18.3 linux
cd /usr/src/linux
Modify /etc/modprobe.conf
Now you must comment out the mptscsi module in /etc/modprobe.conf because you will get a warning like this in future:
WARNING: No module mptscsi found for kernel 2.6.22.4, continuing anyway
when we build our new kernel.
vi /etc/modprobe.conf
Code:
alias eth0 pcnet32
alias scsi_hostadapter mptbase
# alias scsi_hostadapter1 mptscsi
alias scsi_hostadapter2 mptfc
alias scsi_hostadapter3 mptspi
alias scsi_hostadapter4 mptsas
alias scsi_hostadapter5 mptscsih
Apply Patches To The Kernel Sources
Download the patches for routes from this site http://www.ssi.bg/%7Eja/ for ur respective kernel and give the file read, write, execute permission for root. apply the patch by issuing the command in Konsole. Download these files in /usr/src/
Code:
bzip2 -dc /usr/src/routes-2.6.22-15.diff | patch -p1 --dry-run
bzip2 -dc /usr/src/routes-2.6.22-15.diff | patch -p1
if the file path is missing then give the file path manually. the first command will only test the patch and the second command will patch the kernel. So if your not sure how to do it then donot issue the second command but I strongly suggest to patch the kernel with these route patch.
Configure The Kernel
Code:
make clean && make mrproper
Then we run
Code:
make xconfig
this will bring up a X window, alternately u can use menuconfig instead of xconfig this will bring a command line Gui window.
the Window will have kernel configuration menu. Now go into the Network tab (on the left if your using xconfig or in the window if your using menuconfig) and select all the options to be on a safe side do not select those option for which “EXPERIMENTAL”
is mentioned in brackets without the quotes. Take special care for all netfilter options as we require it, these need to be enabled except those for which “EXPERIMENTAL” is mentioned.
Build And Install The Kernel
To build and install the kernel, execute these three commands:
Code:
make all
make modules_install
make install
Now be patient, the kernel compilation can take some hours, depending on your kernel configuration and your processor speed. The last command will also automatically create a ramdisk for you as well as configure /boot/grub/menu.lst.
Now edit /boot/grub/menu.lst. You should find a stanza for your new kernel at the top of the list, but to make sure that the new kernel gets booted instead of your old one, you must set the value of default to 0.
vi /boot/grub/menu.lst
My menu.lst looks like this:
Code:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.22.4)
root (hd0,0)
kernel /vmlinuz-2.6.22.4 ro root=/dev/VolGroup00/LogVol00 enforcing=0
initrd /initrd-2.6.22.4 .img
title CentOS (2.6.9-42.0.3.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.3.EL ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.9-42.0.3.EL.img
title CentOS-4 i386 (2.6.9-42.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.EL ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.9-42.EL.img
do not forget to add that “enforcing=o” without quotes otherwise it will throw “kernel panic” error at the time of booting and your new installed kernel will not boot.
Now reboot the system:
Code:
shutdown -r now
If everything goes well, it should come up with the new kernel. You can check if it's really using your new kernel by running
Code:
uname -r
This should display something like
Code:
2.6.18.3
If the system doesn't start, restart it, and when you see thecountdown of grub trying to boot press
Code:
e
and goto ur old kernel n press
Code:
b
or just press enter and try to compile again.
2.Failover
Now lets configure the system for failover Internet, in the network configuration add the network ip's and gatways along with dns. My setup was like this
Internal Lan Eth0=192.168.1.0 - 192.168.1.255 with netmask 255.255.255.0
ISP1 Eth1=202.61.19.29 with netmask 255.255.255.0
ISP2 Eth2= 202.63.89.45 with netmask 255.255.255.248
You can do these configurations using Xwindow from Start>System Settings>Network. This will open a network configuration window, which will show all the network card on your system. Double click on the LAN card icon you want to configure, select the ‘Statically set IP address’ radio button and assign the IP address with subnet mask.
After this, enable IP forwarding on the Linux box. For this, open the file /etc/sysclt.conf from a terminal window. Here, you’ll find an entry ‘net.ipv4.ip_forward = 0’. Set its value to 1 and save the file. Now execute a command in Konsole
Code:
sysctl –p
Next, you need to set the IP table so that the internal network can route packets to the Internet. For this, issue the following commands from a terminal window.
Code:
# iptables –t nat –A POSTROUTING –o eth1 –j MASQUERADE
(Routing packets to Internet connected to first ISP)
# iptables –t nat –A POSTROUTING –o eth2 –j MASQUERADE
(Routing packets to Internet connected to second ISP)
# iptables –A FORWARD –s 192.168.1.0/24 –j ACCEPT
(Forwarding from Internal lan)
# iptables –A FORWARD –d 192.168.1.0/24 –j ACCEPT
# iptables –A FORWARD –s ! 192.168.1.0/24 –j DROP
# iptables-save > /etc/sysconfig/iptables
(saving the IP tables)
# /etc/init.d/network restart
(restarting the network)
# /etc/init.d/iptables restart
(restarting the IP tables)
If you would like to have Failover + Load balance then skip this otherwise goahead.
Now you need to configure failover routing, wherein if the first route dies, then it will look for an alternative route path. For this, you’ll need to add default gateway routes (provided by your ISP) for both network cards. This is done as follows.
Code:
# route add default gw 202.61.19.1 dev eth1
# route add default gw 202.63.89.1 dev eth2
(202.61.19.1 is a gateway IP given by first ISP and 202.63.89.1 is a gateway IP given by second ISP)
Add these commands in /etc/rc.d/rc.local file, otherwise the routes will vanish every time you reboot the system.
Finally, open /proc/sys/net/ipv4/ route/gc_timeout file from a terminal window and set the value from 300 to 10 and save this file. The gc_timeout file contains some timeout value, after which the kernel declares a route to be dead and automatically switches to other route. Your system will now automatically switch to the second route every time the primary route fails.
Your done with Failover now the next section deals with load balance, if you don't want load balance then stop right here (so that you don't confuse others and yourself).
3. Load balance
Now in order to configure load balance issue this command in Konsole
Code:
#ip route del default
#ip route add default equalize nexthop via 202.61.19.1 dev eth1 nexthop via 202.63.89.1 dev eth2
Add these commands in /etc/rc.d/rc.local file, otherwise the route will vanish every time you reboot the system.
Finally, open /proc/sys/net/ipv4/ route/gc_timeout file from a terminal window and set the value from 300 to 10 and save this file. The gc_timeout file contains some timeout value, after which the kernel declares a route to be dead and automatically switches to other route. Your system will now automatically switch to the second route every time the primary route fails.
To load balance outbound network connections from the internal network, the CONFIG_IP_ROUTE_MULTIPATH kernel option is used, which allows you to have multiple default gateways. It is set up by removing the default gateway from the /etc/sysconfig/network file and setting up the default gateway using advanced routing features with the command we issued.
Congrats now your Linux machine is configured as a Router.
Installing Linksys WMP54G with NDISWRAPPER-11
Installing Linksys WMP54G with NDISWRAPPER-11
1.
Code:
tar -zxvf ndiswrapper-0.11.tar.gz
2.
Code:
cd ndiswrapper-0.11
3.
Code:
make install
4.
Code:
ndiswrapper -i /mnt/cdrom/Drivers/wmpci54g.inf
5.
Code:
modprobe ndiswrapper
6.
Code:
ndiswrapper -l
Code:
Installed ndis drivers:
wmpci54g driver present, hardware present
7.
Code:
ndiswapper -m
Code:
Adding "alias wlan0 ndiswrapper" to /etc/modules.conf
8.
Code:
dhcpcd wlan0
9.
Code:
iwconfig wlan0
Code:
wlan0 IEEE 802.11b ESSID:"linksys"
Mode:Managed Frequency:2.437GHz Access Point: 00:0F:66:58:7E:A6
Bit Rate:18Mb/s Tx-Power:14 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Power Management:off
Link Quality:94/100 Signal level:-53 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:347 Invalid misc:7753 Missed beacon:0
Open /etc/rc.d/rc.wireless.conf
Scroll down until you see this:
Code:
--------- START SECTION TO REMOVE -----------
Pick up any Access Point, should work on most 802.11 cards
*)
INFO="Any ESSID"
ESSID="any"
;;
---------- END SECTION TO REMOVE ------------
Edit it to match this:
Code:
--------- START SECTION TO REMOVE -----------
Pick up any Access Point, should work on most 802.11 cards
*)
INFO="linksys"
ESSID="linksys"
CHANNEL="6"
;;
---------- END SECTION TO REMOVE ------------
Save it.
Open /etc/rc.d/rc.local and add this to the end of the file:
Code:
/etc/rc.d/rc.wireless wlan0
/sbin/dhcpcd wlan0
Save it.
If you use this guide please offer a response. Also please ask questions I am willing to help. If you need and explanation do NOT hesitate to post. Enjoy!
1.
Code:
tar -zxvf ndiswrapper-0.11.tar.gz
2.
Code:
cd ndiswrapper-0.11
3.
Code:
make install
4.
Code:
ndiswrapper -i /mnt/cdrom/Drivers/wmpci54g.inf
5.
Code:
modprobe ndiswrapper
6.
Code:
ndiswrapper -l
Code:
Installed ndis drivers:
wmpci54g driver present, hardware present
7.
Code:
ndiswapper -m
Code:
Adding "alias wlan0 ndiswrapper" to /etc/modules.conf
8.
Code:
dhcpcd wlan0
9.
Code:
iwconfig wlan0
Code:
wlan0 IEEE 802.11b ESSID:"linksys"
Mode:Managed Frequency:2.437GHz Access Point: 00:0F:66:58:7E:A6
Bit Rate:18Mb/s Tx-Power:14 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Power Management:off
Link Quality:94/100 Signal level:-53 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:347 Invalid misc:7753 Missed beacon:0
Open /etc/rc.d/rc.wireless.conf
Scroll down until you see this:
Code:
--------- START SECTION TO REMOVE -----------
Pick up any Access Point, should work on most 802.11 cards
*)
INFO="Any ESSID"
ESSID="any"
;;
---------- END SECTION TO REMOVE ------------
Edit it to match this:
Code:
--------- START SECTION TO REMOVE -----------
Pick up any Access Point, should work on most 802.11 cards
*)
INFO="linksys"
ESSID="linksys"
CHANNEL="6"
;;
---------- END SECTION TO REMOVE ------------
Save it.
Open /etc/rc.d/rc.local and add this to the end of the file:
Code:
/etc/rc.d/rc.wireless wlan0
/sbin/dhcpcd wlan0
Save it.
If you use this guide please offer a response. Also please ask questions I am willing to help. If you need and explanation do NOT hesitate to post. Enjoy!
Sunday, June 7, 2009
Visual Sidekick
Visual Sidekick 3 is a powerful Visual Studio / C++ addin designed to improve any C++ and C# developer's efficiency. Visual Sidekick 3 offers an up-to-date, searchable database of all project classes, symbols, files and project folders. Additional features include a symbol browser, source code navigator, source code generator, code metrics report, header/source flip, method declaration-definition flip and clipboard history.
download now
download now
ASPNet Spell
ASP.Net Spell-Check component provides international spellchecking for your ASP.Net web forms. It can be installed and integrated into most applications in a few minutes. AspNetSpell behaves very similarly to MS Word's own spellchecker, making it familiar to users. The software includes familiar features such as Grammar Checking and Personal Dictionaries. AspNetSpell is compatible with ASP.Net 1 and 2, and is W3C HTML / XHTML Compliant.
download now
download now
Stunnix C and C++ Obfuscator
Stunnix C and C++ Obfuscator is cross-platform professional obfuscator tool for making C/C++ code difficult to understand and rework (even after use of code prettyprinters), with advanced GUI (Project Manager) and ActiveX symbols extraction tool. It has unique support for all dialects of C/C++ and heavy use of preprocessor, source compression mode, has a lot of means for easy preparation of code for obfuscation and other unique features.
download now
download now
Jitbit AspNetForum
Jitbit AspNetForum: A powerful forum software for an ASP.NET website.A discussion board ASP.NET component that can be installed in seconds. This ASP.NET forum is datasource independent (Access/SQL-server), supports user profiles and registration, private messaging, online administration, email notifications engine, RSS-feeds,it is cross-browser and more. Source code license available.Free edition available.
download now
download now
Blog Script for PHP
Blog Script for PHP: Easy to install blogging system for PHP and MySQL. Sinlge and multy-user modes. Bloly is installed on thousands servers world wide. Bloly blog script is based on simple templates. It's very easy to afjust Bloly Blog to fit any design of any website.You may see live sample on our website.Bloly Blogging system is completely free.
download now
download now
Xlight ftp server
Xlight ftp server is an easy-to-use ftp server with very little memory and CPU, Xlight also has many professional features such as ODBC,LDAP,Active Directory,SSL,remote administration,IPv6 etc.
download now
download now
WinaXe Windows X Server
WinaXe Windows X Server-Run Linux and Unix on Windows Desktop. The WinaXe Windows X Server is a program that emulates the X terminal on your PC. WinaXe is XServer implementation of the X11 R6 release of the X Window System. The X Server can run one or more X Window based client applications (X clients) that are resident on a host computer.The host can be any computer that supports the X protocol.
download now
download now
Servers Alive
Servers Alive: Use Servers Alive to automatically monitor critical server functions and processes even when your data center is closed. Comprehensive reporting and notification features alert you via SMTP mail, cell phone messaging, Paging, Instant Messenger, ICQ, Pop-Up message, or NotePager. Easily create scripted response scenarioes to reboot, shut down, execute another program, or take any other emergency response action.Try free Windows version today.
download now
download now
Serv-U
Serv-U is a powerful,easy-to-use,award-winning File Server that allows files to be shared across the Internet using the FTP, HTTP, and SFTP protocols. Serv-U helps you securely and efficiently share files with your users by employing industry-standard SSL encryption, powerful management tools, and detailed logging. Using the built-in transfer client, users can access the File Server using their Web browser.
download now
download now
AbiWord
AbiWord: A word processor.Leaner and quicker than OpenOffice.Compatible with Microsoft Word documents and OpenDocument Format.
download now
download now
OpenOffice.org
OpenOffice.org: Big, full featured suite of tools for word processing and spreadsheets. Compatible with and a free replacement for Microsoft Word documents. Also supports OpenDocument Format.
download now
download now
Pidgin -Instant Messaging
Pidgin -Instant Messaging: Connect to multiple IM accounts simultaneously in a single app, including: AOL IM, MSN, and Jabber.
Supported chat networks:
Supported chat networks:
* AIM
* Bonjour
* Gadu-Gadu
* Google Talk
* Groupwise
* ICQ
* IRC
* MSN
* MySpaceIM
* QQ
* SILC
* SIMPLE
* Sametime
* XMPP
* Yahoo!
* Zephyr
download now
Supported chat networks:
Supported chat networks:
* AIM
* Bonjour
* Gadu-Gadu
* Google Talk
* Groupwise
* ICQ
* IRC
* MSN
* MySpaceIM
* SILC
* SIMPLE
* Sametime
* XMPP
* Yahoo!
* Zephyr
download now
Miro-Video Player / Video Podcasting
Miro-Video Player / Video Podcasting: Beautiful interface. Plays any video type (much more than windows media player). Subscribe to video RSS, download, and watch all in one. Torrent support. Search and download from YouTube and others.
download now
download now
Subscribe to:
Posts (Atom)
