🚀 go-pugleaf

---

From: federico@heinz.in-berlin.de (Federico Heinz)
Message-ID: <1992Apr2.132737.17286@heinz.in-berlin.de>
Date: 2 Apr 92 13:27:37 GMT

"...there's this ``insanely great'' feature of the NeXT environment that 
 allows mapping a file into memory, which would greatly reduce the complexity 
 of my code. The caveat: I must have the file's name in order to map it, but 
 I don't know the name.

"No sweat, I think: just use fstat() to get the file's inode number, and ask  
 the file system to make a link to it under a name I like (let's assume I know  
 is on the same device), and voila, there's a file I can map... only I haven't  
 found any way to set up a link to a particular inode..."

---

From: jfw@ksr.com (John F. Woods)
Message-ID: <11173@ksr.com>
Date: 2 Apr 92 21:20:37 GMT

"The answer is that you cannot do this (in general)."

---

From: byer@adobe.com (Scott Byer)
Message-ID: <1992Apr3.001624.23736@adobe.com>
Date: 3 Apr 92 00:16:24 GMT

"Search the NextDev docs for map_fd:

"#include <mach.h>

"kern_return_t map_fd(int fd, vm_offset_t offset, vm_offset_t *address,  
 boolean_t find_space, vm_size_t size)"

---

From: jml@taco.visus.com (Jim Large)
Message-ID: <1992Apr4.013717.17114@visus.com>
Date: 4 Apr 92 01:37:17 GMT

"Fire up DigitalLibrarian and search the NeXT Developer docs for "map_fd".
 It does exactly what you want."

--

Moral of the story: us Unix generalists shouldn't make hasty assumptions 
about SPECIFIC implementations of modern Unix and Unix-like OSes. The 
environments out there today are richer and more developer-friendly than they 
were say 5 or 10 years ago. Live and learn...

								- Kevin