Linux commands for Windows

It’s very common scenario in IT field that people who are familiar with one OS have to learn/work with another OS. I do see many people, who are familiar with Linux commands, looking for their equivalent commands in Windows OS. Below I have attempted to list down the Windows commands for most widely used Linux commands. If I have missed any, please write in the comments section and let me know.

Ls : The Windows equivalent one is dir. ‘Dir‘ has many switches to list files based on different attributes, sort the list on size or date modified etc.

Grep : Findstr is the closet matching one for grep. find is also for searching strings in files, but it does not have many options.

Adduser: We can use net user to manage user accounts.

Useradd: net localgroup can be used to manage user groups. Net group can be used to manage active directory (domain) groups.

Uname : ver command shows Windows OS version. Systeminfo shows lot of hardware and software information.
Ps : The closest matching command is tasklist, though it’s not as feature rich as ps.

Echo : echo. Very much similar to Linux’s echo.
Md : mkdir

rm: Del deletes files whereas rmdir can be used to delete directories.
Du : du can be used to monitor the disk usage. However, this tool is not part of Windows OS. We need to install it separately. See the link for more information.
Df : Net use. We can list the network shares mapped on the computer.
Mount : Net use . Map network share to local drive
Cat : Type print the contents of a text file in the console/command prompt.
Head : there’s no equivalent command I am aware of.
Tail : Tail resource kit tool.
touch: Fsutil can be used to create files of require size.

I will add few more commands to the list soon…If you are searching for some specific command and do not find it here, please let me know.

Команда Uname в Linux

В этой статье мы рассмотрим команду uname .

uname — это утилита командной строки, которая выводит основную информацию об имени операционной системы и аппаратном обеспечении системы.

команда uname

Инструмент uname обычно используется для определения архитектуры процессора, имени хоста системы и версии ядра, работающего в системе.

Синтаксис команды uname имеет следующий вид:

Возможны следующие варианты:

• -s , ( —kernel-name ) — печатает имя ядра.
• -n , ( —nodename ) — печатает имя узла системы (имя хоста). Это имя, которое система использует при обмене данными по сети. При использовании с параметром -n uname дает тот же результат, что и команда hostname .
• -r , ( —kernel-release ) — печатает версию ядра.
• -v , ( —kernel-version ) — —kernel-version ядра.
• -m , ( —machine ) — печатает имя аппаратного имени машины.
• -p , ( —processor ) — печатает архитектуру процессора.
• -i , ( —hardware-platform ) — печатает аппаратную платформу.
• -o , ( —operating-system ) — —operating-system имя операционной системы. В системах Linux это «GNU / Linux»
• -a , ( —all ) — При использовании параметра -a uname ведет себя так же, как если бы были заданы параметры -snrvmo .

При вызове без каких-либо параметров uname выводит имя ядра, как если бы была указана опция -s :

Как вы уже знаете, имя ядра — «Linux»:

Вам не нужно запоминать все параметры командной строки. Обычно команда uname используется с параметром -a для вывода всей доступной информации:

Вывод включает следующую информацию:

• Linux — имя ядра.
• dev.linuxize.com — Имя хоста.
• 4.19.0-6-amd64 Релиз ядра.
• #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) — Версия ядра.
• x86_64 — Имя оборудования компьютера.
• GNU/Linux — Название операционной системы.

Параметры можно комбинировать друг с другом для получения желаемого результата. Например, чтобы узнать, какая версия ядра Linux работает в вашей системе, вы должны ввести следующую команду:

При использовании нескольких параметров информация, содержащаяся в выводе, находится в том же порядке, что и параметр -a . Положение данных опций не имеет значения. И uname -msr и uname -srm дают одинаковый результат.

Выводы

Команда uname используется для печати основной системной информации. Обычно он вызывается с параметром -a для отображения всей доступной информации.

Если у вас есть какие-либо вопросы или отзывы, не стесняйтесь оставлять комментарии.

Uname command in windows

display system name information

Command, KornShell Built-in

The uname command lets shell scripts and other programs determine configuration information about the machine upon which the KornShell is running.

You can use the major and minor version numbers, returned by the and options to determine precisely which version of Windows is running on the machine:

