Your currently stated requirements would be fulfilled by anything with a general-purpose CPU made in the last decade and 2-4GB RAM. You could use almost literally anything that looks like a computer and isn't ancient.
You're going to need to go into more detail to get any advice worth following here.
What home servers differ most in is storage capacity, compute power and of course cost.
Do you plan on running any services that require significant compute power?
How much storage do you need?
How much do you want it to cost to purchase?
How much do you want it to cost to running?
Most home server services aren't very heavy. I have like 8 of them running on my home server and it idles with next to no CPU utilisation.
For me, I can only see myself needing ~dozens of TiB and don't forsee needing any services that require significant compute.
My home server is an 4 core 2.2GHz Intel J4105 single-board computer (mATX) in a super cheap small PC tower case that has space for a handful of hard drives. I'd estimate something on this order is more than enough for 90% of people's home server needs. Unless you have specific needs where you know it'll need significant compute power, it's likely enough for you too.
It needs about 10-20W at idle which is about 30-60€ per year in energy costs.
I've already seen pre-built NAS with fancy hot-swap bays recommended here (without even asking what you even need of it, great). I think those are generally a waste of money because you easily can build a low-power PC for super cheap yourself and you don't need to swap drives all that often in practice. The 1-2 times per decade where you actually need to do anything to your hard drives, you can open a panel, unplug two cables and unscrew 4 screws; it's not that hard.
Someone will likely also recommend buying some old server but those are loud and draw so much power that you could buy multiple low power PCs every year for the electricity cost alone. Oh and did I mention they're loud?
I'm quite certain it was being compared to mainline WINE, so no esync or fsync which themselves usually double FPS in CPU-bound scenarios.
Hers is actually better
[citation needed]
From what I gather from the ntsync feedback thread where some users have tested the WIP patches, it's not clearly better than esync/fsync but rather slightly worse. Though that isn't very clear data as it's still in development. Still, if it was very clearly better than the status quo, we should have already seen that.
can be fully implemented in Wine
It cannot, hence the kernel patch.
It’ll be better but no one really knows the full concrete extend of improvement until it lands
I see no reason to believe it should be "better". If anything, I'd expect slightly worse performance than esync/fsync because upstream WINE primarily wants a correct solution while the out-of-tree esync/fsync patches trade some correctness for performance in games.
Ideally, I'd like to be proven wrong; that ntsync is both correct and performant but that's not what you should expect going into this.
That's just an ACK and Elizabeth replied that she'll resend again with further changes.
Nothing is in any tree that is going to Linus yet AFAICT.
We could be reasonably sure that it'll go to Linus if it's in char-misc but that hasn't happened yet. I'm also actually not sure whether Greg's or Arnd's tree is the canonical one there.
What exactly does she need the SD card for? If she just needs to transfer files to and from an SD card, an external reader (via USB) might be sufficient.
3.5mm jack can be substituted with an external adapter too and they're not even half bad.
Both suboptimal of course but small phones that don't suck are rare enough as is.
If size is the most important, get an a-variant Pixel.
This is also one of those weird things: Why do people use dd for this?
It doesn't do anything special, it just does a plain old read()/write() loop on regular-ass UNIX files. Its actual purpose is to do character set conversions while doing so.
You can just cp image.iso /dev/sda or even cat image.iso > /dev/sda. (The latter only works in a privileged shell because it's the shell which open()s the device file.)
Installing it offline could prove to be quite a challenge. If you don't actually need Nix (the package manager) to work on your target system though, you could just not install Nix and use i.e. a static Nix binary to do the store path copying.
Read closely and you'll notice they used a thumb drive.
People usually refer to the act of copying the data directly onto the device as something other than "copying" to differentiate from copying the ISO as a file to a filesystem on the drive.
Note that the clients being FOSS is of little relevance because all they do is forward a recording to a blackbox proprietary service run by a for-profit company.
The code that has access to your audio and does the actual task at hand is not FOSS in the slightest.
Atemu @ Atemu @lemmy.ml Posts 63Comments 1,439Joined 5 yr. ago
Ding ding ding, the only good reply in this thread.
The symptoms described by OP smell like good old memory exhaustion.