From: "Aymeric O." <ejisneos@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2 kernels, 2 different mice locations
Date: Wed, 17 Feb 2010 22:19:24 +0000 [thread overview]
Message-ID: <4B7C6B6C.9060203@mailoo.org> (raw)
In-Reply-To: <4B7BC06B.50004@mailoo.org>
[-- 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 --]
prev parent reply other threads:[~2010-02-17 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 10:09 2 kernels, 2 different mice locations Aymeric O.
2010-02-17 13:57 ` Kay Sievers
2010-02-17 18:35 ` Aymeric O.
2010-02-17 21:40 ` Aymeric O.
2010-02-17 21:57 ` Kay Sievers
2010-02-17 22:19 ` Aymeric O. [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B7C6B6C.9060203@mailoo.org \
--to=ejisneos@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.