Messages in this thread | | | Date | Thu, 8 May 2003 10:22:52 +0200 | From | DervishD <> | Subject | Re: [patch] set argv[0] of init process to filename |
| |
Hi Glenn :)
* Glenn McGrath <bug1@optushome.com.au> dixit: > This current behaviour is inconvenient for busybox > (www.busybox.net) as it uses argv[0] to determine functionality.
I had a similar problem with my init clone (a virtual console init+getty+login for embedded systems) with the same issue. I wanted to change the argv[0] for spawned processes for chaging the name that the ps command will show. At the end I assumed that the shortest name possible was 'init' and that I had four characters at least... If the space is shorter, less characters are used.
> The attached patch against 2.4.20 sets argv[0] to the filename > being run as the init process, it results in marginally smaller > binary (12 bytes).
IMHO this is a good thing, I hope it gets included, since in the general case it won't do any harm (IMHO, again). Let's see what says Marcelo.
> Is there a reason why argv[0] should always be set to "init" ?
Don't know :??
Raúl Núñez de Arenas Coronado
-- Linux Registered User 88736 http://www.pleyades.net & http://raul.pleyades.net/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |