n***@gmail.com
2012-03-22 19:28:58 UTC
I'm writing this while I'm thinking it through, so I'll have a record.
Duke mentioned the problem of email for LNO.
I don't like LNO much, compared to LEO, which I use all the time.
But LNO can run on a netbook using a framebuffer, without the
full X-window system.
So let's think this problem through.
And correct my mistaken assumptions and conclusions:-
N-O was originaly designed for RS232-modem,
and the full <IP/TCP stack> was in N-O [of course].
So for <send string1 to IP/port>,
all stages/levels, from the app's passing the string,
down to the serial port driving the modem,
was handled by N-O [of course].
Under LEO, the underlying linux does the internet handling.
Without anlysing the source code, I want to know how the
N-O part of LEO interfaces with linux.
Does the fact that "everything in *nix is a file" make this
easy?
Since linux, which previously drove a modem via a RS232,
can easily be 'reconfigured' to drive a radio-modem via a
USB; and passing the same byte-stream in both cases, I'm
guessing that just the appropriate file-driver are needed.
So the byte-stream is just fed to any character-type
file-device, and the appropriate driver handles it.
So the input-feeder need not be concerned what is
receiving the input.
If that is the case, and although the netbook has no actual
RS232, if I create a /dev/tty0 [pseudo]file and [symbolicly]
link it to the /dev/<existingUSB> , which is connected to
the remote IP:port via linux, could I communicate with the
remote IP:port via LNO? Would LNO treat the /devtty0/
as if it was a PC's "COM" port?
I guess not, since during boot, linux would see that there
is NO RS232-port and .....?
If not, I suspect that facilities exist to easily connect into
the IP:stack at various levels, and connecting at the highest
level would be most convenient, via an Oberon <-> C
interface ?
Thanks for any ideas,
== Chris Glur.
Duke mentioned the problem of email for LNO.
I don't like LNO much, compared to LEO, which I use all the time.
But LNO can run on a netbook using a framebuffer, without the
full X-window system.
So let's think this problem through.
And correct my mistaken assumptions and conclusions:-
N-O was originaly designed for RS232-modem,
and the full <IP/TCP stack> was in N-O [of course].
So for <send string1 to IP/port>,
all stages/levels, from the app's passing the string,
down to the serial port driving the modem,
was handled by N-O [of course].
Under LEO, the underlying linux does the internet handling.
Without anlysing the source code, I want to know how the
N-O part of LEO interfaces with linux.
Does the fact that "everything in *nix is a file" make this
easy?
Since linux, which previously drove a modem via a RS232,
can easily be 'reconfigured' to drive a radio-modem via a
USB; and passing the same byte-stream in both cases, I'm
guessing that just the appropriate file-driver are needed.
So the byte-stream is just fed to any character-type
file-device, and the appropriate driver handles it.
So the input-feeder need not be concerned what is
receiving the input.
If that is the case, and although the netbook has no actual
RS232, if I create a /dev/tty0 [pseudo]file and [symbolicly]
link it to the /dev/<existingUSB> , which is connected to
the remote IP:port via linux, could I communicate with the
remote IP:port via LNO? Would LNO treat the /devtty0/
as if it was a PC's "COM" port?
I guess not, since during boot, linux would see that there
is NO RS232-port and .....?
If not, I suspect that facilities exist to easily connect into
the IP:stack at various levels, and connecting at the highest
level would be most convenient, via an Oberon <-> C
interface ?
Thanks for any ideas,
== Chris Glur.