Custom software as init process (PID 1)
up vote
0
down vote
favorite
I'm making an embedded system and I don't want to use C or C++ for security reasons, and I need lots of RAM, so things like a PIC processor which I've used in the past aren't an option. I'm planning to use an ARM board, such as the Beaglebone Black and a language such as python.
All I need is access to things like GPIO, serial /dev, and I2C, so what I'm wondering is, can I get away with having u-boot call my process directly (something like /usr/bin/python /opt/myprocess.py
) and have that run as PID 1? Basically, have my code run as the only process in userspace.
I don't need networking, and I'm even going to have the root file system as read only. Is there something the normal init process does that I'd be missing out on?
boot embedded init u-boot
add a comment |
up vote
0
down vote
favorite
I'm making an embedded system and I don't want to use C or C++ for security reasons, and I need lots of RAM, so things like a PIC processor which I've used in the past aren't an option. I'm planning to use an ARM board, such as the Beaglebone Black and a language such as python.
All I need is access to things like GPIO, serial /dev, and I2C, so what I'm wondering is, can I get away with having u-boot call my process directly (something like /usr/bin/python /opt/myprocess.py
) and have that run as PID 1? Basically, have my code run as the only process in userspace.
I don't need networking, and I'm even going to have the root file system as read only. Is there something the normal init process does that I'd be missing out on?
boot embedded init u-boot
4
It's not uboot which should call your init; but the kernel. And you could easily give it a try by giving the path as theinit=
argument on the kernel's command line:linux ... console=... init=/usr/bin/python /opt/myprocess.py
(any extra arguments not handled by the kernel will be passed to the init program). But your using of python script as init instead of a C program for 'security reason' is, of course, absolutely ridiculous.
– mosvy
Dec 1 at 0:24
Yes, you can do that. However, if your custom software crashes, you'll have to reboot the system. So possibly run a really small monitor process as PID 1 and let it monitor and restart your custom software.
– dirkt
Dec 1 at 21:19
Mosvy, how could you possibly think C software is as secure, on average, as managed code?
– Dave
Dec 2 at 0:54
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm making an embedded system and I don't want to use C or C++ for security reasons, and I need lots of RAM, so things like a PIC processor which I've used in the past aren't an option. I'm planning to use an ARM board, such as the Beaglebone Black and a language such as python.
All I need is access to things like GPIO, serial /dev, and I2C, so what I'm wondering is, can I get away with having u-boot call my process directly (something like /usr/bin/python /opt/myprocess.py
) and have that run as PID 1? Basically, have my code run as the only process in userspace.
I don't need networking, and I'm even going to have the root file system as read only. Is there something the normal init process does that I'd be missing out on?
boot embedded init u-boot
I'm making an embedded system and I don't want to use C or C++ for security reasons, and I need lots of RAM, so things like a PIC processor which I've used in the past aren't an option. I'm planning to use an ARM board, such as the Beaglebone Black and a language such as python.
All I need is access to things like GPIO, serial /dev, and I2C, so what I'm wondering is, can I get away with having u-boot call my process directly (something like /usr/bin/python /opt/myprocess.py
) and have that run as PID 1? Basically, have my code run as the only process in userspace.
I don't need networking, and I'm even going to have the root file system as read only. Is there something the normal init process does that I'd be missing out on?
boot embedded init u-boot
boot embedded init u-boot
asked Nov 30 at 22:06
Dave
1346
1346
4
It's not uboot which should call your init; but the kernel. And you could easily give it a try by giving the path as theinit=
argument on the kernel's command line:linux ... console=... init=/usr/bin/python /opt/myprocess.py
(any extra arguments not handled by the kernel will be passed to the init program). But your using of python script as init instead of a C program for 'security reason' is, of course, absolutely ridiculous.
– mosvy
Dec 1 at 0:24
Yes, you can do that. However, if your custom software crashes, you'll have to reboot the system. So possibly run a really small monitor process as PID 1 and let it monitor and restart your custom software.
– dirkt
Dec 1 at 21:19
Mosvy, how could you possibly think C software is as secure, on average, as managed code?
– Dave
Dec 2 at 0:54
add a comment |
4
It's not uboot which should call your init; but the kernel. And you could easily give it a try by giving the path as theinit=
argument on the kernel's command line:linux ... console=... init=/usr/bin/python /opt/myprocess.py
(any extra arguments not handled by the kernel will be passed to the init program). But your using of python script as init instead of a C program for 'security reason' is, of course, absolutely ridiculous.
– mosvy
Dec 1 at 0:24
Yes, you can do that. However, if your custom software crashes, you'll have to reboot the system. So possibly run a really small monitor process as PID 1 and let it monitor and restart your custom software.
– dirkt
Dec 1 at 21:19
Mosvy, how could you possibly think C software is as secure, on average, as managed code?
– Dave
Dec 2 at 0:54
4
4
It's not uboot which should call your init; but the kernel. And you could easily give it a try by giving the path as the
init=
argument on the kernel's command line: linux ... console=... init=/usr/bin/python /opt/myprocess.py
(any extra arguments not handled by the kernel will be passed to the init program). But your using of python script as init instead of a C program for 'security reason' is, of course, absolutely ridiculous.– mosvy
Dec 1 at 0:24
It's not uboot which should call your init; but the kernel. And you could easily give it a try by giving the path as the
init=
argument on the kernel's command line: linux ... console=... init=/usr/bin/python /opt/myprocess.py
(any extra arguments not handled by the kernel will be passed to the init program). But your using of python script as init instead of a C program for 'security reason' is, of course, absolutely ridiculous.– mosvy
Dec 1 at 0:24
Yes, you can do that. However, if your custom software crashes, you'll have to reboot the system. So possibly run a really small monitor process as PID 1 and let it monitor and restart your custom software.
– dirkt
Dec 1 at 21:19
Yes, you can do that. However, if your custom software crashes, you'll have to reboot the system. So possibly run a really small monitor process as PID 1 and let it monitor and restart your custom software.
– dirkt
Dec 1 at 21:19
Mosvy, how could you possibly think C software is as secure, on average, as managed code?
– Dave
Dec 2 at 0:54
Mosvy, how could you possibly think C software is as secure, on average, as managed code?
– Dave
Dec 2 at 0:54
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485269%2fcustom-software-as-init-process-pid-1%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
4
It's not uboot which should call your init; but the kernel. And you could easily give it a try by giving the path as the
init=
argument on the kernel's command line:linux ... console=... init=/usr/bin/python /opt/myprocess.py
(any extra arguments not handled by the kernel will be passed to the init program). But your using of python script as init instead of a C program for 'security reason' is, of course, absolutely ridiculous.– mosvy
Dec 1 at 0:24
Yes, you can do that. However, if your custom software crashes, you'll have to reboot the system. So possibly run a really small monitor process as PID 1 and let it monitor and restart your custom software.
– dirkt
Dec 1 at 21:19
Mosvy, how could you possibly think C software is as secure, on average, as managed code?
– Dave
Dec 2 at 0:54