2 kernels, 2 different mice locations

2 kernels, 2 different mice locations

[Aymeric O.]

[-- Attachment #1: Type: text/plain, Size: 827 bytes --]

Hi,


I'm using 2 kernels on my distribution. The "official" one is 2.6.32,
and I'm providing a 2.6.29.6-rt24 for those who want to use RealTime.
But since we upgraded udev to the latest version, some of /dev files are
placed at different locations depending on which kernel is used.

With 2.6.32, everything works fine, but now, when I boot with
2.6.29.6-rt24, I cannot move my mouse unless I symlink /dev/mice to
/dev/input/mice. And it doesn't completely work, because I'm unable to
scroll.

I'm not familiar with udev, so I don't really know why older kernels
don't seem to be able to use udev the same way. I tried with the
development version of the RT kernel, which patches 2.6.31, and all
worked fine.

Can you give me some clues to make my system be able to boot right with
my RT kernel?


Thanks in advance,
Aymeric.

[-- Attachment #2: 0xEF3AF04D.asc --]
[-- Type: application/pgp-keys, Size: 2116 bytes --]

Re: 2 kernels, 2 different mice locations

[Kay Sievers]

2010/2/17 Aymeric O. <ejisneos@gmail.com>:
> I'm using 2 kernels on my distribution. The "official" one is 2.6.32,
> and I'm providing a 2.6.29.6-rt24 for those who want to use RealTime.
> But since we upgraded udev to the latest version, some of /dev files are
> placed at different locations depending on which kernel is used.
>
> With 2.6.32, everything works fine, but now, when I boot with
> 2.6.29.6-rt24, I cannot move my mouse unless I symlink /dev/mice to
> /dev/input/mice. And it doesn't completely work, because I'm unable to
> scroll.

New udev versions and old kernels need some old udev rules to name
device nodes. You should be able to use the Gentoo rules, which seem
to support this:
  http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;f=rules/gentoo/30-kernel-compat.rules;hb=HEAD

Kay

Re: 2 kernels, 2 different mice locations

[Aymeric O.]

[-- Attachment #1: Type: text/plain, Size: 995 bytes --]

That did the trick!
I will be able to provide a new stable RT kernel, now.

Thank you very much!


(2010年02月17日 14:57), Kay Sievers wrote:
> 2010/2/17 Aymeric O. <ejisneos@gmail.com>:
>   
>> I'm using 2 kernels on my distribution. The "official" one is 2.6.32,
>> and I'm providing a 2.6.29.6-rt24 for those who want to use RealTime.
>> But since we upgraded udev to the latest version, some of /dev files are
>> placed at different locations depending on which kernel is used.
>>
>> With 2.6.32, everything works fine, but now, when I boot with
>> 2.6.29.6-rt24, I cannot move my mouse unless I symlink /dev/mice to
>> /dev/input/mice. And it doesn't completely work, because I'm unable to
>> scroll.
>>     
> New udev versions and old kernels need some old udev rules to name
> device nodes. You should be able to use the Gentoo rules, which seem
> to support this:
>   http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;f=rules/gentoo/30-kernel-compat.rules;hb=HEAD
>
> Kay
>   


[-- Attachment #2: 0xEF3AF04D.asc --]
[-- Type: application/pgp-keys, Size: 2116 bytes --]

Re: 2 kernels, 2 different mice locations

[Aymeric O.]

[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]

I just noticed raw1394 is owned by the "root" group, but it should be
owned by "disk" so it could be used by a regular user. This problem
occurs with both kernels. Is it a udev problem or should our udev be
added some rules to solve this?


(2010年02月17日 14:57), Kay Sievers wrote:
> 2010/2/17 Aymeric O. <ejisneos@gmail.com>:
>   
>> I'm using 2 kernels on my distribution. The "official" one is 2.6.32,
>> and I'm providing a 2.6.29.6-rt24 for those who want to use RealTime.
>> But since we upgraded udev to the latest version, some of /dev files are
>> placed at different locations depending on which kernel is used.
>>
>> With 2.6.32, everything works fine, but now, when I boot with
>> 2.6.29.6-rt24, I cannot move my mouse unless I symlink /dev/mice to
>> /dev/input/mice. And it doesn't completely work, because I'm unable to
>> scroll.
>>     
> New udev versions and old kernels need some old udev rules to name
> device nodes. You should be able to use the Gentoo rules, which seem
> to support this:
>   http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;f=rules/gentoo/30-kernel-compat.rules;hb=HEAD
>
> Kay
>   


[-- Attachment #2: 0xEF3AF04D.asc --]
[-- Type: application/pgp-keys, Size: 2116 bytes --]

Re: 2 kernels, 2 different mice locations

[Kay Sievers]

On Wed, Feb 17, 2010 at 22:40, Aymeric O. <ejisneos@gmail.com> wrote:
> I just noticed raw1394 is owned by the "root" group, but it should be
> owned by "disk" so it could be used by a regular user. This problem
> occurs with both kernels. Is it a udev problem or should our udev be
> added some rules to solve this?

Default installations don't want that, because of security concerns
with firewire and DMA access.

The old firewire stack is deprecated now and replaced with new
drivers, so these rules will not be there for very long anymore.

No regular user should ever be in the group "disk". It will allow to
reformat all system partitions. Historically "disk" is more for backup
programs.

Also raw1394 has not much to do with "disk". :)

Kay

Re: 2 kernels, 2 different mice locations

[Aymeric O.]

[-- Attachment #1: Type: text/plain, Size: 993 bytes --]

So that means that libraw1394
(http://sourceforge.net/projects/libraw1394/) must be up to date from
now on? If so, I will ask its maintainer for it.


(2010年02月17日 22:57), Kay Sievers wrote:
> On Wed, Feb 17, 2010 at 22:40, Aymeric O. <ejisneos@gmail.com> wrote:
>   
>> I just noticed raw1394 is owned by the "root" group, but it should be
>> owned by "disk" so it could be used by a regular user. This problem
>> occurs with both kernels. Is it a udev problem or should our udev be
>> added some rules to solve this?
>>     
> Default installations don't want that, because of security concerns
> with firewire and DMA access.
>
> The old firewire stack is deprecated now and replaced with new
> drivers, so these rules will not be there for very long anymore.
>
> No regular user should ever be in the group "disk". It will allow to
> reformat all system partitions. Historically "disk" is more for backup
> programs.
>
> Also raw1394 has not much to do with "disk". :)
>
> Kay
>   


[-- Attachment #2: 0xEF3AF04D.asc --]
[-- Type: application/pgp-keys, Size: 2116 bytes --]