| cd / chdir | |
| Developer: | AT&T Bell Laboratories, MetaComCo, Microsoft, IBM, DR, Novell, HP, JP Software, ReactOS Contributors |
| Operating System: | Unix, Unix-like, V, DOS, MSX-DOS, FlexOS, OS/2, TRIPOS, Windows, MPE/iX, Plan 9, Inferno, ReactOS, KolibriOS, SymbOS |
| Platform: | Cross-platform |
| Genre: | Command |
The command, also known as (change directory), is a command-line shell command used to change the current working directory in various operating systems. It can be used in shell scripts and batch files.
The command has been implemented in operating systems such as Unix, DOS, IBM OS/2,[1] MetaComCo TRIPOS,[2] AmigaOS[3] (where if a bare path is given, cd is implied), Microsoft Windows, ReactOS,[4] and Linux. On MS-DOS, it is available in versions 2 and later.[5] DR DOS 6.0 also includes an implementation of the and commands.[6] The command is also available in the open source MS-DOS emulator DOSBox and in the EFI shell.[7] It is named in HP MPE/iX.[8] The command is analogous to the Stratus OpenVOS command.[9]
is frequently included built directly into a command-line interpreter. This is the case in most of the Unix shells (Bourne shell, tcsh, bash, etc.), [[cmd.exe]] on Microsoft Windows NT/2000+ and Windows PowerShell on Windows 7+ and [[COMMAND.COM]] on DOS/ Microsoft Windows 3.x-9x/ME.
The system call that effects the command in most operating systems is that is defined by POSIX.
Command line shells on Windows usually use the Windows API to change the current working directory, whereas on Unix systems calls the POSIX C function. This means that when the command is executed, no new process is created to migrate to the other directory as is the case with other commands such as ls. Instead, the shell itself executes this command. This is because, when a new process is created, child process inherits the directory in which the parent process was created. If the command inherits the parent process' directory, then the objective of the command cd will never be achieved.
Windows PowerShell, Microsoft's object-oriented command line shell and scripting language, executes the command (cmdlet) within the shell's process. However, since PowerShell is based on the .NET Framework and has a different architecture than previous shells, all of PowerShell's cmdlets like, etc. run in the shell's process. Of course, this is not true for legacy commands which still run in a separate process.
A directory is a logical section of a file system used to hold files. Directories may also contain other directories. The command can be used to change into a subdirectory, move back into the parent directory, move all the way back to the root directory or move to any given directory.
Consider the following subsection of a Unix filesystem, which shows a user's home directory (represented as) with a file,, and three subdirectories.
If the user's current working directory is the home directory, then entering the command [[ls]] followed by might produce the following transcript:
The user is now in the "games" directory.
A similar session in DOS (though the concept of a "home directory" may not apply, depending on the specific version) would look like this:
C:\> dir workreports
DOS maintains separate working directories for each lettered drive, and also has the concept of a current working drive. The command can be used to change the working directory of the working drive or another lettered drive. Typing the drive letter as a command on its own changes the working drive, e.g. ; alternatively, with the switch may be used to change the working drive and that drive's working directory in one step.Modern versions of Windows simulate this behaviour for backwards compatibility under CMD.EXE.[10]
Note that executing from the command line with no arguments has different effects in different operating systems. For example, if is executed without arguments in DOS, OS/2, or Windows, the current working directory is displayed (equivalent to Unix [[pwd]]). If is executed without arguments in Unix, the user is returned to the home directory.
Executing the command within a script or batch file also has different effects in different operating systems. In DOS, the caller's current directory can be directly altered by the batch file's use of this command. In Unix, the caller's current directory is not altered by the script's invocation of the command. This is because in Unix, the script is usually executed within a subshell.
cd ~''username'' will put the user in the username's home directory.In the File Transfer Protocol, the respective command is spelled in the control stream, but is available as in most client command-line programs. Some clients also have the for changing the working directory locally.
The numerical computing environments MATLAB and GNU Octave include a cdfunction with similar functionality.[11] [12] The command also pertains to command-line interpreters of various other application software.