diff options
-rw-r--r-- | faq/0-still_useful.mdwn | 16 | ||||
-rw-r--r-- | faq/old/old_faq.txt | 26 | ||||
-rw-r--r-- | faq/old/old_hurd_faq.txt | 63 | ||||
-rw-r--r-- | faq/support/2_gib_partition_limit.mdwn | 2 |
4 files changed, 15 insertions, 92 deletions
diff --git a/faq/0-still_useful.mdwn b/faq/0-still_useful.mdwn index d98f98ed..96ea6f32 100644 --- a/faq/0-still_useful.mdwn +++ b/faq/0-still_useful.mdwn @@ -8,10 +8,20 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] -[[!meta title="Why is the Hurd useful?"]] +[[!meta title="What are the advantages with the Hurd over Linux/BSD?"]] -What are the advantages with the Hurd over Linux? (In general of course, nothing -in depth) +The Hurd will be considerably more flexible and robust +than generic Unix. Wherever possible, Unix kernel features have been +moved into unprivileged space. Once there, anyone who desires can +develop custom replacements for them. Users will be able to write and +use their own file systems, their own `exec' servers, or their own +network protocols if they like, all without disturbing other users. + +The Linux kernel has now been modified to allow user-level file +systems, so there is proof that people will actually use features such +as these. It will be much easier to do under the Hurd, however, +because the Hurd is almost entirely run in user space and because the +various servers are designed for this sort of modification. > Notably, flexibility for the user: > diff --git a/faq/old/old_faq.txt b/faq/old/old_faq.txt index 24127462..f6a4204b 100644 --- a/faq/old/old_faq.txt +++ b/faq/old/old_faq.txt @@ -85,11 +85,6 @@ partition on the first drive detected by the BIOS (or the second partition with GRUB 1). As Grub now has tab completion, there is not a lot of guess work. -?? Can I use partitions larger than 2GB? - -{ST} Yes. Disk drivers however currently do not support more than 2^32 sectors, i.e. -2TiB. - ?? How much swap do I need? {ST} The usual rule of thumb applies: the same amount as RAM, for instance. @@ -269,16 +264,6 @@ hung, it will not be able respond to its message port and thus, ps will wait forever. The `-M' option instructs ps to not gather information that would require use of the message port. -?? Where are ... - -{MB} `dmesg' is not available. You can read `/var/log/dmesg` instead. - -?? Why does the command `df' not work? - -{NHW} It does, you just have to tell it what filesystem to query. E.g. - - # df / - ?? Why are my translators dying? {NHW} Try passing the `-ap' flag to settrans. By default, settrans only @@ -364,12 +349,6 @@ reboot the system. ? Porting -?? What programs have been ported? - -{NHW} A lot, take a look at the Debian archive. Many programs, however, -do not necessarily need to be ported; they have just never been -compiled. - ?? Is porting easy? {NHW} Porting applications to GNU/Hurd is relatively easy assuming the @@ -382,11 +361,6 @@ thousand, however, on GNU/Hurd, there is no maximum and thus, this is not set. The correct thing to do is to submit a patch to the upstream author that allocates memory dynamically. -?? How can I help? - -{ST} Please see the contributing page: -http://www.gnu.org/software/hurd/contributing.html - ? Compiling ?? Where can I get the source? diff --git a/faq/old/old_hurd_faq.txt b/faq/old/old_hurd_faq.txt index 4ebe019b..20b4c260 100644 --- a/faq/old/old_hurd_faq.txt +++ b/faq/old/old_hurd_faq.txt @@ -16,73 +16,10 @@ Original Document by: Derek Upham <upham@cs.ubc.ca> Contents: -Q0. Where can I get the Unofficial GNU Hurd FAQ? -Q2. Where can I get a copy? -Q3. Why bother writing a new OS when we have Linux and 386/BSD? Q4. What's all this about Mach 3.0 (and Mach 4.0)? -Q5. Where can I find more information? -Q7. What sort of machines will run Hurd in the future? -Q8. What is the current development status? -Q9. What sort of system would we have if the Hurd was bootable today? ============================== -Q0. Where can I get the Unofficial GNU Hurd FAQ? - -The Unofficial Hurd FAQ (what you are reading now) is occasionally -posted to the USENET newsgroup, gnu.misc.discuss. It is also -available from - - http://www.enci.ucalgary.ca/~gord/hurd/hurd-faq.txt (Broken Link ?) - -If you don't have WWW access, you may send mail to me, Gordon -Matzigkeit <gord@enci.ucalgary.ca> with a subject line that reads: - - Subject: send hurd-faq - -You should receive a PGP-signed copy of the current version of this -document in a matter of minutes. - - -Q2. Where can I get a copy? - -To put it simply, you can't. It is still under development (by -Michael Bushnell, Roland McGrath and Miles Bader). It is almost, but -not quite, at the point where you can do real work on it. Keep your -fingers crossed. - -Some people have actually bootstrapped it, but the work is not easy, -and the current snapshot won't work until a new multiserver boot -mechanism is made. - -If you *really* want to try it, beware that it is still pre-alpha -code, and that it will likely crash on you. See Trent Fisher's Hurd -pages (under question 5) for the latest information. - - -Q3. Why bother writing a new OS when we have Linux and 386/BSD? - -For one thing, Linux and BSD don't scale well. Hardware designers are -shifting more and more toward multiprocessor machines for performance, -and standard Unix kernels do not provide much multiprocessor support. -The Hurd, on the other hand, runs on top of the Mach 3.0 micro-kernel -[[1]] from CMU. Mach was designed precisely for multiprocessing -machines, so its portability should carry over nicely to the Hurd. - -In addition, the Hurd will be considerably more flexible and robust -than generic Unix. Wherever possible, Unix kernel features have been -moved into unprivileged space. Once there, anyone who desires can -develop custom replacements for them. Users will be able to write and -use their own file systems, their own `exec' servers, or their own -network protocols if they like, all without disturbing other users. - -The Linux kernel has now been modified to allow user-level file -systems, so there is proof that people will actually use features such -as these. It will be much easier to do under the Hurd, however, -because the Hurd is almost entirely run in user space and because the -various servers are designed for this sort of modification. - - Q4. What's all this about Mach 3.0 (and Mach 4.0)? As mentioned above, Mach is a micro-kernel, written at Carnegie Mellon diff --git a/faq/support/2_gib_partition_limit.mdwn b/faq/support/2_gib_partition_limit.mdwn index 726605f9..3315cc08 100644 --- a/faq/support/2_gib_partition_limit.mdwn +++ b/faq/support/2_gib_partition_limit.mdwn @@ -11,3 +11,5 @@ is included in the section entitled [[!meta title="Is there still a 2 GiB Partition Limit ?"]] The 2 GiB limit has been removed in Debian GNU/Hurd. + +Disk drivers however currently do not support more than 2^32 sectors, i.e. 2TiB. |