• Bash Terminal Download Win 10

Terminal User Guide

In Terminal, you can move and copy files locally or remotely using the mv, cp, and scp command-line tools.

Tip: It’s easier to move and copy files using the Finder. See Organize files in folders.

Move a file or folder locally

• In the Terminal app on your Mac, use the mv command to move files or folders from one location to another on the same computer. The mv command moves the file or folder from its old location and puts it in the new location.

  For example, to move a file from your Downloads folder to a Work folder in your Documents folder:

  % mv ~/Downloads/MyFile.txt ~/Documents/Work/MyFile.txt

  You can also change the name of the file as it’s moved:

  % mv ~/Downloads/MyFile.txt ~/Documents/Work/NewFileName.txt

See the mv command man page.

Copy a file or folder locally

Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un.x-like operating systems. It only takes a minute to sign up. How can I run the same command in mac terminal for multiple files in a folder? The files are named like 245387#1.fq, 245387#2.fq, 245387#3.fq, 245387#4.fq and so on. Open multiple terminal windows mac using bash script. Ask Question Asked 2 years, 7 months ago. Per file, so your #!/usr/bin. Add a comment 2 Answers Active Oldest Votes. If you want to open 10 new Terminal windows from a bash script (or from the command line), use the following command.

• In the Terminal app on your Mac, use the cp command to make a copy of a file.

  For example, to copy a folder named Expenses in your Documents folder to another volume named Data:

  % cp -R ~/Documents/Expenses /Volumes/Data/Expenses

  The -R flag causes cp to copy the folder and its contents. Note that the folder name does not end with a slash, which would change how cp copies the folder.

See the cp command man page.

Copy a file or folder remotely

• In the Terminal app on your Mac, use the scp command to copy a file or folder to or from a remote computer.

  scp uses the same underlying protocols as ssh.

  For example, to copy a compressed file from your home folder to another user’s home folder on a remote server:

  % scp -E ~/ImportantPapers.tgz username@remoteserver.com:/Users/username/Desktop/ImportantPapers.tgz

  You’re prompted for the user’s password.

  The -E flag preserves extended attributes, resource forks, and ACL information.

  The -r flag, which isn’t used in this example, causes scp to copy a folder and its contents.

See the scp command man page.

A Unix shell is a command-line interpreter or shell that provides a command line user interface for Unix-likeoperating systems. The shell is both an interactive command language and a scripting language, and is used by the operating system to control the execution of the system using shell scripts.^[2]

Users typically interact with a Unix shell using a terminal emulator; however, direct operation via serial hardware connections or Secure Shell are common for server systems. All Unix shells provide filename wildcarding, piping, here documents, command substitution, variables and control structures for condition-testing and iteration.

Concept[edit]

The most generic sense of the term shell means any program that users employ to type commands. A shell hides the details of the underlying operating system and manages the technical details of the operating system kernel interface, which is the lowest-level, or 'inner-most' component of most operating systems.

In Unix-like operating systems, users typically have many choices of command-line interpreters for interactive sessions. When a user logs into the system interactively, a shell program is automatically executed for the duration of the session. The type of shell, which may be customized for each user, is typically stored in the user's profile, for example in the local passwd file or in a distributed configuration system such as NIS or LDAP; however, the user may execute any other available shell interactively.

On hosts with a windowing system, like macOS, some users may never use the shell directly. On Unix systems, the shell has historically been the implementation language of system startup scripts, including the program that starts a windowing system, configures networking, and many other essential functions. However, some system vendors have replaced the traditional shell-based startup system (init) with different approaches, such as systemd.

Early shells[edit]

The first Unix shell was the Thompson shell, sh, written by Ken Thompson at Bell Labs and distributed with Versions 1 through 6 of Unix, from 1971 to 1975.^[3] Though rudimentary by modern standards, it introduced many of the basic features common to all later Unix shells, including piping, simple control structures using if and goto, and filename wildcarding. Though not in current use, it is still available as part of some Ancient UNIX Systems.

