K&K Software Lynxviewer

Ergebnis für URL: http://www.gnu.org/software/hurd/

#[1]Edit this page [2]GNU Hurd (RSS feed) [3]GNU Hurd (Atom feed) [4]copyright

GNU Hurd
________________
* [5]Recent Changes
* [6]Preferences

* [7]Edit
* [8]History
* [9]Source
* [10]?Discussion

Welcome to... [11][boxes-redrawn.png] ... the GNU Hurd!
____________________________________________________________________________

* Home
* [12]Community
+ [13]Contact Us
* [14]Donate
* [15]Contributing
+ [16]Public Hurd Boxen
+ [17]QEMU Images
+ [18]Getting Help
+ [19]Project Ideas
+ [20]Open Issues
* [21]Documentation
+ [22]FAQ
____________________________________________________________________________

* [23]Hurd
+ [24]Documentation
+ [25]Running
* [26]Mach
+ [27]Documentation
+ [28]GNU Mach
* [29]MIG
+ [30]Documentation
+ [31]GNU MIG
____________________________________________________________________________

* [32]Debian GNU/Hurd
* [33]GNU System
____________________________________________________________________________

* [34]Hurd NG

What is the GNU Hurd?

The GNU Hurd is the GNU project's replacement for the Unix kernel. It 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 kernels (such as Linux). [35]More detailed.

What is the mission of the GNU Hurd project?

Our mission is to create a general-purpose kernel suitable for the GNU operating
system, which is viable for everyday use, and gives users and programs as much
control over their computing environment as possible. [36]Our mission explained.

Download latest stable release [37]here or [38]browse the Git repository.
____________________________________________________________________________

1. [39]News
2. [40]Contributing
1. [41]Access to a GNU/Hurd System
3. [42]Getting Help
4. [43]Running the Hurd
5. [44]Current Status
1. [45]Advantages and Challenges
____________________________________________________________________________

News

[46]RSS [47]Atom
[48]2024-q1
* [49]Edit
* [50]?Discussion

Hello! Welcome to a new qoth. This qoth covers new and interesting GNU/Hurd
developments in Q1 of 2024! [51]Details.

Etienne Brateau modified console-client to use [52]xkbcommon instead of x11 for
xkb extended support, which improves keyboard layout coverage a lot!

Flavio Cruz also worked on [53]porting GDB to the 64-bit Hurd, implemented
setcontext/getcontext/makecontext/swapcontex () in [54]glibc, and [55]implemented
child process resource accounting. The latter
implementsgetrusage(RUSAGE_CHILDREN, ) and populates child related data in
times().

He fixed the [56]perl testsuite for the Hurd, and he also posted a [57]RFC to
enhance tracing utilities, which he used to port the RPC format to 64 bit.

Flavio also had a smattering of fixes [58]here, [59]here, [60]here, [61]here, and
[62]here.

Damien Zammit had some fixes including [63]fixing the console with APIC enabled,
[64]patching GNU Mach to support ACPI v2, [65]fixing baud rate on com ports,
[66]porting the Hurd to some AMD CPUs (WIP), [67]adding HPET (high precision
timers). He also worked on making ext2fs [68]use xattr by default to store
translators.

Damien also worked on more SMP fixes [69]here, [70]here, [71]here, [72]here,
[73]here, and [74]here. Hurd currently boots in SMP mode on the BSP. Damien wrote
a test program that lets you run a [75]task on the APs.

Sergey Bugaev [76]patched binutils to support the GNU/Hurd on AArch64, and he
wrote some patches to make the Hurd easier to port [77]here, [78]here, and
[79]here,

