summaryrefslogtreecommitdiff
path: root/community/weblogs/ArneBab/niches_for_the_hurd.mdwn
diff options
context:
space:
mode:
authorarnebab <arne_bab@web.de>2008-10-27 13:06:37 +0100
committerarnebab <arne_bab@web.de>2008-10-27 13:06:37 +0100
commit2158156da9c8d2e0b5f52059af0388a4622acfa5 (patch)
tree99723ba6af1e08b8d3148bd42e95b3dd951ef9e9 /community/weblogs/ArneBab/niches_for_the_hurd.mdwn
parent5588c22870c459748ef4a42de091511173edd1ad (diff)
Niches for the Hurd - some more planning.
Diffstat (limited to 'community/weblogs/ArneBab/niches_for_the_hurd.mdwn')
-rw-r--r--community/weblogs/ArneBab/niches_for_the_hurd.mdwn83
1 files changed, 61 insertions, 22 deletions
diff --git a/community/weblogs/ArneBab/niches_for_the_hurd.mdwn b/community/weblogs/ArneBab/niches_for_the_hurd.mdwn
index 361f4143..0d4077e4 100644
--- a/community/weblogs/ArneBab/niches_for_the_hurd.mdwn
+++ b/community/weblogs/ArneBab/niches_for_the_hurd.mdwn
@@ -1,9 +1,10 @@
Niches for the Hurd
===================
-We did a search for niches where the Hurd is *the biggest fish in the pond*.
+In the bug-hud mailinglist we did a search for niches where the Hurd is *the biggest
+fish in the pond*.
-This was search was segmented into four distinct phases, three of them major:
+This search was segmented into four distinct phases, three of them major:
- Brainstorm
- Reality check: can already do vs. could be used for
@@ -13,20 +14,37 @@ This was search was segmented into four distinct phases, three of them major:
Brainstorm
----------
-- Tinkerers who like its design.
-- Give back power to users: arbitrary mounts, subhurds
+"Which niches could there be for the Hurd?"
+
+### Basic Results
+
+The result is a mix of target groups,
+nice features and options of the Hurd, reasons for running a Hurd and areas where
+the Hurd offers advantages:
+
+#### Nice features and options the Hurd offers
+
+- Give back power to users: arbitrary mounts, subhurds
- Nice features: dpkg -iO ftp://foo/bar/*.deb
-- multicore-systems
-- All-in-one out-of-the-box distro running a webserver for crash-proof
-operation.
-- Having a _complete_ GNU System
+- Easier access to low-level functions
+- Advanced lightweight virtualization
- operating system study purposes as its done with minix
+- The possibility to create more efficient and powerful desktop environments
+- Having a _complete_ GNU System
+- All-in-one out-of-the-box distro running a webserver for crash-proof operation.
+
-------
+#### Target groups and strong environments
-Here's one which just got to my mind:
+- Tinkerers who like its design.
+- multicore-systems
-- Simpler virtual computing environments - no need to setup XEN, everyone can
+
+### The keyphrases in more detail or with additional ideas
+
+#### Give back power to users: arbitrary mounts, subhurds
+
+Simpler virtual computing environments - no need to setup XEN, everyone can
just open up his/her computer for someone else by creating a new user account,
and the other one can login and easily adapt the system for his/her own needs.
If most systems just differ by the translators setup on them, people could
@@ -34,12 +52,26 @@ even transfer their whole environment from one computer to another one without
needing root access or more root interaction than creating a new user account.
"I want my tools" -> "no problem, just setup your translators"
-------
+
+#### Easier access to low-level functions
One important use is for very technical people, who don't always go with
standard solutions, but rather use new approaches to best solve their
problems, and will often find traditional kernels too limiting.
+Another interesting aspect is application development: With the easily
+customized/extended system functionality, and the ability to contain
+such customizations in subenvironments, I believe that Hurd offers a
+good platform for much more efficient development of complex
+applications. Application developers can just introduce the desired
+mechanisms on a very low level, instead of building around existing
+abstractions. The extensible filesystem in particular seems extremely
+helpful as a powerful, intuitive and transparent communication
+mechanism, which allows creating truly modular applications.
+
+
+#### Advanced lightweight virtualization
+
There is also the whole area I called "advanced lightweight
virtualization" (see
http://tri-ceps.blogspot.com/2007/10/advanced-lightweight-virtualization.html
@@ -53,15 +85,7 @@ isolating them from other applications and the main system, and thus
reducing incompatibilities. Creating lightweight software appliances
sounds like an interesting option.
-Another interesting aspect is application development: With the easily
-customized/extended system functionality, and the ability to contain
-such customizations in subenvironments, I believe that Hurd offers a
-good platform for much more efficient development of complex
-applications. Application developers can just introduce the desired
-mechanisms on a very low level, instead of building around existing
-abstractions. The extensible filesystem in particular seems extremely
-helpful as a powerful, intuitive and transparent communication
-mechanism, which allows creating truly modular applications.
+#### The possibility to create more efficient and powerful desktop environments
While I believe this can be applied to any kind of applications, I'm
personally most interested in more efficient and powerful desktop
@@ -80,6 +104,21 @@ monologue at the end... I really should put these ideas into my blog.)
+#### Nice features
+
+Another example of features which would be easily possible with the Hurd:
+
+* media-player translator:
+ - settrans play /hurd/mediaplayer_play
+ - cp song1.ogg song2.ogg play
+ - # -> files get buffered and played.
+
+or even:
+
+* cp ftp://foo/bar/ogg play
+
+that's KDEs fabled network transparency on the shell level.
+
Reality check
-------------
@@ -130,7 +169,7 @@ Each participant:
- Give your personal priorities to the niches:
* Must -> all of these of all developers must be included;
remember that at most 3 to 4 ideas can be conveyed in any text.
- * Should -> The ones with the most "shoulds" will be included.
+ * Should -> The number of shoulds can be used for ranking and similar.
("must", because in a community people can do what they perceive as important, and
telling someone to stop what he's doing is no option (in my opinion))