summaryrefslogtreecommitdiff
path: root/community
diff options
context:
space:
mode:
Diffstat (limited to 'community')
-rw-r--r--community/gsoc/project_ideas/tcp_ip_stack.mdwn2
-rw-r--r--community/gsoc/project_ideas/xmlfs.mdwn2
-rw-r--r--community/weblogs/ArneBab/technical-advantages-of-the-hurd.mdwn13
3 files changed, 13 insertions, 4 deletions
diff --git a/community/gsoc/project_ideas/tcp_ip_stack.mdwn b/community/gsoc/project_ideas/tcp_ip_stack.mdwn
index 28c95626..99befbf7 100644
--- a/community/gsoc/project_ideas/tcp_ip_stack.mdwn
+++ b/community/gsoc/project_ideas/tcp_ip_stack.mdwn
@@ -19,7 +19,7 @@ lwip as a complete replacement for pfinet. However, lwip uses the netdde device
drivers for wireless chips, which are old drivers from an old version of linux. To use
lwip for a wifi connection on more modern hardware, one would also need modern
device drivers to access the internet. The promising approach to this is using
-a rump kernel. This is essentially the New Driver Framework google summer of
+[[hurd/rump/rumpnet]]. This is essentially the [[New Driver Framework|community/gsoc/project_ideas/driver_glue_code]] google summer of
code project idea. Hopefully, one day soon the Hurd project will completely replace pfinet
with lwip.
diff --git a/community/gsoc/project_ideas/xmlfs.mdwn b/community/gsoc/project_ideas/xmlfs.mdwn
index 5e5eaa13..41c0b018 100644
--- a/community/gsoc/project_ideas/xmlfs.mdwn
+++ b/community/gsoc/project_ideas/xmlfs.mdwn
@@ -15,7 +15,7 @@ different format. This is a very powerful ability: it allows using standard
tools on all kinds of data, and combining existing components in new ways, once
you have the necessary translators.
-A typical example for such a translator would be xmlfs: a translator that
+A typical example for such a translator would be [[hurd/translator/xmlfs]]: a translator that
presents the contents of an underlying XML file in the form of a directory
tree, so it can be studied and edited with standard filesystem tools, or using
a graphical file manager, or to easily extract data from an XML file in a
diff --git a/community/weblogs/ArneBab/technical-advantages-of-the-hurd.mdwn b/community/weblogs/ArneBab/technical-advantages-of-the-hurd.mdwn
index 35e55518..b2fa5585 100644
--- a/community/weblogs/ArneBab/technical-advantages-of-the-hurd.mdwn
+++ b/community/weblogs/ArneBab/technical-advantages-of-the-hurd.mdwn
@@ -15,13 +15,22 @@ The filesystem implements stuff like Gnome VFS (gvfs) and KDE **network transpar
One practical advantage of this is that the following works:
- settrans -a ftp\: /hurd/hostmux /hurd/ftpfs /
- dpkg -i ftp://ftp.gnu.org/path/to/*.deb
+ $ settrans -a ftp\: /hurd/hostmux /hurd/ftpfs /
+ $ dpkg -i ftp://ftp.gnu.org/path/to/*.deb
This installs all deb-packages in the folder `path/to` on the FTP server. The shell sees normal directories (beginning with the directory “ftp:”), so shell expressions just work.
You could even define a Gentoo mirror translator (`settrans mirror\: /hurd/gentoo-mirror`), so every program could just access mirror://gentoo/portage-2.2.0_alpha31.tar.bz2 and get the data from a mirror automatically: `wget mirror://gentoo/portage-2.2.0_alpha31.tar.bz2`
+How about mounting a remote ISO file? Now that we can access ftp.gnu.org transparently,
+this is trivial!
+
+ $ settrans -c mnt /hurd/iso9660fs $PWD/ftp://ftp.gnu.org/old-gnu/gnu-f2/hurd-F2-main.iso
+ $ ls mnt/
+
+It is interesting to note that since the ISO9660 format is indexed, ftpfs does not have to
+download the whole ISO file, it merely fetches what iso9660fs requests.
+
Or you could add a unionmount translator to root which makes writes happen at another place. **Every user is able to make a readonly system readwrite** by just specifying where the writes should go. But the writes **only affect his view of the filesystem**.
Starting a network process is done by a translator, too: The first time something accesses the network card, the network translator starts up and actually provides the device. This replaces most **initscripts in the Hurd: Just add a translator to a node**, and the service will persist over restarts.