From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Reminder: /tmp/net.$netif.* files
Date: Thu, 18 Jun 2009 09:40:06 +0200 [thread overview]
Message-ID: <4A39EF56.9030408@bfh.ch> (raw)
In-Reply-To: <4A392E76.5020909-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Warren Togami wrote:
> If you write a file to /tmp/net.$netif.* please be sure it only exists
> if that interface ends up as part of the netboot. The net.* files are
> to be considered post-switch_root by initscripts or NetworkManager. We
> don't want those tools to be confused by net.* files from aborted
> interfaces that were not part of the netboot.
Question: What net.* files would you consider to be necessary for
initscripts and NetworkManager? I'd assume that would have to be
dhclient-options and -lease file, an override file containing ip=
contents and the written ifcfg-files. Anything else?
> A tricky part might be ensuring net.* files for constituent interfaces
> part of layered interfaces like bridges or bonds, in addition to net.*
> files for the bridge or bond.
>
> Warren Togami
> wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
> --
> To unsubscribe from this list: send the line "unsubscribe initramfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-06-18 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 17:57 Reminder: /tmp/net.$netif.* files Warren Togami
[not found] ` <4A392E76.5020909-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-18 7:40 ` Seewer Philippe [this message]
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=4A39EF56.9030408@bfh.ch \
--to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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