Progress looks to have been picking up for the Unununium OS, where dietlibc has been ported and much work has continued in all areas including the file system, thread engine, memory manager, graphic device support, network stack as well as the build and documentation system. A new release is ‘imminent’.
Man that’s a really nice logo they have on the main page.
The Logo is great.
Sreenshots….. |
|
|/
*
Thanks, Dave spent a lot of time creating the shapes, and I made my poor celeron spent a LOT of time ray tracing the finish on it until I had it exactly like I wanted.
As for the screenshots, they’re not all that plentiful, we rather encourage that people install it on a floppy and give it a try. It won’t touch your harddrive, so there’s nothing to worry about.
As for Unununium… just wait a few weeks… there will be some major announcements coming from us.
Unununium is a mouthfull of a name. Maybe for PR reasons, it will be better to find something more pronounceable, Unium OS for instance. My 2 cents.
eheh.. There’s a good story to how we chose that name but we wont go into that, and as for how to pronounce it… that’s something we don’t all agree on. Most of the time we just end up saying Uuu (you-you-you), which is the abbreviation for the Unununium element.
I’ll have to take a look at it. How long has work been going on this project? I’ve never heard of it before.
Sidenote: How about Triunium (Pronounced Tree-oo-nee-um), or Triun (Tree-oon). Could even go Trunium (true-nee-um). Just a couple junk thoughts for the fold;)
According to the website, Unununium will evolve from a RTOS to a desktop oriented OS. Isn’t it quite a challenge to make such a transition ?
1) “The Unununium Operating Engine is designed as a highly componentized system, where each component can be dynamically loaded, unloaded, replaced at runtime. This concept is pushed to the extreme, completely removing the presence of a kernel.” IOW, a microkernel, yes?
2) Why is the documentation if FDL?
3) The logo is really nice, but perhaps a symmetric logo which is more connected with itself like SUN’s or SGI’s is even cooler. Okay, SUN’s logo is not symmetric while SGI’s is, but i guess you got what i mean.
What an unsocial geek 😎 If they pretend to be l33t, at least they should put some screenshots on par with their logo, not some chicken sh*t toolbar buttons.
We’ve since fixed the MSIE problem (ie: no PROPER css support), however, for some reason we aren’t using the modified site quite yet. The reason it doesn’t work in IE is cause we designed the site, got it all working like we wanted, and then afterwards we were told it wouldnt render in IE. It’s not like we purposefully went and used CSS that IE would not like. But like I’ve said, the issue has been resolved, and there’s a different way of rendering the page in IE, and when we migrate to the new site, all will be good
Ass for the screenshots… the toolbars (yes, butt ugly) are the Bochs toolbar buttons, from the Bochs x86 Emulator, which is what we primarily use for testing.
Bochs cannot emulate an 80×50 text resolution very well, so taking text mode screenshots with it makes it look very bad, hense the lack of them.
I’ll have to take a look at it. How long has work been going on this project? I’ve never heard of it before.
Well, Uuu started in 2001, but it has changed forms many times. The principle goals have remained fairly constant, but the implementation has not. Uuu Dimension 0.3.2 is the most ‘complete’ Uuu version you can get, but we haven’t put work into Dimension in over a year. What we’re working on now we’ve named Uuu Existence, and it has a lot of interesting ideas behind it. As I’ve said before, you should hear more from us in a few weeks.
Well… maybe it’s hard to spell for english speakers, but not at all for me (polish speaker). I think it’s really cool name
I’ll try to answer your 3 questions (I must be the only Uuu-er that’s still awake)
1) No, not a microkernel. Even a microkernel has a small piece of code that must remain static in memory to manage all the different little parts.
2) Why not? And we wont start a BSD vs GPL fight here.
3) Actually, SGI’s logo is where we got most of our inspiration, it’s a logo that I like a lot. Our point was not to mimick them, but to create something of our own, which had some similarities. We’ve spent enough time on our logo (4 full days, poor poor celeron (400mhz btw )), and we’re happy with it. We’ve gotten many compliments on it, and constructive criticism is always welcome, but I don’t think we’ll be changing it any time soon.
I did not write that particular piece of text, but we will not be making a transition from an RTOS to a Desktop OS. The goal is to make a small usable Desktop OS that happens to be based off an RTOS.
I think the name is great and the logo, but those are secondary. I think the concept is very cool.
From the looks of it, this seems like a very innovative way to work with an OS. I do hope you guys continue the good work and show us more as things keep progressing.
1) Hmm but how can it function if there is no kernel at all? Linux 2.6 can be compiled in a very modulair manner, but there’s still a kernel. Microkernels do it different by leaving as much as possible in application layer, but how on earth can is it possible to have no kernel at all? Or almost no kernel? Do you mean it implies something like Linux 2.6 but even a lot more modulair? Do you have a technical documentation about this? I couldn’t find this info on the site.
2) No, NOFI. I’m trying to look at it from the BSD/X11/-prefered point of view: “Most, if not all Uuu code that is on our CVS is either under the BSD license, or X11 license, both of which are virtually identical and GPL compatible. The reason that we chose such a license versus the oh so popular GPL, is that we do not want developers to feel like they are obligated to give us anything for using Uuu sources. If you can make use of our sources, all the more power to you, an email letting us know would be nice, but unless you want, you aren’t required to send us your modifications.” Therefore i was wondering: “why another approach for the documentation?” Quoted: “[..] If you don’t mind people making proprietary versions of your manual, use a permissive, non-copyleft license such as the X11 license. (The X11 license explicitly mentions documentation.) [..]” and “[..] GFDL’ed invariant sections prohibit modification. You probably just want to require that modified versions don’t pretend to be your version, and possibly that they credit you as the author of the original. This can be accomplished much more easily, with better, freer licenses. [..]” taken from http://home.twcny.rr.com/nerode/neroden/fdl.html
3) Well ok. I just thought it would be even more nice when it has the “connected” aspect and perhaps too when it looks nice when turned around, like the SGI one. I’d claim the SGI logo says something about the company and their scope (complex, connected, mathical and graphical perfect, which shines throught when it is circulating around it’s inner middle point) – which is imo a Good Thing from a marketing point of view. Now if the projects’ scope would be related to the logo (is it?) it would be nice. Something which describes the modularity and extreme small size (or no size) of the kernel (inner?) – but then again it’s easy talk for one.
It definitely reminds me of something erotic, but I can’t exactly point out what.
By popular demand, I’ll spend today adding some introductory material on our website. Note that I’ll be using our new website, http://unununium.org/ . We have been meaning to transistion towards this new server, but have been too busy coding 😉
1) The idea is to link at run/load time rather than link at compile time. If you look at how most kernels are built (even microkernel), they take multiple linkable objects, most often ELF, and thru ‘ld’ they generate a single binary that will be loaded by Grub/Lilo/*. What we do is have those individual .o be loaded at runtime individually, allowing each and every of them to be unloaded/reloaded any time in any order.
2) Not much research was done on documentation license, we will try to take some time and see about those other alternatives you pointed out.
3) In the same way the SGI logo try to look “connected”, we try to emphasis the idea of “separate individual component” to reflect our kernel less implementation. The 3 parts of the logo are actually symmetrically placed, only the camera angle makes it look asymmetric.
(y´´nny´nm) (KEY) , artificially produced radioactive chemical element; symbol Uuu; at. no. 111; mass number of most stable isotope 272; m.p., b.p., sp. gr., and valence unknown. Situated in group Ib of the periodic table, it is expected to have properties similar to those of gold.
http://www.bartleby.com/65/un/unununium.html
In 1994 an international research team led by Peter Armbruster and Sigurd Hofmann at the Institute for Heavy Ion Research at Darmstadt, Germany bombarded bismuth-209 atoms with nickel-64 ions. In an 18-day experiment, three atoms were unambiguously identified as an isotope of element 111 with mass number 272 and a half-life of 1.5 msec. No name has yet been suggested for element 111, which is therefore called unununium, from the Latin root un for one, under a convention for neutral temporary names proposed by the International Union of Pure and Applied Chemistry (IUPAC) in 1980.
See also synthetic elements; transactinide elements; transuranium elements.