Toughen up /s
I vaguely recall reading something about some of their departments were not even using the floppy. Like you had to submit with a floppy, but it was never actually written or read from, and you supplied the documents another way. (I could have entirely made this up, don't quote me)
The DNS risk is not mitigated by a VPN, just shifted.Your VPN has full ability to log your connection if they wish. You have to decide who you trust more. Bear in mind that depending on your location, your ISP may be more legally restricted from snooping on you than a VPN hosted in another country (I know nothing about the US laws, further research would be required).
Also, unless you are using one of the encrypted DNS variants, just changing your DNS provider does nothing, as the ISP or VPN can snoop the unencrypted traffic regardless of its destination.
Its only a genocide if it comes from the third reich. Anything else is just sparkling ethnic cleansing.
To be fair, we only know of this one. There may well be other open source backdoors floating around with no detection. Was heartbleed really an accident?
I knew the trans agenda was to get rid of bridges. Wakeup sheeple!!!2!!?
Some might be paid actors, but i bet a lot are just brain rotted morons.
That kinda sounds reasonable. Especially if it can prevent someone going down that rabbithole? Good job PH.
Im not a lawyer, but is this really good news? Isnt this just setting a precedent that Nintendo can shake down any emulator developer for ~2.4m any time they feel like it? So small developers are basically screwed?
Everyones getting called back to the office :D
It is actually a boot failure. Normally the kernel reads some config from the initrd (the bootloader loads initrd and passes it to the kernel - thanks dan) and then does a bunch of setup stuff, and then it mounts the actual root filesystem, and then switches to using that. In this case, the root filesystem has failed to mount.
Hardware failure is most likely the cause, but misconfiguration can also make this happen. Probably hardware though.
If its misconfiguration, an admin can reattempt to mount the root drive on /new_root, and then ctrl-d to get the init system to try again
ELI5: couldnt open C:/ drive
Edit: clarified what loads the initrd - as per dans comment.
I think its better to think of it like a president or prime minister. He might set the plan and direction and making the big decisions, but there are thousands of others supporting and making the plan actually happen.
In the past he has delegated the release to others as well.
So if the worst would happen, the linux project would continue operating fairly seamlessly.
Zombie processes are already dead. They aren't executing, the kernel is just keeping a reference to them so their parent process can check their return code (
waitpid
).All processes becomes zombies briefly after they exit, just usually their parents wait on them correctly. If their parents exit without waiting on the child, then the child gets reparented to init, which will wait on it. If the parent stays alive, but doesn't wait on the child, then it will remain zombied until the parent exits and triggers the reparenting.
Its not really Linux's fault if processes don't clean up their children correctly, and I'm 99% sure you can zombie a child on redox given its a POSIX OS.