Identification info within iSH (Device, CPU, RAM, Network etc)?

[iyerusad]

What are the identification options within iSH/can we get more identification in iSH?

What info might be useful:

• Device model (e.g. iPad, iPad Pro, iPad Air 5 2022)
• CPU name (e.g. A15, M1)
• Network info (private IP, card?)
• ???

Places I have checked:

• uname -a
  • Was able to source OS family (Linux) and arch (i686/x86/32bit)
• cat /etc/os-release
  • Was able to source OS name (Alpine Linux) and OS version (3.14.3)
• cat /proc/version
  • Was able to source iSH name, version, build (albeit unstructured)
• nproc
  • Was able to source number of presumably the perceived physical CPUs, namely 1
• getconf _NPROCESSORS_ONLN
  • Was able to source presumably the perceived virtual CPUs, namely 6
• cat /proc/meminfo | grep MemTotal
  • Was able to source amount of RAM
• hostname
  • Was able to source device name
• df -h
  • Was able to source diskspace of root filesystem /
• lscpu - failed to determine number of CPUs
• cat /proc/cpuinfo - failed, no such file
• free - failed, returns table of memory data, but unpopulated/zero values
• lspci - failed, cannot open /proc/bus/pci
• lshw - failed, returns data but not particularly useful
• hwinfo - mostly failed, returns data but most details are not implemented/unable to probe
• ip a/ip addr - failed, invalid argument/socket doesn't exist

Why

Find it neat to see this kind of info injected it into my .profile, example below on new shell session:

P.S.> ❤️ Kudos on a neat project, been tweaking .dotfiles to support iSH, been a fun way to dip toe into Alpine and challenge assumptions of available tools (or even CPU instructions) and the lack thereof.

[saagarjha]

We can probably expose some of these (we're working on an interface to do so), yeah. But it's all manual from our side, so we'll probably start with the obvious ones first. To help us pick, what are you planning on use this for?

[iyerusad]

To help us pick, what are you planning on use this for?

Mostly for fun + easy visualization of what/where I'm working on in a new shell session.

The one practical use case that came up was/is limiting certain packages from being installed on iSH environment until CPU instructions are working (e.g. rely on built-in ls vs something like lsd which has some bugs within iSH at the moment).

If I had to say biggest interest would be possibly an additional /etc/ish-release file that might allow more structured parsing of iSH version etc - the current cat /proc/version looks to be a little difficult to parse sanely.

[saagarjha]

If I had to say biggest interest would be possibly an additional /etc/ish-release file that might allow more structured parsing of iSH version etc - the current cat /proc/version looks to be a little difficult to parse sanely.

Boy do I have the commit for you: https://github.com/ish-app/ish/commit/a2df244e81be2780d1ce800125104d24c5574090