You’re practically not supposed to to build external modules. It’s supported to only the most minimal degree- Linus, and the Linux project, WANT you to build things in.
And as everyone else has told you, this is so that support for hardware is in Linux and in distros BEFORE users have to taint their kernels and create crazy bugs kernel devs have to deal with.
Only if you adhere to their standards, until very recently you couldn't even do rust. If i made something fully working in rust today it still wouldn't get accepted.
No it isn't. The reason you can't write external modules is because the kernel interfaces aren't stable. You would have to provide a module binary for every single kernel version (and maybe even for different configurations).
And the reason for that is mostly that providing a stable interface is a) a ton of work, and b) would make distributing closed source drivers easier which is something Linus hates.
if you read the mailing list, you know there’s a lot of reasons. Linus hates out of tree and closed modules for quite a number of reasons- but in this specific context it seems the most relevant.
800M is 10% of the current population - the OP's point is that if he's right, there's a non-trivial chance that he, and you, may be dead, making the prediction moot.
In terms of EV, it never pays to bet on the apocalypse since you can't collect. Markets can't price in their own demise. (it would actually be quite interesting if they could).
(Also, given how often people make predictions online, how often do you see people saying "mea culpa, I was totally wrong about that one!" It's close to zero. Guessing wrong, even in earnest, about important things, doesn't matter anymore, and doesn't pose even a minor threat to one's reputation. This lack of social/cultural corrective has made our zeitgeist is so remarkably polluted with utterly ignorant, bad faith BS like bets about the apocalypse that it doesn't even register any more. How fascinatingly horrible!)
EDIT: I just don’t trust promises for things to be open source. Notch said Minecraft would be open source, and look where that went. A promise let’s you skip out on releasing the code if it turns out to be a convenient or profitable options.
> They aren’t (and do not) require any privleged system calls, whatsoever.
You're making a distinction about 'privileged' system calls, why, exactly? You really think something like Oracle won't require access to a ton of syscalls to work correctly?
> If you can actually exploit a system call, neither a MAC based approach or a pledge will help.
> System call filtering isn't a sandbox. It provides a clearly defined
mechanism for minimizing the exposed kernel surface. It is meant to be
a tool for sandbox developers to use. Beyond that, policy for logical
behavior and information flow should be managed with a combination of
other system hardening techniques and, potentially, an LSM of your
choosing
I've used it. I know what it does. For a while, I've even run a linux with a slightly patched version of it for some quirky needs of my own.
seccomp-bpf is a more fragile version of pledge; you need to keep changing your sandbox whenever you upgrade glibc, because there's no mechanism to keep syscall usage in sync between the kernel and userspace.
It was fine for my case, because I was implemeting my own direct system calls, and froze any external dependencies, but it's typically very fragile across system and dependency upgrades.
The scientific consensus is that children need more sleep than theyre getting, and that waking up later is healthier. I assume this problem is the same in most parts of the world.
in the article: „And around puberty, their circadian clocks shift by a couple of hours, meaning they get tired later at night than before and wake up later in the morning than they used to. This shift reverses at adulthood.“
I agree with you somewhat that there is some personal responsibility required here, but I disagree that the answer here is so simple as going to sleep earlier.
>I agree with you somewhat that there is some personal responsibility required here, but I disagree that the answer here is so simple as going to sleep earlier.
I think this is where I'm at. I know its entirely possible to sleep earlier with lifestyle changes. I spent a summer at my grandparents with no wifi, tech etc and going outside to play, I was so bored but damn if that wasn't the best sleep I ever had in my life, lol... and early too, never more than 10 PM.
I'm just worried if we start later and later, it could keep creeping up until you have no reasonable time left to start later. I suppose experimenting with it couldn't hurt though.
Did the article cite the source for this and maybe I missed it? It says a lot of things and "countless studies" but curiously doesn't list all of them.
Its more than just rebelliousness. Teens' circadian rhythms are naturally shifted towards falling asleep later in the evening and waking up later in the morning.
The cicadian rhytm doesn't actually know what the clock on your wall says, only when you eat and get daylight. A late cicadian rhytm is functionally equivalent with poor sleep hyhiene.
And when other people are active. It seems to be fairly common that night owls need an hour or two of their own time after most other people have gone to sleep, or at least have stopped bothering them.
That era marked the lowest level of competition in CPU performance and it really showed in terms of how relatively lame an upgrade with the leader of the time (Intel) was. With AMD's products being competitive and ARM CPUs no longer being relegated to smartphone class performance there is real competition again. Given that and the historical tendency that software grows to use the available hardware I wouldn't bank on every CPU upgrade lasting as long as they did in that period.
But damn if it hasn't been hard to get a good deal on a GPU these last couple of years...
It shows on iTunes for PC just fine. I have confirmed in another reply in this thread that I was able to see the DRMd podcast episode posted by @bastawhiz on PC, but I was not able to download it.
And as everyone else has told you, this is so that support for hardware is in Linux and in distros BEFORE users have to taint their kernels and create crazy bugs kernel devs have to deal with.