Re: MODPROBE: next generation

2008-07-06 Thread Denys Vlasenko
[CC: [EMAIL PROTECTED] On Sunday 06 July 2008 08:27, Vladimir Dronnikov wrote: Hello, Denys! Looked through modutils-small.c. Could you explain the changes you made? I see the code became 500 bytes larger... I made the following changes: * directory scannig is done just once * if we find

Re: MODPROBE: next generation

2008-06-24 Thread Denys Vlasenko
On Monday 23 June 2008 19:02, [EMAIL PROTECTED] wrote: Hello, Denys! Made a patch: 1. lsmod, modprobe, rmmod, depmod retain compatible interface: 1717 octets for all. Wow. 2. insmod: do we really need to publish it as applet? Ja ja. We love our users, we don't want to upset them by

Re: MODPROBE: next generation

2008-06-24 Thread Denys Vlasenko
On Tuesday 24 June 2008 18:00, Denys Vlasenko wrote: On Monday 23 June 2008 19:02, [EMAIL PROTECTED] wrote: Hello, Denys! Made a patch: 1. lsmod, modprobe, rmmod, depmod retain compatible interface: 1717 octets for all. Wow. 2. insmod: do we really need to publish it as applet?

Re: MODPROBE: next generation

2008-06-24 Thread Denys Vlasenko
On Tuesday 24 June 2008 23:48, [EMAIL PROTECTED] wrote: Hello, Denys! Made a new patch. Tried to fix the issues you pointed out. + do { + /* search for the first char in word */ + ptr = memchr(ptr, *word, len - (ptr - (char*)the_module)); + if

Re: MODPROBE: next generation

2008-06-23 Thread Bernhard Fischer
On Mon, Jun 23, 2008 at 10:02:51AM -0700, [EMAIL PROTECTED] wrote: Hello, Denys! Made a patch: 1. lsmod, modprobe, rmmod, depmod retain compatible interface: 1717 octets for all. 2. insmod: do we really need to publish it as applet? 3. modules.dep move to /tmp/modules.dep.bb: that way we ensure

Re: MODPROBE: next generation

2008-06-20 Thread Denys Vlasenko
On Tuesday 17 June 2008 19:24, [EMAIL PROTECTED] wrote: 0. Intro depmod + modprobe is some kind of complicated codec. Though the syntax of modprobe.conf and friends is human-friendly most of module dependencies is intrinsic and are hardly a subject to be customized manually. du modules.*

Re: MODPROBE: next generation

2008-06-20 Thread Bernhard Fischer
On Fri, Jun 20, 2008 at 04:58:04PM +0200, Denys Vlasenko wrote: We already have open_transformer(), so you just call fd = open_transformer(gzfile_fd, unpack_gz_stream, gunzip); and voila - you can gunzip file on the fly :) Can we have a libunarchival wrapper that sets up open_transformer for

Re: MODPROBE: next generation

2008-06-20 Thread Denys Vlasenko
On Friday 20 June 2008 17:05, Bernhard Fischer wrote: On Fri, Jun 20, 2008 at 04:58:04PM +0200, Denys Vlasenko wrote: We already have open_transformer(), so you just call fd = open_transformer(gzfile_fd, unpack_gz_stream, gunzip); and voila - you can gunzip file on the fly :) Can we

Re: MODPROBE: next generation

2008-06-18 Thread Natanael Copa
On Tue, 2008-06-17 at 10:24 -0700, [EMAIL PROTECTED] wrote: I suggest to invent for BB a custom modules.dep format which bites all above issues. ... Comments? Please no. My alpine linux distro is based on uclibc/busybox. If hte busybox utility is not good enough for user, then it is