Correction, I meant change the registry key HKEY_CURRENT_USER\Software\Microsoft\Command Processor\\CompletionChar to 9. That'll teach me to post things without testing them...
I Think You Mean cmd under NT; it doesn't have command.com.
More importantly, tab completion can be enabled, although you do have to go registry diving. Simply change the HKEY_CURRENT_USER\Software\Microsoft\Windows\Comma ndProcessor\\CompletionChar to 9. I have no idea why this is not an option in the cmd preferences or somewhere more easily accessible, but it is there. It isn't as good as bash's because it won't search the path or anything like that (it does check the current directory though).
You need some PuTTY- it makes Windows usable. It's a free SSH client for Windows, that also (if I remember correctly) supports port-forwarding etc. It is released under the MIT licence (kinda similar to the BSD licence) which is 'Open Source certified'.
That is a very nice program, thank you for telling me about it. It makes windows much more bearable. Though there could be patent issues for it in the US (an issue for colleges who want their students to use it), it looks like they will clear up soon (in September 2000). I'll definitely suggest it when I get back on campus in September (though it could be more well documented...).
Also, I didn't see anything about port-forwarding when I wandered through the webpage or in the program itself. But that could probably be added fairly painlessly, if it isn't in there now.
Just as an aside; how recently is it that SSH has become a standard part of Linux distributions.
I has been a standard part of at least the non-free parts of linux for around 2 or 3 years AFAIK. Now that OpenSSH is out, it is essentially standard on all systems where it isn't specificly unwanted.
Given that SSH implementations are now available on most any platform you care to mention, telnet should rightly be regarded as a legacy protocol. Anonymous ftp obviously has its place, but the 'nonymous' version could easily be supplanted by SCP style functionality
Except that on Windows, ssh is not a stock part of the OS (there are/no/ free versions that I'm aware of, and even the pay versions don't seem to support tunnelling[1], etc), and there is no secure way to access email, ftp, etc. IMHO this is one of the worst aspects of Windows (low emphasis on security), but it means that there is no way to force security without more work than most people are interested in.
[1] Ssh tunnelling is cool because it can make most protocols much more secure. You connect to a computer via ssh, with the correct options to forward a port to or from it, and any traffic to a local port that you pick is sent over the secure connection, then sent to the remote host. When the remote host and the ssh host are the same, this is pretty secure (no chance for sniffing), and when they aren't the same, the sniffing risk goes down significantly if the server network is separate from the student nets, since that one is much less likely to be sniffed.
Slashdot Mirror
-nh
> The author's post is NOT flamebait.
:) )h
Sure it is. It makes a highly debatable point in an inflamatory tone without providing any depth, thus becoming the epitome of flamebait.
-n( Not that I disagree with it
Sorry about that.
-nh
More importantly, tab completion can be enabled, although you do have to go registry diving. Simply change the HKEY_CURRENT_USER\Software\Microsoft\Windows\Comma ndProcessor\\CompletionChar to 9. I have no idea why this is not an option in the cmd preferences or somewhere more easily accessible, but it is there. It isn't as good as bash's because it won't search the path or anything like that (it does check the current directory though).
-nh
That is a very nice program, thank you for telling me about it. It makes windows much more bearable. Though there could be patent issues for it in the US (an issue for colleges who want their students to use it), it looks like they will clear up soon (in September 2000). I'll definitely suggest it when I get back on campus in September (though it could be more well documented...).
Also, I didn't see anything about port-forwarding when I wandered through the webpage or in the program itself. But that could probably be added fairly painlessly, if it isn't in there now.
Just as an aside; how recently is it that SSH has become a standard part of Linux distributions.
I has been a standard part of at least the non-free parts of linux for around 2 or 3 years AFAIK. Now that OpenSSH is out, it is essentially standard on all systems where it isn't specificly unwanted.
-nh
Except that on Windows, ssh is not a stock part of the OS (there are /no/ free versions that I'm aware of, and even the pay versions don't seem to support tunnelling[1], etc), and there is no secure way to access email, ftp, etc. IMHO this is one of the worst aspects of Windows (low emphasis on security), but it means that there is no way to force security without more work than most people are interested in.
[1] Ssh tunnelling is cool because it can make most protocols much more secure. You connect to a computer via ssh, with the correct options to forward a port to or from it, and any traffic to a local port that you pick is sent over the secure connection, then sent to the remote host. When the remote host and the ssh host are the same, this is pretty secure (no chance for sniffing), and when they aren't the same, the sniffing risk goes down significantly if the server network is separate from the student nets, since that one is much less likely to be sniffed.