From: "Kevin Hilman" <khilman@baylibre.com>
To: kernelci@groups.io
Cc: matthew.hart@linaro.org
Subject: debian rootfs for ramdisk and NFS
Date: Mon, 04 Jun 2018 13:33:58 -0700 [thread overview]
Message-ID: <7hy3fumguh.fsf@baylibre.com> (raw)
Hi Ana,
In testing the debian rootfs images for NFS, Matt Hart and I both
noticed that the full.rootfs.tar.xz images don't work for NFS because
the systemd network init causes a (re)init of networking while actively
using an NFSroot. This causes things to grind to a halt.
So the first question is whether anyone knows if systemd can be made
pursuaded to not try to reconfigure networking.
Ideally, we'd like a single rootfs image to be either a ramdisk, where
it might need to (re)configure networking and an NFSroot where it
definitely should not reconfigure networking.
It would be a shame to have to have different images for ramdisk vs. NFS
just for network init.
Ideas?
Kevin
next reply other threads:[~2018-06-04 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 20:33 Kevin Hilman [this message]
2018-06-06 8:11 ` [kernelci] debian rootfs for ramdisk and NFS Tomeu Vizoso
2018-06-06 8:14 ` matthew.hart
2018-06-06 19:18 ` Ana Guerrero Lopez
2018-06-06 21:00 ` Kevin Hilman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7hy3fumguh.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=kernelci@groups.io \
--cc=matthew.hart@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox