Loading...

VONDS ©

Lab 50: Finding System Architecture (arch)

Lab Index

Validate that a system meets a 64-bit deployment requirement by confirming architecture and CPU execution mode using CLI-only checks. Cross-verify results across multiple tools, then produce a simple confirmation statement suitable for a deployment note.

core troubleshooting

Scenario

You are preparing a report for a new software deployment. The application requires a 64-bit system, so you need to confirm the machine architecture and verify the OS is running in 64-bit mode using terminal commands only.

Operator context

This is a quick, low-risk validation you perform before installing binaries, troubleshooting compatibility failures, or approving a host for production workloads.

Objective

  • Check the machine architecture with arch.
  • Confirm the same architecture via uname -m.
  • Review CPU architecture and execution modes using lscpu.
  • Verify the OS bitness using getconf LONG_BIT.
  • Produce a short confirmation note suitable for a deployment record.

What You’ll Practice

  • Architecture identification using arch and uname -m.
  • CPU capability review using lscpu (including op-modes).
  • OS bitness validation using getconf LONG_BIT.
  • Practical cross-verification: confirming the same fact using multiple independent commands.
  • Writing a concise verification statement for operational documentation.

Walkthrough

Step 1 : Check the machine architecture.
Command 
arch

arch prints the system hardware architecture. This is a quick baseline check when confirming whether a host can run 64-bit binaries. 

x86_64
Step 2 : Confirm the same architecture with uname.
Command 
uname -m

uname -m reports the machine hardware name. Using a second command to confirm the same result reduces mistakes and strengthens the evidence you capture in a deployment report. 

x86_64
Step 3 : Review architecture and CPU execution modes.
Command 
lscpu

lscpu provides detailed CPU information, including the architecture, byte order, and supported CPU operating modes. This is useful when verifying that the hardware can execute 64-bit code even if the OS architecture is unclear. 

Architecture:           x86_64
CPU op-mode(s):         32-bit, 64-bit
Byte Order:             Little Endian
CPU(s):                 2
Model name:             Intel(R) Xeon(R) CPU
Step 4 : Verify OS bitness directly.
Command 
getconf LONG_BIT

getconf LONG_BIT reports whether the current userland is operating in 32-bit or 64-bit mode. This is a clean “yes/no” confirmation for deployment readiness. 

64
Step 5 : Write a short confirmation note.
Command 
echo 'System is 64-bit compatible'

This produces a short statement you can paste into a ticket, change record, or deployment checklist after completing your validation. 

System is 64-bit compatible

Reference

  • arch : Prints the machine hardware architecture.
  • uname -m : Displays the machine hardware name (architecture).
    • -m: Outputs the machine hardware name.
  • lscpu : Displays CPU architecture details and execution modes.
    • Useful fields include Architecture and CPU op-mode(s).
  • getconf LONG_BIT : Reports whether userland is operating in 32-bit or 64-bit mode.
    • LONG_BIT: Returns 32 or 64.
  • echo 'System is 64-bit compatible' : Produces a short confirmation message for operational notes.