![]() Linux line commands enable you to gather all possible details about your computer's memory. The -i flag on the grep command simply ensures your search ignores whether the output it searches is upper or lower case. Or its BogoMips power rating: lscpu | grep -i bogo To view just the CPU's speed in megahertz: lscpu | grep -i mhz For example, to view only the CPU make and model: lshw -C cpu | grep -i product With all these commands, you can reduce verbiage and narrow any answer down to a single detail by parsing the command output with the grep command. Here you can find out whether your processor supports specific features. In both cases, the last few lines of output list all the CPU's capabilities. View CPU details by issuing either the lscpu command or its close relative lshw: lscpu You can learn everything about your CPU through line commands. The long forms of these two commands spew out exhaustive-but hard to read-output: hwinfo The hwinfo and lshw commands display much of the same information in different formats: hwinfo -short The -F flag means you'll get full output, x adds details, and z masks out personally identifying information like MAC and IP addresses. It's a standard diagnostic for problem-solving: inxi -Fxz Forum participants often ask for its output when they're trying to help others solve problems. The inxi command lists details about your system, CPU, graphics, audio, networking, drives, partitions, sensors, and more. ![]() There are several line commands that will give you a comprehensive overview of your computer's hardware. The quick reference chart at the end summarizes them. This article introduces many of the most useful line commands for system discovery. So either switch to the root user ID, or issue the command under your regular user ID preceded by sudo: sudo Īnd respond to the prompt for the root password. Many line commands for detecting hardware must be issued under root authority. Whether you employ the Linux shell or another programming language, scripting typically requires coding line commands. Probably the main reason to use line commands is for writing scripts. Perhaps you don't have a GUI program available or don't want to install one. Sometimes it's easy to find a specific bit of information through a well-targeted line command.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |