Re: Problem with PFS path representation containing ":"

Am 15.12.2014 um 22:31 schrieb Matthew Dillon:
 > Is /usr/bin a softlink to /pfs/@@-1:00003/bin or is it a null mount ?

It's a null mount (from a regular DragonFly install).

# mount

/pfs/@@-1:0003 on /usr (null, local)

I am using readlink /proc/curproc/file now and it works. Working on
porting the most recent version of Rust again to DragonFly :)

Regards,

   Michael


 >
 > -Matt
 >
 > On Mon, Dec 15, 2014 at 7:22 AM, Michael Neumann <[email protected]
 > <mailto:[email protected]>> wrote:
 >
 >     Hi,
 >
 >     I am using sysctl(3) to retrieve the process's executable name via
 >     CTL_KERN -> KERN_PROC -> KERN_PROC_PATHNAME.
 >
 >     The path I am getting for /usr/bin/t for example is
 >     /pfs/@@-1:00003/bin/t. Now the problem is that this path is used top
 >     determine the system root ("/usr") and is further used to build up
 >     several paths joined by ":". But it already contains a colon!!!
 >
 >     Any idea on how to get the current process's executable name without
 >     resolving mount points? Ok, I found out about "readlink
 >     /proc/curproc/file". Is this the recommended way? Isn't it 
dangerous in
 >     general to have ":" in the PFS part of the path as it is used in 
sh to
 >     separate paths?
 >
 >     Regards,
 >
 >        Michael
 >