From 7e4ec33e095c6923fd13c56a9cf6c4083dbd116d Mon Sep 17 00:00:00 2001 From: "Stephen L. Favor" Date: Mon, 11 Jan 1999 14:45:29 +0000 Subject: Initial revision --- hurd-paper.html | 792 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 792 insertions(+) create mode 100644 hurd-paper.html (limited to 'hurd-paper.html') diff --git a/hurd-paper.html b/hurd-paper.html new file mode 100644 index 00000000..e98e5edf --- /dev/null +++ b/hurd-paper.html @@ -0,0 +1,792 @@ + + + +Towards a New Strategy of OS Design + + + +

Towards a New Strategy of OS Design

+ [image of a Hurd Metafont Logo] (jpeg 10k) +(jpeg 20k) +no gifs due to patent problems +

+This article explains why FSF is developing a new operating system named the +Hurd, which will be a foundation of the whole GNU system. +The Hurd is built +on top of CMU's Mach 3.0 kernel and uses Mach's virtual memory management and +message-passing facilities. +The GNU C Library will provide the Unix system +call interface, and will call the Hurd for needed services it can't provide +itself. +The design and implementation of the Hurd is being lead by Michael +Bushnell, with assistance from Richard Stallman, Roland McGrath, +Jan Brittenson, and others. + +

Part 1: A More Usable Approach to OS Design

+

+The fundamental purpose of an operating system (OS) is to enable a variety of +programs to share a single computer efficiently and productively. +This +demands memory protection, preemptively scheduled timesharing, coordinated +access to I/O peripherals, and other services. +In addition, an OS can allow +several users to share a computer. +In this case, efficiency demands services +that protect users from harming each other, enable them to share without +prior arrangement, and mediate access to physical devices. +

+On today's computer systems, programmers usually implement these goals +through a large program called the kernel. +Since this program must be +accessible to all user programs, it is the natural place to add functionality +to the system. +Since the only model for process interaction is that of +specific, individual services provided by the kernel, no one creates other +places to add functionality. +As time goes by, more and more is added to the +kernel. +

+A traditional system allows users to add components to a kernel only if they +both understand most of it and have a privileged status within the system. +Testing new components requires a much more painful edit-compile-debug cycle +than testing other programs. +It cannot be done while others are using the +system. +Bugs usually cause fatal system crashes, further disrupting others' +use of the system. +The entire kernel is usually non-pageable. +(There are +systems with pageable kernels, but deciding what can be paged is difficult +and error prone. +Usually the mechanisms are complex, making them difficult +to use even when adding simple extensions.) +

+Because of these restrictions, functionality which properly belongs +behind +the wall of a traditional kernel is usually left out of systems unless it is +absolutely mandatory. +Many good ideas, best done with an open/read/write +interface cannot be implemented because of the problems inherent in the +monolithic nature of a traditional system. +Further, even among those with +the endurance to implement new ideas, only those who are privileged users of +their computers can do so. +The software copyright system darkens the mire by +preventing unlicensed people from even reading the kernel source. +

+Some systems have tried to address these difficulties. +Smalltalk-80 and +the Lisp Machine both represented one method of getting around the problem. +System code is not distinguished from user code; all of the system is +accessible to the user and can be changed as need be. +Both systems were +built around languages that facilitated such easy replacement and extension, +and were moderately successful. +But they both were fairly poor at insulating +users and programs from each other, failing one of the principal goals of OS +design. +

+Most projects that use the Mach 3.0 kernel carry on the hard-to-change +tradition of OS design. +The internal structure is different, but the same +heavy barrier between user and system remains. +The single-servers, while +fairly easy to construct, inherit all the deficiencies of the monolithic +kernels. +

+A multi-server divides the kernel functionality up into logical blocks with +well-defined interfaces. +Properly done, it is easier to make changes and add +functionality. +So most multi-server projects do somewhat better. +Much more +of the system is pageable. +You can debug the system more easily. +You can +test new system components without interfering with other users. +But the +wall between user and system remains; no user can cross it without special +privilege. +

+The GNU Hurd, by contrast, is designed to make the area of +system +code as +limited as possible. +Programs are required to communicate only with a few +essential parts of the kernel; the rest of the system is replaceable +dynamically. +Users can use whatever parts of the remainder of the system +they want, and can easily add components themselves for other users to take +advantage of. +No mutual trust need exist in advance for users to use each +other's services, nor does the system become vulnerable by trusting the +services of arbitrary users. +

+This has been done by identifying those system components which users +must +use in order to communicate with each other. +One of these is responsible for +identifying users' identities and is called the + +authentication server. + +In +order to establish each other's identities, programs must communicate, each +with an authentication server they trust. +Another component establishes +control over system components by the superuser, provides global bookkeeping +operations, and is called the + +process server. + +

+Not all user programs need to communicate with the process server; it is only +necessary for programs which require its services. +Likewise, the +authentication server is only necessary for programs that wish to communicate +their identity to another. +None of the remaining services carry any special +status; not the network implementation, the filesystems, the program +execution mechanism (including setuid), or any others. + +

The Translator Mechanism

+

+The Hurd uses Mach ports primarily as methods for communicating between users +and servers. +(A Mach port is a communication point on a Mach task where +messages are sent and received.) Each port implements a particular set of +protocols, representing operations that can be undertaken on the underlying +object represented by the port. +Some of the protocols specified by the Hurd +are the I/O protocol, used for generic I/O operations; the file protocol, +used for filesystem operations; the socket protocol, used for network +operations; and the process protocol, used for manipulating processes et al. +

+Most servers are accessed by opening files. +Normally, when you open a file, +you create a port associated with that file that is owned by the server +that owns the directory containing the file. +For example, a disk-based +filesystem will normally serve a large number of ports, each of which +represents an open file or directory. +When a file is opened, the server +creates a new port, associates it with the file, and returns the port to the +calling program. +

+However, a file can have a +translator +associated with it. +In this case, +rather than return its own port which refers to the contents of the file, the +server executes a translator program associated with that file. +This +translator is given a port to the actual contents of the file, and is then +asked to return a port to the original user to complete the open operation. +

+This mechanism is used for +mount +by having a translator associated with +each mount point. +When a program opens the mount point, the translator (in +this case, a program which understands the disk format of the mounted +filesystem) is executed and returns a port to the program. +After the +translator is started, it need not be run again unless it dies; the parent +filesystem retains a port to the translator to use in further requests. +

+The owner of a file can associate a translator with it without special +permission. +This means that any program can be specified as a translator. +Obviously the system will not work properly if the translator does not +implement the file protocol correctly. +However, the Hurd is constructed so +that the worst possible consequence is an interruptible hang. +

+One way to use translators is to access hierarchically structured data using +the file protocol. +For example, all the complexity of the user interface to +the +ftp +program is removed. +Users need only know that a particular +directory represents FTP and can use all the standard file manipulation +commands (e.g +ls +or +cp) +to access the remote system, rather than learning +a new set. +Similarly, a simple translator could ease the complexity of +tar +or +gzip. +(Such transparent access would have some added cost, but it would +be convenient.) + +

Generic Services

+

+With translators, the filesystem can act as a rendezvous for interfaces which +are not similar to files. +Consider a service which implements some version +of the X protocol, using Mach messages as an underlying transport. +For each +X display, a file can be created with the appropriate program as its +translator. +X clients would open that file. +At that point, few file +operations would be useful (read and write, for example, would be useless), +but new operations ( +XCreateWindow +or +XDrawText) +might become meaningful. +In this case, the filesystem protocol is used only to manipulate +characteristics of the node used for the rendezvous. +The node need not +support I/O operations, though it should reply to any such messages with a +message_not_understood +return code. +

+This translator technique is used to contact most of the services in the Hurd +that are not structured like hierarchical filesystems. +For example, the +password server, which hands out authorization tags in exchange for +passwords, is contacted this way. +Network protocol servers are also +contacted in this fashion. +Roland McGrath thought up this use of translators. + +

Clever Filesystem Pictures

+

+In the Hurd, translators can also be used to present a filesystem-like view +of another part of the filesystem, with some semantics changed. +For example, +it would be nice to have a filesystem that cannot itself be changed, but +nonetheless records changed versions of its files elsewhere. +(This could be +useful for source code management.) +

+The Hurd will have a translator which creates a directory which is a +conceptual union of other directories, with collision resolution rules of +various sorts. +This can be used to present a single directory to users that +contains all the programs they would want to execute. +There are other useful +variations on this theme. + +

What The User Can Do

+

+No translator gains extra privilege by virtue of being hooked into the +filesystem. +Translators run with the uid of the owner of the file being +translated, and can only be set or changed by that owner. +The I/O and +filesystem protocols are carefully designed to allow their use by mutually +untrusting clients and servers. +Indeed, translators are just ordinary +programs. +The GNU C library has a variety of facilities to make common sorts +of translators easier to write. +

+Some translators may need special privileges, such as the password server or +translators which allow setuid execution. +These translators could be run by +anyone, but only if they are set on a root-owned node would they be able to +provide all their services successfully. +This is analogous to letting any +user call the +reboot +system call, but only honoring it if that user is root. + +

Why This Is So Different

+

+What this design provides is completely novel to the Unix world. +Until now, +OSs have kept huge portions of their functionality in the realm of system +code, thus preventing its modification and extension except in extreme need. +Users cannot replace parts of the system in their programs no matter how much +easier that would make their task, and system managers are loath to install +random tweaks off the net into their kernels. +

+In the Hurd, users can change almost all of the things that are decided for +them in advance by traditional systems. +In combination with the tremendous +control given by the Mach kernel over task address spaces and properties, the +Hurd provides a system in which users will, for the first time, be able to +replace parts of the system they dislike, without disrupting other users. +

+Most Mach-based OSs to date have mostly implemented a wider set of the + +same old + +Unix semantics in a new environment. +In contrast, GNU is extending +those semantics to allow users to improve, bypass, or replace them. + + +

Part 2: A Look at Some of the Hurd's Beasts

+

The Authentication Server

+

+One of the Hurd's more central servers is the authentication server. +Each +port to this server identifies a user and is associated by this server with +an +id block. +Each id block contains sets of user and group ids. +Either +set may be empty. +This server is not the same as the password server +referred to above. +

+The authentication server exports three services. +First, it provides simple +boolean operations on authentication ports: given two authentication ports, +this server will provide a third port representing the union of the two sets +of uids and gids. +Second, this server allows any user with a uid of zero to +create an arbitrary authentication port. +Finally, this server provides RPCs +(Remote Procedure Calls between different programs and possibly different +hosts) which allow mutually untrusting clients and servers to establish their +identities and pass initial information on each other. +This is crucial to +the security of the filesystem and I/O protocols. +

+Any user could write a program which implements the authentication protocol; +this does not violate the system's security. +When a service needs to +authenticate a user, it communicates with its trusted authentication server. +If that user is using a different authentication server, the transaction will +fail and the server can refuse to communicate further. +Because, in effect, +this forces all programs on the system to use the same authentication server, +we have designed its interface to make any safe operation possible, and to +include no extraneous operations. +(This is why there is a separate password +server.) +

The Process Server

+

+The process server acts as an information categorization repository. +There +are four main services supported by this server. +First, the process server +keeps track of generic host-level information not handled by the Mach kernel. +For example, the hostname, the hostid, and the system version are maintained +by the process server. +Second, this server maintains the Posix notions of +sessions and process groups, to help out programs that wish to use Posix +features. +

+Third, the process server maintains a one-to-one mapping between Mach tasks +and Hurd processes. +Every task is assigned a pid. +Processes can register a +message port with this server, which can then be given out to any program +which requests it. +This server makes no attempt to keep these message ports +private, so user programs are expected to implement whatever security they +need themselves. +(The GNU C Library provides convenient functions for all +this.) Processes can tell the process server their current `argv' and `envp' +values; this server will then provide, on request, these vectors of arguments +and environment. +This is useful for writing +ps-like +programs and also +makes it easier to hide or change this information. +None of these features +are mandatory. +Programs are free to disregard all of this and never register +themselves with the process server at all. +They will, however, still have a +pid assigned. +

+Finally, the process server implements +process collections, +which are used +to collect a number of process message ports at the same time. +Also, +facilities are provided for converting between pids, process server ports, +and Mach task ports, while ensuring the security of the ports managed. +

+It is important to stress that the process server is optional. +Because of +restrictions in Mach, programs must run as root in order to identify all the +tasks in the system. +But given that, multiple process servers could +co-exist, each with their own clients, giving their own model of the +universe. +Those process server features which do not require root privileges +to be implemented could be done as per-user servers. +The user's hands are +not tied. +

Transparent FTP

+

+Transparent FTP is an intriguing idea whose time has come. +The popular +ange-ftp +package available for GNU Emacs makes access to FTP files +virtually transparent to all the Emacs file manipulation functions. +Transparent FTP does the same thing, but in a system wide fashion. +This +server is not yet written; the details remain to be fleshed out, and will +doubtless change with experience. +

+In a BSD kernel, a transparent FTP filesystem would be no harder to write +than in the Hurd. +But mention the idea to a BSD kernel hacker, and the +response is that ``such a thing doesn't belong in the kernel''. +In a sense, +this is correct. +It violates all the layering principles of such systems to +place such things in the kernel. +The unfortunate side effect, however, is +that the design methodology (which is based on preventing users from changing +things they don't like) is being used to prevent system designers from making +things better. +(Recent BSD kernels make it possible to write a user program +that provides transparent FTP. +An example is +alex, +but it needs to run +with full root privileges.) +

+In the Hurd, there are no obstacles to doing transparent FTP. +A translator +will be provided for the node +/ftp. +The contents of +/ftp +will probably +not be directly listable, though further subdirectories will be. +There will +be a variety of possible formats. +For example, to access files on uunet, one +could + +cd /ftp/ftp.uu.net:anonymous:mib@gnu. + +Or to access files on a remote +account, one might + +cd /ftp/gnu.org:mib:passwd. + +Parts of this +command could be left out and the transparent FTP program would read them +from a user's +.netrc +file. +In the last case, one might just + +cd /ftp/gnu.org; + +when the rest of the data is already in +.netrc. +

+There is no need to do a +cd +first--use any file command. +To find out about +RFC 1097 (the Telnet Subliminal Message Option), just type + +more /ftp/ftp.uu.net/inet/rfc/rfc1097. + +A copy command to a local disk +could be used if the RFC would be read frequently. +

Filesystems

+

+Ordinary filesystems are also being implemented. +The initial release of the +Hurd will contain a filesystem upwardly compatible with the BSD 4.4 Fast File +System. +In addition to the ordinary semantics, it will provide means to +record translators, offer thirty-two bit user ids and group ids, and supply a +new id per file, called the +author +of the file, which can be set by the +owner arbitrarily. +In addition, because users in the Hurd can have multiple +uids (or even none), there is an additional set of permission bits providing +access control for + +unknown user + +(no uids) as distinct from + +known but arbitrary user + +(some uids: the existing +world +category of file +permissions). +

+The Network File System protocol will be implemented using 4.4 BSD as a +starting point. +A log-structured filesystem will also be implemented using +the same ideas as in Sprite, but probably not the same format. +A GNU network +file protocol may be designed in time, or NFS may be extended to remove its +deficiencies. +There will also be various ``little'' filesystems, such as the +MS-DOS filesystem, to help people move files between GNU and other OSs. + +

Terminals

+

+An I/O server will provide the terminal semantics of Posix. +The GNU C +Library has features for keeping track of the controlling terminal and for +arranging to have proper job control signals sent at the proper times, as +well as features for obeying keyboard and hangup signals. +

+Programs will be able to insert a terminal driver into communications +channels in a variety of ways. +Servers like +rlogind +will be able to insert +the terminal protocol onto their network communication port. +Pseudo-terminals will not be necessary, though they will be provided for +backward compatibility with older programs. +No programs in GNU will depend +on them. +

+Nothing about a terminal driver is forced upon users. +A terminal driver +allows a user to get at the underlying communications channel easily, to +bypass itself on an as-needed basis or altogether, or to substitute a +different terminal driver-like program. +In the last case, provided the +alternate program implements the necessary interfaces, it will be used by the +C Library exactly as if it were the ordinary terminal driver. +

+Because of this flexibility, the original terminal driver will not provide +complex line editing features, restricting itself to the behavior found in +Posix and BSD. +In time, there will be a +readline-based +terminal driver, +which will provide complex line-editing features for those users who want +them. +

+The terminal driver will probably not provide good support for the +high-volume, rapid data transmission required by UUCP or SLIP. +Those +programs do not need any of its features. +Instead they will be use the +underlying Mach device ports for terminals, which support moving large +amounts of data efficiently. + +

Executing Programs

+

+The implementation of the +execve +call is spread across three programs. +The +library marshals the argument and environment vectors. +It then sends a +message to the file server that holds the file to be executed. +The file +server checks execute permissions and makes whatever changes it desires in +the exec call. +For example, if the file is marked setuid and the fileserver +has the ability, it will change the user identification of the new image. +The file server also decides if programs which had access to the old task +should continue to have access to the new task. +If the file server is +augmenting permissions, or executing an unreadable image, then the exec needs +to take place in a new Mach task to maintain security. +

+After deciding the policy associated with the new image, the filesystem calls +the exec server to load the task. +This server, using the BFD (Binary File +Descriptor) library, loads the image. +BFD supports a large number of object +file formats; almost any supported format will be executable. +This server +also handles scripts starting with +#!, +running them through the indicated +program. +

+The standard exec server also looks at the environment of the new image; if +it contains a variable +EXECSERVERS +then it uses the programs specified +there as exec servers instead of the system default. +(This is, of course, +not done for execs that the file server has requested be kept secure.) +

+The new image starts running in the GNU C Library, which sends a message to +the exec server to get the arguments, environment, umask, current directory, +etc. +None of this additional state is special to the file or exec servers; +if programs wish, they can use it in a different manner than the Library. + +

New Processes

+

