From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Irrelevant kernel modules
Date: Fri, 29 May 2009 16:24:37 +0200 [thread overview]
Message-ID: <4A1FF025.90903@bfh.ch> (raw)
In-Reply-To: <4A1EF025.4040102-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Warren Togami wrote:
> drivers/net/irda/
> drivers/net/appletalk
We could get rid of these (and others) if we'd filter the network-modules
for the call 'eth_type_trans' (nm -uPA ... | grep eth_type_trans)
/> net/ipv4/netfilter
> net/sched/
> net/irda/
> net/bridge/netfilter/
> net/netfilter/
> net/phonet
> net/dccp/
> net/ipv6/netfilter/
> net/bluetooth/
> net/atm/
> net/802/
Hmmm... Would it make sense if the network installer would just specify
which modules below /kernel/net are needed and only /kernel/drivers/net
is process automatically?
>
> It seems these (and possibly more) kernel modules are being copied into
> the initrd but are never needed during initrd. Any ideas of a better
> and more specific way of specifying only network interface drivers?
>
> rm -rf ${initdir}/lib/modules/$kernel/kernel/net/wireless
> rm -rf ${initdir}/lib/modules/$kernel/kernel/drivers/net/wireless
Add
nm -uPA $srcmods/$(modprobe -l $mod) | egrep -qv 'ieee802011|wireless' || return
To to just before the modprobe inside instmods and wireless drivers should be gone
>
> In related news, Harald suggested adding this as an ugly hack to get rid
> of wireless drivers. This immediately after instmods =net didn't work
> for some reason I haven't yet figured out. It is successfully deleting
> the modules, but something else is copying them back later. I am hoping
> the $drivers cleanups I just pushed help this situation.
>
> So the other bug involving instmods() firmware handling being broken is
> the reason for wireless .ko modules to be loaded during initrd but
> failing due to missing firmware. We already agreed on this list earlier
> to exclude wireless in the standard initrd though, so this doesn't
> matter yet. I guess some SCSI or FC controllers might be more effected
> by the missing firmware.
>
> Warren Togami
> wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
> --
> To unsubscribe from this list: send the line "unsubscribe initramfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-05-29 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 20:12 Irrelevant kernel modules Warren Togami
[not found] ` <4A1EF025.4040102-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-05-29 14:24 ` Seewer Philippe [this message]
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=4A1FF025.90903@bfh.ch \
--to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox