Hi,
1. I love shellworld and cannot conceive of needing to change to an
either or
circumstance. both is the only thing I will consider, if I will consider
that at all given the Linux box issues.
having elinks working with java scripting in place alone is worth the price
I pay for shellworld.
Even my personal site is hosted here, and the years of flexible tools to
hand is profoundly valuable professionally to me, especially with no in
town support.
2. the dos ssh telnet package is called
ssh2d386.
created by the university of Waterloo in Ontario it makes use of the
watpcp <spelling> library. includes SFTP as well.
I use it with my high speed provider, have for rather a few years now.
3. the problem with the Linux box is that it is not configured for dsl at
all, no ip address or anything *that I can tell* as It has no screen
reader that is usable, it
must be checked in person, by someone knowledgeable in debian.
Although I have been on the debian discussion list for years, I have not
found anyone in Toronto with either the skill, or the ability to understand
the goal is just to correct this issue, not remove the command line
configuration in place.
Rumors of a local Linux users group are, as Mark twain would say, grossly
exaggerated.
The person who put debian squeeze on this computer's hard drive mailing me
the drive did not include dsl configuring. There is a dial up modem in the
machine, but again no speech I can use.
I had a p3 computer built to house the drive, and while debian did
recognize some of the hardware, I know too little and have too little in
person talent to learn anything more.
In fact my Engineer friend and I may convert that box to my main dos one
leaving this older unit for whatever Linux effort I make. The debian unit
has been
sitting here without a purpose for a long time, and I am working my main
computer very hard indeed.
if the ssh dos package interest
you, I can send you a copy. Kare
On Tue, 23 Dec 2014, Tim Chase wrote:
On December 23, 2014, Karen Lewellen wrote:
However since I can ssh TELNET into shellworld using Dos and access
all the command line tools here with that speech, I cannot imagine
why the ssh TELNET process will not work the other way into
whatever this box becomes.
I would expect that, if that's the way you're comfortable, that you
could fairly readily set up a similar configuration of SSHing into
your local Linux/BSD box instead of into shellworld. It sounds like
this is what you're already trying to do but having some sort of
difficulty. However, I'm not sure what the issue is. The two things
that come to mind are
1) if you really are telnetting from DOS (it's been a long time since
I've used pure DOS as the core operating system), I remember being
able to telnet but not SSH. They're different protocols, so unless
there's a SSH program for DOS (there could well be, I'm just ignorant
in that department), you really do want to telnet. If this is the
case, you'd want to ensure that the telnet daemon is running and
listening for connections on your Linux box. It's not secure, but if
you're only running over your local network, it shouldn't expose you
greatly.
2) if you do have a SSH client in DOS and still can't connect, it
sounds like your Linux box may not be running "sshd" (the SSH daemon).
Or, maybe you *are* able to connect to your Linux box and I'm just
mis-understanding again.
Nothing personal, but I have zero reason to buy a box for a
platform that has yet to prove worth investing in otherwise.
Perhaps in time, but first things first, being able to do something
with the Linux box presently holding up the speakers for my DOS one.
Ah, if you already have one then, no worries or need to buy any
additional machine. I must have misinterpreted something you wrote
which lead me to believe that you didn't have any machine locally to
monkey with.
-tim
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list