Re: [arch-general] Why does a regular user have access to /dev/uinput (and why only temporary)

I've been searching a little more and found it: https://bugs.archlinux.org/task/47995 On 02/02/2016 06:41 PM, Manuel Reimer wrote: Hello, I'm currently developing a usermode input driver using uinput. While doing this, I've found some "ugly" behaviour. If I do getfacl from my regular user,

Re: [arch-general] Why does a regular user have access to /dev/uinput (and why only temporary)

>> $ getfacl /dev/uinput >> getfacl: Removing leading '/' from absolute path names >> # file: dev/uinput >> # owner: root >> # group: root >> user::rw- >> user:manuel:rw-#effective:--- >> group::--- >> mask::--- >> other::--- >> >> So somehow the permission is still there, but no

[arch-general] systemd user accounts are created in a inconsistent way

Most systemd user accounts are present in the /etc/passwd file provided by the filesystem package. This is not the case for only two of them, namely systemd-journal-upload and systemd-journal-remote, which are set up by systemd-sysusers, executed when the systemd package is installed. Is there a

Re: [arch-general] pacman and hooks

Stefan Tatschner writes: > On 01.02.2016 23:05, Magnus Therning wrote: >> Is there more information about this feature available somewhere? > > $ man 5 alpm-hooks Excellent. I also found this https://github.com/andrewgregory/pachooks. I'm guessing that link contains one erroneos bit of

Re: [arch-general] systemd user accounts are created in a inconsistent way

On 2 February 2016 at 21:28, Daniel Milewski wrote: > Most systemd user accounts are present in the /etc/passwd file provided > by the filesystem package. This is not the case for only two of them, > namely systemd-journal-upload and systemd-journal-remote, which are set >

Re: [arch-general] systemd user accounts are created in a inconsistent way

Op 2 feb. 2016 22:24 schreef "Damjan Georgievski" : > it's better to let `systemd-sysusers` create all users, /etc/passwd > should probably not be included in any package > since it changes in the lifetime of the distro and updates are hard to merge. Agreed. And while we're at

Re: [arch-general] pacman and hooks

On Tue, 02 Feb 2016 23:25:58 +0100 Magnus Therning wrote: > Stefan Tatschner writes: > > > On 01.02.2016 23:05, Magnus Therning wrote: > >> Is there more information about this feature available somewhere? > > > > $ man 5 alpm-hooks > > Excellent. I also found this

Re: [arch-general] pacman and hooks

Doug Newgard writes: > On Tue, 02 Feb 2016 23:25:58 +0100 > Magnus Therning wrote: > >> Stefan Tatschner writes: >> >> > On 01.02.2016 23:05, Magnus Therning wrote: >> >> Is there more information about this feature available somewhere? >> > >> > $ man 5 alpm-hooks

Re: [arch-general] pacman and hooks

On Tue, 02 Feb 2016 23:51:16 +0100 Magnus Therning wrote: > Doug Newgard writes: > > > On Tue, 02 Feb 2016 23:25:58 +0100 > > Magnus Therning wrote: > > > >> Stefan Tatschner writes: > >> > >> > On 01.02.2016 23:05, Magnus Therning wrote: > >>

Re: [arch-general] pacman and hooks

On 02/02/2016 06:54 PM, Doug Newgard wrote: > No, even those are for packages. Users/admins should use /etc/pacman.d/hooks. > Not sure about scripts. I would guess that scripts can be put anywhere, I would probably just put them in the HookDir (matching *.{hook,sh} files). But why would anyone

Re: [arch-general] pacman and hooks

On 02/02/16 at 08:43pm, Eli Schwartz wrote: > On 02/02/2016 06:54 PM, Doug Newgard wrote: > > No, even those are for packages. Users/admins should use > > /etc/pacman.d/hooks. > > Not sure about scripts. > > I would guess that scripts can be put anywhere, I would probably just > put them in the

Re: [arch-general] pacman and hooks

