Saturday, October 13, 2007

FrostWire

=====FrostWire=====
I saw FrostWire mentioned in one of the Linux forums and thought that I'd give it a try. I downloaded FrostWire from [http://www.frostwire.com/ The FrostWire Site]. It saved to my desktop by default. To install the program I opened a terminal and installed the .rpm package.
sudo rpm -ivh /home/glenn/Desktop/frostwire-4.13.2.noarch.rpm
Once installed there will be a new menu item, Applications > Internet > FrostWire. Alas, clicking on FrostWire in the menu did nothing. FrostWire appears to be non-functional. But wait, a little digging for a solution got me some help. A thread at [http://forum.fedoraforum.org/forum/showthread.php?t=163529&highlight=frostwire Fedora Forum] shows that one needs to install something called '''libXp'''. To do that I opened a terminal and typed
sudo yum install libXp
A few seconds later '''libXp''' was installed. Now clicking the menu item runs FrostWire and I see the '''Language Options screen.

[[Image:screenshot-frostwire setup dialog.png]]

Clicking '''Next''' advances to the welcome screen.

[[Image:screenshot-frostwire setup dialog-1.png]]

Clicking '''Next''' advances to the '''Save Folder''' dialog.

[[Image:screenshot-frostwire setup dialog-2.png]]

I'll leave the save folder as it is. Clicking '''Next''' advances to the '''Connection Speed''' dialog.

[[Image:screenshot-frostwire setup dialog-3.png]]

I have cable so I'll leave the default. Adjust this to your own preference. Clicking '''Next''' advances to the '''Chat Nickname''' dialog.

[[Image:screenshot-frostwire setup dialog-4.png]]

At this point I was unable to type anything in the box. Looking in the FrostWire forums I found that there seems to be a bug in the installer related to language selection. Nothing I tried worked so I cancelled the setup and started it again. This time I was able to type in a chat nickname and move forward with the setup. Clicking '''Next''' advances to the '''Scan For Files''' dialog.

[[Image:screenshot-frostwire setup dialog-5.png]]

I didn't want FrostWire to scan my system so I selected '''No''' and clicked '''Next''', advancing to the '''Finish Setup''' dialog.

[[Image:screenshot-frostwire setup dialog-6.png]]

FrostWire launches and I'm outa here!

[[Image:screenshot-frostwire.png]]

Flash

===Flash Player===
There's more than one way to install Adobe FlashPlayer on your Fedora 7 system, and as many opinions as to which was is the right way. Here's what works for me. I download the .tar.gz version from [http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash Adobe's download site]. The file saves to my desktop, so I move it to the /opt folder. To do that I open a terminal as root and type
mv /home/glenn/Desktop/install_flash_player_9_linux.tar.gz /opt/
Change to the /opt folder
cd /opt
and unpack the archive
tar xfvz install_flash_player_9_linux.tar.gz
This command extracts all the files from the archive and puts them into a newly created folder, /opt/install_flash_player_9_linux. Now I need to copy the file libflashplayer.so to the Firefox and Mozila plugins folders. In a terminal type
cp /opt/install_flash_player_9_linux/libflashplayer.so /usr/lib/firefox-2.0.0.4/plugins
and
cp /opt/install_flash_player_9_linux/libflashplayer.so /usr/lib/mozilla/plugins
Close and restart Firefox. In the url bar type '''about:plugins'''. You should see '''Shockwave Flash''' listed.

[[Image:flash-plug-in.png]]

=====The .rpm way=====
Download the .rpm repo file from the same web site. Install by right clicking on the desktop file and choose '''open with archive manager'''. Now that the adobe repo is added to your system you can open a terminal and install flash by typing yum install flash-plugin.

Return to [[Fedora 7]]

Extra Repositories

===Adding Extra Repositories to Fedora 7===
[[#Livna|Livna]]

[[#FreshRPMS|FreshRPMS]]
There are several third party repositories available to Fedora 7 users. Some of them work well together while others don't. Use caution when choosing your
repositories so that you don't end up with dependency errors. The one's that I use are [http://rpm.livna.org/rlowiki/ Livna] and [http://www.freshrpms.net FreshRPMS.]

=====Livna=====
To add the [http://rpm.livna.org/rlowiki/ Livna] repository simply follow this link [http://rpm.livna.org/rlowiki/ Livna] and click on the Fedora 7 Repository RPM hyperlink. You can choose to '''open with archive manager''' or '''save to desktop'''. If you '''save to desktop''' you will need to right click on the file to install it.

An alternative method for installing the [http://rpm.livna.org/rlowiki/ Livna] repository. Open a terminal as root and type
rpm --import /etc/pki/rpm-gpg/*
rpm -ivh http://rpm.livna.org/livna-release-7.rpm
rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-livna
The [http://rpm.livna.org/rlowiki/ Livna] repository is now installed and active, making a greater selection of software available to you. The repository will also be included during system updates.

=====FreshRPMS=====
To add the [http://www.freshrpms.net FreshRPMS] repository follow this link to the [http://www.freshrpms.net FreshRPMS] web page. About 1/2 way down the page there's a line starting with '''The easiest way to install freshrpms.net packages is to click here from within firefox, '''. Click the link and choose to '''open with software installer''' or '''save to desktop'''. If you '''save to desktop''' you will need to right click on the file to install it. After the installation you need to edit the freshrpms.repo file to make it disabled by default. This is to avoid possible dependency errors or conflicts between repositories. Open a terminal as root and type
gedit /etc/yum.repos.d/freshrpms.repo
Find the line near the top of the file that says
enabled = 1
Change it to read
enabled = 0
This will disable the repository. Save the file and close the editor. You can temporarily enable it using yum by typing
yum --enablerepo=freshrpms install thepackageicantlivewithout

Return to [[Fedora 7]]

Edit Default Path

===Changing the default search path===
I always make a small change to my default $PATH because when I work with sudo I still can't use some of the system commands without typing the path to the command and then the command. A good number of the commands reside under /sbin, so I add /sbin to my $PATH. Here's what I do. Open a terminal as your regular user and edit the file .bash_profile in your home folder.
gedit .bash_profile
This is what the default file looks like.
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH
I change the file to look like this, adding :/sbin to the end of the $PATH line.
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin:/sbin
export PATH
Save the file and exit the editor. Log out and back in to the desktop and you will now have access to the commands in /sbin by default.

Return to [[Fedora 7]]

Color Bash Prompt

===Color Bash Prompt===
I like to colorize my bash prompt. It's an easy way to see if you are working as your regular user or as root.
Open a terminal as your regular user, making sure you are in your home directory, and type
gedit .bashrc
Move to the bottom of the file and add this line
PS1="[\[\033[1;34m\]\u\[\033[0m\]@\h \W]\\$ "
The number 34 seen in that line gives you a blue prompt.
Save and exit the editor. Now log in as root in the terminal and make sure you are in root's home folder. Again type
gedit .bashrc
Move to the bottom of the file and add the same line that we added for regular user
PS1="[\[\033[1;31m\]\u\[\033[0m\]@\h \W]\\$ "
Left as it is, this line will give you a red prompt. Save and exit the editor.
The actual color code is "1;31" inside the PS1 variable. The 1 says make it '''bold''' and the 31 says the color red.

1;30 Black

1;31 Red

1;32 Green

1;33 Yellow

1;34 Blue

1;35 Magenta

1;36 Cyan

1;37 White (Don't think white would show up too well on this page)

Back to [[Fedora 7]]

Beryl

[[#Installing Beryl|Installing Beryl]]

[[#Auto Starting Beryl|Auto Starting Beryl]]

[[#Beryl Performance Tweak|Beryl Performance Tweak]]

===Installing Beryl===
Open a terminal and as root or using sudo type
yum install beryl beryl-manager emerald
This will install everything you need to get Beryl up and running on your Gnome desktop. Once everything is installed there will be a menu entry under

'''Applications > System Tools > Beryl Manager'''. Click on that item and the Beryl icon will appear on the top panel. From there you can configure Beryl to your liking.

=====Auto Starting Beryl=====
If you want Beryl to start automatically when you log in to your Gnome desktop add it to the sessions manager. Click on '''System > Preferences > Personal > Sessions'''. The sessions manager opens.

[[Image:sessions1.png]]

Click the '''new''' tab and the '''New Startup Program''' window opens.

[[Image:sessions2.png]]

Under '''name''' enter a name for the program. Beryl would be the logical choice, although you can call it whatever you like. Under '''Command''' enter '''beryl-manager'''. Click '''OK''' and click '''Close'''. Now whenever you log in to your '''Gnome''' desktop Beryl will start automatically.
=====Beryl Performance Tweak=====
It's been suggested that you can improve Beryl's performance with a few changes to the settings. Right click the Beryl icon on the top panel and select '''Beryl Settings Manager'''.

[[Image:berylmanager1.png]]

Uncheck '''Detect Refresh Rate''', set '''Refresh Rate''' to '''200''' and unckeck '''Sync To VBlank'''. I did this on one of my systems but the performance gains were not too noticeable , at least in my case. Your results may vary and you can always undo the changes.

Back to [[Fedora 7]]

Basic Display

====Fix My Display====
I see a lot of posts in the Linux forums about users who have just installed Linux and upon the first boot they get a blank screen and no GUI. The problem is often a misconfigured /etc/X11/xorg.conf file or a misconfigured default runlevel. Check your default runlevel first. There are three other areas that could be causing your display troubles. They are the '''Device''' section, the '''Monitor''' section and the '''Screen''' section. Following these steps will get you a basic GUI that you can work with.


[[#Runlevel|Runlevel]]

[[#Display|Display]]

[[#Monitor|Monitor]]

[[#Screen|Screen]]

=====Runlevel=====
If you boot your Fedora system and it doesn't go into GUI mode, it could be that you need to edit the '''default runlevel'''. If the '''default runlevel''' is incorrect you will be left at a command prompt with no error messages. This is runlevel 3. To boot to the GUI mode the system needs to boot to runlevel 5. To correct this malady login as root at the command prompt and type '''vi /etc/inittab'''. There will be a section that looks like this:
id:3:initdefault:
Change the line so that it looks like this
id:5:initdefault:
Save the file, exit the editor and reboot. Your Fedora system will boot to the GUI this time.

=====Display=====
Boot the computer and log in as root. At the command prompt type
vi /etc/X11/xorg.conf
Once the '''vi''' editor opens you will need to press the '''INS''' key to get into edit mode. Look for the section that is similar to this:
Section "Device"
Identifier "Videocard0"
Driver "intel"
EndSection

Change the driver to 'vesa'. Save the file with the following keystrokes: '''ESC : wq! ENTER'''. Back at the command prompt type
startx
and press enter. After a short delay while the system is working you should be presented with the graphical display that is at least ''close'' to what you expected. From there you can work to fine tune things like the proper video driver and screen resolution.

=====Monitor=====
To get the correct refresh rates for ''your'' monitor you need to edit the '''monitor''' section. Often times the screen refresh rates are incorrect and my cause an off center display or some other malady. Before you change the refresh rates make sure you know what the proper rates are for your particular monitor. These can be found on the back of the monitor, in the manual that came with the monitor or most certainly from [http://www.google.com Google]. Look for the section that is similar to this:

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30-107
VertRefresh 48-120
EndSection

Changing the HorizSync and VertRefresh numbers to ones that accurately reflect your monitor will have a drastic effect on the quality of the display. Save the file and exit the editor. That will bring you back to the command prompt. Again, as we did in the '''Device''' section, type
startx
and press enter. Again after a short delay you should see a much improved GUI display.


=====Screen=====
To further improve upon the quality of the display and to get the correct or desired screen resolution you need to edit the '''screen''' section in the /etc/X11/xorg.conf file: Before you change anything here you need to know the limitations of your monitor. What is the maximum resolution that it will display? Trying to set a resolution higher than the monitor is capable of providing can and probably will cause undesired results. The maximum resolution for your monitor can be found on the back of the monitor, in the manual that came with the monitor or by searching [http://www.google.com Google]. Once you know what your monitor is capable of then you can go ahead and try to configure the display for the resolution that you prefer. Most of today's monitors are capable of a resolution of at least 1280x1024. I'll use this resolution in this example. In the xorg.conf file look for the section that is similar to this:

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768"
EndSubSection
EndSection

The part we're interested in is the Modes line(s). In the above sample the computer is configured to show a display of 1024x768 only. This will usually work well, but we want to use 1280x1024 because that is what our monitor will do and it's what we prefer. Change the Modes line so that it looks like this:
Modes "1280x1024" "1024x768"
Save the file and exit the editor. This leaves you back at the command prompt. As we did above, type
startx
and press enter. Again after a short delay you should see a much improved GUI at the desired screen resolution.

This is just a basic writeup on editing the xorg.conf file to resolve some of the issues that I see mentioned on a daily basis in the Linux forums.

Auto Login

If you use wireless to connect to the network and internet you may not want to use the auto login feature.
My preference is to be automatically logged in when I reach my Gnome desktop. Here's how to enable auto login for your user. On the top panel, select System > Administration > Login Screen. Enter the root password and the login window appears.

[[Image:login window1.png]]

Click on the '''users''' tab.

[[Image:login window2.png]]

and click the '''add''' button.

[[Image:login window3.png]]

Add your user name

[[Image:login window4.png]]

Click '''add''' once more. Now click on the '''security''' tab.

[[Image:login window5.png]]

On this screen you want to click the drop down boxes for '''Enable Automatic Login''' and '''Enable Timed Login''' and add yourself to the lists. Click the '''close''' icon and you are done. Now, every time you boot to your Gnome desktop you will be automatically logged in. No need to enter your user name and password.
Some people feel that auto login is a security risk. I'm sure it is on a multi-user system. My computers are all home machines. All the Linux boxes
are used by me and me alone except for the rare occasion where another family member might use the computer for a few minutes. No security issues here.


Back to [[Fedora 7]]

Adobe Reader

=====Adobe Reader 8.1.1=====
Download the Adobe Reader '''rpm''' file from [http://www.adobe.com/products/acrobat/readstep2_allversions.html Adobe Download]. I install from the /opt folder so I move the file there.
sudo mv /home/glenn/Desktop/AdobeReader_enu-8.1.1-1.i486.rpm /opt/

Change to the /opt folder
cd /opt
and install Adobe
sudo rpm -ivh AdobeReader_enu-8.1.1-1.i486.rpm
After these steps were taken I opened a '''.pdf''' file in Firefox without a problem. There were no additional steps that I needed to take to get Acrobat Reader to work.

--[[User:Glenn|Glenn]] 05:18, 21 September 2007 (EDT)

Monday, June 18, 2007

Two Weeks with Fedora 7

It's been 2 1/2 weeks since Fedora 7 was released. May 31 to be exact. I installed it on my Toshiba Satellite as soon as it was available, triple booting with Windows Vista and Fedora Core 6. Fedora 7 has been running very well to date. The display resolution is perfect at 1280x800 and I have all the applications I need. Internet, e-mail, etc. The IPW3945 wireless is even working flawlessly. Still, there's no sound volume. As far as I can tell music plays correctly, I just can't hear it. It's not really a big issue with me. It would be nice to be able to play some tunes, but I'll survive with out them. The built-in the bezel web cam doesn't work either, but I consider that a toy at best. I really have no use for it. Other than those two minor issues I'm very pleased with the latest release from the Fedora developers.