Post a Comment
My favorite was the floppy demo - an entire graphical OS with web-browser, tcp-ip, file manager, etc. that ran off of just a floppy. It wowed me. Unfortunatley, I didn't have the same experience trying to install it on my laptop - just not enough general hardware support. I really wish someone would run with it as a desktop, but the market is just too crowded for that. I, too, really like the micro-kernal concept. Maybe Minix will rise up and rule them all!! [Halloween laugh ensues]
[EDIT: grammar]
Edited 2008-10-31 21:54 UTC
I can't help but wonder how computers would be different if QNX desktop had taken off.
Insanely fast, insanely small - (looked quite good too I remember)
I look at my pc now. 2gb ram 160hd and my 8gb windows folder and how p1ss poor slow my pc is (running vista) and wonder where it all went wrong!
I swear to pseudo-god, their site is hard to navigate.. I like everyone else, have tested the old floppy release. (And the old Unisys ICON family), but I dislike how fragmented and confusing their website is.
They have so many products that share the same name, they have "hosted" versions of the OS that I would assume install only a SDK or a version of QNX in a virtualization environment.
They also have a native version, which is hard to find.. and when you do find it, you need a serial code... or not.. for non-commercial uses.. if you find yet another image buried somewhere else.
Why is it so confusing? what does one do if they simply want to boot the damned OS on a run-of-the-mill beige box x86 PC?
To conclude, definitely a worthy release day... scary is a perfect way to describe their website.
Thanks QNX, we miss you.
Edited 2008-10-31 23:49 UTC
The mobile phone (cell phones for you Yanks) sphere really lacks good OSes. There are a few good ones, but really few, and a good graphical user interface layer on top of QNX could have made a really really stable mobileOS. Heck, it could still happen. The vast majority of the devices out there run really crappy stuff.
Now hop to it and develop it 
Here's eQip.
http://eqip.openqnx.com/?D=screen_shots
Uses PhotonUI, iirc. Nice stuff.
not sure he was talking about this one :
http://www.youtube.com/watch?v=yTUweJKAUfk
ps : i have to admit, it's surprisingly quick..
Edited 2008-11-01 01:28 UTC
Thanks for the link.
Note that they said that the BIOS was checking the memory and their application didn't: memory check take the majority of BIOS time on my computer so the comparison is biased.
That said, I agree that BIOS shouldn't test memory by default: it should be the job of the OS to check memory continuously (when plugged for laptops) to report potential memory issue.
I agree. The weird thing is on my new P5Q motherboard, the BIOS seems to take an eternity, whereas the HP I have at work just flies through it.
My BIOS takes a good 15 seconds to boot. I've tried trimming it down, but it doesn't help much.
Linux itself usually boots in about 20-25 seconds. Windows Vista takes forever and a day...
But for all those crackheads that want their computers to boot into their OS fast, shouldn't we have trimmed down Bioses? Hell, Windows half the time doesn't pay attention to Bios settings anyhow.
I knew a guy who originally had an all SCSI system, and so he disabled the IDE devices inside his PC so that they wouldn't sit there and scan for them (the SCSI card took long enough by itself) and when he added a DVD burner to his setup, forgot to re-enable the IDE. So when he burned things it'd take 8 hours to burn! But Windows said nothing. It just saw the device as if it was enabled and went for it.
I laughed really hard at him because he hadn't thought about going into the BIOS to fix it. In essence it was one of those "When are you going to come over and fix it for me?" and months later, I finally got around to it and fixed it in less than 5 minutes.
problem is, the BIOS does not spend as much time on pure cpu based computations as on device (PCI cards, storage devices) scan, and initialization loops (that are executed serially)
moreover, delays and timeouts are introduced in routines that detect devices that may not be available or may need some time to become so - think of a HDD taking some fractions of a second to spin up
I have spent this morning reading the technical documents describing the architecture of QNX.
I am really impressed with QNX! The messaging system that is the basis for the entire operating system is well developed. They have been successful with creating a POSIX OS with an effective microkernel design whose performance is comparable to monolithic kernels. I don't think MINIX could compete with QNX when it comes to performance. QNX is far more elegant than the Linux kernel.
I can't get behind QNX any more. I got burned for choosing them for an old project years ago. The kernel was good, but the problem is like every other closed source OS where you become completely reliant on few developers to extend the platform. Think of all of the resources that MSFT can throw behind Windows Mobile, that Nokia can throw into Symbian. QNX probably has less than a quarter of the developer resources. Try to get an embedded browser with an up-to-date Flash plugin, Skype, Divx or other apps and extensions. That's the bottleneck, and will always be 2 generations behind the most useful stuff.
Linux boots fast too - easily under 5 seconds straight into Mozilla, when it's configured correctly. That guy was also booting off of a flash drive, which takes considerably less power and time to boot. Yes, I can back this up.
Sir,
You can not boot any operating system in less than 3 seconds. I have tried three times telling it to the Developers, once on /. and twice on planet Ubuntu and planet Gnome. I got put down very fast and crudely. They are just happy to be perfect with their shitty optimization to be able to boot in less than 30 seconds on common hardware. I call that 1 second startup from the video a hoax!
Also, I call 5 seconds on Linux a hoax. I was told by so magnificent, omnipotent, and Developerish developers that I can not question what they told me!
Ok, enough of irony. No operating system really should boot for 5 seconds to a complete desktop environment. Or 3 seconds. 2 seconds sounds more like it. a) There simply are no good reasons for it b) It doesn't produce any extra value to be slow c) It is well possible and not even hard to boot really fast d) It WOULD benefit the users. The sad thing is, I don't seriously believe it would be even hard to do with the common desktop.
It's just lack of integration, silly decisions like starting 1-5 different VMs for 1-5 times in the process for nothing, and lack of doing things in proper order and in proper time. Piece of cake tbh.
It boots under 5 seconds to Mozilla with a modified bios, like the one shown in the vid? Or is the Bios itself replaced with LinuxBios?




