51–60 of 140 posts
Earlier quoted context omitted.
It's still the finest OS Microsoft ever shipped. ;-)
I seem to recall Xenix ran on an 80286. Speaking of which, did anyone ever end up apologising for the 80286?
Wait. systemd, kdbus, GNOME and systemd-udevd. Shit.
We have met the enemy, and befriended it. Now we are the enemy.
I imagine anything Microsoft releases that could possibly have gpl software, such as the linux kernel in it will have the most aggressive search for violation of any software ever. Memories are long and that distrust is not going away any time soon.
Microsoft has a long way to go before they get the benefit of the doubt from me due to their decades of Embracing Extending and Extinguishing.
Earlier quoted context omitted.
Throughput. The BSD networking stack has been very carefully engineered over time. Linux is OK, but nowhere near as robust. FreeBSD is legendary for load tolerance and network throughput, that on equal machines would choke a Linux server. Seen it, work(ed) with it. When we do something serious that requires heavy load and awesome throughput, we always lean on FreeBSD, never anything else. Everything else has always l…
That was as true ten years ago, is it still? Have there been any recent benchmarks?
The article says "Microsoft will release a custom Debian Linux," but the linked Github repository says: > Q. Is SONiC a Linux distribution? > A. No, SONiC is a collection of networking software components required to have a fully functional L3 device that can be agnostic of any particular Linux distribution. Today SONiC runs on Debian
This article has changed since the last time I read it, minutes ago. It didn't used to have that link, and it used to speculate that the supposed linux distro would be MIT licensed. ...There are several things I don't like about this article.
That doesn't sound very credible of them. The kernel is stuck as GPL; that won't change anytime soon.
In tangentially-related news, there was a lot of talk at NetDev about switchdev, a new Linux driver model for hardware-offload switching hardware. It allows the kernel's Layer-2 and Layer-3 switching/routing configuration to be reflected down into the switch offload hardware, and the switch's ARP and MAC table data to be reflected back up to the kernel stack. The overall idea being you can continue to use the same us…
In tangentially-related news, there was a lot of talk at NetDev about switchdev, a new Linux driver model for hardware-offload switching hardware. It allows the kernel's Layer-2 and Layer-3 switching/routing configuration to be reflected down into the switch offload hardware, and the switch's ARP and MAC table data to be reflected back up to the kernel stack. The overall idea being you can continue to use the same us…
Sounds like the Cumulus Linux approach (they use some daemon called switchd iirc)
- nolan co-founder, CTO @Cumulus
Earlier quoted context omitted.
I seem to recall Xenix ran on an 80286. Speaking of which, did anyone ever end up apologising for the 80286?
Not iirc. But I wasn't around at the time, so nobody told me anything about what was wrong with the 286 in the first place.
The article says "Microsoft will release a custom Debian Linux," but the linked Github repository says: > Q. Is SONiC a Linux distribution? > A. No, SONiC is a collection of networking software components required to have a fully functional L3 device that can be agnostic of any particular Linux distribution. Today SONiC runs on Debian
Porting them to another distribution would be work.
Earlier quoted context omitted.
Not iirc. But I wasn't around at the time, so nobody told me anything about what was wrong with the 286 in the first place.
As I recall, it was mostly that backwards-compatibility with 8086 was so required that they put every useful performance enhancement except raw MHz in a separate protected mode... and then you couldn't switch between protected and real mode without (I am not making this up) asking the 8042 processor controlling the keyboard to hold your beer and reset you, which could take an agonizingly long time.
Also, there was another way of getting the processor back into real mode that was even more fun. You'd initiate a triple fault to trigger the reset, because that was faster than asking the 8042 to do it for you. Oh, the good old days.