Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Booster doesn't pass init process arguments properly #266

Open
Kuchteq opened this issue Aug 2, 2024 · 0 comments · May be fixed by #267
Open

Booster doesn't pass init process arguments properly #266

Kuchteq opened this issue Aug 2, 2024 · 0 comments · May be fixed by #267

Comments

@Kuchteq
Copy link

Kuchteq commented Aug 2, 2024

As title says. I discovered it when trying to pass the -q flag to dinit init system. Normally, the kernel command would look something like this: "kerneloptions initrd etc -- -q" the double dashes marking the beginning of arguments that are to be passed to the init process. On mkinitcpio, the flag is passed as expected and calling ps -fp 1 clearly lists its presence. On booster, it unfortunately doesn't happen even though when checking dmesg, the parameters passed to the init process are correctly listed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant