This patch adds the sdio identifiers known to be supported by
the brcmfmac open-source driver.
Cc: Marcel Holtmann
Signed-off-by: Arend van Spriel
---
hwdb/sdio.ids | 10 ++
1 file changed, 10 insertions(+)
diff --git a/hwdb/sdio.ids b/hwdb/sdio.ids
index 8a4c713..d617297 100644
--- a/
2015-02-25 13:02 GMT+03:00 Arend van Spriel :
> This patch adds the sdio identifiers known to be supported by
> the brcmfmac open-source driver.
What about BCM43228 ?
--
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
jabber: v...@selfip.ru
___
systemd-d
Am 28.01.2015 um 02:48 schrieb Lennart Poettering:
On Tue, 20.01.15 13:48, Reindl Harald (h.rei...@thelounge.net) wrote:
after upgrade to Fedora 21 with new systemd namespaces like below no longer
works which breaks *all my systemd-units*
why?
ReadOnlyDirectories=/var/lib
ReadWriteDirectori
On 02/25/15 12:29, Vasiliy Tolstov wrote:
2015-02-25 13:02 GMT+03:00 Arend van Spriel:
This patch adds the sdio identifiers known to be supported by
the brcmfmac open-source driver.
What about BCM43228 ?
That's a PCIe device.
Regards,
Arend
___
I disagree on your opinion, waiting for additional and more competent
comments...
D.
Il 25/feb/2015 05:56 "Zbigniew Jędrzejewski-Szmek" ha
scritto:
> On Fri, Feb 20, 2015 at 11:01:18AM +0100, Daniele Medri wrote:
> > ---
> > src/core/org.freedesktop.systemd1.policy.in.in | 6 +++---
> > src/log
On Wed, 25.02.15 02:22, Vasiliy Tolstov (v.tols...@selfip.ru) wrote:
Heya,
> Hello =). I'm try to think about creating containers with
> systemd-nspawn and machinectl from dbus. Does it possibe?
We provide a small daemon "systemd-importd" that can import tar, raw
or dkr containers and place them
On Wed, 25.02.15 00:05, Cyrill Gorcunov (gorcu...@gmail.com) wrote:
> Hi all! I would really appreciate if someone enlighten me if there is some
> simple
> solution for the problem we met in OpenVZ: modern containers are mostly
> systemd
> based so that once it is started up the systemd daemon m
On Wed, Feb 25, 2015 at 2:16 AM, Kai Krakow wrote:
> Hello!
>
> Is it possible to somehow create a service which enables port forwardings on
> my router using upnp? Currently, I guess it is not possible (except maybe
> using ExecPost or ExecPre and the upnpc program). But when my client IP
> chang
On Wed, 25.02.15 08:16, Kai Krakow (hurikha...@gmail.com) wrote:
> Hello!
>
> Is it possible to somehow create a service which enables port forwardings on
> my router using upnp? Currently, I guess it is not possible (except maybe
> using ExecPost or ExecPre and the upnpc program). But when my
Because the order of coldplugging is not defined, we can reference a
not-yet-coldplugged unit and read its state while it has not yet been
set to a meaningful value.
This way, already active units may get started again.
We fix this by deferring such actions until all units have been at least
some
Suggested by Zbyszek on IRC.
---
This does not conditionalize on HAVE_PAM. Don't know whether that's right.
Makefile.am | 37
man/systemd-user-sessions.service.xml | 2 +-
src/login/Makefile| 1 -
src/login/user-sessions.c
On Tue, 24.02.15 11:00, Peter Paule (systemd-de...@fedux.org) wrote:
> Hi,
>
> while playing around with "systemd-nspawn" a lot in the last few days two
> things
> I'm really missing are links between containers like dkr supports
> https://docs.docker.com/userguide/dockerlinks/ and getting an ip
On Wed, Feb 25, 2015 at 06:48:20PM +0100, Lennart Poettering wrote:
...
>
> There have been proposals on LKML to add cgroup namespacings, but no
> idea where that went.
As far as I know they are still being discussed. Thanks a huge for reply,
Lennart!
Need to figure out if we can use this nspawn
The USENIX/LISA conference to be held in Washington, DC, USA in
November is seeking a paid presenter for a half-day tutorial about
systemd. I received an invitation to present a tutorial which I
will be happy to forward to anyone who would like to respond.I
have no information about the con
On Tue, 24.02.15 09:39, Peter Paule (systemd-de...@fedux.org) wrote:
> Hi, any suggestions to cleanly shutdown containers?
>
> If using defaults in a service file for stopping a container started with
> nspawn it will be killed by SIGTERM/SIGKILL. This makes "systemd-nspawn" to
> exit with
> "1"
Mike Gilbert schrieb:
> On Wed, Feb 25, 2015 at 2:16 AM, Kai Krakow wrote:
>> Hello!
>>
>> Is it possible to somehow create a service which enables port forwardings
>> on my router using upnp? Currently, I guess it is not possible (except
>> maybe using ExecPost or ExecPre and the upnpc program)
Lennart Poettering schrieb:
> On Wed, 25.02.15 08:16, Kai Krakow (hurikha...@gmail.com) wrote:
>
>> Hello!
>>
>> Is it possible to somehow create a service which enables port forwardings
>> on my router using upnp? Currently, I guess it is not possible (except
>> maybe using ExecPost or ExecPre
On Tue, 24.02.15 19:53, Jan Engelhardt (jeng...@inai.de) wrote:
> On Tuesday 2015-02-24 19:47, Lennart Poettering wrote:
>
> >On Tue, 24.02.15 17:49, Jan Engelhardt (jeng...@inai.de) wrote:
> >
> >> The setup program would not set the font on tty16 upwards.
> >> There is a maximum of 63 VCs possi
On Mon, 23.02.15 15:12, Peter Paule (systemd-de...@fedux.org) wrote:
> Hi,
>
> I run "nginx" in a container which itself is under systemd-control. All
> error messages are put to stderr and the incomming requests are logged in
> access.log. To reduce the filesize I want to rotate the access.log.
On Wed, 25.02.15 21:14, Kai Krakow (hurikha...@gmail.com) wrote:
> > That said I think it wouldn't be too far off I figure to add logic for
> > this to networkd. I mean, it speaks a variety of client side protocols
> > already, and this could just be one more. The major difference though
> > is th
On Wed, 25.02.15 20:35, Lennart Poettering (lenn...@poettering.net) wrote:
> I'd be willing to take a patch that adds --kill-signal= that allows
> changing the kill signal from SIGRTMIN+3 to anything else. With that
> you could use --kill-signal=SIGTERM to get the behaviour you want...
I implemen
Lennart Poettering schrieb:
> On Wed, 25.02.15 21:14, Kai Krakow (hurikha...@gmail.com) wrote:
>
>> > That said I think it wouldn't be too far off I figure to add logic for
>> > this to networkd. I mean, it speaks a variety of client side protocols
>> > already, and this could just be one more.
Hi,
if one is trying to debug (eary-)boot issues, debug-shell.service is a
handy tool.
Unfortunately there is the very unpleasant side effect, that systemd
spews all log messages to tty9, once you switched to that tty, making
it almost impossible to work on this shell.
If it reaches a timeout for
On Thu, 26.02.15 00:36, Michael Biebl (mbi...@gmail.com) wrote:
> Hi,
>
> if one is trying to debug (eary-)boot issues, debug-shell.service is a
> handy tool.
>
> Unfortunately there is the very unpleasant side effect, that systemd
> spews all log messages to tty9, once you switched to that tty,
This is useful, for example, to create system accounts on an initramfs
using the host's configuration.
---
src/sysusers/sysusers.c | 97 +
1 file changed, 66 insertions(+), 31 deletions(-)
diff --git a/src/sysusers/sysusers.c b/src/sysusers/sysusers
Hi there.
These patches allow using firstboot and sysusers together to construct an
initramfs with a fully functional emergency.service and rescue.service.
Moreover, they allow to build a "clean" passwd for the initramfs and don't
resort to copying it from the host system (as it has been done in
This is needed to interoperate firstboot and sysusers. The former one is started
first, and it writes only /etc/shadow when it is told to set the root password.
It's better to relax checks here than to duplicate functionality in firstboot.
---
src/sysusers/sysusers.c | 23 +--
---
src/firstboot/firstboot.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/firstboot/firstboot.c b/src/firstboot/firstboot.c
index a765d6d..a37ca17 100644
--- a/src/firstboot/firstboot.c
+++ b/src/firstboot/firstboot.c
@@ -525,9 +525,9 @@ static int process_root_pa
On 2015-02-26 at 02:46 +0300, Ivan Shapovalov wrote:
> Hi there.
>
> These patches allow using firstboot and sysusers together to construct an
> initramfs with a fully functional emergency.service and rescue.service.
>
> Moreover, they allow to build a "clean" passwd for the initramfs and don't
>
2015-02-26 0:44 GMT+01:00 Lennart Poettering :
> What precisely is supposedly written there? I have never seen anythign
> like that on FEdora...
>
> Maybe you should reconfigure your kernel to not spew its output always
> on the console?
Well, if you want to debug boot issues, you typically remove
2015-02-26 0:55 GMT+01:00 Michael Biebl :
> To reproduce the problem, add e.g. a non-existing device to /etc/fstab
>
> The "Waiting for device to show up ..." messages are printed all over tty9.
And just in case you have plymouth enabled, make sure to remove
"splash" from the kernel command line.
On Thu, Feb 26, 2015 at 01:04:55AM +0100, Michael Biebl wrote:
> 2015-02-26 0:55 GMT+01:00 Michael Biebl :
> > To reproduce the problem, add e.g. a non-existing device to /etc/fstab
> >
> > The "Waiting for device to show up ..." messages are printed all over tty9.
We made rescue.service conflict w
Hello all,
I hope this is the right place for this inquiry. I was noticing
extremely slow reboot times on three of my hosts running
corosync/pacemaker for shared storage. I enabled the systemd debug logs,
and found that pacemaker was attempting to communicate with it's peers
to notify of the
Hello.
I'm looking to store some process tick values from /proc//stat
into the journal and retrieve them later to look at cpu load. This
information is most useful if I can also retrieve how long the system
has been up since last boot.
From
http://www.freedesktop.org/software/systemd/man/systemd
On 25 February 2015 at 20:50, Chris Morgan wrote:
> From
> http://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html#__MONOTONIC_TIMESTAMP=
> it looks like __MONOTONIC_TIMESTAMP might be just what I'm looking for
> but the information at the start of that section has me wonderin
Ping?
--
Lucas De Marchi
On Wed, Feb 18, 2015 at 2:22 PM, wrote:
> From: Lucas De Marchi
>
> By notifying the clients when this property is changed it's possible to
> allow "system health monitor" tools to get transitions like
> running<->degraded. This is an alternative to send changes on th
В Wed, 25 Feb 2015 18:42:47 -0500
Benjamin Rose пишет:
> Hello all,
>
> I hope this is the right place for this inquiry. I was noticing
> extremely slow reboot times on three of my hosts running
> corosync/pacemaker for shared storage. I enabled the systemd debug logs,
> and found that pacema
Hi,
it seems that the lz4 headers are broken when getting coredumps
generated. They cannot even be extracted by the lz4 tool itself, let
alone using them via the coredump controller util.
My system, which is Archlinux, is using lz4 127 and systemd 219.
My current workaround was to disable compre
On Thu, Feb 26, 2015 at 04:41:48AM +, Laszlo Papp wrote:
> Hi,
>
> it seems that the lz4 headers are broken when getting coredumps
> generated. They cannot even be extracted by the lz4 tool itself, let
> alone using them via the coredump controller util.
>
> My system, which is Archlinux, is
39 matches
Mail list logo
