On Thu, Feb 21, 2013 at 06:46:35PM +, Steven Hiscocks wrote:
> On 21/02/13 01:49, Zbigniew Jędrzejewski-Szmek wrote:
> >On Tue, Feb 19, 2013 at 09:02:56PM +, Steven Hiscocks wrote:
> >>I've pushed a few more commits.
> >I've pushed a few commits to
> >https://github.com/keszybz/systemd/comm
2013/2/20 Simon McVittie :
> On 19/02/13 23:55, Peeters Simon wrote:
>> or just use a systemd generater to generate systemd .service files from the
>> dbus service files.
>> (i have something like this laying around slightly unfinished if you
>> want code, let me know)
>
> That would be an interest
On 19/02/13 16:06, Simon McVittie wrote:
> On 18/02/13 20:13, Simon McVittie wrote:
Is there any plan for how GUI processes started via session D-Bus
activation should pick up the right value for $DISPLAY?
>>
>> I've started prototyping what would be needed for `systemd --user` to
>> trac
Hi,
systemd-nspawn already allows you start a container with an
all networking but lo disabled (--private-network).
This experimental patch developed during Hackfest in Brno
allows one to add up to 16 veth pairs to a containers with
one end outside of the container and the other inside of the
cont
On Friday 22 February 2013 11:34:20 Colin Guthrie wrote:
> This kind of setup might be desirable in very basic custom
> configurations where the full network "initscripts" are not needed.
many thanks
___
systemd-devel mailing list
[email protected]
'Twas brillig, and Reindl Harald at 22/02/13 10:55 did gyre and gimble:
>
>
> Am 22.02.2013 11:21, schrieb lux-integ:
>> On Friday 22 February 2013 10:00:39 Lennart Poettering wrote:
>>> DHCP does not apply to the loopback device as the loopback is
>>> unconditionally configured to 127.0.0.1, and
Am 22.02.2013 11:21, schrieb lux-integ:
> On Friday 22 February 2013 10:00:39 Lennart Poettering wrote:
>> DHCP does not apply to the loopback device as the loopback is
>> unconditionally configured to 127.0.0.1, and dynamic configuration is
>> not necessary
> Thanks for you information concernin
On Friday 22 February 2013 10:00:39 Lennart Poettering wrote:
> DHCP does not apply to the loopback device as the loopback is
> unconditionally configured to 127.0.0.1, and dynamic configuration is
> not necessary
Thanks for you information concerning the loopback interface.
But my question ANDed
On Fri, 22.02.13 08:58, lux-integ ([email protected]) wrote:
> Greetings,
>
> I am attempting to learn to implement systemd. I have been searching
> the internet for example unit files for the loopback interface (lo)
> and dhclient.
The loopback device is set up very very early at boot in
Hello everybody.
Hi Lennart.
Since I was watching and looking at the diagrams which is building by my
application... it shows
the depending of any objects to each other.
I catch myself for one though...
systemd's units build some bounds, like a humans.
I mean each of us can be 'WantsBy' somebod
Greetings,
I am attempting to learn to implement systemd. I have been searching the
internet for example unit files for the loopback interface (lo) and dhclient.
I would be grateful for advce on the location of any or how to go about
synthesising the said.
thanks in advance
sincerely
lu
11 matches
Mail list logo
