Je viens de voir passer un document tres interressant sur debian-doc, sans
qu'il y ait de references sur ou le trouver sur le r�seau. Alors je
l'attache.
En r�sum�, c'est la liste des differences majeures entre debian et les
autres distribs en une page. Pas de la pub, mais la liste des pieges �
eviter pour les nouveaux venus d'autres distrib. Bon, y'a pas tout, mais
y'a pleins de trucs biens.
Si vous insistez, je peux le rajouter comme chapitre � la FAQ:
quick start pour les gourous d'autres distributions d�couvrant Debian.
(si c'est pas plus epais que ca)
Voila, voila, Mt.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Sysadmin Hints on Debian Linux</title>
<meta name="modificationdate" content="$Date: 1998/08/05 17:23:10 $">
<meta name="revision" content="$Revision: 1.4 $">
</head>
<body bgcolor="white">
<!--
Copyright @copyright{} 1998 onShore Inc. All rights deserved.
-->
<h2 align="center"><a name="top">Getting Along with Debian Linux</a></h2>
<p align="center">
(hints from Adam Harris
<a href="mailto:[EMAIL PROTECTED]">
<tt><[EMAIL PROTECTED]></tt></a>)
</p>
<p></p>
<hr>
<p>
If you're new to Debian, you might not know the following:</p>
<ul>
<li>
the pkg management system <em>owns</em> much of your hard drive. The
following directories should not be messed with manually unless you
really know what you are doing:
<br>
<ul>
<li><tt>/usr</tt> (excluding <tt>/usr/local</tt>)</li>
<li><tt>/var</tt>
(you could make <tt>/var/local</tt> and be safe in there)</li>
<li><tt>/bin</tt></li>
<li><tt>/sbin</tt></li>
<li><tt>/lib</tt></li>
</ul>
<br>
If you do mess around in there, you are liable to have whatever
you did be stomped by upgrading a package.
<p>
</li>
<li>
alternative versions of applications are managed by
<tt>update-alternatives</tt>, man page for which (!!!!) still not
shipped as of 4 June 1998, unfortunately. Basically, say,
<tt>/usr/bin/vi</tt> -> <tt>/etc/alternatives/vi</tt> ->
{<tt>nvi</tt>, <tt>vim</tt>, whatever you like}. You can set your
preferred <tt>vi</tt> by modifying the symlinks in
<tt>/etc/alternatives/</tt>.
<p>
</li>
<li>
X configuration is a pain in the butt; but I suggest you use the
<tt>XF86Setup</tt> program (part of the <tt>xserver-vga</tt>
package). Sometimes that doesn't work, however.
<p>
</li>
<li>
Documentation to be found in /usr/doc. To submit bugs, look at
<tt>/usr/doc/debian/bug*</tt>. To read about Debian-specific
issues, look at <tt>/usr/doc/<pkg>/README.Debian</tt>.
<p>
</li>
<li>
The best installation method is <tt>apt</tt>. Get it from
<tt><debian_mirror>/project/experimental/</tt>. Once you have
that, you can use it as a method from <tt>dselect</tt>; or you can use the
command line version. Look at <tt>apt-get</tt>(8). Note
<tt>apt</tt> also will let you merge, say, <tt>ftp1.debian.org</tt>
with <tt>ftp.de.debian.org</tt> in such a way as you have the
export-restricted packages (like pgp) as well as the std pkgs.
<p>
</li>
<li>
The debian way of building a kernel is also somewhat different.
Get the <tt>kernel-package</tt> pkg, get the kernel source tree
(either debian version or standard linux archive kernel will work),
install in <tt>/usr/src/linux</tt> (or symlink to that), and for any
non-std modules (i.e., pcmcia) get that source too (debian module
sources will install to <tt>/usr/src/modules</tt>). Then read
<tt>/usr/doc/kernel-packages/README.gz</tt>. This method will make
a <tt>.deb</tt> of your kernel source, and, if you have non-std
modules, make a synchronized dependant <tt>.deb</tt> of those too.
It's a better way to manage kernel images; <tt>/boot</tt> will hold
the kernel, the <tt>System.map</tt>, and a log of the active config
file for the build.
<p>
</li>
<li> Ever said, "Damn, where the fsck is that cron job"? Ever
<tt>grep</tt>ped thru <tt>/var/spool/cron/crontabs</tt>, had to
<tt>su</tt> to some wierd user, then do <tt>crontab -e</tt>? Even had
to look through all the cron jobs, thinking about whether they all
happen to fire at the same time or not?
<p>
Well, you don't have to anymore. Only <em>personal</em> cron jobs
should be in <tt>/var/spool/cron/crontabs</tt> on a debian server.
Any jobs under the purview of the system administrator should be in
<tt>/etc</tt>, since they are configuration files. If you have a root
cron job for daily, weekly, or nightly runs, put them in
<tt>/etc/cron.{daily,weekly,monthly}</tt>. These are invoked from
<tt>/etc/crontab</tt>, and will run in alphabetic order, which
serializes them.</p>
<p>
On the other hand, if you have a cron job that (a) needs to run as a
special user, or (b) needs to run at a special time or frequency, you
can use either <tt>/etc/crontab</tt>, or, better yet,
<tt>/etc/cron.d/whatever</tt>. These particular files also have an
extra field that allows you to stipulate which the user under which
the cron job runs.</p>
<p>
In either case, you just edit the files and cron will notice them
automatically. No need to run a special command.</p>
<p>
For more information see <tt>cron(8)</tt>, <tt>crontab(5)</tt>, and
<tt>/usr/doc/cron/README.Debian</tt>.</p>
<p>
</li>
</ul></body></html>
