mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Dennis Schridde <devurandom-hi6Y0CQ0nG0@public.gmane.org>
To: Will Woods <wwoods-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] [40network] Fix ifup.sh to always execute initqueue/online hook after bringing up an interface
Date: Fri, 17 May 2013 18:13:57 +0200	[thread overview]
Message-ID: <1992756.u6R4HOtcTb@ernie> (raw)
In-Reply-To: <1367349915.2614.5.camel-s6BhOCdKmxS3M6m420IelR/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

Hello!

Am Dienstag, 30. April 2013, 15:25:15 schrieb Will Woods:
> On Thu, 2013-04-11 at 18:13 +0200, Dennis Schridde wrote:
> > Am Donnerstag, 11. April 2013, 17:44:08 schrieb Harald Hoyer:
> > > IIRC, that is done, as soon as the dhcp client gets an IP
> 
> Technically it doesn't happen *immediately* - it adds a job to the
> initqueue, and that job will run the initqueue/online hook.
> 
> > These patches are already a few months old, so dracut's behaviour may very
> > well have changed in the meantime. Where does what you describe happen?
> 
> See 40network/dhclient-script.sh - when $reason is BOUND (i.e. initial
> binding to a new address, as per dhclient-script(8)), it adds a job
> named "setup_net_$netif.sh" to the initqueue.

Thanks for that information!

I removed the patch and discovered some bugs and misconceptions about the 
inner workings of dracut in my own code. It works now without the patch.

Best regards,
Dennis

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-05-17 16:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 15:41 [PATCH] [40network] Fix ifup.sh to always execute initqueue/online hook after bringing up an interface Dennis Schridde
     [not found] ` <1365694894-7926-1-git-send-email-devurandom-hi6Y0CQ0nG0@public.gmane.org>
2013-04-11 15:44   ` Harald Hoyer
     [not found]     ` <5166DA48.20803-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-04-11 16:13       ` Dennis Schridde
2013-04-30 19:25         ` Will Woods
     [not found]           ` <1367349915.2614.5.camel-s6BhOCdKmxS3M6m420IelR/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2013-05-17 16:13             ` Dennis Schridde [this message]
2013-04-11 15:45   ` Dennis Schridde

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=1992756.u6R4HOtcTb@ernie \
    --to=devurandom-hi6y0cq0ng0@public.gmane.org \
    --cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wwoods-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