+The +fork +call is implemented almost entirely in the GNU C Library. +The new +task is created by Mach kernel calls. +The C Library arranges to have its +image inherited properly. +The new task is registered with the process server +(though this is not mandatory). +The C Library provides vectors of functions +to be called at fork time: one vector to be called before the fork, one after +in the parent, and one after in the child. +(These features should not be +used to replace the normal fork-calling sequence; it is intended for +libraries which need to close ports or clean up before a fork occurs.) +The C +library will implement both fork calls specified by the draft Posix.4a (the +proposed standard dealing with the threads extension to the real-time +extension). +

+Nothing forces the user to create new tasks this way. +If a program wants to +use almost the normal fork, but with some special characteristics, then it +can do so. +Hooks will be provided by the C Library, or the function can even +be completely replaced. +None of this is possible in a traditional Unix +system. + +

Asynchronous Messages

+

+As mentioned above, the process server maintains a + +message port + +for each +task registered with it. +These ports are public, and are used to send +asynchronous messages to the task. +Signals, for example, are sent to the +message port. +The signal message also provides a port as an indication that +the sender should be trusted to send the signal. +The GNU C Library lists a +variety of ports in a table, each of which identifies a set of signals that +can be sent by anyone who possesses that port. +For example, if the user +possesses the task's kernel port, it is allowed to send any signal. +If the +user possesses a special + +terminal id + +port, it is allowed to send the +keyboard and hangup signals. +Users can add arbitrary new entries into the C +library's signal permissions table. +

+When a process's process group changes, the process server will send it a +message indicating the new process group. +In this case, the process server +proves its authority by providing the task's kernel port. +

+The C library also has messages to add and delete uids currently used by the +process. +If new uids are sent to the program, the library adds them to its +current set, and then exchanges messages with all the I/O servers it knows +about, proving to them its new authorization. +Similarly, a message can +delete uids. +In the latter case, the caller must provide the process's task +port. +(You can't harm a process by giving it extra permission, but you can +harm it by taking permission away.) The Hurd will provide user programs to +send these messages to processes. +For example, the +su +command will be able +to cause all the programs in your current login session, to gain a new uid, +rather than spawn a subshell. +

+The C library will allow programs to add asynchronous messages they wish to +recognize, as well as prevent recognition of the standard set. +

Making It Look Like Unix

+

+The C Library will implement all of the calls from BSD and Posix as well as +some obvious extensions to them. +This enables users to replace those calls +they dislike or bypass them entirely, whereas in Unix the calls must be used +``as they come'' with no alternatives possible. +

+In some environments binary compatibility will also be supported. +This works +by building a special version of the library which is then loaded somewhere +in the address space of the process. +(For example, on a VAX, it would be +tucked in above the stack.) A feature of Mach, called system call +redirection, is then used to trap Unix system calls and turn them into jumps +into this special version of the library. +(On almost all machines, the cost +of such a redirection is very small; this is a highly optimized path in Mach. +On a 386 it's about two dozen instructions. +This is little worse than a +simple procedure call.) +

+Many features of Unix, such as signal masks and vectors, are handled +completely by the library. +This makes such features significantly cheaper +than in Unix. +It is now reasonable to use +sigblock +extensively to protect +critical sections, rather than seeking out some other, less expensive method. + +

Network Protocols

+

+The Hurd will have a library that will make it very easy to port 4.4 BSD +protocol stacks into the Hurd. +This will enable operation, virtually for +free, of all the protocols supported by BSD. +Currently, this includes the +CCITT protocols, the TCP/IP protocols, the Xerox NS protocols, and the ISO +protocols. +

+For optimal performance some work would be necessary to take advantage of +Hurd features that provide for very high speed I/O. +For most protocols this +will require some thought, but not too much time. +The Hurd will run the +TCP/IP protocols as efficiently as possible. +

+As an interesting example of the flexibility of the Hurd design, consider the +case of IP trailers, used extensively in BSD for performance. +While the Hurd +will be willing to send and receive trailers, it will gain fairly little +advantage in doing so because there is no requirement that data be copied and +avoiding copies for page-aligned data is irrelevant. + +


+ +Return to GNU's home page. +

+FSF & GNU inquiries & questions to +gnu@gnu.org. +Other ways to contact the FSF. +

+Comments on these web pages to +webmasters@www.gnu.org, +send other questions to +gnu@gnu.org. +

+Copyright (C) 1996 Trent Fisher +
+Copyright (C) 1996, 1997, 1998 Free Software Foundation, Inc., +59 Temple Place - Suite 330, Boston, MA 02111, USA +

+Verbatim copying and distribution of this entire article is +permitted in any medium, provided this notice is preserved.

+Updated: + +19 Dec 1998 jonas + +


+ + -- cgit v1.2.3 From 104b4171c70fe1c9fc60ebe7aeef9ef75a2eb1bc Mon Sep 17 00:00:00 2001 From: "Alfred M. Szmidt" Date: Fri, 23 May 2003 09:54:31 +0000 Subject: Added links to the Hebrew translations. From the duke Of Spacingham . --- gnumach.html | 2 ++ hurd-paper.html | 12 ++++++++++++ hurd.html | 2 ++ mig.html | 2 ++ 4 files changed, 18 insertions(+) (limited to 'hurd-paper.html') diff --git a/gnumach.html b/gnumach.html index 1034e4c3..2e1dc08e 100644 --- a/gnumach.html +++ b/gnumach.html @@ -13,6 +13,7 @@  [image of the Hurd logo] [ English +| Hebrew ] @@ -134,6 +135,7 @@ has cleaner machine specific support code. [ English +| Hebrew ]
diff --git a/hurd-paper.html b/hurd-paper.html index e98e5edf..6f3bbc75 100644 --- a/hurd-paper.html +++ b/hurd-paper.html @@ -11,6 +11,11 @@ WIDTH="333" HEIGHT="80"> (jpeg 10k) (jpeg 20k) no gifs due to patent problems +
+
+[ English +| Hebrew + ]

This article explains why FSF is developing a new operating system named the Hurd, which will be a foundation of the whole GNU system. @@ -765,6 +770,13 @@ avoiding copies for page-aligned data is irrelevant.


+[ + English +| Hebrew +] + +
+ Return to GNU's home page.

FSF & GNU inquiries & questions to diff --git a/hurd.html b/hurd.html index 44cf14e0..fbca3b59 100644 --- a/hurd.html +++ b/hurd.html @@ -17,6 +17,7 @@ Chinese(Simplified) | Chinese(Traditional) | English +| Hebrew ] @@ -171,6 +172,7 @@ developers. Chinese(Simplified) | Chinese(Traditional) | English +| Hebrew ]


diff --git a/mig.html b/mig.html index 4726921f..0a772663 100644 --- a/mig.html +++ b/mig.html @@ -13,6 +13,7 @@  [image of the Hurd logo] [ English +| Hebrew ] @@ -80,6 +81,7 @@ OSF Mach. [ English +| Hebrew ]
-- cgit v1.2.3 From 1227cac8df0eeaa315a0dcd6fe2b1312afcbae8e Mon Sep 17 00:00:00 2001 From: "Alfred M. Szmidt" Date: Mon, 26 May 2003 12:48:26 +0000 Subject: Added reminder note. --- changelogs.html | 4 ++++ devel.html | 4 ++++ docs.html | 4 ++++ download.html | 4 ++++ gnumach-download.html | 4 ++++ gnumach-install.html | 4 ++++ gnumach.html | 8 ++++++-- help.html | 4 ++++ history.html | 8 ++++---- hurd-paper.html | 12 +++++++++--- hurd-talk.html | 4 ++++ hurd.html | 2 ++ install.html | 4 ++++ mig-download.html | 4 ++++ mig.html | 8 ++++++-- related-projects.html | 4 ++++ whatsnew.html | 12 ++++++++---- whatsold.html | 4 ++++ 18 files changed, 83 insertions(+), 15 deletions(-) (limited to 'hurd-paper.html') diff --git a/changelogs.html b/changelogs.html index 46bd340b..8cd894b9 100644 --- a/changelogs.html +++ b/changelogs.html @@ -12,6 +12,8 @@  [image of the Hurd logo] [ + + English ] @@ -147,6 +149,8 @@ covers all changes to MiG.
[ + + English ] diff --git a/devel.html b/devel.html index 90f7de8c..642177ed 100644 --- a/devel.html +++ b/devel.html @@ -12,6 +12,8 @@  [image of the Hurd logo] [ + + English ] @@ -87,6 +89,8 @@ of the Hurd source repository.
[ + + English ] diff --git a/docs.html b/docs.html index 78c4ddc0..9e413017 100644 --- a/docs.html +++ b/docs.html @@ -12,6 +12,8 @@  [image of the Hurd logo] [ + + English ] @@ -155,6 +157,8 @@ Then, you should submit any modifications to
[ + + English ] diff --git a/download.html b/download.html index d3b2ee9a..bddb564b 100644 --- a/download.html +++ b/download.html @@ -12,6 +12,8 @@  [image of the Hurd logo] [ + + English ] @@ -93,6 +95,8 @@ to date.
[ + + English ] diff --git a/gnumach-download.html b/gnumach-download.html index 8838881d..96ee79ad 100644 --- a/gnumach-download.html +++ b/gnumach-download.html @@ -12,6 +12,8 @@  [image of the Hurd logo] [ + + English ] @@ -134,6 +136,8 @@ to date.
[ + + English ] diff --git a/gnumach-install.html b/gnumach-install.html index 7e70b74d..f15e214c 100644 --- a/gnumach-install.html +++ b/gnumach-install.html @@ -12,6 +12,8 @@  [image of the Hurd logo] [ + + English ] @@ -87,6 +89,8 @@ GNU/Hurd.
[ + + English ] diff --git a/gnumach.html b/gnumach.html index 2e1dc08e..33e67d8a 100644 --- a/gnumach.html +++ b/gnumach.html @@ -12,8 +12,10 @@  [image of the Hurd logo] [ + + English -| Hebrew +| Hebrew ] @@ -134,8 +136,10 @@ has cleaner machine specific support code.
[ + + English -| Hebrew +| Hebrew ]
diff --git a/help.html b/help.html index 50050170..a12c666a 100644 --- a/help.html +++ b/help.html @@ -12,6 +12,8 @@  [image of the Hurd logo] [ + + English ] @@ -96,6 +98,8 @@ FSF. The FSF is not responsible for the content of these other web sites.
[ + + English ] diff --git a/history.html b/history.html index 93f2d182..f5200322 100644 --- a/history.html +++ b/history.html @@ -14,8 +14,8 @@ [ - English | - Hebrew + English +| Hebrew ] @@ -157,8 +157,8 @@ works! [ - English | - Hebrew + English +| Hebrew ]
diff --git a/hurd-paper.html b/hurd-paper.html index 6f3bbc75..4fe7c12f 100644 --- a/hurd-paper.html +++ b/hurd-paper.html @@ -13,9 +13,13 @@ no gifs due to patent problems

