<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24"> <TITLE>RE: mdev scan</TITLE> </HEAD> <BODY>  >> I'm having problems scanning usb_endpoint '/dev's on older kernels, 2.6.13 in particular. >> The usb_endpoints are beyond the constant MAX_SYSFS_DEPTH somewhere under /sys. > >How much is ok on those kernels? 4? 5? 5 would be good, but then I have problems with circular recursion. >> Is there any particular reason for scanning /sys/block and /sys/class separately other than >> to ascertain a nodes type? > >I guess scanning whole /sys will go into e.g. /sys/module too >and it can be rather deep. It would prolong scan times. I think it doesn't matter if a scan is little longer. >> Assuming a particular <name>/dev combination is unambiguous, one could scan the entire /sys tree >> without missing any '/dev's. I see three prerequisites. > >Can you re-formulate your thoughts is a simpler way? By now, I don't >understand what is the problem you are trying to solve. ... >Solution for what problem? I can try... My problem is that some dev files are too deep in the /sys tree to be caught by the default mdev definition. When I increase the maximum depth to say 5, I have problems with circular recursion. Being that the dev files can be found elsewhere in the /sys tree albeit deeper and without following links, I wanted to solve the problem as previously stated. John Cellent Finance Solutions AG Firmensitz: Calwer Straße 33, 70173 Stuttgart Registergericht: Amtsgericht Stuttgart, HRB 720743 Vorstand: Thomas Wild Vorsitzender des Aufsichtsrats: Rudolf Zipf </BODY> </HTML>