Messages in this thread | | | Date | Sun, 29 Jan 2006 12:26:58 -0800 | From | Greg KH <> | Subject | Re: Does /sys/module/foo reflect external module name? |
| |
On Sun, Jan 29, 2006 at 07:14:47PM +0300, Andrey Borzenkov wrote: > Is it correct that /sys/module lists module *file* names (sans -_ confusion)? > Is it possible to find out if module is built in or truly external? The goal > is to automate initrd build by walking from /dev/root up and pulling in all > modules. Now missing module may mean that it is built in or that it is really > missing :) In my case: > > {pts/1}% for i in /sys/module/* > for> do > for> grep -q ${i:t} /proc/modules || echo $i > for> done > /sys/module/8250 > /sys/module/i8042 > /sys/module/md_mod > /sys/module/psmouse > /sys/module/tcp_bic > {pts/1}% for i in $(lsmod | awk '{print $1}') > do > [[ -d /sys/module/$i ]] || echo $i > done > Module > > so it looks quite reliable up to built in modules. Is there any information > that could be exported in sysfs (like "builtin" == 0|1)?
What would that be needed for? You can always just compare the list with /proc/modules, right?
thanks,
greg k-h - 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/
| |