Readit NewsI think it was MS Access 2.0 that had some text on the back about being up to 100x faster than the previous versions, and to me that reads as "old was crap as hell", but some marketing person thought that was a super quote to put on the packaging. Perhaps it works, perhaps not.
Lets take the pilot walking at the start of Raid over Moscow, it was super well animated and designed for the sprite limitations a C64 has, but I am not so sure it would be upscaled to represent a walking pilot, since some of the oddly placed pixels might grow into something vastly different.
Lets take the pilot walking at the start of Raid over Moscow, it was super well animated and designed for the sprite limitations a C64 has, but I am not so sure it would be upscaled to represent a walking pilot, since some of the oddly placed pixels might grow into something vastly different.
Yup, still the case today.
Currently with an SSD, when there’s a power cut, there’s about a 20% chance my router will require me to walk downstairs and plug in a keyboard, type “fsck” manually and press y at all the prompts.
I haven’t actually had any issues with noticeable data loss though.
I’d settle for a default “boot anyway, press y for all fsck questions” mode on boot. I just don’t want to have to physically touch the thing.
> I’d settle for a default “boot anyway, press y for all fsck questions” mode on boot. I just don’t want to have to physically touch the thing.
Look up where fsck is run in /etc/rc and add the -y there.
I wonder how useful this will be for the modest but still multicore systems used for firewalls.
Then again, the sentence "tcp is outside of global lock" is very generalized, there are so many parts that got out of the kernel lock in pieces, like ip input, routing lookups and device packet handling that it is hard to talk about it as one singular thing that you just flip a switch on to make it MP-performant.
You could make filesystem code mp, disk device drivers mp and then still run on an IDE-disk which forces all IO to be one at a time and serialized first-come-first-served at which point all the work was for 'nothing'.
Same goes for networking, there are many many layers and places that all need code that actually allows for MP processing to improve its performance, fine grained locks (which reduce perf at this stage), then prove that the fine grained locks are sufficient for ALL use cases, all kinds of layering violations that could possibly happen, then you can unlock this single layer, and move to the next if nothing acts up on any machine.
) https://www.youtube.com/live/wEM-E-IJ6sY?si=X3lLX9tEIO2mcEJl...