|
These days it is easier to just jump in your car and drive it through the front door of your neighbors house that you don't like.
Of course just like the ol' days much smarter of you to convince another neighbor that you don't like to drive their car. So you take out two at once.
|
|
|
|
|
Yes.
Will Rogers never met me.
|
|
|
|
|
Yeah, it's the non forbidden version of the ballista.
You can fire boulders at your enemy, just not missiles made of entire trees. Some pope forbade it. Imagine, a huge crossbow on your ship, capable of firing a tree that been cut as a missile.
A trebuchet is a long shot, yes. Just less effective.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
|
Wordle 812 3/6
⬛⬛⬛⬛⬛
⬛⬛⬛⬛🟨
🟩🟩🟩🟩🟩
That was interesting.
|
|
|
|
|
Wordle 812 5/6
⬜⬜⬜⬜🟨
⬜🟩⬜⬜⬜
⬜🟩⬜⬜🟩
⬜🟩🟨⬜🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Ironical
|
|
|
|
|
Wordle 812 3/6*
⬜⬜⬜⬜⬜
⬜🟩⬜⬜🟨
🟩🟩🟩🟩🟩
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
🟨⬜⬜⬜⬜
⬜⬜⬜🟨⬜
⬜🟩🟩⬜🟩
🟩🟩🟩🟩🟩
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
Wordle 812 4/6
⬜🟩⬜⬜⬜
🟨⬜⬜⬜⬜
⬜🟨⬜⬜⬜
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 812 3/6
⬛🟨⬛⬛⬛
🟩⬛⬛⬛⬛
🟩🟩🟩🟩🟩
Ok, I have had my coffee, so you can all come out now!
|
|
|
|
|
Wordle 812 3/6
🟨⬛⬛⬛⬛
⬛⬛⬛🟨🟨
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 812 3/6
⬜🟨⬜⬜⬜
🟩⬜⬜⬜⬜
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 812 4/6
⬜⬜⬜⬜⬜
⬜🟩⬜⬜🟩
⬜🟩🟨⬜🟩
🟩🟩🟩🟩🟩
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
#Worldle #595 1/6 (100%)
🟩🟩🟩🟩🟩🎉
https://worldle.teuteuf.fr
easy
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Windows XP and it’s predecessors did pretty good at recovering when an application went kaboom, however once every two or three application crashes the OS went down together with the app.
Multithreaded Windows is tougher, you probably can’t crash the OS even if you give it a try. Both 32 bit and 64 bit OS share the RAM with the app, the common dwelling means that the app can overwrite critical OS data, running on a separate thread shouldn’t make a difference. Does the 64 bit OS have some kind of memory backup in case things go wrong?
|
|
|
|
|
I would think that apps and OS run in their own virtual memory spaces, making it virtually (no pun intended) impossible for a non OS process to mess with OS memory space. Add to that different process execution rights, with user apps having no right to mess with OS memory, then the probability of a user application causing a crash by altering OS RAM contents approaches zero.
Keep Calm and Carry On
|
|
|
|
|
k5054 wrote: user apps having no right to mess with OS memory
This. User space vs kernel space. Drivers might still overwrite critical OS data, as they share memory with the kernel (that's why BSODs still occur), but a user-mode application should no longer be able to do that like they did back in the Windows 3.x/9x days.
|
|
|
|
|
That all falls apart on embedded when you're dealing with primitive memory protection schemes and an RTOS at best.
I was just dealing with a buffer overrun this morning.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Granted, but this thread was started discussing Windows only, which tries a lot harder protecting itself than embedded systems.
|
|
|
|
|
It's the goal that is basically unreachable for Windows as well and I think Linux has to necessarily be limited in how much better it can be in that regard.
At some point you're talking hardware and any OS is going to have the same problems/limitations.
I probably read about it from an article on here, but pretty much every modern Intel processor will give you whatever memory you want, maybe even let you write it (I can't remember), and they say you can patch this... I've no idea how you possibly patch this. Apparently, applying the patch can reduce performance by 50%.
IMO, some of these expectations of user vs kernel memory space are simply out of whack with the realities.
The whole TPM windows 11 debacle is kind of a highlighter pen at the heart of why expectations in this regard are misaligned with reality.
The hardly-oversimplification is that something, somewhere has to be the authority of what's right/ok. That authority essentially builds the walls to delineate user vs kernel memory. Right now, this is pretty much software with not so much hardware involvement aside from some limited specific things/use cases.
Maybe over the next decade we'll actually see things built at the hardware level that enable this to happen instead of just basically faking it at the software level. I think this will require something like FPGAs being able to dynamically build the interfaces between CPU and RAM for the application/software on demand (while also verifying against security permissions whether the structure should be allowed).
|
|
|
|
|
Don't forget the ring protection. Drivers are not supposed to run in ring 0.
|
|
|
|
|
That is kernel mode (ring 0) vs usermode (ring 3), no?
|
|
|
|
|
(Most) drivers are supposed to run in ring 1 or 2 - call that "driver mode" if you like.
I guess that the OS kernel has some central drivers of its own running in ring 0. The borderline is fuzzy between drivers and code for manipulating CPU resources (such as the interrupt system or MMS). The OS may trust itself. It should not trust "foreign" drivers, e.g. those developed by manufacturers/vendors of "foreign" peripherals, to run in ring 0.
|
|
|
|
|
What (admittedly little) exposure I've had to this had led me to conclude that, for all practical purposes, there was no such thing as Ring 1 and Ring 2, at least when it comes to Windows. I think Mark Russinovich even said so himself, but don't quote me on that.
Although it does make sense that this is where drivers ought to live.
|
|
|
|