man system is well-developed and most apps have a man file.
No DOS equivalent.
Use ~/.bashrc to set permanently in *nix.
Setting the path allows you to run commands without thinking about where their executable file is.
Much more complexity is possible in both flavors of OS, here.
hostname is DNS-related, whereas the Windows net name command shows netbios info.
Lsdev and procinfo do not work on Linux VPSs sometimes due to the way disks are provisioned.
Pushd and popd are available for newer Windows versions.
The "bare" directory list commands are inherently different in display characteristics.
Notice you are stringing together args in Linux after the dash, but that you have to put in additional slashes and args in DOS.
Du or diskusage is common, but the switches will be different so do a "man du" to find out more in your *nix. Treesize is an excellent GUI version of du for Windows.
Use tree with more to get page-by-page output, and space-bar through the pages. I.e.: $ tree | more
Neither assign nor subst are really much like ln.
Deltree is Win 95.
Of course you can just cp a file in Linux, as well.
DOS has hidden switch; use mv to .somename to make a file hidden in *nix.
In *nix, editors are a religion because the are used so heavily for systems administration tasks. Pico was the editor that came with the Pine mailer, and nano is a standalone pico variant. Many swear by simple vi or complex emacs, though.
Note, tar just concatenates files together for easy manipulation, and is often used before compression.
You cannot configure the network from the command line in Windows, like you can with ifconfig in *nix. Use Control Panel.
NetBIOS is a Windows and DOS affair.
There is a whoami command for Windows available in the Resource Kit. Or, you can use set to list the environment variables, of which the username is one.
Older OS X Leopard was "lookupd -flushcache".
79 件の記事を表示しています。