why are init's arguments wiped ?

[Nicolas CARRIER]

Thank you for your answer.

Even if I'm using linux, I want the solution to work in the context of init
being launched as a pid 1 of a pid namespace, which is my main use case.
In this situation, the kernel's command line can't be changed as it's the
one of the host PC.

Luckily enough, I have several ways to achieve what I want, but in my
opinion, using init's arguments would have been the most elegant option.

I'm really interested in knowing which is the real reason behind this
feature and if there is any chance that a patch would be accepted, to
either remove, or allow to disable this part of the code.

2016-01-28 18:05 GMT+01:00 Jody Bruchon <jody at jodybruchon.com>:

> On 2016-01-28 12:02, Nicolas CARRIER wrote:
>
>> Why are init's arguments wipe ?
>> I had the hope to pass init some arguments, then read them by looking
>> into /proc/1/cmdline, but no luck...
>>
>
> I don't know the answer to the question about init's arguments being
> erased, but assuming you're on Linux, you might consider passing the
> arguments to the kernel at boot time and fetch them from /proc/cmdline
> instead. As long as the kernel doesn't recognize them, they'll be silently
> ignored by the kernel.
>
> -Jody
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20160129/b1cae094/attachment.html>