Translations for the debian web site maintained by Jérôme Abela
Hello,
This is a automatically generated mail sent to you
because you are the official translator of some pages
in french of the Debian web site.
I send you the diff between the version you translated and
the current version to allow you to update your work.
For more informations, contact your team coordinator, or
the Debian web-masters (debian-www@lists.debian.org).
Thanks, and sorry for the annoyance.
+++++++++++++++++++++++++++++ CHANGES IN english/ports/hurd/hurd-install.wml
Index: english/ports/hurd/hurd-install.wml
===================================================================
RCS file: /cvs/webwml/webwml/english/ports/hurd/hurd-install.wml,v
retrieving revision 1.10
retrieving revision 1.14
diff -u -u -r1.10 -r1.14
--- english/ports/hurd/hurd-install.wml 1999/08/05 22:22:17 1.10
+++ english/ports/hurd/hurd-install.wml 2000/08/11 16:53:52 1.14
@@ -8,113 +8,127 @@
[ <a href="hurd-links">Links</a> ]
[ <a href="hurd-contact">Contact</a> ]<p>
-<h1>Debian GNU/Hurd</h1>
-<h2>Hardware</h2>
+<h1>
+Debian GNU/Hurd</h1>
+
+<h2>
+Installation</h2>
+
+<h3>
+Hardware</h3>
+<p>
+Please check the <a
+href="http://www.urbanophile.com/arenn/hacking/hurd/hurd-hardware.html";>Hardware
+Compatibility Guide</a> to learn which hardware is supported under the
+Hurd.</p>
+
+<h3>
+Software</h3>
+<p>
+There is an excellent document available, the <a
+href="http://www.pick.ucam.org/~mcv21/hurd.html";>Easy Guide</A> by
+Matthew Vernon, which you should definitly read (but be careful,
+Matthew has not always the time to keep it up to date. Don't get
+confused by slightly outdated instructions). Below you find all you
+need to get a working system, but the Easy Guide has probably some
+interesting note that give you more information about the
+installation.</p>
+
+<p>
+There are two ways to install a Debian GNU/Hurd system. The first way
+makes it possible to install directly from the Debian packages, but
+requires <code>dpkg</code>, the Debian package manager. This may be
+difficult if you use another Linux distribution beside Debian, or if
+you don't run Linux at all. Therefore, there is a second method using
+a prepared <code>tar</code> archive file. After installing that, you
+can update your system to the most up to date versions of the Debian
+packages natively. Both methods are described in more detail
+below.</p>
+
+<h4>
+Common Preperations</h4>
+<p>
+To start the installation, make the Hurd partition with <code>mke2fs
+-O sparse_super -o hurd /dev/PARTITION</code>, where <code>PARTITION</code> is the
+partition of the hard disk you want to dedicate to the Hurd. Note that
+the partition size should not exceed about 1 GigaByte currently, due
+to a known limitation in the Hurd.
+<p>
+Then mount your partition somewhere safe. I use <code>/gnu</code> as
+the mount point, mostly because this is our default for cross
+compilation. Any other place is good enough, as well as doing this
+into a disk image inside a file (loop mount). From here, I will assume
+that you use <code>/gnu</code>. Please change the commands accordingly
+if you use something else.</p>
+
+<h4>
+Two Alternatives</h4>
+
+<h5>
+Installation Using Debian Packages</h5>
<p>
-Please check the
-<a href="http://www.urbanophile.com/arenn/hacking/hurd/hurd-hardware.html";>Hardware Compatibility Guide</a>
-to learn which hardware is supported under the Hurd.
-</p>
-<H2>Installing Debian GNU/Hurd</H2>
-<P>
-There is an excellent document available, the <A
-HREF="http://www.pick.ucam.org/~mcv21/hurd.html";>Easy Guide</A> by Matthew
-Vernon, which you should definitly read. On this page, you will only find
-very sparse information, just enough to get you started if you are an
-experienced user or developer.
-</P>
-<P>
-There are two ways to install a Debian GNU/Hurd system. The first way makes
-it possible to install directly from the Debian packages, but you will need
-<TT>dpkg</TT>, the Debian package manager, to do so. This may be difficult
-if you use another Linux distribution beside Debian, or if you don't run
-Linux at all. Therefore, there is a second method, using a prepared tar
-archive file. After installing that, you can update your system to the most
-up to date versions of the Debian packages natively. Both methods will be
-described in more detail below.
-</P>
-<H3>Common Preperations</H3>
-<P>
-To start the installation, make the Hurd partition with <TT>mke2fs -o hurd
-/dev/PARTITION</TT>, where <TT>PARTITION</TT> is the partition of the hard
-disk you want to dedicate to the Hurd. Note that the partition size should not
-exceed about 1 GB currently, due to a known limitation in the Hurd.
-</P>
-<P>
-Then mount your partition somewhere safe. I use <TT>/gnu</TT> as the mount
-point, mostly because this is our default for cross compilation. Any other
-place is good enough, as well as doing this into a disk image on a file
-system. From here, I will assume that you use <TT>/gnu</TT>. Please change the
-commands accordingly if you use something else.
-</P>
-
-<H3>Two Alternatives</H3>
-<H4>Installing with Debian packages</H3>
-<P>
To install Debian GNU/Hurd, you need to fetch the Debian software packages
and my installation scripts. First get the following scripts:
-<UL>
-<LI><A HREF="extra-files/cross-install"><TT>cross-install</TT></A> - Installing a
- bunch of packages from Linux</LI>
-<LI><A HREF="extra-files/native-install"><TT>native-install</TT></A> - Configuring the new
- system</LI>
-<LI><A HREF="extra-files/dpkg-hurd"><TT>dpkg-hurd</TT></A> - Use dpkg on the Hurd
- partition from Linux</LI>
-</UL>
-</P>
-<P>
-If you don't have Debian, you will also need a version of <TT>dpkg</TT> for your
-system.
-</P>
-<P>
-Last but not least, the Debian packages are required. They are located on
-any <A HREF="../../distrib/ftplist">Debian FTP mirror</A>, in the directory
-<TT>debian/dists/unstable/main/binary-hurd-i386/</TT>. You need a certain
-set which is specified at the top of the <TT>dpkg-hurd</TT> script. You can
-save the packages in a single directory or spread in subdirectories in the
-way they are organized at the FTP site.
-</P>
-<P>
-Now <TT>cd</TT> into the directory you keep your scripts and the Debian
-packages in. If you use a single directory, it must contain all files. If
-you use the FTP organization for packages, be sure that the scripts are in
-the top level directory, so it can find the packages in <TT>base/</TT> etc.
-Run <TT>./cross-install /gnu</TT>. Answer the question about the
-<TT>/usr</TT> symlink with <TT>y</TT>. Now continue with <A
-HREF="#reboot">Rebooting the System</A>.
-</P>
-
-<H4>Installing with tar Archive File</H4>
-<P>
-Sometimes, I upload snapshots of the current base system to some FTP site.
-Currently, this is <tt><a href="ftp://alpha.gnu.org/pub/gnu/hurd/contrib/marcus/";>ftp://alpha.gnu.org/pub/gnu/hurd/contrib/marcus/</a></tt>
-Those files are named <TT>gnu-YYYYMMDD.tar.gz</TT>, where <TT>YYYYMMDD</TT>
-is the date of the snapshot. Those files can be used to install the Hurd even
-if you have never seen a Debian system. The procedure described here will
-not work out of the box for the <TT>gnu-19990104.tar.gz</TT>, so get a later
-one if available.
-</P>
-<P>
-To do this, download the tar file of the most recent date. This is the only
-file you will need to get a working system (beside GRUB). <TT>cd /gnu</TT> to
-get to the root of the Hurd partition. Now extract the tar file with the
-command <TT>tar -xpzf /somewhere/gnu-YYYYMMDD.tar.gz</TT> using the correct
-path and date.
-</P>
-<p><B>IMPORTANT:</B>If you use the version from 19990505, please update the
-<tt>native-install</tt> script inside the tar file with the latest version.
-</p>
-<A NAME="reboot"><H3>Rebooting the System</H4></A>
-<P>
-Now reboot the system and use GRUB to boot the Hurd partition. I won't give
-detailed information on GRUB and partition naming schemes here, this is
-covered elsewhere. You will find this and other useful information in the <A
-HREF="http://www.pick.ucam.org/~mcv21/hurd.html";>Easy Guide</A> by M. C. Vernon.
-</P>
-<P>
-After the reboot, you only need to run <TT>./native-install</TT> to finish
-the installation. Have fun!
-</P>
+<ul>
+<li>
+<a href="extra-files/cross-install"><code>cross-install</code></a> -
+Installing a bunch of packages from Linux</li>
+<li>
+<a href="extra-files/native-install"><code>native-install</code></a> -
+Configuring the new system</li>
+<li>
+<a href="extra-files/dpkg-hurd"><code>dpkg-hurd</code></a> - Use dpkg
+on the Hurd partition from Linux</li></ul></p>
+<p>
+If you don't have Debian, you will also need a version of
+<code>dpkg</code> for your system.</p>
+<p>
+Last but not least, the Debian packages are required. They are located
+on any <a href="../../distrib/ftplist">Debian FTP mirror</a>, in the
+directory <code>debian/dists/unstable/main/binary-hurd-i386/</code>.
+You need a certain set which is specified at the top of the
+<code>dpkg-hurd</code> script. Recent versions of
+<code>cross-install</code> offer an automatical download feature for
+your convenience. This option requires a network connection and the
+<code>wget</code> utility. Otherwise you can manually download the
+packages and save them in a single directory or spread in
+subdirectories in the way they are organized at the FTP site.</p>
+<p>
+Now <code>cd</code> into the directory you keep your scripts and the
+Debian packages in. If you use a single directory, it must contain all
+files. If you use the FTP organization for packages, be sure that the
+scripts are in the top level directory, so they can find the packages
+in <code>base/</code> etc. Run <code>./cross-install /gnu</code>. If
+all goes well, the packages will be installed and some patches will be
+applied to fix known problems. Now continue with <a
+href="#reboot">Rebooting the System</a>.</p>
-</BODY>
-</HTML>
+<h5>
+Installation Using the <code>tar</code> Archive File</h5>
+<p>
+Sometimes I upload snapshots of the current base system to <code><a
+href="ftp://alpha.gnu.org/pub/gnu/hurd/contrib/marcus/";>ftp://alpha.gnu.org/pub/gnu/hurd/contrib/marcus/</a></code>
+Those files are named <code>gnu-YYYYMMDD.tar.gz</code>, where
+<code>YYYYMMDD</code> is the date of the snapshot. Those files can be
+used to install the Hurd even if you don't have a working version of
+the <code>dpkg</code> package manager available.
+<p>
+Download the tar file of the most recent date. This is the only file
+you will need to get a working system (beside GRUB). <code>cd
+/gnu</code> to get to the root of the Hurd partition. Now extract the
+tar file with the command <code>tar --same-owner -xpzf
+/somewhere/gnu-YYYYMMDD.tar.gz</code> using the correct path and
+date.</p>
+
+<h4><a name="reboot">
+Rebooting the System</a></h4>
+<p>
+Now reboot the system and use GRUB to boot the Hurd partition. I won't
+give detailed information on GRUB and partition naming schemes here,
+this is covered somewhere else. You will find this and other useful
+information in the <a
+href="http://www.pick.ucam.org/~mcv21/hurd.html";>Easy Guide</a> by
+M. C. Vernon.</p>
+<p>
+After rebooting, you only need to run <tt>./native-install</tt> to
+finish the installation. Have fun!</p>
+++++++++++++++++++++++++++++ END OF english/ports/hurd/hurd-install.wml
+++++++++++++++++++++++++++++ CHANGES IN english/ports/hurd/index.wml
Index: english/ports/hurd/index.wml
===================================================================
RCS file: /cvs/webwml/webwml/english/ports/hurd/index.wml,v
retrieving revision 1.5
retrieving revision 1.7
diff -u -u -r1.5 -r1.7
--- english/ports/hurd/index.wml 1999/08/05 22:22:17 1.5
+++ english/ports/hurd/index.wml 1999/09/30 00:55:23 1.7
@@ -8,41 +8,45 @@
[ <a href="hurd-links">Links</a> ]
[ <a href="hurd-contact">Contact</a> ]<p>
-<h1>Debian GNU/Hurd</h1>
-<h2>Introduction</h2>
-<P>
-The <A HREF="http://www.gnu.org/software/hurd/hurd.html";>Hurd</A> is a set
-of translators on top of the GNU Mach Microkernel. Together they build the
-base for the <A HREF="http://www.gnu.org/";>GNU</A> Operating System.
-</P>
-<P>
+<h1>
+Debian GNU/Hurd</h1>
+<h2>
+Introduction</h2>
+<p>
+The <a href="http://www.gnu.org/software/hurd/hurd.html";>Hurd</a> is a
+set of servers running on top of the GNU Mach microkernel. Together they
+build the base for the <a href="http://www.gnu.org/";>GNU</a> operating
+system.</p>
+<p>
Currently, Debian is only available for Linux, but with Debian
-GNU/Hurd we have started to offer the Hurd as a development platform, too.
-Debian GNU/Hurd is not officially released yet, and won't be for some time.
-</P>
-<H2>Development</H2>
-<P>
-This is, because the Hurd is under development, and does not provide the
-performance and stability you would expect from a production system. Also,
-the number of Debian packages ported to the Hurd does only make a small
-percentage of the full Debian distribution (about 10%). There is a lot of
-work to do before we can make a release.
-</P>
-<P>
-Until then, you can participate in the development if you want. Depending on
-your experience and time commitment, you can help us in many different
-ways. For example, we need experienced C hackers for development and
-implementation of new features, we need C hackers for bug fixing and
-debugging, too. If you are not very experienced in C programming, you can
-still help: Either by testing the existing systems, and reporting bugs, or
-by trying to compile more software you have experience with. Also writing
-documentation is important, or maintaining the web pages.
-</P>
-<H2>How do I join?</H2>
-<P>
-To start with Hurd development, you should <A HREF="hurd-install">install
-the Hurd</A>, and get used to it. Also, join the <A HREF="hurd-contact">mailing
-lists</A> and try to get a feeling for the state of the development. Offer
-your help, and we will tell you what is needed. There are also various
-<A HREF="hurd-task">task lists</A> available.
-</P>
+GNU/Hurd we have started to offer the Hurd as a development, server
+and desktop platform, too. However, Debian GNU/Hurd is not officially
+released yet, and won't be for some time.</p>
+<h2>
+Development</h2>
+<p>
+The Hurd is under <a href="hurd-devel">active development</a>, but
+does not provide the performance and stability you would expect from a
+production system. Also, the number of Debian packages ported to the
+Hurd does only make a small percentage of the full Debian distribution
+(about 10%). There is a lot of work to do before we can make a
+release.</p>
+<p>
+Until then, you can participate in the development if you want.
+Depending on your experience and time commitment, you can help
+us in many different ways. For example, we need experienced C hackers
+to develop and implement new features and to fix bugs and debug the system.
+If you are not very experienced in C programming, you can still help:
+Either by testing the existing systems and reporting bugs, or by trying
+to compile some unported software you have experience with.
+Also writing documentation is important, or maintaining the web pages.</p>
+<h2>
+How do I join?</h2>
+<p>
+To start with Hurd development, you should <a
+href="hurd-install">install the Hurd</a> and get used to it. Also,
+join the <a href="hurd-contact">mailing lists</A> and try to get a
+feeling for the state of the development. Offer your help, and we will
+tell you what is needed to do. There are also various <a
+href="hurd-devel-tasks">task lists</a> available.</p>
+
+++++++++++++++++++++++++++++ END OF english/ports/hurd/index.wml
+++++++++++++++++++++++++++++ CHANGES IN english/ports/hurd/hurd-faq.wml
Index: english/ports/hurd/hurd-faq.wml
===================================================================
RCS file: /cvs/webwml/webwml/english/ports/hurd/hurd-faq.wml,v
retrieving revision 1.10
retrieving revision 1.22
diff -u -u -r1.10 -r1.22
--- english/ports/hurd/hurd-faq.wml 1999/08/05 22:22:17 1.10
+++ english/ports/hurd/hurd-faq.wml 2000/11/12 15:13:43 1.22
@@ -8,308 +8,437 @@
[ <a href="hurd-links">Links</a> ]
[ <a href="hurd-contact">Contact</a> ]<p>
-<h1>Debian GNU/Hurd</h1>
-<h2>Frequently Asked Questions (FAQ)</h2>
+<h1>
+Debian GNU/Hurd</h1>
+<h2>
+Frequently Asked Questions (FAQ)</h2>
<p>
-Note that this FAQ will not only contain FAQ's, but probably all interesting
-talk on the Hurd mailing lists. I am going to use this as a catch all bucket
-until the various information is in its proper place.
-
-<h3>"General"</h3>
-<p>
-<b>Question</b>:
-Is the Hurd under development, or is it a dead project?</p>
-<p><b>Answer</b>:
-It is under active development these days. We are fixing bugs to get more
-stability and port many common software packages. We also add small to
-medium sized features. We would like to get more developers on board, too.
-There are a lot of very interesting features to be implemented, and you
-seldom get the chance to design and implement parts of an exciting
-operating system!</p>
-
-<p><b>Question</b>:
-Does it run at all?</p>
-<p><b>Answer:</b>
-Yeah.
-</p>
-
-<h3>... At Installation Time</h3>
-<P>
-<B>Question</B>:
-Which partition type should I use for my GNU/Hurd partition?</P>
-<p><b>Answer</b>:
-You should use an ext2 file system. Alternatively, you may
-use BSD style ufs. The partition type number for ext2fs is 0x83 (same as Linux),
-<em>not</em> 0x63 (GNU HURD). Thomas explains why 0x63 is the wrong choice:
+Note that this FAQ will not only contain FAQ's, but probably all
+interesting talk on the Hurd mailing lists. I am going to use this as
+a catch all bucket until the various information is in its proper
+place.
+
+<h3>
+`General'</h3>
+<p>
+<b>
+Question</b>: Is the Hurd under development, or is it a dead
+project?
+<p>
+<b>
+Answer</b>: It is under active development these days. We are fixing
+bugs to get more stability and port many common software packages. We
+also add small to medium sized features. We would like to get more
+developers on board, too. There are a lot of very interesting
+features to be implemented, and you seldom get the chance to design
+and implement parts of an exciting operating system, so join in
+today!
+
+<p>
+<b>
+Question</b>: Does it run at all?
+<p>
+<b>
+Answer</b>: Yeah.
+
+<p>
+<b>
+Question</b>: What is a Hurd?
+<p>
+<b>
+Answer</b>: The Hurd stands for Hird of Unix Replacing Daemons, while
+Hird stands for Hurd of Interfaces Representing Depth.
+<p>
+The Hurd is a collection of servers to run on top of a microkernel,
+and providing a Un*x-like environment.
+
+<h3>
+... At Installation Time</h3>
+<p>
+<b>
+Question</b>: Which hardware is supported by the Hurd?
+<p>
+<b>
+Answer</b>: Please read the <a
+href="http://www.urbanophile.com/arenn/hacking/hurd/hurd-hardware.html";>Hardware
+Compatibility Guide</a> to answer your question.
+
+<p>
+<b>
+Question</b>: Which partition type should I use for my GNU/Hurd
+partition?</P>
+<p>
+<b>Answer</b>: You should use an ext2 file system. Alternatively, you
+may use BSD style ufs. The partition type number for ext2fs is
+<code>0x83</code> (same as Linux), <em>not</em> <code>0x63</code> (GNU
+HURD). Thomas explains why <code>0x63</code> is the wrong choice:
<blockquote>
One day we may have a new filesystem format, which would probably be
called the GNU Hurd filesystem format, and might well use that
partition code. Regardless, it is always an error to use that code
-for an ext2fs partition, as Roland points out.
-</blockquote>
+for an ext2fs partition, as Roland points out.</blockquote>
+
+<p>
+<b>
+Question</b>: What is my partition name/number?
+<p>
+<b>
+Answer</b>: I knew you would ask this. If I had to reduce this FAQ to
+only one question, I'd choose this one. It is pretty easy, but you
+have to know that there are actually three naming convention we face
+here.
+<p>
+All naming conventions use <code>hd</code> for IDE and <code>sd</code>
+for SCSI disks. So far the commonalities. Now for the differences.
+<p>
+First, figure out the disk number. If it is a SCSI disk, you need to
+know the SCSI disk number. If it is an IDE disk, you need to know on
+which controller it is and if it is a master or slave. For Linux, the
+master disks on the primary controller has the letter "a", the slave
+on the same controller the letter `b'. Master and slave on the
+secondary controller have the letters `c' and `d' respectively. The
+Hurd does use BSD style notation so it is `0', `1', `2' and `3'
+instead `a', `b', `c' and `d'. This means <code>/dev/hdc</code> under
+Linux translates to <code>/dev/hd2</code> under the Hurd. Got it?
+Good. GRUB does it differently! GRUB is doing it like the BIOS and
+enumerates all installed disks it can boot from starting from "0"
+incrementing by 1. So `hd(0,?)' is a partition on the first disk it
+can boot from, regardless if this is a master or slave or
+whatever. The second disk it finds has `hd(1,?)' etc. Luckily, the
+BIOS is searching in the well defined order primary controller
+master/slave, secondary controller master/slave.
+<p>
+Now figure out the partition number. The partition number for DOS
+style partitions is the same under Linux and the Hurd, but the Hurd
+does use BSD style notation with slices. So it is
+<code>/dev/hdc3</code> under Linux, but <code>/dev/hd2s3</code> under
+the Hurd. If you use BSD partitions, you already know what the Hurd
+name for this partition is. GRUB does it, again, differently: It
+starts counting from "0", so <code>/dev/hd0s3</code> is
+<code>hd(0,2)</code> in GRUB, <em>not</em> <code>hd(0,3)</code>!
+
+<p>
+<b>
+Question</b>: How do I add a swap partition?
+<p>
+<b>
+Answer</b>: A swap partition is also called a paging file. Usually, it
+is sufficient to add the swap partition to <code>/etc/fstab</code>
+just as you would under Linux. You can swap to a Linux swap
+partition, and the Hurd will honour the Linux swap signature (both
+versions). But the Hurd will just as happily swap to any other raw
+disk space and overwrite anything it finds, so be careful!
+<p>
+If you want to swap to a file, or make sure that it checks the Linux
+swap signature before, you need to edit
+<code>/boot/servers.boot</code>. The syntax is the partition device
+file name, plus optionally the swap file inside an ext2fs partition,
+followed by a space and then one of
+<code>$(add-raw-paging-file)</code>,
+<code>$(add-linux-paging-file)</code>,
+<code>$(add-paging-file)</code>. The first works with any
+partition/file and does not honour any swap sigature or other
+data. The second has a safety check and only works if a Linux swap
+signature can be found. The third looks for a swap signature first and
+falls back to raw paging if it couldn't find one. This is also the
+default for entries in <code>/etc/fstab</code>.
-<p><b>Question</b>:
-What is my partition name/number?</p>
-<p><b>Answer</b>:
-I knew you would ask this. If I had to reduce this FAQ to only one question,
-I'd choose this one. It is pretty easy, but you have to know that there are
-actually three naming convention we face here.</p>
-<p>
-All naming conventions use <code>hd</code> for IDE and <code>sd</code> for
-SCSI disks. So far the commonalities. Now for the differences.</p>
-<p>
-First, figure out the disk number. If it is a SCSI disk, you need to know
-the SCSI disk number. If it is an IDE disk, you need to know on which
-controller it is and if it is a master or slave. For Linux, the master
-disks on the primary controller has the letter "a", the slave
-on the same controller the letter "b". Master and slave on the secondary
-controller have the letters "c" and "d" respectively. The Hurd does use BSD
-style notation and does use "0", "1", "2" and "3" instead "a", "b", "c" and
-"d". So it is <code>/dev/hdc</code> under Linux, but <code>/dev/hd2</code>
-under the Hurd. Got it? Good. GRUB does it differently! GRUB is doing it
-like the BIOS and enumerates all installed disks it can boot from starting
-from "0" incrementing by 1. So "hd(0,?)" is a partition on the first disk it
-can boot from, regardless if this is a master or slave or whatever. The
-second disk it finds has "hd(1,?)" etc. Luckily, the BIOS is searching in the well
-defined order primary controller master/slave, secondary controller
-master/slave.</p>
-<p>
-Now figure out the partition number. The partition number for DOS style
-partitions is the same under Linux and the Hurd, but the Hurd does use BSD
-style notation with slices. So it is <code>/dev/hdc3</code> under Linux, but
-<code>/dev/hd2s3</code> under the Hurd. If you use BSD partitions, you
-already know what the Hurd name for this partition is. GRUB does it, again,
-differently: It starts counting from "0", so <code>/dev/hd0s3</code> is
-<code>hd(0,2)</code> in GRUB, <em>not</em> <code>hd(0,3)</code>!</p>
-
-<p><b>Question</b>:
-How do I add a swap partition?</p>
-<p><b>Answer</b>:
-A swap partition is also called a paging file. Usually, it is sufficient to
-add the swap partition to <tt>/etc/fstab</tt> just as you would under Linux.
-You can swap to a Linux swap partition, and the Hurd will honour the Linux
-swap signature (both versions). But the Hurd will just as happily swap to
-any other raw disk space and overwrite anything it finds, so be careful!
-</p>
-<p>If you want to swap to a file, or make sure that it checks the Linux swap
-signature before, you need to edit <tt>/boot/servers.boot</tt>. The syntax
-is the partition device file name, plus optionally the swap file inside an
-ext2fs, followed by a space and then one of
-<tt>$(add-raw-paging-file)</tt>, </tt>$(add-linux-paging-file)</tt>,
-<tt>$(add-paging-file)</tt>. The first works with any partition/file and
-does not honour any swap sigature or other data. The second has a safety
-check and only works if a Linux swap signature can be found. The third looks
-for a swap signature first and falls back to raw paging if it couldn't find
-one. This is also the default for entries in <tt>/etc/fstab</tt>.
-</p>
-
-<p><b>Question</b>:
-I get <code>Operation not permitted</code> error at installation time!</p>
-<p><b>Answer</b>:
-You forgot to set the file system owner of the Hurd partition to
-<code>hurd</code>. The Hurd does use additional information in inodes to set
-translators, to make this work the partition must be marked as "owned by the
-Hurd". You can do this with <code>mke2fs -o hurd /dev/XXX</code> when
-creating the partition or afterwards using the <code>e2os</code> script.</p>
+<p>
+<b>
+Question</b>: I get <code>Operation not permitted</code> error at
+installation time!
+<p>
+<b>
+Answer</b>: You forgot to set the file system owner of the Hurd
+partition to <code>hurd</code>. The Hurd does use additional
+information in inodes to set translators, to make this work the
+partition must be marked as "owned by the Hurd". You can do this with
+<code>mke2fs -o hurd /dev/XXX</code> when creating the partition or
+afterwards using the <code>e2os</code> script.
-<p><b>Question</b>:
-What does the following error mean?
+<p>
+<b>
+Question</b>: What does the following error mean?
<pre>
/hurd/ext2fs.static: cannot vm_map whole disk: (os/kern) no space available
-</pre></p>
-<p><b>Answer</b>:
-It means that your partition is bigger than 1 GB. Such big partitions are
-currently not supported, sorry.</p>
-
-<p><b>Question</b>:
-After <code>native-install</code> finished, I had to write tthhiiss wwaayy.
-In particular I had to type <code>rreebboooott</code> to reboot.
-<p><b>Answer</b>:
-Funny, isn't it? Somehow two <code>term</code> server got started and are
-sharing the keyboard input among each other. After a reboot, you will not
-notive this problem any more. There is currently no known solution, but we
-are keeping an eye on it. If <code>tar</code> would support translator, we
-would not have this problem...</p>
-
-<p><b>Question</b>:
-Why is <code>/usr</code> a symbolic link to <code>.</code>?</p>
-<p><b>Answer</b>:
-The distinction between <code>/</code> and <code>/usr</code> has historical
-reasons, back when Unix systems were booted from two tapes, a small root
-tapes an big user tape. Today, we like to use different partitions for these
-two spaces. The Hurd throws this historical garbage away, as we think that
-we have found a more flexible solution, shadow filesystems. Unfortunately,
-shadowfs is not yet implemented.</P>
-
-<p><b>Question</b>:
-How do I set up my network card? It was autodetected by GNU Mach.</p>
-<p><b>Answer</b>:
-<code>settrans -fgc /servers/socket/2 /hurd/pfinet --interface=eth0
---address=AA.BB.CC.DD --netmask=EE.FF.GG.HH --gateway=II.JJ.KK.LL</code>
-where the various <code>WW.XX.YY.ZZ</code> are your IP number, your netmask
-and your gateway address respectively. Also don't forget to set up
-<code>/etc/resolv.conf</code>, <code>/etc/hosts</code> and so on.</p>
-
-<p><b>Question</b>:
-Pipes don't work!</p>
-<p><b>Answer</b>:
-<code>settrans -fgc /servers/socket/1 /hurd/pflocal</code> will help
-you.</p>
-
-<p><b>Question</b>:
-When the APM support in the BIOS spins down my disk drives, the Hurd is
-unable to wake up!</p>
-<p><b>Answer</b>:
-APM is not supported in the current version of GNU Mach, sorry. Please
-disable APM in your BIOS setup.</p>
-
-<p><b>Question</b>:
-What about X?
-<p><b>Answer</b>:
-Don't ask.</p>
-
-<p><b>Question</b>:
-Why?
-<p><b>Answer</b>:
-The problem is not X, most of X is ported. The complete X distribution
-compiles and the programs run. Even the server seem to run just fine.
-However, we need to port the Linux character devices to GNU Mach, so we have
-a fancy keyboard server and PS/2 mouse support etc. Until then, the servers
-are not useful. But you can run the clients with a remote display.</p>
-
-<p><b>Question</b>:
-My X clients won't work!
-<p><b>Answer</b>:
-Try <code>export LD_LIBRARY_PATH=/usr/X11R6</code>. This is a linker issue.
-The Hurd systems wants to use <code>RPATH</code>, and Debian does avoid
-<code>RPATH</code>. Sorry, there is no solution for this currently but
-setting <code>LD_LIBRARY_PATH</code> to a list of all libraries in unusual
-places.</p>
-
-
-<h3>Using the Hurd</h3>
-
-<p><b>Question</b>:
-What's a translator?</p>
-<p><b>Answer</b>:
-There is a <a href="hurd-doc-translator">text about translators</a> available.
-</p>
-
-<p><b>Question</b>:
-How can I pass options to serverboot from the GRUB command line?</p>
-<p><b>Answer</b>:
-Just give them to the kernel and it will pass them down to serverboot.
-</p>
-
-<p><b>Question</b>:
-Can I use the Linux version of <code>e2fsck</code> on my Hurd partition?</p>
-<p><b>Answer</b>:
-Yes, you can since <code>e2fsprogs-1.05</code>. Check with <code>e2fsck
--V</code> first.</p>
-
-<p><b>Question</b>:
-<code>ps aux</code> does not give the output I'd expect.</p>
-<p><b>Answer</b>:
-Try <code>ps Aux</code>.</p>
-
-<p><b>Question</b>:
-Whenever I do a <code>ls -l /dev/</code>, it shows <code>fd: Gratuitous
-error</code>. What is happening?</p>
-<p><b>Answer</b>:
-The <code>magic</code> server has no support for the filesystem operations
-in questions. Ideally, it would act like a directory (probably an empty
-one), and that needs to be implemented. For now, you can safely ignore the
-error message, it is not harmful. For more information, see also the
-information on the <a href="hurd-doc-server#magic"><code>magic</code>
-server</a>.</p>
-
-<p><b>Question</b>:
-Where is ...</p>
-<p><b>Answer</b>:
-<ul><li><code>fdisk</code>, <code>dmesg</code> are not yet ported.</li>
-<li>instead <code>free</code>, use <code>vmstat</code> and <code>vminfo</code>
-</ul></p>
-
-<p><b>Question</b>:
-Is there a <code>/proc</code> filesystem?</p>
-<p><b>Answer</b>:
-No. Maybe there will be an emulation some day for
-programs that need it. If you wonder about the empty <code>/proc</code>
+</pre>
+<p>
+<b>
+Answer</b>: It means that your partition is bigger than 1 GB. Such big
+partitions are currently not supported, sorry.
+
+<p>
+<b>
+Question</b>: After <code>native-install</code> finished, I had to
+write tthhiiss wwaayy. In particular I had to type
+<code>rreebboooott</code> to reboot.
+<p>
+<b>
+Answer</b>: Funny, isn't it? In addition to the rescue
+<code>term</code> server in <code>/tmp/console</code>, another
+<code>term</code> server got started and is clobbing the keyboard
+input. After a reboot this problem vanishes, because only one
+<code>term</code> server will remain. There is currently no known
+clean solution, but we are keeping an eye on it. If <code>tar</code>
+would support translator, we would not have this problem... Even if
+you don't experience this problem right after the installation, reboot
+immediately so you don't hit this bug by accident.
+
+<p>
+<b>
+Question</b>: Why is <code>/usr</code> a symbolic link to
+<code>.</code>?
+<p>
+<b>
+Answer</b>: The distinction between <code>/</code> and
+<code>/usr</code> has historical reasons, back when Unix systems were
+booted from two tapes, a small root tapes and a big user tape. Today,
+we like to use different partitions for these two spaces. The Hurd
+throws this historical garbage away. We think that we have found a
+more flexible solution called shadow filesystems. Unfortunately,
+support for shadowed filesystems is not yet implemented.
+
+<p>
+<b>
+Question</b>: How do I set up my network card? It was autodetected by
+GNU Mach.
+<p>
+I don't have any network card, how do I set up a loopback only network?
+<p>
+<b>
+Answer</b>: Setup the <a href="hurd-doc-server"><code>pfinet</code></a>
+server. Also don't forget to set up <code>/etc/resolv.conf</code>,
+<code>/etc/hosts</code> and so on.
+<p>
+Of course, you only need to do this if the installation routine didn't do it
+for you.
+
+<p>
+<b>
+Question</b>: Pipes don't work!
+<p>
+<b>
+Answer</b>: <code>settrans -fgc /servers/socket/1 /hurd/pflocal</code>
+will help you.
+
+<p>
+<b>
+Question</b>: When the APM support in the BIOS spins down my disk
+drives, the Hurd is unable to wake up!
+<p>
+<b>
+Answer</b>: APM is not supported in the current version of GNU Mach,
+sorry. Please disable APM in your BIOS setup.
+
+<p>
+<b>
+Question</b>: What about X?
+<p>
+<b>
+Answer</b>: It works! The packages are available at
+href="ftp://alpha.gnu.org/gnu/hurd/debian";>the GNU alpha FTP server</a>.
+Instructions are in the mailing list archive (link follows later).
+
+<p>
+<b>
+Question</b>: My X won't work!
+<p>
+<b>
+Answer</b>: Try <code>export LD_LIBRARY_PATH=/usr/X11R6</code>. This
+is a linker issue. The Hurd systems wants to use <code>RPATH</code>,
+and Debian does avoid <code>RPATH</code>.
+
+<h3>
+Using the Hurd</h3>
+
+<p>
+<b>
+Question</b>: What's a translator?
+<p>
+<b>
+Answer</b>: There is a <a href="hurd-doc-translator">text about
+translators</a> available. Read this and ask further questions on the
+mailing list.
+
+<p>
+<b>
+Question</b>: Why can I <code>read()</code> a directory?
+<p>
+<b>
+Answer</b>: It is important to understand that there is nothing
+special about a directory under the Hurd, it is just another
+file. This fits in the translator concept where a translator can
+appear as a directory but provide a file, too.
+
+<p>
+<b>
+Question</b>: How can I pass options to <code>serverboot</code> from
+the GRUB command line?
+<p>
+<b>
+Answer</b>: Just give them to the kernel and it will pass them down to
+<code>serverboot</code>.
+
+<p>
+<b>
+Question</b>: Can I use the Linux version of <code>e2fsck</code> on my
+Hurd partition?
+<p>
+<b>
+Answer</b>: Yes, you can since <code>e2fsprogs-1.05</code>. Check with
+<code>e2fsck -V</code> first.
+
+<p>
+<b>
+Question</b>: <code>ps aux</code> does not give the output I'd
+expected.
+<p>
+<b>
+Answer</b>: Try <code>ps Aux</code>.
+
+<p>
+<b>
+Question</b>: What are these strange pids 2 and 3?
+<p>
+<b>
+Answer</b>: 2 is the kernel, 3 is the default pager. 4 is the root
+filesystem.
+
+<p>
+<b>
+Question</b>: Where is ...
+<p>
+<b>
+Answer</b>:
+<ul>
+<li>
+<code>fdisk</code>, <code>dmesg</code> are not yet ported.</li>
+<li>
+Instead <code>free</code>, use <code>vmstat</code> and
+<code>vminfo</code>.</li></ul>
+
+<p>
+<b>
+Question</b>: Is there a <code>/proc</code> filesystem?
+<p>
+<b>
+Answer</b>: No. Maybe there will be an emulation some day for programs
+that need it. If you wonder about the empty <code>/proc</code>
directory, that is a relict from a Debian GNU/Linux package
-(<tt>base-files</tt>).</p>
+(<code>base-files</code>). You can probe for existing hardware devices with
+the <a href="hurd-doc-utils#devprobe">devprobe</a> utility.
+<p>
+<b>
+Question</b>: What is this login shell?
+<p>
+<b>
+Answer</b>: The Hurd has the concept of the not-logged in user. It is
+the user without any uids. This concept stems from the fact that the
+Hurd supports uid sets, and one possibility to take care of is the
+empty set. Instead just denying access in such a case, Hurd
+filesystems offer a forth permission set (rwx), which is used to
+determine the privilegies (the default is to fall back to the
+permission set of the "other" users, though).
+<p>
+The Hurd login shell is a shell running with empty uids and gids. To
+restrict access to your files, either change the fourth permission
+set, or change the login shell of the "login" user in the password
+file to <code>/bin/loginpr</code>, which implements the standard login
+prompt.
<h3>... When Something Breaks</h3>
-<p><b>Question</b>:
-What is a <tt>default pager</tt>, <tt>paging</tt>, or a
-<tt>pager request</tt>?</p>
-<p><b>Answer</b>:
-The default pager handles the virtual memory allocation. If it can't
-allocate a new memory page, because you are out of memory, some terrible
-things may happen. Whenever you get such errors you either need more memory
-or you have found a memory leak. Always add a swap partition.</p>
-
-<p><b>Question</b>:
-What is a <tt>Gratuitous error</tt>?</p>
-<p><b>Answer</b>:
-This is coming from <tt>strerror(EGRATUITOUS)</tt>. If you check glibc's
-documentation, it will say that this error code has no purpose <tt>:)</tt>.
-However, this is not quite true. You only get this when something terrible
-happened. Thomas explains:
+<p>
+<b>
+Question</b>: What is a <code>default pager</code>,
+<code>paging</code>, or a <code>pager request</code>?
+<p>
+<b>
+Answer</b>: The default pager handles the virtual memory
+allocation. If it can't allocate a new memory page because you are out
+of memory, some terrible things may happen. Whenever you get such
+errors you either need more memory or you have found a memory
+leak. Always add a swap partition.
+
+<p>
+<b>
+Question</b>: What is a <code>Gratuitous error</code>?
+<p>
+<b>
+Answer</b>: This is coming from <code>strerror(EGRATUITOUS)</code>. If
+you check <code>glibc</code>'s documentation, it will say that this
+error code has no purpose <code>:)</code>. However, this is not quite
+true. You only get this when something terrible happened. Thomas
+explains:
<blockquote>
-More precisely EGRATUITOUS officially means that some server has
-responded in an impossible or protocol-violating fashion. There are
-some cases in the Hurd where EGRATUITOUS is returned and probably
-something else should be chosen instead.
+More precisely <code>EGRATUITOUS</code> officially means that some
+server has responded in an impossible or protocol-violating fashion.
+There are some cases in the Hurd where <code>EGRATUITOUS</code> is
+returned and probably something else should be chosen instead.
</blockquote>
If you can reproduce this error message, please report it. But <em>do
-not</em> report this for accessing <tt>/dev/fd</tt>, we already know that.
-</p>
+not</em> report this for accessing <code>/dev/fd</code>, we already know
+that.
-<p><b>Question</b>:
-Why does <code>df</code> not work?</p>
-<p><b>Answer</b>:
-<code>df</code> tries to get a list of all mounted filesystems. This is a
-list that is not available under the Hurd because there is currently no
-central list of all mounted filesystems. You can try <code>df /</code> to
-get the free diskspace on the root filesystem and similar for other
-filesystem, but this doesn't work with some versions of
-<code>fileutils</code> (for example, as time of writing, summer 1999, it
-does not work).</p>
-
-<p><b>Question</b>:
-When something crashes, GNU Mach reboots automatically. But it does it too
-fast, and I can't write the error message.</p>
-<p><b>Answer</b>:
-Give the <code>-H</code> option to init (add it to the boot command line), and
-init will tell Mach to enter the kernel debugger instead to reboot. At the
-debugger prompt, you can type <code>db> reboot</code> any time to reboot the
-system.</p>
+<p>
+<b>
+Question</b>: Why does <code>df</code> not work?
+<p>
+<b>
+Answer</b>: <code>df</code> tries to get a list of all mounted
+filesystems. This is a list that is not available under the Hurd
+because there is currently no central list of all mounted
+filesystems. You can use <code>df /</code> to get the free diskspace
+on the root filesystem and similar for other filesystem (you need at
+least <code>fileutils 4.0-2.1</code> for this feature).
-<p><b>Question</b>:
+<p>
+<b>
+Question</b>: When something crashes, GNU Mach reboots
+automatically. But it does it too fast, and I can't write the error
+message.
+<p>
+<b>
+Answer</b>: Give the <code>-H</code> option to init (add it to the
+boot command line), and <code>init</code> will tell Mach to enter the
+kernel debugger instead to reboot. At the debugger prompt, you can
+type <code>db> reboot</code> any time to reboot the system.
+
<h3>Development</h3>
+
+<p>
+<b>
+Question</b>: Where can I get the source?
+<p>
+<b>
+Answer</b>: You can get the source of all Debian packages on any <a
+href="../../distrib/ftplist">Debian ftp mirror</a>. For GNU Mach and
+the Hurd there is also <a
+href="http://www.gnu.org/software/devel";>anonymous CVS access</a>
+available.
-<p><b>Question</b>:
-Where can I get the source?</p>
-<p><b>Answer</b>:
-You can get the source of all Debian packages on any
-<a href="../../distrib/ftplist">Debian ftp mirror</a>. For GNU Mach and the
-Hurd, there is also
-<a href="http://www.gnu.org/softwrae/devel";>anonymous CVS access</a> available.
-</p>
-
-<p><b>Question</b>:
-Where should I start reading the Hurd source code?</p>
-<p><b>Answer</b>:
-Probably start with the <code>auth</code> server.</p>
-
-<p><b>Question</b>:
-Are there example programs that make use of special Hurd features?</p>
-<p><b>Answer</b>:
-Have a look at the <code>utils/</code> directory in the Hurd source
-tree.</p>
+<p>
+<b>
+Question</b>: Where should I start reading the Hurd source code?
+<p>
+<b>
+Answer</b>: Probably start with the <code>auth</code> server.
+<p>
+<b>
+Question</b>: Are there example programs that make use of special Hurd
+features?
+<p>
+<b>
+Answer</b>: Have a look at the <code>utils/</code> directory in the
+Hurd source tree.
+<p>
+<b>
+Question</b>: <code>ps</code> hangs, and I need to check its output!
+<p>
+<b>
+Answer</b>: Interrupt it and start it with <code>-M</code>.
+++++++++++++++++++++++++++++ END OF english/ports/hurd/hurd-faq.wml
+++++++++++++++++++++++++++++ CHANGES IN english/ports/hurd/hurd-doc.wml
Index: english/ports/hurd/hurd-doc.wml
===================================================================
RCS file: /cvs/webwml/webwml/english/ports/hurd/hurd-doc.wml,v
retrieving revision 1.8
retrieving revision 1.11
diff -u -u -r1.8 -r1.11
--- english/ports/hurd/hurd-doc.wml 1999/08/05 22:22:17 1.8
+++ english/ports/hurd/hurd-doc.wml 2000/04/21 22:26:15 1.11
@@ -8,25 +8,31 @@
[ <a href="hurd-links">Links</a> ]
[ <a href="hurd-contact">Contact</a> ]<p>
-<h1>Debian GNU/Hurd</h1>
-<h2>Documentation</h2>
-<P>
-The existing documentation for the Hurd is not complete, and if you are a
-skilled programmer and writer, you are invited to improve the Hurd reference
-manual or write other documentation covering the Hurd.
-</P>
-<UL>
-<LI><a href="hurd-faq">Frequently Asked Questions</a> and their answers, of course.</li>
-<li>Introduction into <a href="hurd-doc-translator">the translator concept</a>.</li>
-<LI><a href="hurd-port">Porting packages</a> often requires some
-modifications to the upstream software or the Debian packaging scripts.
-</li>
-<LI><A HREF="reference-manual/hurd_toc.html">The Hurd Reference Manual</a>
-in browseable Hypertext format covers both, user and
-developer aspects of the Hurd. It is also available as a <a
+<h1>
+Debian GNU/Hurd</h1>
+<h2>
+Documentation</h2>
+<p>
+The existing documentation for the Hurd is not complete, and if you
+are a skilled programmer and writer, you are invited to improve the
+Hurd reference manual or write other documentation covering the
+Hurd.</p>
+<ul>
+<li>
+<a href="hurd-faq">Frequently Asked Questions</a> and their answers,
+of course.</li>
+<li>
+Introduction to <a href="hurd-doc-translator">the translator
+concept</a>.</li>
+<li>
+<a href="reference-manual/hurd_toc.html">The Hurd Reference Manual</a>
+in browseable Hypertext format covers both, user and developer aspects
+of the Hurd. It is also available as a <a
href="reference-manual/hurd.html">single file</a>.</LI>
-<LI><A HREF="hurd-doc-server">Preliminary User Interface Description</A> has a
-list of the available Hurd servers and their <tt>--help</tt> output.</LI>
-<LI>Sparse information on some <A HREF="hurd-doc-utils">utilities</A>.</LI>
-</UL>
-</P>
+<li>
+<a href="hurd-doc-server">Preliminary User Interface Description</a>
+has a list of the available Hurd servers and their <code>--help</code>
+output.</li>
+<li>
+Sparse information on some <a
+href="hurd-doc-utils">utilities</a>.</li></ul>
+++++++++++++++++++++++++++++ END OF english/ports/hurd/hurd-doc.wml
+++++++++++++++++++++++++++++ CHANGES IN english/ports/hurd/hurd-doc-translator.wml
Index: english/ports/hurd/hurd-doc-translator.wml
===================================================================
RCS file: /cvs/webwml/webwml/english/ports/hurd/hurd-doc-translator.wml,v
retrieving revision 1.3
retrieving revision 1.5
diff -u -u -r1.3 -r1.5
--- english/ports/hurd/hurd-doc-translator.wml 1999/08/05 22:22:17 1.3
+++ english/ports/hurd/hurd-doc-translator.wml 2000/04/21 22:26:15 1.5
@@ -15,9 +15,9 @@
<li><a href="#examples" name="TOC_examples">Examples</a></li>
<li><a href="#actpas" name="TOC_actpas">Passive Translators, Active Translators</a></li>
<li><a href="#manage" name="TOC_manage">Managing Translators</a></li>
-
+</ul>
-<a href="#TOC_concept" name="concept"><h3>Concept</h3></a>
+<h3><a href="#TOC_concept" name="concept">Concept</a></h3>
<p>
Before we take a closer look at translators, let us consider regular
filesystems. A filesystem is store for a hierarchical tree of directories
@@ -73,7 +73,7 @@
<code>ls</code> and at the same time behaves like a file when accessed by
<code>cat</code>.</p>
-<a href="#TOC_examples" name="examples"><h3>Examples</h3></a>
+<h3><a href="#TOC_examples" name="examples">Examples</a></h3>
<h4>Mount Points</h4>
<p>
A mount point can be seen as an inode that has a special translator attached
@@ -96,7 +96,7 @@
Because the Hurd is heavily multi threaded, this is very cheap.</p>
<p>
When hardware is involved, a translator usually starts to communicate with
-the kernel to get the data from the hardware. However, if no hardwrae access
+the kernel to get the data from the hardware. However, if no hardware access
is necessary, the kernel does not need to be involved. For example,
<code>/dev/zero</code> does not require hardware access, and can therefore
be implemented completely in user space.</p>
@@ -120,10 +120,10 @@
filesystem very fast, and add native support for symlinks and other features
later.</p>
-<a href="#TOC_actpas" name="actpas"><h3>Passive Translators, Active Translators</h3></a>
+<h3><a href="#TOC_actpas" name="actpas">Passive Translators, Active Translators</a></h3>
<p>
There are two types of translators, passive and active. They are really
-completely different things, so don't mix them up, but they havea close
+completely different things, so don't mix them up, but they have a close
relation to each other.</p>
<h4>Active Translators</h4>
@@ -134,7 +134,7 @@
command. The <code>-a</code> option is necessary to tell
<code>settrans</code> that you want to modify the active translator.</p>
<p>
-The <code>settrans</code> command takes three kind of options. First, you
+The <code>settrans</code> command takes three kind of arguments. First, you
can set options for the <code>settrans</code> command itself, like
<code>-a</code> to modify the active translator. Then you set the inode you
want to modify. Remember that a translator is always associated with an
@@ -179,18 +179,18 @@
<p>
There is a further difference: active translators can die or get lost. As
soon as the active translator process is killed (for example, because you
-reboot the machine) it is lost forever. Passive translators are transient
+reboot the machine) it is lost forever. Passive translators are not transient
and stay in the inode during reboots until you modify them with the
<code>settrans</code> program or delete the inodes they are attached to.
This means, you don't need to maintain a configuration file with your mount
points.</p>
<p>
-One last point: Even if you have set apassive translator, you can still
+One last point: Even if you have set a passive translator, you can still
set a different active translator. Only if the translator is automatically
started because there was no active translator the time the inode was
accessed the passive translator is considered.</p>
-<a href="#TOC_manage" name="manage"><h3>Managing Translators</h3></a>
+<h3><a href="#TOC_manage" name="manage">Managing Translators</a></h3>
<p>
As mentioned above, you can use
<a href="reference-manual/hurd_7.html#SEC49"><code>settrans</code></a>
@@ -198,7 +198,7 @@
to change the behaviour of <code>settrans</code> in case something goes
wrong, and to conditionalize its action. Here are some common usages:</p>
<ul><li><code>settrans -c /mnt /hurd/ext2fs /dev/hd2s5</code> mounts a
-partition, the translator will stay transient.</li>
+partition, the translator will stay across reboots.</li>
<li><code>settrans -a /mnt /hurd/ext2fs ~/dummy.fs</code> mounts a
filesystem inside a data file, the translator will go away if it dies.</li>
<li><code>settrans -fg /nfs-data</code> forces a translator to go away.</li>
@@ -239,7 +239,7 @@
<p>
You should have some understanding of what is going on now. Now remember
that this was only <em>one</em> special server, the Hurd ext2fs server.
-There are many more server in the <code/hurd</code> directory. Some of them
+There are many more server in the <code>hurd</code> directory. Some of them
are for filesystems. Some are needed for file system features like links.
Some are needed for device files. Some are useful for networking. Imagine
"mounting" an FTP Server with <code>settrans</code> and downloading files
+++++++++++++++++++++++++++++ END OF english/ports/hurd/hurd-doc-translator.wml
+++++++++++++++++++++++++++++ CHANGES IN english/ports/hurd/hurd-links.wml
Index: english/ports/hurd/hurd-links.wml
===================================================================
RCS file: /cvs/webwml/webwml/english/ports/hurd/hurd-links.wml,v
retrieving revision 1.7
retrieving revision 1.15
diff -u -u -r1.7 -r1.15
--- english/ports/hurd/hurd-links.wml 1999/08/05 22:22:17 1.7
+++ english/ports/hurd/hurd-links.wml 2000/08/02 06:57:01 1.15
@@ -8,86 +8,131 @@
[ <b>Links</b> ]
[ <a href="hurd-contact">Contact</a> ]<p>
-<h1>Debian GNU/Hurd</h1>
-<h2>Links</h2>
-<P>
-There are a lot of resources on the web about Debian GNU/Hurd and related
-projects. Please let me know if you find more or some information on this
-page is incorrect. Note that most links on this page point to domains
-outside of Debian, and neither Debian nor SPI nor the author of this web
-page is responsible for the content of those pages.
-</P>
-<P>
-<UL>
-<LI>Debian
- <UL>
- <LI><A HREF="http://www.debian.org";>Debian entry page</A></LI>
- <LI><A HREF="http://www.debian.org/ports/";>Debian Ports</A> to other
- architectures</LI>
- <LI><A HREF="http://www.debian.org/ports/hurd/";>Debian
- GNU/Hurd</A></LI>
- <LI><A HREF="http://www.debian.org/distrib/ftplist";>Debian FTP
- servers</A> to download the Debian software from</LI>
- <LI><A HREF="http://www.debian.org/Lists-Archives";>Debian List
- Archive</A> where you can search and browse the Debian GNU/Hurd
- mailing list</LI>
- </UL>
-<LI>GNU/Hurd
- <UL>
- <LI><A HREF="http://www.gnu.org";>GNU entry page</A></LI>
- <LI><A HREF="http://www.gnu.org/software/hurd/hurd.html";>Official
- Hurd web site</A> by GNU. There are a lot of links on those pages that
- are not duplicated here. Try also the new, but more up to date
- <A HREF="http://www.gnu.org/software/hurdtest/navigation.html";>experimental
- web pages<A/>.</LI>
- <LI><A HREF="http://www.gnu.org/software/devel.html";>GNU Development
- Resources</A> has info about Anonymous CVS access to the Hurd
- software, Mailing Lists, FTP server etc</LI>
- <li><a href="http://www.urbanophile.com/arenn/hacking/hurd/hurd-hardware.html";>Hardware Compatibility Guide</a>
- </li>
- </UL>
-<LI>GRUB
- <UL>
- <LI><A HREF="http://www.uruk.org/grub/";>GRUB</A> homepage, which is
- a boot loader written by Erich Boleyn.</LI>
- <LI> Gordon Matzigkeit and his team are currently putting a lot of
- work in GRUB, please visit the
- <a href="http://www.gnu.org/software/grub/grub.html";>GNU Grub web page</a>.
- There is also a <a href="hurd-contact#bug-grub">mailing list</a> where
- the development of GNU Grub is discussed.</li>
- </UL>
-<LI>Microkernels
- <UL>
- <LI><A HREF="http://www.cs.utah.edu/projects/flexmach/mach4/html/Mach4-proj.html";>Mach 4</A>,
- the Utah release of the Mach, on which GNU Mach is based.</LI>
- <LI><A HREF="http://www.cs.cmu.edu/afs/cs.cmu.edu/project/mach/public/www/mach.html";>CMU
- CS Project Mach Home Page</A>, the origin of Mach. Check it out if
- you are interested in GNU Mach, because it has all the low level
- documentation for kernel hackers.</LI>
- <LI><A HREF="http://www.cs.utah.edu/projects/flexmach/";>Flex</A>,
- the successor of Mach 4</LI>
- <LI><A HREF="http://os.inf.tu-dresden.de/L4/";>L4</A>, a purists
- microkernel</LI>
- <LI><A HREF="http://os.inf.tu-dresden.de/fiasco";>Fiasco</A>, a clone
- of L4</LI>
- </UL>
-<LI>Personal Web Pages
- <UL>
- <LI><A HREF="http://duff.kuicr.kyoto-u.ac.jp/~okuji/";>OKUJI
- Yoshinori</A> is working on GRUB and GNU Mach, and has some
- interesting links about Microkernels on his web page (among
- other stuff).</LI>
- <LI><A HREF="http://f77.nop.or.jp/";>UCHIYAMA Yasushi</A> got X Free
- 86 running on the Hurd and worked on SMP support for GNU Mach.</LI>
- <LI><A HREF="http://www.lares.dti.ne.jp/~jargon/";>YAMASHITA</A> works
- on Japanese documentation for the Hurd, both translations of
- existing documents and new documentation.</LI>
- <LI><A HREF="http://www.cs.pdx.edu/~trent/";>Trent Fisher</A>. His
- pages are a must to read if
- you are interested in Hurd history. Trent has some interesting links
- to historical Hurd announcement and discussion mail. Although you
- can find most of these stuff directly from the official web pages,
- there are some gems hidden that are worth digging out.</LI>
- </UL>
-</UL>
-</P>
+<h1>
+Debian GNU/Hurd</h1>
+<h2>
+Links</h2>
+<p>
+There are a lot of resources on the web about Debian GNU/Hurd and
+related projects. Please let me know if you find more or some
+information on this page is incorrect. Note that most links on this
+page point to domains outside of Debian, and neither Debian nor SPI
+nor the author of this web page is responsible for the content of
+those pages.</p>
+<p>
+<ul>
+<li>
+Debian
+
+<ul>
+<li>
+<a href="http://www.debian.org";>Debian entry page</a></li>
+<li>
+<a href="http://www.debian.org/ports/";>Debian Ports</a> to other
+architectures</li>
+<li>
+<a href="http://www.debian.org/ports/hurd/";>Debian GNU/Hurd</a></li>
+<li>
+<a href="http://www.debian.org/distrib/ftplist";>Debian FTP servers</a>
+to download the Debian software from</li>
+<li>
+<a href="http://lists.debian.org/";>Debian List Archive</a>
+where you can search and browse the Debian GNU/Hurd mailing
+list</li></ul>
+
+<li>
+GNU/Hurd
+
+<ul>
+<li>
+<a href="http://www.gnu.org";>GNU entry page</a></li>
+<li>
+<a href="http://www.gnu.org/software/hurd/hurd.html";>Official Hurd web
+site</a> by GNU. There are a lot of links on those pages that are not
+duplicated here.
+<li>
+<a href="http://www.gnu.org/software/devel.html";>GNU Development
+Resources</a> has info about Anonymous CVS access to the Hurd
+software, Mailing Lists, FTP server etc.
+<li>
+<a href="http://www.urbanophile.com/arenn/hacking/hurd/hurd-hardware.html";>Hardware Compatibility Guide</a></li></ul>
+
+<li>
+GRUB
+
+<ul>
+<li>
+<a href="http://www.uruk.org/grub/";>GRUB</a> homepage, which is a boot
+loader written by Erich Boleyn.</li>
+<li>
+Gordon Matzigkeit, OKUJI Yoshinori and their team are currently
+putting a lot of work in GRUB, please visit the <a
+href="http://www.gnu.org/software/grub/grub.html";>GNU Grub web
+page</a>. There is also a <a href="hurd-contact#bug-grub">mailing
+list</a> where the development of GNU Grub is discussed.</li>
+</ul>
+
+<li>
+Microkernels
+
+<ul>
+<li>
+<a
+href="http://www.cs.utah.edu/projects/flexmach/mach4/html/Mach4-proj.html";>Mach
+4</a>, the Utah release of the Mach, on which GNU Mach is based.</li>
+<li>
+<a
+href="http://www.cs.cmu.edu/afs/cs.cmu.edu/project/mach/public/www/mach.html";>CMU
+CS Project Mach Home Page</A>, the origin of Mach. Check it out if you
+are interested in GNU Mach, because it has all the low level
+documentation for kernel hackers.</li>
+<li>
+<a href="http://www.cs.utah.edu/flux/";>Flux</a>, another microkernel.</li>
+<li>
+<a href="http://www.cs.utah.edu/flux/oskit";>OSKit</a>, a hardware
+abstraction layer complete with many device drivers by the Flux
+project.</li>
+<li>
+<a href="http://www.cs.utah.edu/projects/flexmach/";>Flex</a>, the
+successor of Mach 4</li>
+<li>
+<a href="http://os.inf.tu-dresden.de/L4/";>L4</a>, a purists
+microkernel</li>
+<li>
+<a href="http://os.inf.tu-dresden.de/fiasco";>Fiasco</A>, a clone
+of L4</li>
+<li>
+<a href="ftp://ftp.cse.ucsc.edu/pub/comp.os.research/93/93-03-14-17-09.47.gz";>
+Archive</a> of the comp.os.research news group and their
+<a href="http://www.best.com/~bos/os-faq/FAQ-1.html";>FAQ</a>.
+</ul>
+
+<li>
+Personal Web Pages
+<ul>
+<li>
+<a href="http://hurd.zugzug.com/";>Jeff Bailey</a> runs a webserver on the
+Hurd, so if you want to see the Hurd in action, hit the link and visit him.
+The web server hosts documentation and other information.</li>
+<li>
+<a href="http://duff.kuicr.kyoto-u.ac.jp/~okuji/";>OKUJI
+Yoshinori</a> is working on GRUB and GNU Mach, and has some
+interesting links about Microkernels on his web page (among other
+stuff).</li>
+<li>
+<a href="http://f77.nop.or.jp/";>UCHIYAMA Yasushi</a> got X Free 86
+running on the Hurd and worked on SMP support for GNU Mach.</li>
+<li>
+<a href="http://www.lares.dti.ne.jp/~jargon/";>YAMASHITA</a> works on
+Japanese documentation for the Hurd, both translations of existing
+documents and new documentation.</li>
+<li>
+<a href="http://www.cs.pdx.edu/~trent/gnu/hurd/";>Trent</a> has some
+ancient, but interesting stuff on the Hurd.</li>
+<li>
+<a href="http://www.tamacom.com/tour/hurd/index.html";>A browseable web
+interface</a> to the Hurd source tree. You can look search for functions,
+for example.
+</ul>
+</ul>
+</p>
+++++++++++++++++++++++++++++ END OF english/ports/hurd/hurd-links.wml
+++++++++++++++++++++++++++++ CHANGES IN english/ports/hurd/hurd-news.wml
Index: english/ports/hurd/hurd-news.wml
===================================================================
RCS file: /cvs/webwml/webwml/english/ports/hurd/hurd-news.wml,v
retrieving revision 1.4
retrieving revision 1.7
diff -u -u -r1.4 -r1.7
--- english/ports/hurd/hurd-news.wml 1999/08/05 22:22:17 1.4
+++ english/ports/hurd/hurd-news.wml 2000/01/07 17:59:21 1.7
@@ -8,30 +8,78 @@
[ <a href="hurd-links">Links</a> ]
[ <a href="hurd-contact">Contact</a> ]<p>
-<h1>Debian GNU/Hurd</h1>
-<h2>News</h2>
-<h3>5 Aug 1999</h3>
+<h1>
+Debian GNU/Hurd</h1>
+<h2>
+News</h2>
+<h3>
+1 Nov 1999</h3>
<p>
-Source NMU for <code>passwd</code> (<code>shadow</code>) should fix all
-remaining problems in this package. This should make for a smoother install.</p>
+Cleaned up some outstanding bug reports which were closed by now. Going to
+upload some more packages, in addition to those uploaded in the last days
+(inetutils, grub, man-db, now coming hostname, mtools, ...). All those now
+compile without any changes, which is a good thing. Seems we are slowly
+stabilizing the basic set of packages.</p>
+<h3>
+29 Sep 1999</h3>
+<p>
+There are <a
+href="ftp://alpha.gnu.org/gnu/hurd/contrib/marcus/";>patches to glue
+Linux character devices into GNU Mach</a> now. These patches are very
+experimental, and the tty driver does not work correctly with the term
+translator, but we are working on it and hope to be able to provide a
+binary soon. Note that this will bring the Linux console to the Hurd
+(including color and virtual consoles), as well as drivers for various
+non standard mice and other serial devices.</p>
+<p>
+I heard that some people are concerned about the size of GNU Mach, as
+well as it becoming a subset of Linux. Please note that we are only
+searching for a temporary solution here, until we have the time to
+redesign the driver interface in GNU Mach (or use another
+Microkernel). The microkernel is not at all that important as the Hurd
+servers are which run on top of it.</p>
+<p>
+On the package side, we have now a proper <code>shadow</code> package
+(which produces <code>passwd</code> (thanks, BenC!). Also,
+<code>man-db</code> should work out of the box now even with long
+filenames, but I haven't checked the other changes. All in all, the
+base section is getting into a good shape. Torin has applied my patch
+for <code>perl</code>, and that's another package I have to check out
+if it can be `finalized' now.</p>
+
+<h3>
+31 Aug 1999</h3>
+<p>
+<code>debianutils 1.12</code> does now compile without patch.</p>
+
+<h3>
+5 Aug 1999</h3>
+<p>
+Source NMU for <code>passwd</code> (<code>shadow</code>) should fix
+all remaining problems in this package. This should make for a
+smoother install. On the other side, <code>mutt</code> requires a
+small patch.</p>
-<h3>27 Jul 1999</h3>
+<h3>
+27 Jul 1999</h3>
<p>
-New packages of the core system are finished now. The Hurd has a new way to
-boot (the part that happens after init is started), take a look at
-<code>/libexec/runsystem</code>. This is useful for the
-<code>sysvinit</code> package, which is almost done. Fixed a buglet in GNU
-Lib C and one in GNU Mach. Autodetection of all network cards should work
-now, but maybe we need to tweak the order a bit (3c5x9 before 3c59x).</p>
+New packages of the core system are finished now. The Hurd has a new
+way to boot (the part that happens after init is started), take a look
+at <code>/libexec/runsystem</code>. This is useful for the
+<code>sysvinit</code> package, which is almost done. Fixed a buglet in
+GNU Lib C and one in GNU Mach. Autodetection of all network cards
+should work now, but maybe we need to tweak the order a bit (3c5x9
+before 3c59x).</p>
-<h3>22 Jul 1999</h3>
+<h3>
+22 Jul 1999</h3>
<p>
-<code>cpio 2.4.2-25</code> fixes the remaining Hurd compatibilty issue and
-can now be compiled without changes. Thanks Brian!</p>
+<code>cpio 2.4.2-25</code> fixes the remaining Hurd compatibilty issue
+and can now be compiled without changes. Thanks Brian!</p>
-<h3>5 Jul 1999</h3>
-<P>
-Perl 5.005.03 patches submitted to the maintainer. The upstream code was
-already clean (thanks, Mark!), but the Debian packaging scripts were linux
-specific.
-</P>
+<h3>
+5 Jul 1999</h3>
+<p>
+Perl 5.005.03 patches submitted to the maintainer. The upstream code
+was already clean (thanks, Mark!), but the Debian packaging scripts
+were linux specific.</p>
+++++++++++++++++++++++++++++ END OF english/ports/hurd/hurd-news.wml
Reply to: