From 6f9c0342f33f52a2bda98d3709fbefd678bd46d9 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 13 May 2012 06:06:11 +0200 Subject: IRC. --- .../discussion.mdwn | 64 ++++++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 community/gsoc/project_ideas/namespace-based_translator_selection/discussion.mdwn (limited to 'community/gsoc/project_ideas') diff --git a/community/gsoc/project_ideas/namespace-based_translator_selection/discussion.mdwn b/community/gsoc/project_ideas/namespace-based_translator_selection/discussion.mdwn new file mode 100644 index 00000000..befd680a --- /dev/null +++ b/community/gsoc/project_ideas/namespace-based_translator_selection/discussion.mdwn @@ -0,0 +1,64 @@ +[[!meta copyright="Copyright © 2012 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]]."]]"""]] + +[[!tag open_issue_hurd]] + + +# IRC, freenode, #hurd, 2012-04-22 + + btw, I was wondering, when working on namespace mangling, did they + think about automatitioning ? + autopartitioning, I meant + i.e. with a foo.img file, open foo.img,,part1 + what are you referring to with namespace mangling + and voila + I don't remember the exact term they used + you mean there is a hurd library that parses names and can direct + to different services depending on part of the name ? + namespace-based_translator_selection + yes + i thought it only handled directories + well, the classical path representation + * civodul finds it ugly + civodul: because of potential conflict, and the not-too-nice ",," + part? + actually I wonder whether using directory access would be nicer + i.e. you have a foo.gz, just open foo.gz/gunzip to get the unzipped + content + and for foo.img.gz, open foo.img.gz/gunzip/part/1 + youpi: because of the interpretation of special chars in file + names + users should be free to use any character they like in file names + foo.gz/gunzip looks nicer to me + ok, so we agree + that said, the user could choose the separator + the namespace can be not run by root for everybody, but just for + your shell, run by yourself + civodul: the user can't use any character anyways... '/' and '\0' + are reserved :-P + antrik: '/' isn't quite reserved on the Hurd :-) + you could implement dir_lookup such that it does something + special about it + (server-side) + civodul: as for overloading '/', although I haven't thought it + through entirely, I guess that would work for nodes that present as files + normally. however, it would *not* work for directory nodes + which would be quite a serious limitation IMHO + I can think of various kinds of useful directory translators + what's more, one of the main use cases I originally had in mind is + a policy filter + you could pass a directory name with a appropriate filter applied + to tar for example, so it wouldn't try to follow any translators + I don't see why taking an obscure prefix like ,, would be much of + a problem in practice anyways + (also, it doesn't strictly prevent the user from having such file + names... you just need to escape it if accessing such files through the + namespace multiplexer. though admittedly that would need some special + handling in *some* programs to work properly) -- cgit v1.2.3