Am 25.09.2012 18:49, schrieb Canek Peláez Valdés:
> On Tue, Sep 25, 2012 at 3:32 AM, Stefan G. Weichinger wrote:
>> Am 25.09.2012 10:09, schrieb Stefan G. Weichinger:
>>
>>> So if I don't use systemd right now, it would be better to keep
>>> consolekit? I give it a try now ... compiling stuff with
On Tue, Sep 25, 2012 at 3:32 AM, Stefan G. Weichinger wrote:
> Am 25.09.2012 10:09, schrieb Stefan G. Weichinger:
>
>> So if I don't use systemd right now, it would be better to keep
>> consolekit? I give it a try now ... compiling stuff without that flag
>> for a test.
>
> Did not work. Rather ea
Am 25.09.2012 10:09, schrieb Stefan G. Weichinger:
> So if I don't use systemd right now, it would be better to keep
> consolekit? I give it a try now ... compiling stuff without that flag
> for a test.
Did not work. Rather easy to understand, if neither systemd or
consolekit is there, how should
Am 25.09.2012 08:33, schrieb Canek Peláez Valdés:
> On Mon, Sep 17, 2012 at 10:45 AM, Stefan G. Weichinger wrote:
>> Am 16.09.2012 20:45, schrieb Canek Peláez Valdés:
>>
>>> This workaround also works in my systemd-only overlay. So, if you have
>>> the systemd flag in any of those four packages, d
On Mon, Sep 17, 2012 at 10:45 AM, Stefan G. Weichinger wrote:
> Am 16.09.2012 20:45, schrieb Canek Peláez Valdés:
>
>> This workaround also works in my systemd-only overlay. So, if you have
>> the systemd flag in any of those four packages, disable it and
>> everything should work. Just to be expl
Am 16.09.2012 20:45, schrieb Canek Peláez Valdés:
> This workaround also works in my systemd-only overlay. So, if you have
> the systemd flag in any of those four packages, disable it and
> everything should work. Just to be explicit, the versions are:
>
> gnome-base/gdm-3.4.1-r1
> gnome-base/gno
Am 16.09.2012 20:45, schrieb Canek Peláez Valdés:
> On Fri, Sep 14, 2012 at 12:42 AM, Stefan G. Weichinger wrote:
> [snip]
>> Great to hear, thanks so far.
>> Looking forward to his reply
>
> Stefan, do you use systemd?
I don't boot with systemd now (yes, kinda green) ... but have the
USE-
On Fri, Sep 14, 2012 at 12:42 AM, Stefan G. Weichinger wrote:
[snip]
> Great to hear, thanks so far.
> Looking forward to his reply
Stefan, do you use systemd? David told me that he could only check the
bug on monday, so I did a little research on the weekend. I installed
Gentoo in a QEMU VM
Am 2012-09-13 20:56, schrieb Canek Peláez Valdés:
> On Thu, Sep 13, 2012 at 1:08 PM, Stefan G. Weichinger wrote:
>> Am 13.09.2012 19:48, schrieb Canek Peláez Valdés:
>>> On Thu, Sep 13, 2012 at 12:29 PM, Canek Peláez Valdés
>>> wrote:
>>> [snip]
I actually hadn't thought about downgrading p
On Thu, Sep 13, 2012 at 09:19:19AM -0500, Canek Pel??ez Vald??s wrote
> On Thu, Sep 13, 2012 at 1:50 AM, Walter Dnes wrote:
> > A normal user can pumount *WHAT THAT SAME USER* has pmounted. Now try
> > for a general solution.
>
> The general solution is using something like udisks+polkit. Tha
On Thu, Sep 13, 2012 at 1:08 PM, Stefan G. Weichinger wrote:
> Am 13.09.2012 19:48, schrieb Canek Peláez Valdés:
>> On Thu, Sep 13, 2012 at 12:29 PM, Canek Peláez Valdés
>> wrote:
>> [snip]
>>> I actually hadn't thought about downgrading polkit, since it was
>>> working with the same version in
Am 13.09.2012 19:48, schrieb Canek Peláez Valdés:
> On Thu, Sep 13, 2012 at 12:29 PM, Canek Peláez Valdés
> wrote:
> [snip]
>> I actually hadn't thought about downgrading polkit, since it was
>> working with the same version in GNOME 3.2. Or maybe it was a fluke
>> (the bug is reproducible, but s
Am 13.09.2012 19:31, schrieb Canek Peláez Valdés:
> Oh, BTW; I just run /usr/sbin/libvirtd --verbose as my user before
> starting boxes; everything works. It also works invoking qemu by hand.
I rebuilt libvirt without the polkit-USE-flag. Standalone box for
myself, unix-auth is enough ... IMO.
S
Am 13.09.2012 19:29, schrieb Canek Peláez Valdés:
> $ /usr/lib/polkit-1/polkitd --replace --no-debug
I think you want debug ... so:
$ /usr/lib/polkit-1/polkitd --replace
right?
No additional output here, tried clicking user-menu (upper right) as
mentioned in your bug-report ...
>> I fixed it
On Thu, Sep 13, 2012 at 12:29 PM, Canek Peláez Valdés wrote:
[snip]
> I actually hadn't thought about downgrading polkit, since it was
> working with the same version in GNOME 3.2. Or maybe it was a fluke
> (the bug is reproducible, but sometimes I need to try several times).
> I will try downgrad
On Thu, Sep 13, 2012 at 12:14 PM, Stefan G. Weichinger wrote:
> Am 13.09.2012 18:41, schrieb Canek Peláez Valdés:
>
>> It doesn't, but I was under the assumption it was because I'm using
>> systemd. Since I installed gnome-shell-3.4 this has stopped working;
>> my findings can be seen on the bug t
On Thu, Sep 13, 2012 at 12:14 PM, Stefan G. Weichinger wrote:
> Am 13.09.2012 18:41, schrieb Canek Peláez Valdés:
>
>> It doesn't, but I was under the assumption it was because I'm using
>> systemd. Since I installed gnome-shell-3.4 this has stopped working;
>> my findings can be seen on the bug t
Am 13.09.2012 18:41, schrieb Canek Peláez Valdés:
> It doesn't, but I was under the assumption it was because I'm using
> systemd. Since I installed gnome-shell-3.4 this has stopped working;
> my findings can be seen on the bug to freedesktop.org:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=
On Thu, Sep 13, 2012 at 11:21 AM, Stefan G. Weichinger wrote:
> Am 13.09.2012 16:19, schrieb Canek Peláez Valdés:
>
>> The general solution is using something like udisks+polkit.
>
> I have troubles with that combo for a month or so ... seems as if
> polkit-0.107 somehow is responsible for stuff n
Am 13.09.2012 16:19, schrieb Canek Peláez Valdés:
> The general solution is using something like udisks+polkit.
I have troubles with that combo for a month or so ... seems as if
polkit-0.107 somehow is responsible for stuff not mounted here.
~amd64 btw, gnome-3-context.
udisks comes (/is instal
On Thu, Sep 13, 2012 at 9:42 AM, Neil Bothwick wrote:
> On Thu, 13 Sep 2012 09:19:19 -0500, Canek Peláez Valdés wrote:
>
>> > A normal user can pumount *WHAT THAT SAME USER* has pmounted. Now
>> > try for a general solution.
>>
>> The general solution is using something like udisks+polkit. That
On Thu, 13 Sep 2012 09:19:19 -0500, Canek Peláez Valdés wrote:
> > A normal user can pumount *WHAT THAT SAME USER* has pmounted. Now
> > try for a general solution.
>
> The general solution is using something like udisks+polkit. That is a
> true general solution; otherwise you end up like th
On Thu, Sep 13, 2012 at 1:50 AM, Walter Dnes wrote:
> On Wed, Sep 12, 2012 at 09:03:50AM +0100, Neil Bothwick wrote
>
>> I don't understand, why are you using sudo to run pmount when its core
>> purpose is to be run by normal users?
>>
>> % whatis pmount
>> pmount (1) - mount arbitrary hotplugga
On Thu, 13 Sep 2012 02:50:27 -0400, Walter Dnes wrote:
> > I don't understand, why are you using sudo to run pmount when its core
> > purpose is to be run by normal users?
> >
> > % whatis pmount
> > pmount (1) - mount arbitrary hotpluggable devices as normal user
>
> A normal user can pum
On Wed, Sep 12, 2012 at 09:03:50AM +0100, Neil Bothwick wrote
> I don't understand, why are you using sudo to run pmount when its core
> purpose is to be run by normal users?
>
> % whatis pmount
> pmount (1) - mount arbitrary hotpluggable devices as normal user
A normal user can pumount *WHA
120911 Neil Bothwick was worried at the idea
of leaving a root console open for all to access:
My machine is not accessible to anyone else, so it's not a problem here.
Yes, it's not a good idea if you're in a data centre or open-plan office.
--
,,=
On Tue, 11 Sep 2012 22:47:21 -0400, Walter Dnes wrote:
> Fully agree that's a bad idea. My system uses sudoers. I.e. in
> /etc/sudoers.d/001 I have the lines...
>
> user2 d531 = (root) NOPASSWD: /usr/local/bin/ux *
> waltdnes d531 = (root) NOPASSWD: /usr/local/bin/ux *
>
> ...where /usr
On Tue, Sep 11, 2012 at 11:51:30PM +0100, Neil Bothwick wrote
> It's the idea of leaving a root console open for all to access that is
> the issue, not the commands you run in it.
Fully agree that's a bad idea. My system uses sudoers. I.e. in
/etc/sudoers.d/001 I have the lines...
user2
On Tue, 11 Sep 2012 17:55:41 -0400, Walter Dnes wrote:
> > > I goto the root console which is always open on one of my desktops
> > > & enter 'musb', which is a Bash alias for a 'mount' command;
> >
> > Leaving aside the implications of leaving open a root console,
>
> My scripts use pmoun
On Tue, Sep 11, 2012 at 5:55 PM, Walter Dnes wrote:
> On Tue, Sep 11, 2012 at 10:41:22AM +0100, Neil Bothwick wrote
>
> > > I goto the root console which is always open on one of my desktops
> > > & enter 'musb', which is a Bash alias for a 'mount' command;
> >
> > Leaving aside the implications
On Tue, Sep 11, 2012 at 10:41:22AM +0100, Neil Bothwick wrote
> > I goto the root console which is always open on one of my desktops
> > & enter 'musb', which is a Bash alias for a 'mount' command;
>
> Leaving aside the implications of leaving open a root console,
My scripts use pmount and pum
On Tue, Sep 11, 2012 at 10:30 AM, Chris Stankevitz
wrote:
> On Mon, Sep 10, 2012 at 10:03 PM, Walter Dnes wrote:
>> Every time that a USB device is inserted or removed, an
>> "event" is triggered by the kernel. What's required is an "event
>> handler" that reacts appropriately to those events.
On Mon, Sep 10, 2012 at 10:03 PM, Walter Dnes wrote:
> Every time that a USB device is inserted or removed, an
> "event" is triggered by the kernel. What's required is an "event
> handler" that reacts appropriately to those events. This is usually
> udev, but mdev will also work. I've replaced
On Tue, 11 Sep 2012 04:56:21 -0400, Philip Webb wrote:
> Why do people want to automount these sticks ?
Because it is easy and convenient, something computers are supposed to be
good for.
> I goto the root console which is always open on one of my desktops
> & enter 'musb', which is a Bash alias
120911 Walter Dnes wrote:
> On Mon, Sep 10, 2012 Chris Stankevitz asked how to automount a USB stick :
> A GUI is not necessary. Every time a USB device is inserted or removed,
> an "event" is triggered by the kernel. What's required is
> an "event handler" that reacts appropriately to those even
On Mon, Sep 10, 2012 at 03:56:20PM -0700, Chris Stankevitz wrote
> Also, ideally after I know about it I'd like to be able to
> "understand" and derive on my own the answer to this question:
> "is it possible for TWM to recognize when I plug in a USB thumbdrive
> and display it for me to use."
Hello,
Can someone refer me to a source that explains how when I plug in a
USB "thumb drive" it appears on my XFCE4 desktop (or any other WM)?
Ideally the answer will use words like:
daemon
hal
udev
policykit
consolekit
/etc/init.d/*
hotplug
gvfs
mount
automount
pmount
gnome-volume-manager
udisks
On 11/17/2011 04:54 P, Neil Bothwick wrote:
> I thought that pcmanfm, the LXDE file manager, had a context menu
> option to unmount.
>
Me too, and I think that a long time ago I did have it, but now it's
not there. Probably I'd better try on the lxde mailing list.
thanks,
raf
On Thu, 17 Nov 2011 15:58:03 +0100, Raffaele BELARDI wrote:
> The ArchWiki link on Udev posted by James shows how to set a rule for
> un-mounting:
>
> ACTION=="remove", ENV{dir_name}!="", RUN+="/bin/su tomk -c
> '/usr/bin/pumount /media/%E{dir_name}'"
>
> Based on your feedback I suppose the sam
On 11/17/2011 03:06 PM, Neil Bothwick wrote:
> On Thu, 17 Nov 2011 14:22:35 +0100, Raffaele BELARDI wrote:
>> 3. uam: does not require fiddling with udev rules but cannot
>> un-mount
>
> 3 is wrong, you can unmount with pmount, exactly the same as with
> 1.
>
> uam is basically a set of udev rule
On Thu, 17 Nov 2011 14:22:35 +0100, Raffaele BELARDI wrote:
> 1. udev rules: mounts automatically, with pmount can do non-root
> un-mounting 2. mdev: according to the man page works only at system boot
> 3. uam: does not require fiddling with udev rules but cannot un-mount
>
> I suppose I'll go w
On 11/17/2011 11:37 AM, Neil Bothwick wrote:
> On Thu, 17 Nov 2011 10:07:11 +0100, Raffaele BELARDI wrote:
>> When I need to mount a removable USB device on LXDE (~amd64) I currently
>> manually issue the mount command. What do I need to do to make
>> automounting possible?
>
> The simplest option
On Thu, 17 Nov 2011 10:07:11 +0100, Raffaele BELARDI wrote:
> When I need to mount a removable USB device on LXDE (~amd64) I currently
> manually issue the mount command. What do I need to do to make
> automounting possible?
The simplest option is to emerge uam.
--
Neil Bothwick
Will the last
On Nov 17, 2011 4:51 PM, "James Broadhead" wrote:
>
> On 17 November 2011 09:07, Raffaele BELARDI
wrote:
> > When I need to mount a removable USB device on LXDE (~amd64) I currently
> > manually issue the mount command. What do I need to do to make
> > automounting possible?
> >
> > According to
On 17 November 2011 09:07, Raffaele BELARDI wrote:
> When I need to mount a removable USB device on LXDE (~amd64) I currently
> manually issue the mount command. What do I need to do to make
> automounting possible?
>
> According to LXDE wiki (1) you need HAL, which I don't have on my
> system. I
When I need to mount a removable USB device on LXDE (~amd64) I currently
manually issue the mount command. What do I need to do to make
automounting possible?
According to LXDE wiki (1) you need HAL, which I don't have on my
system. I found several suggestions on the net but none seems promising.
46 matches
Mail list logo
