This guide a personal configuration of Fedora Core 6. This page is to provide some common installation tips that people may find useful. Keep in mind this works for me, so take care in doing proper backups to critical files whenever trying something.
It is highly recommended you read the Fedora Core 6 Release Notes and official Installation Guide before installing Fedora.
Obtain the Fedora Core 6 cd images or DVD image from a Fedora mirror (or use the torrent) and burn to CD's or DVD. (For more information on how to download Fedora Core CD's or DVD).
Boot from the first disc.
Warning: Installer problem. Please read Common Problems before installing. If you have an i686 system (most new computers), then enter:
when booting the first disc. This is required if upgrading an existing Fedora installation.
I did a Custom Install of Fedora Core 6.
Fedora Extras - [NOT Recommended at Install time]. If you select Fedora Extras, 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.
Warning: When using the Fedora Core Add/Remove Software application you will require a valid internet connection - preferrably high speed. It is recommended that you carefully select everything that you need during this installation step.
Note: There is a hidden option to select multiple packages. You can Right-Click over a major section (ex: KDE) and Select or Deselect all optional components.
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:
Display Settings -- Display settings are automatically detected and set. The resolution and scan rate may be significantly different than your typical settings. Just follow through the first boot process and set the proper resolution once you login.
Fedora Core 6 shipped with several bugs and problems. Most of the reported issues can be found on the following page: http://fedoraproject.org/wiki/Bugs/FC6Common.
If you have NOT yet installed FC6, then you can prevent this mistake at installation. When the booting the CD (or DVD) enter the following at the boot prompt:
If you upgraded from FC5 and find you have the wrong kernel installed follow these steps:
Download the proper kernel from: http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/Fedora/RPMS/ Install it: (enter root password when prompted) # su -c "rpm -Uvh --replacefiles --replacepkgs kernel-2.6.18-1.2798.fc6.i686.rpm"
Fedora Core, 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 your personal account for daily use root only for adminstration/configuration. To run as 'root' use su or sudo. 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.
[mirandam@charon ~]$ su Password: <--- Enter root password [root@charon mirandam]# chmod +w /etc/sudoers [root@charon mirandam]# echo 'mirandam ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers [root@charon mirandam]# chmod -w /etc/sudoers [root@charon mirandam]# exit exit
NOTE: Some users mentioned they require permissions change (chmod) because /etc/sudoers was read-only. However, I was able to run the above command with the file read-only.
The following is an example of how sudo lets you execute root commands:
[mirandam@charon ~]$ du -sh /root du: `/root': Permission denied <--- Fails!!! [mirandam@charon ~]$ 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'.
Fedora Core uses yum to install and update its software. When connected to the internet it will automatically determine application dependancies.
Fedora has 3 repositories enabled by default: core (the same packages that come on CD's/DVD), updates (updated packages, newer than core) and extras (countless other applications not included on CD's/DVD).
These repositories 'sign' their RPM file's to make sure they are valid when downloaded. Import the GPG keys to these repositories:
[mirandam@charon ~]$ sudo rpm --import /etc/pki/rpm-gpg/*
Third Party Repositories
For applications that are against Fedora policies (MP3, DVD, MPEG, NTFS, etc). A third party repository should be used. For the purpose of this guide, (most) all needs are met by the Livna repository. (Note: the Livna repository is NOT compatible with the Freshrpms repository.)
[mirandam@charon ~]$ sudo rpm -ivh http://rpm.livna.org/livna-release-6.rpm [mirandam@charon ~]$ sudo rpm --import http://rpm.livna.org/RPM-LIVNA-GPG-KEY
NOTE: Installation Prompt
After yum downloads the application or update requested it will prompt to install. This is good for learners or to keep track of what is happening. Applications can possibly be UN-installed in a update as well. If you wish yum to automatically install downloads and make changes, run yum with the -y (answer "yes") option.
# sudo yum -y install application_name
NOTE: Full System Updates
If you run the following, EVERY SINGLE RPM that has an available update through ANY repository will be updated.
[mirandam@charon ~]$ sudo yum update
Generally speaking this is highly recommended the FIRST time you install Fedora (if you have high speed internet). After that, full system updates are probably less necessary. Keep in mind that updates, may update all their dependancies, which can lead to long download times. Often a new update may break something that already worked. Please understand what you are doing before running continuous updates.
NOTE: If YUM does not run after first install.
You may see the following error:
Loading "installonlyn" plugin Existing lock /var/run/yum.pid: another copy is running. Aborting.
This is because the background YUM updater service is running. To stop it, run:
[mirandam@charon ~]$ sudo /etc/init.d/yum-updatesd stop
Fedora recommends users install a 3rd-party RPM packaged driver instead of using the installer from Nvidia's website. Currently Livna provides a well packaged driver.
NOTE: For users who upgraded from FC5 please read the known bugs and problems.
For yum only:
First, setup Livna Repository
[mirandam@charon ~]$ sudo rpm -ivh http://rpm.livna.org/livna-release-6.rpm [mirandam@charon ~]$ sudo rpm --import http://rpm.livna.org/RPM-LIVNA-GPG-KEY
Install the nvidia driver through Livna:
[mirandam@charon ~]$ sudo yum install kmod-nvidia
If you see the following message, then please read the note below:
Error: Editing failed, restoring backup
If a kernel update is installed at the same time, then a reboot will be required. If not, then simply log out completely of Gnome or KDE and the Nvidia driver should load. The Nvidia logo will flash quickly once.
For users without yum
Download the GPG Key and run:
[mirandam@charon ~]$ sudo rpm --import RPM-LIVNA-GPG-KEY
Navigate to http://rpm.livna.org/fedora/6/ and select your architecture: i386, x86_64 or ppc. You will need 2 components: xorg driver and nvidia kernel module.
For xorg driver, select the one matching the latest Nvidia driver (1.0.8776). For example:
For nvidia kernel driver you MUST MATCH YOUR KERNEL. Use the uname command for the proper match. For example:
[mirandam@charon ~]$ uname -rm 2.6.18-1.2798.fc6 i686
Install both files at the same time:
[mirandam@charon downloads]$ sudo rpm -ivh kmod-nvidia-1.0.8776-184.108.40.206_1.2798.fc6.i686.rpm \ xorg-x11-drv-nvidia-1.0.8776-2.lvn6.i386.rpm Preparing... ########################################### [100%] 1:kmod-nvidia ########################################### [ 50%] 2:xorg-x11-drv-nvidia ########################################### [100%] Error: Editing failed, restoring backup ----- see NOTE below
If you had a previous version of these files before, remove them first with rpm -e.
If you cannot find a perfect match you may will have to update to a kernel that matches from FC6 Updates.
If after installing you see the following error:
Error: Editing failed, restoring backup
then edit the file /etc/X11/xorg.conf
[mirandam@charon ~]$ sudo gedit /etc/X11/xorg.conf
Add the following lines to the END of the file:
Section "Files" ModulePath "/usr/lib/xorg/modules/extensions/nvidia,/usr/lib/xorg/modules" EndSection Section "Module" EndSection
NOTE: 64-bit users: please use the following line instead:
Re-enable the nvidia driver:
[mirandam@charon ~]$ sudo /usr/sbin/nvidia-config-display enable
Once done, logging out of KDE/Gnome and logging back in should initialize the driver. If not, try rebooting.
More information regarding this problem, can be found on the Livna wiki: http://rpm.livna.org/rlowiki/Packages/xorg-x11-drv-nvidia.
Fedora Core 6 ships and uses GCC 4.1. Some applications that were compiled with an older GCC (ex: 3.2) will require compatibility libraries. Make sure to have the following RPM's installed. These are included with the FC6 CD-disk3 or DVD or online (ftp, yum, etc).
With 'yum', run:
[mirandam@charon ~]$ sudo yum -y install compat-libstdc++-33 compat-libstdc++-296
The compat-libstdc++-33 package is required for Realplayer and the Sun Java browser plugin.
This is an optional step.
FC6 includes GCC 4.1 compiler. Some applications will NOT compile in GCC 4.1. You can install GCC 3.4 to allow compiling applications which do not yet support GCC 4.1. Make sure to have the following RPM's installed. These are included with the FC6 CD's or DVD or online (ftp, yum, etc).
With 'yum', run:
[mirandam@charon ~]$ sudo yum install compat-gcc-34 compat-gcc-34-c++
To use either, run gcc34 or g++34. I have more information on using alternate compilers.
ALSA is the "sound system" used by Fedora Core. It has drivers, libraries and utilities. The drivers are included with the kernel package.
If your sound card is not detected or working properly, most likely it will be an issue with ALSA . Try the following:
If your system requires an update run, then the following minimum is recommended:
[mirandam@charon ~]$ sudo yum update kernel alsa-lib alsa-utils
Users without yum can look for updates manually: http://download.fedora.redhat.com/pub/fedora/linux/core/updates/6/.
Other comments from previous guides: Fedora Core 3 Guide, Fedora Core 2 Guide.
Download RealPlayer 10.0 GOLD from: http://www.real.com/linux/.
Select: "Advanced Installation RedHat Package"NOTE: You can have both HelixPlayer and RealPlayer installed, however I recommend using RealPlayer over HelixPlayer. Users of amarok may find HelixPlayer required, if so, leave it.
Check for HelixPlayer: [mirandam@charon ~]$ rpm -q HelixPlayer HelixPlayer-1.0.7-4.fc6 Uninstall HelixPlayer: [mirandam@charon ~]$ sudo rpm -e HelixPlayer
Before installing RealPlayer, make sure to have the compat-libstdc++-33 compatibility libraries installed.
[mirandam@charon downloads]$ sudo yum install compat-libstdc++-33 Install RealPlayer: [mirandam@charon downloads]$ sudo rpm -ivh RealPlayer10GOLD.rpm Preparing... ########################################### [100%] 1:RealPlayer ########################################### [100%]
RealPlayer/HelixPlayer Forums: https://helixcommunity.org/forum/?group_id=154
Fedora Core 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 Livna repository and Fedora Extras.
XMMS: simple, older GUI, minimalistic features (but still popular)
[mirandam@charon ~]$ sudo yum install xmms xmms-mp3
[mirandam@charon downloads]$ sudo rpm -ivh xmms* glib* gtk+*(Note, you should have mikmod installed from the Individual Package Selection, also on your CD's/DVD)
Audacious: (A fork of Beep Media Player - BMP). XMMS rebuilt to be a little bit more modern. Still basic but much better than XMMS.
[mirandam@charon ~]$ sudo yum install audacious audacious-plugins-nonfree* NOTE: There is a '*' at the end.NOTE: Installing Audacious will replace BMP (if you have it installed). Attempting to install BMP will actually install Audacious.
[mirandam@charon downloads]$ cd audacious [mirandam@charon audacious]$ sudo rpm -ivh *
Rythmbox/Gstreamer - A simple audio application similar to iTunes layout.
[mirandam@charon ~]$ sudo yum install gstreamer-plugins-ugly
[mirandam@charon downloads]$ cd gstreamer [mirandam@charon gstreamer]$ sudo rpm -ivh *
Amarok - A modern feature rich media player application.
[mirandam@charon ~]$ sudo yum install amarok amarok-extras-nonfree
Amarok Engine: Amarok requires you to select an "engine" which can play different media. The current support engines are Xine/Gstreamer and RealPlayer/HelixPlayer. If you installed the gstreamer-plugins-ugly or amarok-extras-nonfree the Xine engine will be default. (Recommended)
If you require the RealPlayer engine (or the Xine engine will not work), first install Realplayer and make the following changes:
Settings > Configure Amarok... > Engine
Make the following changes: Sound System: Helix Engine (hit Apply, then the following edits:) Helix/Realplay core directory: /usr/local/RealPlayer/common Helix/Realplay plugins directory: /usr/local/RealPlayer/plugins Helix/Realplay codecs directory: /usr/local/RealPlayer/codecs ---- Output plugin: alsa
NOTE: Fedora 8 users, please read the Fedora 8 Guide.
You have to make the RPM using the above site. For convenience I have created the RPM (please do not link directly to this file):
[mirandam@charon ~]$ sudo rpm -ivh msttcorefonts-2.0-1.noarch.rpm [mirandam@charon ~]$ sudo /etc/init.d/xfs restart
Restarting xfs may not be necessary. Many programs need only to be restarted. Some older applications, may require you to log out of Gnome or KDE and log back in (reboot NOT required).
Information regarding services and their functions can be found on: Services in Fedora Core 6 (http://www.mjmwired.net/resources/mjm-services-fc6.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).
The Macromedia(Adobe) Flash plugin is can be installed either from Adobe's website or the Macromedia Flash Linux repository (recommended). Please note the plugin will not work directly on 64-bit browsers without some re-configuration.
For yum users:
Install the macromedia.repo file to your repositories, and install through yum:
[mirandam@charon downloads]$ wget http://macromedia.mplug.org/macromedia-i386.repo [mirandam@charon downloads]$ sudo cp macromedia-i386.repo /etc/yum.repos.d/ [mirandam@charon downloads]$ sudo rpm --import http://macromedia.mplug.org/FEDORA-GPG-KEY [mirandam@charon downloads]$ sudo yum install flash-plugin
For manual installation (users without yum):
Go to http://macromedia.mplug.org/ and pick a mirror (USA, Europe). The current version is:
Current Version: 220.127.116.11 (01/17/2007)
RPM Version: 18.104.22.168-1 (01/17/2007)
Fedora Core flash-plugin (apt, yum rpm)
and save the RPM file to disk: flash-plugin-22.214.171.124-release.i386.rpm.
[mirandam@charon downloads]$ sudo rpm -ivh flash-plugin-126.96.36.199-release.i386.rpm
NOTE: The Flash 9 Release Notes state that only GTK2 based Mozilla browsers (Firefox, Mozilla, Seamonkey) are supported and that other browsers may have stability issues.
NOTE: The following instructions have been switched back to Java 1.5 as version 1.6 has been troublesome. Users who wish to use 1.6 can read Fedora 7 - Java.
NOTE: These instructions are for using Sun Java for the web browser and using Java dependant applications. This is not meant for developers. The official recommendation from Fedora can be found on http://www.fedoraproject.org/wiki/JavaFAQ. However the following instructions are simple for non-developers or users who don't use yum.
NOTE: Fedora Core advises AGAINST using the Sun Java RPM. If you do not use yum or do not have any Fedora/GNU java installed this will not affect you. If you are using yum and installed the RPM it is recommended to remove it:
[mirandam@charon ~]$ rpm -q jre jre-1.5.0_09-fcs [mirandam@charon ~]$ sudo rpm -e jre
Download the Java package from:
Select: Java Runtime Environment (JRE) 5.0 Update 12
On the next page, accept the license agreement, and make sure to select:
Linux self-extracting file jre-1_5_0_12-linux-i586.bin 16.34 MB
[mirandam@charon downloads]$ sh jre-1_5_0_12-linux-i586.bin (type 'yes') [mirandam@charon downloads]$ sudo mv -f jre1.5* /opt/jre1.5 [mirandam@charon downloads]$ sudo ln -s /opt/jre1.5/plugin/i386/ns7/libjavaplugin_oji.so /usr/lib/mozilla/plugins/libjavaplugin_oji.so
To update: If you update the JRE package, simply delete the /opt/jre1.5 directory and copy the newer download to /opt/jre1.5 -- No need to run the 'ln -s' command.---
Controlling Java through 'alternatives'. When running the java command, Fedora will automatically pick the GNU Java, to use Sun's java do the following:
[mirandam@charon ~]$ sudo /usr/sbin/alternatives --install /usr/bin/java java /opt/jre1.5/bin/java 2 [mirandam@charon ~]$ echo 2 | sudo /usr/sbin/alternatives --config java example: [mirandam@charon ~]$ java -version java version "1.5.0_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing)
To view PDF files, Fedora includes evince, however this application is very basic and may not work will all PDF's.
Download Acrobat from: http://www.adobe.com/products/acrobat/readstep2_allversions.html
Operating system: Unix/Linux
Version: Linux (.rpm)
The current version of Adobe Acrobat is 7.0.9 and download size is between 42-60MB depending on your language. (Not all languages are supported under Linux).
[mirandam@charon downloads]$ sudo rpm -ivh AdobeReader_enu-7.0.9-1.i386.rpm
NOTE: There is a problem with v7.0.9 (and v7.0.8) that will prevent Acrobat from working in FC6.
To fix, edit as root:
[mirandam@charon ~]$ sudo gedit /usr/local/Adobe/Acrobat7.0/bin/acroread
Make the following changes:
Line ~418: From: echo $mfile| sed 's/libgtk-x11-\([0-9]*\).0.so.0.\([0-9]\)00.\([0-9]*\)\|\(.*\)/\1\2\3/g' To: echo $mfile| sed 's/libgtk-x11-\([0-9]*\).0.so.0.\([0-9]*\)00.\([0-9]*\)\|\(.*\)/\1\2\3/g' Line ~643: From: MIN_GTK_VERSION="240" To: MIN_GTK_VERSION="2040"
More information: http://www.adobeforums.com/cgi-bin/webx/.3bc14512
Patch: As proposed on the fedora-list there is a quick solution with this: acroread.patch. This should do the same steps as above. Warning: This patch is only known to work for versions 7.0.8 and 7.0.9.
[mirandam@charon ~]$ wget -O /tmp/acroread.patch http://www.mjmwired.net/resources/files/acroread.patch [mirandam@charon ~]$ cd /usr/local/Adobe/Acrobat7.0/bin [mirandam@charon bin]$ sudo cp acroread acroread.orig [mirandam@charon bin]$ sudo patch < /tmp/acroread.patch
Acrobat Browser Plugin
The browser plugin is NOT automatically installed. This is optional. To install it:
[mirandam@charon downloads]$ sudo ln -s /usr/local/Adobe/Acrobat7.0/Browser/intellinux/nppdf.so /usr/lib/mozilla/plugins/nppdf.so
If you have other Windows computers on your Lan and want to share files 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.
1. Install Samba
It is best to have Samba installed in the installation process. If not yum users can install using: Add/Remove Software > Servers > Windows File Server. Users without yum can install the following packages from their CD's (or download): samba, samba-common, 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)
[mirandam@charon ~]$ 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.
If home data (all personal files under /home/username) is to be accessible, then set 'browseable = yes' under [homes] (~line 166). 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.
[mirandam@charon ~]$ sudo smbpasswd -a username New SMB password: Retype new SMB password: account_policy_get: (warnings ignore) Added user username.
(Note: 'username' must be a valid account on the machine)
4. Start Samba Service
Run samba and check for any errors:
[mirandam@charon ~]$ sudo /etc/init.d/smb start Starting SMB services: [ OK ] Starting NMB 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.
[mirandam@charon ~]$ /sbin/chkconfig --list smb smb 0:off 1:off 2:off 3:off 4:off 5:off 6:off [mirandam@charon ~]$ sudo /sbin/chkconfig --level 35 smb on [mirandam@charon ~]$ /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'
[mirandam@charon ~]$ sudo /etc/init.d/smb restart Shutting down SMB services: [ OK ] Shutting down NMB services: [ OK ] Starting SMB services: [ OK ] Starting NMB services: [ OK ]
Firewall and SELinux Users
To allow Samba access to work through your firewall you must set 'Samba' as a 'Trusted service'.
Modify SELinux Policy > Samba Disable SELinux protection for smbd daemon
On the command line you can run:
[root@charon ~]# setsebool -P smbd_disable_trans 1
Run man samba_selinux for more help.
For any changes made above to the SELinux settings or smb.conf, it is recommended to restart Samba.
Windows uses a different filesystem (NTFS) to store files. In order for Fedora to read that filesystem, you require NTFS support in your kernel. You can either recompile your kernel for NTFS read support -OR- obtain the proper kernel module.
NOTE: For users who upgraded from FC5 please first read the known bugs and problems.
To setup NTFS access you must (1) install NTFS support, (2) check how many partitions you have, (3) create mount points, (4) mount partitions, and (5) update fstab to mount at next boot.
NOTE: Previously Livna was recommended. However that solution has been known to be problematic in that it may update your kernel, which is normal behaviour. It is recommended to use NTFS-3G instead as it is supported in Fedora Extras and does NOT require kernel updates/upgrades. NTFS-3G also provides safe read-write access. (However SELinux may cause some problems for NTFS-3G.)
1. Install NTFS Support
For yum users:
[mirandam@charon ~]$ sudo yum install fuse fuse-libs ntfs-3g ntfsprogs ntfsprogs-gnomevfs
Users without yum, download fuse, fuse-lib and ntfs-3g (ntfsprogs and ntfsprogs-gnomevfs are optional) from Fedora Extras. Save them to a separate directory (ntfs). They are less than 1MB download.
[mirandam@charon downloads]$ cd ntfs [mirandam@charon ntfs]$ sudo rpm -ivh fuse* ntfs*
No kernel version checking is required, so long as you are using a FC6 kernel.
2. Check Your Partitions
Use fdisk to list partitions. Most ATA hard drives will be /dev/hda. Drives may also show up as /dev/hdb, /dev/sda depending on your configuration.
[mirandam@charon ~]$ sudo /sbin/fdisk -lu /dev/hda | grep NTFS /dev/hda1 * 63 33559784 16779861 7 HPFS/NTFS /dev/hda2 33559785 67119569 16779892+ 7 HPFS/NTFS /dev/hda3 67119570 100679354 16779892+ 7 HPFS/NTFS
Usually the first will be a drive "letter": C drive, next D, etc. Hence /dev/hda1 is my C:\ drive used by Windows.
3. Create Mount Points
For every partition in step 2 that you wish to access, you will need a "mount point". A mount point is just a directory. Common directories are: /media/ and /mnt/. Use whichever, but be consistent.
[mirandam@charon ~]$ cd /media/ [mirandam@charon media]$ sudo mkdir c_drive d_drive e_drive
You do not have to use these names, if you prefer to create folders such as movies, documents, or winxp, any name will work (without spaces).
4. Mount Partitions
Using NTFS-3G, we can mount the NTFS partition read-write, however it is recommended for novices as read-only. The following mounts and sets the permissions so all users can read the contents of each partition.
[mirandam@charon ~]$ sudo mount /dev/hda1 /media/c_drive -t ntfs-3g -r -o umask=0222 [mirandam@charon ~]$ sudo mount /dev/hda2 /media/d_drive -t ntfs-3g -r -o umask=0222 [mirandam@charon ~]$ sudo mount /dev/hda3 /media/e_drive -t ntfs-3g -r -o umask=0222
Read/Write Access: The above is for read-only access. In order to mount read/write, you must use the -rw -o umask=0000. Example:
[mirandam@charon ~]$ sudo mount /dev/hda1 /media/c_drive -t ntfs-3g -rw -o umask=0000
HIGHLY RECOMMENDED: Please run
5. Update /etc/fstab
Every time Fedora boots, the partitions must be mounted. To automatically mount, you must edit /etc/fstab.
Open /etc/fstab in an editor: (use nano instead of gedit if you do not have a GUI)
[mirandam@charon ~]$ sudo gedit /etc/fstab
Add these lines to the END of the file:
/dev/hda1 /media/c_drive ntfs-3g ro,defaults,umask=0222 0 0 /dev/hda2 /media/d_drive ntfs-3g ro,defaults,umask=0222 0 0 /dev/hda3 /media/e_drive ntfs-3g ro,defaults,umask=0222 0 0
Read/Write Access: The above is for read-only access. In order to mount read/write, you must use the rw,defaults,umask=0000. Example:
/dev/hda1 /media/c_drive ntfs-3g rw,defaults,umask=0000 0 0
NOTE: SELinux Problems
Users of SELinux will fix Fedora blocks the automounting of ntfs partitions when using NTFS-3G. This is a Fedora/SELinux bug, not NTFS-3G. Some support can be found on the NTFS-3G support page.. However for now users can mount everything when they log in by running:
[mirandam@charon ~]$ sudo mount -a
NOTE for FAT32 users
If you have FAT32 or FAT16 partitions, instead of ntfs-3g above you can use vfat to mount your partitions. No extra modules or downloads are required, this is built into the kernel. Just replace vfat for every place we have ntfs-3g when mounting and when editting /etc/fstab.
FAT32/FAT16 read and write is supported. If you wish to mount read/write,
then use: '-rw' for Step 4. Mounting Partitions, and
NOTE for Livna NTFS Modules
The Livna NTFS modules are read-only access. I do not recommend using them due to the kernel dependancy. If you require them or NTFS-3G will not work then first setup the Livna repository. Then you can install them:
[mirandam@charon ~]$ sudo yum install kmod-ntfs
For all the above changes you should use ntfs instead of ntfs-3g.
NOTE: If there is a real problem which is solved by disabling IPv6, then that is not normal -- that means there is a bug either in Fedora or (more likely these days) a problem with the local network (or nameservers) which should be reported and fixed. If there's a real problem you should report the problem in Redhat bugzilla or to your ISP/network admin.
FC6 has the most IPv6 support than in previous releases. Most likely you do not use IPv6. If you wish to eliminate the slight extra resources consumed by enabling IPv6, then you may do the following steps.
This may speed up your DNS lookup times when using the internet.
Disable IPv6 Networking Support
Edit /etc/sysconfig/network. (A reboot will be required)
[mirandam@charon ~]$ sudo gedit /etc/sysconfig/network Change: NETWORKING_IPV6=yes To: NETWORKING_IPV6=no
Disable IPv6 Protocol Stack for Kernel
[mirandam@charon ~]$ sudo gedit /etc/modprobe.conf
Add the following 2 lines: (A reboot will be required)
alias net-pf-10 off alias ipv6 off
Disable IPv6 Firewall
Stop ipv6 firewall:
[mirandam@charon ~]$ sudo /etc/init.d/ip6tables stop Flushing firewall rules: [ OK ] Setting chains to policy ACCEPT: filter [ OK ] Unloading ip6tables modules: [ OK ]
Turn ipv6 firewall off during future usage:
[mirandam@charon ~]$ sudo /sbin/chkconfig --level 35 ip6tables off
Issue with localhost
In /etc/hosts, the following entry for localhost using IPv6 can be removed:
::1 localhost.localdomain localhost
If you choose to remove the above IPv6 entry, then you must keep the following IPv4 entry for localhost:
127.0.0.1 localhost.localdomain localhost
Some applications may have problems with this (Gnome).
This package provides kernel headers and makefiles sufficient to build modules against the kernel package. The kernel headers are necessary if you require to install a driver (for example: Nvidia, ndiswrapper, Cisco VPN, etc.). If a driver requires kernel sources, it may be sufficient to install only the kernel headers.
The kernel headers The Kernel Headers are available through the kernel-devel RPM. This may or may not be installed by Fedora. This package can be installed from your FC6 CD's, DVD's or online through FTP or yum.
Look on online online and make sure you match your system, using the uname command. For example:
[mirandam@charon ~]$ uname -rm 2.6.18-1.2747.fc6 i686 Select: kernel-devel-2.6.18-1.2747.fc6.i686.rpm
If you have updated your kernel (using yum), then it is recommended you use yum to install the package:
[mirandam@charon ~]$ sudo yum install kernel-devel
Installing the kernel source is typically NOT needed unless you wish to re-compile your kernel or for some special development. However in some cases the kernel headers may be required.
There are 3 basic steps involved in installing the kernel source.
NOTE: Following these steps will consume at least ~500MB of disk space!
1. Download the Kernel Source
Obtaining Kernel Source (for default FC6 kernel)
The default kernel source can be found through any Fedora mirror. Look in the directory "/SRPMS/" under the "/6/" directory . For example: http://download.fedora.redhat.com/pub/fedora/linux/core/6/source/SRPMS/.
kernel-2.6.18-1.2798.fc6.src.rpm 16-Oct-2006 22:26 44M
Obtaining Kernel Source (for updated FC6 kernel)
If you updated your kernel, then the typically the last 2 or 3 releases of the source of the kernel will be available though the Fedora updates. IF YOU REQUIRE you can (try to) match the kernel source with your running kernel.
Look in the update directory on most Fedora mirror sites. For example: http://download.fedora.redhat.com/pub/fedora/linux/core/updates/6/SRPMS/.
Obtaining Kernel Source through 'yum' (for latest FC6 kernel)
There are yum utilities which will download the LATEST kernel source. If it does not find anything, then there are no updates (yet) use the DEFAULT Fedora kernel source.
[mirandam@charon ~]$ sudo yum install yum-utils [mirandam@charon ~]$ cd downloads [mirandam@charon downloads]$ yumdownloader --source kernel --enablerepo updates-source
2. Install the Kernel Source
Install the kernel.src.rpm that you chose to download in the previous steps.
[mirandam@charon downloads]$ sudo rpm -ivh kernel-2.6.18-1.2798.fc6.src.rpm 1:kernel ########################################### [100%]
Ignore, group does not exist or user does not exist errors.
3. Prepare the Source
[mirandam@charon downloads]$ sudo rpmbuild -bp --target=$(uname -m) /usr/src/redhat/SPECS/kernel-2.6.spec
The source files will be properly located in /usr/src/redhat/BUILD/kernel-2.6.18/. There are 2 useful directories:
NOTE: Users of x86_64 architecture may experience the following error:
error: Failed build dependencies: unifdef is needed by kernel-2.6.18-1.2798.x86_64
To fix, run sudo yum install unifdef.
Help Out: If you found this guide or any Resource helpful, please consider supporting this site by recommending this page to others or linking to this page. I appreciate all the support I receive. Thank you in advance.
Disclaimer: The author makes no claim to the accuracy of the information provided. This information is provided in the hope that it will be useful, but WITHOUT ANY WARRANTY. There is no implied support from referencing this guide. Any help that is provided is at will. Use this information at your own risk. Always make proper backups and use caution when modifying critical system files.
PLEASE DO NOT mirror, translate or duplicate this page without contacting me.
Copyright © 2003-2013 by Mauriat Miranda (mjmwired.net).