All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: David Dillow <dave-i1Mk8JYDVaaSihdK6806/g@public.gmane.org>
Cc: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>"
	<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Netboot test suite: PXE instead of qemu -kernel?
Date: Wed, 24 Jun 2009 08:53:43 +0200	[thread overview]
Message-ID: <4A41CD77.9030201@bfh.ch> (raw)
In-Reply-To: <1245819018.18861.3.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>

David Dillow wrote:
[snip]
>> Additionally we could use -net tap* instead of -net socket, which would 
>> allow brctl setfd of a large value like 20 seconds to simulate the link 
>> delay in the test suite.
> 
> There is merit here, but I think we probably need to have a separate
> test suite to check the ip= option parsing. I haven't thought much how
> it should be done, other than it seems like we could use a pre-mount
> hook to check the configuration without needing to actually mount a real
> root.
> 
> If we have that test suite, then doing PXE boot or emulating BOOTIF=
> seems like a good idea. And I'd rather add a 20+ second delay to one or
> two tests here rather than every network root test we do.

I used an ugly copy of the nfs test suite to test ip= options handling. 
I'll try to make time this evening to clean it up and post it.
--
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

      parent reply	other threads:[~2009-06-24  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 17:11 Netboot test suite: PXE instead of qemu -kernel? Warren Togami
     [not found] ` <4A410CA4.8030506-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-24  4:50   ` David Dillow
     [not found]     ` <1245819018.18861.3.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2009-06-24  6:53       ` 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=4A41CD77.9030201@bfh.ch \
    --to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
    --cc=dave-i1Mk8JYDVaaSihdK6806/g@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.