0 00 host0
--
Yours Sincerely
Han
At 2016-03-03 02:33:22, "Kai Krakow" wrote:
>Am Wed, 2 Mar 2016 16:53:01 +0800 (CST)
>schrieb kennedy :
>
>> Hi
>>
>>
>> On my first run systemd-nspawn everything that's OK.
>> When I s
Hi
On my first run systemd-nspawn everything that's OK.
When I shutdown the nspawn container, and re-run systemd-nspawn again, this
error comes.
In container, it's only have 169.254.x.x network, didn't have network bridge's
network.
On my host, I run systemctl status systemd-networkd it show m
uch addresses in networkd. AFAIK it's called APIPA.
Regards,
Kai
kennedy schrieb am Mo., 29. Feb. 2016 um 07:43 Uhr:
Thanks! it works!
but I had a little question.
In my container, I run `route -n` it show me 3 result ,they are:
Kernel IP routing table
Destination Gateway Ge
stemd-nspawn, the "169.254.0.0"
it's disappeared.
--
Yours Sincerely
Han
At 2016-02-29 00:26:54, "Kai Krakow" wrote:
>Am Sun, 28 Feb 2016 23:41:22 +0800 (CST)
>schrieb kennedy :
>
>> how to ping container to container each other in systemd-nspawn ?
how to ping container to container each other in systemd-nspawn ?
I've tried --network-veth option but it doesn't work enough.___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
t;On Thu, Oct 29, 2015 at 3:26 AM, kennedy wrote:
>> the boot sequence is it right ?
>> kernel --> initramfs --> switch_root --> systemd --> init & mount /etc/fstab
>> --> user login
>
>http://www.freedesktop.org/software/systemd/man/bootup.html
>
the boot sequence is it right ?
kernel --> initramfs --> switch_root --> systemd --> init & mount /etc/fstab
--> user login___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
where is the systemd-modules-load.service to load the .ko file path ?
http://www.freedesktop.org/software/systemd/man/modules-load.d.html
this example doesn't tell us where is the virtio-net.ko file.___
systemd-devel mailing list
[email protected]
runlevel*.target for compatibility with sysV, just a symbol link to systemd's
target ?
means that users can use runlevel*.target instead of default.target to setting
boot sequence ?
quote: http://www.freedesktop.org/software/systemd/man/systemd.special.html___
, and then start some service
(console-setup.service,udevd.service, etc.) parallel ?
在 2015-10-26 16:42:03，"Mantas Mikulėnas" 写道：
On Mon, Oct 26, 2015 at 10:13 AM, kennedy wrote:
what's the relationship between the target file and the real executable file ?
"local-
what's the relationship between the target file and the real executable file ?
"local-fs-pre.target" ,"local-fs.target" will start which service (will execute
which binary file) ?
best regards!___
systemd-devel mailing list
[email protected]
thanks.
when will systemd run "generators"? In the beginning of the boot ?
I can't see "sysv-generator" in /src/core/main.c
在 2015-10-22 15:35:58，"Mantas Mikulėnas" 写道：
On Thu, Oct 22, 2015 at 9:37 AM, kennedy wrote:
what is systemd booting sequ
what is systemd booting sequence?
how is Systemd support both sysV's runlevel script and systemd's target file at
the same time?
I define the sysV runlevel script, and add it into /etc/rc5.d/
and I define another systemd target file, and use systemctl enable it.
both of them could work fine.
reference http://0pointer.de/blog/projects/systemd-for-admins-3.html
In this blog
"
Note that a dependency of type After= only encodes the suggested ordering, but
does not actually cause syslog to be started when abrtd is -- and this is
exactly what we want, since abrtd actually works fine e
14 matches
Mail list logo
