LQWiki - User contributions [en]

MBR

2005-06-19T20:58:00Z

TomFrayne: Link to MBR and partition recovery

'''MBR''': '''M'''aster '''B'''oot '''R'''ecord. It is located in the first sector of the first [[hard disk]] or a [[floppy disk]]. It contains a small program that is read into memory and executed at [[boot]] (after the [[BIOS]] bootup). The program tries to find a bootable [[partition]] in the partition table (which is located in the end of the MBR sector). The boot sector of the partition is then loaded and executed. This normally is some [[boot loader]] but can also be an actual [[kernel]] of some specific OS. In Linux [[LILO]] or [[GRUB]] is usually installed in the MBR.

In linux the MBR can be directly accessed with [[dd]]. For example to make a backup of the MBR:
# dd if=/dev/hda of=/path/mbr-backup bs=512 count=1

and restore it with

# dd if=/path/mbr-backup of=/dev/hda bs=512 count=1

Change hda to sda for SCSI or SATA drives
Change to the a of hda to b or c etc for drives on other controllers.

WARNING...Making a typo on the restore command may mean too much is over-written or the wrong MBR is over-written. If this happens to you, try the recovery procedure in [[MBR and partition recovery]].

==See also==

*[[Using Toms floppy]]

SuSE

2005-05-28T04:09:04Z

TomFrayne: Add reference to Novell's support forums

'''SuSE''' is one of the oldest and most known Linux [[distribution]]s. It is [[RPM]]-based, and it is well known for its stability and for the quality of its configuration toolkit, [[YAST]]. There are SuSE Linux flavours tailored for desktop or laptop, office and server needs.

SuSE is seen as a good distro for beginners (along with [[Mandrake]] or [[Fedora]]) as it provides a user friendly environment, with [[GUI]]'s for configuring hardware in the excellent Yast. [[KDE]] has been integrated into SuSE ([[Gnome]] and other [[window manager]]s are included) providing seamless configuration. Suse declared: "We offer both desktops at the highest possible level to maximize a customer's choice. We also spend a great amount of development effort to make both KDE & Gnome interoperate smoothly."

Originally a German organisation, SuSE was acquired in 2003 by the US networking giant, [[Novell]], but will retain their SuSE brand name and independent operations. This move is intended to give SuSE a better foothold in the US and Novell a significant share in the Linux business.

SuSE was sometimes debated in the free software community because it heavily relied on the [[yast|YAST]] configuration toolkit, that was released under a non-open source license. The YAST2 license for current versions of SuSE is the [[GPL]], so.

The boxed version of [[Suse 9.3]] is a [[Mere aggregation]], in GPL terminology, so it can legally contain non-GPL'd products. Further, the license for Suse 9.3 as a whole allows giving away (but not selling) copies of the CDs and DVDs containing products with proprietary licenses.

