for example on the console i type
1/ login root , + passwwd and i m logged
2/ than i type login user + passwd and i m logged
3/ when i type login user2 + passwd and there is no more keyboard , i
think no more shell
i don t undeerstand because on the doc i read that after
a login threre is automatically a nex shell ???
How embedded?
I’m just wondering if your running out of memory.
I do realize that you really haven’t done anything substancial.
c > and telnetd work fine
c > but when i log more than twice i m disconnected
c > it is the same if i make a login on the console:
c > for example on the console i type
c > 1/ login root , + passwwd and i m logged
c > 2/ than i type login user + passwd and i m logged
c > 3/ when i type login user2 + passwd and there is no more keyboard , i
c > think no more shell
Are you loggin in 3 times on the same console or on 3 different consoles?
c > i don t undeerstand because on the doc i read that after
c > a login threre is automatically a nex shell ???
How embedded?
I’m just wondering if your running out of memory.
I do realize that you really haven’t done anything substancial.
c > and telnetd work fine
c > but when i log more than twice i m disconnected
c > it is the same if i make a login on the console:
c > for example on the console i type
c > 1/ login root , + passwwd and i m logged
c > 2/ than i type login user + passwd and i m logged
c > 3/ when i type login user2 + passwd and there is no more
keyboard , i
c > think no more shell
Are you loggin in 3 times on the same console or on 3 different consoles?
c > i don t undeerstand because on the doc i read that after
c > a login threre is automatically a nex shell ???
You might also consider starting the QNET stack on your embedded system if
you are using QNX as your development system. Then you don’t have to log
in, everything will be accessible, file system, process space, etc, etc.
from accross the network from anyother QNX box running QNET.
If you dev environment isn’t QNX, then this won’t work…
for example on the console i type
1/ login root , + passwwd and i m logged
2/ than i type login user + passwd and i m logged
3/ when i type login user2 + passwd and there is no more keyboard ,
i
think no more shell
i don t undeerstand because on the doc i read that after
a login threre is automatically a nex shell ???
Exactly what would one have to put in a boot image to get just qnet running
over ethernet (without tcp-ip, or login) ??
Would the image be MUCH smaller if you don’t need the overhead of tcp/ip
(libraries, protocol stack, etc…)?? Or would it require lots of overhead of
it’s own?
You might also consider starting the QNET stack on your embedded system if
you are using QNX as your development system. Then you don’t have to log
in, everything will be accessible, file system, process space, etc, etc.
from accross the network from anyother QNX box running QNET.
If you dev environment isn’t QNX, then this won’t work…
for example on the console i type
1/ login root , + passwwd and i m logged
2/ than i type login user + passwd and i m logged
3/ when i type login user2 + passwd and there is no more keyboard
,
i
think no more shell
i don t undeerstand because on the doc i read that after
a login threre is automatically a nex shell ???
Exactly what would one have to put in a boot image to get just qnet
running
over ethernet (without tcp-ip, or login) ??
Would the image be MUCH smaller if you don’t need the overhead of tcp/ip
(libraries, protocol stack, etc…)?? Or would it require lots of overhead
of
it’s own?
npm-qnet.so
It’s a bit bigger than the tiny tcp/ip stack but half the size of the full
tcpip stack. Also no need for telnetd, inetd, or anyting like it.
But if you are going to use tcp/ip anyway, then it doesn’t matter…just a
suggestion.
You might also consider starting the QNET stack on your embedded system
if
you are using QNX as your development system. Then you don’t have to
log
in, everything will be accessible, file system, process space, etc, etc.
from accross the network from anyother QNX box running QNET.
If you dev environment isn’t QNX, then this won’t work…
for example on the console i type
1/ login root , + passwwd and i m logged
2/ than i type login user + passwd and i m logged
3/ when i type login user2 + passwd and there is no more
keyboard
,
i
think no more shell
i don t undeerstand because on the doc i read that after
a login threre is automatically a nex shell ???
You might also consider starting the QNET stack on your embedded system if
you are using QNX as your development system. Then you don’t have to log
in, everything will be accessible, file system, process space, etc, etc.
from accross the network from anyother QNX box running QNET.
If you dev environment isn’t QNX, then this won’t work…
for example on the console i type
1/ login root , + passwwd and i m logged
2/ than i type login user + passwd and i m logged
3/ when i type login user2 + passwd and there is no more keyboard
,
i
think no more shell
i don t undeerstand because on the doc i read that after
a login threre is automatically a nex shell ???