From 6c7d45e4631784d0e077e806521a736da6b0266e Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 7 Apr 2013 18:18:44 +0200 Subject: IRC. --- open_issues/translate_fd_or_port_to_file_name.mdwn | 70 ++++++++++++++++++---- 1 file changed, 59 insertions(+), 11 deletions(-) (limited to 'open_issues/translate_fd_or_port_to_file_name.mdwn') diff --git a/open_issues/translate_fd_or_port_to_file_name.mdwn b/open_issues/translate_fd_or_port_to_file_name.mdwn index bd9abcf9..0d786d2a 100644 --- a/open_issues/translate_fd_or_port_to_file_name.mdwn +++ b/open_issues/translate_fd_or_port_to_file_name.mdwn @@ -1,4 +1,5 @@ -[[!meta copyright="Copyright © 2010, 2011 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2010, 2011, 2013 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 @@ -15,14 +16,17 @@ License|/fdl]]."]]"""]] # IRC, freenode, #hurd, June (?) 2010 - is there a way (POSIX or Hurdish) to get the corresponding file name for a fd or a hurd port? + is there a way (POSIX or Hurdish) to get the corresponding file + name for a fd or a hurd port? there is a way marcusb: which one would that be? I forgot there is an implementation in libc realpath has a similar job but that's not what I mean - pochu: maybe I am misremembering. But it was something where you keep looking up .. and list that directory, looking for the node with the ID of the node you had .. for + pochu: maybe I am misremembering. But it was something where you + keep looking up .. and list that directory, looking for the node with the + ID of the node you had .. for maybe it works only for directories yeah pochu: check the getcwd() implementation of libc @@ -30,20 +34,25 @@ License|/fdl]]."]]"""]] _hurd_canonicalize_directory_name_internal  * pochu looks marcusb: interesting - though that is for dirs, and doesn't seem to be extensible to files, as you cannot lookup for ".." under a file + though that is for dirs, and doesn't seem to be extensible to + files, as you cannot lookup for ".." under a file right oh you already said that :) actually, I am not sure that's correct - it's probably correct, but there is no reason why looking .. up on a file couldn't return the directory it's contianed in - I don't know the interfaces or the Hurd internals very well yet, but it would look strange to me if you could do that + it's probably correct, but there is no reason why looking .. up + on a file couldn't return the directory it's contianed in + I don't know the interfaces or the Hurd internals very well yet, + but it would look strange to me if you could do that the hurd is strange - it sounds like if you could `ls getcwd.c/..` to get sysdeps/mach/hurd/ :-) + it sounds like if you could `ls getcwd.c/..` to get + sysdeps/mach/hurd/ :-) yep ok. interesting you wouldn't find "ls foo.zip/.." very strange, wouldn't you? I guess not if `ls foo.zip` listed the contents of foo.zip there you go - or the other way round: would you be surprised if "cat somedir" would work? + or the other way round: would you be surprised if "cat somedir" + would work? I think so. if it did, what would it do? originally, cat dir would list the directory content! in the old unix times @@ -51,10 +60,49 @@ License|/fdl]]."]]"""]] and some early BSDs * pochu feels young :-) he don't worry, I didn't see those times either - technically, files and directories are implemented in the same way in the hurd, they both are objects implementing the fs.defs interface + technically, files and directories are implemented in the same + way in the hurd, they both are objects implementing the fs.defs interface which combines file and directory operations - of course, files and directories implement those functions differently - marcusb: do you know why this behavior (cat on directories) was changed? + of course, files and directories implement those functions + differently + marcusb: do you know why this behavior (cat on directories) was + changed? + + +## IRC, freenode, #hurd, 2013-03-07 + + * pinotree ponders about sending as RFC his patch for /proc/$pid/maps + Including a scheme for providing the names of mapped files? + ;-D + that would be really great indeed + I have not yet researched how Linux does this. Perhaps store + the filename used for first opening a file as a string somewhere? + tschwinge: eh, indeed that's lacking in my patch + i'm not sure we should aim at doing it the same way + I was wondering about having interfaces for naming tasks, threads, + objects + that'd be useful for debugging in general + yes + i don't think we need to take namespaces into account + a simple name or path should be quite enough + Agreed. "Just something!" + So, a Java toString() method for ports. + ;-) + yes + Oh, and could this also work recursively? The ext2fs instance + on /home asks its parent fs about its own path -- can it do that? (And + then cache that, most likely?) Would one get rooted filesnames that way? + i really don't think we should link it to the VFS + it should merely be a name for debugging + yep, same for me + I'd say it's the linker's task of just setting a sane name + first, keeping it isolated prevents increasing complexity + next, it doesn't reduce performance + youpi: Linker? + braunr: Ack. + yes, ld is the one creating the mappings + tschwinge: the one that loads libraries + Ah, for /proc/*/maps, right. I've been thinking more globally. # IRC, freenode, #hurd, 2011-07-13 -- cgit v1.2.3