Standalone repository for libnetworking stack
Vijay Kumar Banerjee
vijay at rtems.org
Wed Mar 10 05:00:41 UTC 2021
On Tue, Mar 9, 2021 at 9:56 PM Chris Johns <chrisj at rtems.org> wrote:
> On 10/3/21 3:51 pm, Gedare Bloom wrote:
> > On Tue, Mar 9, 2021 at 6:58 PM Joel Sherrill <joel at rtems.org> wrote:
> >> On Tue, Mar 9, 2021, 3:28 PM Vijay Kumar Banerjee <vijay at rtems.org> wrote:
> >>> On Fri, Mar 5, 2021 at 10:03 AM Vijay Kumar Banerjee <vijay at rtems.org> wrote:
> >>> In this proposed set of patches, I have removed telnetd from RTEMS and
> >>> have placed it in the net-legacy repo, it seems like libbsd uses
> >>> telnetd as well. Do we want to keep it in RTEMS and remove it from the
> >>> legacy net repo? There are checks in for RTEMS_NETWORKING in telnetd,
> >>> to add rtems_bsdnet.h, how do we want to deal with that? In the legacy
> >>> repo, we can just remove these checks and let them build.
> >> Move it and remove rtems networking conditional. Freezes it with legacy stack.
> >> Just my opinion
> > Is there a different telnetd in libbsd?
> Yes ...
This seems to include rtems/telnetd.h
Does the libbsd telnetd depend on the cpukit/telnetd?
> > The longer term pseudo-goal of being able to (potentially) build
> > multiple networking stacks and pick which one to link against may also
> > be a consideration at this stage.
> Are there issues? If there are issues do we know what they are?
More information about the devel