unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Dušan Xmetov" <merkur32@gmail.com>
Cc: 18483@debbugs.gnu.org
Subject: bug#18483: Fwd: Dmd tries to initialize my network interface before it become available.
Date: Tue, 16 Sep 2014 10:24:46 +0200	[thread overview]
Message-ID: <877g14nfap.fsf@gnu.org> (raw)
In-Reply-To: <CAN=wXfCnYXnJYJpNPT5Rs1Yaqzz2d+uGP2U2rvZX2EzJ7prUgw@mail.gmail.com> ("Dušan Xmetov"'s message of "Mon, 15 Sep 2014 18:24:46 +0200")

Dušan Xmetov <merkur32@gmail.com> skribis:

> Dmd attempts to configure my network interface before the kernel
> module even gets loaded.
>
> Yesterday, there was a commit that tried to fix this problem by
> starting udev before configuring the network, but in my case it
> doesn't help.

Yes (that was 150d8e6, for the record.)

> I'm enclosing in this email my os definition, a dmesg log and a photo
> of the problem (At the top you can see it trying to configure the
> network, while at the bottom you can see e100, my network adapter's
> driver, getting loaded).

I was hoping that, by the time ‘udevadm trigger’ completes, all the
devices would have been detected, but obviously there’s no such
guarantee.

dmd will need something akin to ‘upstart-udev-bridge’
<http://upstart.ubuntu.com/cookbook/#id278> to turn device
discovery/removal events into service start/stop triggers.

Until then you’ll have to restart the networking service manually.  :-/

Thanks for the report,
Ludo’.

  reply	other threads:[~2014-09-16  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAN=wXfDbirM8b+kOZ7Svgo1JMFFXZaFEpj-f3i+Gb6+magx+=A@mail.gmail.com>
2014-09-15 16:24 ` bug#18483: Fwd: Dmd tries to initialize my network interface before it become available Dušan Xmetov
2014-09-16  8:24   ` Ludovic Courtès [this message]
2019-02-13  0:25   ` bug#18483: " Leo Famulari
2019-02-21 20:04     ` Andreas Enge

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877g14nfap.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=18483@debbugs.gnu.org \
    --cc=merkur32@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).