Re: [bug #28934] execve(path, args) should take path as a a relative path if it doesn't contain slashes

2010-02-26 Thread Ivan Shmakov
[I've unsuccessfully tried to submit the comment via the Web interface at http://savannah.gnu.org/bugs/, thus I'm posting it to the list instead.] > Carl Fredrik Hammar writes: [...] > The reason argv[0] is expanded is because it is passed as an argument > to the i

[bug #28934] execve(path, args) should take path as a a relative path if it doesn't contain slashes

2010-02-26 Thread Carl Fredrik Hammar
Follow-up Comment #6, bug #28934 (project hurd): > > The reason argv[0] is expanded is because it is passed as an argument > > to the interpreter, otherwise the interpreter can't find it. > > Unless it is a relative path, of course. I did mean any path, relative or not. What's important is tha

[bug #28934] execve(path, args) should take path as a a relative path if it doesn't contain slashes

2010-02-26 Thread Emilio Pozuelo Monfort
Follow-up Comment #5, bug #28934 (project hurd): > The reason argv[0] is expanded is because it is passed as an argument > to the interpreter, otherwise the interpreter can't find it. Unless it is a relative path, of course. > Also, ``./foo bar'' gets me `bar' in Linux not `./bar'. Are you sur

[bug #28934] execve(path, args) should take path as a a relative path if it doesn't contain slashes

2010-02-26 Thread Carl Fredrik Hammar
Follow-up Comment #4, bug #28934 (project hurd): I researched further how argv[0] is supposed to be handled and have a much firmer grasp on the situation now. argv[0] is only expanded to path to the executed file when the executed file is a #!-script. This means that touching argv[0] in execve(

[bug #28934] execve(path, args) should take path as a a relative path if it doesn't contain slashes

2010-02-26 Thread Emilio Pozuelo Monfort
Follow-up Comment #3, bug #28934 (project hurd): Hi Carl, Actually I don't think the exec server needs to know what exec*() variant has been called, since the call itself will have called execve() with the full path by looking at PATH if needed (see glibc's posix/execvpe.c, the beginning of the

X-related GSoC project ideas?

2010-02-26 Thread olafBuddenhagen
Hi, Last year we had three ideas for Hurd-related Google Summer of Code projects at X.org: libpciaccess, VT switching, and initial DRM porting. The first one is obsolete now, but the other ones are still fine. (The updated list is on http://www.bddebian.com/~hurd-web/community/gsoc/xorg_ideas/ )

Re: [bug #28859] remove(3) fails to remove an empty directory

2010-02-26 Thread olafBuddenhagen
Hi, On Wed, Feb 24, 2010 at 10:25:39AM +0100, Ludovic Courtès wrote: > Samuel Thibault writes: > > Ludovic Courtès, le Tue 23 Feb 2010 16:40:12 +, a écrit : > >> For now, how about fixing it locally in hurd/glibc.git at Savannah? > > > > For now, I've commited a fix to Debian's glibc. > > T

[bug #28859] remove(3) fails to remove an empty directory

2010-02-26 Thread Thomas Schwinge
Update of bug #28859 (project hurd): Assigned to:None => tschwinge ___ Follow-up Comment #4: Yes, I'll commit the fix there, as soon (``soon'' -- pun unavoidable...) as I get back to working