Sergey also posted a fairly large [80]RFC patch series for his AArch64 port. He
writes:
MIG seems to just work (thanks to all of Flávio's work!). I'm using
the same message ABI as on x86_64, and haven't seen any issues so far
-- neither compiler errors / failed static assertions (about struct
sizes and such), nor hardware errors from misaligned accesses.

He also mentions that "the hardware hardening features (BTI, MTE, PAC) are
currently 'not really supported', but I do want to support them in the future".
Samuel merged [81]many [82]of [83]the [84]patches.

In Sergey's later glibc patch series, he wrote about the [85]AArch64 port
progress. He wrote:
Last time, there was no AArch64 port of GNU Mach, and so the only testing
I have done was running a simple statically-linked executable on Linux under
GDB, which, nevertheless, helped me identify and fix a number of issues.

Since then, however, I have been (some may say, relentlessly) working on
filling in the missing piece, namely porting GNU Mach (with important help &
contributions by Luca D.). I am happy to report that we now have an
experimental port of GNU Mach that builds and works on AArch64! While that may
sound impressive, note that various things about it are in an extremely basic,
proof-of-concept state rather than being seriously production-ready; and also
that Mach is a small kernel (indeed, a microkernel), and it was designed from
the start (back in the 80s) to be portable, so most of the "buisness logic"
functionality (virtual memory, IPC, tasks/threads/scheduler) is explicitly
arch-independent.

Despite the scary "WIP proof-of-concept" status, there is enough
functionality in Mach to run userland code, handle exceptions and
syscalls, interact with the MMU to implement all the expected virtual
memory semantics, schedule/switch tasks and threads, and so on.
Moreover, all of GNU Mach's userspace self-tests pass!

This meant there was enough things in place for me to try running
glibc on it, and the amazing thing is my simple test executable, the
same one I previously tested on Linux with GDB, just worked on real
Mach without me having to make any additional changes to the glibc
side, or even recompile it.

But I did not stop there, and I got several of the core Hurd servers
working! Namely, these are ext2fs, exec, startup, auth, and proc
servers. All of them but ext2fs are dynamically linked; ld
aarch64.so.1 sucessfully locates and maps the programs themselves
and their required dependencies, and Mach pages in code and data
pages from ext2fs as they are accessed, transparently to the
program, just as one would expect it to.

Be sure to read more from his announcement [86]email.

Sergey also announced [87]a new Alpine distro based on Hurd (it currently does
not have a name). His goal is to add another Hurd distribution, which will force
the Hurd to work with different software and hopefully fix more bugs. Alpine
Linux also usually runs the latest software, so this new Hurd distribution will
be for those who like living on the bleeding edge. He writes:
I have ported many Alpine packages to build with (i386, for now) GNU
Mach, the Hurd, and glibc, replacing Linux and musl. If you want a
specific number: as of yesterday, I have 299 installable packages; the
number of source packages is of course several times less than that.
Still, this includes things like curl, ncurses, nano, native binutils
& gcc & mig, libffi, openrc, openssl, util-linux, busybox, apk-tools,
... and of course gnumach, hurd (with dependencies like libdaemon,
parted, ...), and glibc. Importantly, all this cleanly bootstraps
using the scripts/bootstrap.sh script that they provide; this is too
somewhat like Flávio's scripts, but it uses the real full Alpine
package definitions for e.g. GCC (patched by me for glibc / Hurd
support).

Above the kernel and libc, things remain much as they were in upstream
Alpine: the system boots (will boot -- I haven't tried it yet) with
busybox init & OpenRC, and uses busybox as its basic userland. GNU
software such as Bash is installable, too.

This new Hurd distribution currently does not have a mailing list, irc room, or
website. If you are interesting in helping Sergei to develop it further, then
please email bug-hurd@gnu.org.

Luca Dariz added [88]userspace tests, which work with qemu. We currently test the
Hurd in qemu on a GNU/Linux host. He also described how [89]he currently uses the
64-bit Hurd. Perhaps you should follow that advice if you want to try running a
64-bit Hurd on qemu.

Manolo de Medici made a WIP patch series that gets [90]qemu to run on the Hurd.

I organized a belated GNU/Hurd Christmas party. We had 6 or 7 attenders, which
was pretty awesome! I was not able to record the event, so perhaps we should try
for another meet perhaps at the end of Q2. If you would like to help me
plan/organize/join such a party, then please email bug-hurd@gnu.org.

If you want to test if your favorite packages work on the Hurd and contribute
towards making the full GNU system usable for a wider range of people, please
[91]check the contributing page.
____________________________________________________________________________

GNU Mach is the microkernel upon which a GNU Hurd system is based. It provides an
Inter Process Communication (IPC) mechanism that the Hurd uses to define
interfaces for implementing in a distributed multi-server fashion the services a
traditional operating system kernel provides. [93]More detailed.
[94]2023-q4
* [95]Edit
* [96]?Discussion

Hello! Welcome to a new qoth. This qoth covers new and interesting GNU/Hurd
developments in Q4 of 2023! [97]Details.

Samuel Thibault fixed gcc's Hurd's default pie and [98]added static pie support.
He also added a [99]whatis command to GNU Mach's kernel debugger, which can
determine what an address points to (a stack? a port? some kalloc? ...). He also
added [100]hurd-amd64 support to GCC.

Samuel requested that the Hurd team set up a [101]continuous integration, so that
when developers make code changes, they can be certain that they did not break
anything. It turns out that the Hurd supports several different environments: 32
bit, 64 bit, 32-on-64 bit, ACPI, non-ACPI, SMP, non-SMP, Xen, etc. Apparently
Flavio has a [102]personal CI, but it is set up in a Debian independent way. If
you are interested in helping the Hurd project set up a CI, then please get in
touch!

Luca Dariz worked on adding [103]some simple GNU Mach user-space tests . With a
working MiG, a GNU/Linux machine can run make check in the GNU Mach source code,
which will launch qemu to ensure that 32 bit (PAE and non PAE), 32 on 64 bit, and
full 64 bit GNU Mach works. We currently do this testing on GNU/Linux, because
qemu does not run on the Hurd.

Many people worked on the Hurd's new [104]x86_64 bit support. A 64-bit debian
buildd is set up, and we can bootstrap a chroot! The hurd-amd64 wanna-build
infrastructure is also set up. We are having issues reliably building packages on
a 64-bit Hurd, which lead Samuel to uncover and fix [105]a proc leak.

Flavio Cruz [106]improved GNU Mach's IPC by reordering mach_msg_type_t fields to
byte align msgt_name and msgt_size. He also created a patch series to [107]avoid
message resizing for x86_64. He also [108]removed untyped mach RPC code. GNU Mach
uses typed IPC. The Hurd could support both typed and untyped, but it appears
that the Hurd only uses typed RPC. So it seems best to remove any untyped RPC
code.

Sergey Bugaev added [109]GNU Mach entry re-coalescing support. Essentially, Mach
was not always able to merge two vm entries that are made next to each other,
which was slowing down ext2, bash, etc. Sergey allowed GNU Mach to merge entries
in the common cases, which greatly helps ext2fs for instance.

Sergey is also working on [110]porting the Ladybird web browser to the Hurd. The
author of this post uses the [111]netsurf web browser on the Hurd, which works on
simple websites like wikipedia, but it badly renders javascript heavy websites,
which makes many websites un-useable. If Sergey is successful in porting
[112]Ladybird, then Hurd users could start using sites like Github! It is worth
noting that someone should update the [113]Firefox port as well.

Sergey also started [114]porting the Hurd to AArch64! While a port to RISC-V
might be more exciting, it is worth mentioning that AArch64 is more established.
What is interesting is that Sergey is already able to build Hurd servers for
AArch64! Normally, in order to run the binaries, one would port GNU Mach to
AArch64. Luckily for us, he turned to GDB and directly ran a 'Hello World' Hurd
AArch64 binary on Linux! This helped him fix some bugs along the way. We still
need to define the ABI and complete the GNU Mach port, but this is exciting news!

Tobias Platen started [115]porting GNU Mach to Power9.

So if you want to test if your favorite packages work on the Hurd and contribute
towards making the full GNU system usable for a wider range of people, please
[116]check the contributing page.
____________________________________________________________________________

GNU Mach is the microkernel upon which a GNU Hurd system is based. It provides an
Inter Process Communication (IPC) mechanism that the Hurd uses to define
interfaces for implementing in a distributed multi-server fashion the services a
traditional operating system kernel provides. [118]More detailed.
[119]2023-q3
* [120]Edit
* [121]?Discussion

Hello! Welcome to a new qoth. This qoth covers new and interesting GNU/Hurd
developments in Q3 of 2023! [122]Details.

Joan Lledo modified the PCI arbiter to prevent mapping I/O region files. He
previously sent some patches to implement mapping region and ROM files using
mmap(). However, a BAR region can represent either memory or I/O space, and only
memory should be allowed to be mapped. Since I/O BARs only contain I/O addresses,
he went ahead and [123]prevented the mapping of I/O region files. The next step
is to make IO spaces available for users through the pci-arbiter. He plans to add
a new RPC that checks for permission and calls i386_io_perm_create(). Then it
returns the resulting port.

Our Google summer of code student Vedant Tewari decided to port rust, and the
rust porting effort is making good progress. [124]The build process is a bit
wonky, and Debian is using an older rust version. Check out [125]the rust pull
request that adds Hurd support!

[126]Samuel worked on setting up [127]PAE, which will eventually let us use more
than 4GB of RAM on a 32-bit Hurd! It is also useful for the X86_64 architecture.
He also fixed the [128]jemalloc build.

Samuel was incredibly productive this quarter making the X86_64 bit port more
stable. He fixed the 64-bit Hurd [129]PIE build, and he got [130]git working on
the 64-bit port! Though a few of the [131]git tests are failing on both X86_64
and the 32 bit port. He fixed the [132]glibc build, which involved fixing
pmap_remove and pmap_protect. He discovered that [133]core dumping is currently
causing problems on the 64-bit port, and he temporarily encourages people to
disable core dumping. Samuel fixed some [134]networking issues and a [135]dpkg
issue for the 64-bit port. It was hard to discover what the problem was, because
the debugging tools have not been ported to the 64-bit port. He add some helpers
to locking to fix some bugs, and he encourages other developers to help him fix
the debugging tools for X86-64. It seems that most developers are currently
running the 64-bit Hurd in a virtual machine and not in real hardware.

Luca Dariz got a patch series merged [136]for [137]the [138]64 [139]bit
[140]port.

Sergey implemented [141]MAP_EXCL and provided MAP_FIXED_NOREPLACE and
MAP_TRYFIXED as aliases of (MAP_FIXED|MAP_EXCL) as well other mmap work. He
explains:

MAP_FIXED is defined to silently replace any existing mappings at the address
range being mapped over. However, this is dangerous and only rarely desired
behavior.

Various Unix systems provide replacements or additions to MAP_FIXED.
* SerenityOS and Linux provide MAP_FIXED_NOREPLACE. If the address space
already contains a mapping in the requested range, Linux returns EEXIST.
SerenityOS returns ENOMEM, however that is a bug, as the MAP_FIXED_NOREPLACE
implementation is intended to be compatible with Linux.
* DragonFly BSD, NetBSD, and OpenBSD provide MAP_TRYFIXED, but with different
semantics. DragonFly BSD returns ENOMEM if the requested range already
contains existing mappings. NetBSD does not return an error, but instead
creates the mapping at a different address if the requested range contains
mappings. OpenBSD behaves the same, but also notes that this is the default
behavior even without MAP_TRYFIXED (which is the case on the Hurd too).

Since the Hurd leans closer to the BSD side, add MAP_EXCL as the primary API
to request the behavior of not replacing existing mappings. Declare
MAP_FIXED_NOREPLACE and MAP_TRYFIXED as aliases of (MAP_FIXED|MAP_EXCL), so
any existing software that checks for either of those macros will pick them up
automatically. For compatibility with Linux, return EEXIST if a mapping
already exists.

Damien Zammit added a USB mass storage translator via [142]rumpusbdisk. Though it
has some issues as he explains:

Netdde sneems to exhibit a bug when running ifdown /dev/eth0 simultanously to
running the rumpusbdisk translator, because to the two devices share the same
IRQ.

Damien also worked on the Hurd's SMP support (much of his SMP contributions is
based on the earlier work done by Almudena Garcia):
* He tweaked [143]GNU Mach's scheduler, and he merged [144]three [145]GNU Mach
[146]commits.
* He added a [147]show all runqs command to GNU Mach's kernel debugger.
* He also [148]improved SMP in GNU Mach by storing the struct processor in a
percpu area and avoiding an expensive cpu_number every call of
current_processor(), as well as getting the cpu_number from an offset in the
percpu area. Further improvements can be made by using other percpu areas. It
was untested on 64 bit.
* Damien also taught GNU Mach to use the x86 CPUID instruction to get the
[149]CPU ID for speed. He reduced the time it takes to get the CPUID. He made
it 100 times faster!
* He mentioned [150]some [151]issues: 60% of the time, booting a 32 bit Hurd,
with SMP enabled, fails to boot (sometimes apparently getting stuck in the
rumpdisk). When it does boot, it is not particularly stable and likely to
crash.

Essentially, the SMP work is progressing, but it is not ready for production use.
His recent work made the non-SMP faster, and a 32 bit Hurd, with SMP enabled and
only one core, [152]appears relatively stable (but slow to boot). The [153]32-bit
SMP enabled Hurd may soon be as fast as the non-SMP Hurd. Eventually the SMP
enabled Hurd will be faster than a non-SMP Hurd.

Flavio Cruz halved the size of mach_msg_type_long_t, from 16 to 8 bytes. He also
[154]simplified the overall 64bit RPC ABI, removing "holes" in mach_msg_type_t or
mach_msg_type_long_t, which prevents possible leakages to userspace.

Some Hurd people talked to Kent Overstreet, the author of [155]bcachefs to
discuss the possibility of porting Linux's newest filesystem to the Hurd; the
conversation [156]was recorded. While most Hurd developers believe that it would
possible to port bcachefs to the Hurd, all agree that it would be difficult to
port and hard to maintain. No Hurd developers are currently planning or working
on porting bcachefs to the Hurd. But perhaps you want to?

So if you want to test if your favorite packages work on the Hurd and contribute
towards making the full GNU system usable for a wider range of people, please
[157]check the contributing page.
____________________________________________________________________________

GNU Mach is the microkernel upon which a GNU Hurd system is based. It provides an
Inter Process Communication (IPC) mechanism that the Hurd uses to define
interfaces for implementing in a distributed multi-server fashion the services a
traditional operating system kernel provides. [159]More detailed.
[160]2023-06-11-debian gnu hurd 2023
* [161]Edit
* [162]?Discussion

Debian GNU/Hurd 2023 released! [163]Details.

It is with huge pleasure that the Debian GNU/Hurd team announces the release of
Debian GNU/Hurd 2023.

This is a snapshot of Debian "sid" at the time of the stable Debian "bookworm"
release (June 2023), so it is mostly based on the same sources. It is not an
official Debian release, but it is an official [164]Debian GNU/Hurd port release.

Read the [165]announcement email.
____________________________________________________________________________

GNU Mach is the microkernel upon which a GNU Hurd system is based. It provides an
Inter Process Communication (IPC) mechanism that the Hurd uses to define
interfaces for implementing in a distributed multi-server fashion the services a
traditional operating system kernel provides. [167]More detailed.
[168]2021-08-14-debian gnu hurd 2021
* [169]Edit
* [170]?Discussion

Debian GNU/Hurd 2021 released! [171]Details.

It is with huge pleasure that the Debian GNU/Hurd team announces the release of
Debian GNU/Hurd 2021.

This is a snapshot of Debian "sid" at the time of the stable Debian "bullseye"
release (August 2021), so it is mostly based on the same sources. It is not an
official Debian release, but it is an official [172]Debian GNU/Hurd port release.

Read the [173]announcement email.
____________________________________________________________________________

Older news entries can be found in the [176]news archive. For Hurd developers'
musings have a look at the [177]shared weblog. The [178]?@ recent changes page
lists the latest changes of this website.
____________________________________________________________________________

Contributing

So, you are interested in contributing to the GNU Hurd project? Welcome! Every
single contribution is very much encouraged. Please read our [179]detailed
recommendations about how to contribute.

See our [180]source repositories for the source code.

Access to a GNU/Hurd System

We provide accounts on our [181]public Hurd boxen, and there are also several
GNU/Hurd [182]Distributions that allow for [183]QEMU emulation.
____________________________________________________________________________

Getting Help

There are a couple of different [184]FAQ lists. There are a number of [185]IRC
channels and several different [186]mailing lists with searchable archives.

Before asking a question on a mailing list or on IRC, first, please try to answer
your own question using a search engine and reading the introductory information.
If you have done this and you cannot find the answer to your question, feel free
to ask on a mailing list or on IRC.
____________________________________________________________________________

Running the Hurd

The most functional distribution of the Hurd is the one provided by Debian. Find
more information about it at the [187]Debian GNU/Hurd website.

Along with it there are [188]various ways to run a GNU/Hurd system. Three of them
are
* Installing a [189]GNU/Hurd distribution,
* Running it [190]in Xen and
* Starting a Hurd [191]QEMU image or [192]LiveCD.

And these web pages are a living proof of the usability of the Hurd, as they are
rendered on a [193]Debian GNU/Hurd system.
____________________________________________________________________________

Current Status

The latest GNU releases are Hurd 0.9, Mach 1.8, and MIG 1.8 [194](Release Notes),
2016-12-18.

The Hurd is developed by [195]a few volunteers in their spare time. The project
welcomes any assistance [196]you can provide. Porting and development expertise
is still badly needed in many key areas.

Functional systems are installable in a dual-boot configuration. Development
systems are currently mostly based on the [197]Debian GNU/Hurd port sponsored by
the [198]Debian project.

Aside from this Wiki, community resources for related projects focus around
[199]gnu.org, the [200]mailing lists, and the [201]IRC channels.

If you want to see the current discussions in the Hurd project, please have a
look at the [202]bug-hurd mailinglist archives. If you want to have a look at the
current coding work, you can just head over to our [203]source repositories.

For more details, please read our writeup on the [204]current state of the GNU
Hurd.

Advantages and Challenges

The GNU Hurd operating system design provides [205]advantages, but uncovers new
[206]challenges, too.
____________________________________________________________________________

These pages are powered by [207]ikiwiki.

Further information about this site and how it was created can be found in the
[208]colophon.
Links: [209]sidebar

[211]GFDL 1.2+

Permission is granted to copy, distribute and/or modify this document under the
terms of the GNU Free Documentation License, Version 1.2 or any later version
published by the Free Software Foundation; with no Invariant Sections, no
Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in
the section entitled [212]GNU Free Documentation License.
Last edited 2021-03-20 19:20:52 UTC

References

1. https://darnassus.sceen.net/cgi-bin/hurd-web?do=edit&page=index
2. http://www.gnu.org/software/hurd/index.rss
3. http://www.gnu.org/software/hurd/index.atom
4. http://www.gnu.org/software/hurd/#pagecopyright
5. http://www.gnu.org/software/hurd/recent_changes.html
6. https://darnassus.sceen.net/cgi-bin/hurd-web?do=prefs
7. https://darnassus.sceen.net/cgi-bin/hurd-web?do=edit&page=index
8. https://darnassus.sceen.net/cgit/hurd-web.git/log/index.mdwn
9. https://darnassus.sceen.net/cgi-bin/hurd-web?do=getsource&page=index
10. https://darnassus.sceen.net/cgi-bin/hurd-web?do=create&from=index&page=Discussion
11. http://www.gnu.org/software/hurd/logo.html
12. http://www.gnu.org/software/hurd/community.html
13. http://www.gnu.org/software/hurd/contact_us.html
14. http://www.gnu.org/software/hurd/donate.html
15. http://www.gnu.org/software/hurd/contributing.html
16. http://www.gnu.org/software/hurd/public_hurd_boxen.html
17. http://www.gnu.org/software/hurd/hurd/running/qemu.html
18. http://www.gnu.org/software/hurd/getting_help.html
19. http://www.gnu.org/software/hurd/community/gsoc/project_ideas.html
20. http://www.gnu.org/software/hurd/open_issues.html
21. http://www.gnu.org/software/hurd/documentation.html
22. http://www.gnu.org/software/hurd/faq.html
23. http://www.gnu.org/software/hurd/hurd.html
24. http://www.gnu.org/software/hurd/hurd/documentation.html
25. http://www.gnu.org/software/hurd/hurd/running.html
26. http://www.gnu.org/software/hurd/microkernel/mach.html
27. http://www.gnu.org/software/hurd/microkernel/mach/documentation.html
28. http://www.gnu.org/software/hurd/microkernel/mach/gnumach.html
29. http://www.gnu.org/software/hurd/microkernel/mach/mig.html
30. http://www.gnu.org/software/hurd/microkernel/mach/mig/documentation.html
31. http://www.gnu.org/software/hurd/microkernel/mach/mig/gnu_mig.html
32. http://www.gnu.org/software/hurd/hurd/running/debian.html
33. http://www.gnu.org/software/hurd/hurd/running/gnu.html
34. http://www.gnu.org/software/hurd/hurd/ng.html
35. http://www.gnu.org/software/hurd/hurd/documentation.html
36. http://www.gnu.org/software/hurd/community/weblogs/antrik/hurd-mission-statement.html
37. https://ftp.gnu.org/gnu/hurd/hurd-0.9.tar.gz
38. https://git.savannah.gnu.org/cgit/hurd
39. http://www.gnu.org/software/hurd/#index1h1
40. http://www.gnu.org/software/hurd/#index2h1
41. http://www.gnu.org/software/hurd/#index1h2
42. http://www.gnu.org/software/hurd/#index3h1
43. http://www.gnu.org/software/hurd/#index4h1
44. http://www.gnu.org/software/hurd/#index5h1
45. http://www.gnu.org/software/hurd/#index2h2
46. http://www.gnu.org/software/hurd/index.rss
47. http://www.gnu.org/software/hurd/index.atom
48. http://www.gnu.org/software/hurd/news/2024-q1.html
49. https://darnassus.sceen.net/cgi-bin/hurd-web?do=edit&page=news%2F2024-q1
50. https://darnassus.sceen.net/cgi-bin/hurd-web?do=create&from=news%2F2024-q1&page=Discussion
51. http://www.gnu.org/software/hurd/#news-2024-q1.full-news
52. https://lists.gnu.org/archive/html/bug-hurd/2024-03/msg00060.html
53. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00147.html
54. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00106.html
55. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00098.html
56. https://lists.gnu.org/archive/html/bug-hurd/2024-03/msg00021.html
57. https://lists.gnu.org/archive/html/bug-hurd/2024-03/msg00034.html
58. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00219.html
59. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00091.html
60. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00151.html
61. https://lists.gnu.org/archive/html/bug-hurd/2024-03/msg00008.html
62. https://lists.gnu.org/archive/html/bug-hurd/2024-03/msg00068.html
63. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00277.html
64. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00278.html
65. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00176.html
66. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00220.html
67. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00039.html
68. https://lists.gnu.org/archive/html/bug-hurd/2024-03/msg00012.html
69. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00016.html
70. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00021.html
71. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00051.html
72. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00063.html
73. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00079.html
74. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00124.html
75. https://lists.gnu.org/archive/html/bug-hurd/2024-02/msg00088.html
76. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00000.html
77. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00002.html
78. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00063.html
79. https://lists.gnu.org/archive/html/bug-hurd/2024-03/msg00100.html
80. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00022.html
81. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00050.html
82. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00051.html
83. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00052.html
84. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00062.html
85. https://lists.gnu.org/archive/html/bug-hurd/2024-03/msg00114.html
86. https://lists.gnu.org/archive/html/bug-hurd/2024-03/msg00114.html
87. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00180.html
88. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00125.html
89. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00047.html
90. https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00153.html
91. http://www.gnu.org/software/hurd/contributing.html
92. http://www.gnu.org/software/hurd/hurd/documentation.html
93. http://www.gnu.org/software/hurd/microkernel/mach/gnumach.html
94. http://www.gnu.org/software/hurd/news/2023-q4.html
95. https://darnassus.sceen.net/cgi-bin/hurd-web?do=edit&page=news%2F2023-q4
96. https://darnassus.sceen.net/cgi-bin/hurd-web?do=create&from=news%2F2023-q4&page=Discussion
97. http://www.gnu.org/software/hurd/#news-2023-q4.full-news
98. https://lists.gnu.org/archive/html/bug-hurd/2023-10/msg00061.html
99. https://lists.gnu.org/archive/html/bug-hurd/2023-10/msg00007.html
100. https://lists.debian.org/debian-hurd/2023/11/msg00039.html
101. https://lists.gnu.org/archive/html/bug-hurd/2023-12/msg00007.html
102. https://github.com/flavioc/cross-hurd/actions/runs/7080757561
103. https://lists.gnu.org/archive/html/bug-hurd/2023-10/msg00031.html
104. https://lists.gnu.org/archive/html/bug-hurd/2023-10/msg00036.html
105. https://lists.gnu.org/archive/html/bug-hurd/2023-11/msg00035.html
106. https://lists.gnu.org/archive/html/bug-hurd/2023-11/msg00033.html
107. https://lists.gnu.org/archive/html/bug-hurd/2023-11/msg00028.html
108. https://lists.gnu.org/archive/html/bug-hurd/2023-11/msg00026.html
109. https://darnassus.sceen.net/~hurd-web/open_issues/gnumach_vm_map_entry_forward_merging/
110. https://lists.gnu.org/archive/html/bug-hurd/2023-11/msg00013.html
111. https://www.netsurf-browser.org/
112. https://ladybird.dev/
113. https://lists.debian.org/debian-hurd/2014/09/msg00070.html
114. https://lists.gnu.org/archive/html/bug-hurd/2023-12/msg00110.html
115. https://lists.gnu.org/archive/html/bug-hurd/2023-10/msg00021.html
116. http://www.gnu.org/software/hurd/contributing.html
117. http://www.gnu.org/software/hurd/hurd/documentation.html
118. http://www.gnu.org/software/hurd/microkernel/mach/gnumach.html
119. http://www.gnu.org/software/hurd/news/2023-q3.html
120. https://darnassus.sceen.net/cgi-bin/hurd-web?do=edit&page=news%2F2023-q3
121. https://darnassus.sceen.net/cgi-bin/hurd-web?do=create&from=news%2F2023-q3&page=Discussion
122. http://www.gnu.org/software/hurd/#news-2023-q3.full-news
123. https://lists.gnu.org/archive/html/bug-hurd/2023-07/msg00041.html
124. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00091.html
125. https://github.com/rust-lang/rust/pull/115230
126. http://www.gnu.org/software/hurd/user/samuelthibault.html
127. https://en.wikipedia.org/wiki/Physical_Address_Extension
128. https://lists.debian.org/debian-hurd/2023/08/msg00000.html
129. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00040.html
130. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00059.html
131. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00069.html
132. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00064.html
133. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00068.html
134. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00027.html
135. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00058.html
136. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00000.html
137. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00001.html
138. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00002.html
139. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00003.html
140. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00004.html
141. https://lists.gnu.org/archive/html/bug-hurd/2023-07/msg00010.html
142. https://lists.gnu.org/archive/html/bug-hurd/2023-07/msg00025.html
143. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00084.html
144. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00080.html
145. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00010.html
146. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00018.html
147. https://lists.gnu.org/archive/html/bug-hurd/2023-09/msg00072.html
148. https://lists.gnu.org/archive/html/bug-hurd/2023-09/msg00048.html
149. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00056.html
150. https://lists.gnu.org/archive/html/bug-hurd/2023-09/msg00075.html
151. https://lists.gnu.org/archive/html/bug-hurd/2023-09/msg00046.html
152. https://lists.gnu.org/archive/html/bug-hurd/2023-09/msg00046.html
153. https://lists.gnu.org/archive/html/bug-hurd/2023-09/msg00074.html
154. https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00049.html
155. https://bcachefs.org/
156. https://lists.gnu.org/archive/html/bug-hurd/2023-09/msg00073.html
157. http://www.gnu.org/software/hurd/contributing.html
158. http://www.gnu.org/software/hurd/hurd/documentation.html
159. http://www.gnu.org/software/hurd/microkernel/mach/gnumach.html
160. http://www.gnu.org/software/hurd/news/2023-06-11-debian_gnu_hurd_2023.html
161. https://darnassus.sceen.net/cgi-bin/hurd-web?do=edit&page=news%2F2023-06-11-debian_gnu_hurd_2023
162. https://darnassus.sceen.net/cgi-bin/hurd-web?do=create&from=news%2F2023-06-11-debian_gnu_hurd_2023&page=Discussion
163. http://www.gnu.org/software/hurd/#news-2023-06-11-debian-gnu-hurd-2023.full-news
164. http://www.gnu.org/software/hurd/hurd/running/debian.html
165. https://lists.gnu.org/archive/html/bug-hurd/2023-06/msg00038.html
166. http://www.gnu.org/software/hurd/hurd/documentation.html
167. http://www.gnu.org/software/hurd/microkernel/mach/gnumach.html
168. http://www.gnu.org/software/hurd/news/2021-08-14-debian_gnu_hurd_2021.html
169. https://darnassus.sceen.net/cgi-bin/hurd-web?do=edit&page=news%2F2021-08-14-debian_gnu_hurd_2021
170. https://darnassus.sceen.net/cgi-bin/hurd-web?do=create&from=news%2F2021-08-14-debian_gnu_hurd_2021&page=Discussion
171. http://www.gnu.org/software/hurd/#news-2021-08-14-debian-gnu-hurd-2021.full-news
172. http://www.gnu.org/software/hurd/hurd/running/debian.html
173. https://lists.debian.org/debian-hurd/2021/08/msg00040.html
174. http://www.gnu.org/software/hurd/hurd/documentation.html
175. http://www.gnu.org/software/hurd/microkernel/mach/gnumach.html
176. http://www.gnu.org/software/hurd/news.html
177. http://www.gnu.org/software/hurd/community/weblogs.html
178. https://darnassus.sceen.net/cgi-bin/hurd-web?do=create&from=index&page=__64___recent_changes
179. http://www.gnu.org/software/hurd/contributing.html
180. http://www.gnu.org/software/hurd/source_repositories.html
181. http://www.gnu.org/software/hurd/public_hurd_boxen.html
182. http://www.gnu.org/software/hurd/hurd/running/distrib.html
183. http://www.gnu.org/software/hurd/hurd/running/qemu.html
184. http://www.gnu.org/software/hurd/faq.html
185. http://www.gnu.org/software/hurd/irc.html
186. http://www.gnu.org/software/hurd/mailing_lists.html
187. http://www.debian.org/ports/hurd/hurd-install
188. http://www.gnu.org/software/hurd/hurd/running.html
189. http://www.gnu.org/software/hurd/hurd/running/distrib.html
190. http://www.gnu.org/software/hurd/microkernel/mach/gnumach/ports/xen.html
191. http://www.gnu.org/software/hurd/hurd/running/qemu.html
192. http://www.gnu.org/software/hurd/hurd/running/live_cd.html
193. http://www.gnu.org/software/hurd/hurd/running/debian.html
194. http://www.gnu.org/software/hurd/news/2016-12-18-releases.html
195. http://www.gnu.org/software/hurd/faq/how_many_developers.html
196. http://www.gnu.org/software/hurd/contributing.html
197. http://www.gnu.org/software/hurd/hurd/running/debian.html
198. http://www.debian.org/
199. https://hurd.gnu.org/
200. http://www.gnu.org/software/hurd/mailing_lists.html
201. http://www.gnu.org/software/hurd/irc.html
202. http://lists.gnu.org/pipermail/bug-hurd/
203. http://www.gnu.org/software/hurd/source_repositories.html
204. http://www.gnu.org/software/hurd/hurd/status.html
205. http://www.gnu.org/software/hurd/advantages.html
206. http://www.gnu.org/software/hurd/challenges.html
207. http://ikiwiki.info/
208. http://www.gnu.org/software/hurd/colophon.html
209. http://www.gnu.org/software/hurd/sidebar.html
210. https://www.fsf.org/
211. http://www.gnu.org/software/hurd/#index.license
212. http://www.gnu.org/software/hurd/fdl.html

Usage: http://www.kk-software.de/kklynxview/get/URL
e.g. http://www.kk-software.de/kklynxview/get/http://www.kk-software.de
Errormessages are in German, sorry ;-)