Re: Another problem of a monolithic monster kernel
Given today's CPU architectures (multi-core) this can even be beneficial, as you don't need a context switch (another thread can pick it up right away).
540 posts • joined 22 May 2018
But you need the whole calabash of sources around and then the interface changes once more and you're *ucked.
I went through that while building VMware patches. You always needed the fitting version, otherwise you'll get errors. Eventually I just gave up on VMware. In other words, you have to maintain it and check if it still works and build it anew with every new kernel release. That sucks and is the main reason for having so many IOT devices with ancient kernels (and tons of security issues) around.
That's just another problem of the monolithic monster kernel.
Typically, people start small. They have to get used to the process. With Linux there is just a landslide of things you have to know before you can get started. Consequently, almost nobody ever manages to jump that hurdle... :-(
This post has been deleted by a moderator
... and becoming immune.
As Corona viruses tend to mutate rather quickly, it is noteworthy that the level of immunity achieved this way is MUCH higher than that of a potential vaccine. These people are, henceforward, immune to this disease; they can't spread it either.
After nuking (flushing) L1, there's really not much room for "more security". Next up: disable the cpu clock!
Let's face it, Intel CPUs are broken by design (cheating on correctness & security for more performance). They want to get home. Let's send them there and demand the money back. ;-)
Some "attacks" never took place, i.e. they were staged completely. In others the “friendly opposition” (ISIS and Al-Qaeda affiliates) used chlorine gas, while pretending that the government hat attacked the population with Sarin nerve gas, though.
Back in the days when the Amiga was designed, CPUs didn't have a "memory management unit".
Today, every program gets its own virtual address space. Therefore, every program can pretend that it is located at a fixed address. It cannot access the address space of other programs (processes). They themselves can believe to be located at the exact same address and it doesn't matter as they don't interfere.
In order for programs to work together in a multi-tasking environment, unlike DOS where only one program could run at a time, they had to be "pc-relative". "pc" stands for program counter. It's a register of the processor that determines the position of the current instruction. When your program got loaded and executed, you had to access your data relatively to the program counter (that is, relatively to where in the address space your program was loaded into).
Say, your program's start address was at 0x0000. Say the data was located at 0x0100. Now, if your program was loaded into address 0x2000, then your data was located at 0x2100 (for simplicity I used 16-bit addresses, though the 68k used 32-bit).
By accessing your data relatively to the pc-register, your programs became independent of the memory locations they were loaded into.
Some idiots never managed to program properly. Their programs were always accessing fixed addresses (most demos, for instance). If there was something else at those addresses - boom!
As has already been previously stated, the SCSI implementation was broken. Likely, some idiot forgot a fixed address somewhere. By running the clock first, you allocated a certain address space, guaranteeing that whatever came afterwards was pushed further up in memory.
I feel the obligation to tell the people that ZFS is only useful on dedicated file-servers (as Ubuntu is unlikely to be used for those). Some people read the specs and decide to run ZFS on their desktop systems. That is stupid in many ways. Do yourself the favor and don't.
This is standard practice. There's a demonstration with thousands of people demanding better payment? Throw in a few people, who then set cars and shops on fire while yelling that Satan is their master. Soon people will dissociate themselves from the movement.
This is somewhat exaggerated, but in core how it is effectively done.
*"for your own protection", a.k.a. don't question anything we do or blame on COVID-19
*errm*?!? Your SmartPhone can be taken over via the driver BLOBs. There are also many other ways to take it over, as Android is a security nightmare with the media-framework being constantly vulnerable to remote attacks.
If you think that running the latest Android and only downloading approved apps from the PlayStore gives you security, you are very naive.
> Other allegations include a Huawei staffer creeping around a trade show in the middle of night and removing covers from networking gear in order to photograph the circuitry inside.
This sounds like something to someone who doesn't have a clue of today's technology. It would have worked in the 70's or 80's, maybe. Today, those circuits come on boards with several layers. A photograph from the top, typically, doesn't give you much.
> Another engineer is accused of sneaking into a rival firm’s lab in order to pinch a robot arm used for testing mobile phones. The robo-arm was measured and photographed before being returned, the US claims.
This is the old Telekom accusation. A German tech-media site (Heise) commented on this, that they had built such a device themselves with little trouble. Students can do this in a few days. The accusations are ridiculous.
The source is a certain "Dana Rohrabacher" and not Assange. Rohrabacher is a republican member of congress, who has been known for lying through his teeth for decades now. Amongst other things, the human turd is an admirer of Putin.
The BND is just a GERMan speaking CIA outlet. They helped them to start the war against Iraq, by torturing an Iraqi until he told the lie they want him to tell (see: “Curveball”). They started the war in Sudan for the US, by delivering tanks and other weapons to both sides - “rebels” and government (see: “We’re Going to Take out 7 Countries in 5 Years: Iraq, Syria, Lebanon, Libya, Somalia, Sudan & Iran”). They have been spying on their own (strongly forbidden) for the US. All to no avail.
So this is why Huawei is so evil, eh?
Another reason being the old hardware's specs, of course. A device with 8 cores, 8 GB of RAM and 256 GB flash (hard disk), would have been considered a mainframe not so long ago.
It has become hard to slow down such machines. Even the most inefficient of software rarely manages to hog so much RAM or processing power. Therefore, you can safely keep the old, as there's not much of a difference anyhow. ;-)
That's the real culprit:
> execle("/bin/sh", "/bin/sh", "-c", mda_command, (char *)NULL, mda_environ);
The issue here is "the typical Unix problem": Programs are starting other programs to do things. The correct approach would be putting the code in libraries. The shell commands would then only be handling the command-line options, passing them on to the library. Programs could use the libraries "as part of their code". This is the safe way. This is the efficient way. But they never learn...
And it did so we with help of German goons, remember?
Curveball - the guy who got tortured by the BND (German CIA) in order to provide the lies:
"Ex-spy chief says BND 'misused' for Iraq War"
They know that this falls on fertile ground. That's why they "approached" the Germans to begin with.
If you are thinking about reporting bugs and adding code – don't.
I did report several bugs, sometimes proposing fixes. I got insulted, and even bugs marked as critical, which would cause the entire QtCreator installation to become unusable, were ultimately ignored.
I don't know what is going on there. They have too little personnel? They might have overstretched (3D and whatnot)? They might have issues with getting enough cash in? I don't know. All I know is that the people there appear to be stressed “beyond repair” and they pass this on whenever you get in contact with them.
I dropped Qt a while ago when I noticed that things were only getting worse instead of better (i.e.: I found the bugs in their code mostly and thus couldn't repair things. I found myself avoiding Qt functionality wherever possible and using it for the GUI only. This increasingly sucked, though.).
Biting the hand that feeds IT © 1998–2020