On Tue, 2 Feb 2016 21:06:14 -0500 Eli Schwartz wrote: > On 02/02/2016 09:00 PM, Andrew Gregory wrote: > > Neither hooks.bin nor hooks.local are used by alpm/pacman in any way. > > They are merely my own personal suggestions for where packages should > > put scripts and

Re: [arch-general] btrfs/snapper hook for pacman 5.0?

Hi, Am 02.02.2016 um 01:32 schrieb Andrew Gregory: > https://github.com/andrewgregory/pachooks thank you very much. This is basically exactly what I was looking for and I will have a play with it. By the way: When exactly and how often are the PreTransaction and PostTransaction actions

Re: [arch-general] btrfs/snapper hook for pacman 5.0?

Hi, Am 02.02.2016 um 04:30 schrieb Leonid Isaev: > Thanks. But /boot can not be snapshot with this, right? technically you can snapshot whatever you want. snapper can also (kind of) work with LVM and ext4, so btrfs is not an absolute requirement. Bootloaders can boot from btrfs. The only

Re: [arch-general] btrfs/snapper hook for pacman 5.0?

Hi, Am 02.02.2016 um 10:16 schrieb Karol Babioch: > When exactly and how often are the PreTransaction and > PostTransaction actions executed? Are they executed for each and every > package, or for each invocation of pacman itself, i.e. once per upgrade > (of multiple packages)? after having a

Re: [arch-general] btrfs/snapper hook for pacman 5.0?

> https://github.com/andrewgregory/pachooks do hook files need to end in .hook ? I couldn't find it mentioned in man alpm-hooks or pacman -- damjan

Re: [arch-general] btrfs/snapper hook for pacman 5.0?

Am 02.02.2016 um 10:40 schrieb Damjan Georgievski: https://github.com/andrewgregory/pachooks do hook files need to end in .hook ? I couldn't find it mentioned in man alpm-hooks or pacman Yes, a hook ends in .hook, that should be mentioned somewhere. I had to check the sourcecode:

Re: [arch-general] btrfs/snapper hook for pacman 5.0?

Am 2016-02-02 um 14:53 schrieb Karol Babioch: Hi, Am 02.02.2016 um 14:15 schrieb Elmar Stellnberger: However you may implement this feature please make sure that it takes care of the availabel disk space! Most people do only have limited space on their root partition and by making numerous

Re: [arch-general] btrfs/snapper hook for pacman 5.0?

On 2 February 2016 at 10:40, Damjan Georgievski wrote: >> https://github.com/andrewgregory/pachooks > > do hook files need to end in .hook ? > I couldn't find it mentioned in man alpm-hooks or pacman Also, `Exec =` requires a full path to the executable -- damjan

[arch-general] Why does a regular user have access to /dev/uinput (and why only temporary)

Hello, I'm currently developing a usermode input driver using uinput. While doing this, I've found some "ugly" behaviour. If I do getfacl from my regular user, I get: $ getfacl /dev/uinput getfacl: Removing leading '/' from absolute path names # file: dev/uinput # owner: root # group: root

Re: [arch-general] pacman and hooks

On 02/02/2016 09:00 PM, Andrew Gregory wrote: > Neither hooks.bin nor hooks.local are used by alpm/pacman in any way. > They are merely my own personal suggestions for where packages should > put scripts and inactive hooks. The intent for hooks.local is for > packages to place any hooks that

Re: [arch-general] btrfs/snapper hook for pacman 5.0?

However you may implement this feature please make sure that it takes care of the availabel disk space! Most people do only have limited space on their root partition and by making numerous snapshots your hard drive will be clobbered soon. Besides this the feature should stop automatically

Re: [arch-general] btrfs/snapper hook for pacman 5.0?

Hi, Am 02.02.2016 um 14:15 schrieb Elmar Stellnberger: > However you may implement this feature please make sure that it takes > care of the availabel disk space! Most people do only have limited space > on their root partition and by making numerous snapshots your hard drive > will be clobbered