Aka “Windows subsystem for Linux”

Removed by mod

Kill -9 is a command on Unix and Linux to send signal 9 (SIGKILL) to a process. That’s the version of kill that is the most reliable and has immediate effect.

Taskkill is a Windows command line program. I believe that taskkill /f uses the TerminateProcess() API. This is more forceful than the End Task button on the Task Manager. There is a different End Process button on the Task Manager that does use TerminateProcess().

TerminateProcess() is pretty reliable, but it doesn’t form part of the C signals stack on Windows like kill -9. So for instance, if you’re doing process control on Python, you need to use a special Windows-only API to access TerminateProcess().

Would a fork be technically viable if Americans and American businesses can’t participate (because the fork works with SDN entities)? Maybe.

The reality is that the Linux Foundation is in the United States, and Linus is a naturalized US citizen who lives in Oregon (at least on Wikipedia). So they both will have to pay attention to avoid transacting business with individuals and companies on the SDN list. That is the law in the United States.

Yep. Linux is a total pain in the behind to write applications for, because of API and ABI instability. Just ask notable Linux desktop application developer Linus Torvalds.

(not a lawyer). If you bought the game copies that the AIs are playing, then it seems like you’re not making a copy of the game just to have the AI play it.

That kind of assumes that your AI is playing the game through a mechanism like AutoHotKey, generating keyboard or controller inputs that pass through the operating system to the game.

If your AI hooks into or modifies the game code to “play”, then it could run afoul of anti-reverse engineering clauses that are common in the click through license agreements. Those clauses may not be enforceable in your jurisdiction. Legal results on anti-reverse engineering clauses are kind of mixed in the United States.

Edit: for reference, there was a software called “Glider” that played World of Warcraft for you, so you don’t have to grind to level up. Blizzard absolutely hated the makers of Glider, but it stuck around for a long time, before it was ultimately sued into oblivion.

It used to be that 640K oughta be enough for anyone.

The Linux software you can get as a regular user from your typical Linux distributions is absolutely not any more secure on average than your typical Windows software.

I say this as someone who writes application programs on both systems.

I think it’s really debatable whether the Linux kernel is really any more secure than the Windows NT kernel. Linux advocates have pushed the “many eyes, shallow bugs” line for a long time, but high profile lapses seem to really have put the lie to that.

That’s what I’ve got (on Gentoo).

Process Explorer is still great.

For example, synaptic is a long running front end for apt that has the buttons for update and upgrade.

Oh yeah. I remember all the warnings plastered all over the X11 config file about how dangerous the settings were if you got them wrong.

Discarded corn cobs and pages from the Sears Roebuck catalog. At least in midwestern USA.

I think my mother played that star trek game on a time shared minicomputer.

Let us all remember that, at least back when it started, the establishment alternative to systemd was a product named after its original operating system, System V UNIX, which is a direct descendent of the original UNIX from AT&T. This sysvinit software used complicated shell scripts to manage daemons. Contrary to some opinions, these shell scripts were not “just working”; they were in fact a constant and major maintenance burden for Linux distributions. When I started on Linux at least, Debian had a suspiciously large fraction of bugs on init script breakages.

All this is to say that the new system, systemd, doesn’t have to be anywhere near perfect to be worth replacing sysvinit.

People argue that systemd is rejecting the “UNIX philosophy” of small tools that do one thing well. I argue that this UNIX philosophy is not some kind of universal good with no tradeoffs. It’s an engineering rule of thumb. There are always tradeoffs.

People argue that systemd is too much like Windows NT. I argue that Windows NT has at least a few good ideas in it. And if one of those ideas solves a problem that Linux has, Linux should use that idea.

Pay no attention to gconf, dconf, GSettings, or whatever else there is.

Some of those dialog boxes have not changed a bit since Windows 3.0.

The bit about the small forge forging a forge is skewering the Gentoo concept of toolchain bootstrapping.

Problem: how can you claim to have compiled the entire system on your own local machine if you need a compiler to compile a compiler? Where do you get that compiler from?

Solution: Use an external compiler to compile a compiler. Then use that compiler that you just compiled to compile itself again. Then use that second compiler to recompile the rest of the system.