[openbeosnetteam] Re: Where next?
- From: "David Reid" <dreid@xxxxxxxxxxxx>
- To: <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Mon, 18 Feb 2002 10:54:41 -0000
/me is a bit confused.
$ ls -l /
total 2
l--------- 1 dreid users 0 Feb 18 10:48 BeOS R5 Pro -> /boot
l--------- 1 dreid users 0 Feb 18 10:48 bin -> /boot/beos/bin
drwxr-xr-x 1 dreid users 2048 Sep 4 1999 boot
drwxr-x--- 1 dreid users 0 Feb 18 10:48 dev
l--------- 1 dreid users 0 Feb 18 10:48 etc -> /boot/beos/etc
drwxrwxrwx 1 dreid users 0 Feb 18 10:48 pipe
l--------- 1 dreid users 0 Feb 18 10:48 system ->
/boot/beos/system
l--------- 1 dreid users 0 Feb 18 10:48 tmp -> /boot/var/tmp
l--------- 1 dreid users 0 Feb 18 10:48 var -> /boot/var
I already have a /dev directory and so /dev/socket would seem to be OK? Also
it makes the /dev/net directory available for ethernet drivers. Of course we
could have
/dev/net/socket
/dev/net/tulip/0
However, I'm not aware of any way that an app can tell what sort of device a
driver refers to! Whatever...
david
----- Original Message -----
From: <j-schwerer@xxxxxxx>
To: <openbeosnetteam@xxxxxxxxxxxxx>
Sent: Monday, February 18, 2002 7:43 AM
Subject: [openbeosnetteam] Re: Where next?
> Hi,
>
> >Now, Axel said he thought we should use a /dev/socket to create sockets.
>
> Is it BeOS-ish enough? Will we need some additional filesystem entries at
some
> point or not? Rather than having to force the /dev directory into a Linux
mess
> maybe we should consider something less straight, e.g. some kind of
> /dev/net/sockets or /dev/net/driver/sockets.
> The /dev/net and /dev/net/<drivername> directories are already there for
us to
> use so let's not create a top /dev directory maybe? :)
>
> What do you think?
>
> Jean
>
>
> ____________________________________________________________________
> Get free e-mail and a permanent address at http://www.amexmail.com/?A=1
>
>
Other related posts:
