public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001177] Redboot DHCP client race condition, XID, and retry problems.
Date: Sat, 26 Mar 2011 04:21:00 -0000	[thread overview]
Message-ID: <20110326042054.A83A92F78001@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001177-13@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001177

--- Comment #8 from Grant Edwards <grant.b.edwards@gmail.com> 2011-03-26 04:20:52 GMT ---
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #2)
> > 
> > > - It would be nice (although admittedly arguably an enhancement)
> > >   for all of bootp/dhcp support to be removable by config
> > >   option. There are many instances where redboot is only ever
> > >   given a static IP, so this code is just taking up space.
> > 
> > I've create a new CYGPKG_REDBOOT_NETWORKING_BOOTP which now contains
> > CYGSEM_REDBOOT_NETWORKING_DHCP and CYGSEM_REDBOOT_NETWORKING_VERBOSE_BOOTP.
> > 
> > I'm wondering about the latter names.  Are names supposed to
> > reflect package heirachy like more like this?
> > 
> >       CYGPKG_REDBOOT_NETWORKING
> >        CYGPKG_REDBOOT_NETWORKING_BOOTP
> >         CYGPKG_REDBOOT_NETWORKING_BOOTP_DHCP
> >         CYGPKG_REDBOOT_NETWORKING_BOOTP_VERBOSE
> 
> While I think that would be the ideal, changing option names (in
> general invalidates people's existing configurations, so shouldn't
> be done lightly.

Agreed.  It had slipped my mind that two of the names were for options
that already existed -- and enhancing the consistency of the names a
bit doesn't justify breaking somebody's previously working
configuration.

> I'd suggest just leaving it. The more important thing is that the
> actual hierarchy of options is correct. But if you want to change
> it, I'm ok with that too.

The two existing names are going to stay the same.

>[...]
> > I don't have a strong opinion one way or the other, but if I were to
> > pick, I'd move CYGSEM_REDBOOT_DEFAULT_NO_BOOTP into
> > CYGPKG_REDBOOT_NETWORKING_BOOTP and make it independent of whether
> > CYGDAT_REDBOOT_DEFAULT_IP_ADDR is set or not.  Who are we to say that
> > no default IP address and bootp built but disabled by default isn't
> > useful to somebody?
> 
> Yes, there seems no reason to prohibit that, so if you didn't mind,
> I think it would be good if you could do that.

Done.

-- 
Grant

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-03-26  4:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 14:50 [Bug 1001177] New: " bugzilla-daemon
2011-03-24 14:35 ` [Bug 1001177] " bugzilla-daemon
2011-03-24 17:37 ` bugzilla-daemon
2011-03-24 17:37 ` bugzilla-daemon
2011-03-24 17:37 ` bugzilla-daemon
2011-03-24 18:12 ` bugzilla-daemon
2011-03-24 19:33 ` bugzilla-daemon
2011-03-24 19:36 ` bugzilla-daemon
2011-03-25 16:20 ` bugzilla-daemon
2011-03-26  2:17 ` bugzilla-daemon
2011-03-26  4:21 ` bugzilla-daemon [this message]
2011-03-26 18:01 ` bugzilla-daemon
2011-06-08 16:13 ` bugzilla-daemon
2012-03-02 21:10 ` bugzilla-daemon
2012-03-03  3:44 ` bugzilla-daemon
2012-03-03  3:44 ` bugzilla-daemon
2012-03-06 16:47 ` bugzilla-daemon
2011-03-21 14:50 [Bug 1001177] New: " bugzilla-daemon
2011-03-24 14:36 ` [Bug 1001177] " bugzilla-daemon
2011-03-24 17:37 ` bugzilla-daemon
2011-03-24 17:37 ` bugzilla-daemon
2011-03-24 17:37 ` bugzilla-daemon

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=20110326042054.A83A92F78001@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-bugs@ecos.sourceware.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).