From: Louis Bouchard <louis.bouchard@hp.com>
To: kexec@lists.infradead.org
Subject: Re: kdump_post : busybox returns "Applet not found"
Date: Mon, 06 Dec 2010 11:59:08 +0100 [thread overview]
Message-ID: <4CFCC1FC.2020409@hp.com> (raw)
In-Reply-To: <4CFBFB8B.2060902@bwalle.de>
Hello,
On 05/12/2010 21:52, Bernhard Walle wrote:
> Am 05.12.10 21:19, schrieb Neil Horman:
>> I'm kind of suprised this is working at all. I don't see a #!/bin/sh or
>> #!/bin/msh line at the top of the script. How does the system know what
>> interpreter to use?
>
> /bin/sh is the default interpreter.
>
>
> Regards,
> Bernhard
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
While, as Bernhard said, /bin/sh is default so the test script does
work, the crashdc scripts that I'm testing do have the #!/bin/sh at the
beginning, with identical behavior.
Kind regards,
..Louis
--
Louis Bouchard
Linux Support Engineer
Team lead, EMEA Linux Competency Center,
Linux Advocate, HP
HP Technology Services - Global Competency Center
Hewlett-Packard Company
louis.bouchard@hp.com / Email
Mon-Fri 9-17<WET>,<GMT+2> / Working Hours
Mark Fay / Manager
mark.fay@hp.com / Manager's Email
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-12-06 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 16:14 kdump_post : busybox returns "Applet not found" Louis Bouchard
2010-12-05 20:19 ` Neil Horman
2010-12-05 20:52 ` Bernhard Walle
2010-12-06 10:59 ` Louis Bouchard [this message]
2010-12-06 13:27 ` kdump_post : busybox returns "Applet not found"' Neil Horman
2010-12-06 15:02 ` Louis Bouchard
2010-12-06 15:45 ` Neil Horman
2010-12-06 12:03 ` kdump_post : busybox returns "Applet not found" Neil Horman
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=4CFCC1FC.2020409@hp.com \
--to=louis.bouchard@hp.com \
--cc=kexec@lists.infradead.org \
/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.