summaryrefslogtreecommitdiff
path: root/modutils (follow)
Commit message (Collapse)AuthorAgeFilesLines
* egor duda writes:Eric Andersen2004-10-082-5/+11
| | | | | | | | | | | | | | | | | | | | | | | | Hi! I've created a patch to busybox' build system to allow building it in separate tree in a manner similar to kbuild from kernel version 2.6. That is, one runs command like 'make O=/build/some/where/for/specific/target/and/options' and everything is built in this exact directory, provided that it exists. I understand that applyingc such invasive changes during 'release candidates' stage of development is at best unwise. So, i'm currently asking for comments about this patch, starting from whether such thing is needed at all to whether it coded properly. 'make check' should work now, and one make creates Makefile in build directory, so one can run 'make' in build directory after that. One possible caveat is that if we build in some directory other than source one, the source directory should be 'distclean'ed first. egor
* Patch from Egor DudaGlenn L McGrath2004-09-241-0/+5
| | | | | | | | | | | | | Attached patch prevents modprobe from trying to call 'insmod (null)' whenever nonexistent module is either passed to modprobe via command line or mentioned in modules.dep this replaces cryptic error sh: Syntax error: word unexpected (expecting ")") with modprobe: module some-module not found. egor.
* Based on patches from Mike Frysinger, add insmod support forEric Andersen2004-09-021-74/+82
| | | | | | | | | sparc and ia64 (itanium). Also, reorganize the insmod architecture support code to be alphasorted and less messy. Update the readme to list current insmod arch support.
* Fixup some warningsEric Andersen2004-08-281-3/+3
|
* Patch from Rodney Radford adding x86_64 support.Eric Andersen2004-08-191-3/+13
|
* Patch from Mike Castle to cleanup some modutils issues, inEric Andersen2004-08-191-59/+33
| | | | particular making alias support work better.
* Only pass modprobe module params with 2.6.x kernel support.Eric Andersen2004-08-161-2/+4
| | | | -Erik
* Christian Ostheimer writes:Eric Andersen2004-08-141-1/+1
| | | | | | | | | | | Hello, function build_dep in modprobe.c assumes that dependencies of one module have not more than 255 chars; that is not sufficient in kernel 2.6.7 (alsa sound modules). - Below is a diff that solves the problem for me. With regards, Christian Ostheimer
* Patch from Mike Castle, dont print an empty line (patch modified by me toGlenn L McGrath2004-08-111-9/+13
| | | | change formatting).
* Patch from Phil Blundellto improve substring matchGlenn L McGrath2004-08-111-1/+4
|
* Willian Barsse wroteGlenn L McGrath2004-08-111-8/+7
| | | | | | | | | | | | | | | | | "There seems to be a slight problem with the "mod_strcmp" function in modprobe.c, it scans for the first occurence of the module name in the "mod_path" variable and expects it to be the last path element. ie /lib/modules/2.4.22-debug/kernel/fs/vfat in my example. The comparison will always fail if mod_path contains another substring matching the module name." Robert McQueen wrote "Although William Barsse's patch fixed mod_strcmp for 2.4 kernels, there was a remaining problem which prevented it from working for me. I've just tracked it down - when you enable kernel 2.6 module support it hard-wired the extension to .ko instead of checking at runtime like the other places where 2.4 differs from 2.6. The attached patch fixes this for me."
* William Barsse writes:Eric Andersen2004-08-031-10/+9
| | | | | | | | | | | | | fixes two other issues (plus the previous as well) with a 2.4 kernel : - should be able to modprobe an already loaded module and get 0 return code : # modprobe <something> && modprobe <something> && echo "ok" || echo "failed" .... failed Well, hope this helps and that I didn't screw up again, - William
* Patch from Mike Snitzer <snitzer@gmail.com>:Robert Griebl2004-07-221-3/+6
| | | | | | | Support for /etc/modprobe.conf (for 2.6 kernels) should likely be added to bb's modprobe, see attached patch. modprobe.conf is just a (even simpler) variant of modules.conf
* Patch from Mike Snitzer <snitzer@gmail.com>:Robert Griebl2004-07-201-3/+3
| | | | | Please see the attached patch for the following crash with busybox' 2.6 rmmod support
* new_process_module_arguments returns 0 on error and 1 if everything went okRobert Griebl2004-07-201-3/+3
| | | | | somehow the ! got lost.. symptoms: modules could only be loaded _without_ parameters
* Deal with the fact that 2.6.x kernels replace any '-'s in theEric Andersen2004-07-201-4/+36
| | | | | module name with a '_'. -Erik
* Add missing type for CONFIG_FEATURE_QUERY_MODULE_INTERFACEEric Andersen2004-07-201-0/+2
|
* Fixup some cases of "QM_MODULES: not implemented" for bothEric Andersen2004-07-132-10/+13
| | | | | lsmod and rmmod when using 2.6.x module support -Erik
* fix a stupid compile error when CONFIG_FEATURE_INSMOD_VERSION_CHECKINGEric Andersen2004-06-221-4/+4
| | | | is disabled
* kill off insmod support for older pre 2.1 Linux kernels,Eric Andersen2004-06-222-529/+28
| | | | | which are not supported with the current busybox 1.0 release -Erik
* Patrick Huesmann writes:Eric Andersen2004-06-222-7/+30
| | | | | | | | | | | | | Hi, There was some problem with busybox modprobe. For details see http://www.busybox.net/lists/busybox/2004-May/011507.html I made a patch against busybox-1.00-pre10 to fix that one. This is a slight variant of Patrick's patch with a slightly cleaner implementation of mod_strcmp() -Erik
* oopsEric Andersen2004-05-261-3/+3
|
* Patch from Yoshinori Sato:Eric Andersen2004-05-261-3/+47
| | | | | | | | This patch is uClinux-2.4.x for H8/300 module support. please apply. -- Yoshinori Sato
* Larry Doolittle writes:Eric Andersen2004-04-141-5/+5
| | | | | | | | | | | | | | | | | | | | | | This is a bulk spelling fix patch against busybox-1.00-pre10. If anyone gets a corrupted copy (and cares), let me know and I will make alternate arrangements. Erik - please apply. Authors - please check that I didn't corrupt any meaning. Package importers - see if any of these changes should be passed to the upstream authors. I glossed over lots of sloppy capitalizations, missing apostrophes, mixed American/British spellings, and German-style compound words. What is "pretect redefined for test" in cmdedit.c? Good luck on the 1.00 release! - Larry
* Michael Tokarev, mjt at tls dot msk dot ru writes:Eric Andersen2004-04-061-2/+4
| | | | | | | | | | Fix parsing of all tag-value pairs (in modules.conf in particular). Without this fix, code chokes badly on lines where either value or both tag+value are missing, like bare alias line, or alias w/o the value like alias some-module (syntactically incorrect, but no need for coredumps either).
* Michael Tokarev, mjt at tls dot msk dot ru writes:Eric Andersen2004-04-061-1/+1
| | | | | | | | alias 'off' parsing fix. It is not alias off module it is alias module off
* Michael Tokarev, mjt at tls dot msk dot ru writes:Eric Andersen2004-04-061-2/+2
| | | | | | | | | | | | | Initialize all fields of struct dep_t. Without that, e.g. `busybox modprobe -v char-major-10-144' *sometimes* fails this way (strace): write(1, "insmod nvram `\213\f\10\n", 21) = 21 Note the garbage after module name which is taken from the m_options field, which is not initialized in the alias reading/parsing part. (Shell properly complains to this command, telling it can't find the closing backtick)
* Christian Grigis, christian.grigis at smartdata dot ch writes:Eric Andersen2004-04-061-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hello everyone, Busybox's insmod fails to locate a module when that module is the only one existing in the /lib/modules directory (with a unique name). Example: # find /lib/modules/ -type f /lib/modules/kernel/drivers/char/bios.o # insmod bios insmod: bios.o: no module by that name found # touch /lib/modules/dummy # find /lib/modules/ -type f /lib/modules/kernel/drivers/char/bios.o /lib/modules/dummy # insmod bios Using /lib/modules/kernel/drivers/char/bios.o As long as there is another file in the /lib/modules directory, insmod finds it OK. I tracked the problem down to 'check_module_name_match()' in insmod.c: It returns TRUE when a match is found, and FALSE otherwise. In the case where there is only one module in the /lib/modules directory (or more that one module, but all with the same name), 'recursive_action()' will return TRUE and we end up on line 4196 in 'insmod.c' which returns an error. [The reason it works with more than one module with different names is that in this case there will always be one not matching, 'recursive_action()' will return FALSE and we end up in line 4189.] Now, from the implementation of 'recursive_action()' and from other usages of it (tar.c, etc.), it seems to me that FALSE should be returned to indicate that we want to stop the recursion, so TRUE and FALSE should be inverted in 'check_module_name_match()'. At the same time, 'recursive_action()' continues to recurse even after the recursive call has returned FALSE; again in my understanding and other usages of it, we can safely stop recursing at this point. Here is my patch against 1.00-pre8:
* As noted in a patch from Kendrick Hamilton, rmmod was onlyEric Andersen2004-03-191-4/+1
| | | | | half way converted, and still used the old delete_module(), call rather than a syscall, in one spot.
* Add missing ELFCLASSM for m68kEric Andersen2004-03-191-2/+3
|
* Only use R_68K_GOTOFF if it is definedEric Andersen2004-03-191-2/+6
|
* Remove trailing whitespace. Update copyright to include 2004.Eric Andersen2004-03-156-45/+44
|
* Patch from OpenWrt.Manuel Novoa III2004-02-181-3/+5
|
* whitespace cleanupEric Andersen2004-01-101-45/+50
|
* Woody Suwalski writes:Eric Andersen2004-01-101-0/+1
| | | | | | I have found the problem in modprobe, so here is the promised patch At the current stage I can use it as modprobe while switching between 2.4 and 2.6 seemlesly...(that is good!)
* Woody Suwalski writes:Eric Andersen2004-01-061-8/+22
| | | | | accept more then 1 dependency per modules.dep line. Also white space cleanup... I think that parsing still breaks sometimes, but is mostly functional now.
* Fix broken #elseEric Andersen2004-01-051-4/+3
|
* Fix debian bug #215612, insmod should be silent on requestGlenn L McGrath2003-12-311-3/+4
|
* re-indentEric Andersen2003-12-243-1099/+1100
|
* Patch from Woody Suwalski:Eric Andersen2003-12-192-31/+77
| | | | | | | | | | | | | | | | | | | | | | Erik, I think we have met online some time ago when I was in Corel/Rebel Netwinder project.... Anyway, I would like to use BB on 2.6.0 initrd. 1.00-pre4 works OK, if insmod is actually presented with a full path to the module. Otherwise - problems (not to mention conflicts when 2.4 modutil is enabled) Here are some patches for insmod and modprobe which try to walk around the default ".o" module format for 2.2/2.4 modules (you have probably noticed it is now .ko in 2.6 ;-)) Trying to steal as little space as possible if 2.6 not enabled... The modprobe is still not perfect on 2.6 - seems to be jamming on some dependencies, but works with some (to be debugged). Anyway after the patches it at least tries to work.... Will there be a 1.00-pre5 coming any time soon? Thanks, Woody
* Update modutils with 2.6 module supportEric Andersen2003-12-113-36/+138
|
* Add (untested) support for cris, based on the (old) busybox insmodManuel Novoa III2003-12-041-2/+27
| | | | that axis distributes.
* Steven Seeger writes:Eric Andersen2003-11-141-1/+2
| | | | | | | | | | | | | | | | Hey guys. I've found a bug in modprobe where it generates bad strings and makes sytem calls with them. The following patch seems to have fixed the problem. It is rather inherited elsewhere, as there seems to be incorrect entries in the list which results in more dependencies than really exist for a given call to mod_process. But, this patch prevents the bad text from going to the screen. You will notice there are cases where lcmd goes unmodified before calling system. Please consider the following patch. Thanks. -Steve
* Do a better job of dealing with screwy s390 abi changesEric Andersen2003-10-211-2/+5
|
* ccording to this:Eric Andersen2003-10-201-3/+3
| | | | | | http://sources.redhat.com/ml/binutils/2003-01/msg00290.html The name R_390_GOTOFF was changed to R_390_GOTOFF32. -Erik
* Busybox modprobe has a couple of irritating quirks:Glenn L McGrath2003-09-081-4/+33
| | | | | | | | | | | | | - attempting to modprobe a module that is already loaded yields "Failed to load module", whereas modutils quietly ignores such a request. - if a module genuinely can't be loaded due to missing symbols or similar problems, modprobe doesn't produce any useful diagnostics because the output from insmod has been redirected to /dev/null. Here's a patch to address these issue Patch by Philip Blundell
* To load GPLONLY symbols its is required that CHECK_TAINTED_MODULES beGlenn L McGrath2003-09-032-4/+8
| | | | enabled, if not GPLONLY symbols are ignored.
* "insmod caches the symbolname in a variable before modifying it and usesGlenn L McGrath2003-08-311-3/+12
| | | | the cached value afterwards." - Jean Wolter
* handle GPLONLY symbolsGlenn L McGrath2003-08-301-3/+21
|
* Patch from Paul Mundt (lethal) adding sh64 insmod support for busyboxEric Andersen2003-08-131-10/+72
|
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-16 14:30:57 +0000