Re: [systemd-devel] [PATCH 1/2] test: add basic seccomp tests

2014-02-12 Thread Dave Reisner
On Thu, Jan 23, 2014 at 01:34:57AM +0100, Ronny Chevalier wrote: > --- > test/TEST-04-SECCOMP/Makefile | 1 + > test/TEST-04-SECCOMP/test-seccomp.sh| 11 > test/TEST-04-SECCOMP/test.sh| 79 > + > test/TEST-04-SECCOMP/will-fai

Re: [systemd-devel] [PATCH] rules: name Dell iDRAC virtual usb nic

2014-02-12 Thread Charles_Rose
On 02/12/2014 09:21 AM, Kay Sievers wrote: > On Wed, Feb 12, 2014 at 2:12 PM, wrote: > > From: Charles Rose > > > > Dell servers contain a virtual usb nic for systems management. > > Name the device 'idrac' to easily identify it. > > The 75-net-description.rules is doe describe interfaces, n

Re: [systemd-devel] How to prevent sleep during running oneshot units

2014-02-12 Thread Mirco Tischler
Am 13.02.2014 00:14 schrieb "Kai Krakow" : > > Mirco Tischler schrieb: > > > It's late here so excuse me if I'm missing something. But wouldn't a > > simple Before=sleep.target suffice to implement b)? > > I'm not sure... The unit is not enabled, only triggered by the timer - so it > may work. I t

Re: [systemd-devel] How to prevent sleep during running oneshot units

2014-02-12 Thread Kai Krakow
Mirco Tischler schrieb: > It's late here so excuse me if I'm missing something. But wouldn't a > simple Before=sleep.target suffice to implement b)? I'm not sure... The unit is not enabled, only triggered by the timer - so it may work. I think I may try that as an alternative to systemd-inhibit

Re: [systemd-devel] How to prevent sleep during running oneshot units

2014-02-12 Thread Kai Krakow
Zbigniew Jędrzejewski-Szmek schrieb: >> No, you need to wrap your command with it. I.e. instead of >> >> ExecStart=/path/to/backup-command ... >> >> you use >> >> ExecStart=/usr/bin/systemd-inhibit /path/to/backup-command ... > Right. Not too bad, but Inhibits=sleep sounds nice. I probably try t

[systemd-devel] [PATCH 2/3] Fix keysize handling in cryptsetup (bits vs. bytes)

2014-02-12 Thread David Härdeman
The command line key-size is in bits but the libcryptsetup API expects bytes. --- src/cryptsetup/cryptsetup.c |8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/src/cryptsetup/cryptsetup.c b/src/cryptsetup/cryptsetup.c index f72cf9f..e7e8066 100644 --- a/src/cryptsetup/

[systemd-devel] [PATCH 1/3] Add more password agent information

2014-02-12 Thread David Härdeman
Add an (optional) "Id" key in the password agent .ask files. The Id is supposed to be a simple string in ":" form which is used to provide more information on what the requested passphrase is to be used for (which e.g. allows an agent to only react to cryptsetup requests). --- src/ask-password/ask

[systemd-devel] [PATCH 3/3] Fix askpass buffer overflow

2014-02-12 Thread David Härdeman
Fix askpass overflow in reading a passphrase from a tty. Doesn't seem security sensitive, but add a check for correctness. --- src/shared/ask-password-api.c |5 + 1 file changed, 5 insertions(+) diff --git a/src/shared/ask-password-api.c b/src/shared/ask-password-api.c index 1c18274..045c

[systemd-devel] [PATCH 0/3] Password agent fixes

