From: sebastien Couret <sebastien.couret@elios-informatique.fr>
To: ecos-devel@sources.redhat.com
Cc: ecos-maintainers@ecos.sourceware.org.
Subject: DHCP server package
Date: Mon, 02 Feb 2004 15:21:00 -0000 [thread overview]
Message-ID: <MELELIOSFzrK0pWHItq000001d6@melelios.dmz.elios-informatique.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
Hi All,
I have ported the uDHCP DHCP server to eCOS.
I think this can be usefull , because for the momemt there is no DHCP server
package available with eCOS.
As told in the FAQ, my contribution got the form of an epk package under GPL.
I would like to have feedback, comments , bug reports and so on , from all
of you that could find it usefull.
On the other hand, Can someone of you explain me how can this package
integrate the eCOS CVS ? and what is the process to follow ?
[-- Attachment #2: DHCPelios.epk --]
[-- Type: application/x-gzip, Size: 24727 bytes --]
next reply other threads:[~2004-02-02 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 15:21 sebastien Couret [this message]
2004-02-02 15:29 ` Andrew Lunn
2004-02-02 17:10 ` Jonathan Larmour
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=MELELIOSFzrK0pWHItq000001d6@melelios.dmz.elios-informatique.fr \
--to=sebastien.couret@elios-informatique.fr \
--cc=ecos-devel@sources.redhat.com \
--cc=ecos-maintainers@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).