Is there a URL I can go to, to see the versions of packages (libraries) that are in the version of torizonOS we are using?

Technical Support
, , ,
1

We need to list all the versions of libraries that are being used in the build of TorizonOS for our records. Is there a place I can go to get this information?

Thanks,
Steve

3

Hey @Evets,

I believe the best way to get information such as this is to use various tools that make sense within yocto. I don’t believe there is an easy/known way of getting this information without using the tools that ultimately built the image.

You can utilize some tools like build history, or the manifest document in the `torizon-build/deploy/<module_name>/ directory there is a <image_name>.manifest that has the information you are looking for.

Which for an empty build on my host computer has ~1951 entries in the format of :


lvm2-scripts cortexa53 2.03.11-r0
lvm2-udevrules cortexa53 2.03.11-r0
makedevs cortexa53 1.0.1-r0
mmc-utils cortexa53 0.1+git0+b7e4d5a6ae-r0
modemmanager cortexa53 1.18.8-r0
modemmanager-bash-completion cortexa53 1.18.8-r0
mwifiexconf cortexa53 1.0-r0
nano cortexa53 6.2-r0
ncurses cortexa53 6.3+20220423-r0
ncurses-terminfo-base cortexa53 6.3+20220423-r0
ndctl cortexa53 v73-r0
ndctl-bash-completion cortexa53 v73-r0
neofetch cortexa53 7.1.0+git0+60d07dee6b-r0
net-tools cortexa53 2.10-r0
net-tools-mii-tool cortexa53 2.10-r0

-Eric

4

@eric.tx
OK, also, I just downloaded the 6.6.1 quarterly release, and it doesn’t appear that ssh is turned on in it. Is that normal?
If so, how do I turn ssh back on? I tried openssh, but it’s completely unconfigured. Since ssh seemed to be running,

Thanks,
Steve

5

Hey @Evets,

Seems to work well on my end.

Can you give more details?

image
image974×514 52 KB

-Eric

6

@eric.tx
HI Eric,
I can ping it, but I get no response and eventually it times out. Worked fine before I put it on. I’ve installed it a couple of times, using the same build method I have with earlier builds. I’ll try rebuilding it again to see what happens. ssh is on, maybe port 22 isn’t open? But maybe windows did something. I’ll investigate more.

Your hardware is slightly different, mine is V1.1A, but that shouldn’t affect ssh, I wouldn’t think.

Thanks,
Steve

7

@eric.tx
Hi Eric,
What do you get when you run this:

netstat -tuplen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 990 20567 674/systemd-resolve
tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 990 20561 674/systemd-resolve
tcp 0 0 127.0.0.1:36205 0.0.0.0:* LISTEN 0 20712 720/containerd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 14172 1/init
tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 990 20569 674/systemd-resolve
tcp6 0 0 :::5355 :::* LISTEN 990 20564 674/systemd-resolve
tcp6 0 0 :::2375 :::* LISTEN 0 17953 804/dockerd
tcp6 0 0 :::22 :::* LISTEN 0 16623 1/init
tcp6 0 0 :::111 :::* LISTEN 0 14173 1/init
udp 0 0 127.0.0.54:53 0.0.0.0:* 990 20568 674/systemd-resolve
udp 0 0 127.0.0.53:53 0.0.0.0:* 990 20566 674/systemd-resolve
udp 0 0 0.0.0.0:111 0.0.0.0:* 0 909 1/init
udp 0 0 0.0.0.0:60042 0.0.0.0:* 987 20600 709/avahi-daemon: r
udp 0 0 0.0.0.0:5353 0.0.0.0:* 987 20598 709/avahi-daemon: r
udp 0 0 0.0.0.0:5355 0.0.0.0:* 990 20560 674/systemd-resolve
udp6 0 0 :::111 :::* 0 16454 1/init
udp6 0 0 fe80::bf:d207:da54::546 :::* 0 18777 662/NetworkManager
udp6 0 0 :::48109 :::* 987 20601 709/avahi-daemon: r
udp6 0 0 :::5353 :::* 987 20599 709/avahi-daemon: r
udp6 0 0 :::5355 :::* 990 20563 674/systemd-resolve

This shows it is only listening on port 22 for IPv6, not IPv4.

Steve

8

Eric,
Nevermind, there was an issue with my PC.