If you have enjoyed Fedora Core 4, I can higly recommend upgrading to Fedora 5
and have been using it myself from a week after it's release.
To enable RTSP real audio streaming protocol to use realplay in firefox. Open firefox and about:config
then create a "new string" of network.protocol-handler.app.rtsp with value "/usr/bin/realplay".
I have had problems with the 2.6.17 kernels and RAID arrays on Promise FastTrak 20376 as boot devices.
But rebuilding initrd for the particular 2.6.17 kernel on your system seems to fix the problem:-
#yum -y --enablerepo development update mkinitrd
#mv /boot/initrd-2.6.17-1.2174_FC5.img /boot/initrd-2.6.17-1.2174_FC5.img.old
#mkinitrd /boot/initrd-2.6.17-1.2174_FC5.img 2.6.17-1.2174_FC5
If you have enjoyed Fedora Core 3, I can higly recommend upgrading to Fedora 4
and have been using it myself from a week after it's release.
Badblock checking a LVM2 volume - On a RedHat ES V4.0 system I recently needed
to badblock it's volumes that use LVM2 partioning. To check for bad blocks you really
need to un mount the partition before checking. You obviously can't un-mount the root
partition on a live system. I therefore used the Fedora Core 4 Rescue Boot CDR, which thankfully
automatically mounts LVM2 volumes. So on this single disk RH V4 system it had:-
#/dev/hda1 ;/boot
#/dev/VolGroup00/LogVol00 ;/ root partion
#/dev/VolGroup00/LogVol01 ;swap
From the FC4 Recuse disk it will mount these under /mnt/sysimage, before you can run "e2fsc" with non-destructive
read-write testing you must unmount all the /mnt/sysimage mounts. Then your ready to run:-
#e2fsck -cc -v /dev/VolGroup00/LogVol00
Note this will take quite some time. It should relocate (assuming spare blocks) any bad blocks it finds. Repeat for /boot
with:-
#e2fsck -cc -v /dev/VolGroup00/LogVol01
The next problem is to check the swap partion, for this I rebooted FC4 Rescue so it re-mounted the volumes then run:-
chroot /mnt/sysimage/
Then re-create the swap partion. Note I include instruction not to use swap for completness:-
#swapoff -a ;un-mounts all swaps specified in /etc/fstab
#mkswap -c /dev/hda1 ;create swap on /dev/hda1 and badblock check
After that you should have bad block checked all partition, as long a large amounts of badblocks are not found
you should be able to reboot the live system with the knowledge badblocks are taken care of. If lots of bad blocks
are found it time to get a new disk!. This can obviously be applied to all Fedora Core systems using LVM2.
If you have enjoyed Fedora Core 2, I can higly recommend upgrading to Fedora 3
While Fedora Core 2 is not recommended for production
enviroments I can confirm it is proving very reliable and use it
for my own dektop. Below is some of the workarounds and extras you
may need:-
There is a problem installing on some systems dual booting with
Windows XP. This problem occurs if the BIOS has not used LBA disk
geometry for used by Fedora Core 2. Please see http://www.redhat.com/archives/fedora-devel-list/2004-May/msg00908.html
for full details and workarounds
Kernel 2.6.7 uses different network parameters than kernel 2.6.6.
For example, window scaling is turned on in 2.6.7 (but it was off
on 2.6.6). This causes problems with most firewalls which can result in very
slow network speeds compared to kernel 2.6.6. Execute the
following commands with root privileges, that should "fix" the
networking problem for all new connections:
sysctl -w net.ipv4.tcp_default_win_scale=0
sysctl -w net.ipv4.tcp_moderate_rcvbuf=0
Put this in your /etc/rc.d/rc.local file or put
"net.ipv4.tcp_default_win_scale = 0" directly into
/etc/sysctl.conf (which is the better way, but be careful
that it doesn't get overwritten by package updates).
The kernel 2.6.7 network parameter changes are fine, the problem is other
firewalls etc, that can't except window scaling enabled.
How to upgrade to Fedora if you don't have a CDROM or DVD drive. The following
link gives you full details of how to upgrade an existing Linux system by mounting an ISO image
and boot it from your hard disk:-
http://www-2.cs.cmu.edu/~colohan/docs/fedora_upgrade.html
If your wireless interface is not supported directly by Fedora
Core 2 check out both of the following sites:-
http://sourceforge.net/projects/ndiswrapper/
http://www.linuxant.com/driverloader/
Not all applications and utilities know the video envirment is
now xorg from xfree86. If you get the following sort of error on
starting a Gnome session:-
Error activating XKB
configuration.
Probably internal X server problem.
X server version data:
The X.Org Foundation
60700000
If you report this situation as a bug, please include:
- The result of xprop -root | grep XKB
- The result of gconftool-2 -R
/desktop/gnome/peripherals/keyboard/xkb
you need to add additional symoblic links in
/usr/X11R6/lib/X11/xkb/rules:-
ln -s xorg.lst xfree86.lst
ln -s xorg-it.lst xfree86-it.lst
ln -s xorg.xml xfree96.xml
The approved update method for Fedora Core 2 is /usr/bin/yum.
You may wish to expand the sites that yum uses by editing
/etc/yum.conf. Check out http://fedorafaq.org for a yum.conf and details of
adding the GPG keys to rpm so you can verify the integrity of the
packages
Need to setup a APC smart-ups check out http://fedoranews.org/anewman/apcupsd/
and get apcupsd from the links provided. It was very simple to
setup
If you have a AMD Athlon processor and want some power saving check out http://members.jcom.home.ne.jp/jacobi/linux/softwares.html
Athcool manages to reduce my CPU temp from 60C to 40C on my Athlon XP 2200+. I have "athcool on" most of the time
but turn it off "athcool off" to play audio DVD's. System remains very stable.
How to setup a Synaptics trackpad on your laptop under Fedora Core 2, See:-
http://w1.894.telia.com/~u89404340/touchpad/index.html
lm_sensors & gkrellm - The 2.6 kernel now has enviromental
monitoring built-in. gkrellm is GUI system mointor that can display
and monitor the values returned by lm_sensors. To setup lmsensors
run /usr/sbin/sensors-detect, to run this untillity you need the
/usr/sbin path added to root shell use to run it. Run:-
PATH=$PATH:/usr/sbin ;or add it to
/root/.bashrc
sensors-detect ;follow the instructions
Checking which chips are used on your motherboard and loading the
appropriate driver may have to be done namually if sensor-detect
fails to find it. Once /usr/bin/sensors is returning sensible
values for your CPU temperature and fan, install gkrellm-2.1.28-3
which can found on the third Fedora core 2 install CDROM. The
/usr/bin/gkrellm GUI can then be used to monitor the CPU
temperature and fan speeds that sensor provides.
The Fedora Core 2 like other Redhat releases doesn't include support for accessing Windows NTFS
partitons as standard. You can add the Open Source NTFS driver support by recompling the kernel with NTFS
enabled, or download precomplied versions from below:-
http://linux-ntfs.sourceforge.net/rpm/fedora2.html
Note at present the NTFS linux support only allows read-only access so you may want to also create a
Windows FAT32 partition on a dual boot system for the common interchange of files between Windows NT/2000/XP NTFS
partitions and Linux. Please see full Linux NTFS detials on:-
http://linux-ntfs.sourceforge.net/info/ntfs.html
To intercept all requests and redirect them to HTTPS port 443, use the following
rewrite script in the Apache httpd.conf:-
<VirtualHost *>
ServerName www.domain.com
ServerAdmin webmaster@domain.com
DocumentRoot /var/www/domain
RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [L,R,NC]
</VirtualHost>
What this does is act on any connection which does not come in on port 443.
The neat thing is that it then takes everything in the URL after the first slash
with the (.*) and remembers it as $1. By "after the first slash" I mean after the
slash at the end of http://www.domain.com/ <-- that last slash. So everything
after that slash, that is the internal URL, is memorized. The URL is then rewritten
as https://www.domain.com/$1 where "www.domain.com" came from the SERVER_NAME
httpd variable and $1 is the internal URL as memorized earlier.
The ideal way of your email server receiving Email is to have a
permanent connection to the Internet with SMTP [tcp port 25] open
so other Email servers can automatically send you any mail for your
domain. Unfortunately in the real world many users only have
dial-on-demand ISDN connections to the Internet so SMTP mail
retrieval is not a practical option
With linux being used more and more for small email servers and
embedded Internet appliances such as the Cobalt Qube3, many users
are forced to use POP3 to retrieve email from a global POP account.
Fetchmail is the common utility used for this purpose even if
hidden by a user interface as in many Internet appliances
Fetchmail is a remote-mail retrieval and forwarding utility
intended to be used over dial up TCP/IP links. It supports every
remote-mail protocol now in use on the Internet: POP2, POP3, RPOP,
APOP, KPOP, all flavours of IMAP, ETRN, and ODMR. Fetchmail
retrieves mail from remote mail servers and forwards it via SMTP,
to the normal linux SMTP servers agents such as postfix, sendmail,
mutt, elm(1) or BSD Mail.
While Fetchmail is a excellent utility it can have one notably
problem/feature that needs to be taken into account, when
configuring how often Fetchmail polls the remote mail box. Most
POP3 accounts don't allow multiple connections yet alot of early
linux distributions will automatically start another Fetchmail
access if the poll time has expired since the last POP3 access
started. If the previous remote mail access hasn't completed yet
due to an excess of email waiting at the ISP, and the next
Fetchmail access starts this often aborts the previous access. The
result is all the email the previous access fetched before being
aborted is not deleted from the remote ISP. The next access again
fails to fetch all the email within the interval before the next
access starts so the same email is read time and time again without
removing it from the remote ISP. It is therefore important to
consider the speed of your Internet connection and performance of
your remote ISP mail server when determining how often to poll the
remote mail box. This problem can also occur if your ISP diconnects
you due to say a 2 hour limit. See the following example for single
channel ISDN:-
Single Channel ISDN and Fetchmail Poll Rate
The typical download rate for 64kbps ISDN is 7 Kbytes/sec so for a
15 minute poll interval the maximum about email that can be
retrieved in one go is 7 x 60 x 15 = 6300Kbytes or 6.15MB. When
taking other delays into account the maximum email size this
configuration could retrieve in one go is nearer to 5MB.
If you inadvertently end up with a dead lock with mail being
continually read multiple times, the answer is to increase the
Fetchmail poll interval to something very large, allow all the
waiting email to be retrieved in one go without another access
starting. Clear the remote mailbox in this way, then reset the poll
interval once your sure all the email has been successfully
retrieved and removed from the remote ISP mailbox
The latest dsitributions of the excellent OpenOffice.org now comes
with a wide selection of different language dictionaries and hyphenation
as standard. This can cause problems with excessive ram usage when using spelling
suggestion in writer via right-clicking a bad spelling. This can appear as the system
hanging for several minutes. To speed things up and reduce the ram usage, edit:-
/usr/lib/ooo-1.1/share/dict/ooo/dictionary.lst
and comment out any languages you don't use.
2.6 Kernels have IPSec enabled in the kernel. Fedora 2/3 comes with IPSec-Tools providing
racoon (IKE deamon) and Setkey. You can also add PPTP and L2TP if necessary:-
http://ipsec-tools.sourceforge.net/
http://www.funknet.org/doc/tunnel/l2tp.html
http://www.openswan.org/
http://www.jacco2.dds.nl/networking/freeswan-l2tp.html
http://pptpclient.sourceforge.net/
If you are using a 2.4.20 or newer Liunx kernel you may get
asked whether you have it enabled or not, as it can have problems
with some firewalls and other network servers that don't yet
support the protocol. With the present builds of kernels the ECN
signalling is disabled. But just incase you have had something
accidentally enable ECN, it is controlled by:-
/proc/sys/net/ipv4/tcp_ecn
If this file contains a "0" then ECN signalling is disabled. To
learn more about the TCP ECN protocol see rfc3540.txt.
Having problems with mime types and Mozilla and trying to get it
play multimedia like Real Audio. You need to check out the
following three files:-
| /etc/mime.types |
;The mime type must be define in this file before Mozilla will
acknowledge it. |
| /etc/mailcap |
;Definitions of how to play different mime types. |
| /etc/pluggerrc |
;If your using Plugger 4.0 see "about:plugins" then this file
amongst other possible versions (see "man plugger"), then this file
defines how plugger is to play the mime type. |
Have you downloaded log files or the like from Windows 2000/XP
servers to your linux system only to find they appear unreadable
and double spaced with control characters. The file will be in
Unicode UTF-16 format where your Linux system is almost certainly
wants ISO-8859-1 or UTF-8 character encoding.
You can use "iconv" to convert files between differnet character
formats. On our Red Hat system the command syntax is as below, on
others check your man pages:-
iconv -f UTF-16 -t UTF-8 input-file
> output-file
Send mail to with any comments
about this web site.
Last modified: 21 August 2006
www.linnetsol.co.uk © 2010 Linnet Solutions Ltd
All Rights Reserved
|