ie. the installer is entirely broken unless you, somehow, don't need any kernel modules whatsoever!

I initially reported this for pureos-8.0-live-amd64.hybrid.iso with a SHA1 of
021d002fe8f7fdf2ba4d53a40d297069ef0a811d

I can reproduce this on the latest version of pureos-8.0-live-amd64.hybrid.iso with SHA1 94a60b15505085c588ad67d13de40af957383fbe.

(The latter is apparently dated 2017-12-17)

I actually warned about this issue, so people would not link to the December image from our download page, as I haven't had the time to fix the problem during that month...
Oh well...

This issue will be resolved with the next image rebuild, which will be done once the Meltdown attack is mitigated in our kernel.

I actually warned about this issue, so people would not link to the December image from our download page

Not sure I understand this given that both versions (November and December?) do not work.

Hmm, the November image should work (from 2017-11-11) and only the December images should have this issue... But maybe I overlooked something there.
This issue should be resolved soon.

Thanks!

So my other ISO which I thought that was November might be from earlier - it has a non-November timestamp on my filesystem, but I have idea whether I can trust that hence giving you the SHAs in a few messages back.

(+1 for versioned file downloads!)

Confirmed with da3762b113acc39c81d6ba8a8903054ab40d3858 pureos-8.0-live-amd64.hybrid.iso