Anyone actually measured this? I see a lot of bandwidth/etc style tests but few that can show the actual impact of enabling disabling deep packet inspection and a few of the other metrics that I actually care about. Serve the home seems to have gotten some fancy test HW but they don't seem to be running these kinds of tests yet.

His early stuff contains some real masterworks. Hyperion is still to this day, going to show up at the top of my scifi recommended reading list, most of his horror novels were also great in their own ways.

PS: I thought Fall of Hyperion should have been the end, it was just too final. There was plenty of space for some prequels but while the sequels contained some interesting ideas, they just never got to the level I felt justified reversing the finality of Fall. And Olympus/etc was pretty forgettable, but I don't regret the time I spent reading pretty much everything he wrote, sometimes more than once. So again, RIP.

OTOH, most states have a stay right except to pass, slower traffic keep right laws.

Which means, that unless the person to your right is weaving through traffic, driving on the shoulder, or a few other bits of unsafe behavior, if someone passes you on the right your likely the one violating the law by not moving right when your not actively overtaking/passing someone.

In Austin if you want to merge, decide if you can, blink and then merge.

Don't expect people to stomp on their brakes and stop to let you in, especially if your already traveling slower than the lane you are trying to get into and decide to further slow yourself.

And if you can't merge, deal with it, exit, or miss your exit and go around. Next time you will be more prepared or you will learn how to properly merge.

Thats not a constitutional democracy, thats just anarchy and rule by whoever can buy the most seats.

Put another way, Writs of Assistance, were perfectly legal common sense way for the British government to assure their customs laws were being enforced, and it was one of the more significant drivers of the revolution.

The airlines don't even check ID most of the time with these electronic boarding passes if your not checking luggage.

Bush should have _NEVER_ nationalized them, at least as a private entity they existed in a sorta gray area. Now they are clearly violating the 1st, 2nd, 4th, and 10th amendments.

And the solution isn't another bullshit supreme court amendment of the absolutist language in the bill of rights/etc but to actually have a national discussion about how much safety the are providing vs their cost, intrusiveness, etc and actually find enough common ground to amend the constitution. Until then they are unconstitutional and the court makes a mockery of itself and delgitimizes then entire apparatus in any ruling that doesn't tear it down as such.

And before anyone says "oh thats hard", i'm going to argue no its not, pretty much 100% of the country could agree to amend the 2nd to ban the private ownership of nuclear weapons, there isn't any reason that it shouldn't be possible to get 70% support behind some simple restrictions "aka no guns, detected via a metal detector on public airplanes" passed. But then the agency wouldn't be given free run to do whatever the political appointee of the week feels like. But there are "powers" that are more interested in tracking you, selling worthless scanners, and creating jobs programs for people who enjoy feeling people up and picking through their dirty underwear.

Frankly, 10Gbit is fully 25 years old with, 10GbaseT being 20 years old this year.

Thats ridiculously ancient technology. There is/was a 25/40GbaseT spec too (now 10 years old), which basically no one implemented because like ECC ram (and tape drives, and seem to be trying to do it with harddrives and GPUs) the MBA's have taken over parts of the computer industry and decided that they can milk huge profit margins from technologies which are incrementally more difficult because smaller users just don't matter to their bottom lines. The only reason those MBAs are allowing us to have it now, is because a pretty decent percentage of us can now get 5Gbit+ internet access and our wifi routers can do 1Gbit+ wireless, and the weak link is being able to attach the two.

I did a bit of back of the napkin math/simulation about a possible variable rate Ethernet (ex like NBbaseT, where it has multiple speeds and selects faster one based on line conditions), and concluded that 80+Gbit using modern PHY/DSP's and high symbol rate, multiple bands, techology which is dirt cheap thanks to wifi/bt/etc on fairly short cable distances (ex 30-50M) on CAT8 is entirely possible. And this isn't even fantasy, short cat7 runs are an entire diffrent ballpark from a phone pair, and these days mg.fast/etc have shown 10Gbit+ over that junk.

