Windows 10 bash shell 10.0.14316 very good for getting system information.

Posted: April 12, 2016. At: 10:27 PM. This was 2 years ago. Post ID: 8866
Page permalink.
WordPress uses cookies, or tiny pieces of information stored on your computer, to verify who you are. There are cookies for logged in users and for commenters. These cookies expire two weeks after they are set.

The new bash shell in Windows 10 build 10.0.14316 is the best addition to Windows 10 yet. Here I am getting information about the CPU.

root@localhost:/mnt/c/Users/johnc# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 60
model name      : Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz
stepping        : 3
microcode       : 0xffffffff
cpu MHz         : 3399.000
cache size      : 256 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 6
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave osxsave avx f16c rdrand hypervisor
bogomips        : 6798.00
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

The networking does not work with this shell, so you cannot install any programs or ping websites, but the prompt is useful for using various commands. I am not sure why, there is no networking device available to create a static route. I have entered values into the /etc/resolv.conf, but this useless with no networking support. So you could not use the Lynx browser in a CMD window to browse Slashdot. But if the user has VMware, then Debian Jessie could be installed and this used to access a Linux command prompt.

The vmstat command is there, but the /proc filesystem is not working.

But I can use the lscpu command to get CPU information.

root@localhost:/mnt/c/Windows# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                1
On-line CPU(s) list:   0
Thread(s) per core:    1
Core(s) per socket:    1
Socket(s):             1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 60
Stepping:              3
CPU MHz:               3399.000
BogoMIPS:              6798.00
Hypervisor vendor:     VMware
Virtualization type:   full

Even piping works.

root@localhost:/mnt/c/Windows# lsof | grep txt
init      1 root  txt       REG    0,0   22856 1407374883651976 /init
bash      2 root  txt       REG    0,0 1021112 1125899906944571 /bin/bash
lsof     81 root  txt       REG    0,0  163224  562949953616850 /usr/bin/lsof
grep     82 root  txt       REG    0,0  191952 1125899906944574 /bin/grep
lsof     83 root  txt       REG    0,0  163224  562949953616850 /usr/bin/lsof

But not much else. Better to stick with a native Debian Jessie or Ubuntu 16.04 installation. This is shit without networking capability.

No comments have been made. Use this form to start the conversation :)

Leave a Reply