-[ English +[ + + + English | Hebrew - ] +] +

This article explains why FSF is developing a new operating system named the Hurd, which will be a foundation of the whole GNU system. @@ -771,8 +775,10 @@ avoiding copies for page-aligned data is irrelevant.


[ + + English -| Hebrew +| Hebrew ]
diff --git a/hurd-talk.html b/hurd-talk.html index 5ae2217e..756eee1c 100644 --- a/hurd-talk.html +++ b/hurd-talk.html @@ -12,6 +12,8 @@  [image of the Hurd logo] [ + + English ] @@ -1111,6 +1113,8 @@ FSF. The FSF is not responsible for the content of these other web sites.
[ + + English ] diff --git a/hurd.html b/hurd.html index fbca3b59..ce834955 100644 --- a/hurd.html +++ b/hurd.html @@ -169,6 +169,8 @@ developers.
[ + + Chinese(Simplified) | Chinese(Traditional) | English diff --git a/install.html b/install.html index 9cfa5c23..3d5e6ae9 100644 --- a/install.html +++ b/install.html @@ -12,6 +12,8 @@  [image of the Hurd logo] [ + + English ] @@ -103,6 +105,8 @@ FSF. The FSF is not responsible for the content of these other web sites.
[ + + English ] diff --git a/mig-download.html b/mig-download.html index ba4c8316..0539a60a 100644 --- a/mig-download.html +++ b/mig-download.html @@ -12,6 +12,8 @@  [image of the Hurd logo] [ + + English ] @@ -115,6 +117,8 @@ to date.
[ + + English ] diff --git a/mig.html b/mig.html index 0a772663..1b6c908d 100644 --- a/mig.html +++ b/mig.html @@ -12,8 +12,10 @@  [image of the Hurd logo] [ + + English -| Hebrew +| Hebrew ] @@ -80,8 +82,10 @@ OSF Mach.
[ + + English -| Hebrew +| Hebrew ]
diff --git a/related-projects.html b/related-projects.html index ad0c9087..f7d01494 100644 --- a/related-projects.html +++ b/related-projects.html @@ -12,6 +12,8 @@  [image of the Hurd logo] [ + + English ] @@ -109,6 +111,8 @@ topic, and everyone is invited to contribute to it.
[ + + English ] diff --git a/whatsnew.html b/whatsnew.html index 39292f82..0cea85c4 100644 --- a/whatsnew.html +++ b/whatsnew.html @@ -12,8 +12,10 @@  [image of the Hurd logo] [ - English | - Hebrew + + + English +| Hebrew ] @@ -146,8 +148,10 @@ about the details of authentication in the Hurd.
[ - English | - Hebrew + + + English +| Hebrew ]
diff --git a/whatsold.html b/whatsold.html index 974aa49b..b9104830 100644 --- a/whatsold.html +++ b/whatsold.html @@ -12,6 +12,8 @@  [image of the Hurd logo] [ + + English ] @@ -235,6 +237,8 @@ German).
[ + + English ] -- cgit v1.2.3 From 895454f34a24f788e34ae75ff16564365a51d207 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 8 Feb 2006 19:27:40 +0000 Subject: Turkish translation of `Towards a New Strategy of OS Design' by Oktay Poçan, web-hurd, 2006-02-01. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- hurd-paper.html | 6 ++++-- whatsnew.html | 8 ++++++++ 2 files changed, 12 insertions(+), 2 deletions(-) (limited to 'hurd-paper.html') diff --git a/hurd-paper.html b/hurd-paper.html index 4fe7c12f..fbd34014 100644 --- a/hurd-paper.html +++ b/hurd-paper.html @@ -18,6 +18,7 @@ English | Hebrew +| Turkish ]

@@ -777,8 +778,9 @@ avoiding copies for page-aligned data is irrelevant. [ - English -| Hebrew + English +| Hebrew +| Turkish ]


diff --git a/whatsnew.html b/whatsnew.html index 24cf2347..465fbe88 100644 --- a/whatsnew.html +++ b/whatsnew.html @@ -69,6 +69,14 @@ so that it can be added here.

+
08 February 2006
+
+Added a Turkish translation +of Towards a New Strategy of +OS Design by Oktay Poçan. +

+

+
02 October 2005
Added Polish translations -- cgit v1.2.3 From 576122f6309c49745d16be06e7ce2218a769e96c Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Mon, 4 Dec 2006 19:42:27 +0000 Subject: This was a `sed'-based change, where I didn't review every single detail and thus hope that I didn't break anything. Replace `MiG' with `MIG'. Replace `MIG' with `GNU MIG' and `The GNU Hurd' with `GNU Hurd' when linking to the pages. Make the space between `GNU' and `Hurd' or `Mach' or `MIG' non-breakable. --- acknowledgements.html | 8 ++++---- auth.html | 6 +++--- changelogs.html | 16 ++++++++-------- devel.html | 6 +++--- docs.html | 16 ++++++++-------- download.html | 8 ++++---- gnumach-download.html | 20 ++++++++++---------- gnumach-install.html | 18 +++++++++--------- gnumach.html | 36 ++++++++++++++++++------------------ help.html | 10 +++++----- history.html | 10 +++++----- hurd-announcements.html | 4 ++-- hurd-folks.html | 6 +++--- hurd-l4.html | 12 ++++++------ hurd-paper.html | 2 +- hurd-talk.html | 22 +++++++++++----------- hurd.html | 10 +++++----- install.html | 8 ++++---- mig-download.html | 20 ++++++++++---------- mig.html | 16 ++++++++-------- old_hurd_faq.html | 10 +++++----- related-projects.html | 10 +++++----- whatsnew.html | 28 ++++++++++++++-------------- whatsold.html | 18 +++++++++--------- 24 files changed, 160 insertions(+), 160 deletions(-) (limited to 'hurd-paper.html') diff --git a/acknowledgements.html b/acknowledgements.html index fb39187d..5e04a01d 100644 --- a/acknowledgements.html +++ b/acknowledgements.html @@ -3,7 +3,7 @@ - GNU Hurd: Acknowledgements + GNU Hurd: Acknowledgements @@ -12,7 +12,7 @@ diff --git a/changelogs.html b/changelogs.html index 12e0f759..0038c742 100644 --- a/changelogs.html +++ b/changelogs.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -26,7 +26,7 @@  
ChangeLogs

-The GNU Hurd
+GNU Hurd
 
Documentation
Installation
@@ -41,7 +41,7 @@ Installation
Source Code
 
-MiG
+GNU MIG
 
Source Code
 
@@ -131,20 +131,20 @@ subdirectories: libthreads, libtrivfs -

GNU Mach

+

GNU Mach

The GNU -Mach ChangeLog covers all changes to GNU Mach and covers all changes to GNU Mach and GNU Mach 1 branch ChangeLog those on the gnumach-1-branch. Changes before March 1997 are listed in ChangeLog.0 and ChangeLog.00. -

MiG

+

MIG

The MiG ChangeLog -covers all changes to MiG. +HREF="http://cvs.savannah.gnu.org/viewcvs/~checkout~/hurd/mig/ChangeLog">MIG ChangeLog +covers all changes to MIG. diff --git a/devel.html b/devel.html index 87426bb9..868277a0 100644 --- a/devel.html +++ b/devel.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -26,7 +26,7 @@  
ChangeLogs

-The GNU Hurd
+GNU Hurd
 