displays all fields (equivalent to ).

displays the CPU or machine type. Possible values include:

displays the node name of this particular machine. The node name usually differentiates machines running at one location.

displays the release (major version) number of the operating system.

displays the name of the operating system. This is the default output, when no options are given. The operating system name is Windows_NT for all supported platforms.

displays the version (minor version) number of the operating system.

uname displays the selected information in the following order:

This shell command changes the prompt to identify the computer location.

Possible exit status values are:

Failure due to an inability to find the desired information.

Failure due to an invalid command line option.

POSIX.2. x /OPEN Portability Guide 4.0. UNIX System V. Windows Server 2012. Windows 8.1. Windows Server 2012 R2. Windows 10. Windows Server 2016. Windows Server 2019.

uname is provided as both an external utility and as a built-in MKS KornShell utility.

PTC MKS Toolkit for Power Users
PTC MKS Toolkit for System Administrators
PTC MKS Toolkit for Developers
PTC MKS Toolkit for Interoperability
PTC MKS Toolkit for Professional Developers
PTC MKS Toolkit for Professional Developers 64-Bit Edition
PTC MKS Toolkit for Enterprise Developers
PTC MKS Toolkit for Enterprise Developers 64-Bit Edition

PTC MKS Toolkit 10.3 Documentation Build 39.

OS detecting makefile

I routinely work on several different computers and several different operating systems, which are Mac OS X, Linux, or Solaris. For the project I’m working on, I pull my code from a remote git repository.

I like to be able to work on my projects regardless of which terminal I’m at. So far, I’ve found ways to get around the OS changes by changing the makefile every time I switch computers. However, this is tedious and causes a bunch of headaches.

How can I modify my makefile so that it detects which OS I’m using and modifies syntax accordingly?

Here is the makefile:

13 Answers 13

There are many good answers here already, but I wanted to share a more complete example that both:

• doesn’t assume uname exists on Windows
• also detects the processor

The CCFLAGS defined here aren’t necessarily recommended or ideal; they’re just what the project to which I was adding OS/CPU auto-detection happened to be using.

The uname command (http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/uname.1.html) with no parameters should tell you the operating system name. I’d use that, then make conditionals based on the return value.

Detect the operating system using two simple tricks:

• First the environment variable OS
• Then the uname command

Or a more safe way, if not on Windows and uname unavailable:

Ken Jackson proposes an interesting alternative if you want to distinguish Cygwin/MinGW/MSYS/Windows. See his answer that looks like that:

Then you can select the relevant stuff depending on detected_OS :

Notes:

Command uname is same as uname -s because option -s ( —kernel-name ) is the default. See why uname -s is better than uname -o .

The use of OS (instead of uname ) simplifies the identification algorithm. You can still use solely uname , but you have to deal with if/else blocks to check all MinGW, Cygwin, etc. variations.

The environment variable OS is always set to «Windows_NT» on different Windows versions (see %OS% environment variable on Wikipedia).

An alternative of OS is the environment variable MSVC (it checks the presence of MS Visual Studio, see example using Visual C++).

Below I provide a complete example using make and gcc to build a shared library: *.so or *.dll depending on the platform. The example is as simplest as possible to be more understandable.

To install make and gcc on Windows see Cygwin or MinGW.

My example is based on five files

Reminder: Makefile is indented using tabulation. Caution when copy-pasting below sample files.

The two Makefile files

1. lib/Makefile

2. app/Makefile

The source code

— lib/hello.h

— lib/hello.c

— app/main.c

The build

Fix the copy-paste of Makefile (replace leading spaces by one tabulation).

The make command is the same on both platforms. The given output is on Unix-like OSes:

The run

The application requires to know where is the shared library.

On Windows, a simple solution is to copy the library where the application is:

On Unix-like OSes, you can use the LD_LIBRARY_PATH environment variable:

Run the command on Windows:

Run the command on Unix-like OSes:

I was recently experimenting in order to answer this question I was asking myself. Here are my conclusions:

Since in Windows, you can’t be sure that the uname command is available, you can use gcc -dumpmachine . This will display the compiler target.

There may be also a problem when using uname if you want to do some cross-compilation.

