summaryrefslogtreecommitdiff
path: root/Hurd/TranslatorWishList.mdwn
diff options
context:
space:
mode:
authorGreg Buchholz <hurd@sleepingsquirrel.org>2003-07-25 18:57:29 +0000
committerGreg Buchholz <hurd@sleepingsquirrel.org>2003-07-25 18:57:29 +0000
commit4370907c0351cf3b6991c2b2d7d55f5491c7ef92 (patch)
tree829f2e2110a963c75fec8a8c4db8211527805367 /Hurd/TranslatorWishList.mdwn
parent0a934e13763a57a5cb11c6e3822aa5a436662cb4 (diff)
none
Diffstat (limited to 'Hurd/TranslatorWishList.mdwn')
-rw-r--r--Hurd/TranslatorWishList.mdwn4
1 files changed, 3 insertions, 1 deletions
diff --git a/Hurd/TranslatorWishList.mdwn b/Hurd/TranslatorWishList.mdwn
index d4d0e5ab..d4fb0af6 100644
--- a/Hurd/TranslatorWishList.mdwn
+++ b/Hurd/TranslatorWishList.mdwn
@@ -14,6 +14,8 @@ This translator could be a sub-directory of the Audio\_cdfs translator and it wo
Of course it would be a lot nicer if the above two translators didn't name their files something worthless like track001.ogg. So we would want a translator which would hook up with a database on the web and produce meaningful file names.
+## <a name="Crypto"> Crypto </a>
+
A cryptographic/steganographic seem like a nice match with the concept of user-land file systems. I like the idea of something like `settrans -a /secure stegfs --mpeg file001.mpg`
## <a name="Revision_control"> Revision control </a>
@@ -30,7 +32,7 @@ How about a translator which makes it look like you can write to read only media
## <a name="Super_FIFO"> Super\_FIFO </a>
-It's like a named pipe which is smart enough to start a process everytime something new tries to read from it. For example, let's say I have a script that reads in a JPEG image and spits out a smaller thumbnail \*.jpg to STDOUT. With a standard fifo (mknod -p fifo) this would almost works (script big.jpg &gt; fifo). But what if there are two processes trying to read the fifo at once? Ick. And of course the standard way only works once without rerunning the command. I'm not quite sure what the syntax should look like, but I'm sure someone out there has a great idea waiting to happen.
+It's like a named pipe which is smart enough to start a process everytime something new tries to read from it. For example, let's say I have a script that reads in a JPEG image and spits out a smaller thumbnail \*.jpg to STDOUT. With a standard fifo (`mknod -p fifo`) this would almost works (`script big.jpg > fifo`). But what if there are two processes trying to read the fifo at once? Ick. And of course the standard way only works once without rerunning the command. I'm not quite sure what the syntax should look like, but I'm sure someone out there has a great idea waiting to happen.
## <a name="Perl"> Perl </a>