From: Stephan Raue <mailinglists@openelec.tv>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] New package: kmod
Date: Tue, 17 Jan 2012 23:32:26 +0100 [thread overview]
Message-ID: <4F15F6FA.5020805@openelec.tv> (raw)
In-Reply-To: <CAGm1_ks1+PmxFWF6CAA7Y4FSaWVKSaOvRZXwQRVXti=ojMcRbA@mail.gmail.com>
On 01/17/2012 11:13 PM, Yegor Yefremov wrote:
> I added this package, because it is udev's dependency now. I'll have
> to look into udev, to tell if it uses only library or binary too. As
> we came to this topic, what is your opinion on adding /run? It also
> became udev's dependency. I'll set my udev's patch series tomorrow.
> Yegor _______________________________________________ buildroot
> mailing list buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
udev byself needs only the lib. the binarys can be used as
insmod/rmmod/modprobe/modinfo replacement from module-init-tools or
busybox's solution. the "kmod" binary byself is a multicall binary so
insmod/rmmod/... can be symlinks to this binary.
Stephan
next prev parent reply other threads:[~2012-01-17 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 15:04 [Buildroot] [PATCH 1/2] ethtool: bump to 3.2 yegorslists at googlemail.com
2012-01-16 15:04 ` [Buildroot] [PATCH 2/2] New package: kmod yegorslists at googlemail.com
2012-01-16 15:18 ` Peter Korsgaard
2012-01-16 17:45 ` Arnout Vandecappelle
2012-01-16 19:27 ` Peter Korsgaard
2012-01-17 13:57 ` Arnout Vandecappelle
2012-01-17 14:15 ` Peter Korsgaard
2012-01-17 22:13 ` Yegor Yefremov
2012-01-17 22:32 ` Stephan Raue [this message]
2012-01-17 23:00 ` Arnout Vandecappelle
2012-01-17 23:04 ` Peter Korsgaard
2012-01-17 23:15 ` Yegor Yefremov
2012-01-16 15:18 ` [Buildroot] [PATCH 1/2] ethtool: bump to 3.2 Peter Korsgaard
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=4F15F6FA.5020805@openelec.tv \
--to=mailinglists@openelec.tv \
--cc=buildroot@busybox.net \
/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.