From: Adam Jiang <jiang.adam@gmail.com>
To: runcoderen <runcoderzhcn@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ldd scull_load question
Date: Sun, 5 Sep 2010 12:21:48 +0900 [thread overview]
Message-ID: <20100905032148.GA9971@capricorn-x61> (raw)
In-Reply-To: <1283646914.1741.3.camel@bencharluo-laptop>
On Sun, Sep 05, 2010 at 08:35:14AM +0800, runcoderen wrote:
> hi all:
> I am reading ldd(3rd).
> when I read the scull_load part.
> I can't understand some special sentences in the scripts as follows:
>
> /sbin/insmod ./$module.ko $* || exit 1
>
> why we add $* and || exit 1 after /sbin/insmod ./$module.ko?
> can anyone help me to understand?
Hey,
The '$*' means bash variables. I believe it is a question not related to
Linux kernel. See
http://tldp.org/LDP/abs/html/othertypesv.html
/Adam
> runcoderen
>
> --
>
> /****************************************
> http://runcoderen.wordpress.com
> ****************************************/
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2010-09-05 3:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 9:20 [RFC 04/22] tcm: Add v4 base data structures and struct target_core_fabric_ops Nicholas A. Bellinger
2010-09-02 5:56 ` Konrad Rzeszutek Wilk
2010-09-02 19:19 ` Nicholas A. Bellinger
2010-09-04 23:53 ` Nicholas A. Bellinger
2010-09-05 0:35 ` ldd scull_load question runcoderen
2010-09-05 0:43 ` Randy Dunlap
2010-09-05 1:01 ` runcoderen
2010-09-05 21:20 ` Randy Dunlap
2010-09-05 3:21 ` Adam Jiang [this message]
2010-09-07 20:56 ` [RFC 04/22] tcm: Add v4 base data structures and struct target_core_fabric_ops Konrad Rzeszutek Wilk
2010-09-08 1:44 ` Nicholas A. Bellinger
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=20100905032148.GA9971@capricorn-x61 \
--to=jiang.adam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=runcoderzhcn@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®