Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

linux only ? #19

Open
gedw99 opened this issue Aug 7, 2024 · 1 comment
Open

linux only ? #19

gedw99 opened this issue Aug 7, 2024 · 1 comment

Comments

@gedw99
Copy link

gedw99 commented Aug 7, 2024

I wanted to use this to help with device debugging on servers but also other devices like desktops etc.

Seems it's linux only ?

from my Mac :

go install github.com/powersj/whatsthis/app/whatsthis@latest
go: downloading github.com/powersj/whatsthis v1.3.5
go: github.com/powersj/whatsthis/app/whatsthis@latest: create zip: internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/size: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/size": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/uevent: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/uevent": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p2/size: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p2/size": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p2/uevent: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p2/uevent": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/size: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/size": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/uevent: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/uevent": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:04.0/0000:05:00.0/net/wlp5s0/address: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:04.0/0000:05:00.0/net/wlp5s0/address": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:04.0/0000:05:00.0/net/wlp5s0/device/uevent: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:04.0/0000:05:00.0/net/wlp5s0/device/uevent": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:04.0/0000:05:00.0/net/wlp5s0/mtu: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:04.0/0000:05:00.0/net/wlp5s0/mtu": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:04.0/0000:05:00.0/net/wlp5s0/uevent: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:04.0/0000:05:00.0/net/wlp5s0/uevent": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:05.0/0000:06:00.0/net/enp6s0/address: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:05.0/0000:06:00.0/net/enp6s0/address": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:05.0/0000:06:00.0/net/enp6s0/device/uevent: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:05.0/0000:06:00.0/net/enp6s0/device/uevent": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:05.0/0000:06:00.0/net/enp6s0/mtu: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:05.0/0000:06:00.0/net/enp6s0/mtu": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:05.0/0000:06:00.0/net/enp6s0/speed: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:05.0/0000:06:00.0/net/enp6s0/speed": invalid char ':'
internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:05.0/0000:06:00.0/net/enp6s0/uevent: malformed file path "internal/filesystem/testdata/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:05.0/0000:06:00.0/net/enp6s0/uevent": invalid char ':'
@powersj
Copy link
Owner

powersj commented Aug 7, 2024

I wanted to use this to help with device debugging on servers but also other devices like desktops etc.

Thanks for sharing you use case!

Seems it's linux only ?

Unfortunately, yes. The bulk of the data is pulled from the procfs and sysfs filesystems currently. macOS does not implement procfs. While some equivalent data can be found via sysctl I'm not sure all of it can be found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants