“Nintendo sues” oh look it’s a day that ends in Y. The only person Nintendo isn’t dead set on suing is Nintendo.
Here’s you 937th remake of Super Mario Bros 2 that you can only rent, have a nice day.
And our online service is absolute trash but you’ll pay anyway to have a legal emulator until we also discontinue that for Super other garbage online service!
It does apply to the President. Colorado's judge erred here because they did not have access to Federal documents.
We have the minutes from the 39th Congress that literally indicates that it applies to the President.
Why did you omit to exclude them [The office of the President and Vice President]?
— Sen. Reverdy Johnson (D-MD)
Let me call the Senator's attention to the words 'or hold any office, civil or military, under the United States'
— Sen. Lot Morrill (R-MA)
It was a very specific question that was answered by the Senate while they were discussing it. So Judge Wallace's determination is incorrect on the merits. Judges can be wrong sometimes, that's why we have appeals.
Well the issue at hand is that this is starting to get to the point that like the x86 arch, you cannot just move the NR_CPUS value upward and call it done. The kernel needs to keep some information on hand about the CPUs, it's usually about 8KB per CPU. That is usually allocated on the stack which is a bit of special memory that comes with some assurances like it being continuous and when things go out of scope they are automagically deallocated for you.
However, because of those special assurances, just simply increasing the size of the stack can create all kinds of issues. Namely TLB missing, which one of the things to make CPUs go faster is to move bits of RAM into some special RAM inside the CPU called cache (which there's different levels of cache and each level has different properties which is getting a bit too deep into details). The CPU attempts to make a guess as to the next bit of RAM that needs to move into cache before it's actually needed, this called prediction. Usually the CPU gets it right but sometimes it gets it wrong and the CPU must tell the actual core that it needs to wait while it goes and gets the correct bit of RAM, because the cores move way faster than the transfer of RAM to the cache, this is why the CPU needs to move the bits from RAM into cache before the core actually needs it.
So keeping the stack small pretty much ensures that you can fit the stack into one of the levels of cache on the CPU and allows the stack to be fast and have all that neat automagical stuff like deallocation when it goes out of scope. So you just cannot increase the NR_CPUS value because the stack will just get too large to nicely fit inside the cache, so it'll get broken up into "pages" with the current page in cache and the other one still in RAM and there will be swapping between the pages which can introduce TLB misses.
So the patch being submitted for particular configurations will set the CPUMASK_OFFSTACK flag. This moves that CPU information that's being maintained to be off of the stack. That is to be allocated with slab allocation. Slab allocation is a kernel allocation algorithm that's a bit different than if you did the usual C style malloc or calloc (which I will indicate that for any C programmers out there, you should use calloc first and if you have reasons use malloc. But calloc should be your go to for security reasons but I don't want to paper over details here by just saying use calloc and never use malloc. There's a difference and that difference is important in some cases).
Without deep diving into kernel slabs, slabs are a bit different in that they don't have some of those nice automagical things that come with the stack memory. So one must be a bit more careful with how they are used, but that's the nice thing about the slab allocator is that it's pretty smart about ensuring it's doing the right thing. This is for the 5.3 kernel, but I love the charts that give a overview of how the slab allocator works. It's pretty similar in 6.x kernels, but I don't have any nifty charts for that version, but if some does I will love you if you posted a link.
That said, it's a bit slower but a fair enough tradeoff until there's some change in ARM Cortex-X memory cache arrangement. Which going from memory I think Cortex-X4 has 32MB shared L3 cache, which if you have 8KB on the 8192 CPU max, you'll need 64MB just to hold the CPU bitmap in L3 which is slow compared to the other levels. And there's other stuff you're going to need in the cache at any given time so hogging it all is not ideal. Setting the limit for stack usage to 512 is good as that means the bitmap is just 4MB and you can schedule well ahead of time (the kernel has a prefetcher which things within the kernel can do all kinds of special stuff with it to indicate when a bit of RAM needs to be moved into cache, for us measly users we can only make a suggestion called a hint, to the prefetcher) when to move it all into cache or leave it in RAM. So it's a good balance for the moment.
But Server style ARM is making headway and so it makes sense to do a lot with it in the same way the kernel handles server style x86 and other server style archs like POWER and what not. But not mess with it too much for consumer style ARM, which hardly needs these massive bitmaps.
Musk responded that the advertising boycott is likely to kill the company. "What this advertising boycott is going to do is it's going to kill the company, and the whole world will know that those advertisers killed the company and we will document it in great detail,"
When Sorkin pointed out that advertisers see things differently, Musk replied, "oh yeah? Tell it to Earth."
Sorkin continued: "They're going to say, Elon, that you killed the company because you said these things and they were inappropriate things and they didn't feel comfortable on the platform. That's what they're going to say."
"And let's see how Earth responds to that," Musk replied.
I mean… I think that pretty much removes any last doubt anyone might have had that Elon Musk had any grasp on the reality that he himself exists in.
I’m also nervous about using an OS I’m not familiar with for business purposes right away
Absolutely STOP. Do not go with Linux, go with what you are comfortable with. If this is business, you do not have time to be uncomfortable and the learning curve to ramp up to ANY new OS and be productive is something that's just a non-negotiable kind of thing.
If you've never used Linux, play with Linux first on personal time. For business time, use what you know works first and foremost.
All OSes are tools. You do not just learn a tool when your job is waiting for a bed frame to be made or whatever.
TL;DR
If you are not comfortable with Linux, do NOT use it for business.
Issue 1 covers so much more than just Abortion.
From the ballot:
This is a Freedom of Speech type amendment that centers around a person's reproductive rights. In that this amendment prohibits the Ohio State government from passing any law that restricts a person's reproductive rights except in special cases under strict scrutiny. So this goes way pass just abortion. Additionally, it grants doctors benefit of the doubt protections that would have strict scrutiny bars for the State to overcome, an incredibly high evidentiary bar for the State to overcome.
To just say this protects abortion is really missing the forest for the tree. Yeah, it protects abortion but additionally it protects everything related to reproductive rights (contraception, IVF, etc) and sets a massive barrier for the State to later meddle. This is a massive win for not those seeking abortion but for everyone who cheers reproductive protection and Government non-intervention in such matters.
For hardware folks: Using RISC-V.
Legit, some dude in US Congress is wanting to crack down on China via..... RISC-V exports, because oh no, the technology is too open and might give China some of our IP. Oh and by the way, dude has a pretty big Intel portfolio, but nevermind that!!
As an aside, why the hell are lawmakers allowed to trade stocks?
KDE: Welcome to Linux. Do you like the UI of Windows? Well we have an excellent offering for you if that’s your choice. There’s also other DEs that you may select from if that’s your choice.
Windows: Here’s an ad bitch, fuck your choice.
"The mature and responsible thing to do would have been to add a content security policy to the page", he wrote. "I am not mature so instead what I decided to do was render the early 2000s internet shock image Goatse with a nice message superimposed over it in place of the app if Sqword detects that it is in an iFrame."
I submit the Internet axiom of: there's times and places for a measured and reasonable response, and the other times are funny af.
Let this be a lesson to you—if you are using an iFrame to display a site that isn't yours, even for legitimate purposes, you have no control over that content—it can change at any time. One day instead of looking into an iFrame, you might be looking at an entirely different kind of portal.
Bravo.
Brave Software, the company behind the browser of the same name, was founded by Brendan Eich. He's best known as the creator of JavaScript from his days at Netscape Communications
Say no more fam.
Yes. Twitter was at one point tagging links to Mastodon as "potentially harmful" and removing them.
But the one thing that's been shown consistent about Mr. Musk's ownership of Twitter is that it is consistently self-contradicting. So as Twitter positions itself as "free speech absolutist" one can rest assured that the reality will be "self-contradicting".
Let us not forget that time that Musk said that "Elon Jet Tracker" would not be banned WHILE it was indeed banned. Literally tweeting verifiably false information and then subsequently being called out on it, only for Musk to do the traditional "ignore and move on".
In case you're wondering what the argument is. You should still read the story though.