Here’s a example list of possible output of gcc -dumpmachine :

You can check the result in the makefile like this:

It worked well for me, but I’m not sure it’s a reliable way of getting the system type. At least it’s reliable about MinGW and that’s all I need since it does not require to have the uname command or MSYS package in Windows.

To sum up, uname gives you the system on which you’re compiling, and gcc -dumpmachine gives you the system for which you are compiling.

The git makefile contains numerous examples of how to manage without autoconf/automake, yet still work on a multitude of unixy platforms.

Update: I now consider this answer to be obsolete. I posted a new perfect solution further down.

If your makefile may be running on non-Cygwin Windows, uname may not be available. That’s awkward, but this is a potential solution. You have to check for Cygwin first to rule it out, because it has WINDOWS in its PATH environment variable too.

I finally found the perfect solution that solves this problem for me.

The UNAME variable is set to Linux, Cygwin, MSYS, Windows, FreeBSD, NetBSD (or presumably Solaris, Darwin, OpenBSD, AIX, HP-UX), or Unknown. It can then be compared throughout the remainder of the Makefile to separate any OS-sensitive variables and commands.

The key is that Windows uses semicolons to separate paths in the PATH variable whereas everyone else uses colons. (It’s possible to make a Linux directory with a ‘;’ in the name and add it to PATH, which would break this, but who would do such a thing?) This seems to be the least risky method to detect native Windows because it doesn’t need a shell call. The Cygwin and MSYS PATH use colons so uname is called for them.

Note that the OS environment variable can be used to detect Windows, but not to distinguish between Cygwin and native Windows. Testing for the echoing of quotes works, but it requires a shell call.

Unfortunately, Cygwin adds some version information to the output of uname, so I added the ‘patsubst’ calls to change it to just ‘Cygwin’. Also, uname for MSYS actually has three possible outputs starting with MSYS or MINGW, but I use also patsubst to transform all to just ‘MSYS’.

If it’s important to distinguish between native Windows systems with and without some uname.exe on the path, this line can be used instead of the simple assignment:

Of course in all cases GNU make is required, or another make which supports the functions used.

Windows commands

All supported versions of Windows (server and client) have a set of Win32 console commands built in.

This set of documentation describes the Windows Commands you can use to automate tasks by using scripts or scripting tools.

Prerequisites

The information that is contained in this topic applies to:

• Windows Server 2019
• Windows Server (Semi-Annual Channel)
• Windows Server 2016
• Windows Server 2012 R2
• Windows Server 2012
• Windows Server 2008 R2
• Windows Server 2008
• Windows 10
• Windows 8.1

Command shell overview

The Command shell was the first shell built into Windows to automate routine tasks, like user account management or nightly backups, with batch (.bat) files. With Windows Script Host you could run more sophisticated scripts in the Command shell. For more information, see cscript or wscript. You can perform operations more efficiently by using scripts than you can by using the user interface. Scripts accept all Commands that are available at the command line.

Windows has two command shells: The Command shell and PowerShell. Each shell is a software program that provides direct communication between you and the operating system or application, providing an environment to automate IT operations.

PowerShell was designed to extend the capabilities of the Command shell to run PowerShell commands called cmdlets. Cmdlets are similar to Windows Commands but provide a more extensible scripting language. You can run Windows Commands and PowerShell cmdlets in Powershell, but the Command shell can only run Windows Commands and not PowerShell cmdlets.

For the most robust, up-to-date Windows automation, we recommend using PowerShell instead of Windows Commands or Windows Script Host for Windows automation.

You can also download and install PowerShell Core, the open source version of PowerShell.

Incorrectly editing the registry may severely damage your system. Before making the following changes to the registry, you should back up any valued data on the computer.

To enable or disable file and directory name completion in the Command shell on a computer or user logon session, run regedit.exe and set the following reg_DWOrd value:

To set the reg_DWOrd value, use the hexadecimal value of a control character for a particular function (for example, 0 9 is Tab and 0 08 is Backspace). User-specified settings take precedence over computer settings, and command-line options take precedence over registry settings.

Command-line reference A-Z

To find information about a specific command, in the following A-Z menu, click the letter that the command starts with, and then click the command name.