2014-02-12 Thread David Härdeman
The following series contains patch 1 - 3 of the previous patchset that I've posted. Lennart wanted a single "Id=" instead of the two "Purpose=" and "Target=" strings in the .ask files, so I've changed it accordingly. The two following patches are just small fixes. I've left out the binary protoc

Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread Greg KH
On Wed, Feb 12, 2014 at 11:12:07PM +0100, Reindl Harald wrote: > > the major point of my critism is systemd-upstream's "release-and-forget" > with no point releases at all and the state of systemd in F20 makes that > not looking like a working strategy overstraining downstream maintainers > > tha

Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread Kay Sievers
On Wed, Feb 12, 2014 at 11:12 PM, Reindl Harald wrote: > my tone is ok, if someone can't stand critism that's a different problem layer Your tone is not ok. This is a development mailing list and not a bitching or product discussion channel. What you do is not appropriate or welcome here. If t

Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread Reindl Harald
Am 12.02.2014 22:41, schrieb Jóhann B. Guðmundsson: > On 02/12/2014 07:37 PM, Reindl Harald wrote: >> these are all regressions from F19 to F20 >> https://bugzilla.redhat.com/show_bug.cgi?id=1023820 >> https://bugzilla.redhat.com/show_bug.cgi?id=1010572 >> https://bugzilla.redhat.com/show_bug.cgi?

Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread Jóhann B. Guðmundsson
On 02/12/2014 07:37 PM, Reindl Harald wrote: these are all regressions from F19 to F20 https://bugzilla.redhat.com/show_bug.cgi?id=1023820 https://bugzilla.redhat.com/show_bug.cgi?id=1010572 https://bugzilla.redhat.com/show_bug.cgi?id=1057811 https://bugzilla.redhat.com/show_bug.cgi?id=1057618 h

Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread Tomasz Torcz
On Wed, Feb 12, 2014 at 12:45:50PM -0800, David Timothy Strauss wrote: > On Wed, Feb 12, 2014 at 12:37 PM, Tomasz Torcz wrote: > > That's some downstream distro bug. And this is Fedora mailinglist. > > RHEL issues are offtopic here. > > This is not a Fedora mailing list at all. Ouch. I'm sor

Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread David Timothy Strauss
On Wed, Feb 12, 2014 at 12:37 PM, Tomasz Torcz wrote: > That's some downstream distro bug. And this is Fedora mailinglist. > RHEL issues are offtopic here. This is not a Fedora mailing list at all. ___ systemd-devel mailing list [email protected]

Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread Reindl Harald
my last post for this topic before i get blocked again by disturbing development in peace with real user problems i thought so once per month it's woth to make notice Am 12.02.2014 21:37, schrieb Tomasz Torcz: > On Wed, Feb 12, 2014 at 08:05:47PM +0100, Reindl Harald wrote: >> https://bugzill

Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread Tomasz Torcz
On Wed, Feb 12, 2014 at 08:05:47PM +0100, Reindl Harald wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1047614 > > Product: Red Hat Enterprise Linux 7 > Component:systemd (Show other bugs) > Version: 7.0 That's some downstream distro bug. And this is Fedora mailinglist. RHE

Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread Reindl Harald
Am 12.02.2014 21:19, schrieb Lennart Poettering: > On Wed, 12.02.14 20:05, Reindl Harald ([email protected]) wrote: > >> https://bugzilla.redhat.com/show_bug.cgi?id=1047614 >> >> Product: Red Hat Enterprise Linux 7 >> Component: systemd (Show other bugs) >> Version: 7.0 >> Hardwar

Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread Lennart Poettering
On Wed, 12.02.14 20:05, Reindl Harald ([email protected]) wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1047614 > > Product: Red Hat Enterprise Linux 7 > Component:systemd (Show other bugs) > Version: 7.0 > Hardware: Unspecified Unspecified > Priority urgent Sev

Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread Reindl Harald
Am 12.02.2014 20:18, schrieb Greg KH: > On Wed, Feb 12, 2014 at 08:05:47PM +0100, Reindl Harald wrote: >> https://bugzilla.redhat.com/show_bug.cgi?id=1047614 >> >> Product: Red Hat Enterprise Linux 7 >> Component: systemd (Show other bugs) >> Version: 7.0 >> Hardware:Unspecified Uns

Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread Greg KH
On Wed, Feb 12, 2014 at 08:05:47PM +0100, Reindl Harald wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1047614 > > Product: Red Hat Enterprise Linux 7 > Component:systemd (Show other bugs) > Version: 7.0 > Hardware: Unspecified Unspecified > Priority urgent Severity hi

[systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614

2014-02-12 Thread Reindl Harald
https://bugzilla.redhat.com/show_bug.cgi?id=1047614 Product:Red Hat Enterprise Linux 7 Component: systemd (Show other bugs) Version:7.0 Hardware: Unspecified Unspecified Priorityurgent Severity high first reported more than 3 months ago https://bugzilla.redhat.c

Re: [systemd-devel] Misleading InterfaceStabilityPromise wiki page (due to formatting)

2014-02-12 Thread Kay Sievers
On Wed, Feb 12, 2014 at 6:59 PM, Elijah Newren wrote: > At http://www.freedesktop.org/wiki/Software/systemd/InterfaceStabilityPromise > (linked to from LWN just recently), the stable, almost-stable, and > not-stable lists all run together in one long bulleted list making it > appear that all categ

[systemd-devel] Misleading InterfaceStabilityPromise wiki page (due to formatting)

2014-02-12 Thread Elijah Newren
Hi, At http://www.freedesktop.org/wiki/Software/systemd/InterfaceStabilityPromise (linked to from LWN just recently), the stable, almost-stable, and not-stable lists all run together in one long bulleted list making it appear that all categories are part of the stability promise. I suspect a newl

Re: [systemd-devel] [PATCH v3 2/2] syscallfilter: port to libseccomp

2014-02-12 Thread Lennart Poettering
On Wed, 12.02.14 01:29, Ronny Chevalier ([email protected]) wrote: Commited this one! Thanks! (I added another commit on top, to add SystemCallErrorNumber= to optionally return an error from blacklisted syscalls instead of aborting the process) > --- > Ok so I found the problem. I forgot

[systemd-devel] [PATCH v2 1/2] test: add basic seccomp tests

2014-02-12 Thread Ronny Chevalier
--- test/TEST-04-SECCOMP/Makefile | 1 + test/TEST-04-SECCOMP/test-seccomp.sh| 13 + test/TEST-04-SECCOMP/test.sh| 79 + test/TEST-04-SECCOMP/will-fail.service | 8 +++ test/TEST-04-SECCOMP/will-fail2.service | 6 +++

Re: [systemd-devel] [PATCH] rules: name Dell iDRAC virtual usb nic

2014-02-12 Thread Kay Sievers
On Wed, Feb 12, 2014 at 2:12 PM, wrote: > From: Charles Rose > > Dell servers contain a virtual usb nic for systems management. > Name the device 'idrac' to easily identify it. The 75-net-description.rules is doe describe interfaces, not to carry out any policy. Product specific matches do not

Re: [systemd-devel] Undefined reference efi_loader_get_boot_usec

2014-02-12 Thread Cristian Rodríguez
El 11/02/14 09:12, Allmeroth, Robert escribió: I helped myself to #ifdef the body of boot_timestamps() in shared/boot_timestamp.c Oh btw.. since you figured out before I did.. the next time please send patches, it does not matter if they are wrong, ifdef is misplaced or whatever.. just try!

[systemd-devel] [PATCH] rules: name Dell iDRAC virtual usb nic

2014-02-12 Thread Charles_Rose
From: Charles Rose Dell servers contain a virtual usb nic for systems management. Name the device 'idrac' to easily identify it. --- rules/75-net-description.rules | 3 +++ 1 file changed, 3 insertions(+) diff --git a/rules/75-net-description.rules b/rules/75-net-description.rules index 7e62f

Re: [systemd-devel] threads and cgroups

2014-02-12 Thread Lennart Poettering
On Wed, 12.02.14 11:28, Allmeroth, Robert ([email protected]) wrote: > Hi, > > I read a lot about the new cgroup concept of the kernel/systemd. > I understand the logic behind it and why systemd wants to be the MCP of it. > But I miss information how threads are handled. > > Example: >

[systemd-devel] threads and cgroups

2014-02-12 Thread Allmeroth, Robert
Hi, I read a lot about the new cgroup concept of the kernel/systemd. I understand the logic behind it and why systemd wants to be the MCP of it. But I miss information how threads are handled. Example: Due to performance reasons we arrange components with various profiles into one executable. As

[systemd-devel] [PATCH] hostnamed: Fix the way that static and transient host names interact

2014-02-12 Thread Stef Walter
It is almost always incorrect to allow DHCP or other sources of transient host names to override an explicitly configured static host name. This commit changes things so that if a static host name is set, this will override the transient host name (eg: provided via DHCP). Transient host names can