buildroot/busybox: launch bootchartd on startup
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I built a custom linux image using buildroot and busybox. To speed up the boot process I'd like to use bootchartd (built-in version of busybox) to profile the process. However bootchartd is not running, therefore no output file (/var/log/bootchart.tgz) is generated.
I appended each of these two lines to the kernel command line. Unfortunately, neither of them is working:
init=/sbin/bootchartd
Second version:
real_init=/sbin/bootchartd
Does anybody know why bootchartd isn't launched?
Note: initramfs as a root filesystem
kernel busybox init profiling
asked May 30 '12 at 11:08
SecStoneSecStone
11616
add a comment |
I built a custom linux image using buildroot and busybox. To speed up the boot process I'd like to use bootchartd (built-in version of busybox) to profile the process. However bootchartd is not running, therefore no output file (/var/log/bootchart.tgz) is generated.
I appended each of these two lines to the kernel command line. Unfortunately, neither of them is working:
init=/sbin/bootchartd
Second version:
real_init=/sbin/bootchartd
Does anybody know why bootchartd isn't launched?
Note: initramfs as a root filesystem
kernel busybox init profiling
asked May 30 '12 at 11:08
SecStoneSecStone
11616
But it is there, right? I.e.bootchartdin a console returns something?
– sr_
May 30 '12 at 12:39
Yes, it does what it is supposed to do (showing the usage). As soon as it's started with PID=1, it should start logging.
– SecStone
May 31 '12 at 17:31
Can you verify that the initramfs stuff gets passed the parameter properly? (cmp. this)
– sr_
Jun 1 '12 at 9:43
The first line ofdmesgshows the passed arguments. However, I'm not quite sure if that is enough to proof that the parameters are passed properly. Do you know whether that suffices?
– SecStone
Jun 1 '12 at 21:12
Probably not as it would work otherwise, wouldn't it? Can you include more information, e.g. what distribution you use (if any, otherwise describing your setup, how you create your initramfs...)
– sr_
Jun 2 '12 at 9:09
add a comment |
I built a custom linux image using buildroot and busybox. To speed up the boot process I'd like to use bootchartd (built-in version of busybox) to profile the process. However bootchartd is not running, therefore no output file (/var/log/bootchart.tgz) is generated.
I appended each of these two lines to the kernel command line. Unfortunately, neither of them is working:
init=/sbin/bootchartd
Second version:
real_init=/sbin/bootchartd
Does anybody know why bootchartd isn't launched?
Note: initramfs as a root filesystem
kernel busybox init profiling
asked May 30 '12 at 11:08
SecStoneSecStone
11616
I built a custom linux image using buildroot and busybox. To speed up the boot process I'd like to use bootchartd (built-in version of busybox) to profile the process. However bootchartd is not running, therefore no output file (/var/log/bootchart.tgz) is generated.
I appended each of these two lines to the kernel command line. Unfortunately, neither of them is working:
init=/sbin/bootchartd
Second version:
real_init=/sbin/bootchartd
Does anybody know why bootchartd isn't launched?
Note: initramfs as a root filesystem
kernel busybox init profiling
kernel busybox init profiling
asked May 30 '12 at 11:08
SecStoneSecStone
11616
asked May 30 '12 at 11:08
SecStoneSecStone
11616
asked May 30 '12 at 11:08
SecStoneSecStone
11616
asked May 30 '12 at 11:08
SecStoneSecStone
11616
asked May 30 '12 at 11:08
SecStoneSecStone
11616
11616
But it is there, right? I.e.bootchartdin a console returns something?
– sr_
May 30 '12 at 12:39
Yes, it does what it is supposed to do (showing the usage). As soon as it's started with PID=1, it should start logging.
– SecStone
May 31 '12 at 17:31
Can you verify that the initramfs stuff gets passed the parameter properly? (cmp. this)
– sr_
Jun 1 '12 at 9:43
The first line ofdmesgshows the passed arguments. However, I'm not quite sure if that is enough to proof that the parameters are passed properly. Do you know whether that suffices?
– SecStone
Jun 1 '12 at 21:12
Probably not as it would work otherwise, wouldn't it? Can you include more information, e.g. what distribution you use (if any, otherwise describing your setup, how you create your initramfs...)
– sr_
Jun 2 '12 at 9:09
add a comment |
But it is there, right? I.e.bootchartdin a console returns something?
– sr_
May 30 '12 at 12:39
Yes, it does what it is supposed to do (showing the usage). As soon as it's started with PID=1, it should start logging.
– SecStone
May 31 '12 at 17:31
Can you verify that the initramfs stuff gets passed the parameter properly? (cmp. this)
– sr_
Jun 1 '12 at 9:43
The first line ofdmesgshows the passed arguments. However, I'm not quite sure if that is enough to proof that the parameters are passed properly. Do you know whether that suffices?
– SecStone
Jun 1 '12 at 21:12
Probably not as it would work otherwise, wouldn't it? Can you include more information, e.g. what distribution you use (if any, otherwise describing your setup, how you create your initramfs...)
– sr_
Jun 2 '12 at 9:09
But it is there, right? I.e.
bootchartd in a console returns something?– sr_
May 30 '12 at 12:39
But it is there, right? I.e.
bootchartd in a console returns something?– sr_
May 30 '12 at 12:39
Yes, it does what it is supposed to do (showing the usage). As soon as it's started with PID=1, it should start logging.
– SecStone
May 31 '12 at 17:31
Yes, it does what it is supposed to do (showing the usage). As soon as it's started with PID=1, it should start logging.
– SecStone
May 31 '12 at 17:31
Can you verify that the initramfs stuff gets passed the parameter properly? (cmp. this)
– sr_
Jun 1 '12 at 9:43
Can you verify that the initramfs stuff gets passed the parameter properly? (cmp. this)
– sr_
Jun 1 '12 at 9:43
The first line of
dmesg shows the passed arguments. However, I'm not quite sure if that is enough to proof that the parameters are passed properly. Do you know whether that suffices?– SecStone
Jun 1 '12 at 21:12
The first line of
dmesg shows the passed arguments. However, I'm not quite sure if that is enough to proof that the parameters are passed properly. Do you know whether that suffices?– SecStone
Jun 1 '12 at 21:12
Probably not as it would work otherwise, wouldn't it? Can you include more information, e.g. what distribution you use (if any, otherwise describing your setup, how you create your initramfs...)
– sr_
Jun 2 '12 at 9:09
Probably not as it would work otherwise, wouldn't it? Can you include more information, e.g. what distribution you use (if any, otherwise describing your setup, how you create your initramfs...)
– sr_
Jun 2 '12 at 9:09
add a comment |
2 Answers
2
active
oldest
votes
According to the Linux kernel source (namely, the file init/main.c), the ramdisk execute command is executed before init= and real_init=. This command is default to /init and can be configured via the rdinit= kernel command line parameter
But to collect logs properly bootchartd need to be started without any parameters, so it looks like patching of init/main.c is needed anyway, as its default parameter is start.
edited Dec 12 '12 at 1:02
jasonwryan
50.8k14135190
answered Dec 11 '12 at 16:52
Mikhail BeloborodyyMikhail Beloborodyy
111
add a comment |
I am having a similar problem to yours and came across your question during my research process. Though we do not have the same problem, I believe I found the answer to yours. So, according to busybox's documentation:
- Note that if you're using an initramfs, you'll need
rdinit=/sbin/bootchartd
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Dec 16 '15 at 11:39
Manuel_RodríguezManuel_Rodríguez
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f39666%2fbuildroot-busybox-launch-bootchartd-on-startup%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
According to the Linux kernel source (namely, the file init/main.c), the ramdisk execute command is executed before init= and real_init=. This command is default to /init and can be configured via the rdinit= kernel command line parameter
But to collect logs properly bootchartd need to be started without any parameters, so it looks like patching of init/main.c is needed anyway, as its default parameter is start.
edited Dec 12 '12 at 1:02
jasonwryan
50.8k14135190
answered Dec 11 '12 at 16:52
Mikhail BeloborodyyMikhail Beloborodyy
111
add a comment |
According to the Linux kernel source (namely, the file init/main.c), the ramdisk execute command is executed before init= and real_init=. This command is default to /init and can be configured via the rdinit= kernel command line parameter
But to collect logs properly bootchartd need to be started without any parameters, so it looks like patching of init/main.c is needed anyway, as its default parameter is start.
edited Dec 12 '12 at 1:02
jasonwryan
50.8k14135190
answered Dec 11 '12 at 16:52
Mikhail BeloborodyyMikhail Beloborodyy
111
add a comment |
According to the Linux kernel source (namely, the file init/main.c), the ramdisk execute command is executed before init= and real_init=. This command is default to /init and can be configured via the rdinit= kernel command line parameter
But to collect logs properly bootchartd need to be started without any parameters, so it looks like patching of init/main.c is needed anyway, as its default parameter is start.
edited Dec 12 '12 at 1:02
jasonwryan
50.8k14135190
answered Dec 11 '12 at 16:52
Mikhail BeloborodyyMikhail Beloborodyy
111
According to the Linux kernel source (namely, the file init/main.c), the ramdisk execute command is executed before init= and real_init=. This command is default to /init and can be configured via the rdinit= kernel command line parameter
But to collect logs properly bootchartd need to be started without any parameters, so it looks like patching of init/main.c is needed anyway, as its default parameter is start.
edited Dec 12 '12 at 1:02
jasonwryan
50.8k14135190
answered Dec 11 '12 at 16:52
Mikhail BeloborodyyMikhail Beloborodyy
111
edited Dec 12 '12 at 1:02
jasonwryan
50.8k14135190
edited Dec 12 '12 at 1:02
jasonwryan
50.8k14135190
edited Dec 12 '12 at 1:02
jasonwryan
50.8k14135190
50.8k14135190
answered Dec 11 '12 at 16:52
Mikhail BeloborodyyMikhail Beloborodyy
111
answered Dec 11 '12 at 16:52
Mikhail BeloborodyyMikhail Beloborodyy
111
answered Dec 11 '12 at 16:52
Mikhail BeloborodyyMikhail Beloborodyy
111
111
add a comment |
add a comment |
I am having a similar problem to yours and came across your question during my research process. Though we do not have the same problem, I believe I found the answer to yours. So, according to busybox's documentation:
- Note that if you're using an initramfs, you'll need
rdinit=/sbin/bootchartd
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Dec 16 '15 at 11:39
Manuel_RodríguezManuel_Rodríguez
1
add a comment |
I am having a similar problem to yours and came across your question during my research process. Though we do not have the same problem, I believe I found the answer to yours. So, according to busybox's documentation:
- Note that if you're using an initramfs, you'll need
rdinit=/sbin/bootchartd
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Dec 16 '15 at 11:39
Manuel_RodríguezManuel_Rodríguez
1
add a comment |
I am having a similar problem to yours and came across your question during my research process. Though we do not have the same problem, I believe I found the answer to yours. So, according to busybox's documentation:
- Note that if you're using an initramfs, you'll need
rdinit=/sbin/bootchartd
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Dec 16 '15 at 11:39
Manuel_RodríguezManuel_Rodríguez
1
I am having a similar problem to yours and came across your question during my research process. Though we do not have the same problem, I believe I found the answer to yours. So, according to busybox's documentation:
- Note that if you're using an initramfs, you'll need
rdinit=/sbin/bootchartd
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Dec 16 '15 at 11:39
Manuel_RodríguezManuel_Rodríguez
1
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
41.9k1483142
answered Dec 16 '15 at 11:39
Manuel_RodríguezManuel_Rodríguez
1
answered Dec 16 '15 at 11:39
Manuel_RodríguezManuel_Rodríguez
1
answered Dec 16 '15 at 11:39
Manuel_RodríguezManuel_Rodríguez
1
1
add a comment |
add a comment |
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.
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%2f39666%2fbuildroot-busybox-launch-bootchartd-on-startup%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
But it is there, right? I.e.
bootchartdin a console returns something?– sr_
May 30 '12 at 12:39
Yes, it does what it is supposed to do (showing the usage). As soon as it's started with PID=1, it should start logging.
– SecStone
May 31 '12 at 17:31
Can you verify that the initramfs stuff gets passed the parameter properly? (cmp. this)
– sr_
Jun 1 '12 at 9:43
The first line of
dmesgshows the passed arguments. However, I'm not quite sure if that is enough to proof that the parameters are passed properly. Do you know whether that suffices?– SecStone
Jun 1 '12 at 21:12
Probably not as it would work otherwise, wouldn't it? Can you include more information, e.g. what distribution you use (if any, otherwise describing your setup, how you create your initramfs...)
– sr_
Jun 2 '12 at 9:09