LQWiki - User contributions [en]

Talk:Main Page

2022-01-05T20:01:34Z

Jeremy: response

Some older posts have been moved here: [[Talk:Main Page/archive]] for purposes of readability.

== Set a network interface to promiscuous mode persistently ==

I am running Ubuntu 20.04. Is there a way to set an interface to "promiscuous mode" which persists between reboots?

:All questions should be asked in the forum: https://www.linuxquestions.org/questions/

Addftinfo

2021-12-16T21:55:20Z

Jeremy:

'''addftinfo''' reads [http://en.wikipedia.org/wiki/Troff troff] [[font]] files and adds font metric information that is used by the [[groff]] system.

== External links ==
* [http://man-wiki.net/index.php/1:addftinfo Man Page]

[[Category:Application]]
[[Category:Application:Authoring]]

Main Page

2021-12-15T19:16:10Z

Jeremy:

__NOEDITSECTION__
Welcome to the LinuxQuestions.org Wiki. This site will allow you to not only learn about Linux and Open Source, but will also allow you to share your knowledge. A Wiki is a type of website that allows you the visitor to [[LQWiki:Plunging forward|change the content]].

You are encouraged to participate regardless of your expertise level. Remember that to be helpful you don't need to be technical. You can help edit grammar and spelling, start a stub page or include any bits of knowledge you may have. If you'd like to contribute but aren't sure where to start, there is a list of [[Special:Wantedpages|most wanted]] pages.

'''Note:'''
* To ask a question and get answers, use our [http://www.linuxquestions.org/questions/ Linux forums].

<table border=0 cellspacing=3 cellpadding=3>
<tr><td class=purple valign=top width=50%>

== Linux Sections ==
* [[LinuxIntro]] - how to start with Linux
* [[Linux-Windows Software Equivalents]]
* [[Commands]] - the "vocabulary" of a Linux system
* [[Howto]]s - how to accomplish some tasks
* [[TroubleShooting]] - some problems and their solution
* [[Tips and tricks]] - explore new ideas
* [[InterOperAbility]] ([[Share files with Windows]] etc.)
* [[Networking]] ([[wireless]], [[firewall]]s etc.)
* [[Security]] (like how to [[encrypt a disk]] etc.)
* [[Scripting]] - write your own [[programs]]
* [[Applications]] for your needs
* [[:Category:Distro|Linux Distributions]]
</td>

<td class=purple valign=top width=50%>
== LQ Wiki Sections ==
* '''[[LQWiki:LQ_Central|LQ Central]]'''
** [[LQWiki:LQ_Central#Introduction|Introduction]]
** [[LQWiki:LQ_Central#Guidelines|Guidelines]]
** [[LQWiki:LQ_Central#Getting started|Getting started]]
** [[LQWiki:LQ_Central#Contribute|Contribute]]
** [[LQWiki:LQ_Central#Administration|Administration]]

* [[Special:Allpages|Browse all articles by name]]
* [[Special:Wantedpages|Pages waiting to be written]]
* [http://wiki.linuxquestions.org/index.php?title=Special:Whatlinkshere&target=LQWiki:stub_articles Stub articles that need more content]

</td></tr></table>
__NOEDITSECTION__

Slackware-FAQ

2020-02-18T17:49:01Z

Jeremy: /* Where are the recommended places to get packages? */

=Business=

===What happened to the store?===

The relationship between Pat Volkerding and the store collapsed in 2018.

https://www.linuxquestions.org/questions/slackware-14/donating-to-slackware-4175634729/#post5882751

===How do I support Slackware?===

Patreon:

https://www.patreon.com/slackwarelinux

Cafepress:

https://www.cafepress.com/volkerdi

Paypal:

https://www.paypal.com/paypalme2/volkerdi

=Roadmap=

==When will the next version of Slackware be released?==

The best indicator is the -current changelog. Feature freezes and release candidates are announced there first.

==What's the easiest way to follow the changelogs?==

Vincent Batts has RSS feeds for them, [http://connie.slackware.com/~vbatts/ here].

=Packages=

==How should I keep my system up to date?==

Use the [http://slakfinder.org/slackpkg+.html slackpkg+] extension to Slackware's included ''slackpkg'' tool. Alien Bob's blog has an [http://alien.slackbook.org/blog/introducing-slackpkg-an-extension-to-slackpkg-for-3rd-party-repositories/ introduction]. It handles Slackware's official repository, and several third party ones, including Alien Bob's multilib and ktown repositories, MateSlackBuilds, and others.

==Where are the recommended places to get packages?==

The two major repositories:
* [http://www.slackbuilds.org/ SlackBuilds.org], optionally with the [http://www.sbopkg.org/ sbopkg] frontend and its [http://slackblogs.blogspot.com/2014/01/managing-sbo-dependencies-easily.html?_sm_au_=iVVD30DNM57QRq75 sqg] queue generator
* [http://www.slacky.eu/ Slacky]

Slackware's contributors:
* [http://rlworkman.net/ Robby Workman]
* [http://alien.slackbook.org/dokuwiki/doku.php?id=start Eric "Alien Bob" Hameleers] (particularly for Steam, VLC and LibreOffice)

Slackware's package-compatible fork(s):
* [http://www.salixos.org Salix OS]

==How do I get GNOME?==

There are several active projects providing variants of GNOME for Slackware:

* [http://mateslackbuilds.github.io/ MATE SlackBuilds]
* Cinnamon SlackBuilds ([http://www.linuxquestions.org/questions/slackware-14/call-for-testers-cinnamon-slackbuilds-4175501059/ discussion thread])
* Dropline GNOME ([http://www.linuxquestions.org/questions/slackware-14/dropline-gnome-3-8-testing-packages-4175459688/ discussion thread])

==How do I get LXQt?==

Use [https://idlemoor.github.io/slackrepo/ slackrepo] to build and install it from [https://notabug.org/SlackDesk/LXQt Skaendo's Slackbuilds].

Reference:
https://www.linuxquestions.org/questions/slackware-14/building-latest-lxqt-0-14-in-slackware64-current-4175647708/#post5998981

==How do I get LXDE?==

Get it from Ponce. He provides prebuilt packages and SBOPkg queues:

http://ponce.cc/slackware/

Here is the discussion thread:

:[http://www.linuxquestions.org/questions/slackware-14/lxde-desktop-for-slackware-13-1-testing-810047/ LXDE desktop for slackware - testing]

==How do I get the latest JDK?==

Either use the SlackBuild in extra/java to build the Sun JDK package, or download an OpenJDK package from Alien Bob.

==How do I tell slackpkg to not replace Alien Bob's packages?==

Alien Bob's KDE and multilib packages replace many stock Slackware packages. You'll have to blacklist them to prevent slackpkg from reverting them.

To do so, put the following in /etc/slackpkg/blacklist:

:<tt>[0-9]+alien</tt>

==How do I get a newer Firefox?==

Slackware-stable includes Firefox ESR, while Slackware-current includes the latest.

On Slackware-stable, the easiest option is to use the following script to download and package the latest Firefox binaries:

https://gist.github.com/ruario/9672798

==How do I figure out package dependencies?==
===How do I figure out dependencies for Slackware packages?===

The truth is that you're not supposed to. The first time you logged into your new Slackware installation, you received an email explaining, among other things, Slackware's approach to package management:

<blockquote>''Slackware is designed around the idea that the system should be a complete installation kept updated with any official patches. This avoids the mess of dependencies that some other Linux based GNU systems face.''</blockquote>

===How do I figure out dependencies for third party packages?===

Repositories such as SlackBuilds.org and Slacky.eu list dependencies for each package. If you need to install several SlackBuilds.org packages in order, then queue them in sbopkg.

===Why do you use Slackware if you need to figure out dependencies?===

As you've seen above, this is (to a large extent) a misconception. See also:

[http://docs.slackware.com/slackware:package_and_dependency_management_shouldn_t_put_you_off_slackware Package and dependency management shouldn't put you off Slackware]

==Why does Slackware have TeTex and not Tex Live?==

The official answer is that Tex Live is too large to include.

See here:
:http://www.linuxquestions.org/questions/slackware-14/tex-live-in-slackware-635217/#post3122767

You can get Tex Live from third parties such as SlackBuilds.org and Robby Workman, or directly from https://www.tug.org/texlive/.

=Setup=

==How do I create a UEFI boot USB?==

See here:

https://www.linuxquestions.org/questions/slackware-14/easiest-way-to-make-a-current-uefi-boot-usb-4175551386/#post5409238

==Which groups do I need to belong to?==

When '''adduser''' asks you this question, press the Up cursor key. It will automatically populate the list.

Typically, you want to belong to:
*audio - access to audio devices
*cdrom - access to cdroms/dvds
*floppy - access to floppy drives
*plugdev - access to flash drives
*video - access to framebuffer devices (/dev/fb0)
*power - allows users to control HAL suspend, hybernate, and shutdown
*netdev - allows users to control wicd for wireless networking

The correct list sometimes changes with Slackware version upgrades, so see CHANGES_AND_HINTS.TXT for updated information.

==How should I set up networking (wireless or otherwise)?==

Slackware provides NetworkManager. Turn it on. There's a note about this in the email you get the first time you log in as root:

Read the following too:
:http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:network

==How do I get a graphical boot sequence?==
Please see the following How-to: [[Slackware-Guides-Graphical_Boot]]

==How do I get CPU frequency scaling?==
Change "CPUFREQ=battery" to "CPUFREQ=on" in /etc/rc.d/rc.modules.

Please remember that very CPU-intensive applications, such as Adobe Flash, will not perform well with a downclocked CPU.

==How do I set my default web browser?==

Some options here:

https://www.linuxquestions.org/questions/slackware-14/how-to-set-default-browser-700564/#post6002604

=Audio=

==How do I get audio working?==

The initial checklist goes something like this:

# Is your user account a member of the audio group?
# Have you run alsamixer to set your volume levels, which may be muted and/or zeroed by default?
# Have you run '''alsactl store''' to save your volume settings?

Carry these out before asking this question, and when you ask, mention that you've done so.

Other steps, such as setting module options or creating an asoundrc file, might be required in special cases.

==How do I get set up Pulseaudio?==

# Install [http://slackbuilds.org/audio/pulseaudio/ Pulseaudio] and [http://slackbuilds.org/libraries/alsa-plugins/ alsa-plugins]
# Put the following in /etc/sound.conf or ~/.asoundrc:

<tt><CODE><PRE>
pcm.pulse {
type pulse
}

ctl.pulse {
type pulse
}
</PRE></CODE></tt>

=Bluetooth=
==Where do I start?==
If all you want is the most direct route to getting bluetooth working under a window manager, try out the Blueman gui tools distributed with Slackware.
*blueman-applet - Gives you a system try icon with access to all the other blueman tools
*blueman-manager - A nice gui for managing the pairing of your devices
*all other blueman - You shouldn't have to run them directly. They will be called for appropriately from blueman-applet/manager

==That's Nice, but I want to do it from the command line==
The old way is to use root access with hidd, hcitool, obexftp. It 'works' and is fine if you don't do a lot of bluetooth. However, I wouldn't try to pair your mouse with it and use it on a regular basis. The new way is through D-Bus/Hal. Neither is within the scope of an FAQ.

=X and Desktop=

==How should I set up an NVidia card?==

Use the SlackBuilds.org packages: nvidia-kernel, libvdpau and nvidia-driver: installed in that order.

If you're using NVidia's installer on -current, see here:

https://www.linuxquestions.org/questions/slackware-14/the-latest-nvidia-linux-driver-release-4175608923/page7.html#post6005347

==How do I get Slackware to boot straight into X?==

Edit /etc/inittab and replace:

:<tt>id:3:initdefault:</tt>

with

:<tt>id:4:initdefault:</tt>

==How can I avoid crashes when I log out?==

This happens to some people who use KDM.

Uncomment (remove the hash from) the ''#TerminateServer=true'' line in '''/etc/kde/kdm/kdmrc''' to solve it

==How do I keep my GTK theme when I'm not in Xfce?==

Either run '''xfsettingsd''' in the background, or use a GTK theme switcher. Examples are '''gtk-chtheme''' and '''LXAppearance'''.'

==How do I make my Qt applications look like my KDE applications?==

The following applies to Slackware:

[https://wiki.archlinux.org/index.php/KDE#KDE_and_Qt_programs_look_bad_when_in_a_different_window_manager KDE and Qt programs look bad when in a different window manager]

Symlinking /usr/lib64/kde/plugins/styles to /usr/lib64/qt/plugins/styles (on a 64-bit installation), or /usr/lib/kde/plugins/styles to /usr/lib/qt/plugins/styles (on a 32-bit installation) works.

==How do I make KDE 4 faster?==

Just wait for strigi's indexing operation to finish. Disable strigi and nepomuk if you don't want to wait; the options are in KDE's System Settings.

==How do I make my Arial font look like an Arial font?==

Slackware, being a commercial product, cannot ship with Microsoft's core fonts for the web. These include Arial, Courier New, and Times New Roman. Instead, Slackware displays Liberation fonts (Liberation Sans, Liberation Mono and Liberation Serif, respectively) in their place.

To change this, you need to install Microsoft's web core fonts from a third party repository such as SlackBuilds.org, remove the Fontconfig file doing the substitution (it's /etc/fonts/conf.d/60-liberation.conf), and run fc-cache to refresh Fontconfig.

==Where is my Adobe Helvetica font?==

Disabled.

Details and explanation are in the patch applied:

:source/x/fontconfig/fontconfig.font.dir.list.diff.gz

==How can I make my fonts look better?==

Start here:

:[http://duganchen.ca/writings/slackware/fonts Optimizing Slackware Linux's Fonts]

=Applications=

==How do I get MP3 support in Amarok and/or H264 support in Firefox?==

Install the gstreamer plugins:

* [http://slackbuilds.org/multimedia/gst-plugins-bad/ gst-plugins-bad]
* [http://slackbuilds.org/multimedia/gst-plugins-ugly/ gst-plugins-ugly]
* [http://slackbuilds.org/multimedia/gst-ffmpeg/ gst-ffmpeg]

Amarok, Firefox (the version included with Slackware) and other applications should then have full multimedia support.

==How can I watch DRM'd Flash (e.g. Amazon Prime and paid Youtube) videos?==

You need HAL, which has not been included since Slackare 13.37. You can choose to do one of the following:

a) Install the HAL packages (hal and possibly hal-info) from Slackware 13.37. Make sure HAL is running by starting /etc/rc.d/rc.hald.

b) Install [http://slackbuilds.org//system/hal-flash/ hal-flash]

See here for more information, including a link to a test page:

https://helpx.adobe.com/x-productkb/multi/flash-player-11-problems-playing.html

=Slackware64=

==How should I run 32-bit software in my 64-bit installation?==

:http://connie.slackware.com/~alien/multilib/

==How can I get my 32-bit software to see my GTK theme?==

First build and install 32-bit compatibility versions of the GTK engines that your themes use. To build one for ''murrine'', for example, first build a normal 32-bit package (a 32-bit Slackware installation running in a virtual machine is useful for this). Then move it to your 64-bit installation and run ''convertpkg-compat32'' on it to create a 32-bit compatibility package. Install that package.

Set the GTK_PATH environment variable to /usr/lib/gtk-2.0 before launching 32-bit GTK programs. Its default setting of :/usr/lib64/gtk-2.0, by contrast, is correct for 64-bit programs.

The launchers for Adobe Reader (''acroread'') and Realplayer (''realplay'') are shell scripts, so you can edit them and add "export GTK_PATH=/usr/lib/gtk-2.0" to their beginnings.

Talk:Software Repo / Package Manager FAQ

2019-10-04T14:36:58Z

Jeremy: Blanked the page

Software Repo / Package Manager FAQ

2019-10-04T14:36:45Z

Jeremy: Created page with "== Preamble == The purpose of this wiki article is to guide users on diagnosing problems with installing, upgrading and/or removing software packages using package managers...."

== Preamble ==

The purpose of this wiki article is to guide users on diagnosing problems with installing, upgrading and/or removing software packages using package managers. This sticky thread is intended to cover problems that arise with software repositories causing problems with the installation, or updating of software packages. It is '''not''' intended to guide readers on merely installing, updating, or removing Linux software from Linux systems, be that through software packages, or via other means. There is some resources in the "More Resources" section at the end of this wiki article regarding such matters. It also does '''not''' cover all possible issues that could arise with [https://en.wikipedia.org/wiki/Package_manager package managers] and/or software packages.

This sticky is '''not''' intended to be a "how-to" guide as such, nor is it intended to replace your own troubleshooting; it is intended to provide some ideas on how you might troubleshoot problems involving software repositories, as well as some ideas and tips on some common causes of such problems, as well as some possible solutions to those problems.

There is also some general background on packages managers below the next section. This explains some fundamentals that should be understood when dealing with package managers – particularly when trying to solve problems related to package managers and/or software packages.

'''Note:''' This wiki article is by no means a complete guide to package managers, software packages, or software repositories; more information can be found in the "More Resources" section at the end of this wiki article.

== Common package manager issues ==

Some common problems with installing/updating software packages, stem from incompatible software repositories being enabled. This may be a repository meant for a different version of the Linux distribution you're using (or a different Linux distribution entirely) - such as having repositories for CentOS 7 enabled on CentOS 6, for example.

Probably a more common problem would be "third party software repositories" that have different versions of shared libraries that are also included in your Linux distribution's official software repositories. This can cause major problems, and can very easily lead to something known as "[https://en.wikipedia.org/wiki/Dependency_hell dependency hell]". This means your package manager cannot satisfy the dependencies for the package(s) you're trying to install, without breaking the dependencies for packages that are already installed - thus you cannot install or update the packages you're trying to install or update. Therefore the package manager is unable to "resolve the dependencies". This is more likely than not caused by having repositories enabled that have the same packages, but different versions of those same packages - this will lead to confusion for your package manager. This will very likely cancel out the installation/update, and therefore your package manager cannot proceed with the installation and/or update.

=== How to determine if you are facing a problem with enabled software repositories ===

The first step is to examine any error messages from your package manager. This will often give you some clues as to the nature of the problem you're facing.

If you have '''not''' added any additional software repositories to your package manager's "repolist", and you're seeing messages indicating you may have conflicting software package versions, check the following points;

'''*''' If it's mentioning the same package(s) name(s), but different versions in different software repositories you have enabled; then you probably have a conflict and your package manager is having problems resolving the package dependencies.

'''*''' Check to see if the official repositories for your Linux distribution have the same packages you're having trouble with in them. If they do, then this could be causing a conflict.

If you have added any third party repositories to your package manager's "repolist", then check the following points;

'''*''' Ensure that any third party software repositorie(s) you may have enabled in your package manager, are the correct version(s) for your Linux distribution. If this is not true, then this could be the problem.

'''*''' Check if more than one enabled third party software repository(s) contains a package(s) with the same name in them, and particularly if it's mentioned in any error messages your package manager is giving you when you attempt to install or update packages that you're having problems with. If this is true, then you have a conflict on your hands.

'''Note:''' How you check the above dot points is dependant on your package manager, so there is no single answer to this question. Check the following sections, as well as the "More Resources" section at the end of this wiki article for further information.

=== I believe I have a problem related to enabled software repositories, what do I do? ===

The answer to this really depends on both your Linux distribution, as well as the software repositories involved, and particularly how far advanced the situation is.

The general solution would be to remove the offending software repositorie(s) from your package manager's "repolist". You should also consult your Linux distribution's website for a list of official repositories, to figure out which are "third party software repositories", and which ones are official repositories.

If your problems are too advanced; the "safest" and/or the most "viable" solution may be to backup any important data to external media, then do a complete reinstall of your system; therefore, starting off with a "clean installation".

If your situation is very advanced; you can try removing all but official repositories, then forcing an update of all "base packages" for your distribution, but there is no guarantee this will solve your problems.

If you are still unsure at this point, then it may be time to post a question here at LQ for further assistance with your problem. See "What information should I include when posting a question about software package problems?" below for the information LQ members will require to be able to help you solve the issue.

'''Note:''' This "repolist" may go by a different name, such as "software sources", or similar, depending on your package manager/frontend. It’s advisable to actually ''remove'' the relevant line(s) listing the offending software repositorie(s) from your package manager’s "repolist", rather than just "disabling" the offending software repositorie(s).

=== What information should I include when posting a question about software package problems? ===

The following information will help LQ members figure out what might be the reason(s) for your problems. Because without this information, we are really just guessing, and this does not help you solve your problem. Please also use [https://www.linuxquestions.org/questions/misc.php?do=bbcode#code CODE tags] when posting terminal output, as this makes it much easier for LQ members to read, and separates comments from command output.

'''*''' The name of the package(s) you're trying to install/update/remove

'''*''' The name and version of your Linux distribution

'''*''' A listing of enabled software repositories on your system

'''*''' Any error messages from the package manager/frontend

=== How can I get a list of software repositories enabled on my system? ===

While there are graphical ways of getting this information, because there are many different package managers, different Linux distributions use different package managers, the easiest way is via the terminal. Because there are many different package managers, there is no single answer to this question. Therefore, it will depend on both your Linux distribution, as well as the package manager concerned. If your package manager has an option for this (not all of them do), the best place to look would be at the manual pages for your package manager. You can type the following into a terminal window to bring up the manual page:

'''man <name of package manager/frontend here>'''

Replace '''<name of package manager/frontend here>''' with the actual name of your package manager/frontend, such as [https://linux.die.net/man/8/apt apt], [https://linux.die.net/man/8/apt-get apt-get], [https://linux.die.net/man/8/yum yum], [https://fedoraproject.org/wiki/DNF?rd=Dnf dnf], etc.

'''Note:''' Some distributions don't install the manual pages by default, in this case, you should consult your distribution's website.

There is also a separate utility that can list the repositories in your package manager's "repolist". If you have '''inxi''' installed on your system, you can run the following command from the terminal;

'''inxi -r'''

It does not matter which terminal program you use, nor which shell your system uses by default.

== Why packages managers and software packages? ==

It's worthwhile to understand why we have package managers and software packages. Package managers provide a ''consistent'' way to install, update, and remove software on/from Linux systems. This is because software packages not only contain the pre-compiled version of software, but also usually check to see what else needs to be present on your system for the software in question to work. This is known as "dependency resolution"; in other words, the package manager checks the package's metadata to see which [https://en.wikipedia.org/wiki/Library_(computing) dynamic libraries], and other software needs to also be installed. If a program uses dynamic/shared libraries that are contained in a different software package(s), then that other package(s) is said to be a "dependency". The package(s) you're trying to install/update "depend" on that other package(s) to work. The package metadata also contains information about what files are contained within the software package(s), where on the filesystem those files should be installed to, what permissions should be assigned, what scripts should be run when the package(s) are installed, what services should be started, etc. The package manager keeps this information in a database on your system, so it can keep track of what files belong to what packages, what changes are made and alike. Linux package managers/frontends are a precursor to "app stores" for smartphones and the like.

Some Linux distributions (for example Crux, Gentoo) are source-based. They download source code and build the binary package locally, often with specific optimizations for your hardware. Surprisingly, their package managers function in exactly the same way as package managers do in binary-based Linux distributions. There is a high-level frontend that downloads the package from the repository together with any other packages on which it is dependent, and a low-level package manager that unpacks the sources, builds the packages, and installs them. The main difference is that each package includes a simple script which gives the package manager the instructions for the build.

'''Note:''' It's important to understand that software packages can also contain other types of files as well; they can (and often do) contain files like configuration files, wallpapers, etc.

=== Package manager "frontends" ===

Package manager "frontends" provide functions that the package manager itself does not, for instance, dealing with software repositories. An example of a package manager "frontend" would be yum; yum can both download packages from an online or local repository, and install, update and remove packages. yum uses the [https://linux.die.net/man/8/rpm rpm package manager] (Redhat package manager) "behind the scenes"; the rpm package manager is the actual package manager in that example; it keeps a database of installed packages. So the rpm package manager is a "dependency" of yum, because yum calls on the rpm package manager to actually "manage" installed packages.

=== Third party software repositories ===

Third party [https://en.wikipedia.org/wiki/Software_repository software repositories] are software repositories that are maintained by a third party and are beyond the control of your Linux distribution's developers. Therefore your Linux distribution can make no guarantee that it will not cause problems; more importantly, adding such repositories increases the possibility that you may encounter package dependency problems.

[https://help.ubuntu.com/community/PPA PPA’s] (Personal Package Archives) are also an example of a "third party software repositories", and are even more risky. Some of the risks involved with PPA’s are security related, as well as whether or not packages contained within will continue to receive updates, particularly security updates. There is also the risk of who exactly is behind said PPA(s), and how much testing has gone into the software concerned, as well as the experience the maintainer of said PPA have.

It's advisable to keep third party repositories to an absolute minimum, and only use ones that are known to not be problematic. Your Linux distribution's website is usually a good source for such information. The bottom line is that, if you go overboard with adding third party software repositories, then you are very likely to have serious problems. This can also lead to what's known as a "frankendistro". In other words, and as an example (but not limited to), Debian stable that's not really Debian stable, but a mixture of Debian stable and Debian testing.

The best rule of thumb is to only use "third party repositories" when there are no suitable packages for the software in question in the official repositories for your Linux distribution, and to only use trusted repositories. Even then, it is safer to build the package from source if you can. That will ensure that it is linked to the library versions that your system provides.

'''If in doubt, don’t add it!'''

'''If you play with fire, you're likely to get burnt!'''

== Installing software via package manager's vs from sources ==

Before one can use software written in a compiled programming language, it must be "converted" from human readable code (aka "source code") to machine code instructions for your computer's processor to be able to "see" it as a set of instructions to perform a specific task. So when we say something like "building it from source", this is what we mean, in other words; you would use a compiler to "compile" the source code to machine code instructions.

In binary-based Linux distributions, the developers of said distributions have already done the above for you, and put the end result into "software packages". You should therefore in this case, be able to simply tell your package manager to install the relevant package(s). This will therefore install the pre-compiled binary version of said software onto your system, and therefore you can start using said software, as at this point, it already has been "converted" into machine code instructions that your computer's processor understands to be a set of instructions.

Further information about this topic can be found in the "More Resources" section below, as further details are beyond the scope of this wiki article.

=== A note about managing software that has been installed from source ===

A problem with building software from source by hand is that the package manager then knows nothing about it because it was installed independently. Therefore the package manager cannot "manage" the updating or removal of that software. To bridge this gap, there are some extra tools such as "[http://porg.sourceforge.net/ porg]" you can install, that will record information about that software's installation in a separate database. This is not an issue in a source-based distribution which uses its package manager to download and build automatically from source.

== More Resources ==

'''*''' [https://www.linuxquestions.org/questions/blog/hazel-1029471/package-managers-and-how-to-use-them-37648/ Package Managers and how to use them]

'''*''' [https://www.linuxquestions.org/questions/blog/hydrurga-443802/manage-your-software-sources-in-debian-ubuntu-and-mint-38002/ More information about software repositories for Debian, Ubuntu and Linux Mint]

'''*''' [https://wiki.debian.org/DontBreakDebian Don't break Debian]

'''*''' [https://www.lifewire.com/guide-to-linux-packages-2202801 A guide to Linux software packages] - The basics remain the same, but Fedora has moved to dnf

'''*''' [https://wiki.centos.org/AdditionalResources/Repositories Additional software repositories for CentOS] - A list of third party repositories available for CentOS

'''*''' [https://www.unixmen.com/enable-disable-repositories-centos/ How to enable and disable repositories on CentOS]

'''*''' [https://help.ubuntu.com/community/AptGet/Howto Ubuntu's apt-get how-to guide]

'''*''' [https://access.redhat.com/sites/default/files/attachments/rh_yum_cheatsheet_1214_jcs_print-1.pdf yum cheatsheet]

'''*''' [https://www.thegeekdiary.com/beginners-guide-to-yum-configuration/ A beginners guide to yum configuration]

'''*''' [https://linuxhint.com/debian-package-creation-howto/ Create your own Debian software packages]

'''*''' [https://debian-handbook.info/browse/stable/debian-packaging.html Creating a Debian package]

'''*''' [https://linuxconfig.org/how-to-create-an-rpm-package How to create your own rpm packages]

'''*''' [https://developers.redhat.com/blog/2019/03/18/rpm-packaging-guide-creating-rpm/ rpm packaging guide from Redhat]

'''*''' [https://access.redhat.com/documentation/en-us/red_hat_network_satellite/5.4/html/channel_management_guide/chap-channel_management_guide-building_custom_packages Building custom rpm packages]

'''*''' [https://en.wikipedia.org/wiki/Source_code Source code]

'''*''' [http://www.linuxandubuntu.com/home/basics-of-compiling-software-from-source-code-in-linux/ Basics Of Compiling Software From Source Code In Linux]

'''*''' [https://www.wired.com/2010/02/Compile_Software_From_Source_Code/ Compile Software From Source Code]

EtcPasswd

2016-08-16T22:26:08Z

Jeremy: Reverted edits by Nehaahuja (talk) to last revision by Cargod hera

The "/etc/passwd" file in Linux is a text file that contains infomation on all system users. It typically shows file system permissions of each user, the user ID number and group ID number as well as the login directory and user default shell (terminal program).

Contrary to the belief of some, this file does not show user passwords in most systems. While the linked database does store user passwords, this text file will generally show an "x" in the place of the validation used to log a user in.

User:Dedec0

2015-11-11T15:44:27Z

Jeremy: Created page with "Test"

Test

Talk:Main Page

2014-10-23T18:49:47Z

Jeremy: /* Incomplete License Notice */

Some older posts have been moved here: [[Talk:Main Page (archive)]] for purposes of readablity.

==SPAM==
* We've had a sudden rash of spam and I've installed some additional anti-spam measures as a result. If anyone notices any kind of collateral damage, please let me know ASAP. [[User:Jeremy|Jeremy]] 18:34, March 12, 2011 (UTC)

==Upgrade==
* Just upgraded to the latest version of MediaWiki (1.15.1). If you run into any issues, let us know. [[User:Jeremy|Jeremy]] 18:15, February 27, 2010 (UTC)

==Facebook Connect==
Testing fbconnect [[User:693221900-fb|693221900-fb]] 00:12, March 1, 2010 (UTC)

==Edit Note==
* Edits were disabled for about 12 hours while we addressed some spam issues we were having. We've made a couple minor changes and haven't gotten any additional spam in the 4 hours since we enabled edits. We'll keep an eye on things from here - thanks for the patience.
:Just made some additional changes to try and slow down the current spam attack. If needed we will temporarily disable edits again. [[User:Jeremy|Jeremy]] 15:32, October 10, 2007 (EDT)
::We've added some additional spam filtering - thanks for the patience. [[User:Jeremy|Jeremy]] 18:19, October 30, 2007 (EDT)
:::Seems to have worked, current spam comes from "contributors" who have registered months ago. --[[User:ThorstenStaerk|ThorstenStaerk]] 00:44, November 5, 2007 (EST)
::::I noticed this also, it's an odd pattern. We have two pending code updates that should help alleviate some of this. [[User:Jeremy|Jeremy]] 10:12, November 9, 2007 (EST)
:::::Have you noted we have 18491 users according to http://wiki.linuxquestions.org/index.php?title=Special:Listusers&limit=500&offset=18000
::::::I've been addressing some of the ones that are clearly spam. Thanks. [[User:Jeremy|Jeremy]] 15:23, November 9, 2007 (EST)

==Suggestions for links==
* Other Linux wikis, most notably (according to Alexa traffic rankings): [http://en.linux.wikia.com/wiki/Main_Page linux.wikia.com], [https://wiki.ubuntu.com wiki.ubuntu.com], [http://wiki.debian.org/ wiki.debian.org], [http://gentoo-wiki.com/Main_Page gentoo-wiki.com] and last but not least (because LQ is home to the official Slackware forum) [http://slackwiki.org/Main_Page slackwiki.org]. -- [[User:Marsm|Marsm]] 05:27, May 28, 2007 (EDT)
* [[HOWTO]] section
* [[Performance]]
*:Can someone please add [[Performance]] to the main page, it seems like here would be a better place for it rather then at the end of the "gaming" page. [[User:SciYro|SciYro]]
*:: I agree Performance could be added, but please make sure the size of the main page is reduced for readability. I would remove [[distributions]], [[People]] and [[Programming]] --[[User:ThorstenStaerk|ThorstenStaerk]] 04:35, February 17, 2007 (EST)
*:::I just added a link to performance in [http://wiki.linuxquestions.org/wiki/Linux_installation#Configuring_Linux Linux_installation], that seems like a good place for it. You could also integrate a link to it from the [[Common_Tasks]] page imo. There is much room for improvement of course in the organisation/cleanness/readability of the [[installation]] or [[Common tasks]] pages right now, but i think one could easily find its way to the performance page from those places, or maybe even from the [[hardware]] page.
*:::I don't know if the link will be put on the main page but for now that should be a good start. my two cents. [[User:Questynux|Questynux]] 06:00, February 17, 2007 (EST)

* Where's the best place for cronic hardware/kernel problems? There is a largish problem revolving around APIC (not ACPI) timing issues under various linux kernels that cause the machine to freeze up hard. I'd like to add information about that, and I'm sure there are other cronic issues that deserve to have some space in the WIKI as well. -Scott Miller (5mi11er)
: [[troubleshooting]] and [[apic]]. --[[User:ThorstenStaerk|ThorstenStaerk]] 13:18, November 12, 2009 (UTC)

==Spam links==
Just deleted what appeared to be spam links to german horoscope sites. If those were legit, someone let me know. [[User:Crazyeddie|Crazyeddie]] 03:19, Jul 3, 2004 (EDT)
:That's ok - In order to assess the appropriateness of material, all content must currently be in English, and any external sites which are linked to must also be English language based - [[LQWiki:Policies#General_policies|General policies]]
:-- [[User:Skyline|Skyline]] 06:23, Jul 3, 2004 (EDT)

==Advocacy article==
Should there be an Advocacy section linked from the Main Page?
--[[User:Bunyip|Bunyip]] 08:52, Jul 23, 2004 (EDT)

=== Importing Advocacy article from Linux Documentation Project ===
[[User:Crazyeddie|Crazyeddie]] 11:54, Jul 23, 2004 (EDT):Perhaps, but an Advocacy article doesn't exist yet. There's an advocacy article over at the [http://www.tldp.org Linux Documentation Project], but we would have to get permission from the author of the article, because it looks like their license is not compatible with Creative Commons. Here's the copyright info:

===TLDP Advocacy HOWTO's copyright information===
This mini-HOWTO is Copyright © 1996-2000 by Paul L. Rogers. All rights reserved.

A verbatim copy may be reproduced or distributed in any medium physical or electronic without permission of the author. Translations are similarly permitted without express permission if it includes a notice on who translated it.

Short quotes may be used without prior consent by the author. Derivative work and partial distributions of the Advocacy mini-HOWTO must be accompanied with either a verbatim copy of this file or a pointer to the verbatim copy.

Commercial redistribution is allowed and encouraged; however, the author would like to be notified of any such distributions.

In short, we wish to promote dissemination of this information through as many channels as possible. However, we do wish to retain copyright on the HOWTO documents, and would like to be notified of any plans to redistribute the HOWTOs.

We further want that all information provided in the HOWTOs is disseminated. If you have questions, please contact Tim Bynum, the Linux HOWTO coordinator, at linux-howto@sunsite.unc.edu.

===Responses===
: The "Derivative work and partial distributions of the Advocacy mini-HOWTO must be accompanied with either a verbatim copy of this file or a pointer to the verbatim copy" bit would seem to indicate that we could add the HOWTO(s) to the wiki (it would become a "Derivative work" after the first edit), as long as we include a link to the original verbatim copy, which should not be a problem.
: [[User:Jeremy|Jeremy]] 15:27, Jul 23, 2004 (EDT)

:Yes, but could we in good faith release it under the Creative Commons and let others reuse it from us? I think you might be right, but I would feel better if we got explicit permission from the author. At least there is a single author, unlike most Wikipedia articles. I was planning on trying to incorporate TLDP HOWTOs, as soon as I got to a certain point in the [[Jargon File]] incorporation, so I've had some time to think about this. Do you have any contacts at TLDP, or should I just email the guy myself? [[User:Crazyeddie|Crazyeddie]] 18:34, Jul 23, 2004 (EDT)

===TLDP manifesto===
:: Looking at http://www.tldp.org/manifesto.html I see:
"5. LICENSE REQUIREMENTS

Anyone may copy and distribute (sell or give away) LDP documents (or other LDP works) in any media and/or format. No fees are required to be paid to the authors. It is not required that the documents be modifiable, but it is encouraged.

You can come up with your own license terms that satisfy these conditions, or you can use a previously prepared license. The LDP has a boilerplate license that you can use if you wish. Some people like to use the GPL, while others write their own. There is a project underway to create a special GPL license just for documents and this may turn out to be a good choice.

The copyright for each document should be in the name of the principal authors. "The Linux Documentation Project" isn't a formal entity and thus can't be used as a copyright owner. "

===Responses===
::This seems to fit exactly in with what we want to do. I'll contact TLDP just to verify, however. I'll post the outcome here.
:: [[User:Jeremy|Jeremy]] 00:53, Jul 24, 2004 (EDT)
::: After discussing this with TLDP, I am going to revisit the ability to add GFDL items to the LQ Wiki. Stay tuned. [[User:Jeremy|Jeremy]] 12:17, Jul 25, 2004 (EDT)

How would that work? I thought that the Creative Commons/GFDL incompatibility was pretty well established. "East is East and West is West, and ne'er the twain shall meet." As the GFDL and the CC are presently written, material under one can't be released under the other without the permission of the copyright holder (the original author in most cases). There's rumors that the FSF and the Creative Commons people are working on that issue, but until then, we're pretty well stuck with just asking for permission. Not that I would ''mind'' an easier solution, but I just don't think it's possible.[[User:Crazyeddie|Crazyeddie]] 16:40, Jul 26, 2004 (EDT)

:It would work something like this. When you enter in a doc, there would be a "this is GFDL" checkbox. That doc would then be under the GFDL and *not* the CC. There are a few problems with this, and it could get complicated quite quickly, so It's not a definite addition at this point, just somehting we are exploring. [[User:Jeremy|Jeremy]] 17:50, Jul 26, 2004 (EDT)

Hmmm. That would be possible if it was a new article, and that the changes made to it were also GFDLed. But it would lead to some articles being GFDL, some being CC. A hack, but we're kinda in a corner. I think we'd still be better off contacting the original authors and getting CC permission, since this would increase the number of options available to downstream users (they would be able to use our version under the CC and the original under the GFDL), but I'd be willing to go along if there is consensus for it. [[User:Crazyeddie|Crazyeddie]] 15:32, Jul 27, 2004 (EDT)

Jeremy, if you're still seriously considering dual-licensing, you might want to look at this first: http://en.wikipedia.org/wiki/Wikipedia_talk:Creative_commons_migration Keep in mind that I did not seriously expect this to be accepted, I was more trying to raise awareness of the problem. I would not have even suggested it if I hadn't (which I still do!) believed that the Creative Commons by-sa license is superior to the GFDL. [[User:Crazyeddie|Crazyeddie]] 19:06, Aug 2, 2004 (EDT)

----
How about changing the notice at the bottom of each edit page to ... "WITHOUT PERMISSION from the authors to post under LQWiki's [http://creativecommons.org/licenses/by-sa/1.0/ Creative Commons] license." You should add that each page is owned by the authors listed in its history. [[User:TomFrayne|TomFrayne]] 09:58, Jul 24, 2004 (EDT)

===Crazyeddie's extended post===
(added sectioning for readability) That would be an ugly hack. I think I'd rather roll our own HOWTOs than go through that. Anyway, I'm looking at this from the point of view of a general solution rather than just importing this one article. Some reasons I think we should contact the article authors and ask for explicit permission:
#The Manifesto is a suggestion or a guideline for the TLDP contributors to use when deciding what licensing scheme to use. It doesn't look like they're too big on enforcing it, or at least a few of the older articles didn't even bother appending a license. It is not a license in and of itself.
#Even if the contributors do follow the Manifesto's guidelines, they don't have to allow modifications.
#They may have released in under a copyleft modifiable license that isn't compatible with the Creative Commons such as the GFDL. I'm not sure, but I don't think the GPL is Creative Commons compatible either.
#Like the manifesto says, the LDP is not the copyright holder, so they can't unilaterally give permission.
#Even if we could use an article without permission, it would be good form to tell the author about it. For example, if the author can no longer maintain or host the original, he or she could tell their users where they could go to get an updated copy. It occurs to me that the LDP could see us as competition. It might be a good idea to stress that they can backport any changes under the Creative Commons. Anybody else have any ideas that might smooth the path?
#Letting an experienced technical writer know about this wiki is a Good Thing. This subproject gives us a good excuse.

:If you would like to start contacting authors of articles you think should be added, please feel free to do so. If you need anything from our end, let me know. [[User:Jeremy|Jeremy]] 17:54, Jul 26, 2004 (EDT)

:Okay. I'll use Talk:Linux Documentation Project as a sort of improvised "command center" in case somebody else wants to help out/take over. A good first step would be to send off a general email to their mailing list. (I'll make sure that I mention that I'm doing this as my own intiative, not as an 'offical' LQwiki project.) If you don't think it's confidental or something, could you send me a copy of the correspondence you had with them? After the general email, I'll try contacting the Advocacy HOWTO's author. If anybody has suggestions on what to incorporate next, head over to the LDP talk and let me know. [[User:Crazyeddie|Crazyeddie]] 15:23, Jul 27, 2004 (EDT)

:I have a draft email up on Talk:Linux Documentation Project. Please go idiotproof it everybody! [[User:Crazyeddie|Crazyeddie]] 16:14, Jul 27, 2004 (EDT)

::Seems completely idiotless. :) [[User:Digiot|Digiot]] 17:17, Jul 27, 2004 (EDT)

I'm placing the email on hold until I can rewrite it, to reflect my promotion to moderator. (Since I'm now moderator, it pretty much has to be an offical LQwiki project.) Also, it occurs to me that Grokdoc might want in on this. [[User:Crazyeddie|Crazyeddie]] 19:10, Aug 2, 2004 (EDT)

:Have a list of LDP howtos up over at Talk:Linux Documentation Project. Take a look over and let me know if there is a howto you want me to put on the to-do list. [[User:Crazyeddie|Crazyeddie]] 18:50, Jul 28, 2004 (EDT)

::Seems like to me the best principle would just be to prioritize them into 'niche interest' and 'outdated for a reason' and then take the remaining generally important and relevant topics and do them in chronological order. A major problem is outdated data and attacking that first would probably be most useful and most suited to wikification. Also, those authors who have abandoned or rarely update their topics might be the most receptive to passing on the maintenance of them, including relicensing or whatever it takes. [[User:Digiot|Digiot]] 22:31, Jul 28, 2004 (EDT)

:But on the other hand, abandoned or rarely updated documents also will be the hardest to get permission for. But I get your drift. I'll go over the list myself tomorrow, but I would like to know if there is any particular ones people want. This is going to take long enough that there is no reason to stick to any particular method if there's one that somebody really wants. I'll rig up some sort of voting system I suppose. I've already taken off some "removed for review" entries and I'm going to go back and remove some internationilization howtos, since those are usually written in a different language. (I'll also replace the sectioning with bullet points - didn't realize how ugly it would look until I was halfway through.) [[User:Crazyeddie|Crazyeddie]] 01:31, Jul 29, 2004 (EDT)

Okay, voting is setup (kinda). [[User:Crazyeddie|Crazyeddie]] 19:10, Aug 2, 2004 (EDT)

==Disclaimer==
A bit off the main topic, but one thing I noticed over at the TLDP... It might be wise to have a "No Warranty, As Is" type notice at the bottom of the page, down in the copyright notices. Unlike the Wikipedia (who have a similar notice, but a bit more buried) we're handing out documentation which could cause serious damage if used improperly, or if it is incorrect. In addition to it being a just plain good idea, some of the TLDP articles have that as their sole condition for modification and redistribution. If we actually do have something like that already, well, my friends don't call me "Captain Oblivious" for nothing. [[User:Crazyeddie|Crazyeddie]] 13:24, Jul 24, 2004 (EDT)

:Good idea - a disclaimer has been added. Thanks. [[User:Jeremy|Jeremy]] 12:41, Jul 25, 2004 (EDT)

I've edited it to include contributors under the "don't sue us!" umbrella. [[User:Crazyeddie|Crazyeddie]] 18:48, Aug 2, 2004 (EDT)

==Forum Revisited==
Several people have asked about a general LQwiki discussion forum. Does anybody have any objections to using this talk page as such a forum? [[User:Crazyeddie|Crazyeddie]] 14:02, Jul 24, 2004 (EDT)

== wiki software link ==

Is there a link on the main page or somewhere at the bottom where people can see what wiki software is being used here. It might be nice to link to the software's homepage, assuming it is free. I looks mostly like the software used on wikipedia, with some very nice modifications. --[[User:Paraphelion|Paraphelion]] 06:50, Feb 9, 2005 (EST)

: We do infact use MediaWiki, which is mentioned in the [[LQWiki:FAQ|FAQ]]. [[User:Jeremy|Jeremy]] 11:31, Feb 10, 2005 (EST)

:: Where is the FAQ linked? It might be nice to also mention this information in "About LQ Wiki", especially because the link is on each page. There's no reason not to have it in both. I'm surprised that the FAQ isn't linked on the about page. --[[User:Paraphelion|Paraphelion]] 02:54, Feb 15, 2005 (EST)

Could we open up our modifications to the community? It seems like there is some interest in them, and it's possible that some downstream users will make modifications that we might find useful... 15:24, Feb 10, 2005 (EST)

: At this time we realistically don't have the resources to support a release. More and more, the changes are mostly cosmetic and not functional anyway. What we will definitely do moving forward is push bug fixes (and features if there is interest) upstream so that everyone can benefit. [[User:Jeremy|Jeremy]] 22:57, Feb 10, 2005 (EST)

I'm not suggesting a full release. I'm suggesting making our patches available. For the spellchecker, for example. Last I heard, MediaWiki is reluctant to uptake spellchecking because Wikipedia servers can't handle the load. (Or at least that's what the rumors say.) If enough downstream users show an interest, I think they might change their minds. [[User:Crazyeddie|Crazyeddie]] 03:23, Feb 11, 2005 (EST)

I remember that our modifications aren't in patch form... Could we possibly give read-only access to our cvs? Are we using a cvs? [[User:Crazyeddie|Crazyeddie]] 03:41, Feb 11, 2005 (EST)

: CVS is not used for the LQ Wiki. [[User:Jeremy|Jeremy]] 16:51, Feb 11, 2005 (EST)

How about just an archive of our current PHP code? Surely y'all make backups? [[User:Crazyeddie|Crazyeddie]] 17:26, Feb 11, 2005 (EST)

: As I mentioned earlier, just releasing the code without being able to support it in any way is probably not in anyones best interest. Aside from that, I don't want it to be seen as a fork, which it isn't. Users will get 100% of the benefits by us pushing bugfixes upstream. If there is interest in the spell checker (or anything else we have here) upstream we'd be more than happy to push that too. [[User:Jeremy|Jeremy]] 10:07, Feb 13, 2005 (EST)

I'm not talking about a formal fork, with the support and code maintenance involved. I'm talking about an open documentation project, based on open source software, making its modifications to that software public.

Ideally, since we're only making modifications, not a full fork, we should make those modifications available in the form of patches. In addition to being helpful for third-party users of MediaWiki software, it would help us when it comes time for us to upgrade to the next MediaWiki release, and it would make it easier for MediaWiki to upload our modifications. I fully agree that getting MediaWiki to upload our mods is the best solution, since that would mean that we would no longer have to maintain the code ourselves.

The current method of handing out our modifications, which consists of: "email Jeremy, and he'll fish out the bit you need and email it to you" is not convenient for either party. I think I've seen about six requests for our code in wiki, and I doubt that many requests have made it to you.

As I said, I think the ideal solution is to make our modifications available in patch form. But I realize that such a move would probably involve a lot of work, and I'm trying to suggest a compromise solution. Instead of having to exchange emails, all you would have to do is grunt "Code's over there. Help yourself." We should make it clear that we don't support the code, we're just handing it out to anybody who wants it. If somebody finds a bug, they can tell us about it, but we'll probably only fix it if the bug directly affects us. Patches would be welcome.

Our main added feature is spellchecking. There has been some interest in a spellchecking feature over at the Wikipedia. However, spellchecking would put an additional strain on their servers, so they haven't rolled their own yet. I think MediaWiki would only put in spellchecking as an optional feature if there was strong interest downstream. Some downstream wikis using an experimental and unsupported spellchecker would be a strong argument in favor of formal inclusion of a spellchecker option.

Something similar could be said for any additional feature we might make in the future. If we're adding the feature ourselves, then there is probably some reason why it isn't in the MediaWiki code already, and it will only be added as an option if there is strong downstream interest. The existance of a patch would no doubt help.

Even if one of our modifications is cosmetic, and not worthy of being included in MediaWiki, we should still make it available. There is no telling what an administrator might find helpful.

The LQwiki's main need right now is additional contributors, ideally ones with experience in Linux and/or wikis. Having wiki patches available would give us greater visibility in the wiki community, especially with administrators.

We might even attract some additional administration staff, who might be willing to help with other LQ projects.

Lastly, I think that providing documentation for wiki administration falls under the subject matter of this wiki. I don't think it's a stretch to include wiki code cookbooks. [[User:Crazyeddie|Crazyeddie]] 15:46, Feb 13, 2005 (EST)

We would not be providing a sealed software package to a helpless user. We would be providing prewritten cookbook code to an administrator, who would hopefully have the coding skills needed to modify our code to their own situation. [[User:Crazyeddie|Crazyeddie]] 17:00, Feb 13, 2005 (EST)

Because MediaWiki is distributed under the GPL, you MUST make your modifications available to the public in some manner. A good reason to roll your changes back into the original is so that you don't have to re-patch your code whenever you want to upgrade to the new version. [[User:Xxxyyy|Xxxyyy]] 19:28, Mar 10, 2005 (EST)

Correction, we only have to provide the code if we redistribute the program. That's my understanding, at least. If we were handing out or selling binaries we would have to make the code available at no more cost than the cost of physically creating the media. Since we ''aren't'' handing out binaries, but only using the MediaWiki engine internally, we aren't required by the GPL to hand out code. Google, for example, uses Linux to power their proprietary search engine magic. They, or so I have heard, did make modifications to Fedora Linux in order to use it in their operations, but since they only use it internally, they don't have to hand out their top-secret secret sauce.

I just happen to think that handing out our modifications is a good idea. To a certain extent, Jeremy agrees with me. Where we differ is how to go about it.

Jeremy would love to roll back our changes to MediaWiki. Problem is, most of our changes are cosmetic, only of use to us - or so we think, no telling what another wiki-admin might do with it. MediaWiki hasn't shown much interest in adapting our changes that aren't cosmetic. The main example being the spellchecker. (Making our code more easily available might change that though.)

I'm supporting making our code available to anyone who passes by. Right now, you could get the code by emailing Jeremy (I think, don't quote me on that), but that's not exactly convenient for anybody concerened.

Jeremy is worried that if we make our code easily available, people will think we're doing our own offical fork, and expect us to maintain it and provide support. Our coding room, which consists of exactly two part-time coders, who also keep the entire LQ site up and running, simply doesn't have the resources to do that.

I'd like some compromise plan - make our modifications easily available, but also stave off any requests for support with a clear, upfront, STFU. [[User:Crazyeddie|Crazyeddie]] 03:43, Mar 11, 2005 (EST)

== Article diffs hard to interpret ==

Is there some reason that the diffs in this wiki are so different in appearance from the default? The color highlighting seems to be completely missing, and looking at the diffs isn't nearly as useful as a result. --[[User:Yath|Yath]] 16:04, Jul 26, 2005 (EDT)

:Thanks for the feedback Yath. I'll look into this. [[User:Jeremy|Jeremy]] 09:18, Jul 27, 2005 (EDT)

::This has been fixed - Thanks again. [[User:Jeremy|Jeremy]] 11:34, Jul 27, 2005 (EDT)

:::Thanks that's much better. --[[User:Yath|Yath]] 12:23, Jul 28, 2005 (EDT)

== Your RSS feed now included in Planet Wiki ==

Hi, I included your RSS feed in [http://planetwiki.wikinerds.org/ Planet Wiki], a service of the [http://www.wikinerds.org/ Wikinerds Community] which offers an online news aggregator that collects various RSS feeds from many wikis around the WikiWikiWeb. In this way more people may find your wiki and become contributors. If you have any maximum-hits policy please [http://nsk.wikinerds.org/ contact me through email]. Good luck with your wikisite! [[User:Www.wikinerds.org|Www.wikinerds.org]] 07:18, Jul 29, 2005 (EDT)

:Thanks! [[User:Jeremy|Jeremy]] 11:17, Jul 29, 2005 (EDT)

== link to linux-net ==

Is there someplace to put a link to the linux networking
development wiki? http://linux-net.osdl.org

== merging other Linux wiki -- Main Page locked ==

On
http://en.wikibooks.org/wiki/Talk:Linux_For_Newbies
, someone suggested merging that wiki with this Linux Questions wiki.
The *only* reason given for not merging these wiki is that the main page of Linux Questions (unlike every other page of both wiki) is not editable.

* Should the Main Page be locked?
* Should these wiki be merged?
--[[User:DavidCary|DavidCary]] 17:16, Jan 13, 2006 (EST)

:I'm not sure what is meant by "merged", but it doesn't look like the discussion about this topic is too active at the link you mentioned as there are only two comments with the most recent one being four months old. That being said, we'd surely encourage participation here at the LQ Wiki and I'd agree that often times content is far too spread out. We'd be happy to provide the resources needed on this one. While the main page is locked, the talk page can be used to discuss entirely new sections. It should also be noted that content here can be either CC or GFDL (although of course the two can't be mixed). If there is anything else I can help with, let me know. [[User:Jeremy|Jeremy]] 21:06, Jan 14, 2006 (EST)

== Dos problemitas que tengo - 2 problems that i have ==
moved to [[User talk:Weimarcastro]]

== Wiki Design problems ==
I'm not sure if you're aware that the top navigation of the wiki is not clear on Firefox 2 besides a white background for articles would be more readable
--[[User:walidaly|walidaly]] 12:35, Apr 02, 2006 (GMT)
: Firefox 3 only shows the top half of the tabs...
#column-content {lq.css?195 (regel 46)
margin-top:0;
padding-top:37px;
}
: seems an incompatible .css statement to me... (has been there for years I guess) - [[User:Bemoeial|Bemoeial]] 10:32, May 1, 2009 (UTC)
::The tabs seem to render OK for me in FF 3.x, but we'll take a closer look. [[User:Jeremy|Jeremy]] 16:21, May 1, 2009 (UTC)

== Main Page strategy ==

I would rewrite the [[Main Page]] to be shorter and thus easier to read. I would like to go the "what do you want" approach, 4 links come to my mind:

* [[Linux_software_equivalent_to_Windows_software]]: according to
http://wiki.linuxquestions.org/wiki/Special:Popularpages this is by far the most-read article (besides [[Main Page]])
* Guides/Tutorials/[[HowTo]]s: you know what you want to accomplish, but do not know how. You need a tutorial
* [http://wiki.linuxquestions.org/wiki/Category:Tips Tips]: you do not have a concrete question, but the tips here will pay for reading them
* [[Introduction]]: you need an introduction to Linux

== Source Code Markup Support ==
Any ideas of when support can be added for the "<nowiki><source></nowiki>" tag? It makes source code very readable. Thanks. --[[User:Rdrdrd|Rdrdrd]] 16:30, October 14, 2008 (UTC)
: This is a mediawiki extension, see http://www.mediawiki.org/wiki/Extension:ASHighlight --[[User:ThorstenStaerk|ThorstenStaerk]] 08:53, October 15, 2008 (UTC)
:: It looks like there are a couple MW extensions for this, each with its own set of issues/problems. Is the consensus that something like this is needed here? [[User:Jeremy|Jeremy]] 20:09, October 15, 2008 (UTC)

==Confusing structure==

The structure of the main page is a bit confusing since several links are to the same page. Instead of having

* '''[[LQWiki:LQ_Central|LQ Central]]'''
* [[LQWiki:LQ_Central#Introduction|Introduction]]
* [[LQWiki:LQ_Central#Guidelines|Guidelines]]
* [[LQWiki:LQ_Central#Getting started|Getting started]]
* [[LQWiki:LQ_Central#Contribute|Contribute]]
* [[LQWiki:LQ_Central#Administration|Administration]]

I think it should be

* '''[[LQWiki:LQ_Central|LQ Central]]'''
** [[LQWiki:LQ_Central#Introduction|Introduction]]
** [[LQWiki:LQ_Central#Guidelines|Guidelines]]
** [[LQWiki:LQ_Central#Getting started|Getting started]]
** [[LQWiki:LQ_Central#Contribute|Contribute]]
** [[LQWiki:LQ_Central#Administration|Administration]]

Unfortunately I can't edit that. [[User:Mikedlr|Mikedlr]] 10:56, November 12, 2009 (UTC)

==Incomplete License Notice==

The bottom of each page reads, "Content is available under unless otherwise noted." It seems like there should be a specific license included, there, such as, "Content is available under The Most Awesome License Ever, unless otherwise noted." (License title subject to change.) ;-)
[[User:DaneM|DaneM]] ([[User talk:DaneM|talk]]) 02:16, August 15, 2014 (EDT)

:We'll roll out a fix for this, thanks. [[LQWiki:Copyrights]] has more information about LQ Wiki licensing. [[User:Jeremy|Jeremy]] ([[User talk:Jeremy|talk]]) 11:53, August 15, 2014 (EDT)

::Forgot to note it when the fix was rolled out, but this has been addressed for some time now. Thanks again [[User:Jeremy|Jeremy]] ([[User talk:Jeremy|talk]]) 14:49, October 23, 2014 (EDT)

Talk:Main Page

2014-08-15T15:53:49Z

Jeremy: /* Incomplete License Notice */

WPA. On wheels

2014-08-11T15:23:13Z

Jeremy: Jeremy moved page WPA. On wheels to WPA over redirect: revert

#REDIRECT [[WPA]]

WPA

2014-08-11T15:23:13Z

Jeremy: Jeremy moved page WPA. On wheels to WPA over redirect: revert

'''Wi-Fi Protected Access''' or '''WPA''' is a powerful, standards-based, interoperable [[security]] technology for [[Wi-Fi]] [[network]]s. It provides strong data protection by using [[encryption]] as well as strong access controls and user [http://en.wikipedia.org/wiki/Authentication authentication]. WPA utilizes 128-bit encryption keys and dynamic session keys to ensure your wireless network's privacy and enterprise security.

WPA2 (Wi-Fi Protected Access 2) provides network [[administrator]]s with a high level of assurance that only authorized users can access the network. Based on the ratified IEEE 802.11i standard, WPA2 provides government grade security by implementing the National Institute of Standards and Technology (NIST) FIPS 140-2 compliant AES encryption algorithm. WPA2 is backward compatible with WPA.

== How to use WPA ==
You will need the wpa-supplicant that enables the communication with a WPA-secured access point. Start the wpa-supplicant like this:
wpa_supplicant -ieth1 -c/etc/wpa_supplicant.conf -d

In this example, your password is contained in /etc/wpa_supplicant.conf. That [[file]] might look like this:
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
network={
ssid="FOO"
scan_ssid=1
priority=5
proto=WPA
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP WEP104 WEP40
psk=7b7267507f40f82bef91a6d2442e7313f9757aaccf788fab9eabe66dbc4e17fe
}

The password is encoded in the line with
psk=7b7267507f40f82bef91a6d2442e7313f9757aaccf788fab9eabe66dbc4e17fe
You can encode your password with the [[command]] <code>wpa_passphrase</code>.

== Examples ==

=== SUSE ===
Using [[SUSE]] 10.2 and an [[ipw3945]] [[WLAN]] card. The WLAN router has the IP [[CIDR_notation|192.168.0.1/24]].

Note: This example is for teaching purposes only. If you want to set this up, you can do it in a few clicks using [[Yast2]]. However, if you want to look behind the scenes, read on...

First let's see what the WLAN [[network device]] is:
santosh:~ # [[iwconfig]]
lo no wireless extensions.

eth2 no wireless extensions.

eth3 unassociated ESSID:"FOOLAN" Nickname:"santosh"
Mode:Managed Frequency=nan kHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Encryption key:2102-2630-0BF8-AFA7-0E48-6EBE-F5 Security mode:restricted
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:7 Missed beacon:0

sit0 no wireless extensions.

santosh:~ #
eth3 is the WLAN card. Now let's set a passphrase:
santosh:~ # wpa_passphrase FOOLAN mypassword
network={
ssid="FOOLAN"
#psk="mypassword"
psk=1bb95e189e8196745abfa4e5dfeae03d3c634e1e1e75ea013e7125507fbef715
}
santosh:~ # cat >/etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
network={
ssid="FOOLAN"
scan_ssid=1
priority=5
proto=WPA
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP WEP104 WEP40
psk=sorryIoverwritethisbetterblahblahbahblahblahblahblahblahblafdfff
}
santosh:~ #
Now get it connected:
$ wpa_supplicant -i eth3 -c /etc/wpa_supplicant.conf -D wext
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:0f:c9:01:f5:f4 (SSID='FOOLAN' freq=0 MHz)
Associated with 00:0f:c9:01:f5:f4
WPA: Key negotiation completed with 00:0f:c9:01:f5:f4 [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:0f:c9:01:f5:f4 completed (auth)
In a parallel console session:
[[ifconfig]] eth3 192.168.0.70
Attention: [[dhcpcd]] does not work here.

Now iwconfig eth3 shows me something like:
eth3 IEEE 802.11g ESSID:"FOOLAN" Nickname:"santosh"
Mode:Managed Frequency:2.457 GHz Access Point: 00:0F:C9:01:F5:F4
Bit Rate:24 Mb/s Tx-Power:15 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Encryption key:F523-EBFF-0012-23D1-6F72-FE22-FDBE-C493-68BC-CFA4-F981-B984-48BB-E2AF-4878-0E59 Security mode:open
Power Management:off
Link Quality=72/100 Signal level=-62 dBm Noise level=-70 dBm
Rx invalid nwid:0 Rx invalid crypt:1 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:52 Missed beacon:0
Test your connection:
santosh:~ # ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.970 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1.00 ms

--- 192.168.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.970/0.989/1.009/0.037 ms
santosh:~ # route add default gw 192.168.0.1
santosh:~ # ping wiki.linuxquestions.org
PING wiki.linuxquestions.org (207.44.182.114) 56(84) bytes of data.
64 bytes from mx.linuxquestions.org (207.44.182.114): icmp_seq=1 ttl=53 time=171 ms

[[Category:Networking]]
[[Category:Guides]]

Gentoo and distcc on wheels

2014-08-11T15:23:07Z

Jeremy: Jeremy moved page Gentoo and distcc on wheels to Gentoo and distcc over redirect: revert

#REDIRECT [[Gentoo and distcc]]

Gentoo and distcc

2014-08-11T15:23:07Z

Jeremy: Jeremy moved page Gentoo and distcc on wheels to Gentoo and distcc over redirect: revert

[[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<br>
emerge -av distcc

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

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

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'')

= Using with Paludis =
If you'd like [[Paludis]] to take advantage of distcc then add the following lines to your /etc/paludis/bashrc file making sure to change the host names:

export DISTCC_DIR="/var/tmp/paludis/.distcc"
export PATH="/usr/lib/distcc/bin:${PATH}"
export CC="/usr/lib/distcc/bin/gcc"
export CXX="/usr/lib/distcc/bin/g++"
export DISTCC_HOSTS="localhost another_host"

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

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:<br>
rc-update add distccd default
and start with the command:
/etc/init.d/distccd start

=References=

== See also ==
* [[Distcc]]
* [[Gentoo]]

==External Links==
* [http://www.gentoo.org/ Gentoo home page]

[[Category:Distro]]

JIT on wheels

2014-08-11T15:23:02Z

Jeremy: Jeremy moved page JIT on wheels to JIT over redirect: revert

#REDIRECT [[JIT]]

JIT

2014-08-11T15:23:02Z

Jeremy: Jeremy moved page JIT on wheels to JIT over redirect: revert

'''Just In Time''' (JIT) is a type of late compilation whereby code is [[compile]]d from an intermediate format ([[source]] or [http://en.wikipedia.org/wiki/Bytecode bytecode]) into [[machine code]] at runtime, just before or during execution. It is common with the [[Java]] language, but is also available in other systems including [[Python]] and [[.NET]].

Video conversion on wheels

2014-08-11T15:22:57Z

Jeremy: Jeremy moved page Video conversion on wheels to Video conversion over redirect: revert

#REDIRECT [[Video conversion]]

Video conversion

2014-08-11T15:22:57Z

Jeremy: Jeremy moved page Video conversion on wheels to Video conversion over redirect: revert

Conversion between [[video file formats]] can be done using
* [[transCode]]
* [[mEncoder]]
* [[FFMPeg]]

= Convert a DVD to a file =
To [[convert]] a [[DVD]] to a [[video]] [[file]] (ripping) use [[menCoder]] like this:
mencoder dvd://''1'' -oac mp3lame -lameopts br=192 -ovc lavc -lavcopts vcodec=mpeg4:vhq -o ''output.avi''
In this case the title ''1'' will be stored as ''output.avi''. As video codec, MPEG4 is used and MPEG3 as audio encoding.

= See also =
* [[video]]
* [[conversion]]
* [[Video editor]]

[[Category:Application]]

Bluetoooth-alsa on wheels

2014-08-11T15:22:54Z

Jeremy: Jeremy moved page Bluetoooth-alsa on wheels to Bluetoooth-alsa over redirect: revert

#REDIRECT [[Bluetoooth-alsa]]

Bluetoooth-alsa

2014-08-11T15:22:54Z

Jeremy: Jeremy moved page Bluetoooth-alsa on wheels to Bluetoooth-alsa over redirect: revert

'''Bluetooth-alsa''' is the project to make [[bluetooth]] headsets work with Linux.

There are several bluetooth profiles for interacting with headsets.
* Headset profile (HSP) is the original profile for using a mono, voice-quality headset, typically with a cellphone.
* Handsfree profile (HFP) includes enhancements over HSP that make call management more convenient.
* Advanced audio distribution profile (A2DP) carries higher-quality audio in one direction, typically to a stereo headset.
* Audio/video remote control profile (AVRCP) is combined with most A2DP headsets to make track changes, pause and play functions available from the headset.

Several headsets support all four profiles and are intended to be used as a convenient way to listen to music which is automatically paused for cellphone conversations.

There are several components in bluetooth-alsa for working with each of these profiles.

== External links ==
* [http://bluetooth-alsa.sf.net bluetooth-alsa.sf.net]

[[Category:Tips]]

Rev on wheels

2014-08-11T15:22:48Z

Jeremy: Jeremy moved page Rev on wheels to Rev over redirect: revert

#REDIRECT [[Rev]]

Rev

2014-08-11T15:22:48Z

Jeremy: Jeremy moved page Rev on wheels to Rev over redirect: revert

'''rev''' is the same as [[cat]], only rev shows characters in reverse. Imagine a file ''foo'' that contains:
hello
world
<code>rev ''foo''</code> will print:
olleh
dlrow
to print lines in reverse you can use [[tac]], to print both lines and characters in reverse, for example, use:
tac ''foo'' | rev

== Provided by ==
Most (all?) Linux distributions incorporate this from the [http://www.gnu.org/software/coreutils/manual/html_node/index.html#Top GNU Coreutils]: and use its man
[http://www.gnu.org/software/coreutils/manual/html_node/rev-invocation.html page]

== Related Commands ==
These all relate to the output or processing of entire files
* [[cat]] -- con''cat''enate files into a single result.
* [[tac]] -- line-reversed cat
* [[nl]] -- output with line numbers
* [[od]] -- dump in octal and other character representations.
* [[base64]] -- Encode in printable characters.

[[Category:Command]]

&& on wheels

2014-08-11T15:22:36Z

Jeremy: Jeremy moved page && on wheels to && over redirect: revert

#REDIRECT [[&&]]

&&

2014-08-11T15:22:36Z

Jeremy: Jeremy moved page && on wheels to && over redirect: revert

&& is a famous operator in the [[C language]] and inherited by most [[scripting languages]] including [[shells]], [[perl]], [[python]] and such. It is for conditional execution: in a shell command, for instance, if the left [[command]] succeeded, the right one will be executed, else not.

Example:
[[ls]] /etc/SuSE-release && [[cat]] /etc/SuSE-release
This will only show the content of /etc/SuSE-release if this file could be listed.

==Why?==
&& means a logical AND. Now, if we have
''command1'' && ''command2''
and ''command1'' is successful, it delivers the return code 0 (true). That means, ''command2'' must be evaluated to see if it makes the expression false.
Now if ''command1'' is unsuccessful, it delivers a return code unequal 0 (so, false). That means, ''command2'' does not even need to be evaluated, the expression will be false in any case. So, ''command2'' is not even executed.

== See also ==
* [[bash]]
* [[bash tips]]

[[Category:script]]

Command line interface on wheels

2014-08-11T15:22:30Z

Jeremy: Jeremy moved page Command line interface on wheels to Command line interface over redirect: revert

#REDIRECT [[Command line interface]]

Command line interface

2014-08-11T15:22:30Z

Jeremy: Jeremy moved page Command line interface on wheels to Command line interface over redirect: revert

A '''command line interface''' ('''CLI''') is a textual mode of interaction between computers and humans. With a CLI, the user types commands at a prompt, which are executed by the [[shell]], and receives textual feedback.

In contrast, the Graphical User Interface or [http://en.wikipedia.org/wiki/GUI GUI] operate via [[mouse]] and keyboard, while CLIs only depend on commands entered via a keyboard.

Linux, among with most other Unix-like operating systems, is more attuned to the command line interface than [[Windows]]. While various tools such as [[YAST]] have been introduced, the CLI is still the system administration tool of choice for many Linux operators. Indeed, even though attractive desktop GUIs are frequently seen on desktop Linux systems, they often serve as little more than a manager for multiple [[xterm]]s.

= See also =
* [[Console]]
* [[Open a Console]]
* [[End Users Guide:The Shell]] A beginner's guide to the Linux CLI
* [http://www.linuxcommand.org/index.php Learn the command line]
* [http://www.tuxfiles.org/linuxhelp/sysadmin.html An introduction to the Linux command line]
* [http://www.pixelbeat.org/cmdline.html List of Linux commands for common operations.]
* [http://freeengineer.org/learnUNIXin10minutes.html Learn unix in 10 minutes]
* [http://tlug.up.ac.za/wiki/index.php/CS_Student_Linux_User's_Guide CS Student Linux User's Guide] - Easy introduction to the command line interface (wiki)

Half-Life Server on wheels

2014-08-11T15:22:24Z

Jeremy: Jeremy moved page Half-Life Server on wheels to Half-Life Server over redirect: revert

#REDIRECT [[Half-Life Server]]

Half-Life Server

2014-08-11T15:22:24Z

Jeremy: Jeremy moved page Half-Life Server on wheels to Half-Life Server over redirect: revert

The '''Half-Life Dedicated Server''' (or '''HLDS''') is the dedicated [[server]] for hosting a Steam [[game]]. It allows you to host a server for any game or modification that works with the Steam client (Half-Life, Counter-Strike, Team Fortress, Ricochet, Day of Defeat, and so on). The dedicated server runs in a [[console]]. There are not any [http://en.wikipedia.org/wiki/GUI GUI] releases that I know of.

The linux release can be downloaded from:

[http://files.filefront.com/2127282 Download1]<br>
[http://www.fileplanet.com/files/130000/130424.shtml Download2]

Most of the time, after downloading these files, you will need to update the release anyways. It might be a good idea to visit ftp://ftp.valvesoftware.com and download hldsupdatetool.bin instead of the large packages from the above links. Login as hlserver, password hlserver. That program will download the latest Steam update utility that is used to download game files for a dedicated server.

Insmod on wheels

2014-08-11T15:22:18Z

Jeremy: Jeremy moved page Insmod on wheels to Insmod over redirect: revert

#REDIRECT [[Insmod]]

Insmod

2014-08-11T15:22:18Z

Jeremy: Jeremy moved page Insmod on wheels to Insmod over redirect: revert

'''Insmod''' is a simple program that inserts [[module]]s into the [[Linux]] [[kernel]]. Better use [[modprobe]] for it checks if the insert is secure first.

[[Category:Kernel]]
[[Category:Command]]
[[Category:Configuration]]
[[Category:Kernel-command]]

Window manager on wheels

2014-08-11T15:22:11Z

Jeremy: Jeremy moved page Window manager on wheels to Window manager over redirect: revert

#REDIRECT [[Window manager]]

Window manager

2014-08-11T15:22:11Z

Jeremy: Jeremy moved page Window manager on wheels to Window manager over redirect: revert

A '''window manager''' manages the actual windows on the desktop. The [[X Window System]] doesn't manage the windows on its own, it leaves that job to this program. Any graphical program you run makes a window. The window manager handles where a window will appear on the screen, how big the window will be, etc. It handles things like resizing and minimizing. The title bar at the top of most windows, and other window decorations, is often handled by the window manager.

In more recent times, the term ''composite window manager'' has appeared. This is a window manager that uses some new X extensions (most notable the [[CompositeExt]]) to alter the visual appearance of windows on the screen. A composite window manager can add real shadows to windows, make them see-thru, and perform other visual effects depending upon the window manager.

== Window managers ==

=== Popular ===
* [[Compiz]]
* [http://en.wikipedia.org/wiki/Kwin Kwin] (default window manager for [[KDE]])
* [[Metacity]] (default window manager for some versions of [http://en.wikipedia.org/wiki/GNOME GNOME] version 2) [http://www.gnome.org/start/2.2/notes/rnwm.html]

=== Less popular===
* [[Window Maker]]
* [[Enlightenment]]
* [[Fluxbox]]
* [http://en.wikipedia.org/wiki/FVWM FVWM]
* [[IceWM]]
* [[Afterstep]]
* [[Blackbox]]
* [[Ion]]
* [[Openbox]]
* [http://en.wikipedia.org/wiki/Ratpoison ratpoiSon]
* [[Sawfish]] (originally called Sawmill)
* [[twm]] (Tab Window Manager)

Talk:Window manager on wheels

2014-08-11T15:22:02Z

Jeremy: Jeremy moved page Talk:Window manager on wheels to Talk:Window manager over redirect: revert

#REDIRECT [[Talk:Window manager]]

Talk:Window manager

2014-08-11T15:22:02Z

Jeremy: Jeremy moved page Talk:Window manager on wheels to Talk:Window manager over redirect: revert

I think only proper nouns should be capitalized - otherwise it looks like MS 'Windows'. Unless maybe for emphasis, but then it should be quoted or made bold or something. - Or the tt code. That might not be a bad idea - to tt or bold the keyword under discussion.

A <tt>window manager</tt> is...

or

A <b>window manager</b> is...

[[User:Digiot|Digiot]] 00:35, Mar 1, 2004 (EST)

----

Well.... I think if you took a sample of 100 people, don't think too many would confuse "Window manager" with "MS Windows" in a section entitled "Window Manager" - simply thought that a ''generic term'' with a set of known properties should be given '''some emphasis''' of some sort - as to what what emphasis is appropriate, that's a different matter? - maybe - <tt>window manager</tt> (in typewriter font)?

[[User:Skyline|Skyline]] 01:02, Mar 1, 2004 (EST)

----

I believe that the Do: and Don't: are important to direct the inclusion of more useful content, but I am not sure they belong on this page, because this page does not include a list of all window managers.

Unless this can be changed, I think the Do: and Don't: should be generalized sufficiently to go to the Applications page.

[[User:Dircha|Dircha]]

----

Hjsplit on wheels

2014-08-11T15:21:52Z

Jeremy: Jeremy moved page Hjsplit on wheels to Hjsplit over redirect: revert

#REDIRECT [[Hjsplit]]

Hjsplit

2014-08-11T15:21:52Z

Jeremy: Jeremy moved page Hjsplit on wheels to Hjsplit over redirect: revert

'''HJSplit''' is a freeware, multi-platform file splitter. Allowing you to separate a single file into multiple, easier to swallow chunks allowing transfer through E-Mail, the web, floppies or anything of the sort. Defaults to a full graphical interface based on the [http://www.freebyte.com/linux/libraries Kylix library] but also includes a [[CLI]] based interface, and a [[GTK]] based interface.

= External links =
* [http://www.freebyte.com/hjsplit/ HJSplit's main webpage]
* [http://www.freebyte.com/hjsplit/#linux HJSplit for Linux download]

Software development

2014-06-24T14:57:49Z

Jeremy: Reverted edits by Sindy89 (talk) to last revision by ThorstenStaerk

'''Software development''' is a process by which new [[program]]s are planned, designed, coded, tested, debugged and ultimately released as a new [[application]], usually to the public but sometimes within an organisation only. There are many different methodologies for developing software, each of which has its own advantages and disadvantages and is favoured by its own group of adherents. The [[Open Source]] development model is the one most often used by [[Linux]] developers.

= Tools and processes =

See [[Programming Tips & Tricks]] for more details on the specific tools available to assist with the software development process.

* The ''human brain'' is the most important software development tool: before any program is written the developers need to know exactly what the program is for, how it is going to work and who is going to use it. Poor planning is one of the largest causes of software project failures. See [[software development guidelines]] for more information.
* The program may already have been written. Searching [http://www.google.com Google] or online repositories such as [http://freshmeat.org Freshmeat] may reveal that a program already exists that performs the required task. If a program exists but does not ''quite'' do what is needed, then the open source nature of the program may allow it to be modified to suit individual needs.
* The software developer's most basic tool is the [[text editor]]. Programs are written in a human-readable [[programming language]] and then either converted into executable code by a [[compiler]] or interpreted on the fly by an [[interpreter]]. Interpreted code may be contained within a [http://en.wikipedia.org/wiki/Runtime_environment runtime environment] that isolates the code from the rest of the system.
* A more advanced form of text editor is the [[integrated development environment]] (IDE) which provides features such as syntax highlighting, assisted navigation and refactoring, single-click compilation and incremental [[debug]]ging.
* It is important not to reinvent the wheel if possible: there is a massive selection of [http://en.wikipedia.org/wiki/Toolkit toolkit]s and [http://en.wikipedia.org/wiki/Software_development_kit SDKs] that provide ready-written functionality for such things as user interfaces, 2D or 3D graphics, database access and so on. These toolkits will have a published [http://en.wikipedia.org/wiki/API API] and be accompanied by extensive [[documentation]] that facilitates their use.
* If an IDE is not available, then a standalone [[debugger]] will be useful for locating and correcting errors in a new application (of which there will be many).
* [[Package]] management and deployment tools (for example [[RPM]]) allow the easy distribution and installation of new software.
* Once the software is released, a publically-accessible [[bug reporting]] system will allow users to report bugs so that they can be fixed in later versions, and may allow users to submit feature requests for new releases.

MediaWiki:Modern.css

2014-01-10T18:54:58Z

Jeremy:

/* CSS placed here will affect users of the Modern skin */
#p-logo a { background-image: url('http://images.linuxquestions.org/lqwiki/LinuxQuestions-wiki.gif') !important; }

MediaWiki:Modern.css

2014-01-10T18:54:02Z

Jeremy:

/* CSS placed here will affect users of the Modern skin */
#p-logo a { background-image: url('images.linuxquestions.org') !important; }

MediaWiki:Modern.css

2014-01-10T18:52:27Z

Jeremy: Created page with "/* CSS placed here will affect users of the Modern skin */ #p-logo a { background-image: url('images.linuxquestions.org') !important; }"

/* CSS placed here will affect users of the Modern skin */
#p-logo a { background-image:
url('images.linuxquestions.org') !important; }

User talk:Jeremy

2013-04-15T13:44:00Z

Jeremy:

test
----
Jeremy
I found you on the history of Wiki:Section suggestions, but wanted to see what you had written. Is there a way to make diff's of the history?
[[User:TomFrayne]] June 2, 2004
: You can get a history of each page by clicking the "Page history" link. [[User:Jeremy|Jeremy]] 18:14, Jun 2, 2004 (EDT)
:: I found the history. I wanted diff's of versions of the page.
:: Thanks. I found it on the left side of the watchlist entry. I can't understand how I missed it.
----
Hi Jeremy,

We are running linuxwiki.org since near 2 years meanwhile and I think we have the same goals, so we should coordinate our work.

Maybe we can meet on #wiki on irc.freenode.net. I am permanently logged on to that channel (but not permanently present ;).

Thomas

:Just out of curiosity, what license are you using over at http://linuxwiki.org ? I've been a bit obbsessed with copyleft incompatibilty ever since I found out we can't use Wikipedia content here. [[User:Crazyeddie|Crazyeddie]] 19:06, Jun 29, 2004 (EDT)
----

Jeremy, Dave - another spellcheck-bug ?? - 3 simple spelling corrections on the [[Network addressing]] page brought out some bizarre "userdefined"/"strange symbol" markup - could be the spellchecker and <nowiki><code><pre></pre></code></nowiki> :) - I'll put a note on the Wiki mailing list if I here nothing from here - Sky.

[[User:Skyline|Skyline]] 19:10, Mar 14, 2004 (EST)

:Please post all bugs to the wiki mailing list. Thanks. [[User:Jeremy|Jeremy]] 19:28, Mar 14, 2004 (EST)
----

Hi. I think that the idea of a linux knowledge base as a wiki is great! I'm a contributor of Wikipedia (en and fr) and and hope that this wiki will become as useful and interesting to browse.

My main problem with the LQ.wiki is its appearance; the fonts in the articles are too small, the headers are too big and look like links. I know that all this will be polished over time, but I think that ASAP would be a good idea to avoid turning away potential contributors. [[User:MikeCapone|MikeCapone]] March 06, 2004.

----

I agree the headers are a bit big (specfically the biggest one), but they are like that on Wikipedia also (it should be fixed soon if I understand correctly). As for the font issue, what browser are you using?

[[User:Jeremy|Jeremy]] 00:42, Mar 7, 2004 (EST)

:I'm using Mozilla 1.6 on Linux (Slackware 9.1). The headers might be as big on wikipedia, but they fit in much better since the text of the articles isn't as small. If most of the article formatting was the same as on Wikipedia (same fonts, same size, etc) I'd be 100% happy. If you want to see what I'm talking about, I can take some screenshots comparing wikipedia to here, if you want to see what I'm talking about. [[User:MikeCapone|MikeCapone]] March 07, 2004.

:Mike, we're looking into this now. [[User:Jeremy|Jeremy]] 11:28, Mar 7, 2004 (EST)

:A few changes have been made. How do things look after a shift-refresh? [[User:Jeremy|Jeremy]] 13:56, Mar 7, 2004 (EST)

::They look pretty much the same as they did before, and my minimum font-size is higher than the default (and I no other site that I can think of has been giving me such small fonts). Have a look for yourself: [http://www.imageshack.us/files2/ss-000909-01.png] [http://www.imageshack.us/files1/ss-000909-02.png] [[User:MikeCapone|MikeCapone]] March 07, 20:16 (ET) 2004.

:::Wow, that wikipedia text looks huge to me (almost too big, but I guess that is a matter of taste). You want to forward a note to the mailing list and we'll see what people think? Thanks. [[User:Jeremy|Jeremy]] 20:39, Mar 7, 2004 (EST)

----

Aren't a lot of sites small? (I'm Slack9.1/Moz1.6, myself.) Set mozilla's minimum font size higher if it bothers you. (Not saying it couldn't/shouldn't be adjusted, but just saying it's not exclusive to these pages and there's a workaround.)

And, again, not that things couldn't be adjusted, but I notice a *lot* of comments regarding wikipedia. This isn't wikipedia. Personally, wikipedia's font size is too big, to me - somewhere in the middle might be okay. About the size of how the text looks in the input boxes.

[[User:Digiot|Digiot]] 04:58, Mar 7, 2004 (EST)

:Well, it does use the same software as Wikipedia, and wikipedia is *the* success story in the wiki world, so I think that comparisons are fair. [[User:MikeCapone|MikeCapone]] March 07, 20:16 (ET) 2004.

----

I think the size of the text and headings is fine (now), however I don't think that third and fourth level headings should be indented. Headings are almost never indented ''more'' than the text, usually they are either flush level or hang out to the left of the text. Perhaps this could be changed so that heading levels 2/3/4 are smaller than level one but at the same indent position. [[User:LordK|LordK]] 16:02, Apr 2, 2004 (EST)

:I'll second that. Not a big benefit if the cost is high, but if it's an easy fix, it's a worthwhile fix. Either that or they should be indented more. ;) As is, they just look a bit off. [[User:Digiot|Digiot]] 06:29, Apr 3, 2004 (EST)

::Also it would be nice if external links could be a different colour from internal links (a la Wikipedia) so that the difference is obvious. [[User:LordK|LordK]] 10:34, Apr 4, 2004 (EDT)

:::LordK, can you post these concerns on the mailing list so they can be discussed? Thanks. [[User:Jeremy|Jeremy]] 13:45, Apr 7, 2004 (EDT)

----

I'd love to, but I really hate mailing lists. Would it be okay if I told you and you could pass it on? Let me know [[User:Dysprosia|Dysprosia]]
:You can post it here, it's just easier if everything is collected on the mailing list for discussion. [[User:Jeremy|Jeremy]] 17:58, Mar 23, 2004 (EST)

:: Wikipedia handles redirects by doing the following -
::# assume that a page operating System redirects to Operating system
::# a user clicks on a link that moves to the redirect page.
::# the user is taken to Operating system ''but'' the user is notified of the redirect by saying "(Redirected from Operating System)" just under the main title.
:: This way, on clicking the link in the brackets, the user can then go to the page, which shows the page without redirection, allowing the page to be queried (Edit, What Links Here, &/c) more easier. An example is [http://en.wikipedia.org/w/wiki.phtml?title=OS here - OS]
:: Without this, one must use the wiki.phtml?title=...&action=edit method, which is more difficult.
:: HTH [[User:Dysprosia|Dysprosia]] 01:17, Mar 24, 2004 (EST)

:::Let me look into this. [[User:Jeremy|Jeremy]] 12:00, Mar 24, 2004 (EST)

----
When you delete a page for copyright violations, do you delete just the violating material, or do you NuuKE it? I suggest leaving them as a stub and lilnking to the article that they were plagarizing from.

Jeremy,
someone does a "hacker" attack on my name by writing me with %D0%B5, see http://wiki.linuxquestions.org/wiki/User:Thorst%D0%B5nStaerk --[[User:ThorstenStaerk|ThorstenStaerk]] 03:15, May 26, 2007 (EDT)
:Thanks for the heads up, will look into this. [[User:Jeremy|Jeremy]] 14:06, May 28, 2007 (EDT)

Talk:Linux Dictionary

2013-01-27T17:28:45Z

Jeremy: Reverted edits by Kareempharmacist (Talk) to last revision by ThorstenStaerk

what do you want to express with this article? --[[User:ThorstenStaerk|ThorstenStaerk]] 15:47, January 9, 2013 (UTC)

Main Page

2012-08-31T14:30:38Z

Jeremy: added "Linux Distributions" to Sections

__NOEDITSECTION__
Welcome to the LinuxQuestions.org Wiki. This site will allow you to not only learn about Linux and Open Source, but will also allow you to share your knowledge. A Wiki is a type of website that allows you the visitor to [[LQWiki:Plunging forward|change the content]].

You are encouraged to participate regardless of your expertise level. Remember that to be helpful you don't need to be technical. You can help edit grammar and spelling, start a stub page or include any bits of knowledge you may have. If you'd like to contribute but aren't sure where to start, there is a list of [[Special:Wantedpages|most wanted]] pages.

'''Note:'''
* To ask a question and get answers, use our [http://www.linuxquestions.org forums].
* You can now use either the CC by-sa license or the GFDL. [[LQWiki:Copyrights| Read More]]

<table border=0 cellspacing=3 cellpadding=3>
<tr><td class=purple valign=top width=50%>

== Linux Sections ==
* [[LinuxIntro]] - how to start with Linux
* [[Linux-Windows Software Equivalents]]
* [[Commands]] - the "vocabulary" of a Linux system
* [[Howto]]s - how to accomplish some tasks
* [[TroubleShooting]] - some problems and their solution
* [[Tips and tricks]] - explore new ideas
* [[InterOperAbility]] ([[Share files with Windows]] etc.)
* [[Networking]] ([[wireless]], [[firewall]]s etc.)
* [[Security]] (like how to [[encrypt a disk]] etc.)
* [[Scripting]] - write your own [[programs]]
* [[Applications]] for your needs
* [[:Category:Distro|Linux Distributions]]
</td>

<td class=purple valign=top width=50%>
== LQ Wiki Sections ==
* '''[[LQWiki:LQ_Central|LQ Central]]'''
** [[LQWiki:LQ_Central#Introduction|Introduction]]
** [[LQWiki:LQ_Central#Guidelines|Guidelines]]
** [[LQWiki:LQ_Central#Getting started|Getting started]]
** [[LQWiki:LQ_Central#Contribute|Contribute]]
** [[LQWiki:LQ_Central#Administration|Administration]]

* [[Special:Allpages|Browse all articles by name]]
* [[Special:Wantedpages|Pages waiting to be written]]
* [http://wiki.linuxquestions.org/index.php?title=Special:Whatlinkshere&target=LQWiki:stub_articles Stub articles that need more content]

</td></tr></table>
__NOEDITSECTION__

AGP

2012-08-02T15:18:01Z

Jeremy: Reverted edits by GaleMerritt (Talk) to last revision by Jeremy

'''AGP''' ('''A'''ccelerated '''G'''raphics '''P'''ort) is a specification for a high-speed extension of the [http://en.wikipedia.org/wiki/Conventional_PCI PCI] [[bus]] allowing graphic cards direct access to system [[memory]]. It was originally developed by [http://en.wikipedia.org/wiki/Intel Intel] but is now standard on all makes of PC motherboard, and improves performance on 3D graphics applications and games that require a high memory bandwidth.

= Versions =

There are three versions of AGP:

* AGP1.0, AGP2.0, AGP3.0.

The main differences are:
* AGP1.0 - ''1x'' and ''2x'' speeds, 3.3V
* AGP2.0 - Adds ''4x'' mode and adds 1.5V support ([[backwards compatible]] with 1.0)
* AGP3.0 - ''4x''/''8x'', not [[backwards compatible]] (only supports the 4x mode of 2.0)

= Speeds =

The AGP speed is normally indicated with:

* ''1x'', ''2x'', ''3x'', ''4x'' and ''8x''.<br>

These relate to the amount of data that is sent per clock cycle. (and not the actual clock speed itself). The AGP bus clock speed is normally 66MHz, so for example the ''1x'' speed send 4 bytes of data per clock cycle, the ''2x'' speed sends 8 bytes. (So theoretical bandwith of ''1x'' is 66Mhz * 4bytes = 264Mb/s)

= Physical AGP slots =

Because of the changes in voltage level, different AGP slots and connectors were specified. The different versions have notches at different places, so people can't stick unsupported AGP cards in a wrong slot.
The different types on mainboards are:
*Original AGP 3.3V slots, one notch at the ''front''-end (the side that, if a card is installed, you plug in the monitor/vga cable)
*AGP 1.5V slots (one notch more towards the ''back''-end)
*Universal AGP slots - support multiple voltages (no notches, so both types of cards fit in it).
Then there are also AGP pro versions of all these slots, which provide more watts for power hungry videocards. What specific speeds and AGP versions a mainboard supports should be specified in its manual.

= Linux support =

In the Linux 2.4 series support for this is provided by the agpgart [[kernel module]].<br>
For 2.6 series, it has been split up in a general agpgart module and chipset specific modules named like <chipset-name>-agp, e.g. ''nvidia-agp'' or ''intel-agp''. In the kernel configuration these can be found under ''Device drivers''->''Character devices''.

== Configuring in XFree86 ==

In [[XFree86]] the AGP speed can be configured by adding a line like:<br>
Option "AGPMode" "4x"
to the device section of the [[XF86Config]].
This needs the above mentioned kernel support, and also support in the driver. Check the [[man]] page of the driver to see if it's supported.

[[Category:Hardware]]

AGP

2012-06-21T15:05:58Z

Jeremy: Reverted edits by MaryannCantrell (Talk) to last revision by 4dummies

Talk:FFmpeg

2012-05-23T14:19:47Z

Jeremy: /* Unsupported codec for output stream #0.0 */

=== Unsupported codec for output stream #0.0 ===
I apologize for the style of my contribution, and also for its negative aspect.<br>
I only hope that people knowing how to fix this issue will do it.<br>
Best
:--[[User:Colonna|Colonna]] 18:56, May 20, 2012 (UTC)

:Colonna, as the wiki is not a place for asking questions I have rolled back your edit. You may want to visit the forums to see if someone there can offer a solution. http://www.linuxquestions.org/questions/ [[User:Jeremy|Jeremy]] 21:09, May 21, 2012 (UTC)
::Jeremy, why not to ask questions on a Wiki to start an article ? after all a Wiki page answers (unformulated) questions ?
::I never use Forum : they are unstructured, unreadable and I very soon get lost, I always suggest the use of Wikis instead.
::Sorry --[[User:Colonna|Colonna]] 05:37, May 22, 2012 (UTC)
:::No apology needed, that's just the policy here. I think you'll find LQ quite structured and readable, but we also have a Linux Q&A site if that's the style you prefer. See http://linuxexchange.org/ for more. [[User:Jeremy|Jeremy]] 14:19, May 23, 2012 (UTC)

Talk:FFmpeg

2012-05-21T21:09:59Z

Jeremy: /* Unsupported codec for output stream #0.0 */

FFmpeg

2012-05-21T21:07:57Z

Jeremy: Reverted edits by Colonna (Talk) to last revision by 4dummies

'''FFmpeg''' is used mainly to convert and stream video. FFmpeg uses [http://en.wikipedia.org/wiki/Libavcodec libavcodec]. FFmpeg is developed under [[Linux]], but can be compiled and run under most operating systems.

== How to get it ==

svn co svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg
cd ffmpeg
./[[configure]] && [[make]] && make install

== Formats ==

FFmpeg supports many formats and containers, including: mpeg-1, mpeg-2, DIVx, H.263, H.264, MP2, MP3, and MP4.

== How to use it ==

Here's an example how to convert ''example.dv'' to a .mpg [[file]]:
ffmpeg -i ''example.dv'' -f avi -vcodec mpeg4 -b 1800 -g 300 ''example.mpg''

== FFplay ==

FFmpeg also includes [http://en.wikipedia.org/wiki/Ffplay FFplay], a media player and streaming client.

== FFserver ==

FFmpeg also includes [http://en.wikipedia.org/wiki/Ffserver FFserver], used to stream media to clients over a network.

== External Links ==

* [http://ffmpeg.mplayerhq.hu/index.html FFmpeg home page]
* [http://arrozcru.no-ip.org/ffmpeg/ FFmpeg on Windows help]
* [http://stephenjungels.com/jungels.net/articles/ffmpeg-howto.html FFmpeg on OSX help]

[[Category:Command]]
[[Category:Video]]

Talk:Daemon

2012-04-30T20:59:27Z

Jeremy:

This page is marked as a stub. It's not clear to me what needs to be added that isn't already in the Wikipedia article. --[[User:4dummies|4dummies]] 14:53, April 29, 2012 (UTC)

:It would really be ideal to have a little more information here on the LQ Wiki, as opposed to simply linking to Wikipedia. [[User:Jeremy|Jeremy]] 20:59, April 30, 2012 (UTC)

Music Player (Device)

2012-01-16T21:56:12Z

Jeremy: Reverted edits by Simooceranyh (Talk) to last revision by ThorstenStaerk

== Walkman ==

Sony's [http://en.wikipedia.org/wiki/Sonicstage SonicStage] software which allows the transfer of songs to and from the Walkman series has not been ported to Linux. Two [http://sourceforge.net Sourceforge] projects, [http://sourceforge.net/projects/nwe00xmp3man NW-E00x Mp3 File Manager] (dead) and [http://sourceforge.net/projects/symphonic/ Symphonic] (NW-E00x's Mp3 File Manager's updated successor), have been setup to address this problem.

== Walkman Tutorial ==

'''NOTE''': [http://sourceforge.net/projects/symphonic/ Symphonic] is a much easier to use successor to NW-E00x Mp3 File Manager that only requires you to have a folder man OMGAUDIO or omgaudio in the root directory of the player. No extraneous workaround, as for NW-E00x Mp3 File Manager after the Symphonic tutorial below, is required.

Here is a quick tutorial for Symphonic (not the outdated NW-E00f below), tested on the NW-E003f with Ubuntu 7.10

1. Download Symphonic from [http://sourceforge.net/projects/symphonic/ here] and extract it to the root directory of the Walkman.

2. Make sure you have a folder named OMGAUDIO or omgaudio. If you have this and Symphonic doesn't work erase your current folder
and create a new empty one (the one created by SonicStage may not work)

3. Open the resulting JSymphonic folder.

4. Run JSymphonic_x.x.x.jar, three examples given below (x's in place of version numbers, example of full filename is
JSymphonic_0.1.1b.jar)

a. From the command line, with the JSymphonic folder as the working directory, type '''java -jar JSymphonic_x.x.x.jar'''

b. Using Gnome right-click on JSymphonic_x.x.x.jar and select "Open with Java 6 Runtime"

c. Or, using Gnome, right-click on the jar file, select properties, select the "open with" tab, and pick "Java 6 Runtime".
Now every time one double-clicks the jar file it will automatically open.

Here is a small tutorial, tested on the NW-E003f with [http://www.ubuntu.com Ubuntu] 7.10.

Note: These first nine steps may not be necessary, you might be able to just erase the root directory of you walkman, '''DO NOT FORMAT IT WITH YOUR OPERATING SYSTEM!!!!''', only format the Walkman as outlined below, or as outlined in the Operation Guide, which came on the CD in the Walkman packaging.

1. Take your Walkman, hold the HOME button until the advanced menu appears.

2. Go over to the fourth icon (on the NW-E003f), it looks like a file folder with a bidirectional-horizontal arrow in it.

3. Press play/stop

4. Press fast forward until you get to the advanced menu

5. Press play/stop

6. Press fast forward until you get to initialize

7. Press play/stop

8. Press fast forward until you get format

9. press play/stop to format

10. Goto http://sourceforge.net/projects/nwe00xmp3man and download NW-E00X_MP3_File_Manager-0.13.jar and the OMGAUDIO.ZIP.

11. place nwe00xmp3man.jar and OMGAUDIO.ZIP in the root directory of the walkman.

12. unzip OMGAUDIO to the walkman root directory.

13. Open up a command window and change the working directory to the root directory of the player (if the walkman is the only usb storage device is hooked up to ubuntu it should be '''/media/disk''')

14. type: '''chmod 700 NW-E00X_MP3_File_Manager-0.13.jar''' to make it executeable.

15. type '''./NW-E00X_MP3_File_Manager-0.13.jar'''

16. Voila, now you can dump files onto your Walkman. Just remember to change to /media/disk and type ./NW-E00X_MP3_File_Manager-0.13.jar whenever you want to run the program.

[[Category:Guides]]