🚀 go-pugleaf

Hi,

Is there a hurd mailing list? newsgroups? www home page?

I volunteer if someone wants a proofreader of documentation
being written for hurd.

Some questions:

0) Is hurd mimicking unix to a very large extent or not?
   Is the goal to be a better unix?
   a better free unix?
   how will it compare to other free unix systems?
   I have read the faq a long time ago, but it was too
   technical for me to understand.
1) When hurd is released,
   are features that have not been implemented yet
   going to have documentation but a "Sorry that has not been
   implemented yet" message will be given or will they not be discussed
   publicly until a future release of hurd?
2) What is the philosophy
   of the first release going to be?
3) Is the release cycle
   going to be sort of like the gcc release cycle
   (*.*.0 release followed by *.*.1 and *.*.2 within
   a few months?)? Can one have hurd release n
   and hurd release n+1 both on a machine and if release n+1
   has a bug, then one can switch to release n?
   How hard will it be to upgrade from release n to n+1?

I just finished the "Unix Hater's Handbook" and it brings
out a number of faults of Unix. I was wondering
how hurd will stand up to some of the following questions:

4) Is is easier than unix for a system administrator to maintain?
5) Will it use sendmail or something better? (Better
   means less configurable and/or more stable)
6) Will it use unix-like configuration scripts where
   tabs mean one thing, spaces mean another and
   adding a blank line to the script makes everything
   screwed up?
7) Does one have to partition the hard drive like unix?
   Does it use inodes?
8) Can one use several small drives together as a big drive?
9) Is the file system going to be fast? The book claims that
   there are other systems with file systems considerably
   faster then unix (even much faster than the so-called
   fast file system).
10) Is security going to be a higher priority with hurd than unix?
11) Will the harddrive be in a consistent state at all times
    so that hurd will recover gracefully after a power loss
    or will it use the partially successful fsck method?
12) Will hurd give one a way to ask if you really meant
    to say 'rm *'? How about other common stupid mistakes
    a unix person might do?
13) Are there going to be lots of comments in the hurd source code?
14) Will hurd eventually handle video display terminals?
    Will it use (supposedly slow) curses or something new?
15) Will hurd use suid? This can be a security hole?
16) How are locked files handeled?
17) Is it going to have garbage collection? What happens
    if there is a memory leak in hurd? Murphy's law says
    that it will happen sooner or later.
18) Is hurd going to be able to be run on parallel processors,
    handle concurrency, handle threads, handle <your favorite
    computer science term goes here>?
19) Which languages will be supported on hurd? C and C++
    to start?
20) Which hardware is being used most of the time when hurd
    is being developed? I know that this should not matter,
    but Murphy's law says that it probably will in the early stages.
21) Will the first release of hurd run X?
22) What is the plan for documentation of hurd? Is it being worked
    on now? Will the first release wait for a good document
    on hurd to exist? Is there going to be a documentless
    release?
infinity) How will hurd address some of the other more serious
   complaints of the unix hater's handbook? unix newsgroups?

Mark Stankus