answersLogoWhite

0


Best Answer

Both the 'more' and the 'cat' commands will list the contents of one or more files. In that case, the main difference between the two commands is that 'more' is a 'pager' program, meaning that it stops at the end of every page and waits for the user. The 'cat' command will list everything in the file without stopping.

One other thing that 'cat' does that 'more' does not is to concatenate (add/merge) files together. 'more' is not designed to do that.

Lastly, some versions of 'more' can traverse a file forwards and backwards and have simple searching capabilities, which 'cat' does not.

User Avatar

Wiki User

14y ago
This answer is:
User Avatar
More answers
User Avatar

Wiki User

11y ago

The 'touch' command either creates an empty file or can change the timestamps on an existing file. The 'cat' command lists the contents of one or more files.

This answer is:
User Avatar

Add your answer:

Earn +20 pts
Q: What is the difference between the cat and more commands in Unix?
Write your answer...
Submit
Still have questions?
magnify glass
imp
Related questions

Why does Linux and unix share more commands than windows xp and unix?

Because Linux evolved from UNIX, but Windows evolved from DOS.


Is the architecture of Linux based on DOS?

No. Linux is a free, open-source version of UNIX. Many of DOS's commands were based on UNIX commands, but the underlying operating system is much more powerful than DOS.


Why most of the time you use Linux to execute Unix commands?

Because Linux is actually more popular in most fields these days than certified Unix.


Why are Unix commands simple rather than complex tasks?

UNIX commands are designed to be simple in the first place; they basically do one task per command. To make a more powerful sequence, just put (or pipe) several commands together in a sequence. The ability to use many of the commands in different scenarios just by the command sequence is very powerful; the individual commands do not have to be that powerful or complex, but the result of using several of them in a row makes for a very powerful system.


WHY DO YOU THINK LINUX AND UNIX SHARE MORE COMMANDS THAN WINDOWS XP AND UNIX?

Because Linux was modeled after Unix, and designed to be a suitable free replacement. Windows is targeted at a slightly different market, and was primarily designed to be operated using a GUI, not the command line.


Why do you think Unix and Linux share more commands than Windows XP and Unix?

Because Linux was modeled after Unix, and designed to be a suitable free replacement. Windows is targeted at a slightly different market, and was primarily designed to be operated using a GUI, not the command line.


What are the commands used in Linux but not in Unix?

There is no answer to this question. Under UNIX and Linux, commands are either shell native or external programs found on the path (which usually includes /bin /sbin /usr/bin and ~/bin) Most UNIX and distros allow the admin to choose a shell program of choice and modify the contents of other directories and many admins allow individual users to change their personal shell and add additional executable files adding more commands. That being the case, theoretically any command can be valid under almost any UNIX or Linux. YMMV.


Command for Using in sun Blade 2000 Server?

Sun Microsystem's Solaris operating system is Unix. Solairs comes with virtually every command that is found in other modern Unix systems. Each commercial version of Unix (whether AIX, Unicos, Solaris, HP UX or another) usually has one or more vendor specific commands included that do not appear in versions of Unix from other vendors or in open source implementations. It is doubtful that Sun Solaris has 500 commands that do not appear in some form in other versions of Unix, though as I haven't used Sun Solaris in several years, I suppose this is possible, though unlikely. Typically, the vendor specific commands in various historic versions of Unix have numbered fewer than dozen or two and often have been no more than a handful. IBM's AIX is perhaps the exception to this with probably the most prolific proliferation of vendor specific commands of any commercial version of Unix. Nevertheless, it is unlikely that even AIX has 500 vendor specific commands and likely fewer than 100 or so. [JMH]


What command is used in a Unix environment to know more information about other commands?

Usually, one would use the man command. For instanceman ls


Difference between president and chancellor of germany?

The Chancellor of Germany wields more power than the President.


Why unix is the best operating system than other operating system?

There is no way to answer this question in sufficient detail. "Unix" is a term for a variety of operating systems, many of which have only a few features in common. And with a variety of operating systems on the market, there may or may not be differences between them and "Unix" in selected areas.


What is the difference between the dir and ls commands?

From the user's point of view, there is very little difference between dir on windows or dos and ls on Unix. Anyone who has looked at the will see that ls has a lot more command line switches than dir - most of the alphabet, in fact. (This lead a couple of juvenile colleagues to see what rude words they could make with them and still get usable output!)At a deeper level there are some differences:dir is built in to the operating system and ls is an external program, so that dir should always work, but ls will only work if it is installed and in the path. (Which, of course, it will be unless something has gone wrong!)Whilst file types or extensions (such as *.doc, *.txt) are used in Unix to assist humans to differentiate files, Unix has no built in concept of these whereas dos/Windows expects them. So the dos command:dir *.* will show all files in a directory, but in Unixls *.* will only show files with a dot in the name, ls * is more likely to give the result expected.Also, Unix style "[" and "]" can be used to define a group, so that: ls prog.[oc] will match prog.c and prog.o (but not prog.oc)From the above, it can be seen that both recognise wildcards (* and ?). However, Unix treats them differently. In dos, the wildcard is presented unchanged to the command (DIR in this case) and the command has to understand and interpret it. In Unix, the operating system processes the wild card and presents the results to the command. From the user's perspective, there is normally no difference but it can have subtle effects and is worth being aware of.