Relevant documentation for others about -S / spindown_time:
Values from 1 to 240 specify multiples of 5 seconds, yielding timeouts from 5 seconds to 20 minutes. Values from 241 to 251 specify from 1 to 11 units of 30 minutes, yielding timeouts from 30 minutes to 5.5 hours. A value of 252 signifies a timeout of 21 minutes.
That should be a choice of the OS / controller card not of the drive itself. Also what datacenter wants to run drives that don’t report half of the SMART data just because they felt like it?
It depends. They’re simply the most annoying drives out there because Seagate on their wisdom decided to remove half of the SMART data from reports and they won’t let you change the power settings like other drives. Those drives will never spin down, they’ll even report to the system they’re spun down while in fact they’ll be still running at a lower speed. They also make a LOT of noise.
not really for casual browsing use cases when pretty much 99% of all the major players in the browsing industry maintain a Linux port.
Those users couldn’t care less about if Windows is supported or not. They wont send their 240 million computers to the landfill, they’ll just keep using them.
Either way, Windows 10 22H2 EOL is set to 14 Oct 2025 and Enterprise LTS to 12 Jan 2027. I’m sure Microsoft will cave around January 2026 whenever the first 0-day for Windows 10 22H2 Pro goes into the wild and extends support for the Pro version to 2027 as well for no extra cost. For them this makes way more business sense than having 240M machines infected giving a poor image of Windows.
But it may never see much progress on the WebUI for instance while Canonical has paying customers pushing and asking for it. They may appear inactive and it seems there aren’t many people working on the project but who knows? Maybe they’re setting up their own image server, repacking images etc.
Again, I’m all in favor of this change and I’ve a couple of systems running on both and will obviously migrate everything to Incus but I can’t ignore the fact that enterprise money pushes Canonical todevelop things.
Because I forgot I own it… no. But because I was too lazy go get the physical media and insert into my desktop player, oh yes. To be fair it downloaded probably faster than the time I would’ve spent looking for it.
I perfectly understand, approve and back this move, however I’ve a question about the current state of things and specifically Debian 12 users. Debian includes LXD LTS 5.0.2 on their repositories and that version will be still be around after 2024/05 and trying to use the image server. Debian won’t likely change stable to include Incus until 2025, what’s the suggested path here?
The issue here is that this will stall the development of LXD/Incus. Two separate projects running in different directions no future feature parity and potentially less features in Incus than in LXD.
Are you planning on transcoding? If so you might want to add a decent GPU to deal with that as the CPU won’t be most likely able to handle it alone. Otherwise it should be fine.