From: DervishD <raul@pleyades.net>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Changing argv[0] under Linux.
Date: Tue, 14 Jan 2003 20:50:05 +0100 [thread overview]
Message-ID: <20030114195005.GD162@DervishD> (raw)
In-Reply-To: <Pine.LNX.3.95.1030114143919.13702A-100000@chaos.analogic.com>
Hi Richard :)
> > Any header where I can see the length for argv[0] or is this some
> > kind of unoficial standard? Just doing strcpy seems dangerous to me
> > (you can read 'paranoid'...).
> They need to have space for _POSIX_PATH_MAX (512 bytes), to
> claim POSIX compatibility so any POSIX system will have at
> least 512 bytes available because the pathname of the executable
> normally goes there.
Enough for me, then. Thanks a lot :)) Just one more thing: in my
Single Unix Spec v3 says that the minimum value of _POSIX_PATH_MAX is
256, not 512, and the libc manual says just the same :??
Anyway, 256 bytes is a fair large amount ;))))
Thanks again, Richard.
Raúl
next prev parent reply other threads:[~2003-01-14 19:41 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 18:59 Changing argv[0] under Linux DervishD
2003-01-14 19:10 ` Richard B. Johnson
2003-01-14 19:14 ` DervishD
2003-01-14 19:43 ` Richard B. Johnson
2003-01-14 19:50 ` DervishD [this message]
2003-01-14 19:56 ` Richard B. Johnson
2003-01-14 20:23 ` Mark Mielke
2003-01-14 20:28 ` Richard B. Johnson
2003-01-14 21:21 ` Mark Mielke
2003-01-15 14:00 ` Richard B. Johnson
2003-01-15 16:43 ` Richard B. Johnson
2003-01-15 16:57 ` DervishD
2003-01-14 22:00 ` DervishD
2003-01-21 14:16 ` Bill Davidsen
2003-01-21 15:33 ` DervishD
2003-01-14 20:25 ` Philippe Troin
2003-01-14 20:56 ` Richard B. Johnson
2003-01-14 22:04 ` DervishD
2003-01-14 23:04 ` Bob Miller
2003-01-14 23:11 ` Bob Miller
2003-01-15 4:46 ` Mark Mielke
2003-01-15 8:25 ` jw schultz
2003-01-15 11:41 ` DervishD
2003-01-15 13:16 ` Jakob Oestergaard
2003-01-15 16:22 ` DervishD
2003-01-15 16:47 ` Jakob Oestergaard
2003-01-15 17:10 ` DervishD
2003-01-15 17:36 ` Changing argv[0] under Linux. This MUST work DervishD
2003-01-15 21:26 ` Changing argv[0] under Linux Andreas Schwab
2003-01-15 21:36 ` Jesse Pollard
2003-01-15 22:03 ` DervishD
2003-01-16 9:19 ` Dorin Lazar
2003-01-15 11:35 ` DervishD
2003-01-14 21:55 ` Miquel van Smoorenburg
2003-01-14 22:04 ` Valdis.Kletnieks
2003-01-15 11:28 ` DervishD
2003-01-27 7:47 ` Anuradha Ratnaweera
[not found] <122203493@toto.iv>
2003-01-14 22:55 ` Peter Chubb
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 10:12 Jon Burgess
2003-01-16 10:32 ` DervishD
2003-01-16 11:31 Jon Burgess
2003-01-16 12:58 ` DervishD
[not found] <20030116130013.GE1358@DervishD>
[not found] ` <200301161315.h0GDFLM27487@isengard.accucard.com>
2003-01-17 10:08 ` DervishD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030114195005.GD162@DervishD \
--to=raul@pleyades.net \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.