Re: Patch going boing in 1.11.0.

2008-07-06 Thread Denys Vlasenko
On Saturday 05 July 2008 22:40, Rob Landley wrote: The attached patch applies to the linux-2.6.25 kernel source with Kubuntu's patch (and the one in toybox), but busybox patch fails. With patch 2.5.4: # patch -p1 /usr/srcdevel/bbox/fix/busybox.t1/linux-2.6.13-cmdline.patch -R --dry-run

Re: mdev scan

2008-07-06 Thread Denys Vlasenko
On Sunday 06 July 2008 01:13, Rob Landley wrote: On Friday 04 July 2008 17:07:20 Denys Vlasenko wrote: On Friday 04 July 2008 13:39, Holland, John wrote: Hi, I'm having problems scanning usb_endpoint '/dev's on older kernels, 2.6.13 in particular. The usb_endpoints are beyond the

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

Ответ: MODPROBE: next generation

2008-07-06 Thread Vladimir Dronnikov
Understood. Well done! The only spiky edge I see in the following. At system startup when udevtrigger is called (or another technique of populating /dev is used) a lot of modprobes is called in parallel and they all have no plain module name specified. So they all need to go the most

Re: Ответ: MODPROBE: next generation

2008-07-06 Thread Denys Vlasenko
On Sunday 06 July 2008 09:38, Vladimir Dronnikov wrote: Understood. Well done! The only spiky edge I see in the following. At system startup when udevtrigger is called (or another technique of populating /dev is used) a lot of modprobes is called in parallel and they all have no plain

Ответ: Ответ: MODPROBE: next generation

2008-07-06 Thread Vladimir Dronnikov
Exactly. And the use of fnmatch() is definitely required, or we loose many modules, particularly PCI. -- Vladimir 2008/7/6, Denys Vlasenko [EMAIL PROTECTED]: On Sunday 06 July 2008 09:38, Vladimir Dronnikov wrote: Understood. Well done! The only spiky edge I see in the following. At system

Re: Ответ: Ответ: MODPROBE: next generation

2008-07-06 Thread Denys Vlasenko
On Sunday 06 July 2008 13:31, Vladimir Dronnikov wrote: Exactly. And the use of fnmatch() is definitely required, or we loose many modules, particularly PCI. Like this? /* modname alias1 symbol:sym1 alias2 symbol:sym2 */ desc = xstrdup(modinfo[i].desc);

Ответ: Ответ: Ответ: MO DPROBE: next generation

2008-07-06 Thread Vladimir Dronnikov
Yes. You see some kind of grepping of all modules is needed at startup, so why not to perform it explicitly? On my system it is about 20 modprobe calls with pci: aliases. The time to resolve them currently is an order of magnitude longer than just to cache the definitions once and then use the

mdev -s fails to create /dev entries

2008-07-06 Thread Vladimir Dronnikov
In particular /sys/block/loop* are the symlinks and mdev -s ceased to mknod /dev/loop*. -- Vladimir ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox

Re: mdev -s fails to create /dev entries

2008-07-06 Thread Denys Vlasenko
On Sunday 06 July 2008 16:06, Vladimir Dronnikov wrote: In particular /sys/block/loop* are the symlinks and mdev -s ceased to mknod /dev/loop*. Are you sure? # ls -l /sys/block/ drwxr-xr-x5 root root0 Jul 6 15:27 hdb drwxr-xr-x4 root root0 Jul 6 15:27

Re: mdev scan

2008-07-06 Thread Rob Landley
On Sunday 06 July 2008 01:42:23 Denys Vlasenko wrote: The first is to ignore links while traversing, Yeah, pity mdev author forgot to document why ACTION_FOLLOWLINKS is necessary (example would be most useful). What's ACTION_FOLLOWLINKS? I don't see it in the 1.10.0

Re: mdev -s fails to create /dev entries

2008-07-06 Thread Rob Landley
On Sunday 06 July 2008 09:06:53 Vladimir Dronnikov wrote: In particular /sys/block/loop* are the symlinks and mdev -s ceased to mknod /dev/loop*. Keep in mind that sysfs keeps changing. It has no stable API. In toybox, my callback from dirtree_read() is doing:

cttyhack question

2008-07-06 Thread Poly-p man
I'm working on (almost done with) an init rewrite for my distro... I started getting the no controlling tty message as soon as I fixed my terminal opening code (close all fd's, open() the correct one, dup() twice)... The help message for cttyhack says that I can't open /dev/console... I didn't.