[...] > > > > I do not understand the question. configuration method is drakmouse > > or whatever. it does not depend on kernel. but it must emit something > > suitable for both kernels. > > sorry for not being clear, > what i meant is mousedrake makes a single configuration file, > and probably somewhere in the initscripts or eventually devfsd > adjusts the used mice devices according to the running kernel 2.4 or 2.5
well ... currently (2.4) mousedrake just selects correct device and type (for gpm/X11). When programs tries to open this device right module is autoloaded (either by virtue of char-major-N-M alias or by defvsd). With devfs module also creates correct device name. So there is actually no links involved or needed. > (hm i probably can not explain it properly because i'm thinking about the mice > as an independent devices used by different users, and on a standard kernel > this is not the case) > Why? you can have several mice of different types assuming you have some place to plug them into. You probably cannot have several of the same type. And USB mice are using the same input subsystem as 2.6 already so you get /dev/input/mouse0, 1, 2 ... like in 2.6 with the same /proc information available just without extra input hotplug goody. > > > with oder words, what kind of problem should expect in case > > > i'm running 2.4 with the input from 2.6 > > > in a not that common way: local XFree multi-user > > > > you can't. if you running 2.4 you are running input from 2.4 > > with std 2.4 or mandrake's 2.4 ( as no one once to accept/look into my kernel > packages) you can't, but you can do it with backstreet ruby :) > > http://startx.times.lv > http://tldp.org/HOWTO/XFree-Local-multi-user-HOWTO/ > ok. in this case I do not expect any problem at all. you have 2.4 subsystem still there and any application will continue to work. those wishing to use 2.6 input will use it. > > > PS. > > > about PS2 devices: are they going to be loaded even if not present > > > (you mentioned modprobe.conf) > > > > I mentioned modprobe.preload. Credits to maintainers who still not > > updated mkinitrd and initscripts. > > > > they are going to be loaded if they are configured to be loaded. > > So far we do not have hotplugging for these devices so they are > > going to be configured statically yes. > > may be i'll have to add something similar to the alternative of modprobe.preload > under 2.4(is it /etc/modules ?) yes [...] > > yes but on normal system aren't all mice used as a single input? > that simplifies the situation as /dev/input/mice can be used, or did i miss > smth? > on normal systems people usually have just one mouse :) yes, using /dev/input/mice on both 2.4 and 2.6 would help w.r.t. interoperability. Unless we care about 2.2. Of course there always can be corner cases where people need exactly specific mouse type to access unusual features. > you might also want to check http://people.debian.org/~warp/evdev/ > event interface support for XFree. > anyone knows if this is integrated in mdk XFree? then using /dev/input/evdevN would be yet another alternative. -andrey
