Stewart X Addison

Running the following on [build-osuosl-ubuntu2204-aarch64-1](https://ci.adoptium.net/computer/build-osuosl-ubuntu2204-aarch64-1) with a view to switching over: - [sanity.perf](https://ci.adoptium.net/job/Grinder/8433/) PASSED - [extended.perf](https://ci.adoptium.net/job/Grinder/8434/) Failed as hostname wasn't resolvable in /etc/hosts - I've renamed the machine to [test-osuosl-ubuntu2204-aarch64-1](https://ci.adoptium.net/computer/test-osuosl-ubuntu2204-aarch64-1)...

`/etc/hosts` is getting overwritten on reboot by an entry that doesn't match `/etc/hostname`. I've adjusted `/etc/cloud/cloud.cfg` to comment out `update_etc_hosts` so the hostname resolution doesn't get lost as it won't...

Pass - have enabled `ci.role.perf` on those machines and marked the AWS on offline. There may be some argument for testing on Graviton machines, and RHEL on aarch64, but at...

Comparing with Linux, which installs under /usr/lib/jvm and has directories named: `temurin-17-jdk-amd64` (`.deb`) `temurin-17-jdk` (`.rpm`) On that basis it feels like a format change to `temurin-xx-jdk` etc. for windows would...

> as mentioned here https://github.com/adoptium/temurin-build/issues/2671, temurin = hotspot, but this was just a workaround Yep - it was me that implemented that change - VARIANT was just the easiest differentiator...

This feels like a case where you need to get libatomic from /somewhere/ for yocto, and if it doesn't provide you with one then you will need to build it...

I think this can probably be closed now but I'll await @steelhead31's return and leave it in the October mileston.

Above PR is merged so I'm closing this

> And TRSS runs as a regular Jenkins user. I believe this is complete. If anyone disagrees or believes additional work is required then it can be reopened.

Steps completed: - Under the vagrant1-vagrant4 users I have run: `vagrant box add generic/ubuntu2204` - On vagrant5 to see if this is a more sensible way of copying them across...