Documentation
Installation
@@ -41,7 +41,7 @@ Installation
Source Code
 
-MiG
+GNU MIG
 
Source Code
 
diff --git a/docs.html b/docs.html index 03732f30..b65e6407 100644 --- a/docs.html +++ b/docs.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -26,7 +26,7 @@  
ChangeLogs

-The GNU Hurd
+GNU Hurd
 
Documentation
Installation
@@ -41,7 +41,7 @@ Installation
Source Code
 
-MiG
+GNU MIG
 
Source Code
 
@@ -67,7 +67,7 @@ architectural overview by Thomas Bushnell, BSG. The Hurd, a presentation by Marcus Brinkmann.

  • - The + GNU/Hurd User's Guide, an introduction to the important concepts and software of the GNU system, written for new users, AKA "GNUbies." @@ -87,7 +87,7 @@ for download.
  • The Hurd Hacking -Guide, an introduction to GNU Hurd and Mach programming by +Guide, an introduction to GNU Hurd and Mach programming by Wolfgang Jährling.

    Available Formats: @@ -112,7 +112,7 @@ the authentication mechanisms in the Hurd by Wolfgang Jährling.

    Please check out the Frequently -Asked Questions about the GNU Hurd (33k characters) and their +Asked Questions about the GNU Hurd (33k characters) and their answers, which cover most issues a new user will be confronted with.

    This document is available in several languages: @@ -128,8 +128,8 @@ This document is available in several languages:

    Reference manuals

    -The GNU Hurd Reference Manual documents the architecture, the usage -and the programming of the GNU Hurd. At the moment, the manual is +The GNU Hurd Reference Manual documents the architecture, the usage +and the programming of the GNU Hurd. At the moment, the manual is quite incomplete.

    Available Formats: diff --git a/download.html b/download.html index fe759c4a..ac3b4069 100644 --- a/download.html +++ b/download.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -26,7 +26,7 @@  
    ChangeLogs

    -The GNU Hurd
    +GNU Hurd
     
    Documentation
    Installation
    @@ -41,7 +41,7 @@ Installation
    Source Code
     
    -MiG
    +GNU MIG
     
    Source Code
     
    @@ -84,7 +84,7 @@ to date.

    There is also a cross referenced -database of the Hurd, GNU Mach, MiG, and the GNU C library sources +database of the Hurd, GNU Mach, MIG, and the GNU C library sources online for you to browse. It provides better searching and browsing facilities than the online CVS repository, but it is not always up to date and does not contain history information. diff --git a/gnumach-download.html b/gnumach-download.html index 914efafd..81222bc9 100644 --- a/gnumach-download.html +++ b/gnumach-download.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -25,7 +25,7 @@  
    ChangeLogs

    -The GNU Hurd
    +GNU Hurd
     
    Documentation
    Installation
    @@ -40,7 +40,7 @@ Installation
    Source Code
     
    -MiG
    +GNU MIG
     
    Source Code
     
    @@ -58,7 +58,7 @@

    Latest Release

    -The latest release of GNU Mach is version 1.3, 2002-05-28. It features: +The latest release of GNU Mach is version 1.3, 2002-05-28. It features:

    • Bug fixes.
    • The kernel now directly supports "boot scripts" in the form of @@ -81,7 +81,7 @@ attributes.
    • added.

    -You can download the latest version of GNU Mach from the GNU ftp server: +You can download the latest version of GNU Mach from the GNU ftp server:

    • gnumach-1.3.tar.gz @@ -91,7 +91,7 @@ HREF="http://ftp.gnu.org/gnu/gnumach/gnumach-1.3.tar.gz.sig">gnumach-1.3.tar.gz. [1K].
    • gnumach-1.2-1.3.diff.gz -[310K], containing the differences between GNU Mach 1.2 and GNU Mach 1.3.
    • +[310K], containing the differences between GNU Mach 1.2 and GNU Mach 1.3.
    • gnumach-1.2-1.3.diff.gz.sig [1K].
    • @@ -99,7 +99,7 @@ HREF="http://ftp.gnu.org/gnu/gnumach/gnumach-1.2-1.3.diff.gz.sig">gnumach-1.2-1.

      CVS repository

      -The GNU Mach source code is managed in the version control system CVS. You can check out the CVS repository with the following instruction set. @@ -108,7 +108,7 @@ Source tree:
      cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/hurd co gnumach

      -Use to following to get the GNU Mach 1 branch: +Use to following to get the GNU Mach 1 branch:
      cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/hurd co -r gnumach-1-branch gnumach @@ -121,13 +121,13 @@ href="https://savannah.gnu.org/cvs/?group=hurd">Savannah page.

      You can also browse the CVS -repository of GNU Mach with your web browser. The web pages are +repository of GNU Mach with your web browser. The web pages are generated dynamically at the time you request them and are always up to date.

      There is also a cross referenced -database of the Hurd, GNU Mach, MiG, and the GNU C library sources +database of the Hurd, GNU Mach, MIG, and the GNU C library sources online for you to browse. It provides better searching and browsing facilities than the online CVS repository, but it is not always up to date and does not contain history information. diff --git a/gnumach-install.html b/gnumach-install.html index a44460fd..06d4f6ad 100644 --- a/gnumach-install.html +++ b/gnumach-install.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -25,7 +25,7 @@  
      ChangeLogs

      -The GNU Hurd
      +GNU Hurd
       
      Documentation
      Installation
      @@ -40,7 +40,7 @@ Installation
      Source Code
       
      -MiG
      +GNU MIG
       
      Source Code
       
      @@ -52,22 +52,22 @@


      Latest version

      -The last stable version of GNU Mach is 1.3, but it is recommended that +The last stable version of GNU Mach is 1.3, but it is recommended that you use the version in CVS instead, as this fixes some bugs that prevent the kernel to work on some systems.

      Installation instructions

      -GNU Mach can be compiled or cross-compiled easily. The only package -you are not likely to have installed already is MiG, the Mach +GNU Mach can be compiled or cross-compiled easily. The only package +you are not likely to have installed already is MIG, the Mach interface generator. If you cross-compile gnumach, you need a -cross-MiG for your architecture. You also need the static version of +cross-MIG for your architecture. You also need the static version of the C library for your host architecture, as some functions are taken directly from it. We recommend that you use the GNU C library, other C libraries @@ -75,7 +75,7 @@ have not been tested and might not work. After you have followed the installation instructions in the package and the reference manual, you should end up with a kernel binary where your boot loader can find it. -

      Booting GNU Mach

      +

      Booting GNU Mach

      To actually use the kernel and boot the GNU operating system, you need a boot loader. Not all boot loaders are capable to boot the GNU diff --git a/gnumach.html b/gnumach.html index d00fc274..2a983c76 100644 --- a/gnumach.html +++ b/gnumach.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -27,7 +27,7 @@  
      ChangeLogs

      -The GNU Hurd
      +GNU Hurd
       
      Documentation
      Installation
      @@ -42,7 +42,7 @@ Installation
      Source Code
       
      -MiG
      +GNU MIG
       
      Source Code
       
      @@ -54,32 +54,32 @@

      Table of Contents


      -

      Introduction to GNU Mach

      +

      Introduction to GNU Mach

      -GNU Mach is the microkernel of the GNU system. A microkernel provides +GNU Mach is the microkernel of the GNU system. A microkernel provides only a limited functionality, just enough abstraction on top of the hardware to run the rest of the operating system in user space. The -GNU Hurd servers and the GNU C library implement the POSIX compatible +GNU Hurd servers and the GNU C library implement the POSIX compatible base of the GNU system on top of the microkernel architecture provided by Mach.

      -Currently, GNU Mach runs on IA32 machines. GNU Mach should, and +Currently, GNU Mach runs on IA32 machines. GNU Mach should, and probably will, be ported to other hardware architectures in the future. Mach was ported to many operating systems in the past.

      -GNU Mach is maintained by the Hurd developers for the GNU project. If -you need help with GNU Mach or want to contribute to the development +GNU Mach is maintained by the Hurd developers for the GNU project. If +you need help with GNU Mach or want to contribute to the development of the microkernel, you should contact the Hurd people. -

      Advantages of GNU Mach

      -GNU Mach is not the most advanced microkernel known to the planet, nor +

      Advantages of GNU Mach

      +GNU Mach is not the most advanced microkernel known to the planet, nor is it the fastest or smallest, but it has a rich set of interfaces and some features which make it useful as the base of the Hurd system.
      @@ -90,11 +90,11 @@ Anybody can use, modify, and redistribute it under the terms of the
      it's built to survive
      -As a microkernel, GNU Mach doesn't implement a lot of the features +As a microkernel, GNU Mach doesn't implement a lot of the features commonly found in an operating system, but only the bare minimum that is required to implement a full operating system on top of it. This means that a lot of the operating system code is maintained outside of -GNU Mach, and while this code may go through a complete redesign, the +GNU Mach, and while this code may go through a complete redesign, the code of the microkernel can remain comparatively stable.
      it's scalable
      @@ -103,7 +103,7 @@ Mach is particularly well suited for SMP and network cluster techniques. Thread support is provided at the kernel level, and the kernel itself takes advantage of that. Network transparency at the IPC level makes resources of the system available across machine -boundaries (with NORMA IPC, currently not available in GNU Mach). +boundaries (with NORMA IPC, currently not available in GNU Mach).
      it exists
      @@ -118,17 +118,17 @@ multi-server operating system, the Hurd.

      Status of the project

      -GNU Mach 1.3 was released in May 2002, and features advanced boot +GNU Mach 1.3 was released in May 2002, and features advanced boot script support, support for large disks (>= 10GB) and an improved console.

      -GNU Mach is used as the default microkernel in the GNU/Hurd system. +GNU Mach is used as the default microkernel in the GNU/Hurd system. It is compatible with other popular Mach distributions. The device drivers for block devices and network cards are taken from Linux 2.0.x kernel versions, and so a broad range of common hardware is supported.

      However, the Linux device drivers have been improved greatly since the -2.0.x version, and a new version of GNU Mach based on the OSKit +2.0.x version, and a new version of GNU Mach based on the OSKit library is being worked on, which uses newer drivers and in general has cleaner machine specific support code. diff --git a/help.html b/help.html index 8cdca956..0daafe0e 100644 --- a/help.html +++ b/help.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -26,7 +26,7 @@  
      ChangeLogs

      -The GNU Hurd
      +GNU Hurd
       
      Documentation
      Installation
      @@ -41,7 +41,7 @@ Installation
      Source Code
       
      -MiG
      +GNU MIG
       
      Source Code
       
      @@ -59,14 +59,14 @@

      Mailing lists

      If you have questions about the installation, how the Hurd works and -how it is used, or general questions concerning the Hurd, GNU Mach or +how it is used, or general questions concerning the Hurd, GNU Mach or the other packages maintained by the Hurd people, you can send an e-mail to the Help-Hurd <help-hurd@gnu.org> mailing list.

      -Bug reports for the GNU Hurd, GNU Mach and the other packages +Bug reports for the GNU Hurd, GNU Mach and the other packages maintained by the Hurd people should be sent to the Bug-Hurd <bug-hurd@gnu.org> mailing diff --git a/history.html b/history.html index 5b688d4b..5f559b17 100644 --- a/history.html +++ b/history.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -27,7 +27,7 @@  
      ChangeLogs

      -The GNU Hurd
      +GNU Hurd
       
      Documentation
      Installation
      @@ -42,7 +42,7 @@ Installation
      Source Code
       
      -MiG
      +GNU MIG
       
      Source Code
       
      @@ -145,9 +145,9 @@ works!

      News flash, Apr 94 -- it boots!
      -GNU Hurd announcement, Nov 93
      +GNU Hurd announcement, Nov 93
      -GNU Hurd announcement, May 91
      +GNU Hurd announcement, May 91
      diff --git a/hurd-announcements.html b/hurd-announcements.html index 3d89230f..d4944b57 100644 --- a/hurd-announcements.html +++ b/hurd-announcements.html @@ -73,10 +73,10 @@ works! News flash, Apr 94 -- it boots!
      -GNU Hurd announcement, Nov 93
      +GNU Hurd announcement, Nov 93
      -GNU Hurd announcement, May 91
      +GNU Hurd announcement, May 91
        diff --git a/hurd-folks.html b/hurd-folks.html index 93637440..0becf042 100644 --- a/hurd-folks.html +++ b/hurd-folks.html @@ -1,11 +1,11 @@ -GNU Hurd folks - GNU Project - Free Software Foundation (FSF) +GNU Hurd folks - GNU Project - Free Software Foundation (FSF) -

      GNU Hurd folks

      +

      GNU Hurd folks

       [image of a Hurd Metafont Logo] (jpeg 10k) @@ -14,7 +14,7 @@

      A number of people maintain their own unofficial GNU Hurd pages to describe their involvements. +HREF="hurd.html">GNU Hurd pages to describe their involvements. These are valuable sites because they help introduce more people to the Hurd, and to the GNU project. diff --git a/hurd-l4.html b/hurd-l4.html index d1aad633..62b164bd 100644 --- a/hurd-l4.html +++ b/hurd-l4.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -25,7 +25,7 @@  
      ChangeLogs

      -The GNU Hurd
      +GNU Hurd
       
      Documentation
      Installation
      @@ -40,7 +40,7 @@ Installation
      Source Code
       
      -MiG
      +GNU MIG
       
      Source Code
       
      @@ -50,7 +50,7 @@


      Table of Contents


      -

      The GNU Hurd on top of the L4 microkernel

      +

      The GNU Hurd on top of the L4 microkernel

      -The GNU Hurd on top of the L4 microkernel is an on-going effort to +The GNU Hurd on top of the L4 microkernel is an on-going effort to port the Hurd system to the L4Ka::Pistachio microkernel. diff --git a/hurd-paper.html b/hurd-paper.html index fbd34014..19ccef2f 100644 --- a/hurd-paper.html +++ b/hurd-paper.html @@ -120,7 +120,7 @@ But the wall between user and system remains; no user can cross it without special privilege.

      -The GNU Hurd, by contrast, is designed to make the area of +The GNU Hurd, by contrast, is designed to make the area of system code as limited as possible. diff --git a/hurd-talk.html b/hurd-talk.html index 756eee1c..497f1fb0 100644 --- a/hurd-talk.html +++ b/hurd-talk.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -24,7 +24,7 @@  
      ChangeLogs

      -The GNU Hurd
      +GNU Hurd
       
      Documentation
      Installation
      @@ -39,7 +39,7 @@ Installation
      Source Code
       
      -MiG
      +GNU MIG
       
      Source Code
       
      @@ -117,12 +117,12 @@ this brings further advantages beside freedom.

      The Hurd is a POSIX compatible multi-server -system operating on top of the GNU Mach microkernel. +system operating on top of the GNU Mach microkernel.

      Topics:

        -
      • GNU Mach
      • +
      • GNU Mach
      • The Hurd
      • Development
      • Debian GNU/Hurd
      • @@ -131,10 +131,10 @@ Topics:

        The Hurd is a POSIX compatible multi-server system operating on top of -the GNU Mach Microkernel. +the GNU Mach Microkernel.

        -I will have to explain what GNU Mach is, so we start with that. Then +I will have to explain what GNU Mach is, so we start with that. Then I will talk about the Hurd's architecture. After that, I will give a short overview on the Hurd libraries. Finally, I will tell you how the Debian project is related to the Hurd. @@ -215,7 +215,7 @@ interface, it provides tasks and threads, a messaging system allowing synchronous and asynchronous operation and a complex interface for external pagers. It's certainly not one of the sexiest microkernels that exist today, but more like a big old mama. The GNU project -maintains its own version of Mach, called GNU Mach, which is based on +maintains its own version of Mach, called GNU Mach, which is based on Mach 4.0. In addition to the features contained in Mach 4.0, the GNU version contains many of the Linux 2.0 block device and network card drivers. @@ -355,7 +355,7 @@ To quote Thomas Bushnell, BSG, from his paper ``A new strategy towards OS design'' (1996):

        -The GNU Hurd, by contrast, is designed to make the area of system code +The GNU Hurd, by contrast, is designed to make the area of system code as limited as possible. Programs are required to communicate only with a few essential parts of the kernel; the rest of the system is replaceable dynamically. Users can use whatever parts of the @@ -382,7 +382,7 @@ channels.
      • Potentially many senders

      -MiG provides remote procedure calls on top of Mach IPC. RPCs look like +MIG provides remote procedure calls on top of Mach IPC. RPCs look like function calls to the user.

  • -The GNU Hurd
    +GNU Hurd
    About the Hurd
    About Microkernels
    @@ -67,9 +67,9 @@ apologize... please let us know so that we can update this list!
    Documentation
    Derek Upham
    -
    wrote the original GNU Hurd FAQ
    +
    wrote the original GNU Hurd FAQ
    Gordon Matzigkeit
    -
    reorganized and updated the GNU Hurd Reference Manual for release 0.3reorganized and updated the GNU Hurd Reference Manual for release 0.3
    Matthew C. Vernon
    wrote the ``Idiot's Guide'' for getting started with the Hurd
    diff --git a/auth.html b/auth.html index aa4e6b67..78b9f937 100644 --- a/auth.html +++ b/auth.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -22,7 +22,7 @@  
    ChangeLogs

    -The GNU Hurd
    +GNU Hurd
     
    Documentation
    Installation
    @@ -37,7 +37,7 @@ Installation
    Source Code
     
    -MiG
    +GNU MIG
     
    Source Code

    @@ -990,7 +990,7 @@ Side Goal:

    -The Debian distribution of the GNU Hurd that I started in 1998 is +The Debian distribution of the GNU Hurd that I started in 1998 is supposed to become a complete binary distribution of the Hurd that is easy to install. diff --git a/hurd.html b/hurd.html index f6c870b4..36aca9a9 100644 --- a/hurd.html +++ b/hurd.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -33,7 +33,7 @@  
    ChangeLogs

    -The GNU Hurd
    +GNU Hurd
     
    Documentation
    Installation
    @@ -48,7 +48,7 @@ Installation
    Source Code
     
    -MiG
    +GNU MIG
     
    Source Code
     
    @@ -69,7 +69,7 @@

    Introduction to the Hurd

    -The GNU Hurd is the GNU project's replacement for the Unix kernel. +The GNU Hurd is the GNU project's replacement for the Unix kernel. The Hurd is a collection of servers that run on the Mach microkernel to implement file systems, network protocols, file access control, and other features that are implemented by the Unix kernel or similar @@ -145,7 +145,7 @@ recursive acronyms.

    Status of the project

    -The Hurd, together with the GNU Mach microkernel, the GNU C Library +The Hurd, together with the GNU Mach microkernel, the GNU C Library and the other GNU and non-GNU programs in the GNU system, provide a rather complete and usable operating system today. It is not ready for production use, as there are still many bugs and missing features. diff --git a/install.html b/install.html index fee42941..ad3bf3b0 100644 --- a/install.html +++ b/install.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -26,7 +26,7 @@  
    ChangeLogs

    -The GNU Hurd
    +GNU Hurd
     
    Documentation
    Installation
    @@ -41,7 +41,7 @@ Installation
    Source Code
     
    -MiG
    +GNU MIG
     
    Source Code
     
    @@ -57,7 +57,7 @@

    Latest version

    -The GNU Hurd is under active development. Because of that, there is +The GNU Hurd is under active development. Because of that, there is no `stable' version. We distribute the Hurd sources only through CVS at present.

    diff --git a/mig-download.html b/mig-download.html index 9595a065..48720c38 100644 --- a/mig-download.html +++ b/mig-download.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -25,7 +25,7 @@  
    ChangeLogs

    -The GNU Hurd
    +GNU Hurd
     
    Documentation
    Installation
    @@ -40,7 +40,7 @@ Installation
    Source Code
     
    -MiG
    +GNU MIG
     
    Source Code
     
    @@ -58,17 +58,17 @@

    Latest Release

    -The latest release of MiG is version 1.3, 2002-03-08. It features: +The latest release of MIG is version 1.3, 2002-03-08. It features:

    • Minor bug fixes.
    • The new keyword retcode is accepted as a parameter modifier. This does not do anything, but is accepted for -compatibility with the MiG input syntax used with OSF Mach.
    • +compatibility with the MIG input syntax used with OSF Mach.
    • The debian/ subdirectory of packaging files is now -included in the MiG source distribution.
    • +included in the MIG source distribution.

    -You can download the latest version of MiG from the GNU ftp server: +You can download the latest version of MIG from the GNU ftp server:

    • mig-1.3.tar.gz @@ -80,7 +80,7 @@ HREF="http://ftp.gnu.org/gnu/mig/mig-1.3.tar.gz.sig">mig-1.3.tar.gz.sigCVS repository

      -The MiG source code is managed in the version control system CVS. You can check out the CVS repository through anonymous CVS over SSH with the following instruction set. When prompted for a password for anoncvs, @@ -100,13 +100,13 @@ href="https://savannah.gnu.org/cvs/?group=hurd">savannah page.

      You can also browse the CVS -repository of MiG with your web browser. The web pages are +repository of MIG with your web browser. The web pages are generated dynamically at the time you request them and are always up to date.

      There is also a cross referenced -database of the Hurd, GNU Mach, MiG, and the GNU C library sources +database of the Hurd, GNU Mach, MIG, and the GNU C library sources online for you to browse. It provides better searching and browsing facilities than the online CVS repository, but it is not always up to date and does not contain history information. diff --git a/mig.html b/mig.html index 6811cab5..3f77d28d 100644 --- a/mig.html +++ b/mig.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -27,7 +27,7 @@  
      ChangeLogs

      -The GNU Hurd
      +GNU Hurd
       
      Documentation
      Installation
      @@ -42,7 +42,7 @@ Installation
      Source Code
       
      -MIG
      +GNU MIG
       
      Source Code
       
      @@ -59,22 +59,22 @@


      -

      Introduction to GNU MIG

      +

      Introduction to GNU MIG

      -GNU MIG is the GNU distribution of the Mach 3.0 interface generator `MIG', as -maintained by the GNU Hurd developers for the GNU project. +GNU MIG is the GNU distribution of the Mach 3.0 interface generator `MIG', as +maintained by the GNU Hurd developers for the GNU project.

      The interface generator produces stub code from interface definition (.defs) files. The stub code makes it easy to implement and use Mach interfaces as remote procedure calls (RPC).

      -You need this tool to compile the GNU Mach and GNU Hurd distributions, and to +You need this tool to compile the GNU Mach and GNU Hurd distributions, and to compile the GNU C library for the Hurd. Also, you will need it for other software in the GNU system that uses Mach-based inter-process communication.

      Status of the project

      -MiG 1.3 was released in March 2002, and features compatibility with +MIG 1.3 was released in March 2002, and features compatibility with OSF Mach. diff --git a/old_hurd_faq.html b/old_hurd_faq.html index 00a49827..b310824b 100644 --- a/old_hurd_faq.html +++ b/old_hurd_faq.html @@ -1,10 +1,10 @@ -The Unofficial (and no longer maintained) GNU Hurd FAQ, Version 0.13 +The Unofficial (and no longer maintained) GNU Hurd FAQ, Version 0.13 -

      The Unofficial (and no longer maintained) GNU Hurd FAQ, Version 0.13
      +
      The Unofficial (and no longer maintained) GNU Hurd FAQ, Version 0.13
       
       Contributions by:
       
      @@ -22,7 +22,7 @@ Original Document by: Derek Upham 
       
       Contents:
       
      -Q0.  Where can I get the Unofficial GNU Hurd FAQ?
      +Q0.  Where can I get the Unofficial GNU Hurd FAQ?
       Q1.  What is the Hurd?
       Q2.  Where can I get a copy?
       Q3.  Why bother writing a new OS when we have Linux and 386/BSD?
      @@ -35,7 +35,7 @@ Q9.  What sort of system would we have if the Hurd was bootable today?
       
       ==============================
       
      -Q0.  Where can I get the Unofficial GNU Hurd FAQ?
      +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
      @@ -160,7 +160,7 @@ Q5.  Where can I find more information?
       The June 1995 GNU's Bulletin contains the following official
       information:
       
      -   The GNU Hurd now runs programs native.  We have implemented both
      +   The GNU Hurd now runs programs native.  We have implemented both
          shared libraries using ELF, & the popular `ext2' file system used
          by Linux.  It can run GCC, `make', Emacs, & most other GNU
          utilities.  Progress is being made so rapidly that by the time you
      diff --git a/related-projects.html b/related-projects.html
      index edd896ad..c9928baf 100644
      --- a/related-projects.html
      +++ b/related-projects.html
      @@ -2,7 +2,7 @@
       	"http://www.w3.org/TR/REC-html40/strict.dtd">
       
       
      -The GNU Hurd - GNU Project - Free Software Foundation (FSF)
      +The GNU Hurd - GNU Project - Free Software Foundation (FSF)
       
       
       
      @@ -26,7 +26,7 @@
        
      ChangeLogs

      -The GNU Hurd
      +GNU Hurd
       
      Documentation
      Installation
      @@ -41,7 +41,7 @@ Installation
      Source Code
       
      -MiG
      +GNU MIG
       
      Source Code
       
      @@ -72,11 +72,11 @@ sites.

    • GNU/Hurd on Alpha
    • The purpose of this project is to provide a working implementation of -the GNU Hurd for the Alpha architecture. +the GNU Hurd for the Alpha architecture.
      http://savannah.gnu.org/projects/hurd-alpha/ -

    • The GNU Hurd on top of the L4 microkernel
    • +
    • The GNU Hurd on top of the L4 microkernel
    • The purpose of this project is to port the Hurd system to the L4 microkernel.
      diff --git a/whatsnew.html b/whatsnew.html index f4320291..14ceea3b 100644 --- a/whatsnew.html +++ b/whatsnew.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -31,7 +31,7 @@  
      ChangeLogs

      -The GNU Hurd
      +GNU Hurd
       
      Documentation
      Installation
      @@ -46,7 +46,7 @@ Installation
      Source Code
       
      -MiG
      +GNU MIG
       
      Source Code
       
      @@ -54,9 +54,9 @@


      -

      What is the GNU Hurd?

      +

      What is the GNU Hurd?

      -The GNU Hurd is the GNU project's replacement for the Unix kernel. +The GNU Hurd is the GNU project's replacement for the Unix kernel. The Hurd is a collection of servers that run on the Mach microkernel to implement file systems, network protocols, file access control, and other features that are implemented by the Unix kernel or similar @@ -73,7 +73,7 @@ so that it can be added here.

      27 April 2006
      -

      The GNU Hurd project will participate in this year's +

      The GNU Hurd project will participate in this year's Google Summer of Code, under the aegis of the GNU project.

      The following is a list of items you might want to work on. If you want to @@ -84,12 +84,12 @@ href="/software/hurd/help.html#TOCirc">#hurd IRC channel.

      @@ -195,7 +195,7 @@ Courtès.
      29 July 2005
      Added a Italian translation -of The GNU +of GNU Hurd by Carlo Palma.

      @@ -204,8 +204,8 @@ Hurd by Carlo Palma.
      Added Dutch translations of What's -New and The -GNU Hurd by Roan Embrechts. +New and +GNU Hurd by Roan Embrechts.

      @@ -259,7 +259,7 @@ is now accessible through the Documentation
      Gaël Le Mignot, president of HurdFr, -presented the GNU Hurd on 22 November +presented the GNU Hurd on 22 November 2002 at EpX in Paris. English slides and French slides of the diff --git a/whatsold.html b/whatsold.html index ddad85ac..ace0d66e 100644 --- a/whatsold.html +++ b/whatsold.html @@ -2,7 +2,7 @@ "http://www.w3.org/TR/REC-html40/strict.dtd"> -The GNU Hurd - GNU Project - Free Software Foundation (FSF) +The GNU Hurd - GNU Project - Free Software Foundation (FSF) @@ -24,7 +24,7 @@  
      ChangeLogs

      -The GNU Hurd
      +GNU Hurd
       
      Documentation
      Installation
      @@ -39,7 +39,7 @@ Installation
      Source Code
       
      -MiG
      +GNU MIG
       
      Source Code
      @@ -66,7 +66,7 @@ code to pthreads. The Toronto Hurd Users Group meets again: The University of Waterloo Computer Science Club will -be hosting talks on the GNU Hurd on October 26 by Marcus Brinkmann and +be hosting talks on the GNU Hurd on October 26 by Marcus Brinkmann and Neal Walfield. There will also be a GnuPG keysigning before Marcus's talk. Please email Ryan @@ -93,7 +93,7 @@ at thug@gnu.org

      03 October 2002
      -
      Marcus Brinkmann speaks about the GNU Hurd at "Reflections | +
      Marcus Brinkmann speaks about the GNU Hurd at "Reflections | Projections 2002", the National Student ACM Conference at the University of Urbana-Champaign, Illinois. The @@ -162,7 +162,7 @@ This distribution is only for x86 PC machines. Volunteers interested in ports to other architectures are eagerly sought.

      More information about GNU -Mach 1.3 is available on the GNU Mach web page. +Mach 1.3 is available on the GNU Mach web page.

      @@ -223,14 +223,14 @@ programming!
      08 March 2002
      We are pleased to announce version 1.3 of the GNU distribution of the -Mach 3.0 interface generator `MiG'. It may be found in the file +Mach 3.0 interface generator `MIG'. It may be found in the file http://ftp.gnu.org/gnu/mig/mig-1.3.tar.gz (about 145 KB compressed).

      Diffs from version 1.2 are in http://ftp.gnu.org/gnu/mig/mig-1.2-1.3.diff.gz (about 6 KB compressed, 15 KB uncompressed). Relative to version 1.2, version 1.3 contains only some minor fixes.

      -You need this tool to compile the GNU Mach and Hurd distributions, and +You need this tool to compile the GNU Mach and Hurd distributions, and to compile GNU libc for the Hurd.

      Bug reports relating to this distribution should be sent to @@ -249,7 +249,7 @@ HREF="http://mail.gnu.org/mailman/listinfo/hurd-devel-readers"> Hurd-devel-readers. It is the read-only version of Hurd-devel.

      Hurd-devel is a mailing list for detailed discussions -of design and implementation issues in the GNU Hurd; it is an internal +of design and implementation issues in the GNU Hurd; it is an internal low-volume list restricted to the core developers of the Hurd. While the web-based archive of Hurd-devel has always been public, the new mailing list -- cgit v1.2.3 From f6df5e98f8e251312a42cefbc37414e1256763a2 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Fri, 23 Mar 2007 11:17:36 +0000 Subject: Typo fix by Gumaro Melendez via Yavor Doganov, web-hurd, 2007-03-23. --- hurd-paper.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'hurd-paper.html') diff --git a/hurd-paper.html b/hurd-paper.html index 19ccef2f..22099ef5 100644 --- a/hurd-paper.html +++ b/hurd-paper.html @@ -583,7 +583,7 @@ The terminal driver will probably not provide good support for the high-volume, rapid data transmission required by UUCP or SLIP. Those programs do not need any of its features. -Instead they will be use the +Instead they will be using the underlying Mach device ports for terminals, which support moving large amounts of data efficiently. @@ -798,8 +798,8 @@ send other questions to

      Copyright (C) 1996 Trent Fisher
      -Copyright (C) 1996, 1997, 1998 Free Software Foundation, Inc., -59 Temple Place - Suite 330, Boston, MA 02111, USA +Copyright (C) 1996, 1997, 1998, 2007 Free Software Foundation, Inc., +51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.

      Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.

      -- cgit v1.2.3 From fb815d825bf35be3b2c6b72cae8a86385e247c5c Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Fri, 23 Mar 2007 15:47:41 +0000 Subject: Update to the contact address instead of the webmasters's. Suggested by Yavor Doganov, web-hurd, 2007-03-23. --- acknowledgements.html | 4 ++-- howto/subhurd.html | 2 +- hurd-and-linux.html | 4 ++-- hurd-announcements.html | 4 ++-- hurd-folks.html | 4 ++-- hurd-name.html | 4 ++-- hurd-paper.html | 4 ++-- whatis/translator.html | 2 +- 8 files changed, 14 insertions(+), 14 deletions(-) (limited to 'hurd-paper.html') diff --git a/acknowledgements.html b/acknowledgements.html index 5e04a01d..b7ef5f0c 100644 --- a/acknowledgements.html +++ b/acknowledgements.html @@ -4,7 +4,7 @@ GNU Hurd: Acknowledgements - + @@ -96,7 +96,7 @@ contact the FSF. Please send comments on these web pages to -webmasters@www.gnu.org, +web-hurd@gnu.org, send other questions to gnu@gnu.org.

      diff --git a/howto/subhurd.html b/howto/subhurd.html index 49c48ceb..d3648278 100644 --- a/howto/subhurd.html +++ b/howto/subhurd.html @@ -73,7 +73,7 @@ contact the FSF. Please send comments on these web pages to -webmasters@www.gnu.org, +web-hurd@gnu.org, send other questions to gnu@gnu.org.

      diff --git a/hurd-and-linux.html b/hurd-and-linux.html index e623a3b6..d9181d88 100644 --- a/hurd-and-linux.html +++ b/hurd-and-linux.html @@ -3,7 +3,7 @@ The Hurd and Linux - GNU Project - Free Software Foundation (FSF) - + @@ -82,7 +82,7 @@ FSF & GNU inquiries & questions to Other ways to contact the FSF.

      Comments on these web pages to -webmasters@gnu.org, +web-hurd@gnu.org, send other questions to gnu@gnu.org.

      diff --git a/hurd-announcements.html b/hurd-announcements.html index d4944b57..ab3fbad5 100644 --- a/hurd-announcements.html +++ b/hurd-announcements.html @@ -5,7 +5,7 @@ Hurd Announcements - Free Software Foundation (FSF) - + the FSF. Please send comments on these web pages to -webmasters@www.gnu.org, +web-hurd@gnu.org, send other questions to gnu@gnu.org.

      diff --git a/hurd-folks.html b/hurd-folks.html index 0becf042..14dcaf83 100644 --- a/hurd-folks.html +++ b/hurd-folks.html @@ -2,7 +2,7 @@ GNU Hurd folks - GNU Project - Free Software Foundation (FSF) - +

      GNU Hurd folks

      @@ -60,7 +60,7 @@ FSF & GNU inquiries & questions to Other ways to contact the FSF.

      Comments on these web pages to -webmasters@www.gnu.org, +web-hurd@gnu.org, send other questions to gnu@gnu.org.

      diff --git a/hurd-name.html b/hurd-name.html index 24b9cd9a..946045d1 100644 --- a/hurd-name.html +++ b/hurd-name.html @@ -2,7 +2,7 @@ What the name Hurd means - GNU Project - Free Software Foundation (FSF) - +

      What the name ``Hurd'' means

      @@ -35,7 +35,7 @@ FSF & GNU inquiries & questions to Other ways to contact the FSF.

      Comments on these web pages to -webmasters@www.gnu.org, +web-hurd@gnu.org, send other questions to gnu@gnu.org.

      diff --git a/hurd-paper.html b/hurd-paper.html index 22099ef5..bb49829c 100644 --- a/hurd-paper.html +++ b/hurd-paper.html @@ -2,7 +2,7 @@ Towards a New Strategy of OS Design - +

      Towards a New Strategy of OS Design

      @@ -792,7 +792,7 @@ FSF & GNU inquiries & questions to Other ways to contact the FSF.

      Comments on these web pages to -webmasters@www.gnu.org, +web-hurd@gnu.org, send other questions to gnu@gnu.org.

      diff --git a/whatis/translator.html b/whatis/translator.html index ef2adf32..97a208e1 100644 --- a/whatis/translator.html +++ b/whatis/translator.html @@ -274,7 +274,7 @@ contact the FSF. Please send comments on these web pages to -webmasters@www.gnu.org, +web-hurd@gnu.org, send other questions to gnu@gnu.org.

      -- cgit v1.2.3