From 0b75336c0b71d77b14feaaf7731101cb3721d8e1 Mon Sep 17 00:00:00 2001 From: scolobb Date: Fri, 29 May 2009 07:42:47 +0000 Subject: --- community/gsoc.mdwn | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'community') diff --git a/community/gsoc.mdwn b/community/gsoc.mdwn index 2719d2ab..d1838234 100644 --- a/community/gsoc.mdwn +++ b/community/gsoc.mdwn @@ -23,9 +23,13 @@ always open to introducing newcomers to the world of the GNU Hurd outside of any Google Summer of whatever project. Just pick a task from the list pointed to below on this page and get in touch with us! -The GSoC 2009 student application time has come to an end -- we are now -evaluating your applications. + +The applications have been evaluated and the following student has +been accepted: + +* [[Sergiu Ivanov (scolobb)]] # History -- cgit v1.2.3 From 5d3acb7d8b8d6edd43b22153e9d73f6dec5289c3 Mon Sep 17 00:00:00 2001 From: scolobb Date: Fri, 29 May 2009 08:33:55 +0000 Subject: --- community/sergiu_ivanov___40__scolobb__41__.mdwn | 42 ++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 community/sergiu_ivanov___40__scolobb__41__.mdwn (limited to 'community') diff --git a/community/sergiu_ivanov___40__scolobb__41__.mdwn b/community/sergiu_ivanov___40__scolobb__41__.mdwn new file mode 100644 index 00000000..c5ce15eb --- /dev/null +++ b/community/sergiu_ivanov___40__scolobb__41__.mdwn @@ -0,0 +1,42 @@ +[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="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 [[GNU Free Documentation +License|/fdl]]."]]"""]] + +## Sergiu Ivanov (scolobb) + +### Details + +, Google Summer of Code 2009 Student + +### Project + +**Unionmount**: The goal of this project is to make it possible to +mount a translator on a node in such a way that the contents of the +node be merged with the (virtual) filesystem published by the +translator. + +For documentation, see [[Unionmount]]. + +--- + +# Roadmap + +## DONE + +* Make unionfs build. + +* Change the command line parsing in unionfs to comply with the + requirements of unionmount. + +* Start the mountee. + +## TODO + +* Include the filesystem published by the mountee in the list of + merged filesystems. -- cgit v1.2.3 From bdd439dee5802de1c0f0226d9e1ca9a14c72e311 Mon Sep 17 00:00:00 2001 From: scolobb Date: Fri, 29 May 2009 13:44:21 +0000 Subject: --- community/sergiu_ivanov___40__scolobb__41__.mdwn | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'community') diff --git a/community/sergiu_ivanov___40__scolobb__41__.mdwn b/community/sergiu_ivanov___40__scolobb__41__.mdwn index c5ce15eb..1e1db7a3 100644 --- a/community/sergiu_ivanov___40__scolobb__41__.mdwn +++ b/community/sergiu_ivanov___40__scolobb__41__.mdwn @@ -40,3 +40,13 @@ For documentation, see [[Unionmount]]. * Include the filesystem published by the mountee in the list of merged filesystems. + +* Use a different (better?) implementation idea. + +* Write documentation. + +* Push the unionmount branch (*master-scolobb-unionmount*) to the + unionfs repository. + +* Derive an independent repository based on the + *master-scolobb-unionmount* branch. -- cgit v1.2.3 From 41384151ead1facfedc1cef179d83b819aef9792 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Fri, 29 May 2009 17:08:33 +0200 Subject: Merge scolobb's new page into his old user page. --- community/gsoc.mdwn | 3 +- community/sergiu_ivanov___40__scolobb__41__.mdwn | 52 ------------------------ user/scolobb.mdwn | 47 +++++++++++++++++++-- 3 files changed, 45 insertions(+), 57 deletions(-) delete mode 100644 community/sergiu_ivanov___40__scolobb__41__.mdwn (limited to 'community') diff --git a/community/gsoc.mdwn b/community/gsoc.mdwn index d1838234..ce3b26fb 100644 --- a/community/gsoc.mdwn +++ b/community/gsoc.mdwn @@ -29,7 +29,8 @@ are now evaluating your applications. --> The applications have been evaluated and the following student has been accepted: -* [[Sergiu Ivanov (scolobb)]] + * [[Sergiu Ivanov|scolobb]] + # History diff --git a/community/sergiu_ivanov___40__scolobb__41__.mdwn b/community/sergiu_ivanov___40__scolobb__41__.mdwn deleted file mode 100644 index 1e1db7a3..00000000 --- a/community/sergiu_ivanov___40__scolobb__41__.mdwn +++ /dev/null @@ -1,52 +0,0 @@ -[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="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 [[GNU Free Documentation -License|/fdl]]."]]"""]] - -## Sergiu Ivanov (scolobb) - -### Details - -, Google Summer of Code 2009 Student - -### Project - -**Unionmount**: The goal of this project is to make it possible to -mount a translator on a node in such a way that the contents of the -node be merged with the (virtual) filesystem published by the -translator. - -For documentation, see [[Unionmount]]. - ---- - -# Roadmap - -## DONE - -* Make unionfs build. - -* Change the command line parsing in unionfs to comply with the - requirements of unionmount. - -* Start the mountee. - -## TODO - -* Include the filesystem published by the mountee in the list of - merged filesystems. - -* Use a different (better?) implementation idea. - -* Write documentation. - -* Push the unionmount branch (*master-scolobb-unionmount*) to the - unionfs repository. - -* Derive an independent repository based on the - *master-scolobb-unionmount* branch. diff --git a/user/scolobb.mdwn b/user/scolobb.mdwn index 09016edb..b481f235 100644 --- a/user/scolobb.mdwn +++ b/user/scolobb.mdwn @@ -1,4 +1,4 @@ -[[!meta copyright="Copyright © 2008 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2008, 2009 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -8,13 +8,52 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] -# scolobb -Sergiu Ivanov, interested non-student +Sergiu Ivanov Mail: -Project: Namespace-based translator selection + +# Google Summer of Code: 2009 Project + +**Unionmount**: The goal of this project is to make it possible to +mount a translator on a node in such a way that the contents of the +node be merged with the (virtual) filesystem published by the +translator. + +For documentation, see [[hurd/translator/unionmount]]. + +--- + +## Roadmap + +### DONE + +* Make unionfs build. + +* Change the command line parsing in unionfs to comply with the + requirements of unionmount. + +* Start the mountee. + +### TODO + +* Include the filesystem published by the mountee in the list of + merged filesystems. + +* Use a different (better?) implementation idea. + +* Write documentation. + +* Push the unionmount branch (*master-scolobb-unionmount*) to the + unionfs repository. + +* Derive an independent repository based on the + *master-scolobb-unionmount* branch. + +--- + +# Google Summer of Code: 2008 Project: Namespace-based translator selection --- -- cgit v1.2.3 From b9344bc9677df69de86607f8444abb0602726257 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Fri, 29 May 2009 17:18:55 +0200 Subject: community/gsoc/project_ideas/unionmount -> hurd/translator/unionmount --- community/gsoc/project_ideas/unionmount.mdwn | 60 ---------------------------- hurd/translator.mdwn | 1 + hurd/translator/unionfs.mdwn | 3 ++ hurd/translator/unionmount.mdwn | 60 ++++++++++++++++++++++++++++ 4 files changed, 64 insertions(+), 60 deletions(-) delete mode 100644 community/gsoc/project_ideas/unionmount.mdwn create mode 100644 hurd/translator/unionmount.mdwn (limited to 'community') diff --git a/community/gsoc/project_ideas/unionmount.mdwn b/community/gsoc/project_ideas/unionmount.mdwn deleted file mode 100644 index 47a3d85d..00000000 --- a/community/gsoc/project_ideas/unionmount.mdwn +++ /dev/null @@ -1,60 +0,0 @@ -[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="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 -[[GNU Free Documentation License|/fdl]]."]]"""]] - -[[!meta title="Union Mounts"]] - -When setting a translator on Hurd -- similar to mounting a file system on UNIX --- the new node(s) exported by the translator are obscuring the original node -where the translator is set, and any nodes below it in the directory tree. The -translator itself can access the underlying node (which is a very nice feature, -as it allows translators presenting the contents of the node in a different -format); but it's no longer accessible from the "outside". - -Plan9 has a feature where a file system can be mounted in union mode: the new -file system doesn't obscure the mount point in this case, but instead the -contents are combined. (This feature has also been under discussion in Linux -for a couple of years now, under the label "VFS-based union mounts".) - -This kind of union mounts is generally useful, as it's sometimes more -convenient than unioning existing filesystem locations with unionfs -- it's not -necessary to mount a file system that is to be unioned at some external -location first: just union-mount it directly at the target location. - -But union mounts also allow creating passive translator hierarchies: If there -is a passive translator on a parent node, and further passive translators on -child nodes, the union mount allows the child nodes with the further translator -settings still to be visible after the parent translator has started. - -This could be useful for device nodes for example: let's say we have an -ethernet multiplexer at /dev/veth. Now the virtual subnodes could all be -directly under /dev, i.e. /dev/veth0, /dev/veth1 etc., and explicitely refer to -the main /dev/veth node in the translator command line. It would be more -elegant however to store the virtual nodes direcly below the main multiplexer -node -- /dev/veth/0, /dev/veth/1 etc. - -There are two possible approaches how union mounts could be implemented in the -Hurd. The first one is to let the various translators handle union mounts -internally, i.e. let them present the underlying nodes to the clients in -addition to the actual nodes they export themselfs. This probably can be -implemented as some kind of extension to the existing netfs and diskfs -libraries. - -The other possible apporach is less efficient and probably more tricky, but -probably also more generic: create a special unionmount translator, which -serves as a kind of proxy: setting the union-mounted translator on some -internal node; and at the actual mount location, presenting a union of the -nodes exported by this translator, and the nodes from the underlying file -system. - -The goal of this project is implementing union mounts using either of the -approaches described above. (Though it might be useful initially to prototype -both for comparision.) The ethernet multiplexer shall serve as an example use -case -- any changes necessary to allow using it with the union mount -functionality are also to be considered part of the task. diff --git a/hurd/translator.mdwn b/hurd/translator.mdwn index 8f2f07b4..5c14cfa9 100644 --- a/hurd/translator.mdwn +++ b/hurd/translator.mdwn @@ -70,6 +70,7 @@ available. * [[cvsfs]] * [[tmpfs]] * [[procfs]] +* [[unionmount]] * ... diff --git a/hurd/translator/unionfs.mdwn b/hurd/translator/unionfs.mdwn index b73d9d8e..6f845102 100644 --- a/hurd/translator/unionfs.mdwn +++ b/hurd/translator/unionfs.mdwn @@ -16,6 +16,9 @@ is included in the section entitled ... is a special mode of `unionfs`. +# See Also + + * [[unionmount]] # External Links diff --git a/hurd/translator/unionmount.mdwn b/hurd/translator/unionmount.mdwn new file mode 100644 index 00000000..47a3d85d --- /dev/null +++ b/hurd/translator/unionmount.mdwn @@ -0,0 +1,60 @@ +[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="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 +[[GNU Free Documentation License|/fdl]]."]]"""]] + +[[!meta title="Union Mounts"]] + +When setting a translator on Hurd -- similar to mounting a file system on UNIX +-- the new node(s) exported by the translator are obscuring the original node +where the translator is set, and any nodes below it in the directory tree. The +translator itself can access the underlying node (which is a very nice feature, +as it allows translators presenting the contents of the node in a different +format); but it's no longer accessible from the "outside". + +Plan9 has a feature where a file system can be mounted in union mode: the new +file system doesn't obscure the mount point in this case, but instead the +contents are combined. (This feature has also been under discussion in Linux +for a couple of years now, under the label "VFS-based union mounts".) + +This kind of union mounts is generally useful, as it's sometimes more +convenient than unioning existing filesystem locations with unionfs -- it's not +necessary to mount a file system that is to be unioned at some external +location first: just union-mount it directly at the target location. + +But union mounts also allow creating passive translator hierarchies: If there +is a passive translator on a parent node, and further passive translators on +child nodes, the union mount allows the child nodes with the further translator +settings still to be visible after the parent translator has started. + +This could be useful for device nodes for example: let's say we have an +ethernet multiplexer at /dev/veth. Now the virtual subnodes could all be +directly under /dev, i.e. /dev/veth0, /dev/veth1 etc., and explicitely refer to +the main /dev/veth node in the translator command line. It would be more +elegant however to store the virtual nodes direcly below the main multiplexer +node -- /dev/veth/0, /dev/veth/1 etc. + +There are two possible approaches how union mounts could be implemented in the +Hurd. The first one is to let the various translators handle union mounts +internally, i.e. let them present the underlying nodes to the clients in +addition to the actual nodes they export themselfs. This probably can be +implemented as some kind of extension to the existing netfs and diskfs +libraries. + +The other possible apporach is less efficient and probably more tricky, but +probably also more generic: create a special unionmount translator, which +serves as a kind of proxy: setting the union-mounted translator on some +internal node; and at the actual mount location, presenting a union of the +nodes exported by this translator, and the nodes from the underlying file +system. + +The goal of this project is implementing union mounts using either of the +approaches described above. (Though it might be useful initially to prototype +both for comparision.) The ethernet multiplexer shall serve as an example use +case -- any changes necessary to allow using it with the union mount +functionality are also to be considered part of the task. -- cgit v1.2.3 From c9784a9ed95751a45cca69e1e2e927a39e09c467 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Fri, 29 May 2009 17:56:51 +0200 Subject: Add a redirection page as we currently published this URL. --- community/gsoc/project_ideas/unionmount.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 community/gsoc/project_ideas/unionmount.mdwn (limited to 'community') diff --git a/community/gsoc/project_ideas/unionmount.mdwn b/community/gsoc/project_ideas/unionmount.mdwn new file mode 100644 index 00000000..86ef96c7 --- /dev/null +++ b/community/gsoc/project_ideas/unionmount.mdwn @@ -0,0 +1,11 @@ +[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="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 [[GNU Free Documentation +License|/fdl]]."]]"""]] + +[[!meta redir=hurd/translator/unionmount]] -- cgit v1.2.3 From 2fabec9730d0853b25734d4b05044ad4d5111202 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Thu, 4 Jun 2009 15:38:01 +0200 Subject: Updated the niches blog post a bit.# --- community/weblogs/ArneBab/niches_for_the_hurd.mdwn | 21 +++++++++++++-------- 1 file changed, 13 insertions(+), 8 deletions(-) (limited to 'community') diff --git a/community/weblogs/ArneBab/niches_for_the_hurd.mdwn b/community/weblogs/ArneBab/niches_for_the_hurd.mdwn index 8b6c4226..94cd5e59 100644 --- a/community/weblogs/ArneBab/niches_for_the_hurd.mdwn +++ b/community/weblogs/ArneBab/niches_for_the_hurd.mdwn @@ -112,6 +112,11 @@ monologue at the end... I really should put these ideas into my blog.)"* Another example of features which would be easily possible with the Hurd: +* transparent ftp (already possible!) + - settrans -c ftp: /hurd/hostmux /hurd/ftpfs / + - ls ftp://ftp.gnu.org/ + - # -> list the files on teh FTP server. + * media-player translator: - settrans play /hurd/mediaplayer_play - cp song1.ogg song2.ogg play @@ -246,8 +251,8 @@ Applications A minor phase, which will surely be interleaved with the others: Making the ideas tangible to turn them into ways how people can use the Hurd. -"Hey, look, this is the Hurd. You can use it like this to do that which you can't do -as well/easily/elegantly in any other way." +*"Hey, look, this is the Hurd. You can use it like this to do that which you can't do +as well/easily/elegantly in any other way."* ### Applications for private use @@ -264,18 +269,18 @@ it's too hard. From what I see, each direct cool application must be about as simple as -$ qemu hurd-is-cool.img -$ login root -$ settrans cool /hurd/cool +$ qemu hurd-is-cool.img +$ login root +$ settrans cool /hurd/cool $ ls cool One main focus in this example is: No command line parameters but the ones we really need. No "-a", if the example is also cool without it. No "--console" if it works otherwise. -Especially no "qemu --cd livecd --hda hurd.img ..." - that one is great for -specialists, but the goal here isn't to teach people better usage of qemu, -but to show them that the Hurd is cool, and only that. +Especially no *"qemu --cd livecd --hda hurd.img ..."* - that one is great for +people who already know qemu or want to learn it, but the goal here isn't to teach people +better usage of qemu, but to show them that the Hurd is cool, and only that. All that interesting advanced stuff just gets newcomers confused. -- cgit v1.2.3 From 4f035892571c499e959e1382cdca76ce98820415 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Thu, 4 Jun 2009 16:03:17 +0200 Subject: polishing. --- community/weblogs/ArneBab/niches_for_the_hurd.mdwn | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'community') diff --git a/community/weblogs/ArneBab/niches_for_the_hurd.mdwn b/community/weblogs/ArneBab/niches_for_the_hurd.mdwn index 94cd5e59..ff169b0a 100644 --- a/community/weblogs/ArneBab/niches_for_the_hurd.mdwn +++ b/community/weblogs/ArneBab/niches_for_the_hurd.mdwn @@ -112,12 +112,13 @@ monologue at the end... I really should put these ideas into my blog.)"* Another example of features which would be easily possible with the Hurd: -* transparent ftp (already possible!) +* transparent ftp (already possible!): - settrans -c ftp: /hurd/hostmux /hurd/ftpfs / - ls ftp://ftp.gnu.org/ - - # -> list the files on teh FTP server. + - # -> list the files on the FTP server. -* media-player translator: + +* media-player translator: - settrans play /hurd/mediaplayer_play - cp song1.ogg song2.ogg play - # -> files get buffered and played. -- cgit v1.2.3 From 958bd5447e717d80bc14d4ca7257a55d6638bcc9 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Fri, 5 Jun 2009 08:48:08 +0200 Subject: Added Olafs explanation of the mission statement. --- .../weblogs/antrik/hurd-mission-statement.mdwn | 42 ++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 community/weblogs/antrik/hurd-mission-statement.mdwn (limited to 'community') diff --git a/community/weblogs/antrik/hurd-mission-statement.mdwn b/community/weblogs/antrik/hurd-mission-statement.mdwn new file mode 100644 index 00000000..8679e414 --- /dev/null +++ b/community/weblogs/antrik/hurd-mission-statement.mdwn @@ -0,0 +1,42 @@ +For a while I have been thinking about the lack of a roadmap for the +Hurd; but now I realized that we lack something even more fundamental: a +simple mission statement -- i.e. saying where we want to go, rather +than how we want to get there. I think many of the problems we have are +directly or indirectly related to that. + +As we didn't have such a mission statement so far, the people currently +involved have vastly different ideas about the mission, which of course +makes it a bit hard to come up with a suitable one now. However, I +managed to come up with something that I believe is generic enough so +all contributors can subscribe to it: + +> *The mission of the Hurd project 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.* + +"Suitable for GNU" in the first part implies a number of things. I +explicitely mentioned "general-purpose", because this an important +feature that sets the Hurd apart from many other microkernel projects, +but isn't immediately obvious. + +I didn't mention that it must be entirely free software, as this should +be obvious to anyone familiar with GNU. + +Another thing I did not mention, because it's too controversial: how +much UNIX do we need? I think that being suitable for GNU requires a +pretty high degree of UNIX compatibility, and also that the default +environment looks to the user more or less like UNIX. However, some +people claimed in the past that GNU could do without UNIX -- the wording +used here doesn't totally preclude such views. + +The second part also leaves a lot of slack: I for my part still believe +that a Mach-based Hurd can be viable for everyday use; but those who +think that a microkernel change is required, should be happy with this +wording as well. + +The third part tries to express the major idea behind the Hurd design in +the most compact and generic way possible. + +What do you think? Is this a good mission statement? If so, it should go +on the Hurd web front page. -- cgit v1.2.3 From 6fd8bb79dfc98024e34c51ae4cf371eb2bbe0a10 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Fri, 5 Jun 2009 08:59:32 +0200 Subject: polishing --- community/weblogs/antrik/hurd-mission-statement.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'community') diff --git a/community/weblogs/antrik/hurd-mission-statement.mdwn b/community/weblogs/antrik/hurd-mission-statement.mdwn index 8679e414..3c03fb35 100644 --- a/community/weblogs/antrik/hurd-mission-statement.mdwn +++ b/community/weblogs/antrik/hurd-mission-statement.mdwn @@ -15,8 +15,8 @@ all contributors can subscribe to it: > everyday use, and gives users and programs as much control over their > computing environment as possible.* -"Suitable for GNU" in the first part implies a number of things. I -explicitely mentioned "general-purpose", because this an important +*"Suitable for GNU"* in the first part implies a number of things. I +explicitely mentioned *"general-purpose"*, because this an important feature that sets the Hurd apart from many other microkernel projects, but isn't immediately obvious. -- cgit v1.2.3 From 3439c5d41df9267914e609ffd01c10abf547e1a2 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Fri, 5 Jun 2009 09:35:43 +0200 Subject: removed the question, if the mission statement is good --- community/weblogs/antrik/hurd-mission-statement.mdwn | 3 --- 1 file changed, 3 deletions(-) (limited to 'community') diff --git a/community/weblogs/antrik/hurd-mission-statement.mdwn b/community/weblogs/antrik/hurd-mission-statement.mdwn index 3c03fb35..592e176a 100644 --- a/community/weblogs/antrik/hurd-mission-statement.mdwn +++ b/community/weblogs/antrik/hurd-mission-statement.mdwn @@ -37,6 +37,3 @@ wording as well. The third part tries to express the major idea behind the Hurd design in the most compact and generic way possible. - -What do you think? Is this a good mission statement? If so, it should go -on the Hurd web front page. -- cgit v1.2.3