==Suse support forums==
Novell has a set of support forums for its products, including Suse. These can be found on your web browser, starting at [http://support.novell.com/forums Novell support forums]. For those wanting to use an NNTP news reader, e.g., Pan, you can use Tools/News Servers to add Novell's news server, support-forums.novell.com, to the list of servers accessed.

==External links==
*[http://br-linux.org/main/arquivos/LICENSE.TXT Suse 9.3 license]
*[http://www.novell.com/products/linuxpackages/professional/yast2-sysconfig.html yast2 license - GPL]
*[http://www.suse.com/us/index.html SuSE website]
*[http://www.thejemreport.com/modules.php?op=modload&name=News&file=article&sid=125 SuSE 9.1 Personal Edition review]
*[http://www.linuxdig.com/news_page/1098814198.php SuSE 9.2 Personal Edition review by LinuxDig]
*[http://www.suse.com/us/private/download/ftp/live_eval_int.html 9.2 evaluation CD]

==Internal links==
* Officially recognized LQ [http://www.linuxquestions.org/questions/f60 Suse forum]

=FAQs=
*[[Dual Booting SuSE 9.1 and Windows XP]]

Suse 9.3

2005-04-28T19:11:10Z

TomFrayne: Stub, linked to Suse

Parent [[Suse]]

{{msg:stub}}

SuSE

2005-04-28T19:06:00Z

TomFrayne: laptop, license, Suse 9.3

'''SuSE''' is one of the oldest and most known Linux [[distribution]]s. It is [[RPM]]-based, and it is well known for its stability and for the quality of its configuration toolkit, [[YAST]]. There are SuSE Linux flavours tailored for desktop or laptop, office and server needs.

SuSE is seen as a good distro for beginners (along with [[Mandrake]] or [[Fedora]]) as it provides a user friendly environment, with [[GUI]]'s for configuring hardware in the excellent Yast. [[KDE]] has been integrated into SuSE ([[Gnome]] and other [[window manager]]s are included) providing seamless configuration. Suse declared: "We offer both desktops at the highest possible level to maximize a customer's choice. We also spend a great amount of development effort to make both KDE & Gnome interoperate smoothly."

Originally a German organisation, SuSE was acquired in 2003 by the US networking giant, [[Novell]], but will retain their SuSE brand name and independent operations. This move is intended to give SuSE a better foothold in the US and Novell a significant share in the Linux business.

SuSE was sometimes debated in the free software community because it heavily relied on the [[yast|YAST]] configuration toolkit, that was released under a non-open source license. The YAST2 license for current versions of SuSE is the [[GPL]], so.

The boxed version of [[Suse 9.3]] is a [[Mere aggregation]], in GPL terminology, so it can legally contain non-GPL'd products. Further, the license for Suse 9.3 as a whole allows giving away (but not selling) copies of the CDs and DVDs containing products with proprietary licenses.
==External links==
*[http://br-linux.org/main/arquivos/LICENSE.TXT Suse 9.3 license]
*[http://www.novell.com/products/linuxpackages/professional/yast2-sysconfig.html yast2 license - GPL]
*[http://www.suse.com/us/index.html SuSE website]
*[http://www.thejemreport.com/modules.php?op=modload&name=News&file=article&sid=125 SuSE 9.1 Personal Edition review]
*[http://www.linuxdig.com/news_page/1098814198.php SuSE 9.2 Personal Edition review by LinuxDig]
*[http://www.suse.com/us/private/download/ftp/live_eval_int.html 9.2 evaluation CD]

==Internal links==
* Officially recognized LQ [http://www.linuxquestions.org/questions/f60 Suse forum]

=FAQs=
*[[Dual Booting SuSE 9.1 and Windows XP]]

Gpg

2005-03-29T06:23:06Z

TomFrayne: Link to: GPG signed RPMs

'''GPG''' ('''G'''NU '''P'''rivacy '''G'''uard) is a patent-free, [[GPL]]-licensed version of Pretty Good Privacy (PGP) used to [[encrypt]] and decrypt data. This program uses ''public key encryption'' technology to create a ''key pair'', consisting of a ''secret key'' and a ''public key''.

Your compadres can encrypt messages to you using your public key, which means that this key is available to everyone. Now, these messages can be decrypted using only your secret key, which is why you must safeguard it. So, people can have your public key and you can have the public key of others.

Usage: <tt>gpg ''[option] command''</tt>

==Specific features==
In addition to encryption and decryption capabilities, GNU Privacy Guard also lets you create ''digital signatures'' do ''key signing'' and create ''webs of trust''.

===Digital Signatures===
The concept of Digital Signatures was hatched to verify the authenticity of a message. As the name suggests, the message is digitally signed by the sender. A digital signature is made through a combination of the secret key and the text. Using the senders public key, the message can be verified. Just like a message encrypted using a public key can only be decrypted by the corresponding secret key, a message verified using your public key could only have been signed using your secret key. With the verification, the recipient (or the world) knows that the message came from the sender (or at least someone with access to the sender's private key) and has not been changed during the transportation process. The signature can either be packaged with the original file or sent separately (detached).

To create an [[ASCII]] detached signature for a file with your default key:

$ <tt>gpg -ab ''filename''</tt>

To sign a binary file and attach a signature (encoded message/signature):

$ <tt>gpg -s ''filename''</tt>

To sign an email message (cleartext message with ASCII GPG signature attached):

$ <tt>gpg --clearsign ''filename''</tt>

To verify the signature, enter the name of the detached signature file or the signed file:

$ <tt>gpg --verify ''filename''</tt>

===Key Signing===
Key signing is act of digitally signing a public key and a userid packet attached to that key. Key signing is done to verify that a given user id and public key really do belong to the person that appears to own the key and who is represented by the user id packet.

You can digitally sign your own public key and an associated id on that key, or another person's public key and associated public key packet.

In essence, key signatures validate public keys. They are an endorsement of validity of a public key and associated id by a third party. Just like we all say and know for sure that Jeremy is the owner of LQ. This is the way in which key signing builds the web of trust.

===[[GPG signed RPMs]]===

See [[GPG signed RPMs]] for a description of how GPG signed files are used to improve the security of [[Package]] management.

===Web of Trust===
A web of trust is a term used to describe the trust relationships between a group of keys. You can think of a key signature as a link, or a strand, in the web of trust. These links are called Trust Paths. Trust paths can be bidirectional or only one way. The ideal web of trust is one in which everyone is connected bidirectionally to everyone else. In effect, everyone trusts that every key does in fact belong to its owner. The web of trust can be thought of as the sum of all the trust paths, or links, between all key holding parties.

===Using GPG===
Here is a list of commands you can use with [[gpg]]. The section is formatted with commands on the left and the function they do on the right.

====Commands====
*-b, --detach-sign: Create a detached digital signature.
*-c, --symmetric : Encrypt with a symmetric cipher.
*-b, --detach-sign: Create a detached digital signature.
*-c, --symmetric: Encrypt with a symmetric cipher.
*--clearsign: Create a cleartext signature.
*--decrypt filename: Decrypt the specified filename, verify the signature(if any), and write it to the standard output. Use the --output option to write to a specified file.
*--delete-key name: Remove key from the public key ring.
*--delete-secret-key name: Remove key from he secret and public key ring.
*-e filename, --encrypt filename: Encrypt the specified filename.
*--edit-key name: Launch an interactive utility that enables you to manage keys.
*--export [user ID]: Export all key rings or those with the specified user ID.
*--export-all [user ID]: Export all key rings, or those of the specified user ID, including those that are not compatible with OpenPGP.
*--export-ownertrust: Display the assigned ownertrust value.
*--fingerprint [user ID]: List all keys with their fingerprints or those with the specified ID.
*--gen-key: Launch an interactive utility that generates a new key pair.
*-h,--help: Display available options.
*--import [filename]: Add the keys in the specified filename to the key ring.
*--import-ownertrust [filename]: Update the trust database with the settings specified in filename.
*--list-keys,--list-public-keys [user ID]: Show the keys on the specified key ring, or just those owned by the specified ID.
*--list-secret-keys [user ID]: Show the keys on the specified key ring, or just those owned by the specified ID.
*--list-sigs [user ID]: Show the keys and signatures on the specified key ring or just those owned by the specified ID.
*-s,--sign: Create a digital signature.
*--sign-key user ID: Sign a public key with your secret key.
*--verify [filename]: Verify the digital signature in the specified filename.

====Examples====

*gpg --gen-key: Generates a new key pair.
*gpg --clearsign filename.txt: Creates a clear text signature.
*gpg -e report.txt: Encrypts the specified file. You will be prompted for a destination user ID.
*gpg --decrypt report.txt.gpg: Decrypts the specified file. You will be prompted for the passphrase.

==External links==
*[http://man.linuxquestions.org/index.php?query=gpg&section=0&type=2 gpg man page]
*[http://www.gnupg.org/ GnuPG home page]
*[http://linuxgazette.net/104/oregan3.html KGPG & GPG article]
*[http://en.wikipedia.org/wiki/Public-key_cryptography Wikipedia article on Public-key Cryptography]

Firefox

2005-01-31T20:18:32Z

TomFrayne: How to fix Firefox profile in use problem

'''Mozilla Firefox''' (once known as "Firebird") is a [[cross-platform]], [[open source]], free [[web browser]] available for [[Windows]], [[Mac OS X]], [[Linux]] and a few other systems. Unlike the [[Mozilla]] Suite, which also possesses a [[chat]] client, [[mail]] functions, and web page editor, Firefox is just a browser. It is faster than the full Mozilla suite and is a good choice if you already have, or do not need, a chat client and mail application.

Firefox is now a viable alternative or replacement for Microsoft's browser, [[Internet Explorer]]. With features such as pop-up blocking, tabbed browsing, and perhaps best of all, the Google Toolbar, it allows for increased control over one's web surfing environment.

==History==
Firefox is currently at [[version]] 1.0. Firefox was originally known as Phoenix but was later renamed to Firebird and then, in February 2004, to Firefox, because of confusion with [[FireBirdSQL]].

==Latest major release==
The latest major release of Firefox is Firefox 1.0. For more information about this, see the [http://www.mozilla.org/products/firefox/ Firefox homepage].

==Distribution specific information==

===Debian===
[[Debian]] firefox packages for testing/sarge and unstable/sid users are available in the standard Debian repository, get them with <tt>[[apt-get]] install mozilla-firefox</tt>. Debian stable/woody users can get a backported version [http://www.backports.org here]. A list of available plugins and locales packages can be found with <tt>[[apt-cache]] search --names-only mozilla-firefox</tt>

===Gentoo===
[[Gentoo]] users can install firefox using [[portage]] by typing: 
* <tt>emerge mozilla-firefox</tt>
or
* <tt>emerge mozilla-firefox-bin</tt>
to get the official binary build installed.

==From the new Linux Installer==
Download the latest Linux installer from
[http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/ ftp.mozilla.org].
''(Note: The installer ends in '-installer.tar.gz')''

Extract it to a temporary directory, and go into the 'firefox-installer' directory. Now you must decide whether you want to install firefox system-wide, so that all computer users can use it, or whether to just install it for yourself. When you have finished the install you may delete the 'firefox-installer' directory.

===Installing Firefox for Personal Use===

Run the script called 'firefox-installer', in the firefox-installer directory. (If you are using a gui tool, you should be able to simply click on it) Click next until you are given a choice where to install firefox. You will probably want to install it somewhere like '/home/yourname/programs/firefox'. From there the install should be simple. To run firefox you must either run '/home/yourname/*/firefox/firefox', or make a shortcut to it (varies depending on your desktop environment).

===Installing Firefox System-Wide===

Open a terminal. Type in 'su' to login as the super-user. Use 'cd' to change to the directory where you extracted the firefox-installer (eg. <tt>cd /home/yourname/firefox-installer</tt>). then type in <tt>./firefox-installer</tt>. Click next until you are given a choice where to install firefox. To keep in line with linux standards, you will want to install it to '/opt/firefox'. From there the install should be simple. Once it is completed, go back to your terminal, and while still logged in as root, type in <tt>ln -s /opt/firefox/firefox /usr/local/bin/firefox</tt> (assuming you installed to /opt/firefox). This will mean any user can run firefox by simply typing in <tt>firefox</tt>, just like they were running any other program.

==From Their Binaries==
Mozilla makes nightly binaries available at http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/,
or get the latest release from
http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/

Untar it somewhere in your home directory with "tar -xvzf whatever.tar.gz"
you will have to run it with ./firefox from that directory, or you can create a [[shortcut]] to it.

if you want browser plugins to work, symlink your main plugin directory contents to your new plugins directory. You will want to keep the existing libnullplugin, so rename it before doing so, and rename it back. Main plugin directories are often in /opt/mozilla or in /usr/lib/mozilla-version or similar.

== Firefox tips==
*Type "about:config" in your location bar to get a complete and editable list of Firefox's preferences.
**filter by:
***'''error''' and set the resulting setting to be true for error messages that show in the browser page instead of a pop up
***'''dom''', then set all of the dom.disable options to true if you want to have control over the content in the web browser (these should work with all sites, no site should depend on using these features, they are all [[security hazard]]s when off)
***'''mouse''' set middlemouse.contentLoadURL to false, that way middle clickin on a tab will close it
***'''autoscroll''', set it to true, and you'll middle mouse button wont' paste personal information to a search engine everytime you accidentally click it, also does the autoscroll feature, which is an ergonmic feature, that will save you from finger strain. (IE on windows has this, and firefox on windows has it on by default)

== Firefox troubleshooting==
=== Profile in use after power off===
Firefox uses a file called lock in its profile to determine if the profile is in use. If Firefox is running during a power failure, this file is still there, and Firefox will fail with profile in use message. To fix it, find the lock file and delete it.

Running as user, execute
ls ~/.mozilla/firefox/
to find the profile directories, and find
lock
in one of the directories to remove it. Or you can do the same thing with a file manager such as Konqueror.

==See also==
*[[browser wars]]

== External links ==

* [http://www.mozilla.org/products/firefox/ Official Firefox homepage]
* [http://update.mozilla.org/extensions/ Firefox Themes]
* [http://update.mozilla.org/themes/ FireFox extensions]
* [http://forums.mozillazine.org/ MozillaZine support forums]
* [http://kb.mozillazine.org/index.phtml?title=Mozilla_Firefox The Mozilla Knowledge Base Wiki page on Firefox]

LQWiki talk:How to edit a page

2005-01-10T17:54:49Z

TomFrayne: Request for link to the Links section of Manual of Style

Are there any style guides? --[[User:Caffeine|Caffeine]] 07:34, Mar 6, 2004 (EST)

----
Sort of. [[LQWiki:Manual_of_Style]]. Also check [[LQWiki:Help]] in general.

[[User:Digiot|Digiot]] 07:50, Mar 6, 2004 (EST)

----
End there's the markup guide in [[LQWiki:Wiki_markup]] for people not yet familiar with Wiki - [[User:Streg|Streg]] 07:54, Mar 6, 2004 (EST)

----
For how to do a redirect, see [[LQWiki:How_to_use_a_redirect]].

[[User:JohnMG|JohnMG]] 20:38, Mar 14, 2004 (EST)

----
Find the LQ-wiki faq here: [[LQWiki:FAQ]]

[[User:JohnMG|JohnMG]] 15:47, Mar 27, 2004 (EST)

----

Please add a link to the Links section of [[LQWiki:Manual of Style]] in the sample markup section.

Udev

2004-12-18T17:27:09Z

TomFrayne: default naming scheme, links

'''udev''' is a replacement for [[devfs]], meaning it manages the /dev directory and only creates device files for devices that actually exist in the system. It moves the creation and naming of the devices files to [[userspace]]. The main advantage of this is that device naming schemes can be easily changed and it doesn't depend on static minor/major numbers anymore. It also means devices can be moved around (e.g. different pci slot,adding hard disks,etc) without their name changing. There are different naming schemes available, like one replicating the devfs names or one using the traditional (flat directory structure) names.

The default naming scheme in [[Fedora|fc3]] places new hotplugged devices in /dev/mapper. Some devices are also put into [[fstab]] automatically by [[fstab-sync]]. See [[Removable]].

Udev been added in the Linux [[2.6]] [[kernel]] versions, and devfs has been marked obsolete.

The only thing that devfs does and udev not, is loading kernel modules when a device is being opened. This isn't seen as a needed feature for udev, since loading of kernel modules is handled automatically by [[hotplug]]. But this does mean that all the modules for all the existing devices are always loaded. If for some weird reason (for example, you want save some memory used by the modules) you don't want that, you'll have to use devfs or some manual script to handle that.

It usually mounts a [[tmpfs]] over the /dev directory, and [[hotplug]] is used to receive notification whenever a device is added/removed. The [[sysfs file system]] is used to get the information about the devices.

==Configuration==
All the configuration files are normally located in /etc/udev.
The different naming policy are configured in files ending with .rules. The udev.conf is the main config file, where the used rules and permissions can be configured.

==External links==
*[http://www.kroah.com/linux/talks/ols_2003_udev_talk/ Slideshow] from a talk given about udev
*[http://archive.linuxsymposium.org/ols2003/Proceedings/All-Reprints/Reprint-Kroah-Hartman-OLS2003.pdf Paper] about udev.

{{stub}}

Hotplug

2004-12-18T17:13:52Z

TomFrayne: hotplug in 2.6

To '''hotplug''', or hotplugging, means plugging a hardware device of some kind into a running computer and having it work without requiring a reboot of the computer.

The most common devices that support this are [[USB]] devices.Other device that can be hotplugged are [[PCMCIA]]/[[CardBus]], [[Firewire]], [[CompactPCI]], 'normal' [[PCI]] (through use of a special hotplug controllers), [[IDE]] (some [[RAID]] controlles support this), [[SCSI]], [[CPU]]s, memory and [[laptop]] power docking stations.

==Hotplug in kernel 2.6==
Hotplug is a standard part of the 2.6 kernel. It works with [[udev|udev, see also]] and [[hal]] to add hotplugged devices into /dev/mapper automatically.

==Hotplug vs Hotswap==
The confusion around hotswap and hotplug are dense. Some say they are two names for the same thing, but that isn't entirely true. Normally a hotplug device needs to be shutdown, the power needs to be shut off, before removal. A hotswap device can be plugged out right away and replaced without any preparations.

'''When do this difference matter?''' 
This becomes important when dealing with equipment like PCI cards or harddisks. These can't be removed unless they are hotswap capable or if you power it down. Doing so may damaged your computer severely. When dealing with USB I'm not sure if that functionality should be named hotswap rather than hotplug. USB is designed to be able to do hotswap out of the box so to speak.

[additions and corrections]
==Linux hotplugging==
Hotplugging support in Linux is made out of two parts, a [[kernel]] part that deals with generating events when there is a change in the devices (e.g. a device is disconnected). This event is then passed to a command in [[userspace]]. This part is usually handled by the <tt>hotplug</tt> command, but could easily be replaced with some other implementation. 
'''Note:''' hotplug also supports ''coldplugging'', that means it can be called at boot to configure all the currently connected devices. And because it supports most types of devices it works like a full [[Automatic Hardware Configuration]] tool.

===Kernel part===
In [[kernel]] version 2.4 Linux got a hotplug mechanism (though it's also been backported to 2.2).
If a kernel supports hotplug it will have a file called <tt>/proc/sys/kernel/hotplug</tt>. This file contains the path to the command which the kernel will call to handle the 'event' (e.g. a device being connected or removed). This normally is <tt>/sbin/hotplug</tt> or can be set to <tt>/bin/true</tt> to disable hotplugging. It also requires [[kernel module]]s support in the kernel (which is default in almost every kernel).

===Userpace part===
The userspace part is the ''hotplug'' package, which comes from the Linux hotplugging project[http://linux-hotplug.sourceforge.net/] and is available in many [[distribution]]s (called 'hotplug' in most cases). Hotplug handles loading of the proper [[kernel module]]s when a device is hotplugged, but also does coldplugging (through 'synthesizing' the hotplug events during boot). When it is installed by a version made for your [[distribution]] it shouldn't need any manual configuration.

'''Note''', you may still hotplug, say, USB devices without the "hotplug package" installed -- you'll just have to manually take care of loading kernel modules yourself if necessary (by modifying config files and using [[modutils]], or else using something like [[modconf]]).

==See also==
*[[udev]] - can manage the /dev/ devices directory, creates devices based on hotplug events.
*[[initrd]] - initial ramdisk support. Hotplug + initrd allows for a fully modular and automatically configured kernel.

Hard disk

2004-12-18T17:04:38Z

TomFrayne: /* See also */ Removable hard drives

'''Hard disk'''s are the main storage media used on [[computer]]s. Hard disks are "hard" disks or "fixed" disks in the way that they are not usually intended to be portable like floppies or optical disks. Portable [[USB]] hard drives, or the [[IBM]] Microdrive represents a change in this, as miniaturization increases. Hard disks have the largest storage capacities and highest performance speeds of the several varieties of storage media. The first hard drive for the PC had a capacity of something like 10MB while drives up to 300GB are becoming increasingly common today.

==Physical structure==
Hard disks are made of (usually several) inflexible round, flat disks called "platters". The platters are rotated at a high speed by a spindler motor. Information is written to and read from the platters by builtin read/write heads.

A hard drive can be placed in a portable [[enclosure]] that can be [[hotplug]]ged into the machine while it is stopped, without requiring hardware modifications. In some [[hardware configuration]]s, the enclosure can be hotswapped without requiring the machine to be rebooted. This allows multiple hard drives in separate enclosures to be treated as [[removable]], as if they were just large capacity floppy disks. The most common form factor today is still 3.5 inch. Other common form factors are 5.25 inch, 2.5 inch and 1.0 inch models.

==Hard disk interfaces==

Hard disks also come in several flavors such as [[Integrated Drive Electronics|IDE]] (actually [[ATA]]), [[SCSI]] and [[SATA]], as do optical drives. ATA is the most common interface used today. SCSI disks can usually be found on servers.

==Hard disks in Linux==
In Linux the hard disks are located in the /dev -directory. ATA hard disks are identified as hda, hdb, hdc, and hdd. See [[IDE tree mapping]] for more info. SCSI hard disks are listed as devices sda, sdb, sdc, sdd, sde, sdf, and sdg. For example, /dev/sda refers to SCSI hard disk a.

The space on a hard disk is usually divided into separate segments called [[partition]]s.

==See also==
* [[Add a new hard drive]]
* [[Partition a hard drive]]
* [[Blanking a hard drive]]
* [[Disk space]]
* [[Disk and tape drive commands]]
* [[Removable]] hard drives

Umount

2004-12-11T19:50:52Z

TomFrayne: mount, umount, fuser, lsof don't work

'''umount''' (''not'' "u'''n'''mount") detaches a volume from the file hierarchy - unmounting it. This may be necessary in order to stop a removable disk in order to ensure the filesystem is left in a consistent state so you can remove it.

For example, if /dev/hdc1 is mounted as /mnt/onedisk then you will be able to browse the contents of hdc1 as though it were just another [[directory]]. However, once you "umount" it, it will appear devoid of content. It doesn't mean that there isn't anything on hdc1 - it just means that the [[kernel]] is no longer associating /mnt/onedisk with hdc1. This can be remedied by using [[mount]] to restore this association.

== "device is busy" errors ==

A common issue when attempting to unmount devices currently mounted is that umount will refuse, stating that the device is currently busy. One must close the file in all the [[process]]es that are using the device (that is, accessing files or using the device directly). If you don't know what is using the device, use [[fuser]], or use [[lsof]], ''as root'':

su
lsof /media/cdrom

Alternatively, if the device is mounted in the [[filesystem]], and you are currently in that filesystem, simply changing directory first will often allow umount to do its work.

== [[mount, umount, fuser, lsof don't work]] ==

Go here as the last resort to solve mounting problems before rebooting

==See also==
* [[mount]]

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

Disk and tape drive commands

2004-10-24T00:11:30Z

TomFrayne: Reorganize. Add tune2fs

==Disc and Tape Drives Commands==
===New drive, configuring hard drive===
====[[Partitioning]], [[formatting]] and [[tuning a file system]]====
=====Partitioning=====
* [[parted]] - command line partitioning tool. (parted sometimes complains about boundaries of partitions created with fdisk. parted can format a partition of type ext2 or fat32 partition while creating it.)
* [[fdisk]] - Launches a menu-driven program that partitions a hard disk.
* [[cfdisk]] - Interactive hard disc partition utility for text mode.
=====Formatting=====
* [[mkfs]] - front-end to various filesystem-creation tools
** parted can create a filesystem while partitioning
** mkfs.vfat /dev/sde1 to format a fat32 partition sde1
** mkfs.ext2 /dev/sde2 to format an ext2 partition sde2
=====Tuning=====
* tune2fs - command to tune ext2/ext3 filesystems
** tune2fs -j /dev/sde2 to convert an ext2 filesystem sde2 to ext3 by adding a journal
** tune2fs -L /dev/sde2 bulkdata to set the volume label of sde2 to "bulkdata"
* [[debugfs]] - Interactive utility to repair the ext2 filesystem on specified drive.
* [[e2fsck]] - Performs an analysis of the filesystem's integrity and optionally repairs errors.
* [[badblocks]] - Scans the specified drive for bad blocks.
----
====[[Logical Volume Management]] ([[LVM]])====
This is a stub.
----
===Using a configured hard drive or tape===
====Managing file systems====
* [[autorun]] - Automatically recognizes all available CD-ROM drives.
* [[df]] - Displays the amount of disc space used and remaining on all mounted filesystems.
* [[mount]] - Attaches the device to a specified directory, which will serve as the filesystem's mount point.
* [[umount]] - Unmounts the filesystem specified by the device.
* [[sync]] - Flushes the filesystem buffers.
----
====Managing files, folders, directories====
* [[du]] - Displays the amount of disc space used in the current directory.
** [[duchs]] - Lists the largest directories in human readable format
* [[eject]] - Ejects the media in the specified drive.

----

Disk partitioning

2004-10-23T23:50:39Z

TomFrayne: Description, link to list of tools

==Partitioning==

The first step in preparing a new hard drive that will contain several [[file system]]s for use is partitioning. Tools to do this are listed at [[Disk_and_tape_drive_commands]].

Switching to Linux from Windows

2004-08-24T19:07:36Z

TomFrayne: Link to Thunderbird

Parent: [[FAQ - operating systems]]
See: [[FAQ - Linux kernel and desktop]], [[TOC - Common questions(FAQ)]]

This page discusses the questions: Which Windows users should switch to Linux? Why? When? How?

To summarize:
* Most should switch; exceptions: those not upgrading
* To avoid Microsoft, improve performance, stability, and security, to lower costs
* Start now, but don't hurry to finish
* Switch gradually; minimize programming changes after the switch; plan to use Windows emulators for applications with no Linux equivalent.

==Switching to Linux from Windows==
===Who? Why? When? How?===

====Who is doing it - IBM, Novell, etc.====

====Why switch====

====Who should wait; who should switch now====

====Switching gradually - multi-platform [[FOSS]] programs====
Often, the hardest part of switching to Linux is leaving behind Microsoft applications and other applications that run only on Windows. This roadblock can often be bypassed by starting to use [[Multi-platform]] applications that run on both Windows and Linux while still running on Windows. The advantages over a direct switch to Linux are:
* You can still run the Windows applications
* You can get used to differences in the user interfaces gradually as you have time instead of in the middle of an important project
* You can convert important data to the FOSS formats while the Windows applications are there to help, and archive less important data for conversion as needed

The most important mult-platform applications are replacements for basic Windows applications that you use:
* Web Browser - use [[Mozilla]] instead of [[Internet Explorer]]
* Office - use [[OpenOffice]] instead of [[Microsoft Office]]
* Email - use [[Thunderbird]]

See [[Linux software equivalent to Windows software]] for more examples, but, while you are running on Windows, limit yourself to the multi-platform or [[Cross-platform]] applications.

See [http://www.desktoplinux.com/articles/AT7010636622.html Switching to Linux gradually] for a more detailed discussion.

====The Linux distribution for you====

====Windows emulators in Linux - Wine, Win4Lin====

====Linux replacements for Windows applications====

====Linux usability vs Windows usability====

====Other factors in deciding to switch====

===Trying Linux for the first time===
====Running Linux from a CD====
=====Choices of distributions that run from a CD=====
* [[Knoppix]]
* [[Suse]] 9.1 evaluation CD
=====Steps to get started with your choice=====
* [[Download]] an [[ISO]] file for a bootable CD
* [[CD/DVD Burning|Burn]] the bootable CD
* Read getting started information on the CD - often a [[README]] file
* Boot the CD
* Try basic tasks such as internet access, email, writing and printing a letter
====Picking a Linux distribution====
====Buying a machine with Linux pre-installed====
When I wanted a laptop with Linux pre-installed and configured, I found that the major vendors like Dell and IBM offered them in quantity to corporations, but did not offer them to consumers. I bought from [[Los Alamos Computers]], which also offers pre-configured desktop machines, and have been very satisfied.

Now a Google search for buy "linux laptop" produces 30,500 hits, including
[http://tuxmobil.org/reseller.html Linux laptop vendor list]. Further, Redhat, IBM, and Novell all seem to be pushing Linux for desktop use, so the number of choices for vendors should increase rapidly.

Note: If you buy a machine with Windows pre-installed and don't accept the license by clicking the Accept button, you can get a refund from Microsoft. However, when you can buy a cheaper equivalent machine with Linux pre-installed, why bother?

====Installing a distribution====

====Task-oriented tips for [[Windows]] power users====
Windows power users will want to know how to do tasks in Linux that they were used to doing in Windows. See [[Windows to Linux Migration]].

----

==Compatibility with Windows==
* [[Wine]]
* [[Win4Lin]]
* [[OpenOffice]] and [[AbiWord]]/[[Gnumeric]]
* [[OpenOffice]], [[Mozilla]], [[Apache]] - reverse compatibility
===Windows applications -> Linux applications===
* [[Application Crossover Chart]] - Mapping from Windows to Linux

==See also:==
* [http://www-106.ibm.com/developerworks/ondemand/migrate/linux.html?ca=dgr-lnxw03MigrateLin IBM migration guide] aimed at corporations switching to Linux

Switching to Linux from Windows

2004-08-24T18:49:36Z

TomFrayne: Link to IBM migration guide

Parent: [[FAQ - operating systems]]
See: [[FAQ - Linux kernel and desktop]], [[TOC - Common questions(FAQ)]]

This page discusses the questions: Which Windows users should switch to Linux? Why? When? How?

To summarize:
* Most should switch; exceptions: those not upgrading
* To avoid Microsoft, improve performance, stability, and security, to lower costs
* Start now, but don't hurry to finish
* Switch gradually; minimize programming changes after the switch; plan to use Windows emulators for applications with no Linux equivalent.

==Switching to Linux from Windows==
===Who? Why? When? How?===

====Who is doing it - IBM, Novell, etc.====

====Why switch====

====Who should wait; who should switch now====

====Switching gradually - multi-platform [[FOSS]] programs====
Often, the hardest part of switching to Linux is leaving behind Microsoft applications and other applications that run only on Windows. This roadblock can often be bypassed by starting to use [[Multi-platform]] applications that run on both Windows and Linux while still running on Windows. The advantages over a direct switch to Linux are:
* You can still run the Windows applications
* You can get used to differences in the user interfaces gradually as you have time instead of in the middle of an important project
* You can convert important data to the FOSS formats while the Windows applications are there to help, and archive less important data for conversion as needed

The most important mult-platform applications are replacements for basic Windows applications that you use:
* Web Browser - use [[Mozilla]] instead of [[Internet Explorer]]
* Office - use [[OpenOffice]] instead of [[Microsoft Office]]

See [[Linux software equivalent to Windows software]] for more examples, but, while you are running on Windows, limit yourself to the multi-platform or [[Cross-platform]] applications.

See [http://www.desktoplinux.com/articles/AT7010636622.html Switching to Linux gradually] for a more detailed discussion.

====The Linux distribution for you====

====Windows emulators in Linux - Wine, Win4Lin====

====Linux replacements for Windows applications====

====Linux usability vs Windows usability====

====Other factors in deciding to switch====

===Trying Linux for the first time===
====Running Linux from a CD====
=====Choices of distributions that run from a CD=====
* [[Knoppix]]
* [[Suse]] 9.1 evaluation CD
=====Steps to get started with your choice=====
* [[Download]] an [[ISO]] file for a bootable CD
* [[CD/DVD Burning|Burn]] the bootable CD
* Read getting started information on the CD - often a [[README]] file
* Boot the CD
* Try basic tasks such as internet access, email, writing and printing a letter
====Picking a Linux distribution====
====Buying a machine with Linux pre-installed====
When I wanted a laptop with Linux pre-installed and configured, I found that the major vendors like Dell and IBM offered them in quantity to corporations, but did not offer them to consumers. I bought from [[Los Alamos Computers]], which also offers pre-configured desktop machines, and have been very satisfied.

Now a Google search for buy "linux laptop" produces 30,500 hits, including
[http://tuxmobil.org/reseller.html Linux laptop vendor list]. Further, Redhat, IBM, and Novell all seem to be pushing Linux for desktop use, so the number of choices for vendors should increase rapidly.

Note: If you buy a machine with Windows pre-installed and don't accept the license by clicking the Accept button, you can get a refund from Microsoft. However, when you can buy a cheaper equivalent machine with Linux pre-installed, why bother?

====Installing a distribution====

====Task-oriented tips for [[Windows]] power users====
Windows power users will want to know how to do tasks in Linux that they were used to doing in Windows. See [[Windows to Linux Migration]].

----

==Compatibility with Windows==
* [[Wine]]
* [[Win4Lin]]
* [[OpenOffice]] and [[AbiWord]]/[[Gnumeric]]
* [[OpenOffice]], [[Mozilla]], [[Apache]] - reverse compatibility
===Windows applications -> Linux applications===
* [[Application Crossover Chart]] - Mapping from Windows to Linux

==See also:==
* [http://www-106.ibm.com/developerworks/ondemand/migrate/linux.html?ca=dgr-lnxw03MigrateLin IBM migration guide] aimed at corporations switching to Linux

Windows to Linux Migration

2004-08-24T18:37:01Z

TomFrayne: Link to Switching_to_Linux_from_Windows

I would love to see a section for "ex-windows power users". For people who know what has to be done and how to do it in windows, but not yet how it is done in Linux. This would 'tasks equivalent' list partner to the software equivalent list available at http://linuxshop.ru/linuxbegin/win-lin-soft-en/table.shtml

The key advantage of a task equivlent list would be ex-windows people would be able to search on key words which they already know to find the linux method of performing the task. Quite a lot of the time I have taken to learn linux was taken up by just finding which keyword to seach on. One complication I've identified so far - we'll need instructions for the CLI, KDE & Gnome, but it would probably complicate things too much to support all the oher desktops etc out there...

An example of a few items to get started:

=== Set File Associations ===

In Windows 
Explorer | Tools | Folder Options | File Types

In Linux 
Configuration | KDE | Components | File Associations

Gnome instructions go here...

=== Clear Browser History ===

Windows IE

Internet Explorer | Tools | Internet Options | General Tab | Clear History

Linux

KDE 
The history is stored in ~/.kde/share/apps/konqueror/konq_history
To Clear Go Konqueror | Setting Configure Conqueror | History Sidebar (9th item down on left side panel) | Clear History

=== Kill a crashed App ===
==== In Windows ====
Ctrl-Alt-Delete

==== In Linux ====
Ctrl-Esc bring up a task list, and allows the user to select and kill a process.

Ctrl=Alt-Esc invokes XKill, which changes the cursor to Skull & Crossbones - and allows the user to kill a program by positioning the cursor over the crashed program and clicking to kill it.

----

I apologize for editing your comments (which I definitely don't think should be done as a general rule) but all I did was remove the excessive equal signs and put breaks in where your text indicated you wanted them. No need for pages that would be broken on anything but 1600x1200 or higher.

(( INTERJECTION: I edited them too. To use Wiki header syntax. [[User:Fennec|Fennec]] 22:06, Mar 5, 2004 (EST))

Quote: 
In Windows 
Explorer | Tools | Folder Options | File Types

In Linux 
Configuration | KDE | Components | File Associations

Impossible, really. That's not how Linux works. You don't 'set file associations in Linux'. Setting that varies from KDE to Gnome to non-IDEs and from file manager to file manager. You set file associations in midnight commander and gentoo and emelfm and and and. If you set file associations at all. bash has no file associations. But something like that could be very useful - it's a good idea. It'd just have to be carefully done and require a lot of qualifying - lots of ifs, ands, and buts. 'There's more than one way to do it' and Linux isn't so much about following a rote set of steps. Even './configure, make, make install' is excessive simplification.

BTW, it's customary to separate and sign comments.

[[User:Digiot|Digiot]] 06:50, Mar 1, 2004 (EST)

===See Also===
* [[Windows]]
* [[Windows Replacement]]
* [[Linux Migration]]
* [[Switching_to_Linux_from_Windows]]

Firewall

2004-08-24T18:09:05Z

TomFrayne: Firewall for home NFS LAN on router

Parent: [[Security]]

A '''firewall''' is a piece of [[hardware]] or [[software]] put into the network to control and/or prevent communications forbidden by the [[network policy]] and/or intrusions from the Internet. A firewall often has [[routing]] capabilities to allow [[DMZ]]s or [[honeypot]]s to be used to keep local users separate from Internet server traffic.

==Linux and Firewalls==
Linux is secure enough to be used on the internet without a firewall, provided that you're using it just as a client, and don't have any remote services running. Most [[distro]]s have all remote services turned off by default. If you have ''any'' [[windows]] machines, or are running a server, you should have a firewall. Linux machines are often used as firewalls, and some [[soho]] broadband routers are actually embedded devices running Linux.

==Linux firewall software==
A lot of different firewall witing software is available for Linux, ranging from easy [[GUI]] apps for desktop PCs to dedicated [[firewall distributions]]. They all use the packet filtering method provided by the Linux [[kernel]]. 
The 3 Linux user interfaces to the kernel packet filter system started with [[ipfwadm]] then upgraded to [[ipchains]] and now [[iptables]]. All 3 interfaces are available as kernel options and user packages. Since the 2.4 kernel, the packet filter is called [[netfilter]] and offers "stateful" matching. 
Linux firewall writing software is usually a frontend for iptables/ipchains, and allows more user friendly methods (GUI, easier text based config file, etc.) to create firewall rules, then uses a script that runs at boot time (or whenever the rules are changed) to load the rules. It is common to have more than one script as each one adds rules to the existing set. Scripts must specifically have entries to clear, flush and remove rules/tables. 
The rule system is always improving in quality and variety. The development modules are usually found in the [[patch-o-matic]] section of the [[netfilter]] website and are frequently incorporated into the kernel sources once they are stable and popular.

===Specialized Firewall Linux Distributions===
See [[Firewall distributions]] for a complete list.

===Firewall scripts/console apps===
*[[Iptables|iptables/netfilter]]
** [[Manual configuration of an iptables firewall]]
*** [[A basic firewall configuration suitable for a workstation]]
*** [[A basic firewall configuration suitable for a gateway/nat]]
*** [[Script Firewall for home NFS LAN on router]]
** [[Scripted firewall configuration]]
*** [[Shorewall]] configuration tool for netfilter
*[[BullDog]]
*[[ferm]]
*[[fireHOL]]
*[[gShield]]
*[[IPmenu]]
*[[Shorewall]]
*[[Turtle Firewall]]
*[[TuxFrw]]
*[[yaft]]

===GUI/X firewall applications===
*[[Graphical and interactive firewall configuration]]
** [[fwbuilder]] - GUI for configuring firewalls
** [[Using GNOME lokkit for firewall configuration]]
** [[fireflier]]
** [[firestarter]]
** [[Guarddog]]
** [[gShieldConf]]
** [[Knetfilter]]

===Web interface firewall applications===
*[[easyfwgen]]
*[[webmin]]

==See also==
*[[A basic firewall configuration suitable for a workstation]]
*[[A basic firewall configuration suitable for a gateway/nat]]
*[[packet filtering]]
*[[routing]]
*[[DMZ]]
*[[proxy]]
*[[honeypot]]
*[[security]]

==External links==
*[http://www.linux-firewall-tools.com/linux/ Linux Firewall and Security Site]

{{msg:stub}}

Script Firewall for home NFS LAN on router

2004-08-24T18:08:09Z

TomFrayne: Sample firewall script

Parent: [[Firewall#Firewall_scripts/console_apps]]

I am running Fedora (FC1) on a system connected by a hardware router to DSL and two other PC's in my home, where I use NFS for data transfer. I trust nothing on the internet and everything on the three computers. Therefor, I want to set up my iptables to accept any new INPUT from these three computers and only input from established sessions from anywhere else.

I had a hard time figuring out what the iptables -L output corresponding to a script is to construct the script, so here is the output corresponding to the script below:

:[root@localhost root]# iptables -L
:Chain INPUT (policy DROP)
:target prot opt source destination
:ACCEPT all -- FrayneLaptop anywhere
:ACCEPT all -- asus anywhere
:ACCEPT all -- localhost.localdomain anywhere
:ACCEPT all -- anywhere anywhere state :RELATED,ESTABLISHED

:Chain FORWARD (policy DROP)
:target prot opt source destination

:Chain OUTPUT (policy ACCEPT)
:target prot opt source destination
:[root@localhost root]#

The first time I tried, I destroyed the GUI desktop by neglecting to put in the lo line. If you make a similar mistake, you can use Ctrl-Alt-F1 to go into console mode, logon as root, execute the following to disable the firewall at boot, and reboot with no firewall to fix the problem.

:iptables -A INPUT -j ACCEPT

To use the script, save it in a .sh file, say /home/tom/Tom-iptables.sh, make it executable and execute it by executing as root:

:chmod +x /home/tom/Tom-iptables.sh
:/home/tom/Tom-iptables.sh

==Script Firewall for home NFS LAN on router==

: #!/bin/sh
: #/home/tom/Tom-iptables.sh
: # Clear out the old firewall by running the following as root:

:iptables -F
:iptables -X

: #Setup the new firewall:

: #Accept anything from the two other computers on the LAN
:iptables -A INPUT -j ACCEPT -s FrayneLaptop
:iptables -A INPUT -j ACCEPT -s asus

: #Accept anything from the local computer (needed to run the GUI desktop)
:iptables -A INPUT -j ACCEPT -i lo -s 127.0.0.1

: #Accept related packets from established sessions
:iptables -A INPUT -j ACCEPT -m state --state ESTABLISHED,RELATED

: #Accept any output packets
:iptables -P OUTPUT ACCEPT

: #Drop all other input packets
:iptables -P INPUT DROP
:iptables -P FORWARD DROP

: # Add the following line to /etc/sysconfig/network to stop the scripts from
: # modifying your custom firewall (I did not):

: # FIREWALL_MODS=no

: # Finally you save your firewall configuration to /etc/sysconfig/iptables and
: #enable it to (in Fedora) to survive reboot with:

:service iptables save
:chkconfig iptables on

Talk:SCOvIBM-PSJ

2004-08-01T20:21:38Z

TomFrayne: Response to PSJ comments by AllParadox

Tom:

A brief observation: these pages could be harder-hitting by being less strident.

I have the feeling that you would like all kinds of persons to use these pages as a serious resource, but in particular, attorneys and paralegals for TSG, IBM, Novell, Red Hat, Daimler-Chrysler, and AutoZone, managers for those same companies, and judges and clerks for the related cases.

If that is the case, then insults and personal attacks must be seriously curtailed, and in particular, allegations of lack of integrity must be very carefully handled, and kept to an absolute minimum. As an example, when I saw the comment "this is the stupidest yet", my first thought was "Oh, Really? And where did YOU go to law school, and in which State did YOU pass the Bar exam?" Even if it is undeniably "the stupidest yet", you have lost your audience.

:That was the title of a comment in Groklaw that I was citing. I did not state it myself, and I try to avoid making such statements. Sorry for the delay. I was in the hospital. [[User:TomFrayne|TomFrayne]] 16:21, Aug 1, 2004 (EDT)

In law school, lawyers are trained to avoid calling anyone a liar. Even if that person does nothing but lie, there are more effective ways to deliver the message. I was never satisfied with the law school explanations I received, but I sure knew the gut feeling in court when I heard the allegation. It grates, badly.

Alleging that someone has acted in "bad faith" is only a hair less obnoxious than calling them a liar. For an attorney, dishonesty by lying, and dishonesty by bad faith, are unprofessional and unethical conduct, deserving a professional sanction, up to and including permanent loss of license. I suggest that, at most, you make a single allegation in a Wiki area like the SCO suits, and that only after posting the incontrovertible statements, use a phrase like "and these inconsistencies may show bad faith".

:In the section that I think you refer to, I mentioned the actions and statements I objected to, and ended with the statement: "If IBM is right, that implies that SCOG has not complied with the court orders with respect to the evidence it cited. If SCOG cannot supply a valid reason for this non-compliance, it acted in bad faith." I think that this is close enough to what you suggested. [[User:TomFrayne|TomFrayne]] 16:21, Aug 1, 2004 (EDT)

If you believe that unethical conduct has happened, then the proper place to make the allegation is in your letter to the proper Bar Committee for unethical conduct. Do not do this until after your attorney is under retainer. These people will sue for libel, possibly even if you are perfectly correct.

For my part, given the effect on the audience, I would not use it at all.

--[[User:AllParadox|AllParadox]] 18:00, Jul 28, 2004 (EDT)

:I have already sent several criminal complaints about SCOG to the SEC, but my purpose here is not to accuse SCOG of crimes. IBM's reply on the PSJ motion is due on August 15, and I am trying to organize the undisputed facts and arguments that IBM might want to put into that reply. For example, SCOG is bragging about its good faith in complying with the court orders, and a court decision in favor of SCOG might cause the PSJ motion to be delayed while SCOG seeks 2 billion lines of AIX code in addition to the hundreds of millions of lines that SCOG already has. [[User:TomFrayne|TomFrayne]] 16:21, Aug 1, 2004 (EDT)

----

Tom:

Some thoughts on order of issues.

Put first the procedural steps that must be handled before the merits of the PSJ itself. This would put dismissal issues first, not because they are most important, but because your readers can concentrate on the substance once they are assured that you have addressed the issue. You do not have to be correct to be believed, but you have to address it. The most effective argument I see is IBM's assertion that this is a compulsory counterclaim, prompted by TSG press releases. This probably nails it.

Put "stay" issues next. Substantive arguments for Summary Judgment are pointless until the issue is "ripe" for decision. In order, IMHO, IBM requests for discovery, then two court orders to respond, then TSG responses and observations about where they appear to fail to address Judge Wells' order, then the order to IBM to produce, and TSG's complaint about the format and contrast IBM's production format with TSG's production format (scanned images of paper, I believe), then IBM's certificate on production, and TSG's certificate on production. After that, time of filing of IBM CC-10, and TSG's possibly tardy 56(f) demand for more discovery. TSG may have a valid defense here that this relates to an issue brought up late in the suit and that they have not had sufficient time to respond. Address the defense with the list: initial IBM discovery demand long ago, two orders to produce, attorney's court presentation that this is about copyright (cannot recall name of counsel) including direct quotes, attorney's affirmation to the court of "30 days is adequate", the Christmas massacre, date of filing of CC-10, and delay before requesting more time for discovery and 56(f) filing. Contrast TSG certification that all discovery requests have been fulfilled. All this documentation and argument will establish that TSG has had far more than sufficient time to perform adequate discovery.

Now address CC-10, the substance of the Partial Summary Judgment motion. There are three issues here that are being intermingled, so separate them.

First, is there a justiciable issue? Put another way, if all of TSG's claims are proven to be true, will TSG be entitled to a judgment? I think the correct answer to this is "yes". This is a very narrow question.

Second, is there substantial evidence to support all the elements of TSG's claims? In other words, is there anything critical to TSG's claims that is missing? It is unfair to IBM to force them to go halfway through a trial, only to get to a point where the court has to grant IBM judgment because TSG has no evidence to support a necessary element. In my opinion, this is a serious problem for TSG. If I were trying the trial for IBM, I would demand proof of every foundation before allowing evidence on the next issue.

Proof of properly constituted corporation: only proper proof is a certificate from Utah Sec. of State. If I were IBM, I would have a copy on hand, just in case.

Proof of "successor in interest". Proper proof is TSG keeper of records as witness, bringing in the APA from Caldera/oldSCO/Tarantella to The SCO Group, dated around 2002. Big problem is that this must clearly show that TSG is merely a reorganized Caldera/oldSCO/Tarantella. My hunch is that it is not, but Utah statutes or case law may support such a conclusion. This needs serious legal analysis.

Proof of Novell-SCO APA assignment from Caldera/oldSCO/Tarantella to The SCO Group. First, I do not think it ever existed. Second, by its own terms, the APA cannot be assigned (narrow legal definition of "assigned" here.). A workaround would might be a written consent from Novell to assign to TSG, but I do not think this exists either. Burden of proof is on TSG. No assignment == end of case, I think.

Proof of Novell-SCO APA through the keeper of records.

Proof of Novell-SCO copyright assignments. I do not believe these exist. TSG will continue with their assertion that the APA transferred copyrights, and "scrivener error". This is contradicted by explicit terms of APA (an "integrated document"), attorneys certifications of review, lack of witnesses to attest to "scrivener error" (needs to be a "scrivener" - an outside person is irrelevant), other issues with APA, and Federal statutory requirements for a specific writing. Judges' opinion in the Novell case that no copyrights clearly passed may be relevant as a scholarly opinion (wasn't this Kimball also?)

Proof of USL-Novell APA, through Novell keeper of records.

Proof of USL ownership of copyrights, through ?Novell/Bell Labs? keeper of records. Very difficult problems here. Sealed USL vs. BSD judgment/settlement. IMHO, an adequate proof will include bringing in the sealed judgment and opening it into the SCO vs. IBM record. Very serious issues of BSD code being back-ported into Unix, without any copyright assignments. Worse, original records of who wrote what may not be in possession of keeper of records. Much of the old Unix was written by people like Richard M. Stallman, who were not employees of Bell labs or any entity under contract with Bell labs, and who just shared code around without signing any kind of copyright assignment. Further, because those people were not employees of Bell Labs, any attempted copyright registration by Bell Labs for their work would have been ineffective, and the work probably passed into the public domain as a matter of law, years ago. This is not a hurdle. A hurdle is a barrier about thirty inches tall. TSG is going to have to cross Mt. Everest barefoot on this one. TSG, unfortunately, has the burden of proof here. Every line of code they claim is being infringed must be shown to be properly owned by them here before they go on.

Proof of non-Ancient Unix. Broderick, for oldSCO? released a free license to versions of Ancient Unix. TSG has burden of proof, either that the license is invalid because oldSCO did not own copyrights for license anyway, or that protected code that is claimed was not part of Ancient Unix, probably because it was written as an update for Sys V from Ancient Unix.

Proof of non-Caldera, non-SCO, non-TSG Linux. Caldera, oldSCO, and TSG, have distributed Linux versions, apparently under the GPL. TSG has the burden of proof that all copyrighted code that they are claiming is not intentionally released under these distributions. If they fail to address the issue, they should lose.

Proof of direct copying lines of Unix in Linux. THIS IS NOT A DISCOVERY SANCTION. This is an issue of proof in anticipation of the jury trial. After the IBM discovery requests, and after TSG's certification that everything has been identified, IBM is entitled to say that no lines of Unix are directly copied into Linux. I do not know what is in the sealed documents, but they must satisfy every requirement above before they can be considered as proof of infringement. Lines of Dynix or AIX copied into Linux, alone, are irrelevant, IMHO. IBM wrote new code into Dynix and into AIX. IBM owns the copyrights on the new code.

Proof of derivative copying of Unix code into Linux. Again, this is not a discovery sanction. This is an issue of existence of proof, before trial. Same comments as for above. This one is a bear. This requires a Gates analysis. This is probably outside the scope of a Wiki support page.

Whew. OK. Third CC-10 issue: Sanctions. At this point, there should be a substantial accumulation of evidentiary citations and argument.

Whatever, cite relevant case law, using terms of art, supported with facts from the record, to show that TSG deserves to lose this now, for their failure to follow the rules. Part of the argument will refer back to the proof of direct copying, a few paragraphs above, showing that even if TSG is prejudiced by being sanctioned, their prejudice is small and difficult to determine.

--[[User:AllParadox|AllParadox]] 22:02, Jul 28, 2004 (EDT)

:Over the next two weeks I plan to improve the organization of this set of pages, and I'll consider your suggestions while I am doing it. Your comments seem to be on Section 3, which is the first section I wrote, and I knew that it contained information that really belongs in other sections. [[User:TomFrayne|TomFrayne]] 16:21, Aug 1, 2004 (EDT)
----

Talk:Main Page

2004-07-24T13:58:11Z

TomFrayne: Licensing suggestion

==Talk:Main Page==

==Suggestions for links==
* [[Open source operating systems]] BSD, etc.

----

==Comments==

----
We need to have a link to the user contributed help page on the main page. maybe user contributed help should get it's own namespace? e.g. help:

[[User:Aaron Peterson/Alternate Main Page]]

----

Hi there,
I'm not sure whether I should add bug reports here. However I find it very disturbing that the adress http://wiki.linuxquestions.org/wiki/Wine and http://wiki.linuxquestions.org/wiki/WINE doesn't take me to the same page just as [[Wine]] and [[WINE]] does.

This time I was lucky not to write a lot on the [[WINE]]-page, but I mean sometime someone will get really upset when they realised that everything they䶥 added to a page was written on a different page!

/Jens
:I have changed the WINE page to redirect to Wine. [[User:David ross|David ross]] 13:54, Mar 7, 2004 (EST)
----

That's because an excellent Wine page had already been contributed. You shouldn't be duplicating pages. Contributions are greatly appreciated, but please view all the help and documentation, study the wiki markup and the layout of the top levels, and search to see if your topic has already been covered before diving in. There is no bug - each of those two pairs of addresses goes to each of that pair of pages.

[[User:Digiot|Digiot]] 07:14, Mar 1, 2004 (EST)

----

On second thought, I was under-valuing the 'plunging forward' aspect. Yeah, better to post twice than not at all. :) My suggestions might be valid, but might have missed the spirit of things a bit.

Still didn't notice a problem with the links though. If there is an issue, reporting the post or possibly leaving a message on an admin's talk page would probably be the best way to go. They'll probably see it here but it's not the most direct way to address them and none of this is relevant to the main page.

[[User:Digiot|Digiot]] 07:41, Mar 1, 2004 (EST)

----

We should always encourage [[LinuxQuestions.org_Wiki:plunging forward|plunging forward]], but we need to make sure that we are not duplicating effort. The content from the WINE page should be integrated into the Wine page, links updated and WINE removed.

[[User:Jeremy|Jeremy]] 23:37, Mar 1, 2004 (EST)
----

I was just wandering why isn't there a forum of www.linuxquestions.org (one that i can find anyway) for the wiki. I appreciate they are seperate in a way but a forum would be useful.

[[User:Geniarse|generic_genus]] 03:38, Mar 2, 2004 (EST)
----

Do you mean a place to discuss issues/directions about the Wiki itself? - if so, you can check out the new Wiki mailing list here:

http://lists.linuxquestions.org/mailman/listinfo/lqwiki-list

[[User:Skyline|Skyline]] 07:23, Mar 2, 2004 (EST)

----

Hey all, I don't know what to think about the following issue. If you try to type hash(the thing above the number 3), it won't print. Instead, the number 1 apperars in it's place.

But the funny thing is, the sandbox also shows the number 1 instead of # but here, in the discuss page it shows # as #.

Strange...

[[User:Linuxlala|Linuxlala]]
----
Linuxlala,

The character # (when it is at the start of a line) is interpreted as the beginning of a numbered list and is replaced with a "1" (or another digit if it is one in a series). When it is embedded in a sentence (such as the previous sentence) it is rendered as a "#". If you want to show use it at the beginning of a line without it being interpreted as a list item, use the <pre> <pre> and </pre> </pre> tags around it like:

<pre> # this should show as a hash. </pre>
# this should begin a numbered list.
# a second entry in the numbered list.

[[User:Texastwister|Texastwister]] 15:31, Mar 5, 2004 (EST)
----

Right Texastwister,

I had also posted this in the wiki mailing list and jeremy replied explaining the same to me.

Thanks.

[[User:Linuxlala|Linuxlala]]
Hi all! Enjoy our summer! RESPECT TO ALL OF YOU FOR YOUR WORK! REALLY. Thhanx. I really appreicate your work! Research has to continue. My biggest respect goes to you.

----
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 - [[LinuxQuestions.org_Wiki:Policies#General_policies|General policies]]

:-- [[User:Skyline|Skyline]] 06:23, Jul 3, 2004 (EDT)

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

[[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 [[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:

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.

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

:: 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. "
::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)

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

Linux-UNIX

2004-07-24T13:32:37Z

TomFrayne: Spelling

This page was moved here from its parent: [[http://wiki.linuxquestions.org/wiki/FAQ_-_operating_systems]]
I am continuing with the recent history. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----
==Linux-UNIX==

=== [[Linux-UNIX|Q: What is the relationship of Linux and UNIX/Unix?]] ===

A: This is an extremely complicated question that confuses many people new to the *nix world. [[History of unix|Historically]], [[Unix]] was developed at Bell Labs in the late 60s, though it didn't really come into its own until development through the 70s. Originally, it was just an experiment on the part of the authors - [[Dennis Ritchie]], [[Ken Thompson]], [[Brian Kernighan]], et al - that attained a sort of acceptance at Bell and excited the academic community.

As Bell was originally forbidden to sell operating systems due to monopoly issues, it was originally distributed in the form of source code on tapes and, the story goes, often with a note saying "Love, Ken [Thompson]". So it was proprietary in the sense that Bell owned it, but open source in the sense that people could see and modify the code. Over the course of time, it became more and more popular (and thus potentially more and more profitable). When Bell (AT&T) was broken up, the legal obstruction to selling Unix was removed. Several different companies developed their own versions of Unix which became increasingly less interoperable and further redistribution of the source code (or any distribution of new code) was forbidden.

Meanwhile, [[Microsoft]] and [[IBM]] came up from underneath, with the [[DOS]]-driven PC, which had a closed-source and proprietary operating system from the start. Through the course of the 80s, Unix faltered due to the beginnings of the shift from mainframes and minicomputers to PCs and due to commercial rivalries between the Unices. And, through the course of the 80s, the [[FSF]] movement rose. In reaction to the failures of closed source Unix (though actually sparked by the issues of a different operating system) [[Richard Stallman]] (usually known as RMS) started the [[GNU]] project in 1984: GNU being a [[recursive acronym]] meaning "GNU's Not Unix" which also takes the frequent Unix-ism of paradox. The only reason it's worth saying that GNU's not Unix is because it is. And it isn't.

The essence of this is the source code issue. GNU tools were coded from scratch and the code was [[Free Software]]. So it was not Unix because it had a different codebase. But it was Unix in that the tools usually had the same name, operated the same way, and could interoperate with proprietary Unix to an extent. They also had GNU extensions which gave them more capabilities than the Unix originals.

Just like a generic PC is a "[[clone]]" of the IBM PC - different stuff made by different people that does much the same thing and often better and cheaper - so GNU was intended to be a "clone" of Unix. The one thing they didn't have was a [[kernel]]. So, in a sense, they had nothing. One could not boot or run a GNU machine - only run GNU tools on some other (usually proprietary) system much as DJGPP can run on DOS or Cygwin can run on Windows now.

Enter the early nineties. As early Unix was fascinating to academics, it remained that way to people like [[Andrew S. Tannenbaum]] who developed an academic teaching version of Unix for students, known as [[Minix]]. [[Linus Torvalds]] was a student interested in, but unsatisfied with, Minix and wished to develop a Unix-like operating system for his 386 PC with its nifty new 32-bit address space. (This is why Linux will run on a 386 and up, but not a 286 and down - assuming that's an issue for you.) In 1991 he announced the existence of his preliminary kernel in a [[Usenet]] post and offered the [[source code]] to the [[hacker]] world. Quickly, legions of developers improved and expanded the kernel under his guidance. With his open source Unix-like kernel, the GNU operating system could finally run free, thus came the term Linux.

Legally, it's a whole other kettle of fish and introduces legalisms like UNIX vs. Unix vs. Unix-like and so on. Unix the name, vs. Unix the system, etc. And there are also naming issues over Linux and GNU. But for the user's purposes, it suffices to know that they are running a Free Software, distributable, non-proprietary Unix-like system that isn't a closed source, restrictively distributed, [[proprietary]] Unix. Over the course of development, Linux has progressed to the point where there is little if anything that can be done with a Unix system that can't be done with it.

----
==Recent history==
The recent history of the relationship of UNIX and Linux has become much more complicated. In a series of source code releases, contracts, sales, licenses, standards, PR, and court actions involving one or more of [[UCB]], [[ATT]], [[USL]], [[Novell]], [[oldSCO]] aka Tarantella, [[SCOG]] aka Caldera, [[IBM]], [[Red hat]], [[Autozone]], [[Daimler-Chrysler]], [[OSF]], [[FSF]], [[FOSS]], the public, etc., the issue of who owns what rights to what parts of Linux and UNIX has become extremely muddled. The following sections outline what issues involve which parties, and give links to further discussion. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----
===USL v UC Berkeley===
USL (ATT's successor) accused UCB of copyright violations. The judge remarked that USL appeared to have violated some of UCB's copyrights, and that the remainder of its code was probably in the public domain. USL settled soon thereafter, so who owns what copyrights in Unix, as it was at that time is a complete muddle. The settlement was sealed, so if the issue of who owns what parts of the original comes up in court, the settlement will have to be unsealed to sort it out.
===[[SCOG v IBM]]===
SCOG accused IBM of contract and copyright violations, but tried to avoid a formal claim of copyright claims. IBM countersued, accusing SCOG of unfair competition via massive false public statements that IBM had violated SCOG's copyrights by IBM's Linux activities.

For details of the following outline, see the above link.
====SCOG's PR====
====SCOG's court claims====
====SCOG's compliance with court orders====
====Current status of the suit====
A hearing is scheduled for August 4. See the link in the following subsection.
[[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
=====[[SCOvIBM-PSJ]]=====
----
===Redhat v SCOG===
Accuses SCOG of unfair trade, and seeks a declaratory judgment. The case is currently stayed (but a motion for reconsideration is pending), waiting for the IBM case. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----
===[[SCOG v Novell]]===
SCOG claimed that Novell falsely and maliciously claimed that SCOG does not own the copyrights that SCOG has publicly proclaimed were violated by Linux. The suit was dismissed, but SCOG was allowed to re-file to claim special damages. Nothing has happened since the suit was refiled.

For details of the following outline, see the above link. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
====Memos and motions====
====Judge's hint that SCOG probably doesn't own the copyrights====
----
===[[SCOG v Daimler-Chrysler]]===
SCOG accused DC, an automobile manufacturer, of failing to respond to an audit request. The judge issued a summary judgment on the merits of the case, ruling against all of SCOG's claims except the lateness issue, and leaving that to be decided later.

For details of the following outline, see the above link. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
====Memos and motions====
====Did SCOG have the right to audit?====
----
===SCOG v Autozone===
SCOG accused Autozone, an automobile parts company, of copyright violations by Autozone's Linux activities, after Autozone switched from [[SysV]] to Linux.
The case is currently stayed, waiting for the IBM and Novell cases. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----
===SCOG v others===
SCOG has waged a massive public campaign of [[FUD]].

They talked in 2003 about mountains evidence of infringement in Linux, enough to go to trial without discovery. After a year and two court order for them to detail their claims to copyrights in Linux, no specific details are public, and IBM claims that SCOG did not comply with either order.

SCOG claimed that the [[GPL]] is unconstitutional and that SCOG never intentionally released a product with its code licensed by the GPL. SCOG advertised ELF as supported by its GPL'd OpenLinux release, but now claims (without details) that ELF in Linux violates SCOG's copyrights.

SCOG nagged Linux distributors to indemnify their customers against IP lawsuits. Some have, and [[OSRM]] has offered lawsuit insurance. I have seen no offers from SCOG to indemnify its customers from IBM's patent and claims, which are pending in court.

I could go on, but I won't. If you want more, see [[Groklaw]], especially the Quote Data Base. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----

Linux-UNIX

2004-07-24T13:31:15Z

TomFrayne: Fix link

This page was move here from its parent: [[http://wiki.linuxquestions.org/wiki/FAQ_-_operating_systems]]
I am continuing with the recent history. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----
==Linux-UNIX==

=== [[Linux-UNIX|Q: What is the relationship of Linux and UNIX/Unix?]] ===

A: This is an extremely complicated question that confuses many people new to the *nix world. [[History of unix|Historically]], [[Unix]] was developed at Bell Labs in the late 60s, though it didn't really come into its own until development through the 70s. Originally, it was just an experiment on the part of the authors - [[Dennis Ritchie]], [[Ken Thompson]], [[Brian Kernighan]], et al - that attained a sort of acceptance at Bell and excited the academic community.

As Bell was originally forbidden to sell operating systems due to monopoly issues, it was originally distributed in the form of source code on tapes and, the story goes, often with a note saying "Love, Ken [Thompson]". So it was proprietary in the sense that Bell owned it, but open source in the sense that people could see and modify the code. Over the course of time, it became more and more popular (and thus potentially more and more profitable). When Bell (AT&T) was broken up, the legal obstruction to selling Unix was removed. Several different companies developed their own versions of Unix which became increasingly less interoperable and further redistribution of the source code (or any distribution of new code) was forbidden.

Meanwhile, [[Microsoft]] and [[IBM]] came up from underneath, with the [[DOS]]-driven PC, which had a closed-source and proprietary operating system from the start. Through the course of the 80s, Unix faltered due to the beginnings of the shift from mainframes and minicomputers to PCs and due to commercial rivalries between the Unices. And, through the course of the 80s, the [[FSF]] movement rose. In reaction to the failures of closed source Unix (though actually sparked by the issues of a different operating system) [[Richard Stallman]] (usually known as RMS) started the [[GNU]] project in 1984: GNU being a [[recursive acronym]] meaning "GNU's Not Unix" which also takes the frequent Unix-ism of paradox. The only reason it's worth saying that GNU's not Unix is because it is. And it isn't.

The essence of this is the source code issue. GNU tools were coded from scratch and the code was [[Free Software]]. So it was not Unix because it had a different codebase. But it was Unix in that the tools usually had the same name, operated the same way, and could interoperate with proprietary Unix to an extent. They also had GNU extensions which gave them more capabilities than the Unix originals.

Just like a generic PC is a "[[clone]]" of the IBM PC - different stuff made by different people that does much the same thing and often better and cheaper - so GNU was intended to be a "clone" of Unix. The one thing they didn't have was a [[kernel]]. So, in a sense, they had nothing. One could not boot or run a GNU machine - only run GNU tools on some other (usually proprietary) system much as DJGPP can run on DOS or Cygwin can run on Windows now.

Enter the early nineties. As early Unix was fascinating to academics, it remained that way to people like [[Andrew S. Tannenbaum]] who developed an academic teaching version of Unix for students, known as [[Minix]]. [[Linus Torvalds]] was a student interested in, but unsatisfied with, Minix and wished to develop a Unix-like operating system for his 386 PC with its nifty new 32-bit address space. (This is why Linux will run on a 386 and up, but not a 286 and down - assuming that's an issue for you.) In 1991 he announced the existence of his preliminary kernel in a [[Usenet]] post and offered the [[source code]] to the [[hacker]] world. Quickly, legions of developers improved and expanded the kernel under his guidance. With his open source Unix-like kernel, the GNU operating system could finally run free, thus came the term Linux.

Legally, it's a whole other kettle of fish and introduces legalisms like UNIX vs. Unix vs. Unix-like and so on. Unix the name, vs. Unix the system, etc. And there are also naming issues over Linux and GNU. But for the user's purposes, it suffices to know that they are running a Free Software, distributable, non-proprietary Unix-like system that isn't a closed source, restrictively distributed, [[proprietary]] Unix. Over the course of development, Linux has progressed to the point where there is little if anything that can be done with a Unix system that can't be done with it.

----
==Recent history==
The recent history of the relationship of UNIX and Linux has become much more complicated. In a series of source code releases, contracts, sales, licenses, standards, PR, and court actions involving one or more of [[UCB]], [[ATT]], [[USL]], [[Novell]], [[oldSCO]] aka Tarantella, [[SCOG]] aka Caldera, [[IBM]], [[Red hat]], [[Autozone]], [[Daimler-Chrysler]], [[OSF]], [[FSF]], [[FOSS]], the public, etc., the issue of who owns what rights to what parts of Linux and UNIX has become extremely muddled. The following sections outline what issues involve which parties, and give links to further discussion. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----
===USL v UC Berkeley===
USL (ATT's successor) accused UCB of copyright violations. The judge remarked that USL appeared to have violated some of UCB's copyrights, and that the remainder of its code was probably in the public domain. USL settled soon thereafter, so who owns what copyrights in Unix, as it was at that time is a complete muddle. The settlement was sealed, so if the issue of who owns what parts of the original comes up in court, the settlement will have to be unsealed to sort it out.
===[[SCOG v IBM]]===
SCOG accused IBM of contract and copyright violations, but tried to avoid a formal claim of copyright claims. IBM countersued, accusing SCOG of unfair competition via massive false public statements that IBM had violated SCOG's copyrights by IBM's Linux activities.

For details of the following outline, see the above link.
====SCOG's PR====
====SCOG's court claims====
====SCOG's compliance with court orders====
====Current status of the suit====
A hearing is scheduled for August 4. See the link in the following subsection.
[[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
=====[[SCOvIBM-PSJ]]=====
----
===Redhat v SCOG===
Accuses SCOG of unfair trade, and seeks a declaratory judgment. The case is currently stayed (but a motion for reconsideration is pending), waiting for the IBM case. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----
===[[SCOG v Novell]]===
SCOG claimed that Novell falsely and maliciously claimed that SCOG does not own the copyrights that SCOG has publicly proclaimed were violated by Linux. The suit was dismissed, but SCOG was allowed to re-file to claim special damages. Nothing has happened since the suit was refiled.

For details of the following outline, see the above link. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
====Memos and motions====
====Judge's hint that SCOG probably doesn't own the copyrights====
----
===[[SCOG v Daimler-Chrysler]]===
SCOG accused DC, an automobile manufacturer, of failing to respond to an audit request. The judge issued a summary judgment on the merits of the case, ruling against all of SCOG's claims except the lateness issue, and leaving that to be decided later.

For details of the following outline, see the above link. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
====Memos and motions====
====Did SCOG have the right to audit?====
----
===SCOG v Autozone===
SCOG accused Autozone, an automobile parts company, of copyright violations by Autozone's Linux activities, after Autozone switched from [[SysV]] to Linux.
The case is currently stayed, waiting for the IBM and Novell cases. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----
===SCOG v others===
SCOG has waged a massive public campaign of [[FUD]].

They talked in 2003 about mountains evidence of infringement in Linux, enough to go to trial without discovery. After a year and two court order for them to detail their claims to copyrights in Linux, no specific details are public, and IBM claims that SCOG did not comply with either order.

SCOG claimed that the [[GPL]] is unconstitutional and that SCOG never intentionally released a product with its code licensed by the GPL. SCOG advertised ELF as supported by its GPL'd OpenLinux release, but now claims (without details) that ELF in Linux violates SCOG's copyrights.

SCOG nagged Linux distributors to indemnify their customers against IP lawsuits. Some have, and [[OSRM]] has offered lawsuit insurance. I have seen no offers from SCOG to indemnify its customers from IBM's patent and claims, which are pending in court.

I could go on, but I won't. If you want more, see [[Groklaw]], especially the Quote Data Base. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----

SysV

2004-07-24T13:30:50Z

TomFrayne: Definition and links

Parent: [[Linux-UNIX]]

==SysV==
SysV is an acronym for Unix System V, a version of the [[UNIX]] operating system produced by [[SCOG]]. See [[Linux-UNIX]].

Linux-UNIX

2004-07-23T19:05:09Z

TomFrayne: Moved Linux-Unix history from FAQ_-_operating_systems. Outlined recent history

This page was move here from its parent: [[http://wiki.linuxquestions.org/wiki/FAQ_-_operating_systems]]
I am continuing with the recent history. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
==Linux-UNIX==

=== [[Linux-UNIX|Q: What is the relationship of Linux and UNIX/Unix?]] ===

A: This is an extremely complicated question that confuses many people new to the *nix world. [[History of unix|Historically]], [[Unix]] was developed at Bell Labs in the late 60s, though it didn't really come into its own until development through the 70s. Originally, it was just an experiment on the part of the authors - [[Dennis Ritchie]], [[Ken Thompson]], [[Brian Kernighan]], et al - that attained a sort of acceptance at Bell and excited the academic community.

As Bell was originally forbidden to sell operating systems due to monopoly issues, it was originally distributed in the form of source code on tapes and, the story goes, often with a note saying "Love, Ken [Thompson]". So it was proprietary in the sense that Bell owned it, but open source in the sense that people could see and modify the code. Over the course of time, it became more and more popular (and thus potentially more and more profitable). When Bell (AT&T) was broken up, the legal obstruction to selling Unix was removed. Several different companies developed their own versions of Unix which became increasingly less interoperable and further redistribution of the source code (or any distribution of new code) was forbidden.

Meanwhile, [[Microsoft]] and [[IBM]] came up from underneath, with the [[DOS]]-driven PC, which had a closed-source and proprietary operating system from the start. Through the course of the 80s, Unix faltered due to the beginnings of the shift from mainframes and minicomputers to PCs and due to commercial rivalries between the Unices. And, through the course of the 80s, the [[FSF]] movement rose. In reaction to the failures of closed source Unix (though actually sparked by the issues of a different operating system) [[Richard Stallman]] (usually known as RMS) started the [[GNU]] project in 1984: GNU being a [[recursive acronym]] meaning "GNU's Not Unix" which also takes the frequent Unix-ism of paradox. The only reason it's worth saying that GNU's not Unix is because it is. And it isn't.

The essence of this is the source code issue. GNU tools were coded from scratch and the code was [[Free Software]]. So it was not Unix because it had a different codebase. But it was Unix in that the tools usually had the same name, operated the same way, and could interoperate with proprietary Unix to an extent. They also had GNU extensions which gave them more capabilities than the Unix originals.

Just like a generic PC is a "[[clone]]" of the IBM PC - different stuff made by different people that does much the same thing and often better and cheaper - so GNU was intended to be a "clone" of Unix. The one thing they didn't have was a [[kernel]]. So, in a sense, they had nothing. One could not boot or run a GNU machine - only run GNU tools on some other (usually proprietary) system much as DJGPP can run on DOS or Cygwin can run on Windows now.

Enter the early nineties. As early Unix was fascinating to academics, it remained that way to people like [[Andrew S. Tannenbaum]] who developed an academic teaching version of Unix for students, known as [[Minix]]. [[Linus Torvalds]] was a student interested in, but unsatisfied with, Minix and wished to develop a Unix-like operating system for his 386 PC with its nifty new 32-bit address space. (This is why Linux will run on a 386 and up, but not a 286 and down - assuming that's an issue for you.) In 1991 he announced the existence of his preliminary kernel in a [[Usenet]] post and offered the [[source code]] to the [[hacker]] world. Quickly, legions of developers improved and expanded the kernel under his guidance. With his open source Unix-like kernel, the GNU operating system could finally run free, thus came the term Linux.

Legally, it's a whole other kettle of fish and introduces legalisms like UNIX vs. Unix vs. Unix-like and so on. Unix the name, vs. Unix the system, etc. And there are also naming issues over Linux and GNU. But for the user's purposes, it suffices to know that they are running a Free Software, distributable, non-proprietary Unix-like system that isn't a closed source, restrictively distributed, [[proprietary]] Unix. Over the course of development, Linux has progressed to the point where there is little if anything that can be done with a Unix system that can't be done with it.

----
==Recent history==
The recent history of the relationship of UNIX and Linux has become much more complicated. In a series of source code releases, contracts, sales, licenses, standards, PR, and court actions involving one or more of [[UCB]], [[ATT]], [[USL]], [[Novell]], [[oldSCO]] aka Tarantella, [[SCOG]] aka Caldera, [[IBM]], [[Red hat]], [[Autozone]], [[Daimler-Chrysler]], [[OSF]], [[FSF]], [[FOSS]], the public, etc., the issue of who owns what rights to what parts of Linux and UNIX has become extremely muddled. The following sections outline what issues involve which parties, and give links to further discussion. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----
===USL v UC Berkeley===
USL (ATT's successor) accused UCB of copyright violations. The judge remarked that USL appeared to have violated some of UCB's copyrights, and that the remainder of its code was probably in the public domain. USL settled soon thereafter, so who owns what copyrights in Unix, as it was at that time is a complete muddle. The settlement was sealed, so if the issue of who owns what parts of the original comes up in court, the settlement will have to be unsealed to sort it out.
===[[SCOG v IBM]]===
SCOG accused IBM of contract and copyright violations, but tried to avoid a formal claim of copyright claims. IBM countersued, accusing SCOG of unfair competition via massive false public statements that IBM had violated SCOG's copyrights by IBM's Linux activities.

For details of the following outline, see the above link.
====SCOG's PR====
====SCOG's court claims====
====SCOG's compliance with court orders====
====Current status of the suit====
A hearing is scheduled for August 4. See the link in the following subsection.
[[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
=====[[SCOvIBM-PSJ]]=====
----
===Redhat v SCOG===
Accuses SCOG of unfair trade, and seeks a declaratory judgment. The case is currently stayed (but a motion for reconsideration is pending), waiting for the IBM case. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----
===[[SCOG v Novell]]===
SCOG claimed that Novell falsely and maliciously claimed that SCOG does not own the copyrights that SCOG has publicly proclaimed were violated by Linux. The suit was dismissed, but SCOG was allowed to re-file to claim special damages. Nothing has happened since the suit was refiled.

For details of the following outline, see the above link. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
====Memos and motions====
====Judge's hint that SCOG probably doesn't own the copyrights=====
----
===[[SCOG v Daimler-Chrysler]]===
SCOG accused DC, an automobile manufacturer, of failing to respond to an audit request. The judge issued a summary judgment on the merits of the case, ruling against all of SCOG's claims except the lateness issue, and leaving that to be decided later.

For details of the following outline, see the above link. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
====Memos and motions====
====Did SCOG have the right to audit?====
----
===SCOG v Autozone===
SCOG accused Autozone, an automobile parts company, of copyright violations by Autozone's Linux activities, after Autozone switched from [[SysV]] to Linux.
The case is currently stayed, waiting for the IBM and Novell cases. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----
===SCOG v others===
SCOG has waged a massive public campaign of [[FUD]].

They talked in 2003 about mountains evidence of infringement in Linux, enough to go to trial without discovery. After a year and two court order for them to detail their claims to copyrights in Linux, no specific details are public, and IBM claims that SCOG did not comply with either order.

SCOG claimed that the [[GPL]] is unconstitutional and that SCOG never intentionally released a product with its code licensed by the GPL. SCOG advertised ELF as supported by its GPL'd OpenLinux release, but now claims (without details) that ELF in Linux violates SCOG's copyrights.

SCOG nagged Linux distributors to indemnify their customers against IP lawsuits. Some have, and [[OSRM]] has offered lawsuit insurance. I have seen no offers from SCOG to indemnify its customers from IBM's patent and claims, which are pending in court.

I could go on, but I won't. If you want more, see [[Groklaw]], especially the Quote Data Base. [[User:TomFrayne|TomFrayne]] 15:05, Jul 23, 2004 (EDT)
----

User talk:TomFrayne

2004-07-02T23:35:11Z

TomFrayne: Responses to Crazyeddie

I'm a bit worried about all the work you're sinking into the Hierarchal TOC. Not that I can do much to stop you. But experience seems to show that hierarchialism in a wiki is a Bad Thing. The main reason is that it's too hard to maintain. The main page isn't so much a TOC as a good jumping off point to the more popular pages, which have links into the depths of the wiki. To put it another way, the natural topology of a wiki is a mesh, not a star.

I did something similar when I first joined this wiki with the HCL. I now regard the HCL as my worst mistake here, and I'm about ''this'' close to asking the sysops to remove the whole HCL.

If you think I'm wrong, continue by all means, but I think you'll have more fun and produce more if you get back to editing and adding to articles rather than futsing around with dreary organizational details. Even if you don't think you know much about linux, you do know something about some piece of it, and there is always cosmetic editing to do. [[User:Crazyeddie|Crazyeddie]] 18:52, Jul 1, 2004 (EDT)

:I'll consider your remarks, but I think I'll continue working on the TOC for a while longer. I have already run into some problems updating it, so I see what you mean. [[User:TomFrayne|TomFrayne]] 19:35, Jul 2, 2004 (EDT)
----

If this wiki gets MediaWiki 1.3, you can do what you're doing with categories. I don't know if there's a plan to move to 1.3, but you might want to hold out until we get categories here. [[User:Dysprosia|Dysprosia]] 01:31, Jul 2, 2004 (EDT)

:To add to that, I mentioned MediaWiki 1.3. and ''Categories'' to Jeremy a while back and we should be moving toward this in the near future -- [[User:Skyline|Skyline]] 14:12, Jul 2, 2004 (EDT)
::The categories part seems to be working out well so far, so I think I'll continue to do it manually rather than waiting for the MediaWiki update.

----
More bad news - I was looking over your contrib list, and noticed a "moved from Grokdoc". Last I checked, Grokdoc uses the non-commercial variant of Creative Commons, which isn't compatible with the share-alike variant that we use here. Unless you have permission from the actual copyright holder (whoever originally contributed it to Grokdoc), we're in copyright violation. The incompatibility works the other way too - LQwiki material can't be rereleased under noncommercial CC by anybody besides the orginal copyright holder. I feel your pain - I stumbled over the fact that Wikipedia's GFDL isn't compatible. Fortunately, it was caught before I put the material in an actual article. :-( [[User:Crazyeddie|Crazyeddie]] 05:28, Jul 2, 2004 (EDT)
:I should have noticed that, but didn't. If I can't get permission today, I'll remove it. [[User:TomFrayne|TomFrayne]] 19:35, Jul 2, 2004 (EDT)

Switching to Linux from Windows

2004-06-26T12:49:33Z

TomFrayne: Windows to Linux Migration

Parent: [[FAQ - operating systems]]
See also: [[FAQ - Linux kernel and desktop]], [[TOC - Common questions(FAQ)]]

This page discusses the questions: Which Windows users should switch to Linux? Why? When? How?

To summarize:
* Most should switch; exceptions: those not upgrading
* To avoid Microsoft, improve performance, stability, and security, to lower costs
* Start now, but don't hurry to finish
* Switch gradually; minimize programming changes after the switch; plan to use Windows emulators for applications with no Linux equivalent.

==Switching to Linux from Windows==
===Who? Why? When? How?===

====Who is doing it - IBM, Novell, etc.====

====Why switch====

====Who should wait; who should switch now====

====Switching gradually - multi-platform [[FOSS]] programs====
Often, the hardest part of switching to Linux is leaving behind Microsoft applications and other applications that run only on Windows. This roadblock can often be bypassed by starting to use [[Multi-platform]] applications that run on both Windows and Linux while still running on Windows. The advantages over a direct switch to Linux are:
* You can still run the Windows applications
* You can get used to differences in the user interfaces gradually as you have time instead of in the middle of an important project
* You can convert important data to the FOSS formats while the Windows applications are there to help, and archive less important data for conversion as needed

The most important mult-platform applications are replacements for basic Windows applications that you use:
* Web Browser - use [[Mozilla]] instead of [[Internet Explorer]]
* Office - use [[OpenOffice]] instead of [[Microsoft Office]]

See [[Linux software equivalent to Windows software]] for more examples, but, while you are running on Windows, limit yourself to the multi-platform or [[Cross-platform]] applications.

See [http://www.desktoplinux.com/articles/AT7010636622.html Switching to Linux gradually] for a more detailed discussion.

====The Linux distribution for you====

====Windows emulators in Linux - Wine, Win4Lin====

====Linux replacements for Windows applications====

====Linux usability vs Windows usability====

====Other factors in deciding to switch====

===Trying Linux for the first time===
====Running Linux from a CD====
=====Choices of distributions that run from a CD=====
* [[Knoppix]]
* [[Suse]] 9.1 evaluation CD
=====Steps to get started with your choice=====
* [[Download]] an [[ISO]] file for a bootable CD
* [[CD/DVD Burning|Burn]] the bootable CD
* Read getting started information on the CD - often a README file
* Boot the CD
* Try basic tasks such as internet access, email, writing and printing a letter
====Picking a Linux distribution====
====Buying a machine with Linux pre-installed====
When I wanted a laptop with Linux pre-installed and configured, I found that the major vendors like Dell and IBM offered them in quantity to corporations, but did not offer them to consumers. I bought from [[Los Alamos Computers]], which also offers pre-configured desktop machines, and have been very satisfied.

Now a Google search for buy "linux laptop" produces 30,500 hits, including
[http://tuxmobil.org/reseller.html Linux laptop vendor list]. Further, Redhat, IBM, and Novell all seem to be pushing Linux for desktop use, so the number of choices for vendors should increase rapidly.

Note: If you buy a machine with Windows pre-installed and don't accept the license by clicking the Accept button, you can get a refund from Microsoft. However, when you can buy a cheaper equivalent machine with Linux pre-installed, why bother?

====Installing a distribution====

====Task-oriented tips for [[Windows]] power users====
Windows power users will want to know how to do tasks in Linux that they were used to doing in Windows. See [[Windows to Linux Migration]].

----

==Compatibility with Windows==
* [[Wine]]
* [[Win4Lin]]
* [[OpenOffice]] and [[AbiWord]]/[[Gnumeric]]
* [[OpenOffice]], [[Mozilla]], [[Apache]] - reverse compatibility
===Windows applications -> Linux applications===
* [[Application Crossover Chart]] - Mapping from Windows to Linux

Switching to Linux from Windows

2004-06-26T12:34:50Z

TomFrayne: Moved from FAQ - operating systems

Parent: [[FAQ - operating systems]]
See also: [[FAQ - Linux kernel and desktop]], [[TOC - Common questions(FAQ)]]

This page discusses the questions: Which Windows users should switch to Linux? Why? When? How?

To summarize:
* Most should switch; exceptions: those not upgrading
* To avoid Microsoft, improve performance, stability, and security, to lower costs
* Start now, but don't hurry to finish
* Switch gradually; minimize programming changes after the switch; plan to use Windows emulators for applications with no Linux equivalent.

==Switching to Linux from Windows==
===Who? Why? When? How?===

====Who is doing it - IBM, Novell, etc.====

====Why switch====

====Who should wait; who should switch now====

====Switching gradually - multi-platform [[FOSS]] programs====
Often, the hardest part of switching to Linux is leaving behind Microsoft applications and other applications that run only on Windows. This roadblock can often be bypassed by starting to use [[Multi-platform]] applications that run on both Windows and Linux while still running on Windows. The advantages over a direct switch to Linux are:
* You can still run the Windows applications
* You can get used to differences in the user interfaces gradually as you have time instead of in the middle of an important project
* You can convert important data to the FOSS formats while the Windows applications are there to help, and archive less important data for conversion as needed

The most important mult-platform applications are replacements for basic Windows applications that you use:
* Web Browser - use [[Mozilla]] instead of [[Internet Explorer]]
* Office - use [[OpenOffice]] instead of [[Microsoft Office]]

See [[Linux software equivalent to Windows software]] for more examples, but, while you are running on Windows, limit yourself to the multi-platform or [[Cross-platform]] applications.

See [http://www.desktoplinux.com/articles/AT7010636622.html Switching to Linux gradually] for a more detailed discussion.

====The Linux distribution for you====

====Windows emulators in Linux - Wine, Win4Lin====

====Linux replacements for Windows applications====

====Linux usability vs Windows usability====

====Other factors in deciding to switch====

===Trying Linux for the first time===
====Running Linux from a CD====
=====Choices of distributions that run from a CD=====
* [[Knoppix]]
* [[Suse]] 9.1 evaluation CD
=====Steps to get started with your choice=====
* [[Download]] an [[ISO]] file for a bootable CD
* [[CD/DVD Burning|Burn]] the bootable CD
* Read getting started information on the CD - often a README file
* Boot the CD
* Try basic tasks such as internet access, email, writing and printing a letter
====Picking a Linux distribution====
====Buying a machine with Linux pre-installed====
When I wanted a laptop with Linux pre-installed and configured, I found that the major vendors like Dell and IBM offered them in quantity to corporations, but did not offer them to consumers. I bought from [[Los Alamos Computers]], which also offers pre-configured desktop machines, and have been very satisfied.

Now a Google search for buy "linux laptop" produces 30,500 hits, including
[http://tuxmobil.org/reseller.html Linux laptop vendor list]. Further, Redhat, IBM, and Novell all seem to be pushing Linux for desktop use, so the number of choices for vendors should increase rapidly.

Note: If you buy a machine with Windows pre-installed and don't accept the license by clicking the Accept button, you can get a refund from Microsoft. However, when you can buy a cheaper equivalent machine with Linux pre-installed, why bother?

====Installing a distribution====

----

==Compatibility with Windows==
* [[Wine]]
* [[Win4Lin]]
* [[OpenOffice]] and [[AbiWord]]/[[Gnumeric]]
* [[OpenOffice]], [[Mozilla]], [[Apache]] - reverse compatibility
===Windows applications -> Linux applications===
* [[Application Crossover Chart]] - Mapping from Windows to Linux

Security

2004-06-22T06:34:09Z

TomFrayne: Link to Parent. Move Firewall links

Parent: [[Hierarchical TOC]]
==Security==

Most [[Configuration]] tasks have security implications. At the current state of the art, it is probably too difficult for most of us to maintain a completely secure system, so the goal has to be to make the cost to a malicious hacker of penetrating our systems more than the penetration would be worth to him or her.

The following outline focuses on what has to be done and what tools are available rather than why and how to do security configuration, except for the first item, which is meant to focus on getting the user started with security configuration. It is currently only a stub.

* [[Security configuration - start here]]

* [[Linux Security Basics]]
** [[Permissions|Basic Linux file system attributes]]
** [[User]]s and [[group]]s
** [[Linux security terms and definitions|Security terms and definitions]]
** [[Linux security vulnerabilities]]
** [[Obtaining security updates]]
** [[Community security resources]]

* Base System Security
** Configuring and using [[su]] and [[sudo]]
** [[Identifying and disabling extraneous services]]
** [[chroot]]ing common services and commands
** [[Basic system logging]]

* Network [[Services]]
** [[Telnet and SSH]] - Why ''not'' to use Telnet
** [[SSH]]
*** [[Using SSH]]
*** [[Configuring the OpenSSH SSH daemon]]
*** [[Using SCP and SFTP to transfer files]]
*** [[OpenSSH chrooting|Creating chroot environments with OpenSSH]]
*** [[X11 forwarding with OpenSSH]]
*** [[Tunneling with OpenSSH]]
** [[rsyncBackups|Secure backups with rsync]]

* [[Firewall]] - Iptables, configuration, firewall software

* [[Securing email]]
** [[Sender Verification]]
** [[Spam Filtering]]
** [[Spam Filtering on the desktop]]
** [[Virus/worm Filtering]]
** [[Using GPG to cryptographically sign email]]
** [[Using MailScanner/Postfix/SpamAssassin/ClamAV in Gentoo Linux]]

* [[Securing servers and services]]
** [[Securing Apache]]
** [[Securing SAMBA]]
** [[Securing Sendmail]]
** [[Securing ssh]]

* [[Hardening against users with physical access]]
** [[Physical security]]
** [[Securing the BIOS]]
** [[Securing LILO]]
** [[Securing GRUB]]
** [[Configuring a basic kiosk mode]]

* [[System monitoring]]
** [[Detecting portscans]]

* [[Security auditing]]
** [[Security auditing tools]]

* [[Wireless network security]]
** [[WEP]]
** [[Shortcomings of WEP]]
** [[Secure alternatives to WEP]]
*** [[Using and configuring OpenVPN]]

* [[Local Policies]] - Legal Stuff
** [[TOS]] and [[AUP]]
** [[MOTD]]

Firewall

2004-06-22T06:13:37Z

TomFrayne: Parent: Security. Moved links from Security

Parent: [[Security]]

A '''firewall''' is a piece of [[hardware]] or [[software]] put on the network to prevent some communications forbidden by the [[network policy]].

** [[Graphical and interactive firewall configuration]]
*** [[fwbuilder]] - GUI for configuring firewalls
*** [[Using GNOME lokkit for firewall configuration]]

==Linux firewall software==
A lot of different firewall software is available for Linux, ranging from easy [[GUI]] apps for desktop PCs to dedicated [[firewall distributions]]. They all use the packet filtering method provided by the Linux [[kernel]]. Since Linux kernel 2.4 Linux this is called [[netfilter]]. The [[iptables]] command is used to configure it. [[ipchains]] is the 'old' configuration command for kernels 2.2 and older (but still supported in recent kernels through an emulation layer).
Linux firewall software is usually a front-end for iptables/ipchains, they allow some more userfriendly method (GUI, easier text based config file, etc.) to create firewall rules and use some script that runs at boot time (or whenever the rules are changed) to set the rules.

===Firewall scripts/console apps===
*[[Iptables|iptables/netfilter]]
** [[Manual configuration of an iptables firewall]]
*** [[A basic firewall configuration suitable for a workstation]]
*** [[A basic firewall configuration suitable for a gateway/nat]]
** [[Scripted firewall configuration]]
*** [[Shorewall]] configuration tool for netfilter
*[[BullDog]]
*[[ferm]]
*[[fireHOL]]
*[[gShield]]
*[[IPmenu]]
*[[Shorewall]]
*[[Turtle Firewall]]
*[[TuxFrw]]
*[[yaft]]

===GUI/X firewall applications===
*[[Graphical and interactive firewall configuration]]
** [[fwbuilder]] - GUI for configuring firewalls
** [[Using GNOME lokkit for firewall configuration]]
** [[fireflier]]
** [[firestarter]]
** [[Guarddog]]
** [[gShieldConf]]
** [[Knetfilter]]

===Web interface firewall applications===
*[[easyfwgen]]
*[[webmin]]

==See also==
*[[A basic firewall configuration suitable for a workstation]]
*[[A basic firewall configuration suitable for a gateway/nat]]
*[[packet filtering]]
*[[IP routing]]
*[[routing]]
*[[proxy]]
*[[security]]

{{msg:stub}}

LQWiki:Searching

2004-06-22T01:55:34Z

TomFrayne: Add Hierarchical TOC, Parent

Parent: [[Common Questions and Misconceptions]]

To '''search''' for information at the LinuxQuestions.org Wiki, you can:

* Use the "Go or Find" box, to the right of your screen. ''Go'' attempts to find a single page with a name matching the [[keyword]]s you typed. ''Search'' attempts to find all pages containing the keywords you typed.

* Use [http://www.google.com/linux?num=100 Google]. Note that Google searches can be restricted to a particular domain by using the "site" keyword. For example, if I want to find pages mentioning <code>xterm</code> on the LinuxQuestions.org wiki, I might use the query:
<pre>
xterm site:wiki.linuxquestions.org
</pre>

* Use [[Hierarchical TOC]] to browse LQWiki from very general topics to particular topics. You can start with a vague idea, and quickly zero in on the detailed information you need.

*You can also [[Special:Allpages|browse articles by name]].

LQWiki:Requests for improvement

2004-06-21T20:17:37Z

TomFrayne: Parent: Editable LQ Central#Contribute

Parent: [[Editable LQ Central#Contribute]]
Please list files that you '''request be improved''' here.

== Current requests ==
* [[Functionality]]
* [[Shadow file]]
----
* [[Main Page]] not changed since May 4. Needs refresh from [[Editable Main Page]]. We especially need links to [[Editable Main Page]], [[Hierarchical TOC]]

* [[Editable Main Page]] Needs more top level topics, including this topic
:** Major reorganization done. Still needs review and integration with [[Main Page]]. [[User:TomFrayne|TomFrayne]] 16:11, Jun 21, 2004 (EDT)

* [[Hierarchical TOC]] It should be possible to quickly browse to any topic on the Wiki from here. A lot more work is needed to accomplish this.
:** The top levels need review. More work needs to be done on the subTOCs. [[User:TomFrayne|TomFrayne]] 16:11, Jun 21, 2004 (EDT)

[[User:TomFrayne|TomFrayne]] 11:48, Jun 20, 2004 (EDT)
----

Also see [[Special:Whatlinkshere/LinuxQuestions.org Wiki:Requests for improvement|pages that link here]]. You can create an invisible link to here by using <nowiki>[[page name| ]]</nowiki> (note the space).

LQWiki:Requests for improvement

2004-06-21T20:11:10Z

TomFrayne: Updated requests for Editable Main Page, Hierarchical TOC

Please list files that you '''request be improved''' here.

== Current requests ==
* [[Functionality]]
* [[Shadow file]]
----
* [[Main Page]] not changed since May 4. Needs refresh from [[Editable Main Page]]. We especially need links to [[Editable Main Page]], [[Hierarchical TOC]]

* [[Editable Main Page]] Needs more top level topics, including this topic
:** Major reorganization done. Still needs review and integration with [[Main Page]]. [[User:TomFrayne|TomFrayne]] 16:11, Jun 21, 2004 (EDT)

* [[Hierarchical TOC]] It should be possible to quickly browse to any topic on the Wiki from here. A lot more work is needed to accomplish this.
:** The top levels need review. More work needs to be done on the subTOCs. [[User:TomFrayne|TomFrayne]] 16:11, Jun 21, 2004 (EDT)

[[User:TomFrayne|TomFrayne]] 11:48, Jun 20, 2004 (EDT)
----

Also see [[Special:Whatlinkshere/LinuxQuestions.org Wiki:Requests for improvement|pages that link here]]. You can create an invisible link to here by using <nowiki>[[page name| ]]</nowiki> (note the space).

Hardware

2004-06-21T19:29:00Z

TomFrayne: Reorganize, integrate with Hardware TOC

Parent: [[Hardware TOC]]
==Hardware General==
===Hardware Compatibility List (HCL)===
*[[Hardware Compatibility List]]
*[http://www.linuxquestions.org/hcl/index.php LinuxQuestions.org HCL : Product Reviews].
===Hardware Recommendations===
*[[Hardware_Recommendations]]
===Hardware configuration===
*[[Hardware configuration
===New Hardware===
*[[New Hardware]]
===Linux Laptops===
*[http://www.linuxlaptops.org Linux Laptops]
===Linux On Laptops, Notebooks, PDAs and Mobile Phones===
*TuxMobil: [http://tuxmobil.org/ Linux On Laptops, Notebooks, PDAs and Mobile Phones]
===Ports of Linux===
*[http://perso.wanadoo.es/xose/linux/linux_ports.html Ports of Linux]

==Hardware devices==
===Input devices===
* [[Configuring mice (Serial, PS/2, USB)]]
* [[Configuring keyboards]]

===Graphics cards===
* [[3D graphics acceleration]]
* [[framebuffer]] device
* [[Configuring TV out]]
* [[Using multiple monitors with XFree86]]
* [[Video For Linux]]

===Sound===
* [[OSS]]
* [[ALSA]]

===Printers===
* [[Adding local printers]]
* [[Adding network printers]]

===Disks/Volumes===
* [[IDE]] vs [[SCSI]] vs [[SATA]]
* [[IDE Tree Mapping]]
* [[IDE CD Writer]] (ATAPI)
* [[LVM]]
* [[RAID]]
* [[File Systems]]
* [[USB Flash drive]]

===Busses===
* [[PCI]]
* [[PCMCIA]] (laptops addon cards)
* [[MCA]] (Micro Channel Architecture, old IBM PS2s)
* [[Firewire]] (400 and 800)
* [[ADB]] (old macintosh)
* [[Sun Peripherals]] type 3 type 4 type 5
* [[USB]] Universal Serial Bus
* [[AGP]] Accelerated Graphics Port
* [[IDE bus]] / [[ATA]] and [[ATAPI]].

===[[Power Management]]===
* [[ACPI]]
* [[APM]]

===Scanners===
* [[Scanners]]

== Tools/Tips ==
*[[lspci]]
*[[scanpci]]
*[[Hotplug|Hotplugging]] hardware
*[[Automatic Hardware Configuration]] tools.
*[[Quieting linux]]

Copyleft

2004-06-21T17:04:41Z

TomFrayne: Added explanation

A term coined by [[RMS]] describing a type of software licence such as the [[GNU]] [[GPL]]. A play on words, of course, referring to copyright.

If you make a change to a piece of some copylefted software's [[source code]], and then distribute that software, you must also distribute your modified source code.

If the license you have is the GPL, you must license your modifications as well as the original program under the GPL. The same applies if your distribution contains GPL'd programs and you ship your independently developed program in the distribution, unless the distribution qualifies as a [[Mere aggregation]].

LQWiki:Protected page guidelines

2004-06-21T13:39:41Z

TomFrayne: Initial version. Editable mirrors.

==LQWiki:Protected page guidelines==

[[Main Page]] and [[LQWiki:LQ Central]] are protected pages, and are not editable, except by Wiki administrators. This is to protect the overall structure of LQWiki from careless or malicious editing.

Since users may have good ideas for improving protected pages, each protected page has an editable mirror, e.g, [[Editable Main Page]], [[Editable LQ Central]]. The editable versions of protected pages will be periodically synchronized with the protected versions, after backing up the protected versions.

LQWiki:Requests for improvement

2004-06-20T15:48:44Z

TomFrayne: Main Page, Hierarchical TOC, Editable Main Page requests

Please list files that you '''request be improved''' here.

== Current requests ==
* [[Functionality]]
* [[Shadow file]]
----
* [[Main Page]] not changed since May 4. Needs refresh from [[Editable Main Page]]. We especially need links to [[Editable Main Page]], [[Hierarchical TOC]]

* [[Editable Main Page]] Needs more top level topics, including this topic

* [[Hierarchical TOC]] It should be possible to quickly browse to any topic on the Wiki from here. A lot more work is needed to accomplish this.

[[User:TomFrayne|TomFrayne]] 11:48, Jun 20, 2004 (EDT)
----

Also see [[Special:Whatlinkshere/LinuxQuestions.org Wiki:Requests for improvement|pages that link here]]. You can create an invisible link to here by using <nowiki>[[page name| ]]</nowiki> (note the space).

Common Tasks

2004-06-19T17:53:29Z

TomFrayne: ==LQWiki user's taska==. Outline.

Desktop Linux is still under heavy development. While we all wish Linux was so intuitive nobody needed instructions, currently that isn't always the case. This section is meant for '''notes and quick guides''' on how to perform common tasks on Linux.

If a section isn't yet written and you are able to write it, please do so!

== General user tasks ==

===Productivity===
====Browsing, Burning, Emailing, Office, Scanning, Viewing====
* [[Browsing tasks]] - browsing the WWW and downloading safely
* [[Burning a CDROM]] - some pointers on how to write CDs.
* [[Emailing tasks]] - sending and receiving emails, setting up different mail applications
* [[Office tasks]] - word processing, spreadsheet, presentation, image manipulation and other
* [[Scanning]] - use a [[Scanner]] to convert you paper documents or images to an electronic format
* [[Viewing files]] - various ways to view the contents of files

===Fun===
====Gaming, Multimedia, Talking====
* [[Gaming]] - pass some time ''not'' working
* [[Multimedia tasks]] - listen to music, extract CDs, watch videos and DVDs
* [[Talking to friends online]] - how to access common instant messaging
networks, see also [[IM]].

===Technical===
====Commands, Connecting, GRUB====
* [[Command Line User Interface]] - Techniques for better experience
* [[Connecting to the net]] - using your modem/network connection to get online
* [[GRUB Menu]] - Single Task - Removing old kernel entries from your GRUB Menu boot up selections.
* [http://home.gagme.com/greg/linux/usbcamera.php How to Connect a Digital Camera to Linux (outside link)] - an excellent how-to on connecting digital cameras to Linux.
* [[Installing Software]] - how to find and manage additional software on a running Linux system
* [[Installing Windows fonts]] - installing your Windows fonts so they work with your Linux install.
* [[screenshots|Taking screenshots]] - You want to show somebody your desktop? There are tools that will help you make a [[screenshots | screenshot]] and [[record your desktop]] so that you can send movie-files of how nice your desktop looks.

== Power user tasks ==
=== Compiling kernel, Configure, IRC help, GRUB, Drivers, Recover, Remote connection ===

* [[Compiling a Kernel]] - here is a guide for compiling a kernel
* [[Configure Storage Devices]] - how to partition a hard drive, add a new hard drive, use software RAID, or use LVM (logical volume management).
* [[Getting help from IRC]] - LinuxQuestions is a great forum, but it isn't the only one. If you know how, the IRC chat networks can also be a useful resource.
* [[GRUB boot menu]] - Configuration Guide.
* [[Installing NVIDIA drivers]] - Information on installing the newer (but closed-source) drivers released by NVIDIA. These drivers are sometimes required to run some games, like Unreal or Quake.
* [[Recover a Terminal Session]] - What to do if your screen's garbaged.
* [[Remote_Desktop_Connection|Access your System Remotely]] - Access your Linux system from another computer (running Linux, or some other OS) or use your Linux box to access another computer (running Linux, or some other OS).

==LQWiki user's tasks==
===Finding information in the Wiki - Search, Hierarchical TOC, If not found===
====Search====
=====If not found=====
====Hierarchical TOC====
=====If not found=====
====If not found====
===Editing the Wiki - New page, Existing Page===
====New page====
=====Insert a link=====
====Existing page====
=====Editable=====
=====Non-editable=====
== See Also ==
=== Distro specific ===
* [[Distro specific tips & tricks]]

User talk:Shevegen

2004-06-19T17:08:08Z

TomFrayne: Feel free to edit

I dislike editing other user's userpages, but I felt the urge here. Could you wikify the distros please? (I think my wiki addiction is getting to me.) ;-) [[User:Crazyeddie|Crazyeddie]] 12:06, Jun 19, 2004 (EDT)

==Feel free to edit==
Whenever you can add something useful to someone else's page and the page header contains no prohibition, do it. For example, I inserted [[PHP]] into [[LinuxQuestions.org Wiki:Forums#First Post: Do we want a real forum instead of a thread-mode wiki?]]. [[User:TomFrayne|TomFrayne]] 13:08, Jun 19, 2004 (EDT)

LQWiki:Forums

2004-06-19T16:56:54Z

TomFrayne: Mailing lists are bad, PHP

''This is a prototype of a thread-mode wiki 'Forum', similar to the Village Pump at the Wikipedia. In theory, this page will eventually be locked down a bit, but given the nature of thread-mode wiki, this Forum is usable now.''

==Welcome to the LinuxQuestions.org Wiki Forum==
''This section would be locked down.''

'''The purpose of this forum is to discuss LQWiki related topics (as well as to discuss OT topics with fellow LQWikiers.) For Linux questions, please go to our parent site, http://linuxquestions.org .'''

To post a new topic, click the "Edit this page" link, scroll to the bottom, and type in: <nowiki>==<Insert Topic Name Here>==</nowiki>. You can then write your post underneath.

To reply to a post, the convention is to leave a line between the posts and ident your post with a ":".

Don't forget to sign your post with four tildes (~).

==''Actual Forum''==

===First Post: Do we want a real forum instead of a thread-mode wiki?===
Please note that in actual operation, new topics would use two equal signs instead of three.

Thread-mode wikis have several strikes against them. Basically, they remain forum-like only so long as the posters stick by the conventions. As soon as a noob or a griefer hits the stage, things get hairy unless they are watched like a hawk by mods. There is a lot of confusion about how to start a new thread, how to reply to a post. People forget to sign, signatures can be forged trivially (although they can be checked by looking at the changelog- but who has time for that?) Posts can be edited by third parties. Somebody could post in the middle of someone else's post. Thread-mode wikis are good enough for a commentary on a article - for the most part. But for something as heavily used as this forum is liable to be, we would probably be better off with an actual forum.

The main argument against having an actual forum is if they would have too much of a drain on system resources - including the admins' time. Not being a webmin myself, I'm not qualified to answer that question.

Let me know what you think. [[User:Crazyeddie|Crazyeddie]] 01:21, Jun 19, 2004 (EDT)

Yes, for sure - i love forums. Dont get me wrong, i LOVE wiki's BUT i am also an avid forum user. I think the best wiki would be a wiki+Forum in a [[PHP]] manner. A wiki rules for FAQs and other things like knowledgebase BUT a forum is the best way to solve your problems. (this linux wiki is my favorite linux wiki btw, coming 2nd is a german wiki )
We could have a forum, and then we can additionally extract helpful info from the forum into the wiki.
A forum is also nice - btw :) - to get in contact with other people, about their experience etc. (I am _just_ referring to the topic of LINUX, not about political things etc. In a Linux Forum i am mostly interested in chatting about Linux, and secondarily about other Linux users like crazy eddie and their experiences :)
feel free to delete my post if there is a forum! i know its a bit messy
one last note, i dont think its necessary to invest much of your time into MODERATING a forum... let it flow, it will work (at least it worked for me and my friends, we can even edit and delete each other's post, but somehow we dont, rarely if there are some annoying errors hehe... but then we even use word censors to include our own typos .. much easier ... PHP Forum of course btw :)
- shevegen

==Using the Wiki as a forum==
===Pre-emptive argument===
:Pre-emptive argument: Keep in mind that the LinuxQuestions.org forums are available for Linux questions. I've been trying to extract information from those forums into the wiki, but I've been pressed for time lately. This forum would be for the Wiki community. While hopefully there is a lot of overlap between the LinuxQuestions.org and the LQWiki communities, I think they are two separate communities, and the LQWiki deserves its own "watering hole".

:To answer the other objection to these forums that I see coming down the way: Yes, I know there's the mailing list. There's a lot of arguments on the topic of forums vs. mailing lists, but I'll make just one for now: When's the last time anybody besides me, Aaron Peterson, and the mods have posted to the mailing list?

:Anyway, these forums would be a place to discuss LQWiki related topics (as well as OT conversations with fellow LQWikiers). For linux questions, please go to linuxquestions.org, our parent site.[[User:Crazyeddie|Crazyeddie]] 12:03, Jun 19, 2004 (EDT)

----
===Mailing lists are bad===
::Mailing lists are a poor substitute for forums and wikis. I have never looked at or posted to the Wiki mailing list. There are better ways to ask questions, look for answers, or post answers within the Wiki, which is naturally organized, has a Search facility, and has instant communication, including a central place to look for recent posts.

::For example, I didn't know what PHP meant, so I inserted a link to it, previewed, and went to the linked page to find out. Now anyone with the same problem can solve it with one click. [[User:TomFrayne|TomFrayne]] 12:56, Jun 19, 2004 (EDT)

Common Tasks

2004-06-19T15:46:23Z

TomFrayne: Improved TOC

Desktop Linux is still under heavy development. While we all wish Linux was so intuitive nobody needed instructions, currently that isn't always the case. This section is meant for '''notes and quick guides''' on how to perform common tasks on Linux.

If a section isn't yet written and you are able to write it, please do so!

== General user tasks ==

===Productivity===
====Browsing, Burning, Emailing, Office, Scanning, Viewing====
* [[Browsing tasks]] - browsing the WWW and downloading safely
* [[Burning a CDROM]] - some pointers on how to write CDs.
* [[Emailing tasks]] - sending and receiving emails, setting up different mail applications
* [[Office tasks]] - word processing, spreadsheet, presentation, image manipulation and other
* [[Scanning]] - use a [[Scanner]] to convert you paper documents or images to an electronic format
* [[Viewing files]] - various ways to view the contents of files

===Fun===
====Gaming, Multimedia, Talking====
* [[Gaming]] - pass some time ''not'' working
* [[Multimedia tasks]] - listen to music, extract CDs, watch videos and DVDs
* [[Talking to friends online]] - how to access common instant messaging
networks, see also [[IM]].

===Technical===
====Commands, Connecting, GRUB====
* [[Command Line User Interface]] - Techniques for better experience
* [[Connecting to the net]] - using your modem/network connection to get online
* [[GRUB Menu]] - Single Task - Removing old kernel entries from your GRUB Menu boot up selections.
* [http://home.gagme.com/greg/linux/usbcamera.php How to Connect a Digital Camera to Linux (outside link)] - an excellent how-to on connecting digital cameras to Linux.
* [[Installing Software]] - how to find and manage additional software on a running Linux system
* [[Installing Windows fonts]] - installing your Windows fonts so they work with your Linux install.
* [[screenshots|Taking screenshots]] - You want to show somebody your desktop? There are tools that will help you make a [[screenshots | screenshot]] and [[record your desktop]] so that you can send movie-files of how nice your desktop looks.

== Power user tasks ==
=== Compiling kernel, Configure, IRC help, GRUB, Drivers, Recover, Remote connection ===

* [[Compiling a Kernel]] - here is a guide for compiling a kernel
* [[Configure Storage Devices]] - how to partition a hard drive, add a new hard drive, use software RAID, or use LVM (logical volume management).
* [[Getting help from IRC]] - LinuxQuestions is a great forum, but it isn't the only one. If you know how, the IRC chat networks can also be a useful resource.
* [[GRUB boot menu]] - Configuration Guide.
* [[Installing NVIDIA drivers]] - Information on installing the newer (but closed-source) drivers released by NVIDIA. These drivers are sometimes required to run some games, like Unreal or Quake.
* [[Recover a Terminal Session]] - What to do if your screen's garbaged.
* [[Remote_Desktop_Connection|Access your System Remotely]] - Access your Linux system from another computer (running Linux, or some other OS) or use your Linux box to access another computer (running Linux, or some other OS).

== See Also ==
=== Distro specific ===
* [[Distro specific tips & tricks]]

GPL

2004-06-19T03:28:29Z

TomFrayne: Improved description of GPL. Link to Mere aggregation

==GPL==

The GNU '''GPL''', or ''General Public License'', is a [[software]] license designed to enforce the rights of the software user, rather than furthering the rights of the software distributor at the end-user's expense. It is the standard license of the [[FSF]]'s [[GNU]] project, and much of the important software in a [[Linux]] system is licensed using the GPL.

In addition to the usual rights to run and archive the program, the recipient of a GPL'd program has permission to copy, to modify, and to distribute the program, provided that he or she abides by the terms of the GPL. If the program is only used in-house, there are no other conditions for this permission.

Whereas many software licenses place restrictions on the end-user's use of the software, the GPL places restrictions on the distributor's rights. GPL-licensed software must be available in [[source code]] form to anyone it is distributed to, and the software must be licensed under the GPL whenever it is distributed, whether the original GPL'd program is modified or not. If a collection containing GPL'd programs is distributed, the collection as a whole must be licensed under the GPL, unless it is a [[Mere aggregation]]. Because these provisions fly in the face of traditional copyright considerations, this legal arrangement is sometimes referred to as [[copyleft]].

The GPL does not try to restrict the author's licensing of code that is not based on GPL'd code. For example, if the author's code is not a derivative of GPL'd code, and is distributed by itself, then the author can use a proprietary license, and need not make the source code available. However, if the same code is distributed in a collection and, in that collection, is based on GPL'd code, then the collection and the author's code must both be GPL'd, and the source for the author's code must be available.

==LGPL==
A related license called the [[LGPL]] ("Lesser GPL") also exists. It allows a proprietary program to be linked with the LGPL'd program.

==See also==
*[[free]]
*[[open source]]
*[[FOSS]]

==External links==
* [http://www.gnu.org/copyleft/gpl.html Text of the GNU GPL]

Pan

2004-06-18T18:14:52Z

TomFrayne: Description and links

==Pan==

Pan is a [[News]] reader that provides facilities to access [[Newsgroup]]s.

See [http://pan.rebelbase.com Pan home].

News

2004-06-18T18:09:38Z

TomFrayne: Examples of News readers

==News==

In addition to general online news that can be browsed or [[Search]]ed using [[Google]] News, the internet supports [[Newsgroup]]s that be accessed at a News server using [[Google]] Groups or a News reader.

==News server==
An internet [[Server]] that supports [[News]] groups by storing and retrieving messages [[Post]]ed by users.

==News reader==
An application that provides facilities to access [[News]] group messages. Typical facilities are:
* [[Subscribe]] - Set up for easy download and archive of messages to your machine.
* Download the latest messages sent to a newsgroup
* [[Post]] - send a message creating a new [[Thread]] in a discussion
* [[Reply]] - respond to a message

===Examples of News readers===
* [[Mozilla]]
* [[Pan]]

Newsgroup

2004-06-18T18:01:34Z

TomFrayne: Definition and links

==Newsgroup==

From [http://www.webopedia.com/TERM/N/newsgroup.html Webopedia]: A newsgroup (also called a forum), is an on-line discussion group. On the Internet, there are literally thousands of newsgroups covering every conceivable interest. To view and post messages to a newsgroup, you need a [[News]] reader, a program that runs on your computer and connects you to a [[News]] server on the Internet.

[[Google Groups]] provides an indexed [[Search]] facility that can find messages posted to many news servers, and allows the user to [[Post]] messages to join the discussion. The disadvantage is that Google Groups is always several hours out of date, so it is better to use a [[News]] reader for newsgroups where you are actively posting and reading messages.

==See also==
* [[Mailing list]] - a discussion based on [[Email]]
* [[IRC]] - Interactive Chat sessions
* [[Wiki]] - User editable web pages

News

2004-06-18T17:59:54Z

TomFrayne: Description and links

==News==

In addition to general online news that can be browsed or [[Search]]ed using [[Google]] News, the internet supports [[Newsgroup]]s that be accessed at a News server using [[Google]] Groups or a News reader.

==News server==
An internet [[Server]] that supports [[Newsgroup]]s by storing and retrieving messages [[Post]]ed by users.

==News reader==
An application that provides facilities to access [[Newsgroup]] messages. Typical facilities are:
* [[Subscribe]] - Set up for easy download and archive of messages to your machine.
* Download the latest messages sent to a newsgroup
* [[Post]] - send a message creating a new [[Thread]] in a discussion
* [[Reply]] - respond to a message

Mozilla

2004-06-18T16:54:38Z

TomFrayne: Link to Newsgroup

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

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

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

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

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

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

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

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

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

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

==Tips==

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

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

*Sun Java - you most probably want Java2 Standard Edition [http://java.sun.com/j2se/]

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

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

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

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

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

'''Single user:'''

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

'''Multi user:'''

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

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

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

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

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

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

CD/DVD Burning

2004-06-18T09:19:36Z

TomFrayne: Windows/Mac applications for making bootable CDs

==CD/DVD Burning==

'''CD burning''' in Linux used to be difficult but like so much else, has become much easier lately. If you are using the latest versions of the [[GNOME]] desktop environment, such as those provided with [[Fedora]], you can perform CD burning by first placing a blank disk in the drive. Wait a few seconds and a file manager window should appear. Now drag the files and directories you want into it, and then hit burn.

You can burn ISO CD images by right-clicking on the image file and choosing "Write to CD".

==Windows/Mac applications==
A user that wants to try Linux for the first time may need to download an [[ISO]] file for a single-CD [[Distribution]] such as [[Knoppix]] and burn the ISO file to CDR or CDRW media using a utility on his or her current system. Note that you have to use the function that burns an existing ISO file to CD, NOT the function that creates a temporary ISO file out of one or more files and burns the temporary file to CD. Applications that can do this include:

* [http://www.bay-wolf.com/burnimage.htm Nero] - How to do it with Nero
* [http://www.snapfiles.com/freeware/gmm/fwcdburn.html Freeware utilities] - Pick one that supports burning ISO images to CDR or CDRW.

==GUI applications==
*[[K3b]] - probably the most user-friendly CD/DVD burning application for the Linux desktop.
*[[XCDRoast]]
*[[gcombust]]
*[[Arson]]
*[[Eroaster]]

==Command line applications==
*[[cdrecord]]
*[[cdrdao]]
*[[mkisofs]]
*[[growisofs]]

==Hints and Tips==
* Setting up your [[IDE CD Writer]]
* [[Burning a CDROM from an ISO file]] from the command line
* [[Burning a CDROM from a bin/cue file]] from the command line

==See also==
*[[DVD]]

==External links==
*[http://www.troubleshooters.com/linux/coasterless.htm Coasterless CD Burning] guide

{{msg:stub}}

FOSS

2004-06-16T18:09:51Z

TomFrayne: Definition and links

==FOSS==

FOSS stands for Free and Open Source Software. This term is used for software that satisfies either the definition in [[Free]] or the definition in [[Open Source]], when there is no need to make a distinction.

For practical purposes, FOSS is usually the appropriate term. The distinction only needs to be made when discussing long-term legal, moral, or ethical consequences of the positions of [[FSF]] and [[Open Source]] Initiative.

Free

2004-06-16T18:00:42Z

TomFrayne: Explain FOSS

The concept of "freedom", as it applies to software, is complicated because of the multiple uses of "free" in the English language. Some have proposed the term "libre software" to eradicate potential confusion; as of this writing, this term has not caught on widely.

The [[FSF]] (or Free Software Foundation) clearly explains their position here: [http://www.fsf.org/philosophy/free-sw.html]

Note that, politically, ''free software'' and ''[[Open Source]] software'' are two separate movements, with separate but frequently overlapping goals. "Free Software" focuses on the political and ethical ramifications of keeping software free. "Open Source" tends to focus on more the more pragmatic advantages that come with open source, such as code quality and lower development costs. Individual software packages are often referred to using either term, and the distinctiveness of the two approaches is further blurred by the increasing use of the term [[FOSS]], or 'Free and Open-Source Software' to refer to software that is either free as in speech, or Open-Source.

"FOSS" is a better term to describe programs satisfying its definition when only the practical effects are being considered, since the term can be defined once, without any unfortunate connontations.

There are two different meanings of "free" when referring to software: available at no cost, or freely modifiable under a non-restrictive license. The analogy commonly used to illustrate the distinction is by comparing "free beer" to "free speech." The second meaning is uniformly advocated by some in [[FSF]], with the first meaning rendered "free as in beer".

The [[Open Source Initiative]] maintains a list of dozens licenses which are considered compatible with the goals of the Open Source movement, including the [[GPL]] and [[LGPL]], [[BSD license|BSD]], [[Apache]], [[Mozilla MPL|Mozilla]], and [[SISSL]] licenses.

There is also a Linux command [[free (command)|free]].

Open Source

2004-06-16T17:49:13Z

TomFrayne: FOSS, expanded copyleft description

'''Open Source''' is a recent term developed by a group of Linux and [[Free]] software developers and advocates. It carries more pragmatic connotations than [[Free Software]], though both terms and both movements are still flourishing today. Open source software is not necessarily [[copyleft]]ed.

The term can refer to software that is available under an OSI-approved license; it can also apply more broadly to any software that operates under the general principles of openness, source sharing, and meritocratic development.

The term can also apply to the popular movement of individuals, organizations and companies that seek to put such software into mainstream usage. In this usage, Open Source is generally regarded as the more pragmatic, business-conscious movement, while Free Software proponents take a long-term, more idealistic perspective. Both camps have their acknowledged place in the development of '''Free and Open-Source Software''' (or [[FOSS]]) and both remain friendly despite ideological differences.

A common copyleft license is the [[GNU]] [[GPL]]. Sometimes, confusion arises regarding which is more "free" -- Open source or copyleft. The distinction is: open source software provides more freedom for the user to do what they wish with the code, copylefting keeps the software itself free (as in libre) by forbidding the user from incorporating the software into [[Proprietary]] programs.

==External links==
*[http://www.opensource.org/ Open Source Initiative]
*[http://www.opensource.org/licenses/ OSI Approved Licenses]
*[http://www.opensource.org/docs/definition_plain.php Open Source Definition]
*[http://www.fsf.org/philosophy/free-sw.html The FSF Definition]
*[http://www.gnu.org/philosophy/free-software-for-freedom.html The FSF Position on Open Source]
*[http://www.opensource.org/advocacy/faq.php The OSI Position on Free Software] - midway down the page