Differences between revisions 48 and 49
Revision 48 as of 2008-03-23 20:00:34
Size: 14081
Comment:
Revision 49 as of 2008-03-23 20:05:36
Size: 14089
Comment:
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:
= Why bother = == Why bother ==
Line 38: Line 38:
= Using Debian = == Using Debian ==
Line 106: Line 106:
= Software Packages = == Software Packages ==
Line 136: Line 136:
= Posting on debian-user = == Posting on debian-user ==

Translation(s): none

(!) [:/Discussion:Discussion]


This page is meant to collect frequently asked questions from the [http://lists.debian.org/debian-user debian-user] mailing list. The contents are licenced under the terms of GPLv2 or, in the event a DFSG compatible licence is applied to [http://wiki.debian.org wiki.debian.org] at large, then under that licence. Posting material to this page is an acceptance of this.

?TableOfContents(2)

?Anchor(why)

Why bother

Why should I post to this list? I want to ask the developer/post to debian-devel/file a bug.

Of course, you are free to do this. Almost all debian lists (including debian-devel) are open for anyone to post and Debian encourages users to file bugs in the Debian Bug Tracking System (BTS). BUT, please consider following points first:

  • Make 100% sure your problem needs direct attention of developers. Remember, Debian is created by volunteers in their spare time. Distracting them with other problems will leave less time to do actual work, like solving known bugs, package new versions of software we are all waiting for, packaging software not yet present in Debian and improving or creating Debian specific software. Even if you know you have a really difficult problem, debian-user is read by some very knowledgeable people (including some Debian developers), and they might have a solution for your problem.

  • Some problems are caused just by misconfiguration. Sometimes even the most experienced people can do stupid things. Having other people look over your problem may help.
  • Make sure your problem is not known. That means you should search the archives of debian-user (or other relevant lists) and especially the BTS. Chances are somebody else has experienced the same (or similar) problem and workarounds may be known. Even if you searched thoroughly, you should post to debian-user first (stating what you already tried/researched).

If you considered all above points and still want to address debian-devel, then please make sure:

  • your problem is not specific to a package (you could file a bug instead)
  • it hasn't been discussed yet (you did search the archives, right?)
  • you are addressing the right list (ex. legal stuff should go to debian-legal, website specific to debian-www, ...)

In case you have doubts just post to debian-user, sometimes answers come within minutes.

?Anchor(using)

Using Debian

Should I be running Testing/Unstable(Sid) instead of Stable/Testing?

This is something that you as a user and administrator of your system have to decide for yourself. If you just need a few newer packages try http://www.backports.org before considering an upgrade. If you have Debian on a desktop machine testing might be an option, but it's not really recommended for production machines. If you want all the newest software Debian can provide and don't mind/can handle breakage then you could try unstable. Each Debian distribution has its pros and cons. Here are some:

Stable
  • released approx. every 1.5 years.
  • has security support and occasional bug-fixes (via the security archive, proposed-updates archive and point releases).
  • very stable, thoroughly tested, recommended for environments where frequent changes are not desired and high uptimes are required.
  • can have oldish software and may lack support for very new hardware.

    See DebianEtch and DebianStable for more informations ...

Testing
  • testing is slowly evolving to become the next Stable release, but until released it is still testing ground. As the release approaches (testing freeze) it becomes more and more like a newer stable release (with all pros and cons).
  • packages have already received some testing in unstable.
  • security support.
  • bug fixes have to go through unstable first (min. 10 days). Because of this any breakage will take at least 10 days to be fixed.
  • requires some skill to maintain.

    See DebianLenny and DebianTesting for more informations ...

Unstable (a.k.a. Sid)
  • contains packages uploaded by the developers for the next release, but will never be released. Instead, packages will migrate to testing if no release-critical bugs are found in 10 days (and there are no dependency problems).
  • usually has quite new software.
  • no security support similar to stable or testing, but updated packages should also incorporate security fixes.
  • changes can happen even daily.
  • serious breakage can (and will!) occur; requires good skills to maintain, but good for learning if you don't mind the downtime.

    See DebianSid and DebianUnstable for more informations ...

Experimental

This is not a regular distribution (you cannot run on experimental), but it is mentioned here for completeness.

  • a place for maintainers to upload packages which are not suitable for unstable, but still need a wider audience for testing.
  • no security support and some packages can stay here for long times without any updates.
  • usage is not recommended unless you really know what you are doing.

    See DebianExperimental for more informations ...

How dangerous is it to run a mixed system?

That depends on how many and what packages you are using, but it can be more dangerous than running pure unstable. Installing packages from different releases can cause complex problems which are less likely to occur with packages from a single release. One example is that existing packages may become uninstalled due to internal restructuring of central components within the testing or unstable branches.

Try [http://www.backports.org backports] first. If you can't find what you need there you can also backport a package yourself.

  • See ["Backports"] for more informations ...

?Anchor(using-devswitch)

My harddisks/usb sticks/external drives don't always have the same device name. How can I prevent this from happening?

There are several methods, but it seems the easiest method is to use labels instead of device names. Basically in fstab you just replace the /dev/sda1 (or hda2 or whatever) with a LABEL=mylabel. If you also have problems booting (because your / partition is assigned a different device name) you will also have to edit /boot/grub/menu.lst. Don't edit the real stanza because your changes will be overwriten on the next kernel upgrade. Instead find the line:

# kopt=root=/dev/hda1

and replace with

# kopt=LABEL=my_root_label

After you are done you must run /sbin/update-grub.

Another alternative to using labels is to use UUIDs. You can find the UUID of a device with blkid(8).

?Anchor(package)

Software Packages

Debian is known for its robust, extensive and easy to use package system. The operations that can be performed with regard to package management are sophisticated, easily scripted, and make running Debian a relatively simple and mistake-proof experience. The following questions all deal with some aspect of the package management.

Which is the best package manager?

While "the best" package manager is a matter of personal opinion, the Debian project and many Debian developers and users recommend aptitude. Users of previous versions of Debian may prefer to use the ["dselect"] tool, but aptitude works fine even on sarge (currently oldstable). See http://lists.debian.org/debian-user/2004/04/msg03138.html here] for more details.

  • See ["Aptitude"], ["Synaptic"] or ["dselect"] for more information ...

?Anchor(package-search)

Where is the foo package?

A variety of tools exists to answer this very frequent question: apt-cache search foo will return all the packages with foo in the name or description; aptitude search foo will return all packages with foo in the package name. These are just two of the many methods. Read man apt-cache or man aptitude as appropriate. Finally, http://packages.debian.org also features a handy search engine and don't forget your friend http://www.google.com.

?Anchor(package-file)

Program foo is looking for (or lacking) file bar. Where is it?

This is simple: apt-file update && apt-file search bar. grep as appropriate. man apt-file.

Does Debian have Firefox/What is Iceweasel?

You really should see [#package-search Where is the foo package?] above, but Debian ships with Iceweasel, a rebranded Firefox (reference needed).

  • See ["Iceweasel"] for more informations ...

I am running a mixed system. How can I find out what packages are from which distribution?

You definitely like to play with fire if you got this far, but can't answer this simple question. OK, enough patronizing :) , try apt-show-versions.

?Anchor(posting)

Posting on debian-user

?Anchor(posting-howto)

How should I post/reply to debian-user?

Please see the [http://www.debian.org/MailingLists/#codeofconduct Code of conduct] for Debian mailing lists. It is also helpful if you ask your questions in a [http://www.catb.org/~esr/faqs/smart-questions.html smart way] and answer by [http://www.netmeister.org/news/learn2quote.html quoting] properly.

?Anchor(posting-noreply)

I asked my question according to the directions written at the "How should I post" question, but I still don't get an answer

I don't think you really read [http://www.catb.org/~esr/faqs/smart-questions.html this faq] referenced [#posting-howto above] (this question is anwered there, I just double-checked :) ).

?Anchor(posting-subscribe)

Should I be subscribed to post to debian-user?

Debian has a policy of open mailing lists. This means most lists are open for anyone to write to (the occasional spam resulting from this is unavoidable, but only a minor inconvenience - the list has excellent filters). However, list subscribers can not guess if you are subscribed or not, so you should request replies to be CC'd to you (or set Reply-to: accordingly).

?Anchor(posting-flood)

I subscribed the list, but my mailbox is flooded with mail

The debian-user mailing list is a very high traffic list (numbers?), but there are ways to cope with it:

  • setup a filter to move all list mail to a dedicated folder (if you want it all) or even delete all list mail except specific threads (ex. the ones initiated by you)
  • use alternatives:
    • gmane is a mail-to-news gateway with an alternative nice web interface (subscription required?)
    • google-groups also carries debian-user if you prefer their interface (subscription required)
    • debian-user is also available as a newsgroup (directly or via gmane)
    • read the archives (but beware, it can take a while longer until a mail shows up there)
  • just unsubscribe. If you only want to receive answers to your posts you can ask for a CC (or set Reply-to: accordingly)
  • use a decent mail client. It should support at least some way of threading (and sorting if not done by other means) and reply-to-list (if you plan to participate in discussions).

?Anchor(posting-top)

What is top-posting (and why shouldn't I do it)?

Both questions can be answered with this example (seen in some sig):

A: Because it messes up the way you read

Q: Why is top-posting bad?

A: Writing your answer before the question

Q: What is top-posting?

?Anchor(posting-munging)

Why doesn't this list facilitate easy replies to the list (a.k.a. reply-to-munging)?

Short answer: it's against the standards. See [http://www.unicom.com/pw/reply-to-harmful.html this] document for a thorough explanation. In case your e-mail client doesn't support List-reply (ReplyToListEmailClients) then please use Reply-to-all and delete all but the list address.

?Anchor(posting-whitelist)

My posts are considered spam and rejected (or never show up)

Try subscribing to the [http://lists.debian.org/whitelist/ whitelist]. See also [#posting-gmail this question] in case you post from a gmail account.

?Anchor(posting-gmail)

I'm posting via gmail's servers, but I never receive my own posts (other list mail is fine)

Gmail has a somewhat different (as in against the standards) view of how a mail server should behave. If you still want to use Gmail for posting here are a few possible workarounds:

  • configure your mail client to save outgoing messages to the same folder. Most (all?) mail clients should be able to do this per folder.
  • use a different account for receiving list mail. Most Debian lists (including debian-user) are open for anyone to post, so you don't need to be subscribed to be able to post (you could however subscribe to the [#posting-whitelist whitelist]).

It seems Gmail considers this to be a feature and is not willing to change it, although requested by many users. You could try writing them about this as well, maybe they will eventually listen.


["FAQs"]