LQWiki - User contributions [en]

User:Geniarse

2007-02-20T14:52:14Z

Geniarse:

==My Links==
[[Special:Wantedpages]] 
[http://wiki.linuxquestions.org/wiki.phtml?title=Special:Popularpages&limit=100000&offset=0 All Articles]

Distcc

2006-01-11T14:17:13Z

Geniarse: line break

'''Distcc''' is a program designed to distribute compiling tasks of [[C]], [[C plus plus|C++]], [[Objective-C]], or Objective C++ code across a network to participating hosts. It is comprised of a server (distccd) and a client program (distcc).



30-second installation instructions:

#Install distcc on each machine that you wish to share compiling between.
#On each of the servers, <code>distccd --daemon</code> Using the option ''--allow'' option to restrict access to specific ip addresses.
#Put the names or ip address of the distcc servers environment variable ''DISTCC_HOSTS'': <code>export DISTCC_HOSTS='localhost red green blue'</code>
#Begin compiling on the "main" machine <code>CC=distcc ./configure make -j''x''</code> where ''x'' is twice the number of servers running distcc.

==Internal Links==
*[[Gentoo and distcc]]

==External links==

*[http://distcc.samba.org/ distcc homepage]
*[http://www.linuxquestions.org/linux/answers/Jeremys_Magazine_Articles/Faster_and_Faster_Compilation Linux Magazine article]

Gentoo and distcc

2006-01-09T23:07:22Z

Geniarse:

[[Gentoo]] can take advantage of [[distcc]] to speed up [[compilation]] of packages by sharing compilation accross many machines also running distcc.

==Installation of distcc==
Start by installing distcc using the command 
<code>emerge -av distcc</code>

==Editing /etc/make.conf==
Add distcc to the ''FEATURES'' flag in /etc/make.conf, for example: 
<code>FEATURES="distcc"</code>

Also the ''MAKEOPTS'' setting should be tweaked, for example: 
<code>MAKEOPTS="-jX"</code>

Where ''X'' is typically twice the number of [[CPU]]s, hence twice the number of machines you plan to run distcc on unless you are using machines with more than one CPU. (NOTE: leave anyother options present in ''MAKEOPTS'')

==Adding distcc hosts==
To add the distcc servers to the list of machines participating in the build: 
<code>distcc-config --add-hosts "foo"</code>

foo can be a list of ip addresses and/or hostnames which are running distcc. Also if the machine your running is to participate in the build then add ''localhost'' to the list of machines.

==Security==
You should edit the file ''/etc/conf.d/distcc'' to only allow the configured distcc servers for security reasons.

==Starting distcc==
Add distcc to the default runlevel on each gentoo machine so when you boot the service is available: 
<code>rc-update add distccd default</code>
and start with the command: 
<code>/etc/init.d/distccd start</code>

==See Also==
*[[Distcc]]
*[[Gentoo]]

Gentoo tips & tricks

2006-01-09T23:07:00Z

Geniarse: gentoo and distcc link

This is a collection of '''tips & tricks''' for the peculiarities of [[Gentoo]].

== Use flags ==
[[USE flags]] are the way Gentoo organizes the compile time options. You can list them in your make.conf (See external links below)

===Tools===
ufed = use flag editor, emerge ufed, then run ufed as root

A problem with ufed, is that it organizes your useflags alphabetically, So if you added an experimental one by hand in your make.conf, it will be hidden amongst your countless others.

=== Files ===
/etc/make.conf has a use flag section in it.

===Rebuilding what needs to be rebuilt ===
emerge -pev world | grep 'gtk' | awk '{print "=" $4}'

(rac's line)
swap gtk for the useflag of you choice

== Masked packages ==
A lot of times you'll want to emerge a masked package (or a masked version of one). One short way to do this is <code>ACCEPT_KEYWORDS="~x86" emerge package</code> (replace x86 with your architecture). A slightly shorter way is to create a file called <code>/usr/sbin/expmerge</code>, with the following contents:
<pre>#!/bin/sh
ACCEPT_KEYWORDS="~x86" emerge $*</pre>
Then just <code>expmerge package</code>.
Mixing unstable with stable packages can lead to problems, so it's recommended you pick one type and use it all the time. This is more important for libraries rather then programs.

NOTE: the aforementioned method of emerging masked packages is deprecated and unsupported. please use /etc/portage/ (man portage, man emerge) This is used by:
<pre>echo "package-category/package-name" >> /etc/portage/package.keywords</pre>

== Emerge tips ==
*emerge world -uDp, -- list things to be updated 
*emerge world -uD -- get almost everything updated 
*revdep-rebuild -- check for packages that break by rebuilding a dependancy

==Gentoo & KDE==
Remember - when installing [[KDE]] on Gentoo, you don't have to install every kde package. Instead, you can simply choose to install a "small" subset of them - ''for example'':

<pre># emerge kdebase kdeartwork</pre>

Prior to this, if you want to check out what packages would be installed, use the --pretend option - ''for example'':

<pre># emerge --pretend kdebase kdeartwork | less</pre>

(As a useful alternative to --pretend, you could use the --ask option - see ''man emerge'' for more information).

N.B - As of KDE 3.4 onwards, you will be able to utilise ''split ebuilds'' - this approach enables you to install individual KDE applications, without a plethora of other KDE apps automatically being installed (as in the monolithic approach).

==See also==
*[[Common tasks]]
*[[Distribution specific tips and tricks]]
*[[Gentoo and distcc]]

== External links==
* [http://forums.gentoo.org/viewtopic.php?t=157851 A sorted list of useflags for make.conf].

== Internal links==
*[[Installing Slackware and Gentoo]]

Gentoo

2006-01-09T23:05:57Z

Geniarse: add distcc link

'''Gentoo''' is a special flavor of [[Linux]] that can be automatically optimized and customized for just about any application or need. Extreme performance, configurability, and a top-notch user and developer community are all hallmarks of the Gentoo experience. 'The word ''"gentoo"'' is the name for a species of penguins [http://ourworld.compuserve.com/homepages/Peter_and_Barbara_Barham/gentoo.htm].'

Thanks to a technology called [[Portage]], Gentoo Linux can become an ideal secure server, development workstation, professional desktop, gaming system, embedded solution or whatever you need it to be. Because of its near-unlimited adaptability, Gentoo Linux is called a [[metadistribution]].

Portage is the heart of Gentoo Linux, and performs many key functions. Your local Portage tree contains a complete collection of scripts that can be used by Portage to compile and install the latest Gentoo packages. Currently, there are over 6000 packages in the Portage tree, with new ones being added all the time. Installing a new application is as easy as:

:<tt># [[emerge]] packagename</tt>

The application will then be downloaded and automatically [[Compilation_From_Source|compiled from source]], with compile-time options selected according to preferences you set during installation in your [[make.conf]] file, (i.e. with or without support for [[X]], [[PNG]]s, [[JPEG]]s, [[Gnome]], etc). N.B - Portage will automatically cater for any dependencies when installing software.

[[Daniel Robbins]] is Gentoo's chief architect. You can read his philosophy of Gentoo Linux [http://www.gentoo.org/main/en/philosophy.xml here].

== Gentoo help resources ==
If you are looking for help on Gentoo Linux, the Gentoo forums[http://forums.gentoo.org] are an excellent resource and are full of both friendly and knowledgeable people. The IRC room at irc.freenode.net called #gentoo is also a place to find community around Gentoo. Before checking either of those, visit the Gentoo documentation site[http://www.gentoo.org/doc], where many high-quality documents have been published on common and not-so-common issues.

== Break my gentoo ==
Even though Gentoo is a bleeding edge distro, there are some packages that are not installable immediately. Check out http://www.breakmygentoo.net/ for all the latest portage files to install the latest software.

== Gentoo server project wiki ==
The Gentoo Server Project Wiki is located at http://www.subverted.net/wakka. The Gentoo Server Project has [[mission-critical reliability]] as it's goal, but mostly serves as glue for the official Gentoo documentation.
Includes [[case studies]] and articles.

==Installing Masked Packages==
Some packages in the portage tree are "masked" i.e. marked as unstable, and cannot be installed on a default system. To emerge a masked package (or a masked version of one) prefix the emerge command as follows <code>ACCEPT_KEYWORDS="~x86" emerge package</code> (replace x86 with your architecture). A slightly shorter way is to create a script called <code>/usr/sbin/expmerge</code>, with the following contents:
<pre>#!/bin/sh
ACCEPT_KEYWORDS="~x86" emerge $*</pre>
Then after marking as executable (<code>chown root:root /usr/sbin/expmerge && chmod ug+wrx /usr/sbin/expmerge</code>) just <code>expmerge package</code>.
Mixing unstable with stable packages can lead to problems, so it's recommended you pick one type and use it all the time. This is more important for libraries rather then programs. To use masked packages for the entire system add to /etc/make.conf: 
 <code>ACCEPT_KEYOWORDS="~x86"</code> 
 
Another technique is to create the file /etc/portage/package.keywords and add the packages that you want to always use the unstable version, for example: 
 
<code>media-video/nvidia-kernel ~x86
media-video/nvidia-glx ~x86
x11-base/opengl-update ~x86
media-sound/beep-media-player ~x86
x11-misc/transset ~x86</code>
Then when you upgrade these packages will remain ~x86 

==See also==
*[[Gentoo tips & tricks]]
*[http://www.gentoo.org/doc/en/hpc-howto.xml Gentoo High Performance]
*[http://www.gentoo.org/doc/en/list.xml Gentoo Docs]

==External links==
*[http://www.gentoo.org/ Gentoo homepage]
*[http://forums.gentoo.org/ Forums]
*[http://gentoo-portage.com Gentoo-Portage Package DB]
*[http://gentoo-wiki.com Gentoo Wiki]
*[http://breakmygentoo.net BreakMyGentoo]
*[http://distrocenter.linux.com/article.pl?sid=04/09/10/2148249&tid=108&tid=104 Gentoo 2004.2 review]
*[http://planet.gentoo.org/ Planet Gentoo]

==Internal links==
*[[Installing Slackware and Gentoo]]
*[[Gentoo and distcc]]

==Logo==
http://www.gentoo.org/images/powered-small.png

Gentoo and distcc

2006-01-09T23:05:18Z

Geniarse: some formatting

Gentoo and distcc

2006-01-09T23:04:15Z

Geniarse:

[[Gentoo]] can take advantage of [[distcc]] to speed up [[compilation]] of packages by sharing compilation accross many machines also running distcc.

==Installation of distcc==
Start by installing distcc using the command
<code>emerge -av distcc</code>

==Editing /etc/make.conf==
Add distcc to the ''FEATURES'' flag in /etc/make.conf, for example:
<code>FEATURES="distcc"</code>

Also the ''MAKEOPTS'' setting should be tweaked, for example:
<code>MAKEOPTS="-jX"</code>

Where ''X'' is typically twice the number of [[CPU]]s, hence twice the number of machines you plan to run distcc on unless you are using machines with more than one CPU. (NOTE: leave anyother options present in ''MAKEOPTS'')

==Adding distcc hosts==
To add the distcc servers to the list of machines participating in the build:
<code>distcc-config --add-hosts "foo"</code>

foo can be a list of ip addresses and/or hostnames which are running distcc. Also if the machine your running is to participate in the build then add ''localhost'' to the list of machines.

==Security==
You should edit the file ''/etc/conf.d/distcc'' to only allow the configured distcc servers for security reasons.

==Starting distcc==
Add distcc to the default runlevel on each gentoo machine so when you boot the service is available:
<code>rc-update add distccd default</code>
and start with the command:
<code>/etc/init.d/distccd start</code>

==Internal links==
*[[Distcc]]
*[[Gentoo]]

Distcc

2006-01-09T22:45:33Z

Geniarse: reformatted and altered a few things

'''Distcc''' is a program designed to distribute compiling tasks of [[C]], [[C plus plus|C++]], [[Objective-C]], or Objective C++ code across a network to participating hosts. It is comprised of a server (distccd) and a client program (distcc).



30-second installation instructions:

#Install distcc on each machine that you wish to share compiling between.
#On each of the servers, <code>distccd --daemon</code> Using the option ''--allow'' option to restrict access to specific ip addresses.
#Put the names or ip address of the distcc servers environment variable ''DISTCC_HOSTS'': <code>export DISTCC_HOSTS='localhost red green blue'</code>
#Begin compiling on the "main" machine <code>CC=distcc ./configure make -j''x''</code> where ''x'' is twice the number of servers running distcc.

==Internal Links==
*[[Gentoo and distcc]]

==External links==

*[http://distcc.samba.org/ distcc homepage]

User:Geniarse

2006-01-09T22:33:58Z

Geniarse:

Contact me: [mailto:tom.conneely@gmail.com tom.conneely@gmail.com]

I'm a student of physics in the UK and have long followed LINUX learning most things along the way by using the OS rather than reading up on it before beginning , finding things out as I needed to(perhaps not the best way to do things but it means simple tasks are full of suprises and many reinstallations). Now I am familiar with most aspects of Linux after tweaking and settling on Gentoo as my chosen distro (after trying mandrake, suse, slackware and debian). My main area of expertise computing wise is networking (particularly infrastructure e.g. routing and switching) due to my Cisco networking qualification.

==My Links==
[[Special:Wantedpages]] 
[http://wiki.linuxquestions.org/wiki.phtml?title=Special:Popularpages&limit=100000&offset=0 All Articles]

NVIDIA graphics drivers

2006-01-05T14:09:01Z

Geniarse: /* Gentoo */ corrected eselect mistake

This is a guide on how to install [[NVIDIA]]'s drivers for X-windows, the graphical user interface system on Linux. These drivers are not required, but if you wish to run games such as Quake or Unreal at full speed you should install them. Before you start, take note that the drivers are distributed under a non-opensource license.

==Distribution specific==
=== Fedora Users ===
For [[Fedora]] users, the NVIDIA drivers are available repackaged in RPM, with pre-build kernel modules for easy install and update. Normally you can find the rpms in the [[livna]].org apt/yum respository, but the latest drivers (version 6106) are not yet avaliable as RPMs. See [http://fedorafaq.org/faq/ the Fedora FAQ] for more information on how to install on Fedora Core 2 anyway, or [http://rpm.livna.org/livna-switcher.html here] for more info on the livna nvidia packages.

Drivers before version 6106 will not work with prebuilt Fedora Core 2 kernels, because they do not support [[4stacks|4k Stacks]].

===Debian===
[[Debian]] has packages for these drivers. There are two packages that need to be installed.
One for the binary drivers and libraries and one for the [[kernel module]]. 
For Debian 3.1 (Sarge) and higher they are called <tt>nvidia-glx</tt> and <tt>nvidia-kernel-<version></tt> (both are in the non-free section). Where <version> is one matching your used Debian kernel or <tt>source</tt> to build the module for your specific kernel. See the README.Debian file that comes with them for full instructions. And use the package [[module-assistant]] to help compile the kernel module if you don't have a default Debian kernel. After installing these packages, the X server configuration file needs to be changed, seen the section about that below.

The other optional packages are <tt>nvidia-glx-dev</tt> for when you need to compile an openGL applicating against the nvidia openGL libs and <tt>nvidia-settings</tt> for a [[GUI]] application to configure the various driver options.

In Debian 3.0 (Woody) these packages are called <tt>nvidia-glx-src</tt> and <tt>nvidia-kernel-src</tt> (both are in the contrib section and use [[wget]] to download the actual drivers). 

===SuSE===
For [[SuSE]] users, the NVIDIA drivers are available from [http://www.nvidia.com/object/linux.html NVIDIA], the installation HOWTO is available from [ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/nvidia-installer-HOWTO here].
Follow the steps described in the HOWTO. If Hardware 3D - acceleration fails but X11 in 2D mode is using the new nvidia driver do the following: install the driver again, the second time don't use the program <tt>sax2</tt> but run the command <tt>switch2nvidia</tt>

===Gentoo===
[[Gentoo]] has ebuilds available which can be installed with: 
 <tt> emerge nvidia-kernel nvidia-glx</tt> 
 
The first ebuild "nvidia-kernel" provides Nvidia's driver for their various cards and nvidia-glx provides 3D acceleration (this is optional). To switch to the nvidia [[openGL]] implementation run: 
 <tt> eselect opengl set nvidia </tt> 
 
You have to edit your X11 config file manually using the procedure described [[#Editing the X11 configuration|below]] (note: [[gentoo]] uses [[X.org]]).

===Mandrake/Mandriva===
[[Mandriva]] has Nvidia RPMs available for PowerPack users (ie. those who bought a boxed set or are club members). If you have a PowerPack the drivers will install automatically when you install the OS.

For everyone else the manual procedure is:

1) If you haven't already done so go to http://easyurpmi.zarb.org and setup access to the software repositories for your version.

2) In the Software section in the Mandrake Control Centre, or using the urpmi command as root, install the packages "kernel-source-2.6" ("kernel-source" for versions 9.2 or below) and "gcc" (without quotes).

3) Make sure you have the latest kernel - the kernel package isn't updated automatically but the kernel-source package is, which could lead to a version mismatch. To do this run (from a terminal window):
<tt><code><pre>
su
urpmi.update -a
urpmi kernel
</pre></code></tt>
If it lists a whole lot of different kernels most users can just select number 1 in the list. Otherwise run <tt><code><pre>rpm -qa | grep kernel</pre></code></tt> to see which kernel package you have installed. For more information see http://www.mandriva.com/en/security/kernelupdate

Now follow the rest of the instructions below under "Manual Installation" from "Install" onwards.

==Manual installation==
=== Download ===
The first step is to download some needed files. First, grab the latest version of the drivers from the [http://nvidia.com/content/drivers/drivers.asp NVIDIA Website]. Once you have that downloaded, make sure you have the source for your kernel. You can check what kernel you have by running the command '[[uname]] -r', without the quotes.

=== Install ===
First of all, you need to shut down X. Yes, that's right, we're going to be working from a command line. To do this:

1) Press Ctrl+alt+F1 on the keyboard. Now you should be at a console login screen, login as root.

2) Type the command 'telinit 3' (no quotes) to put your machine into runlevel 3 (no graphical interface). It will tell you about some services its restarting, if it doesn't return you to the command prompt press enter. For more information on this, refer to [[run levels]].

Once you get X shut off, navigate (see [[Directory_Commands]]) to where ever you downloaded the driver file to, and run it. You can run it by typing ''sh filename''. It should check to make sure that it downloaded OK, then start up the installation program.

Go through the first screen, accept the license, and when it asks if you want to try and download a kernel interface from NVIDIA, say no. I've never seen anyone get the kernel interface form the site, so we'll save time and move onto the next screen, where it tells us it will compile the kernel interface on its own. This is where our kernel source comes into play. It should compile and install on its own, so go to the next screen. This should pretty much wrap up anything important in the installation.

=== Editing the X11 configuration ===
The next step is to edit your [[X11]] configuration file, so it loads the nvidia driver. For [[XFree86]] the file is usually found in /etc/X11/ and called [[XF86Config]], but you might also have XF86Config-4, in which case you should edit that instead. Many newer distributions use [[X.org]], which uses /etc/X11/Xorg.conf in place of /etc/X11/XF86Config.

Before we do that, we should back up the file, just in case something goes wrong.

# cp /etc/X11/XF86Config /etc/X11/XF86Config.backup

Then, open the X config file in vi (or whatever editor you prefer, be it [[pico]], [[nano]], [[emacs]] or [[joe]]) by running:

# vi /etc/X11/XF86Config

Look for the '''Module''' section, and make sure it includes the '''Load "glx"''' line. If it doesn't, add it in. Then remove the '''Load "dri"''' and '''Load "GLCore"''' lines, if you have them. If you might want to go back to the old drivers later you can comment out loading dri and GLCore instead of removing them completely by putting a hash at the start of the line. An example configuration:

<tt>
Section "Module"
Load "dbe" # Double buffer extension
Load "type1"
Load "speedo"
Load "freetype"
Load "glx"
<nowiki># Load "dri"</nowiki> 
<nowiki># Load "GLcore"</nowiki> 
EndSection
</tt>

Finally, find the Device setion, and change the line '''Driver "nv"''' or '''Driver"vesa"''' to '''Driver "nvidia"'''. An example device section:

<tt>
Section "Device"
Identifier "NVIDIA"
Driver "nvidia"
VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection
</tt>

To disable the NVidia splash-screen logo when starting X, add the option highlighted below:

<tt>
Section "Device"
Identifier "NVIDIA"
Driver "nvidia"
'''Option "nologo" "1"'''
VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection
</tt>

=== Start X ===
Now all that's left is to start X back up. To do this type the command 'telinit 5' at the console prompt and it should load X and take you to the normal graphical login screen. You should now have your brand-new NVIDIA drivers installed and working. Good job!

=== Uninstalling NVIDIA drivers ===
Did something in your installation go terribly, terrible wrong? No problem! Start your box up in console-only mode, navigate to where you have the nvidia driver installation file saved, and run it with the --uninstall option. ''sh filename.run --uninstall'', and it uninstalls everything it put in. Then it's a simple matter of restoring your XF86Config from the backup we made above.

== Issues ==
* One issue I've had is between the GeForce FX 5200 card and the Asus P4S8X-X motherboard. When you started the X server, it would display garbled text and then hang. This problem can be solved by going into the BIOS and setting your AGP speed down from 8x to 4x.

* Compiling NVIDIA 1.0-7676 on kernel 2.6.14 requires a small modification.
** First you need Module.symvers at the kernel sources dir so you must build the kernel.
** Then extract the driver sources with <tt>./NVIDIA-Linux-x86-1.0-7676-pkg1.run -x</tt>.
** Change line 533 of NVIDIA-Linux-x86-1.0-7676-pkg1/usr/src/nv/nv-linux.h to <tt># define NV_PCI_DEVICE_NAME(dev) pci_pretty_name(dev)</tt>
** After this install the driver with <tt>./NVIDIA-Linux-x86-1.0-7676-pkg1/nvidia-installer --kernel-source-path=...</tt>

==See Also==
* [[NVIDIA]]

Gentoo

2006-01-04T15:26:36Z

Geniarse: Created Installing masked packages section & added content

'''Gentoo''' is a special flavor of [[Linux]] that can be automatically optimized and customized for just about any application or need. Extreme performance, configurability, and a top-notch user and developer community are all hallmarks of the Gentoo experience. 'The word ''"gentoo"'' is the name for a species of penguins [http://ourworld.compuserve.com/homepages/Peter_and_Barbara_Barham/gentoo.htm].'

Thanks to a technology called [[Portage]], Gentoo Linux can become an ideal secure server, development workstation, professional desktop, gaming system, embedded solution or whatever you need it to be. Because of its near-unlimited adaptability, Gentoo Linux is called a [[metadistribution]].

Portage is the heart of Gentoo Linux, and performs many key functions. Your local Portage tree contains a complete collection of scripts that can be used by Portage to compile and install the latest Gentoo packages. Currently, there are over 6000 packages in the Portage tree, with new ones being added all the time. Installing a new application is as easy as:

:<tt># [[emerge]] packagename</tt>

The application will then be downloaded and automatically [[Compilation_From_Source|compiled from source]], with compile-time options selected according to preferences you set during installation in your [[make.conf]] file, (i.e. with or without support for [[X]], [[PNG]]s, [[JPEG]]s, [[Gnome]], etc). N.B - Portage will automatically cater for any dependencies when installing software.

[[Daniel Robbins]] is Gentoo's chief architect. You can read his philosophy of Gentoo Linux [http://www.gentoo.org/main/en/philosophy.xml here].

== Gentoo help resources ==
If you are looking for help on Gentoo Linux, the Gentoo forums[http://forums.gentoo.org] are an excellent resource and are full of both friendly and knowledgeable people. The IRC room at irc.freenode.net called #gentoo is also a place to find community around Gentoo. Before checking either of those, visit the Gentoo documentation site[http://www.gentoo.org/doc], where many high-quality documents have been published on common and not-so-common issues.

== Break my gentoo ==
Even though Gentoo is a bleeding edge distro, there are some packages that are not installable immediately. Check out http://www.breakmygentoo.net/ for all the latest portage files to install the latest software.

== Gentoo server project wiki ==
The Gentoo Server Project Wiki is located at http://www.subverted.net/wakka. The Gentoo Server Project has [[mission-critical reliability]] as it's goal, but mostly serves as glue for the official Gentoo documentation.
Includes [[case studies]] and articles.

==Installing Masked Packages==
Some packages in the portage tree are "masked" i.e. marked as unstable, and cannot be installed on a default system. To emerge a masked package (or a masked version of one) prefix the emerge command as follows <code>ACCEPT_KEYWORDS="~x86" emerge package</code> (replace x86 with your architecture). A slightly shorter way is to create a script called <code>/usr/sbin/expmerge</code>, with the following contents:
<pre>#!/bin/sh
ACCEPT_KEYWORDS="~x86" emerge $*</pre>
Then after marking as executable (<code>chown root:root /usr/sbin/expmerge && chmod ug+wrx /usr/sbin/expmerge</code>) just <code>expmerge package</code>.
Mixing unstable with stable packages can lead to problems, so it's recommended you pick one type and use it all the time. This is more important for libraries rather then programs. To use masked packages for the entire system add to /etc/make.conf: 
 <code>ACCEPT_KEYOWORDS="~x86"</code> 
 
Another technique is to create the file /etc/portage/package.keywords and add the packages that you want to always use the unstable version, for example: 
 
<code>media-video/nvidia-kernel ~x86
media-video/nvidia-glx ~x86
x11-base/opengl-update ~x86
media-sound/beep-media-player ~x86
x11-misc/transset ~x86</code>
Then when you upgrade these packages will remain ~x86 

==See also==
*[[Gentoo tips & tricks]]
*[http://www.gentoo.org/doc/en/hpc-howto.xml Gentoo High Performance]
*[http://www.gentoo.org/doc/en/list.xml Gentoo Docs]

==External links==
*[http://www.gentoo.org/ Gentoo homepage]
*[http://forums.gentoo.org/ Forums]
*[http://gentoo-portage.com Gentoo-Portage Package DB]
*[http://gentoo-wiki.com Gentoo Wiki]
*[http://breakmygentoo.net BreakMyGentoo]
*[http://distrocenter.linux.com/article.pl?sid=04/09/10/2148249&tid=108&tid=104 Gentoo 2004.2 review]
*[http://planet.gentoo.org/ Planet Gentoo]

==Internal links==
*[[Installing Slackware and Gentoo]]

==Logo==
http://www.gentoo.org/images/powered-small.png

NVIDIA graphics drivers

2006-01-04T15:05:26Z

Geniarse: oopsie

This is a guide on how to install [[NVIDIA]]'s drivers for X-windows, the graphical user interface system on Linux. These drivers are not required, but if you wish to run games such as Quake or Unreal at full speed you should install them. Before you start, take note that the drivers are distributed under a non-opensource license.

==Distribution specific==
=== Fedora Users ===
For [[Fedora]] users, the NVIDIA drivers are available repackaged in RPM, with pre-build kernel modules for easy install and update. Normally you can find the rpms in the [[livna]].org apt/yum respository, but the latest drivers (version 6106) are not yet avaliable as RPMs. See [http://fedorafaq.org/faq/ the Fedora FAQ] for more information on how to install on Fedora Core 2 anyway, or [http://rpm.livna.org/livna-switcher.html here] for more info on the livna nvidia packages.

Drivers before version 6106 will not work with prebuilt Fedora Core 2 kernels, because they do not support [[4stacks|4k Stacks]].

===Debian===
[[Debian]] has packages for these drivers. There are two packages that need to be installed.
One for the binary drivers and libraries and one for the [[kernel module]]. 
For Debian 3.1 (Sarge) and higher they are called <tt>nvidia-glx</tt> and <tt>nvidia-kernel-<version></tt> (both are in the non-free section). Where <version> is one matching your used Debian kernel or <tt>source</tt> to build the module for your specific kernel. See the README.Debian file that comes with them for full instructions. And use the package [[module-assistant]] to help compile the kernel module if you don't have a default Debian kernel. After installing these packages, the X server configuration file needs to be changed, seen the section about that below.

The other optional packages are <tt>nvidia-glx-dev</tt> for when you need to compile an openGL applicating against the nvidia openGL libs and <tt>nvidia-settings</tt> for a [[GUI]] application to configure the various driver options.

In Debian 3.0 (Woody) these packages are called <tt>nvidia-glx-src</tt> and <tt>nvidia-kernel-src</tt> (both are in the contrib section and use [[wget]] to download the actual drivers). 

===SuSE===
For [[SuSE]] users, the NVIDIA drivers are available from [http://www.nvidia.com/object/linux.html NVIDIA], the installation HOWTO is available from [ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/nvidia-installer-HOWTO here].
Follow the steps described in the HOWTO. If Hardware 3D - acceleration fails but X11 in 2D mode is using the new nvidia driver do the following: install the driver again, the second time don't use the program <tt>sax2</tt> but run the command <tt>switch2nvidia</tt>

===Gentoo===
[[Gentoo]] has ebuilds available which can be installed with: 
 <tt> emerge nvidia-kernel nvidia-glx</tt> 
 
The first ebuild "nvidia-kernel" provides Nvidia's driver for their various cards and nvidia-glx provides 3D acceleration (this is optional). To switch to the nvidia [[openGL]] implementation run: 
 <tt> eselect opengl nvidia </tt> 
 
You have to edit your X11 config file manually using the procedure described [[#Editing the X11 configuration|below]] (note: [[gentoo]] uses [[X.org]]).

===Mandrake/Mandriva===
[[Mandriva]] has Nvidia RPMs available for PowerPack users (ie. those who bought a boxed set or are club members). If you have a PowerPack the drivers will install automatically when you install the OS.

For everyone else the manual procedure is:

1) If you haven't already done so go to http://easyurpmi.zarb.org and setup access to the software repositories for your version.

2) In the Software section in the Mandrake Control Centre, or using the urpmi command as root, install the packages "kernel-source-2.6" ("kernel-source" for versions 9.2 or below) and "gcc" (without quotes).

3) Make sure you have the latest kernel - the kernel package isn't updated automatically but the kernel-source package is, which could lead to a version mismatch. To do this run (from a terminal window):
<tt><code><pre>
su
urpmi.update -a
urpmi kernel
</pre></code></tt>
If it lists a whole lot of different kernels most users can just select number 1 in the list. Otherwise run <tt><code><pre>rpm -qa | grep kernel</pre></code></tt> to see which kernel package you have installed. For more information see http://www.mandriva.com/en/security/kernelupdate

Now follow the rest of the instructions below under "Manual Installation" from "Install" onwards.

==Manual installation==
=== Download ===
The first step is to download some needed files. First, grab the latest version of the drivers from the [http://nvidia.com/content/drivers/drivers.asp NVIDIA Website]. Once you have that downloaded, make sure you have the source for your kernel. You can check what kernel you have by running the command '[[uname]] -r', without the quotes.

=== Install ===
First of all, you need to shut down X. Yes, that's right, we're going to be working from a command line. To do this:

1) Press Ctrl+alt+F1 on the keyboard. Now you should be at a console login screen, login as root.

2) Type the command 'telinit 3' (no quotes) to put your machine into runlevel 3 (no graphical interface). It will tell you about some services its restarting, if it doesn't return you to the command prompt press enter. For more information on this, refer to [[run levels]].

Once you get X shut off, navigate (see [[Directory_Commands]]) to where ever you downloaded the driver file to, and run it. You can run it by typing ''sh filename''. It should check to make sure that it downloaded OK, then start up the installation program.

Go through the first screen, accept the license, and when it asks if you want to try and download a kernel interface from NVIDIA, say no. I've never seen anyone get the kernel interface form the site, so we'll save time and move onto the next screen, where it tells us it will compile the kernel interface on its own. This is where our kernel source comes into play. It should compile and install on its own, so go to the next screen. This should pretty much wrap up anything important in the installation.

=== Editing the X11 configuration ===
The next step is to edit your [[X11]] configuration file, so it loads the nvidia driver. For [[XFree86]] the file is usually found in /etc/X11/ and called [[XF86Config]], but you might also have XF86Config-4, in which case you should edit that instead. Many newer distributions use [[X.org]], which uses /etc/X11/Xorg.conf in place of /etc/X11/XF86Config.

Before we do that, we should back up the file, just in case something goes wrong.

# cp /etc/X11/XF86Config /etc/X11/XF86Config.backup

Then, open the X config file in vi (or whatever editor you prefer, be it [[pico]], [[nano]], [[emacs]] or [[joe]]) by running:

# vi /etc/X11/XF86Config

Look for the '''Module''' section, and make sure it includes the '''Load "glx"''' line. If it doesn't, add it in. Then remove the '''Load "dri"''' and '''Load "GLCore"''' lines, if you have them. If you might want to go back to the old drivers later you can comment out loading dri and GLCore instead of removing them completely by putting a hash at the start of the line. An example configuration:

<tt>
Section "Module"
Load "dbe" # Double buffer extension
Load "type1"
Load "speedo"
Load "freetype"
Load "glx"
<nowiki># Load "dri"</nowiki> 
<nowiki># Load "GLcore"</nowiki> 
EndSection
</tt>

Finally, find the Device setion, and change the line '''Driver "nv"''' or '''Driver"vesa"''' to '''Driver "nvidia"'''. An example device section:

<tt>
Section "Device"
Identifier "NVIDIA"
Driver "nvidia"
VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection
</tt>

To disable the NVidia splash-screen logo when starting X, add the option highlighted below:

<tt>
Section "Device"
Identifier "NVIDIA"
Driver "nvidia"
'''Option "nologo" "1"'''
VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection
</tt>

=== Start X ===
Now all that's left is to start X back up. To do this type the command 'telinit 5' at the console prompt and it should load X and take you to the normal graphical login screen. You should now have your brand-new NVIDIA drivers installed and working. Good job!

=== Uninstalling NVIDIA drivers ===
Did something in your installation go terribly, terrible wrong? No problem! Start your box up in console-only mode, navigate to where you have the nvidia driver installation file saved, and run it with the --uninstall option. ''sh filename.run --uninstall'', and it uninstalls everything it put in. Then it's a simple matter of restoring your XF86Config from the backup we made above.

== Issues ==
* One issue I've had is between the GeForce FX 5200 card and the Asus P4S8X-X motherboard. When you started the X server, it would display garbled text and then hang. This problem can be solved by going into the BIOS and setting your AGP speed down from 8x to 4x.

* Compiling NVIDIA 1.0-7676 on kernel 2.6.14 requires a small modification.
** First you need Module.symvers at the kernel sources dir so you must build the kernel.
** Then extract the driver sources with <tt>./NVIDIA-Linux-x86-1.0-7676-pkg1.run -x</tt>.
** Change line 533 of NVIDIA-Linux-x86-1.0-7676-pkg1/usr/src/nv/nv-linux.h to <tt># define NV_PCI_DEVICE_NAME(dev) pci_pretty_name(dev)</tt>
** After this install the driver with <tt>./NVIDIA-Linux-x86-1.0-7676-pkg1/nvidia-installer --kernel-source-path=...</tt>

==See Also==
* [[NVIDIA]]

NVIDIA graphics drivers

2006-01-04T15:04:49Z

Geniarse: Added eslect info for gentoo

This is a guide on how to install [[NVIDIA]]'s drivers for X-windows, the graphical user interface system on Linux. These drivers are not required, but if you wish to run games such as Quake or Unreal at full speed you should install them. Before you start, take note that the drivers are distributed under a non-opensource license.

==Distribution specific==
=== Fedora Users ===
For [[Fedora]] users, the NVIDIA drivers are available repackaged in RPM, with pre-build kernel modules for easy install and update. Normally you can find the rpms in the [[livna]].org apt/yum respository, but the latest drivers (version 6106) are not yet avaliable as RPMs. See [http://fedorafaq.org/faq/ the Fedora FAQ] for more information on how to install on Fedora Core 2 anyway, or [http://rpm.livna.org/livna-switcher.html here] for more info on the livna nvidia packages.

Drivers before version 6106 will not work with prebuilt Fedora Core 2 kernels, because they do not support [[4stacks|4k Stacks]].

===Debian===
[[Debian]] has packages for these drivers. There are two packages that need to be installed.
One for the binary drivers and libraries and one for the [[kernel module]]. 
For Debian 3.1 (Sarge) and higher they are called <tt>nvidia-glx</tt> and <tt>nvidia-kernel-<version></tt> (both are in the non-free section). Where <version> is one matching your used Debian kernel or <tt>source</tt> to build the module for your specific kernel. See the README.Debian file that comes with them for full instructions. And use the package [[module-assistant]] to help compile the kernel module if you don't have a default Debian kernel. After installing these packages, the X server configuration file needs to be changed, seen the section about that below.

The other optional packages are <tt>nvidia-glx-dev</tt> for when you need to compile an openGL applicating against the nvidia openGL libs and <tt>nvidia-settings</tt> for a [[GUI]] application to configure the various driver options.

In Debian 3.0 (Woody) these packages are called <tt>nvidia-glx-src</tt> and <tt>nvidia-kernel-src</tt> (both are in the contrib section and use [[wget]] to download the actual drivers). 

===SuSE===
For [[SuSE]] users, the NVIDIA drivers are available from [http://www.nvidia.com/object/linux.html NVIDIA], the installation HOWTO is available from [ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/nvidia-installer-HOWTO here].
Follow the steps described in the HOWTO. If Hardware 3D - acceleration fails but X11 in 2D mode is using the new nvidia driver do the following: install the driver again, the second time don't use the program <tt>sax2</tt> but run the command <tt>switch2nvidia</tt>

===Gentoo===
[[Gentoo]] has ebuilds available which can be installed with: 
 <tt> emerge nvidia-kernel nvidia-glx</tt> 
 
The first ebuild "nvidia-kernel" provides Nvidia's driver for their various cards and nvidia-glx provides 3D acceleration (this is optional). To switch to the nvidia [[openGL]] implementation run
 <tt> eselect opengl nvidia </tt> 
 
You have to edit your X11 config file manually using the procedure described [[#Editing the X11 configuration|below]] (note: [[gentoo]] uses [[X.org]]).

===Mandrake/Mandriva===
[[Mandriva]] has Nvidia RPMs available for PowerPack users (ie. those who bought a boxed set or are club members). If you have a PowerPack the drivers will install automatically when you install the OS.

For everyone else the manual procedure is:

1) If you haven't already done so go to http://easyurpmi.zarb.org and setup access to the software repositories for your version.

2) In the Software section in the Mandrake Control Centre, or using the urpmi command as root, install the packages "kernel-source-2.6" ("kernel-source" for versions 9.2 or below) and "gcc" (without quotes).

3) Make sure you have the latest kernel - the kernel package isn't updated automatically but the kernel-source package is, which could lead to a version mismatch. To do this run (from a terminal window):
<tt><code><pre>
su
urpmi.update -a
urpmi kernel
</pre></code></tt>
If it lists a whole lot of different kernels most users can just select number 1 in the list. Otherwise run <tt><code><pre>rpm -qa | grep kernel</pre></code></tt> to see which kernel package you have installed. For more information see http://www.mandriva.com/en/security/kernelupdate

Now follow the rest of the instructions below under "Manual Installation" from "Install" onwards.

==Manual installation==
=== Download ===
The first step is to download some needed files. First, grab the latest version of the drivers from the [http://nvidia.com/content/drivers/drivers.asp NVIDIA Website]. Once you have that downloaded, make sure you have the source for your kernel. You can check what kernel you have by running the command '[[uname]] -r', without the quotes.

=== Install ===
First of all, you need to shut down X. Yes, that's right, we're going to be working from a command line. To do this:

1) Press Ctrl+alt+F1 on the keyboard. Now you should be at a console login screen, login as root.

2) Type the command 'telinit 3' (no quotes) to put your machine into runlevel 3 (no graphical interface). It will tell you about some services its restarting, if it doesn't return you to the command prompt press enter. For more information on this, refer to [[run levels]].

Once you get X shut off, navigate (see [[Directory_Commands]]) to where ever you downloaded the driver file to, and run it. You can run it by typing ''sh filename''. It should check to make sure that it downloaded OK, then start up the installation program.

Go through the first screen, accept the license, and when it asks if you want to try and download a kernel interface from NVIDIA, say no. I've never seen anyone get the kernel interface form the site, so we'll save time and move onto the next screen, where it tells us it will compile the kernel interface on its own. This is where our kernel source comes into play. It should compile and install on its own, so go to the next screen. This should pretty much wrap up anything important in the installation.

=== Editing the X11 configuration ===
The next step is to edit your [[X11]] configuration file, so it loads the nvidia driver. For [[XFree86]] the file is usually found in /etc/X11/ and called [[XF86Config]], but you might also have XF86Config-4, in which case you should edit that instead. Many newer distributions use [[X.org]], which uses /etc/X11/Xorg.conf in place of /etc/X11/XF86Config.

Before we do that, we should back up the file, just in case something goes wrong.

# cp /etc/X11/XF86Config /etc/X11/XF86Config.backup

Then, open the X config file in vi (or whatever editor you prefer, be it [[pico]], [[nano]], [[emacs]] or [[joe]]) by running:

# vi /etc/X11/XF86Config

Look for the '''Module''' section, and make sure it includes the '''Load "glx"''' line. If it doesn't, add it in. Then remove the '''Load "dri"''' and '''Load "GLCore"''' lines, if you have them. If you might want to go back to the old drivers later you can comment out loading dri and GLCore instead of removing them completely by putting a hash at the start of the line. An example configuration:

<tt>
Section "Module"
Load "dbe" # Double buffer extension
Load "type1"
Load "speedo"
Load "freetype"
Load "glx"
<nowiki># Load "dri"</nowiki> 
<nowiki># Load "GLcore"</nowiki> 
EndSection
</tt>

Finally, find the Device setion, and change the line '''Driver "nv"''' or '''Driver"vesa"''' to '''Driver "nvidia"'''. An example device section:

<tt>
Section "Device"
Identifier "NVIDIA"
Driver "nvidia"
VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection
</tt>

To disable the NVidia splash-screen logo when starting X, add the option highlighted below:

<tt>
Section "Device"
Identifier "NVIDIA"
Driver "nvidia"
'''Option "nologo" "1"'''
VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection
</tt>

=== Start X ===
Now all that's left is to start X back up. To do this type the command 'telinit 5' at the console prompt and it should load X and take you to the normal graphical login screen. You should now have your brand-new NVIDIA drivers installed and working. Good job!

=== Uninstalling NVIDIA drivers ===
Did something in your installation go terribly, terrible wrong? No problem! Start your box up in console-only mode, navigate to where you have the nvidia driver installation file saved, and run it with the --uninstall option. ''sh filename.run --uninstall'', and it uninstalls everything it put in. Then it's a simple matter of restoring your XF86Config from the backup we made above.

== Issues ==
* One issue I've had is between the GeForce FX 5200 card and the Asus P4S8X-X motherboard. When you started the X server, it would display garbled text and then hang. This problem can be solved by going into the BIOS and setting your AGP speed down from 8x to 4x.

* Compiling NVIDIA 1.0-7676 on kernel 2.6.14 requires a small modification.
** First you need Module.symvers at the kernel sources dir so you must build the kernel.
** Then extract the driver sources with <tt>./NVIDIA-Linux-x86-1.0-7676-pkg1.run -x</tt>.
** Change line 533 of NVIDIA-Linux-x86-1.0-7676-pkg1/usr/src/nv/nv-linux.h to <tt># define NV_PCI_DEVICE_NAME(dev) pci_pretty_name(dev)</tt>
** After this install the driver with <tt>./NVIDIA-Linux-x86-1.0-7676-pkg1/nvidia-installer --kernel-source-path=...</tt>

==See Also==
* [[NVIDIA]]

Network addressing

2005-12-07T19:04:53Z

Geniarse:

==IP Adressing==
===IPv4 - The current Internet standard===
To connect to an IP network, your host (specifically your host's [[network interface]]) will need a unique [[IP address]] to identify itself as a host on the network. In IPV4, an IP address is a 32-bit number that uniquely identifies your [[NIC]] on a network. For ease of readability we divide this 32-bit number into 4 [[octet]]s with a period separating each one. Each octet has a decimal equivalent of 0-255. A typical IP address then would look something like this: 192.168.5.26.

===Assigning IP Address===
There are two ways to set the IP address for a [[NIC]]. You can do it manually or you can have it set automatically via [[DHCP]]. [[DHCP]] dynamically assigns IP addresses and other information such as [[subnet mask]], [[DNS]] server, and [[default gateway]] to hosts upon bootup. Most network routers have DHCP built in and enabled by default. However, for small networks it may be preferable to set the IP address manually.

===Subnet Masks===
[[subnet mask|Subnet masks]] are used to logically split a network into "chunks", the details of which are too complicated for this walk-through, though a more detailed description can be found on the [[subnet mask]] page. Simply put, a subnet mask describes what portion (that is, which bits) of an address describes which logical network (the subnet) a host belongs to, and what portion identifies the host on that network. (Note: all hosts/devices on your local network must share the same subnet if you want them to able to communicate, otherwise the use of [[routing]] will be necessary.)

==Connecting to the Internet==

An IP address must be unique to your host, which becomes a problem once you connect your machine to the internet. How can you know which IP to choose? In this case an IP address (or range of addresses) must be obtained from your [[ISP]]. An ISP will often assign IP addresses dynamically, giving your computer whichever unique IP address is available from a range it has been assigned. This means your IP address could constantly change, to have a static IP you must ask your ISP to provide you with one however, buying a range of IP addresses can be expensive.

===Private IP Space===
To overcome this there are 3 ranges of address space which have been reserved for private use, and thus are non-routable (they cannot be sent across a [[WAN]]/internet -- a router will refuse to forward packets addressed to these). These are:

'''IP''' - 10.0.0.0 - 10.255.255.255 '''Subnet''' - 255.0.0.0 
'''IP''' - 172.16.0.0 - 172.31.255.255 '''Subnet''' - 255.255.0.0 
'''IP''' - 192.168.0.0 - 192.168.255.255 '''Subnet''' - 255.255.255.0 

===Connecting Multiple Machines===
Since these addresses (sometimes referred to as "private addresses") cannot not be routed to the global Internet, you might ask so how will I connect my hosts with private addresses to the Internet. This is achieved through some tricks:
*[[Router]] with [[NAT|''N''etwork ''A''ddress ''T''ranslation (NAT)]] and [[PAT|''P''ort ''A''ddress ''T''ranslation (PAT)]]. For outgoing packets, NAT will take a private IP address from the internal LAN and replace it with one provided by your [[ISP]]. [[NAT]], as it maps a private address directly to a public address, each host accessing the internet on the internal network must still have a unique public IP. [[PAT]] works around this and can map multiple private addresses to a single private address. This is achieved by assigning each private address a port on which to communicate with the outside world.
*[[Proxy server]] - This is a machine on your network which accepts requests for internet access from the private LAN then masquerades as that machine to the external network.

==Configuring Linux Host==
To set up a Linux machine on a [[network]], you must first be familiar with how Linux references your network interface card ([[NIC]]). Each NIC on a Linux machine is labeled "ethN" where N is and a number, by default the first being 0. Therefore if you have only one [[NIC]] on your machine it will most likely be labeled eth0.
To see a list of settings for your network card use the [[ifconfig]] command (normally you must be [[root]] to run this command).

The IP address can be configured on the command line using ifconfig, the example below configures the device eth0 with IP address 192.168.1.1 and a [[subnet mask]] of 255.255.255.0:
<tt><CODE><pre>
ifconfig eth0 192.168.1.1 255.255.255.0
</pre></CODE></tt>
To have the address dynamically assigned by a [[DHCP]] server on your network with [[hostname]] and [[domain name]] assigned also:
<tt><CODE><pre>
dhcpd -HD eth0
</pre></CODE></tt>

These settings will only apply until your next reboot, different [[distribution]]s have various ways of permanently configuring a computer's [[NIC]].

On some distributions, network configuration information is stored in the /etc/sysconfig directory. On a SuSE system for instance, you will find the network configuration settings in the ifcfg-eth0 file in this directory. This file contains a list of tuples, or key=value pairs, that tell Linux how to configure the eth0 interface. There are many options that can be set in this file but the following example gives the minimal list of required settings:

BOOTPROTO='static' 
STARTMODE='onboot' 
BROADCAST='192.168.5.255' 
IPADDR='192.168.5.178' 
NETMASK='255.255.255.0' 
NETWORK='192.168.5.0' 

In order for changes in this file to take effect, you must restart your interface. You can do this by using the ifdown and ifup commands. So if I have made changes to the eth0 interface I would do the following to restart that interface:
<tt><CODE><pre>
ifdown eth0
ifup eth0
</pre></CODE></tt>
Again, you need to be root to do this.

For a small private network you should use a private address as defined [[#Private IP space|above]]

Many people use "1" (e.g.192.168.1.1) as the final octet for their [[router]] or [[gateway]]. Look at the following example of IP addresses on some made-up [[LAN]]. All netmasks should be 255.255.255.0:
<code><pre>
Router: 192.168.1.1
Server 1: 192.168.1.10
Server 2: 192.168.1.11
Print server 1: 192.168.1.50
Print server 2: 192.168.1.51
PC 1: 192.168.1.100
PC 2: 192.168.1.101
PC 3: 192.168.1.102
DHCP Range: 192.168.1.150-200
</pre></code>
This gives a general make up that should help define a structured and maintainable network.

==See also==

*[[subnetting]]
*[[supernetting]]
*[[IPV6]]
*[[CIDR]]

Audio conversion

2005-05-17T19:18:38Z

Geniarse:

== Audio Conversion Scripts ==

Here are some scripts that will convert one audio format to another format. Usefull for organizing your audio library into one universal format. Or possibly, you have trouble playing .m4a's with xmms. Just convert them all to .mp3

Change the permissions so they are executable and put them in your [[$PATH]]

* [[.m4a to .mp3]]
* [[.m4a to .ogg]]
* [[.m4a to .wav]]
* [[.mp3 to .wav]]
* [[.mp3 to .ogg]]
* [[.wma to .mp3]]
* [[.wma to .wav]]
* [[.wav to .mp3]]
* [[.wav to .ogg]]

Stty

2005-04-17T17:33:58Z

Geniarse: spelling

'''stty''' (short for '''s'''et '''t'''ele'''ty'''pe) is the command to set up a terminal (or terminal emulation session) such that it will fit the needs of the [[keyboard]] and attached screen. In the old days of [[vt100]] and and [[vt220]] [[terminal]]s is was a necessity to use a unix machine. <tt>stty</tt> without options lists the current setting.

<pre>
$ stty
speed 38400 baud; line = 0;
</pre>

User:Geniarse

2005-04-15T16:49:28Z

Geniarse:

Contact me: [mailto:tom.conneely17@ntlworld.com tom.conneely17@ntlworld.com]

I'm a student of physics in the UK and have long followed LINUX learning most things along the way by using the OS rather than reading up on it before beginning , finding things out as I needed to(perhaps not the best way to do things but it means simple tasks are full of suprises and many reinstallations). Now I am familiar with most aspects of Linux after 3 years of tweaking and settling on Gentoo as my chosen distro (after trying mandrake, suse slackware and debian). My main area of expertise computing wise is networking (particularly infrastructure e.g. routing and switching) due to my Cisco networking qualification.

==My Links==
[[Special:Wantedpages]] 
[http://wiki.linuxquestions.org/wiki.phtml?title=Special:Popularpages&limit=100000&offset=0 All Articles]

Gentoo tips & tricks

2005-04-13T15:56:18Z

Geniarse:

This is a collection of '''tips & tricks''' for the peculiarities of [[Gentoo]].

== Use flags ==
[[USE flags]] are the way Gentoo organizes the compile time options. You can list them in your make.conf (See external links below)

===Tools===
ufed = use flag editor, emerge ufed, then run ufed as root

A problem with ufed, is that it organizes your useflags alphabetically, So if you added an experimental one by hand in your make.conf, it will be hidden amongst your countless others.

=== Files ===
/etc/make.conf has a use flag section in it.

===Rebuilding what needs to be rebuilt ===
emerge -pev world | grep 'gtk' | awk '{print "=" $4}'

(rac's line)
swap gtk for the useflag of you choice

== Masked packages ==
A lot of times you'll want to emerge a masked package (or a masked version of one). One short way to do this is <code>ACCEPT_KEYWORDS="~x86" emerge package</code> (replace x86 with your architecture). A slightly shorter way is to create a file called <code>/usr/sbin/expmerge</code>, with the following contents:
<pre>#!/bin/sh
ACCEPT_KEYWORDS="~x86" emerge $*</pre>
Then just <code>expmerge package</code>.
Mixing unstable with stable packages can lead to problems, so it's recommended you pick one type and use it all the time. This is more important for libraries rather then programs.

NOTE: the aforementioned method of emerging masked packages is deprecated and unsupported. please use /etc/portage/ (man portage, man emerge)

== Emerge tips ==
*emerge world -uDp, -- list things to be updated 
*emerge world -uD -- get almost everything updated 
*revdep-rebuild -- check for packages that break by rebuilding a dependancy

==Gentoo & KDE==
Remember - when installing [[KDE]] on Gentoo, you don't have to install every kde package. Instead, you can simply choose to install a "small" subset of them - ''for example'':

<pre># emerge kdebase kdeartwork</pre>

Prior to this, if you want to check out what packages would be installed, use the --pretend option - ''for example'':

<pre># emerge --pretend kdebase kdeartwork | less</pre>

(As a useful alternative to --pretend, you could use the --ask option - see ''man emerge'' for more information).

N.B - As of KDE 3.4 onwards, you will be able to utilise ''split ebuilds'' - this approach enables you to install individual KDE applications, without a plethora of other KDE apps automatically being installed (as in the monolithic approach).

==See also==
*[[Common tasks]]
*[[Distribution specific tips and tricks]]

== External links==
* [http://forums.gentoo.org/viewtopic.php?t=157851 A sorted list of useflags for make.conf].

== Internal links==
*[[Installing Slackware and Gentoo]]

USE flags

2005-04-13T15:54:32Z

Geniarse: more errors

'''USE flags''' are used by [[Gentoo|Gentoo's]] [[portage]] and [[emerge]], to configure which features should be compiled into the software's binary. This allows software installed to have only the features needed by the user leading to a faster more stable environment.

==Setting flags==
===/etc/make.conf===
The USE flags are set in <tt>/etc/make.conf</tt>, where other portage features can be tweaked. A simple setting could look like:

<tt><code><pre>
USE="gnome gtk2 dvd -kde"
</pre></code></tt>

These flags tell portage to compile packages optimised for [[Gnome]] and with dvd functionality, the <tt>"-kde"</tt> means kde functionality will not be compiled into packages (if option between gnome and kde exists for a package).

===ufed===
There are a huge number of possible use flags [http://gentoo-portage.com/USE] too numerous to list here each tweaking package features to a users precise requirements. To help there is a utility called [[ufed]] ('''U'''se '''F'''lag '''Ed'''itor), which uses a simple text-based [[GUI]] to select USE flags. This can be installed using emerge:
<tt><code><pre>
emerge -av ufed
</pre></code></tt>

The selections are written to <tt>/etc/make.conf</tt> in alphabetical order.

==Updating system after USE flag change==
If after installation of a package the USE flags are altered, the system can be updated to reflect the changes using emerge:

<tt><code><pre>
emerge --newuse --update --ask --deep world
</pre></code></tt>

==See also==
*[[Gentoo]]
*[[Portage]]
*[[Emerge]]
*[[Gentoo tips & tricks]]

==External Links==
*[http://gentoo-portage.com/USE USE flag list]
*[http://www.gentoo.org Gentoo official site]

USE flags

2005-04-13T15:53:43Z

Geniarse:

'''USE flags''' are used by [[Gentoo|Gentoo's]] [[portage]] and [[emerge]], to configure which features should be compiled into the software's binary. This allows software installed to have only the features needed by the user leading to a faster more stable environment.

==Setting flags==
===/etc/make.conf===
The USE flags are set in <tt>/etc/make.conf</tt>, where other portage features can be tweaked. A simple setting could look like:

<tt><code><pre>
USE="gnome gtk2 dvd -kde"
</pre><code></tt>

These flags tell portage to compile packages optimised for [[Gnome]] and with dvd functionality, the <tt>"-kde"</tt> means kde functionality will not be compiled into packages (if option between gnome and kde exists for a package).

===ufed===
There are a huge number of possible use flags [http://gentoo-portage.com/USE] too numerous to list here each tweaking package features to a users precise requirements. To help there is a utility called [[ufed]] ('''U'''se '''F'''lag '''Ed'''itor), which uses a simple text-based [[GUI]] to select USE flags. This can be installed using emerge:
<tt><code><pre>
emerge -av ufed
</pre><code></tt>

The selections are written to <tt>/etc/make.conf</tt> in alphabetical order.

==Updating system after USE flag change==
If after installation of a package the USE flags are altered, the system can be updated to reflect the changes using emerge:

<tt><code><pre>
emerge --newuse --update --ask --deep world
</pre><code></tt>

==See also==
*[[Gentoo]]
*[[Portage]]
*[[Emerge]]
*[[Gentoo tips & tricks]]

==External Links==
*[http://gentoo-portage.com/USE USE flag list]
*[http://www.gentoo.org Gentoo official site]

USE flags

2005-04-13T15:53:08Z

Geniarse: draft article

'''USE flags''' are used by [[Gentoo|Gentoo's]] [[portage]] and [[emerge]], to configure which features should be compiled into the software's binary. This allows software installed to have only the features needed by the user leading to a faster more stable environment.

==Setting flags==
===/etc/make.conf===
The USE flags are set in <tt>/etc/make.conf</tt>, where other portage features can be tweaked. A simple setting could look like:

<tt><code><pre>
USE="gnome gtk2 dvd -kde"
</pre><code></tt>

These flags tell portage to compile packages optimised for [[Gnome]] and with dvd functionality, the "<tt>-kde</tt>" means kde functionality will not be compiled into packages (if option between gnome and kde exists).

===ufed===
There are a huge number of possible use flags [http://gentoo-portage.com/USE] too numerous to list here each tweaking package features to a users precise requirements. To help there is a utility called [[ufed]] ('''U'''se '''F'''lag '''Ed'''itor), which uses a simple text-based [[GUI]] to select USE flags. This can be installed using emerge:
<tt><code><pre>
emerge -av ufed
</pre><code></tt>

The selections are written to <tt>/etc/make.conf</tt> in alphabetical order.

==Updating system after USE flag change==
If after installation of a package the USE flags are altered, the system can be updated to reflect the changes using emerge:

<tt><code><pre>
emerge --newuse --update --ask --deep world
</pre><code></tt>

==See also==
*[[Gentoo]]
*[[Portage]]
*[[Emerge]]
*[[Gentoo tips & tricks]]

==External Links==
*[http://gentoo-portage.com/USE USE flag list]
*[http://www.gentoo.org Gentoo official site]

Emerge

2005-04-13T15:25:05Z

Geniarse: added verbose switch

'''Emerge''' is the traditional, and the simplest, command-line interface to [[Gentoo]]'s [[Portage]] system. Given a package name, emerge will find the latest available version that satisfies the settings in [[make.conf]], and install it, along with any [[dependency|dependencies]] it requires.

==Common usage==
If it is more than a couple of days since you last did, run <tt>emerge sync</tt> before using the commands below. All the install commands lists the [[USE flags]] that affects the emerge; if any sound useful add them to <tt>/etc/make.conf</tt>

* Find package: <tt>emerge -S keywords</tt>
* Install new package quickly: <tt>emerge -av package-name</tt>
* Install new package, upgrading dependencies: <tt>emerge -auDv package-name</tt>
* Upgrade all packages: <tt>emerge -auDv world</tt>

To clean up unwanted packages from the system, it is usually easiest and cleanest to use this approach [http://forums.gentoo.org/viewtopic.php?t=148415].

nano -w /var/cache/edb/world # Remove anything you don't want anymore
emerge depclean -a # Check for sanity. This is important.
rm -f ~/.revdep*
revdep-rebuild -a

==Common command-line options==
Emerge can accept a number of common command-line switches, including:
* -p (--pretend): Given the -p switch, emerge will simply calculate package dependencies, and output a list of packages that would be installed. This is particularly useful if you are unfamiliar with a particular package, and want to know what dependencies it has. This flag can be used together with almost any others (e.g. <tt>emerge -uDp world</tt>).
* -f (--fetchonly): This causes emerge to download the source code for a package and its dependencies, without compiling or installing it.
* -s (--search): With this option, emerge will search the Portage tree for any packages whose names contain the given string (e.g. <tt>emerge -s xfree</tt> will return x11-base/xfree, x11-base/xfree-drm, and games-board/xfreecell).
* -u (--update): This causes emerge to upgrade the given package to the latest version, also updating its dependencies. This is often used together with the ''world'' keyword, updating every package that you have installed.
* -D (--deep): When used together with -u, -D will cause emerge to update '''all''' packages in the package's dependency tree, and not just its immediate dependencies (that is, it searches the package's immediate dependencies, then their dependencies, and so on). Again, this is often used in <tt>emerge -uD world</tt>.
* -v (--verbose): increases the amount of information outputted by emerge. Most usefully lists which [[USE flags]] are enabled for a packages compilation, and the total size of files to be downloaded. Used in conjuction with <tt>-a</tt> or <tt>-p</tt>.

==See also==
*[[Gentoo]]
*[[Portage]]
*[[Gentoo tips & tricks]]

==External links==
*[http://wiki.linuxquestions.org/wiki/Portage Emerge Man page]
*[http://www.gentoo.org Gentoo official site]

Emerge

2005-04-13T15:21:18Z

Geniarse: linking

'''Emerge''' is the traditional, and the simplest, command-line interface to [[Gentoo]]'s [[Portage]] system. Given a package name, emerge will find the latest available version that satisfies the settings in [[make.conf]], and install it, along with any [[dependency|dependencies]] it requires.

==Common usage==
If it is more than a couple of days since you last did, run <tt>emerge sync</tt> before using the commands below. All the install commands lists the USE flags that affects the emerge; if any sound useful add them to <tt>/etc/make.conf</tt>

* Find package: <tt>emerge -S keywords</tt>
* Install new package quickly: <tt>emerge -av package-name</tt>
* Install new package, upgrading dependencies: <tt>emerge -auDv package-name</tt>
* Upgrade all packages: <tt>emerge -auDv world</tt>

To clean up unwanted packages from the system, it is usually easiest and cleanest to use this approach [http://forums.gentoo.org/viewtopic.php?t=148415].

nano -w /var/cache/edb/world # Remove anything you don't want anymore
emerge depclean -a # Check for sanity. This is important.
rm -f ~/.revdep*
revdep-rebuild -a

==Common command-line options==
Emerge can accept a number of common command-line switches, including:
* -p (--pretend): Given the -p switch, emerge will simply calculate package dependencies, and output a list of packages that would be installed. This is particularly useful if you are unfamiliar with a particular package, and want to know what dependencies it has. This flag can be used together with almost any others (e.g. <tt>emerge -uDp world</tt>).
* -f (--fetchonly): This causes emerge to download the source code for a package and its dependencies, without compiling or installing it.
* -s (--search): With this option, emerge will search the Portage tree for any packages whose names contain the given string (e.g. <tt>emerge -s xfree</tt> will return x11-base/xfree, x11-base/xfree-drm, and games-board/xfreecell).
* -u (--update): This causes emerge to upgrade the given package to the latest version, also updating its dependencies. This is often used together with the ''world'' keyword, updating every package that you have installed.
* -D (--deep): When used together with -u, -D will cause emerge to update '''all''' packages in the package's dependency tree, and not just its immediate dependencies (that is, it searches the package's immediate dependencies, then their dependencies, and so on). Again, this is often used in <tt>emerge -uD world</tt>.

==See also==
*[[Gentoo]]
*[[Portage]]
*[[Gentoo tips & tricks]]

==External links==
*[http://wiki.linuxquestions.org/wiki/Portage Emerge Man page]
*[http://www.gentoo.org Gentoo official site]

Installing software

2005-04-13T15:13:11Z

Geniarse: links/grammar

A number of Linux [[distributions]] have faced a common problem: <center>'''"how do we distribute software packages and updates to our users?"'''</center>

Though every distribution has particular quirks, most have standardized around one of two approaches, '''binary''' or '''source installation''', each with its own advantages and drawbacks.

Looking for and installing/removing/updating software has been largely automated on Linux through accessible '''graphical frontends''' and powerful underlying tools.

==Installation methods==

===Graphical package managers===

Most distributions come with administration tools to facilitate installation and removal of software packages. These graphical package manager [[frontend]]s also take care of downloading and installation of other neccessary packages, and can perform security updates of your system.

Using one of these tools will greatly '''facilitate software installation and removal''' on your system, as compared to searching on [[rpmfind]] or [[Compilation From Source]]. Power users and developers tend to favour installation from source.

* [[Red Hat]] uses [[RPM]] packages.
** high-level tools: [[up2date]], [[Synaptic]] (See [[Fedora, Synaptic Package Manager, finding Repositories, listing RPMs, previously installed]] for downloading, installation, and use of Synaptic.
** lower-level tools: [[apt-get]], [[Yum]]
** low-level tool: [[rpm]]

* [[SuSE]] uses [[RPM]] packages.
** high-level tool: [[YAST]]
** low-level tool: [[rpm]]

* [[Mandrake]] uses [[RPM]] packages.
** high-level tool: [[rpmdrake]]
** lower-level tool: [[URPMI]]
** low-level tool: [[rpm]]
** read the [http://www.urpmi.org/easyurpmi/index.php EasyURPMI page] to update your installation sources and search and install packages from the web automagically.

* [[Debian]] (and distros built on Debian, such as [[Knoppix]]) uses [[DEB]] packages.
** high-level tools: [[synaptic]] and [[gnome-apt]]
** lower-level tool: [[apt-get]]
** low-level tool: [[dpkg]]
** see the excellent section on the [[Apt]]-suite for more information on softare installation on Debian systems.

* [[Gentoo]] builds software from source (though binary installation is possible).
** tools: [[portage]] and [[emerge]]

* [[Slackware]] uses [[TGZ]] packages.
** tools: [[pkgtool]], [[slapt-get]], [[swaret]]

===Pre-compiled binaries===

Most Linux distributions today use this method - software packages are built on some conventionally-configured computer, then packaged up for downloading or distribution on CDs. The advantages are speed, standardization, and simplicity - minimal time and tools are required to get a particular piece of software running.

* [[TGZ]] - the longest-lasting form of package management, used by [[Slackware]] and its descendants. Something that confuses many newcomers is the extension. All Slackware packages end in '.tgz' but not all '.tgz' files are Slackware packages. Slackware packages are essentially gzipped tar files of binaries. Ordinarily, non-Slackware gzipped tar files will have the extension '.tar.gz' but sometimes are called '.tgz' as well. Which it is should be clear, based on where you download it but, if not, executing <tt>file</tt> name_of_file.tgz (or just trying to install it) will identify it.

* [[RPM]] - the RedHat Package Manager format, described at [http://www.rpm.org/ www.rpm.org]. This format is used by [[Red Hat]], [[SuSE]], and [[Mandrake]]. You can search for recent RPMs for your system using [[rpmfind]].

* [[DEB]] - the Debian package format. This is used by [[Debian]] and [[Debian]]-based distributions, such as [[Knoppix]].

===[[Compilation from source]]===

Some newer distributions are adopting this method. Rather than compiling a software package, the distributor makes the source available, perhaps with some modifications, along with a "recipe" for configuring it and installing it on an end-user's computer. The advantages of this method are optimization and customization - software is built to take advantage of the hardware you have, rather than falling back on a least common denominator, and you exercise considerable control over how the program is built, what features are included, and so forth.

* [[Portage]] is the [[Gentoo]] distribution's system for handling the downloading, compilation and installation of Gentoo packages.

* [[Compilation from source with checkinstall]]. You can combine the best of both worlds (the easy management of binary packages with the flexibility of compilation from source) by using the program [[checkinstall]]. It generates a [[RPM]] , [[DEB]] or [[TGZ]] binary package from the source compilation, and then installs it. You can manage the resulting package as any other package in your system.

Network addressing

2005-04-12T11:57:51Z

Geniarse: Some additions and editing of sections

==IP Adressing==
===IPv4 - The current Internet standard===
To connect to an IP network, your host (specifically your host's [[network interface]]) will need a unique [[IP address]] to identify itself as a host on the network. In IPV4, an IP address is a 32-bit number that uniquely identifies your [[NIC]] on a network. For ease of readability we divide this 32-bit number into 4 [[octet]]s with a period separating each one. Each octet has a decimal equivalent of 0-255. A typical IP address then would look something like this: 192.168.5.26.

===Assigning IP Address===
There are two ways to set the IP address for a [[NIC]]. You can do it manually or you can have it set automatically via [[DHCP]]. [[DHCP]] dynamically assigns IP addresses and other information such as [[subnet mask]], [[DNS]] server, and [[default gateway]] to hosts upon bootup. Most network routers have DHCP built in and enabled by default. However, for small networks it may be preferable to set the IP address manually.

===Subnet Masks===
[[subnet mask|Subnet masks]are used to logically split a network into "chunks", the details of which are too complicated for this walk-through, though a more detailed description can be found on the [[subnet mask]] page. Simply put, a subnet mask describes what portion (that is, which bits) of an address describes which logical network (the subnet) a host belongs to, and what portion identifies the host on that network. (Note: all hosts/devices on your local network must share the same subnet if you want them to able to communicate, otherwise the use of [[routing]] will be necessary.)

==Connecting to the Internet==

An IP address must be unique to your host, which becomes a problem once you connect your machine to the internet. How can you know which IP to choose? In this case an IP address (or range of addresses) must be obtained from your [[ISP]]. An ISP will often assign IP addresses dynamically, giving your computer whichever unique IP address is available from a range it has been assigned. This means your IP address could constantly change, to have a static IP you must ask your ISP to provide you with one however, buying a range of IP addresses can be expensive.

===Private IP Space===
To overcome this there are 3 ranges of address space which have been reserved for private use, and thus are non-routable (they cannot be sent across a [[WAN]]/internet -- a router will refuse to forward packets addressed to these). These are:

'''IP''' - 10.0.0.0 - 10.255.255.255 '''Subnet''' - 255.0.0.0 
'''IP''' - 172.16.0.0 - 172.31.255.255 '''Subnet''' - 255.255.0.0 
'''IP''' - 192.168.0.0 - 192.168.255.255 '''Subnet''' - 255.255.255.0 

===Connecting Multiple Machines===
Since these addresses (sometimes referred to as "private addresses") cannot not be routed to the global Internet, you might ask so how will I connect my hosts with private addresses to the Internet. This is achieved through some tricks:
*[[Router]] with [[NAT|''N''etwork ''A''ddress ''T''ranslation (NAT)]] and [[PAT|''P''ort ''A''ddress ''T''ranslation (PAT)]]. For outgoing packets, NAT will take a private IP address from the internal LAN and replace it with one provided by your [[ISP]]. [[NAT]], as it maps a private address directly to a public address, each host accessing the internet on the internal network must still have a unique public IP. [[PAT]] works around this and can map multiple private addresses to a single private address. This is achieved by assigning each private address a port on which to communicate with the outside world.
*[[Proxy server]] - This is a machine on your network which accepts requests for internet access from the private LAN then masquerades as that machine to the external network.

==Configuring Linux Host==
To set up a Linux machine on a [[network]], you must first be familiar with how Linux references your network interface card ([[NIC]]). Each NIC on a Linux machine is labeled "ethN" where N is and a number, by default the first being 0. Therefore if you have only one [[NIC]] on your machine it will most likely be labeled eth0.
To see a list of settings for your network card use the [[ifconfig]] command (normally you must be [[root]] to run this command).

The IP address can be configured on the command line using ifconfig, the example below configures the device eth0 with IP address 192.168.1.1 and a [[subnet mask]] of 255.255.255.0:
<tt><CODE><pre>
ifconfig eth0 192.168.1.1 255.255.255.0
</pre></CODE></tt>
To have the address dynamically assigned by a [[DHCP]] server on your network with [[hostname]] and [[domain name]] assigned also:
<tt><CODE><pre>
dhcpd -HD eth0
</pre></CODE></tt>

These settings will only apply until your next reboot, different [[distribution]]s have various ways of permanently configuring a computer's [[NIC]].

On some distributions, network configuration information is stored in the /etc/sysconfig directory. On a SuSE system for instance, you will find the network configuration settings in the ifcfg-eth0 file in this directory. This file contains a list of tuples, or key=value pairs, that tell Linux how to configure the eth0 interface. There are many options that can be set in this file but the following example gives the minimal list of required settings:

BOOTPROTO='static' 
STARTMODE='onboot' 
BROADCAST='192.168.5.255' 
IPADDR='192.168.5.178' 
NETMASK='255.255.255.0' 
NETWORK='192.168.5.0' 

In order for changes in this file to take effect, you must restart your interface. You can do this by using the ifdown and ifup commands. So if I have made changes to the eth0 interface I would do the following to restart that interface:
<tt><CODE><pre>
ifdown eth0
ifup eth0
</pre></CODE></tt>
Again, you need to be root to do this.

For a small private network you should use a private address as defined [[#Private IP space|above]]

Many people use "1" (e.g.192.168.1.1) as the final octet for their [[router]] or [[gateway]]. Look at the following example of IP addresses on some made-up [[LAN]]. All netmasks should be 255.255.255.0:
<code><pre>
Router: 192.168.1.1
Server 1: 192.168.1.10
Server 2: 192.168.1.11
Print server 1: 192.168.1.50
Print server 2: 192.168.1.51
PC 1: 192.168.1.100
PC 2: 192.168.1.101
PC 3: 192.168.1.102
DHCP Range: 192.168.1.150-200
</pre></code>
This gives a general make up that should help define a structured and maintainable network.

==See also==

*[[subnetting]]
*[[supernetting]]
*[[IPV6]]
*[[CIDR]]

NVIDIA graphics drivers

2005-01-19T23:01:41Z

Geniarse: Added gentoo howto, and example config for relevant XF86Config sections

This is a guide on how to install [[NVIDIA]]'s drivers under [[XFree86]]. These drivers are not required, but if you wish to run games such as Quake or Unreal at full speed you should install them. Before you start, take note that the drivers are distributed under a non-opensource license.

==Distribution specific==
=== Fedora Users ===
For [[Fedora]] users, the NVIDIA drivers are available repackaged in RPM, with pre-build kernel modules for easy install and update. Normally you can find the rpms in the [[livna]].org apt/yum respository, but the latest drivers (version 6106) are not yet avaliable as RPMs. See [http://fedorafaq.org/faq/ the Fedora FAQ] for more information on how to install on Fedora Core 2 anyway, or [http://rpm.livna.org/livna-switcher.html here] for more info on the livna nvidia packages.

Drivers before version 6106 will not work with prebuilt Fedora Core 2 kernels, because they do not support [[4stacks|4k Stacks]].

===Debian===
[[Debian]] also got packages for these drivers. There are two needed packages.
One for the binary drivers and libraries and one for the [[kernel module]]. 
For Debian [[stable]] these packages are called <tt>nvidia-glx-src</tt> and <tt>nvidia-kernel-src</tt> (both are in the contrib section and use [[wget]] to download the actual drivers). 
For Debian [[testing]] and [[unstable]] they are called <tt>nvidia-glx</tt> and <tt>nvidia-kernel-<version></tt> (both are in the non-free section). Where <version> is one matching your used Debian kernel or <tt>source</tt> to build the module for your specific kernel. See the README.Debian file that comes with them for full instructions.

===SuSE===
For [[SuSE]] users, the NVIDIA drivers are available from [http://www.nvidia.com/object/linux.html NVIDIA], the installation HOWTO is available from [ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/nvidia-installer-HOWTO here].
Follow the steps described in the HOWTO. If Hardware 3D - acceleration fails but X11 in 2D mode is using the new nvidia driver do the following: install the driver again, the second time don't use the program <tt>sax2</tt> but run the command <tt>switch2nvidia</tt>

===Gentoo===
[[Gentoo]] has ebuilds available which can be installed with: 
 <tt> emerge nvidia-kernel nvidia-glx</tt> 
 
The first ebuild "nvidia-kernel" provides Nvidia's driver for their various cards and nvidia-glx provides 3D acceleration (this is optional).

You have to edit your X11 config file manually using the procedure described [[#Editing the X11 configuration|below]] (note: [[gentoo]] uses [[X.org]]).

==Manual installation==
=== Download ===
The first step is to download some needed files. First, grab the latest version of the drivers from the [http://nvidia.com/content/drivers/drivers.asp NVIDIA Website]. Once you have that downloaded, make sure you have the source for your kernel. You can check what kernel you have by running the command '[[uname]] -r', without the quotes.

=== Install ===
First of all, you need to shut down X. Yes, that's right, we're going to be working from a command line. For more information on this, refer to [[run levels]]. Once you get X shut off, navigate to where ever you downloaded the driver file to, and run it. You can run it by typing ''sh filename''. It should check to make sure that it downloaded OK, then start up the installation program. Go through the first screen, accept the license, and when it asks if you want to try and download a kernel interface from NVIDIA, say no. I've never seen anyone get the kernel interface form the site, so we'll save time and move onto the next screen, where it tells us it will compile the kernel interface on its own. This is where oour kernel source comes into play. It should compile and install on its own, so go to the next screen. This should pretty much wrap up anything important in the installation.

=== Editing the X11 configuration ===
The next step is to edit your [[X11]] configuration file, so it loads the nvidia driver. For [[XFree86]] the file is usually found in /etc/X11/ and called [[XF86Config]], but you might also have XF86Config-4, in which case you should edit that instead. If you use [[X.org]], the file to edit is /etc/X11/Xorg.conf.

Before we do that, we should back up the file, just in case something goes wrong.

# cp /etc/X11/XF86Config /etc/X11/XF86Config.backup

Then, open the X config file in vi (or whatever editor you prefer, be it [[pico]], [[nano]], [[emacs]] or [[joe]]) by running vi /etc/X11/XF86Config. Look for the '''Module''' section, and make sure it includes the '''Load "glx"''' line. If it doesn't, add it in. Then remove the '''Load "dri"''' and '''Load "GLCore"''' lines, if you have them. If you might want to go back to the old drivers later you can comment out loading dri and GLCore instead of removing them completely by putting a hash at the start of the line. An example configuration:

<tt>
Section "Module"
Load "dbe" # Double buffer extension
Load "type1"
Load "speedo"
Load "freetype"
Load "glx"
<nowiki># Load "dri"</nowiki> 
<nowiki># Load "GLcore"</nowiki> 
EndSection
</tt>

Finally, find the Device setion, and change the line '''Driver "nv"''' or '''Driver"vesa"''' to '''Driver "nvidia"'''. An example device section:

<tt>
Section "Device"
Identifier "NVIDIA"
Driver "nvidia"
VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection
</tt>

=== Start X ===
Now all that's left is to start X back up. You should now have your brand-new NVIDIA drivers installed and working. Good job! An easy command is to just type 'startx' at the console prompt.

=== Uninstalling NVIDIA drivers ===
Did something in your installation go terribly, terrible wrong? No problem! Start your box up in console-only mode, navigate to where you have the nvidia driver installation file saved, and run it with the --uninstall option. ''sh filename.run --uninstall'', and it uninstalls everything it put in. Then it's a simple matter of restoring your XF86Config from the backup we made above.

== Issues ==
* One issue I've had is between the GeForce FX 5200 card and the Asus P4S8X-X motherboard. When you started the X server, it would display garbled text and then hang. This problem can be solved by going into the BIOS and setting your AGP speed down from 8x to 4x.

==See Also==
* [[NVIDIA]]

Ls

2004-08-09T16:43:10Z

Geniarse:

The '''ls''' [[command]] is one of the most common ones used when interacting with a text interface to a [[Linux]] system. It is the [[Unix|UNIX]] equivalent to the [[dir]] command common to many operating systems such as [[MS-DOS]].

== Using ls ==
<tt>ls</tt> has a number of common options in its use.

=== The long option ===
<tt>ls</tt>, without any other flags, simply prints a list of files without any other information. It however may be important to get some other details about the file, such as permissions, types, and so on. The long option, <tt>-l</tt>, lists filenames, sizes, permissions, and other information.

=== All files ===
<tt>ls</tt> will normally omit hidden [[dot file]]s unless specified. The <tt>-a</tt> option forces <tt>ls</tt> to show them.

=== Type information===
Normally, the only way to get the type of a file is to use the above long option. However, it may be a little cluttering to get unnecessary data also. The <tt>-F</tt> option uses a normal listing, but instead places a special marker character after each filename to specify its type, otherwise, it is a normal file.

The final character added is <tt>*</tt> when the file is [[executable]], <tt>/</tt> is a directory, <tt>@</tt> is a [[symbolic link]], <tt>|</tt> is a [[FIFO]], <tt>=</tt> is a [[socket]].

== Default options ==
The default options for ls can be changed by either using a shell alias, or by defining an [[enviroment variable]] LS_OPTIONS e.g. adding to [[//etc/profile]]

export LS_OPTIONS="--color -l"

enables color output (a Linux extension) and displaying in the long format by default.

==External links==
*[http://man.linuxquestions.org/index.php?query=ls&section=0&type=2 Linux ls man page]

Scp

2004-08-03T16:33:58Z

Geniarse:

'''scp''', '''s'''ecure '''c'''o'''p'''y, is a tool used to securely copy files, by means of the [[SSH]] protocol. The [[sftp]] tool is similar. scp works very much like the Unix "[[cp]]" command:

scp <source> <destination>

If the source or destination of scp is a remote host, the syntax
username@host:/remote/directory/to/copy/to
is used. For example, to upload a file "foobar.txt" on a local computer to a remote host "hostname.org" using the username "user" to the /var/www directory, the syntax is as follows:

$ scp foobar.txt user@hostname.org:/var/www/
A password prompt follows
Password: <type the user's password here>

==See Also==
*[[SSH]]

Scp

2004-08-03T16:33:32Z

Geniarse: seealso ssh link

Gdm

2004-08-02T21:29:18Z

Geniarse:

'''GDM''' ('''GNOME Display Manager''') is the [[GNOME]] "login manager". It is a complete re-write of [[xdm]], and shares no code with it.

==See also==
*[[xdm]]
*[[kdm]]

{{msg:stub}}

User:Geniarse

2004-08-02T21:28:53Z

Geniarse:

Contact me: [mailto:tom.conneely17@ntlworld.com tom.conneely17@ntlworld.com]

I'm a student of physics in the UK and have long followed LINUX learning most things along the way by using the OS rather than reading up on it before beginning , finding things out as I needed to(perhaps not the best way to do things but it means simple tasks are full of suprises and many reinstallations). Now I am familiar with most aspects of Linux after 2 years of tweaking and settling on Slackware as my chosen distro (after trying mandrake, suse and debian). My main area of expertise computing wise is networking (particularly infrastructure e.g. routing and switching) due to my Cisco networking qualification.

==My Links==
[[Special:Wantedpages]] 
[http://wiki.linuxquestions.org/wiki.phtml?title=Special:Popularpages&limit=100000&offset=0 All Articles]

User:Geniarse

2004-08-02T15:34:10Z

Geniarse:

Contact me: [mailto:tom.conneely17@ntlworld.com tom.conneely17@ntlworld.com]

I'm a student of physics in the UK and have long followed LINUX learning most things along the way by using the OS rather than reading up on it (perhaps not the best way to do things but it means simple tasks are full of suprises and many reinstallations)

==My Links==
[[Special:Wantedpages]] 
[http://wiki.linuxquestions.org/wiki.phtml?title=Special:Popularpages&limit=100000&offset=0 All Articles]

Ls

2004-08-02T15:23:40Z

Geniarse: add ls_options info

The '''ls''' [[command]] is one of the most common ones used when interacting with a text interface to a [[Linux]] system. It is the [[Unix|UNIX]] equivalent to the [[dir]] command common to many operating systems such as [[MS-DOS]].

===[[Command options|Options]]===

<tt>ls -l</tt> - Lists the files contained in the directory, including info about the file; size and owner. 
<tt>ls -a</tt> - Lists the files contained in the directory, including hidden files. 
<tt>ls -F</tt> - Places information after some filenames to indicate the type of file. The final character added is <tt>*</tt> when the file is [[executable]], <tt>/</tt> is a directory, <tt>@</tt> is a [[symbolic link]], <tt>|</tt> is a [[FIFO]], <tt>=</tt> is a [[socket]]. 
'''ls --color''' - Changes output of ls to show different types of files (e.g. diecotries, links and normal files) in different colours.

The default options for ls can be changed by defining an [[enviroment variable]] LS_OPTIONS e.g. adding line to [[/etc/profile]]: 

<tt>export LS_OPTIONS="--color -l"</tt> 

Enables color output and displaying file info by default.

===External links===

*[http://man.linuxquestions.org/index.php?query=ls&section=0&type=2 ls man page]

Tar

2004-08-02T15:03:40Z

Geniarse: added see also

__NOTOC__
'''''tar''''' is short for "tape archive", although its use with magnetic tape backups is primarily of historical concern. ''tar'' is both a [[command]] and a [[file format]] used by the command. It is used to collect several [[files]] into one [[archive]], which can be more easily managed or [[compression|compressed]] as a unit, often with [[gzip]] or [[bzip2]].

== Using tar==
Tar has several uses, but the most commonly used is to extract or to create tar archive (known as "tarballs")

=== .tar ===
To unpack a standard .tar file, use the command
tar -xvf ''filename''
The [[Command options]] of tar:
* ''x'': decompress something
* ''v'': [[verbose]] mode
* ''f'': input from a file

If the ''f'' flag is omitted, the command will read from [[stdin]]. This allows several interesting things: for example, [[pipe|piping]] output in tar format to tar, to have it untarred.

(Note that, unlike most commands, the '-' before the options may be omitted.)

To create a tarball, you can use
tar cf ''tarballname.tar'' ''files''
which can be compressed afterwards.

=== tar.gz ===
Decompressing tarballs that have been gzipped can be done in two ways: first decompressing then extracting, by
gunzip ''filename''.tar.gz && tar xf ''filename''.tar
(the && ensures that if the gunzip fails, the tar program is not run)

Alternatively, some versions of tar support inbuilt decompression of [[gzip]]ped tar files. This requires the ''z'' option, transforming the command to:
tar -xvzf ''filename''

===tar.bz2===
Decompressing [[Bzip2]] tar files can be done in the same manner, bunzip2 first and then tar, but some versions of tar allow you to use the ''j'' option:
tar -xvjf '''filename'''

If this option is not available to you, you can achieve the same effect can be achieved with
bunzip2 '''filename''' | tar -xvf -
where, as mentioned above, the output of bunzip2 is [[pipe]]d to tar, which is directed to read from stdin with the final '-'.

==Using tar to copy files==
In addition to archiving files, tar can also be used to copy a group of files and directories using a [[pipe]]. To move all the files in /olddir to /newdir, for example, the syntax is
tar -c * | (cd /newdir; tar -xv)

Don't worry about the -v option with the pipe; the -v option writes to the [[stderr]] stream and will not interfere with the pipe.

==See Also==
*[[bzip2]]
*[[gzip]]

==External links==

*[http://man.linuxquestions.org/index.php?query=tar&section=0&type=2 tar man page]

Gzip

2004-08-02T15:01:36Z

Geniarse:

The gzip package compresses and decompresses data using a patent-free compression algorithm, LZ77. When called as '''gunzip''' or with the <tt>-d</tt> option, this utility can be used to decompress files created with: [[compress]](.Z), gzip(.gz,.tgz), and [[zip]](.zip) (first file only). When called as '''zcat''' or with the <tt>-dc</tt> options, displays the specified gzip compressed file without decompressing the file. The same program is installed as <tt>gzip</tt>, <tt>gunzip</tt>, and <tt>zcat</tt>.

Usages:
$ gzip [''options''] ''filename''
$ gunzip [''options''] ''filename''
$ zcat [''options''] ''filename'' # Same as gunzip -c

==[[Command options|Options]]==

*-h, --help: Displays available options.
*-c, --stdout: Cat data to stdout instead of a file.
*-d, --decompress: Decompress data even if <tt>gzip</tt> is called.
*-f, --force: Force overwrite to output files.
*-l, --list: For each compressed file, list the compressed and uncompressed size, compression ratio and name of the uncompressed file.
*-L, --license: Displays the software version and license terms and conditions.
*-r, --recursive: act on all the files in a directory tree.

==Examples==

$ gzip bigfile.txt
Compresses the specified filename. The compressed file is called bigfile.txt.gz

$ gzip -9 bigfile.txt
Compresses the specified file using the compression method that yields maximum reduction in size. The compression tradeoff between size and speed can be modified by using the form:
$ gzip -''n'' bigfile.txt
where ''n''=9 is the slowest, but best compression, and 1 is the fastest, and worst compression. This can be useful to tune the speed of compression of extremely large files (on relatively small ones this option can always be used with little performance tradeoff), where compression is not the greatest concern.

$ gzip -r /home/lala/docs
Compresses all the files seperately in the specified directory and all of its associated subdirectories. The "r" stands for recursive, and this option to recurse through all subdirectories is a common one for many Unix utilities.

$ zcat file.txt.gz |less
Decompress <tt>file.txt.gz</tt> and pass the data on to less for viewing. Don't remove the original file.

$ tar -xvzf file.tar.gz
The <tt>-z</tt> option tells [[tar]] to call gzip for decompressing the [[tarball]].

==See also==

* [[bzip2]]
* [[zmore]]
* [[tar]]

==External links==

* [http://man.linuxquestions.org/index.php?query=gzip&section=0&type=2 gzip man page] - also describes gunzip and zcat

Bzip2

2004-08-02T15:00:38Z

Geniarse:

'''bzip2''' uses a sophisticated [[algorithm]] to [[compress]] files that is up to 30 percent faster than that used by [[gzip]].

==Usage==

'''bzip2 [option] ''filename'''''

By default, '''bzip2''' does not overwrite existing output files. Use the '''--force''' option to override this setting. However, the program deletes input files by default. Use the '''--keep''' option to override this setting. The default file extension is '''.bz2'''.

==Examples==

bzip2 test.dat - Compresses the specified file

bzip2 --keep test.dat - Compresses the specified file without overwriting the input file.

==See Also==
*[[bzip2recover]]
*[[gzip]]
*[[tar]]

Bzip2recover

2004-08-02T14:59:48Z

Geniarse:

'''bzip2recover'''

Usage: bzip2recover filename

Attempts to recover data from a damaged file compressed with bzip2. If the file contains any blocks with salvageable data, each block is written to a file with a name such as recooo1file.bz2, recooo2file.bz2, etc.

==See also==
*[[bzip2]]

DNS

2004-08-02T14:47:37Z

Geniarse:

The '''DNS''' ('''D'''omain '''N'''ame '''S'''ystem) [[protocol]] is a distributed Internet directory database. It was designed to replace the task of manually maintaining [[hostname]] to [[IP address]] mappings in [[hostfile]]s, which was the way it was done when the [[Internet]] was still small. As the [[Internet]] grew, these [[hostfile]]s became increasingly difficult to maintain, thus the DNS protocol was born.

DNS is used mostly to translate between [[domain name]]s and [[IP address]]es, and to control Internet [[email]] delivery. Most Internet services rely on DNS to work, and if DNS fails, [[web site]]s cannot be located and email delivery stalls.

==DNS Server software==
* The most widely used server software of linux is [[BIND]], though others like [[dnsmasq]] (found at http://www.thekelleys.org.uk/dnsmasq/doc.html ) and [[djbdns]] (found at http://cr.yp.to/djbdns.html ) are gaining in popularity due to their ease of use and higher built-in [[security]].

* For those with dynamically allocated IP addresses, try [[DynDNS]] or [[no-ip.com]] which are service providers of dynamic DNS.

==DNS query software==
*[[dig]]
*[[nslookup]]

==See also==
*[[BIND]]
*[[Networking basics#DNS Configuration|DNS configuration]]

==External Links==
*[http://www.isc.org/index.pl?/sw/bind/ BIND homepage]
*[http://www.thekelleys.org.uk/dnsmasq/doc.html dnsmasq homepage]
*[http://cr.yp.to/djbdns.html djbdns homepage]

DNS

2004-08-02T14:43:58Z

Geniarse: BIND link in see also

The '''DNS''' ('''D'''omain '''N'''ame '''S'''ystem) [[protocol]] is a distributed Internet directory database. It was designed to replace the task of manually maintaining [[hostname]] to [[IP address]] mappings in [[hostfile]]s, which was the way it was done when the [[Internet]] was still small. As the [[Internet]] grew, these [[hostfile]]s became increasingly difficult to maintain, thus the DNS protocol was born.

DNS is used mostly to translate between [[domain name]]s and [[IP address]]es, and to control Internet [[email]] delivery. Most Internet services rely on DNS to work, and if DNS fails, [[web site]]s cannot be located and email delivery stalls.

==DNS Server software==
* The most widely used server software of linux is [[BIND]], though others like [[dnsmasq]] (found at http://www.thekelleys.org.uk/dnsmasq/doc.html ) and [[djbdns]] (found at http://www.djbdns.org/ ) are gaining in popularity due to their ease of use and higher built-in [[security]].

* For those with dynamically allocated IP addresses, try [[DynDNS]] or [[no-ip.com]] which are service providers of dynamic DNS.

==DNS query software==
*[[dig]]
*[[nslookup]]

==See also==
*[[BIND]]
*[[Networking basics#DNS Configuration|DNS configuration]]

Hosts file

2004-08-02T14:41:45Z

Geniarse: definiton/example file

This file resides in the directory [[<nowiki>/etc</nowiki>]] and maps the [[IP address]] of a device connected to the network to a name (typically the devices [[hostname]]). Due to the arrival of [[DNS]] this file is rarely used but is still useful for small networks and at boot when no [[name server]]s are running.

The layout of the file is a simple list of [[IP address|IP addresses]] followed by the name of the host e.g.: 
<tt>
:127.0.0.1 localhost 
:192.168.1.1 gateway 
:192.168.1.2 fileserver1 
:192.168.1.3 foo1 
:192.168.1.4 foo2 
</tt>

==See Also==
*[[DNS]]
*[[localhost]]

/etc

2004-08-02T14:28:45Z

Geniarse: links

'''/etc''' is the home of most core [[Configuration File|Configuration Files]] in [[Linux]]. It has details and preferences related to [[Hardware]], [[Run Levels]] and just about everything that comes with a barebones [[Kernel]] install.

Important files in /etc:
*[[fstab]]
*group
*[[grub.conf]] (GRUB only)
*hostname
*hosts
*inittab
*[[lilo.conf]] (LILO only)
*[[modules.conf]]
*network/interfaces
*passwd

ISO9660

2004-08-02T14:26:11Z

Geniarse:

#REDIRECT [[ISO 9660]]

WYSIWYG

2004-08-02T14:23:11Z

Geniarse: links/grammar

'''WYSIWYG''' ('''W'''hat '''Y'''ou '''S'''ee '''I'''s '''W'''hat '''Y'''ou '''G'''et. Pronounced "Wissy-Wig".)

WYSIWYG [[application]]s are a class of [[application]]s which display pre-processed information. In other words, the application does not display the [[markup]] or coding (which instructs a [[rendering engine]] how to display the content) rather, the application is itself a [[rendering engine]] which conceals the code from user and merely shows its effects. Conversely, editing of content and markup is not done by editing the code directly, but by manipulating an additional interface layer that translates (usually via graphical [[widget]]s and usually imprecisely) simplified input into code. In other words, the user clicks on an icon and the application inserts a canned subset of code into the text in order to try to approximate what the user might have intended.

Major classes of WYSIWYG applications are [[word processor]]s and [[HTML editor]]s.

Mount point

2004-08-02T14:05:05Z

Geniarse:

A '''Mount Point''' is a directory in which a [[filesystem]] is [[Mount|mounted]]. These directories usually reside in the [[parent directory]] [[<nowiki>/mnt</nowiki>]] but can be anywhere you wish. Default mount points can be defined in the file [[fstab|/etc/fstab]], this file also tells the [[kernel]] which filesystems are mounted at boot.

==See Also==
*[[mount]]/[[umount]]
*[[fstab|/etc/fstab]]
*[[Filesystem]]

Mount point

2004-08-02T14:03:33Z

Geniarse: corrected italics to bold

A '''Mount Point''' is a directory in which a [[filesystem]] is [[Mount|mounted]]. These directories usually reside in the [[parent directory]] [[/mnt]] but can be anywhere you wish. Default mount points can be defined in the file [[fstab|/etc/fstab]], this file also tells the [[kernel]] which filesystems are mounted at boot.

==See Also==
*[[mount]]/[[umount]]
*[[fstab|/etc/fstab]]
*[[Filesystem]]

Mount point

2004-08-02T14:03:12Z

Geniarse: definition/see also links

A ''Mount Point'' is a directory in which a [[filesystem]] is [[Mount|mounted]]. These directories usually reside in the [[parent directory]] [[/mnt]] but can be anywhere you wish. Default mount points can be defined in the file [[fstab|/etc/fstab]], this file also tells the [[kernel]] which filesystems are mounted at boot.

==See Also==
*[[mount]]/[[umount]]
*[[fstab|/etc/fstab]]
*[[Filesystem]]

Mount

2004-08-02T13:57:23Z

Geniarse: linking

'''Mount''' refers to both an action and a command. The Linux and other Unix-like operating systems deal with disks and file systems in a different manner than Windows or other non-Unix-based operating systems. Instead of assigning a drive letter to each drive, operating systems such as Linux instead deal with a single hierachy, and a drive (represented by a [[device]], listed under <tt>/dev</tt>) is made available, or is said to be ''mounted'', and the files on the drive made accessible under this single hierachy. The <tt>mount</tt> tool is used to mount a device.

Linux and other Unix-based operating systems, however, can deal with disks and devices in multiple formats. Consider trying to mount a [[CD-ROM]]. We need to know the following information:
* the [[device name]],
* the format
* where you want the files to appear (mount point).

For example, [[CD-ROM]] disks use the [[ISO9660]] format, and the device name is <tt>/dev/cdrom</tt>. There is a directory available for mounting [[CD-ROM]] disks, and that is <tt>/mnt/cdrom</tt>, so we might use this command to mount a CD-ROM disk:
mount -t iso9660 /dev/cdrom /mnt/cdrom

In general, you can call mount directly from the [[command line]], using the following general [[syntax]]:
mount [options] [device] [dir]

During the installation process, most linux [[distribution]]s create a file called [[fstab|/etc/fstab]], the [[filesystem]] table. This file contains mount settings for the [[volume]]s installed in your system. This means that we can avoid having to type in the [[device name]], format, etcetera, if we merely want to mount a CD. For example, if line did not exist already, you could add the following line in your [[fstab|/etc/fstab]] file for your cdrom drive (the first line here is just a helper for you; only add the /dev/cdrom line to [[fstab|/etc/fstab]]):
(device name) (mount point) (filesystem types) (options) (usually 0 0)
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0

Then, when you want to mount a new CD, you would just type <tt>mount /cdrom</tt>.

By default, many linux distributions will require you to [[go root]] to mount and [[umount|unmount]] volumes (this is signified by the lack of an option "user" or "users" on the line). Example of a root-only-mountable device:

/dev/floppy /mnt/floppy auto noauto,defaults 0 0

To change [[fstab|/etc/fstab]] so that any user can mount (and unmount) his or her own devices, make sure there's an option "user" in the list of options (the fourth thing on the line between filesystem type and the two 0's at the end of the line) for that device {the "user" option is so user mike can mount his cdrom and then only he can [[umount|unmount]] it}.

To make it so that any user can mount any device or [[umount|unmount]] any device, add the options "users" to the list of options for that device {the "users" option is so that mike can mount the cdrom but he or any other regular user can unmount it at any time}. Examples:

/dev/floppy1 /mnt/floppy1 auto noauto,defaults,user 0 0

/dev/floppy2 /mnt/floppy2 auto noauto,defaults,users 0 0

For more information on the mount command, type man mount at any shell prompt.

== Mounting an ISO image ==

Sometimes it is useful to mount an [[ISO image]] that you made or have downloaded to be able to access or check the contents. This is possible with the following command:

mount -t iso9660 -o ro,loop=/dev/loop0 NameOfISOFile MountPoint

The [[mount point]] has to be a directory, as described above. You can also [[Making_an_ISO_from_CDROM|make an ISO of an existing CDROM]].

== See Also ==

* [[umount]]
* [[fstab|/etc/fstab]]
* [[Making an ISO from CDROM]]

Mount

2004-08-01T13:41:13Z

Geniarse:

'''mount''' - Attach a [[volume]] to the [[file system]]

You can call mount directly from the command line, using the following general syntax:
mount [options] [device] [dir]

For example, you might use this command to mount a CD-ROM disc:

mount -t iso9660 /dev/cdrom /mnt/cdrom

The -t iso9660 option tells the system that you are mounting an [[iso9660]] format CD-ROM. Type man fs in a shell for more information on the various [[file system]]s.

During the installation process, most linux [[distribution]]s create a file called [[fstab|/etc/fstab]]. This file contains mount settings for the [[volume]]s installed in your system. This can make mounting drives easier. For example, you could add the following line in your /etc/fstab file for your cdrom drive (the first line here is just a helper for you; only add the /dev/cdrom line to /etc/fstab):
(device name) (mount point) (filesystem types) (options) (usually 0 0)
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0

Then, when you want to mount a new CD, you would just type mount cdrom.

By default, many linux distributions will require you to [[go root]] to mount and unmount volumes (this is signified by the lack of an option "user" or "users" on the line). Example of a root-only-mountable device:

/dev/floppy /mnt/floppy auto noauto,defaults 0 0

To change /etc/fstab so that any user can mount (and unmount) his or her own devices, make sure there's an option "user" in the list of options (the fourth thing on the line between filesystem type and the two 0's at the end of the line) for that device {the "user" option is so user mike can mount his cdrom and then only he can unmount it}.

To make it so that any user can mount any device or unmount any device, add the options "users" to the list of options for that device {the "users" option is so that mike can mount the cdrom but he or any other regular user can unmount it at any time}. Examples:

/dev/floppy1 /mnt/floppy1 auto noauto,defaults,user 0 0

/dev/floppy2 /mnt/floppy2 auto noauto,defaults,users 0 0

For more information on the mount command, type man mount at any shell prompt.

=== Mounting an ISO image ===

Sometimes it is useful to mount an ISO image that you made or have downloaded to be able to access or check the contents. This is possible with the following invocation:

mount -t iso9660 -o ro,loop=/dev/loop0 NameOfISOFile MountPoint

The MountPoint has to be a directory, as described above. You can also [[Making_an_ISO_from_CDROM|make an ISO of an existing CDROM]].

== See Also ==

* [[umount]]
* [[fstab|/etc/fstab]]
* [[Making an ISO from CDROM]]

Mount

2004-08-01T13:40:27Z

Geniarse: fstab see also link

Mozilla

2004-07-25T16:35:25Z

Geniarse: Added ef link and some grammar

'''Mozilla''' was the original code name for the product that came to be known as [[Netscape]] Navigator, and later, Netscape Communicator.

Mozilla.org is a group chartered to act as the virtual meeting place for the Mozilla code. That group is overseen by the Mozilla Foundation.

The Mozilla Foundation, established in July 2003, with start-up support from [[AOL]]'s Netscape division, provides organizational, legal, and financial support for the Mozilla open-source software project. For more information about the creation of the Mozilla Foundation, see [http://www.mozilla.org/press/mozilla-foundation.html this].

==Features==
The Mozilla Suite provides you with a variety of programs integrated into one application, including:

*[[Web browser]]
*[[Email client]]
*[[Newsgroup]] client
*[[IRC]] chat client
*[[HTML]] editor

A standalone browser based on the Mozilla rendering engine, [[Gecko]], is available to the public under the codename: [[Firefox]]. As of now (June 2004), it is at version 0.9 and is stable enough for most uses.

A standalone E-mail client is also being developed, called [[Thunderbird]]. As of now (June 2004), it is at version 0.7.

According to the official roadmap, plans are to replace the monolithic suite by a more modular package composed of at least the browser and E-mail client mentioned above.

==Latest major release==
The latest major version of the suite is Mozilla 1.7. For more information about 1.7, see the:

*[http://www.mozilla.org/releases/mozilla1.7/ Mozilla 1.7 release notes]

==Tips==

===Importing and Exporting Bookmarks===
Go to '''[[Bookmark]]s''' | '''Manage Bookmarks''' | '''Tools''' | '''Import''' or '''Export''' (as the case may be) | Then save (or import) the .html file with the name you want to a directory of your choosing. You can do a similar process using [[IE]] if you want to import you IE "favorites" into Mozilla. IE does it differently though, you go to '''File''' | '''Import/Export''', then basically do the same as above.

===Enabling JVM===
A [[JVM]] is an application which executes java code , in Mozilla it allows you to view [[Java applets]] on the [[internet]]. To enable [[Java applets]] you must first install a [[JVM]] a variety of which are available:

*Sun Java - you most probably want Java2 Standard Edition [http://java.sun.com/j2se/]
*[http://www.mozilla.org/projects/ef/ Electrical Fire] - This is a project linked with mozilla to develop a fast and [[portable]] JVM.

These instructions apply to sun's J2SE though may apply for other JVM.

Assuming you have a JVM installed you must find the path to the plugin directory most likely:

<tt>/usr/lib/java/jre/plugin/i386/ns610-gcc32</tt>

(for [[i386]] architecture have a look around the directory <tt>/usr/lib/java/jre/plugin</tt> if this doesn't apply to you).

Here there should be a file called <tt>libjavaplugin-oji.so</tt> you need to place a link to this file in Mozilla's plugin directory.

'''Single user:'''

<tt>ln -s /usr/lib/java/jre/plugin/i386/ns610-gcc32/libjavaplugin-oji.so /home/'''username'''/.mozilla/plugins/libjavaplugin-oji.so</tt>

'''Multi user:'''

<tt>ln -s /usr/lib/java/jre/plugin/i386/ns610-gcc32/libjavaplugin-oji.so /usr/local/mozilla/plugins/libjavaplugin-oji.so</tt>

Now restart mozilla and try out a java applet: [http://java.com/en/download/help/testvm.jsp]

====Java webstart====
[[Java webstart]] [http://java.sun.com/products/javawebstart/] enables java applications to be run over a network or the internet. To enable Mozilla to handle these files (presuming J2SE-1.4.2 installed):

'''Edit'''|'''Preferences'''|'''Navigator'''|'''Helper Applications'''
Click '''New Type''' and enter details:
[[MIME Type]] - application/x-java-jnlp-file
Description - Java webstart
Open it with - /usr/lib/j2sdk1.4.2_01/jre/javaws/javaws

Now you can try a webstart application, I recommend:
[http://www.sodaplay.com/constructor/beta/ sodaconstructor]

==External links==
* [http://www.mozilla.org Mozilla.org] - Mozilla Foundation
* [http://www.mozillazine.org MozillaZine] - Latest news
* [http://kb.mozillazine.org MozillaZine Knowledge Base] - Wiki with Mozilla related information
* [http://extensionroom.mozdev.org/main.php/Mozilla Extension Room at Mozdev.org] - Collection of extensions for Mozilla