That seems an odd interpretation of how they extended the 286 protected mode on the 386. The 286 converted the fixed address+64k sized segment registers to 'selectors' in the LDT/GDT which added permissions/etc to a segment descriptor structure which were transparently cached along with the 'base' of the segment in generally invisible portions of the register. The problem with this approach was the same as CHERI/etc that it requires a fat pointer comprising the segment+offset which to this day remains problematic with standard C where certain classes of programmers expect that sizeof (void*) == sizeof (int or long).

Along comes the 386 with adds a further size field (limit) to the segment descriptor which can be either bytes or pages.

And of course it added the ability to back linear addresses with paging, if enabled.

Its entirely possible to run the 386 in an object=segment only mode where each data structure exists in its own segment descriptor and the hardware enforces range checking, and heap compression/etc can happen automatically by simply copying the segment to another linear address and adjusting the base address. By today standards the number of outstanding segment descriptors is limiting, but remember 1985 when a megabyte of RAM was a pretty reasonable amount...

The idea that someone would create a couple descriptors with base=0:limit=4G and set all the segment register to them, in order to assure that int=void * is sorta a known possible misuse of the core architecture. Of course this basically requires paging as the processor then needs to deal with the fact that it likely doesn't actually have 4G of ram, and the permissions model then is enforced at a 4K granularity. Leaving open all the issues C has with buffer overflows, and code + data permissions mixing/etc. Its not a better model, just one easier to reason about initially, but then for actual robust software starts to fall apart for long running processes due to address space fragmentation and a lot of other related problems.

AKA, it wasn't necessarily the best choice, and we have been dealing with the repercussion of lazy OS/systems programmers for the 40 years since.

PS: intel got(gets) a lot of hate from people wanting to rewrite history, by ignoring the release date of many of these architectural advancements. Ex the entire segment register 'fiasco' is a far better solution than the banked memory systems available in most other 8/16 bit machines. The 68000 is fully a year later in time, and makes no real attempt at being backwards compatible with the 6800 unlike the 8086 which is clearly intended to be a replacement for the 8080.

And its not like actual flaws people found couldn't be fixed.

There is a word for this.

Is the security extension from 1996, which has a section on keyboard security

and its crazy to me that this anyone can claim X11 can't be off loaded, which its been doing for decades. From all the crazy blt/pattern HW acceleration to GL/vulcan implementations to the fact that the entire server can be on the other side of a network pipe, meaning it could be anywhere, including entirely encapsulated on a graphics card/smart nic/etc.

And if your talking about the xlib serialization, that was largely fixed with XCB.

Notice the date.. 1996

(for those that didn't click the link, that is the X11 security extension which address all that, and it was published ~30 years ago).

One head strictly stuck in the ground and ignoring the cases that make many of those statements flatly false. Like for example, the nvidia support. Nvidia support in Linux is in the 'good luck' catalog, especially on any optimus laptop, where one is lucky if the power management works, much less multiple screen docking/undocking, and a heap of other issues. Then please clarify which actual driver stack one is running (nouveau vs provide by nvidia binaries, vs nvidia open source) To claim its great with wayland ignores core failures that still exist.

Its the same with X11 forwarding, which like copy paste, has been steady degrading to the point where all the dbus/etc services being depended on makes double digit percentages of applications not work with 'ssh -X' and oh wow, waypipe. It seems all of windows/osx and KDE/Gnome are steadily shooting themselves in the foot.

I'm sorta happy I pulled my financial support not long ago, there are a couple 'toxic' people in the distro DE community who are pushing their own agendas, everyone else be damned. And weirdly enough it seems those people aren't doing it for some corporate/whatever reason, but just to wave a flag about their accomplishments. The entire reason most people claim wayland is 'better' is largely FUD, but that doesn't stop the true believers.

Which is a load of FUD, the X11 security extensions from (checks google) 1996, restrict this.

If you flip a bit in memory, on the way to the disk, then its corrupt at rest, and future reads will likely propagate the error.

Sure, who cares, a glitch here/there in your kids first birthday video. Better hope the glitch is there, rather than in say the bit of code computing the sector offsets/whatever.

Stories like this hit the media every couple years, so if it can happen on the big fancy EMC/whatever then it can happen on your little NAS in the closet.

So, just pay the little extra for the CPU+MB+RAM that protects your data from the NIC all the way to the HD.