|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
UNIX/MS-DOs scipt
Post 302223226 by Ikon on Friday 8th of August 2008 04:12:19 PM
08-08-2008
Short answer: They are 2 different operating systems that use different Syntax and Commands
Long Answer:
Back in the days before Microsoft Windows dominated the PC market, operating system were controlled by commands. Prior to MS-Windows, PC users were required to learn these commands in order to perform routine tasks. During the 1980s, Microsoft DOS dominated the PC market while the early UNIX command systems were used on larger multi-processing servers.
The main difference between UNIX and DOS is that DOS was originally designed for single-user systems, while UNIX was designed for systems with many users.
Because UNIX and MS-DOS were developed at the same time they share some common syntax, and the UNIX admin will be happy to find many common commands and concepts. The list below shows some of the commonality between UNIX and MS-DOS commands:
*
Changing directories: both DOS and UNIX utilize the cd commands for this purpose, but UNIX has the "cd " command that allows you to flip-flop between your last two directories.
Display file contents: UNIX has the "cat" command" and DOS uses the "type" command.
Setting file permissions: DOS uses the "attrib" command while UNIX uses the "chmod" command to change file permissions.
Copying files: DOS uses the "copy" command, while UNIX uses the "cp" command.
Comparing two files: UNIX uses the "diff" command and DOS has the "fc" command.
Printing files: UNIX uses the "lp" command while DOS uses the "print" command.
Moving files: DOS uses the "rename" command and UNIX uses the "mv" command.
Make a directory: UNIX uses the "mkdir" command while DOS has the "md" command.
Display directory contents: UNIX uses the "ls" command and DOS has the "dir" command.
Delete files: DOS uses the "del" command while UNIX has the "rm" command.
Display the OS version: DOS uses the "ver" command while UNIX has the "uname -a" command.
EDIT: There was some VERY outdated information in my post so I had to edit it...
Long Answer:
Back in the days before Microsoft Windows dominated the PC market, operating system were controlled by commands. Prior to MS-Windows, PC users were required to learn these commands in order to perform routine tasks. During the 1980s, Microsoft DOS dominated the PC market while the early UNIX command systems were used on larger multi-processing servers.
The main difference between UNIX and DOS is that DOS was originally designed for single-user systems, while UNIX was designed for systems with many users.
Because UNIX and MS-DOS were developed at the same time they share some common syntax, and the UNIX admin will be happy to find many common commands and concepts. The list below shows some of the commonality between UNIX and MS-DOS commands:
*
Changing directories: both DOS and UNIX utilize the cd commands for this purpose, but UNIX has the "cd " command that allows you to flip-flop between your last two directories.
Display file contents: UNIX has the "cat" command" and DOS uses the "type" command.
Setting file permissions: DOS uses the "attrib" command while UNIX uses the "chmod" command to change file permissions.
Copying files: DOS uses the "copy" command, while UNIX uses the "cp" command.
Comparing two files: UNIX uses the "diff" command and DOS has the "fc" command.
Printing files: UNIX uses the "lp" command while DOS uses the "print" command.
Moving files: DOS uses the "rename" command and UNIX uses the "mv" command.
Make a directory: UNIX uses the "mkdir" command while DOS has the "md" command.
Display directory contents: UNIX uses the "ls" command and DOS has the "dir" command.
Delete files: DOS uses the "del" command while UNIX has the "rm" command.
Display the OS version: DOS uses the "ver" command while UNIX has the "uname -a" command.
EDIT: There was some VERY outdated information in my post so I had to edit it...
Last edited by Ikon; 08-08-2008 at 05:17 PM..
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
As the title sugests I need to compress files from DOS to Unix.
The files should be in .Z format, as created using 'compress' in an Unix environment.
Ligs (2 Replies)
Discussion started by: ligs
2 Replies
2. UNIX for Dummies Questions & Answers
I know nothing of unix and didn't know where to start. I've heard of a DOS to Unix translator, and since I know DOS pretty well, I thought that this program would be perfect. Any help you could give me would be appreciated.
Bryan (1 Reply)
Discussion started by: bferguson
1 Replies
3. Shell Programming and Scripting
Hi !
I need to convert a DOS batch file to Unix Shell script. Can anybody help me by providing equivalent Unix shell script code to this DOS batch code?.
for /F "tokens=2,3,4 delims=/- " %%i in ("%date%") do set DateStamp=%%k%%i%%j
Any help would be great.
Thanks,
John. (1 Reply)
Discussion started by: john413
1 Replies
4. UNIX for Dummies Questions & Answers
would like to have ls, wc -l, etc all availble in this silly dos shell I'm stuck in thanks! (1 Reply)
Discussion started by: robersh
1 Replies
5. Windows & DOS: Issues & Discussions
Is there a tool available to convert UNIX (BASH Shell) scripts to DOS scripts?
I understand that DOS scripting is far inferior to unix scripting, and therfore this conversion may not be possible.
Alternativley, perhaps I could convert my Unix scripts to C... then compile it for a windows... (2 Replies)
Discussion started by: Crozz
2 Replies
6. Cybersecurity
hi eveybody,
i use sco unix as server and dos as client . how i can connect from unix server to dos client ( how to telnet to dos and run commands?)?
thanks. (1 Reply)
Discussion started by: shrb78
1 Replies
7. SCO
hi eveybody,
i use sco unix as server and dos as client . how i can connect from unix server to dos client ( how to telnet to dos and run commands?)?
thanks. (1 Reply)
Discussion started by: shrb78
1 Replies
8. Windows & DOS: Issues & Discussions
hi eveybody,
i use sco unix as server and dos as client . how i can connect from unix server to dos client ( how to telnet to dos and run commands?)?
thanks. (8 Replies)
Discussion started by: shrb78
8 Replies
9. Shell Programming and Scripting
Hi,
Is there any method to connect unix box(Excecuting unix commands through Batch Files) through DOS prompt. (1 Reply)
Discussion started by: shekhar_ssm
1 Replies
10. UNIX for Dummies Questions & Answers
I am in the process of converting a batch script into a shell script for CentOS but am a complete Unix newb.
I have the follow Windows batch code:
for /f %%a in (C:\STEAMINVITE\extractor\workfile3.tmp) do C:\Python27\Python.exe C:\STEAMINVITE\extractor\sidconv.py %%a >... (2 Replies)
Discussion started by: spinner0205
2 Replies
LEARN ABOUT OSX
cr
cr(1) General Commands Manual cr(1) NAME
cr - converts text files between nix EOL and dos EOL SYNOPSIS
cr - | + <input file> <output file> DESCRIPTION
Text files, such as tle files, that come from a dos source usualy have the ^M symbol at the end of every line. Cr converts files between the dos newline format and the normal *nix newline format by stripping the ^M to convert dos to *nix, using the '-' option, or adding ^M to a *nix file to create the proper dos file when the '+' option is used. Although this extra character is not often a problem, programs like seesat5, which are data driven will encounter parsing problems when the extra character is present. It is these problems that cr is intended to repair. Options - | + One or the other of these options is required. The '-' option is used to remove ^M from all newlines found in the dos file. The '+' option is used to add ^M to every newline found in a *nix file. input file Fully delineated path to the input file. As this program is used in the dos environment as well, standard input is not used. output file Fully delineated path to the output file. As this program is used in the dos environment as well, standart output is not used. SEE ALSO
seesat5(1), seesat5(7), SEESAT5.INI(5), tle(5) BUGS
Cr is not an inteligent program. It methodicaly replaces/removes the offending character when it finds it in the correct context. Newline sequences found in contexts other than 'newline' will be replaced/removed just like those found in the proper context. Passing a binary file through cr is not advised, for this reason. Send all inqueries to Dale Scheetz <dwarf@polaris.net>. Debian Linux 2 April 96 cr(1)