On Sun, Nov 08, 2015 at 10:39:43PM +0100, Richard Weinberger wrote:
> On Sun, Nov 8, 2015 at 10:35 PM, Greg KH wrote:
> > On Sun, Nov 08, 2015 at 10:06:31PM +0100, Richard Weinberger wrote:
> >> Hi all,
> >>
> >> after reading on the removal of kdbus from Rawhide[1] I've searched
> >> the mailingl
On Sun, Nov 08, 2015 at 10:06:31PM +0100, Richard Weinberger wrote:
> Hi all,
>
> after reading on the removal of kdbus from Rawhide[1] I've searched
> the mailinglist archives for more details but didn't find anything.
> So, what are your plans?
>
> [1] https://lists.fedoraproject.org/pipermail/
On Sun, Nov 8, 2015 at 10:35 PM, Greg KH wrote:
> On Sun, Nov 08, 2015 at 10:06:31PM +0100, Richard Weinberger wrote:
>> Hi all,
>>
>> after reading on the removal of kdbus from Rawhide[1] I've searched
>> the mailinglist archives for more details but didn't find anything.
>> So, what are your pla
Hi all,
after reading on the removal of kdbus from Rawhide[1] I've searched
the mailinglist archives for more details but didn't find anything.
So, what are your plans?
[1] https://lists.fedoraproject.org/pipermail/kernel/2015-October/006011.html
--
Thanks,
//richard
___
Grr, my first reply should have gone to the mailing list...
2015-11-08 21:03 GMT+01:00 Lennart Poettering :
> On Sun, 08.11.15 19:40, Michael Biebl (mbi...@gmail.com) wrote:
>
>> 2015-11-08 19:10 GMT+01:00 Lennart Poettering :
>> > Heya!
>> >
>> > At systemd.conf we discussed whether we can remove
On Fri, 06.11.15 18:38, Francis Moreau (francis.m...@gmail.com) wrote:
> Hi,
>
> I'm trying to change the MemoryLimit property of one the service unit
> running on my system by using 'busctl set-property ...' but getting
> the following error :
>
>Property 'MemoryLimit' is not writable.
>
>
On Sun, 08.11.15 13:17, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
>
> 1- SELinux is disabled as the host distro is difficult to setup with
> it, so it is OK
> 2- Running modprobe bridge nf_nat br_netfilter failed with message: ,
> error: exit status 1"
> These modules are indeed loaded on
Heya!
At systemd.conf we discussed whether we can remove the unit dependency
types RequiresOverridable= and RequisiteOverridable=. I am pretty sure
they are pretty much unused in the wild, and hard to grok at all, and
hence, in order to clean things up a bit, we should really get rid of
it.
Unles
On Sat, 07.11.15 13:33, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> Hi,
>
> do you use .snapshot unit type? If you do, please speak up.
>
> I'd like to remove support for the .snapshot unit type.
> It seems not be used, snapshots are basically transient targets,
> and targets can be
Am 08.11.2015 um 15:41 schrieb arnaud gaboury:
On Sun, Nov 8, 2015 at 2:57 PM Richard Weinberger
mailto:richard.weinber...@gmail.com>> wrote:
On Sun, Nov 8, 2015 at 1:17 PM, arnaud gaboury
mailto:arnaud.gabo...@gmail.com>> wrote:
> I am trying to understand how kernel modules are
On Sun, Nov 8, 2015 at 2:57 PM Richard Weinberger <
richard.weinber...@gmail.com> wrote:
> On Sun, Nov 8, 2015 at 1:17 PM, arnaud gaboury
> wrote:
> > I am trying to understand how kernel modules are "passed" to nspawn
> container.
>
> A container must not load any module as the kernel is a share
On Sun, Nov 8, 2015 at 1:17 PM, arnaud gaboury wrote:
> I am trying to understand how kernel modules are "passed" to nspawn container.
A container must not load any module as the kernel is a shared resource.
--
Thanks,
//richard
___
systemd-devel mail
I am trying to understand how kernel modules are "passed" to nspawn container.
My setup: Archlinux host, Fedora 23 container (function = server).
Example of what I would like to solve:
On container:
--
$ systemctl statu
13 matches
Mail list logo
