Date: Mon, 4 Feb 2002 11:53:18 +0100 From: =?ISO-8859-2?Q?Pawe=B3_Jakub_Dawidek?= <nick@garage.freebsd.pl> To: freebsd-hackers@freebsd.org Subject: Re: file name Message-ID: <20020204115318.E45984@garage.freebsd.pl> In-Reply-To: <200202041036.g14Aai194298@bugz.infotecs.ru>; from vel@bugz.infotecs.ru on Mon, Feb 04, 2002 at 01:36:44PM %2B0300 References: <200202041036.g14Aai194298@bugz.infotecs.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--Q8BnQc91gJZX4vDc Content-Type: text/plain; charset=ISO-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 04, 2002 at 01:36:44PM +0300, Eugene L. Vorokov wrote: +> I faced that problem once. I used an ugly hack: simulation of __getcwd() +> syscall. You need to allocate user memory via mmap() with MAP_ANON flag, +> pass it to __getcwd(), then copy string to kernel using copyin() or like +> that, and munmap() the memory. This is neither proper nor efficient way +> to do that, but it's easy and it works. Note that in case of ./ or +> several ../ in the file name you may need to do some extra processing +> to get "correct" full path. +> =20 Working! thX a lot! :) --=20 Pawe=B3 Jakub Dawidek Network Administrator. Am I Evil? Yes, I Am. --Q8BnQc91gJZX4vDc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQCVAwUBPF5oHj/PhmMH/Mf1AQHWxgP/YYw5C12D832V98eSVFMPjKMe5QFg0gBX 2s2t6r2VucN4EWtPD3Y81lXs7/3c8xeaWmBemBPUoYijEOLphtqXauz2cTZk+Kni lR1UUv4qcGFsMtWrDfn2VaxMTiSR3+eUgrBtdEyqeN5/1I4E1qc6DmFzKxzdDaPu +btvx+3r3ZA= =tpSF -----END PGP SIGNATURE----- --Q8BnQc91gJZX4vDc-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020204115318.E45984>