Linux doesn't retry the EDID with the video drivers, so for multichannel monitors with the Linux box hooked up to a secondary channel, it won't negotiate the screen settings correctly.
Screen is just another kind of these programs like Vim and Emacs, by which I mean obscure UNIX programs which just hamper your workflow with their clunkiness and extremely awkward keyboard shortcuts. These programs actually have blazing features, but they just throw usability out of window and have a terrible learning curve. Sure, these are command line tools and they are not even expected to be the clicky-click fun multimedia experience, but for example the shortcut to deattach a screen, a very common feature, is Ctrl-A, and after that separately press D. That just shows...no taste at all.
If we decide to not eat it at all (and skip the extra wrapping), I guess it could make for a quickly-decomposing water bottle. Not sure how we prevent it from self-destructing itself while still on the shelf, though...
They released the N900, and that seemed to be what their future plan was before MS got involved.
The Internet Tablets were only a small sidetrack and did not represent their future plan in general.
Nokia was mostly dealing with the crusty Symbian and the competition from Android and iPhone had destroyed them almost completely. That's when Microsoft entered the scene.
They didn't put almost any meaningful resources on the Linux phones, and weren't planning to. Actually they killed all those projects. Also Sailfish is a Jolla OS and didn't exist back then at all.
Nokia's cart was thrusting full speed down the mine shaft when Microsoft made the offer.
Submitter here. I take full responsibility for the mistakes you mentioned. Most of that stuff I simply robotically extracted upstream from the Phoronix article. I did not use more of my time to do a verified, accurate research of the topic. My apologies.
Well, it's open source, so dig in and check yourself... The nasty thing here is that if there is a small jump hidden somewhere, it could start executing the music data and you can hide a lot of malicious x86 code there. But the module itself is only a bit under 200 lines, so it is easy enough to be fully audited by anyone that knows a bit C.
But you know about those, and can fix them if you want.
It just doesn't work like that. You need a lot of time to understand how the program works. Reading individual lines of C code is relatively easy, but understanding how the whole thing comes together, takes a lot of effort. This also means that the group of people who can realistically grasp the code and point out vulnerabilities, is relatively small.
Dear people and fans of open source: please sometimes actually do the experiment where you (yes, you, yourself, anyone can do it, right?) just find and fix even one very trivial bug from an open source project and provably go through the whole procedure leading to a patch to the developer.
Just brainstorming... Would it be possible to create an open source license, which would mostly resemble GPL, but which had an additional clause that would require companies to pay the developers royalties when the code is used for commercial purposes?
Striving for the ultimate portability forces you to make all sorts of fancy wrappers around basic functions. Before OpenBSD now started to fix OpenSSL, there was even a function called get_current_time() which was a wrapper around the classic gettimeofday().
Slashdot Mirror
Linux doesn't retry the EDID with the video drivers, so for multichannel monitors with the Linux box hooked up to a secondary channel, it won't negotiate the screen settings correctly.
Why not?
Screen is just another kind of these programs like Vim and Emacs, by which I mean obscure UNIX programs which just hamper your workflow with their clunkiness and extremely awkward keyboard shortcuts. These programs actually have blazing features, but they just throw usability out of window and have a terrible learning curve. Sure, these are command line tools and they are not even expected to be the clicky-click fun multimedia experience, but for example the shortcut to deattach a screen, a very common feature, is Ctrl-A, and after that separately press D. That just shows...no taste at all.
The problems with high-fat diet is that it is uncomfortable for your digestive system, and simply expensive.
Bull. Real men telnet to Port 80.
Real men realize that "Telnet" is not synonym to "raw connection".
Yeah, it will probably work just fine, but in theory you're not supposed to connect a Telnet protocol client to HTTP protocol server.
In PowerShell:
pkgmgr /iu:"TelnetClient"
If we decide to not eat it at all (and skip the extra wrapping), I guess it could make for a quickly-decomposing water bottle. Not sure how we prevent it from self-destructing itself while still on the shelf, though...
For those of us who're still not using a smartphone, the symbian no-frills mobiles have the best UI and quality than anything else on the market..
That's not quite how I remember it. Symbian was extremely laggy, had a clunky UI, crashed a lot, and everyone hated developing apps for it.
They released the N900, and that seemed to be what their future plan was before MS got involved.
The Internet Tablets were only a small sidetrack and did not represent their future plan in general.
Nokia was mostly dealing with the crusty Symbian and the competition from Android and iPhone had destroyed them almost completely. That's when Microsoft entered the scene.
They didn't put almost any meaningful resources on the Linux phones, and weren't planning to. Actually they killed all those projects. Also Sailfish is a Jolla OS and didn't exist back then at all.
Nokia's cart was thrusting full speed down the mine shaft when Microsoft made the offer.
Maybe, but Nokia would still have ended up in a far worse situation without the Microsoft deal.
My goal will be to make it heavyweight, unstable, slow-running, and compliant with nothing!
I cringe how much that sounds like Unity. ;)
Submitter here. I take full responsibility for the mistakes you mentioned. Most of that stuff I simply robotically extracted upstream from the Phoronix article. I did not use more of my time to do a verified, accurate research of the topic. My apologies.
This is going to be something like KDE, as that is what Lumina will be replacing.
On the other hand, LXDE is also being rewritten to be Qt-based, so that will probably be something along the same lines.
Well, it's open source, so dig in and check yourself... The nasty thing here is that if there is a small jump hidden somewhere, it could start executing the music data and you can hide a lot of malicious x86 code there. But the module itself is only a bit under 200 lines, so it is easy enough to be fully audited by anyone that knows a bit C.
I thought releasing it as a kernel module would make it cross user-space and kernel-space less often?
Uhh yeah, fixing security bugs is likely to be even harder than fixing trivial bugs.
But you know about those, and can fix them if you want.
It just doesn't work like that. You need a lot of time to understand how the program works. Reading individual lines of C code is relatively easy, but understanding how the whole thing comes together, takes a lot of effort. This also means that the group of people who can realistically grasp the code and point out vulnerabilities, is relatively small.
Dear people and fans of open source: please sometimes actually do the experiment where you (yes, you, yourself, anyone can do it, right?) just find and fix even one very trivial bug from an open source project and provably go through the whole procedure leading to a patch to the developer.
Why not?
Just brainstorming... Would it be possible to create an open source license, which would mostly resemble GPL, but which had an additional clause that would require companies to pay the developers royalties when the code is used for commercial purposes?
If you suck at a sport, pick another.
Or keep practicing until you get better.
The angry AC strikes again...
You are absolutely correct.
A chocolate bar wrapper.
Microsoft OneNote.
Done.
Striving for the ultimate portability forces you to make all sorts of fancy wrappers around basic functions. Before OpenBSD now started to fix OpenSSL, there was even a function called get_current_time() which was a wrapper around the classic gettimeofday().