Respectfully, what a stubborn position to take. You don't want to listen to anyone else, and you don't want to be taught any new information about it that might change your mind.
Debian supports swap files and has information about setting them up in the Debian wiki, so I don't know why you're implying they've taken a stand on the issue.
Also, this seems to be based on a email from 2005, about kernel version 2.4 and 2.6, and their differences. Things might have changed since then, and also depends on a lot of factors, not the least what filesystem you use. I'm not sure people should seriously follow advice that basically boils down to "do this always it's best".
Better instead to make yourself informed about the tradeoffs, then make your own choice, for your setup.
The thread is quoted to show that they have been functionally equivalent for several decades and yet distros continue to push outdated recommendations.
> yet distros continue to push outdated recommendations
Is it possible perhaps that this advice doesn't apply equally to all situations? Is it the best for people on ZFS? Is it the best for distributions that have their own kernels builds?
I'm not saying it's a bad default, or that people should avoid it, just that it's likely not "the absolute best no questions asked" regardless of the situation, that was what I was trying to point out with my previous comment.
Just because there might exist tradeoffs doesn’t make them matter to someone. If you’re using a Linux distro then you’re already living off thousands of decisions made with tradeoffs and it’s hardly feasible to be informed or care about all of them.
It's actually incredibly sensible not to just make changes to core OS settings unless you know what you're doing. There are good reasons not to use swap files, which become evident in OOM situations.
As @mitxela says, if you need to fault in a page which is needed for some critical OS function, which requires going through the VFS layer, and that requires paging in another page, which has been swapped out due to memory pressure ... There are many edge cases.
Swap on primary partitions also complicates dump and restore, although hardly anyone seems to know what backups are now.
See, the thing is that swapping or paging to a file does not use the VFS layer, except when activating or deactivating it. So swapfiles may not be materially different from swap partitions during operations.
And there are many things that complicate dump and restore. Dump and restore often need to account for what partitions were created, anyway, so don't swap partitions also complicate it?
This was 2021, and while this bug is fixed, maybe take Linus's advice. Rely on a partition for primary swap, and only add files if you need to. Don't put them on the root partition, preferably a second disk.
Normally dump skips swap partitions entirely, and doesn't know anything about partitioning. Swap will refuse to activate on a non-mkswap partition so there is reasonable protection when you're migrating.
One traditional reason to prefer a swap partition was that the filesystem driver might have to allocate memory. I think swap files bypass the filesystem driver, though - getting the block extents and then accessing the block device at those locations, instead of accessing the file.
In the US you can always sue someone in civil court for damages you think they have caused you. For criminal charges you need to have violated the law, but in a civil case it seems it's enough to have suffered monetary or reputational harm which was the other person's fault whether intentional or due to negligence, etc.
IANAL, and I'd be surprised to see any lawsuit come out of this, but you certainly don't need to have "violated the law" to be on the receiving end of a lawsuit.
COM and WinRT (basically COM Next) are the way to do cross language Interoperability in Windows since VB 5 replaced VBX with OCX, it was a key feature in .NET Framework design, and revamped on Windows 8, when WinRT was introduced as the original design for .NET (Ext-VOS).
The original massive controversy was the founder of the studio claiming it had multiplayer when it very clearly didn't which was such an odd thing to claim and easy to prove false.
That and the trailer was very different than the released game.
They apologized IIRC and then continued to work on it for like a decade - adding multiplayer and many large changes to the game
No idea what I'm looking at, it's just combining some noise and a sawtooth wave to create pretty visuals I guess? if this is meant to serve as an introduction to the project it's not really succeeding. The "Description" isn't even readable despite most of the page being used for empty space. I guess it's expected to have no audio output? I presume the real purpose of this is to process signals from an actual radio?
The "Help"->"Help" menu item is notably unhelpful:
> For questions, comments, or suggestions, you can email support@gnuradioworld.com, join the Discord server, or post a GitHub issue.
"Help"->"About" at least starts to clarify some things:
> GNU Radio, entirely in your browser — explore the open-source SDR ecosystem with zero install!
> GNU Radio World is a browser-based GNU Radio Companion flowgraph editor and WebAssembly runtime. You can place, connect, and configure blocks, then run the resulting flowgraph directly in your browser.
> It is designed to download only the WebAssembly modules corresponding to the blocks you use. This on-demand architecture keeps the initial download small and can support a limitless collection of out-of-tree modules (OOTs) in the future.
> GNU Radio World also includes a collection of real RF recordings that are downloaded only when you use them. You can inspect the recordings in the built-in recording view, adapted from IQEngine, and use them in the included flowgraph examples, allowing OOTs to be shown off with real recordings of the corresponding signals
Hey it's Marc, creator of GNU Radio World, I'm glad you brought this up, I made it thinking it would be used by folks already familiar with GNU Radio, but this site can double as a way to introduce new people to GNU Radio, so it might as well have a more friendly introduction that walks you through the basics. I'll start working on it!
reply