[openbeosnetteam] Re: Me as well...
- From: <dreid@xxxxxxxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Wed, 16 Jan 2002 18:35:39 -0000 (GMT/BST)
Oh for a better windows mail client...
I don't think we should be aiming to create BONE or network_server. I think
we should feel free and unburdened by the past (or convention) to go forth
and create something new that works and performs. That is after all the
beos way is it not?
I realise a list of binaries isn't an item high on the list of priorities,
but often it's important to flesh out a project fully before trying to draw
the boundries and the requirements, wouldn't you agree? As long as people
feel free to contribute at the moment and say whatever they feel hopefully
we won't have too many "damn, we missed this" type events :)
I'd like to think that having posix compatibility would be high on
everyones list of priorities, as really the best understood networking code
is that using the BSD interfaces, and if we are to have a hope of getting a
truly useful network stack we need to be able to test and know the results
we expect. Also this makes moving code over much easier.
We'd all like more native apps, but the fact is that if we allow people to
reuse unix-type sockets/network code then the developer can concentrate far
more on getting the interface and the usability right - which has to be
good news. We've been blessed with a very good set of highly usable apps
for beos, let's see if we can't help that trend continue and grow :)
Man, do I go on at times :)
david
>
> David Reid wrote:
> ...
>
>
>>
>> BONE had tcpdump. I think if we're aiming for a list of utilities we
>> should have, then I'd start with
>>
>> - netstat
>> - ifconfig
>> - tcpdump
>> - ping(6)
>> - telnet(6)
>> - ssh (yes client as default)
>> - nslookup (deprecated now in BIND)
>> - dig
>> - whois
>> - host
>> - hostname
>> - tracert
>> - route
>> - arp
>> - finger
>
>
> Some of the utilities will be plain ports (if we
> have posix- and bsd-? compatibility); for example
>ssh, dig, ping and etc. Others such as netstat and
> ifconfig could be harder to port as they depend
> on the ioctl interface.
>
> So it looks like Posix compatibility should pretty
> high on the wish-list (or it is just me ;-)
>
> ...
>
>>
>> Perhaps we should also say we'll do ppp so we'd need
>> -ppp
>> -pppctl
>>
>
>
> I believe The idea of plug-ins for the network
>stack was mentioned on this list before. PPP
> implementation would an excellent testground for this.
>
> ...
>
>
>> Anyone else intimidated by this list? Of course for most of these we
>> get the network layer correct they can just be built with slight mods
>> to allow for beos's differences in other areas :)
>
>
> While the list of possible applications to port is
> an important thing to have (to test if a
> particular application compiles for instance), I
> think that we should concentrate more on the
> features and implementation details of the network
>stack. I don't think that at this point we have a
> clear idea whether we are implementing BONE- or
> NetServer-like stack.
>
> Cheers,
>
> Dmitri
Other related posts:
