From: Gary Thomas <gary@mlbassoc.com>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: Andrew Lunn <andrew.lunn@ascom.ch>,
John Dallaway <jld@ecoscentric.com>,
eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: SNMP for FreeBSD
Date: Wed, 19 Mar 2003 14:23:00 -0000 [thread overview]
Message-ID: <1048083782.9579.4929.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <3E786EAA.5050200@eCosCentric.com>
On Wed, 2003-03-19 at 06:20, Jonathan Larmour wrote:
> Andrew Lunn wrote:
> >
> >>c) A rationale for including the patch in the 2.0 final release.
> >
> >
> > Currently the branch only supports SNMP with the OpenBSD stack. This
> > is no longer the default stack for 2.0b1. FreeBSD should become the
> > stack everyone uses, but if people want SNMP they are forced to use
> > the old stack. This patch touches the two snmp packages only. It does
> > have the risk of breaking the OpenBSD support for snmp :-(
>
> This is a highly desirable patch as it gets rid of a long-standing issue,
> and Andrew has tested it, and Ascom have used the stack far more than any
> other user anyway! I would very much like to have it, although I can see
> why it wouldn't be considered "critical". So I'll leave it to John to make
> a final decision.
I tested it on PowerPC (for big-endian coverage) and it worked well
for me too. I think it should be applied.
--
------------------------------------------------------------
Gary Thomas |
MLB Associates | Consulting for the
+1 (970) 229-1963 | Embedded world
http://www.mlbassoc.com/ |
email: <gary@mlbassoc.com> |
gpg: http://www.chez-thomas.org/gary/gpg_key.asc
------------------------------------------------------------
next prev parent reply other threads:[~2003-03-19 14:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 8:47 Patches for the eCos 2.0 branch John Dallaway
2003-03-18 13:48 ` Gary Thomas
2003-03-18 16:04 ` Proposal for processing patches " John Dallaway
2003-03-18 17:25 ` Jonathan Larmour
2003-03-18 18:21 ` Nick Garnett
2003-03-18 18:56 ` Andrew Lunn
2003-04-12 5:00 ` Jonathan Larmour
2003-04-14 7:28 ` Andrew Lunn
2003-03-18 19:01 ` Andrew Lunn
2003-03-18 22:58 ` Jonathan Larmour
2003-03-18 19:16 ` SNMP for FreeBSD Andrew Lunn
2003-03-19 13:22 ` Jonathan Larmour
2003-03-19 14:23 ` Gary Thomas [this message]
2003-03-19 18:07 ` Nick Garnett
2003-03-25 17:01 ` Andrew Lunn
2003-03-19 14:22 ` 2.0 branch: mn10300 debug info patch Bart Veer
2003-03-19 14:40 ` John Dallaway
2003-03-19 18:07 ` Nick Garnett
2003-03-18 18:09 ` Patches for the eCos 2.0 branch Nick Garnett
2003-03-18 18:25 ` Gary Thomas
2003-03-18 19:05 ` Nick Garnett
2003-03-18 19:13 ` Gary Thomas
2003-03-19 10:18 ` New CPM/DPRAM allocator John Dallaway
2003-03-19 13:02 ` Nick Garnett
2003-03-19 14:38 ` Gary Thomas
2003-03-19 15:44 ` John Dallaway
2003-03-19 17:06 ` Gary Thomas
2003-03-19 18:22 ` Nick Garnett
2003-03-19 18:26 ` Gary Thomas
2003-03-19 18:52 ` Nick Garnett
[not found] ` <1048100525.7462.5617.camel@hermes.chez-thomas.org>
2003-03-19 19:21 ` Nick Garnett
2003-03-20 13:02 ` Nick Garnett
2003-03-20 13:14 ` Gary Thomas
2003-03-20 18:11 ` Nick Garnett
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=1048083782.9579.4929.camel@hermes.chez-thomas.org \
--to=gary@mlbassoc.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@sources.redhat.com \
--cc=jifl@eCosCentric.com \
--cc=jld@ecoscentric.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.
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).