On Tue, 09 Nov 2004 18:50:39 +0100, Martin Pitt wrote:
> However, I was not satisfied with this solution because of several
> reasons:
[Several excellent reasons]
> So the Ubuntu approach is a bit different: we let hal run as normal
> user, do not modify /etc/fstab at all and instead use a pro
Hi!
Marco d'Itri [2004-11-12 11:39 +0100]:
> On Nov 12, Martin Pitt <[EMAIL PROTECTED]> wrote:
> > > BTW, I suggest installing the rules files in /etc/udev/ and then
> > > creating a symlink in the rules.d/ directory.
> > Hmm, the Ubuntu hal package currently places the script directly in
> > rule
On Nov 13, Sjoerd Simons <[EMAIL PROTECTED]> wrote:
> Is there a way to commit these changes in the udev configuration without the
> user needing to reboot. Is it possible to abuse(?) udevstart for this or is
> that a bad idea.
udevstart should work. Maybe.
Another option is to synthesize the hotp
On Fri, Nov 12, 2004 at 10:42:31AM +0100, Marco d'Itri wrote:
> On Nov 10, Martin Pitt <[EMAIL PROTECTED]> wrote:
>
> > I was not sure whether it is valid that packages put their scripts
> > into /etc/udev/rules.d.
> It is as long as they discuss it with me. :-)
> BTW, I suggest installing the rul
On Nov 12, Martin Pitt <[EMAIL PROTECTED]> wrote:
> > BTW, I suggest installing the rules files in /etc/udev/ and then
> > creating a symlink in the rules.d/ directory.
> Hmm, the Ubuntu hal package currently places the script directly in
> rules.d/ (as with any other *.d file) since I did not wan
Hi Marco!
Marco d'Itri [2004-11-12 10:42 +0100]:
> On Nov 10, Martin Pitt <[EMAIL PROTECTED]> wrote:
>
> > I was not sure whether it is valid that packages put their scripts
> > into /etc/udev/rules.d.
> It is as long as they discuss it with me. :-)
> BTW, I suggest installing the rules files in
On Nov 10, Martin Pitt <[EMAIL PROTECTED]> wrote:
> I was not sure whether it is valid that packages put their scripts
> into /etc/udev/rules.d.
It is as long as they discuss it with me. :-)
BTW, I suggest installing the rules files in /etc/udev/ and then
creating a symlink in the rules.d/ directo
On Thu, Nov 11, 2004 at 09:07:12AM +0100, Martin Pitt wrote:
> Hi!
>
> Paul Hampson [2004-11-11 10:03 +1100]:
> > But don't CD-ROM and floppy devices also need the same sort of pmount
> > support you're proposing here? After all, you can hot-swap the media in
> > them, so it seems reasonable to me
Hi!
Marco d'Itri [2004-11-10 14:19 +0100]:
> On Nov 10, Martin Pitt <[EMAIL PROTECTED]> wrote:
>
> > Our /etc/udev/udev.rules has two new rules directly after the cdrom
> > and floppy rules:
> >
> > # put removable IDE/SCSI devices into group 'plugdev' instead of 'disk'
> > BUS="scsi", KERNEL="s
Hi!
Paul Hampson [2004-11-11 10:03 +1100]:
> But don't CD-ROM and floppy devices also need the same sort of pmount
> support you're proposing here? After all, you can hot-swap the media in
> them, so it seems reasonable to me that they can be pmounted? What's the
> rationale for _not_ including th
On Wed, Nov 10, 2004 at 04:43:41PM +0100, Martin Pitt wrote:
> Marco d'Itri [2004-11-10 14:19 +0100]:
> > > Our /etc/udev/udev.rules has two new rules directly after the cdrom
> > > and floppy rules:
> > > # put removable IDE/SCSI devices into group 'plugdev' instead of 'disk'
> > > BUS="scsi", KE
Hi Marco!
Marco d'Itri [2004-11-10 14:19 +0100]:
> > Our /etc/udev/udev.rules has two new rules directly after the cdrom
> > and floppy rules:
> >
> > # put removable IDE/SCSI devices into group 'plugdev' instead of 'disk'
> > BUS="scsi", KERNEL="sd[a-z]*", PROGRAM="/etc/udev/removable.sh %k",
>
On Nov 10, Martin Pitt <[EMAIL PROTECTED]> wrote:
> Our /etc/udev/udev.rules has two new rules directly after the cdrom
> and floppy rules:
>
> # put removable IDE/SCSI devices into group 'plugdev' instead of 'disk'
> BUS="scsi", KERNEL="sd[a-z]*", PROGRAM="/etc/udev/removable.sh %k",
> RESULT="
On Wed, Nov 10, 2004 at 01:25:56PM +0100, Sjoerd Simons wrote:
> On Tue, Nov 09, 2004 at 06:41:40PM +0100, Martin Pitt wrote:
> > We solved (4) by introducing a new group called 'plugdev'. Every user
> > who is a member of this group can access hotpluggable devices (digital
> > cameras, USB drives
On Tue, 09 Nov 2004 19:32:38 +0100, Marco d'Itri wrote:
> On Nov 09, Martin Pitt <[EMAIL PROTECTED]> wrote:
>
>> We solved (4) by introducing a new group called 'plugdev'. Every user
>> who is a member of this group can access hotpluggable devices (digital
>> cameras, USB drives etc.). pmount can
On Tue, Nov 09, 2004 at 06:41:40PM +0100, Martin Pitt wrote:
> We solved (4) by introducing a new group called 'plugdev'. Every user
> who is a member of this group can access hotpluggable devices (digital
> cameras, USB drives etc.). pmount can only be executed by members of
> this group (it is ro
Hi Nikita!
Nikita V. Youshchenko [2004-11-10 14:38 +0300]:
> AFAIK, Sarge is going to be released with 2.6.8.1
>
> I think keeping pmount out of sarge is a bad idea. As long as pmount works
> (it it is *released* with ubuntu, probably it does), and may be useful at
> least from command line, why
> The removable.sh shell script (pasted below) returns whether a device
> is actually removable by looking at the "removable" sysfs attribute.
> However, this attribute was introduced in the kernel not before 2.6.8.
> This is okay for Ubuntu since it ships with 2.6.8.1, and since even
> Sarge ships
Hi Marco!
Marco d'Itri [2004-11-09 19:32 +0100]:
> On Nov 09, Martin Pitt <[EMAIL PROTECTED]> wrote:
>
> > We solved (4) by introducing a new group called 'plugdev'. Every user
> > who is a member of this group can access hotpluggable devices (digital
> > cameras, USB drives etc.). pmount can onl
Hi!
Henning Makholm [2004-11-09 23:28 +]:
> Scripsit [EMAIL PROTECTED] (Paul Hampson)
> > On Tue, Nov 09, 2004 at 06:41:40PM +0100, Martin Pitt wrote:
>
> > > We solved (4) by introducing a new group called 'plugdev'. Every user
> > > who is a member of this group can access hotpluggable devi
Scripsit [EMAIL PROTECTED] (Paul Hampson)
> On Tue, Nov 09, 2004 at 06:41:40PM +0100, Martin Pitt wrote:
> > We solved (4) by introducing a new group called 'plugdev'. Every user
> > who is a member of this group can access hotpluggable devices (digital
> > cameras, USB drives etc.). pmount can on
On Tue, Nov 09, 2004 at 06:41:40PM +0100, Martin Pitt wrote:
> We solved (4) by introducing a new group called 'plugdev'. Every user
> who is a member of this group can access hotpluggable devices (digital
> cameras, USB drives etc.). pmount can only be executed by members of
> this group (it is ro
> So the Ubuntu approach is a bit different: we let hal run as normal
> user, do not modify /etc/fstab at all and instead use a program
> called 'pmount' (policy mount) that allows normal users to mount
> removable devices without an /etc/fstab entries. pmount is now in
It's great to have a pmount
On Nov 09, Martin Pitt <[EMAIL PROTECTED]> wrote:
> We solved (4) by introducing a new group called 'plugdev'. Every user
> who is a member of this group can access hotpluggable devices (digital
> cameras, USB drives etc.). pmount can only be executed by members of
> this group (it is root:plugdev
Hi Debian developers!
I am currently responsible for developing the GNOME Utopia stack for
Ubuntu and closely work together with Sjoerd Simons who maintains the
Debian packages (gnome-volume-manager, hal).
Upstream's idea of automatic USB/FireWire device handling is as
follows: the "hal" daemon r
25 matches
Mail list logo
