linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Gundersen <teg@jklm.no>
To: linux-hotplug@vger.kernel.org
Subject: Re: create /etc/udev/rules.d/70-persistent-net.rules
Date: Thu, 26 Mar 2015 21:15:49 +0000	[thread overview]
Message-ID: <CAG-2HqX1VM-iaT3wg5Ap=eEvHmhRpCLgaV0CYNc+stke22MKig@mail.gmail.com> (raw)
In-Reply-To: <77e5d094647c5243d3b238ef82ee9328.squirrel@postweb.cs.tu-dortmund.de>

Hi Christopher,

On Thu, Mar 26, 2015 at 11:04 AM, Christoph Pleger
<Christoph.Pleger@cs.tu-dortmund.de> wrote:
> I hope that this is a right place fur udev questions.

Sure, though most udev discussions happen on the systemd mailinglist these days.

> My problem is that I need to create a file
> /etc/udev/rules.d/70-persistent-net.rules on a PXE-Booted computer with an
> NFS-Rootfilesystem. Unfortunately, that file ist not created automatically
> at boot time, also "echo add > /sys/class/net/*/uevent" did not work,
> though it did an another, disk-booted computer where I had deleted the
> file before.
>
> So, how can I create /etc/udev/rules.d/70-persistent-net.rules on a
> netbooted computer, if possible without using tools like ifconfig, sed and
> awk?

This mechanism is no longer supported/shipped upstream. Instead we
suggest using the scheme outlined here:
<http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/>,
which is the default.

HTH,

Tom

      reply	other threads:[~2015-03-26 21:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 10:04 create /etc/udev/rules.d/70-persistent-net.rules Christoph Pleger
2015-03-26 21:15 ` Tom Gundersen [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='CAG-2HqX1VM-iaT3wg5Ap=eEvHmhRpCLgaV0CYNc+stke22MKig@mail.gmail.com' \
    --to=teg@jklm.no \
    --cc=linux-hotplug@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).