It was modeled after the Multics shell, developed in 1965 by American software engineer Glenda Schroeder. Schroeder's Multics shell was itself modeled after the RUNCOM program Louis Pouzin showed to the Multics Team. The 'rc' suffix on some Unix configuration files (for example, '.vimrc'), is a remnant of the RUNCOM ancestry of Unix shells.^[1][4]

The PWB shell or Mashey shell, sh, was an upward-compatible version of the Thompson shell, augmented by John Mashey and others and distributed with the Programmer's Workbench UNIX, circa 1975–1977. It focused on making shell programming practical, especially in large shared computing centers. It added shell variables (precursors of environment variables, including the search path mechanism that evolved into $PATH), user-executable shell scripts, and interrupt-handling. Control structures were extended from if/goto to if/then/else/endif, switch/breaksw/endsw, and while/end/break/continue. As shell programming became widespread, these external commands were incorporated into the shell itself for performance.

But the most widely distributed and influential of the early Unix shells were the Bourne shell and the C shell. Both shells have been used as the coding base and model for many derivative and work-alike shells with extended feature sets.^[5]

Bourne shell[edit]

The Bourne shell, sh, was a new Unix shell by Stephen Bourne at Bell Labs.^[6] Distributed as the shell for UNIX Version 7 in 1979, it introduced the rest of the basic features considered common to all the Unix shells, including here documents, command substitution, more generic variables and more extensive builtin control structures. The language, including the use of a reversed keyword to mark the end of a block, was influenced by ALGOL 68.^[7] Traditionally, the Bourne shell program name is sh and its path in the Unix file system hierarchy is /bin/sh. But a number of compatible work-alikes are also available with various improvements and additional features. On many systems, sh may be a symbolic link or hard link to one of these alternatives:

• Almquist shell (ash): written as a BSD-licensed replacement for the Bourne Shell; often used in resource-constrained environments. The sh of FreeBSD, NetBSD (and their derivatives) are based on ash that has been enhanced to be POSIX conformant.
• Bourne-Again shell (bash): written as part of the GNU Project to provide a superset of Bourne Shell functionality. This shell can be found installed and is the default interactive shell for users on most Linux systems.
• Debian Almquist shell (dash): a modern replacement for ash in Debian and Ubuntu
• Korn shell (ksh): written by David Korn based on the Bourne shell sources^[8] while working at Bell Labs
• Public domain Korn shell (pdksh)
• MirBSD Korn shell (mksh): a descendant of the OpenBSD /bin/ksh and pdksh, developed as part of MirOS BSD
• Z shell (zsh): a relatively modern shell that is backward compatible with bash. It's the default shell in macOS since 10.15 Catalina.
• Busybox: a set of Unix utilities for small and embedded systems, which includes 2 shells: ash, a derivative of the Almquist shell; and hush, an independent implementation of a Bourne shell.

The POSIX standard specifies its standard shell as a strict subset of the Korn shell, an enhanced version of the Bourne shell. From a user's perspective the Bourne shell was immediately recognized when active by its characteristic default command line prompt character, the dollar sign ($).

C shell[edit]

The C shell, csh, was modeled on the C programming language, including the control structures and the expression grammar. It was written by Bill Joy as a graduate student at University of California, Berkeley, and was widely distributed with BSD Unix.^[9]

The C shell also introduced many features for interactive work, including the history and editing mechanisms, aliases, directory stacks, tilde notation, cdpath, job control and path hashing. On many systems, csh may be a symbolic link or hard link to TENEX C shell (tcsh), an improved version of Joy's original version. Although the interactive features of csh have been copied to most other shells, the language structure has not been widely copied. The only work-alike is Hamilton C shell, written by Nicole Hamilton, first distributed on OS/2 in 1988 and on Windows since 1992.^[10]

Configuration files[edit]

Shells read configuration files in various circumstances. These files usually contain commands for the shell and are executed when loaded; they are usually used to set important variables used to find executables, like $PATH, and others that control the behavior and appearance of the shell. The table in this section shows the configuration files for popular shells.^[11]

Explanation:

• blank means a file is not read by a shell at all.
• 'yes' means a file is always read by a shell upon startup.
• 'login' means a file is read if the shell is a login shell.
• 'n/login' means a file is read if the shell is not a login shell.
• 'int.' means a file is read if the shell is interactive.

1. ^only if ~/.tcshrc not found
2. ^Newer versions of the Bourne Shell only
3. ^Available on systems that support the 'User Portability Utilities option'; value of the variable must be an absolute path, and it is ignored 'if the user's real and effective user IDs or real and effective group IDs are different.'^[13]
4. ^$ENV is $HOME/.shrc in newer versions of the Bourne Shell
5. ^Same behavior as sh, but only if invoked as sh (bash 2+) or, since bash 4.2, also if invoked explicitly in POSIX compatibility mode (with options --posix or -o posix).^[14]
6. ^ ^abOnly in sh/ksh compatibility mode (when invoked as bash, sh, ksh)
7. ^ ^abcin fact, the first readable of ~/.bash_profile, ~/.bash_login and ~/.profile; and only ~/.profile if invoked as sh or, as of at least Bash 4.2, if invoked explicitly in POSIX compatibility mode (with options --posix or -o posix)

Other shells[edit]

Variations on the Unix shell concept that don't derive from Bourne shell or C shell include the following:^[15]

• es – A functional programming rc-compatible shell written in the mid-1990s.
• Friendly interactive shell (fish) – First released in 2005.
• PowerShell – An object-oriented shell developed originally for Windows OS and now available to macOS and Linux.
• Qshell – A shell on the IBM i operating system based on POSIX and X/Open standards.
• rc – The default shell on Plan 9 from Bell Labs and Version 10 Unix written by Tom Duff. Ports have been made to various Unix-like operating systems.
• scsh – A Scheme Shell.
• wish – A windowing shell for Tcl/Tk.

See also[edit]

References[edit]

1. ^ ^abTom Van Vleck (1995-02-05). 'Unix and Multics'. Multicians.org. Retrieved 2012-08-14.
2. ^Bourne, Stephen R. (October 1983). 'The Unix Shell'. BYTE. p. 187. Retrieved 30 January 2015.
3. ^'V6 Thompson Shell Port - History'. V6shell.org. Retrieved 2012-08-14.
4. ^Louis Pouzin (2000-11-25). 'The Origin of the Shell'. Multicians.org. Retrieved 2012-08-14.
5. ^Nikolai Bezroukov (2015-08-13). 'Introduction to the Unix shell history'. Softpanorama. Retrieved 2016-08-21.
6. ^'Bourne shell, or sh'. Interview with Steve Bourne. Computerworld. 2009-03-05. Retrieved 2016-08-21.
7. ^'Re: Late Bloomers Revisited'. Retrieved 20 September 2014.
8. ^Korn, David G. (October 26, 1994), 'ksh - An Extensible High Level Language', Proceedings of the USENIX 1994 Very High Level Languages Symposium, USENIX Association, retrieved February 5, 2015, Instead of inventing a new script language, we built a form entry system by modifying the Bourne shell, adding built-in commands as necessary.
9. ^Harley Hahn, Harley Hahn's Guide to Unix and Linux.
10. ^'Hamilton C shell for Windows Release Notes 4.0'. Retrieved 20 September 2014.
11. ^'Different UNIX Shells'. unixnote.com. 2010. Retrieved 2016-08-21.
12. ^SCO Unix Group, SCO Unixware 7 documentation, 22 Apr 2004, retrieved 18 Oct 2012.
13. ^'Shell Command Language'. opengroup.org. Retrieved 15 June 2015.
14. ^'Bash Reference Manual: Bash Startup Files'. gnu.org. Retrieved 15 June 2015.
15. ^'FreeBSD Ports: Shells'. Freebsd.org. 2014-03-30. Retrieved 2014-04-05.

Bash Terminal Download Win 10