more Command in Linux Made Simple

The more command in Linux is the fastest way to read large files in your terminal without getting buried in output. When you open a 4,000-line configuration file using cat and it display all that data onto your screen in an instant, you know exactly what I’m talking about. This is precisely what more was made for. The first time I used more to view a systemd journal on a live server, I finally understood how many hours I had wasted scrolling through terminal output I could not even read properly.

Whether you are new to Linux and still learning your way around the terminal, or you have become comfortable enough to start working seriously with shell commands, more is one of those commands you will reach for almost every day. Not only is it easy and fast to use, but it is also available almost everywhere, including minimal containers and older RHEL systems where less may not be installed.

Examples

The more command in Linux gives you a reading window for your terminal instead of flooding the screen. Think of more as a terminal viewing area rather than just another way to view your files. Instead of showing you the entire file at once, more displays one screen of content at a time and waits for you to tell it to continue by pressing the Space key.

You can advance through a file one full screen (or page) at a time by pressing Space, move forward one line at a time by pressing Enter, or quit by pressing q.

more is technically a pager utility. A pager reads a file (which can also be the result of piped input) and breaks the content into chunks that fit within your terminal's vertical size. The pager has existed since the early days of Unix in the 1970s. As such, nearly every Linux distribution includes it by default, from a base installation of Ubuntu 24.04 Server to an outdated CentOS 6 system sitting in a forgotten data center.

Since no setup is required to use more, you can simply run it from your terminal and start viewing files immediately. Advanced users who want to override some of more's default behavior should refer to the MORE environment variable.

The full syntax reference is: more [options] [+line_number] [+/pattern] filename. Breaking each part down in plain English:

[options] are flags like -d or -s that change how the output behaves. They are all optional.

[+line_number] tells more to start at a specific line. So more +50 app.log skips straight to line 50 instead of starting at the top.

[+/pattern] jumps to the first occurrence of a search string. Useful when you know what you are looking for and do not want to scroll manually.

filename is the file you want to read. You can pass multiple filenames and more will page through them in order.

Here are the flags you will actually use, plus what they do in practice.

The most basic use. You have a file and you want to read it without the terminal flooding you. Run more and press Space to page through it.

You run ls -la on a directory with hundreds of files and everything scrolls off the screen. Pipe it into more instead.

If you are working on a shared system or scripting a guide for someone else, -d adds a help prompt so users know what to press without having to guess.

You already know the relevant content is around line 200 in an access log. Skip the top and start there directly with the +N syntax.

You want to jump straight to the first occurrence of "ERROR" in a log file without manually scrolling. Use +/ to do that on launch.

Some config files and logs have stretches of empty lines that waste screen space. The -s flag collapses them into one blank line so you can read faster.

Any command that produces a long output can be piped into more. This is where you will use it most in practice, especially for process lists, package queries, and environment dumps.

You can pass multiple filenames to more and it pages through them one after the other. Useful when reviewing several config files in the same session.

On a minimal Docker container or a stripped-down Rocky Linux 9 image, less is often not installed. more is. When a deployment fails and you need to read the build log fast, this is your command.

Package history files get long fast. On Rocky Linux 9 or RHEL, piping the dnf history output through more gives you a manageable read instead of a wall of transactions.

New users sometimes do this when trying to combine commands. Piping more into another more does nothing useful. The second pager just ends up reading the output of the first one, which has already handled pagination.

Running env or printenv on a system with many variables set dumps everything at once. Pipe to more and read through at your own pace.

Every sysadmin eventually reaches for less as their default pager. Fair enough, it is more capable. But more has a real edge in two specific situations: minimal environments where less is not installed, and scripted or automated contexts where you just need something predictable and portable. It ships on everything from a fresh Rocky Linux 9 minimal install to a Debian container image that weighs under 100MB. You will not always have a choice.

The bigger point is this: learning more properly teaches you the pager mindset. Once you internalize that any long output, whether from a file, a command, or a pipe, can be controlled and read at your pace, you stop letting the terminal overwhelm you. That habit carries forward into everything from reading vim buffers to working with Linux logging pipelines on production systems. The official documentation for more is maintained at man7.org if you want the full reference.