To help the advancement of Linux in the telecom space, the Open Source Development Labs (OSDL) started a working group called the Carrier Grade Linux (CGL) working group. Its mission is to specify and help implement an open source platform that is highly available, secure, scalable, and easily maintained—suitable for carrier-grade systems. Read more at LinuxDevCenter.
OSDL’s Carrier-Grade Linux
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
The article took me to OSDL’s site where I saw that they also established a desktop linux working group 2 months ago.
It’s purpose is “to work with the open source community to identify a broad set of Linux desktop models, then develop specifications and deliver reference implementations.”
Pretty exciting. Maybe in time OSDL will be to the desktop what it is to the kernel – that also desktop developers around the world submit contributions to OSDL for approval and inclusion.
No surprise here. The telecommunications industry has been entrenched in Unix for years so it’s just natural that this would come about.
Desktop OSDL – I also ran across that and had forgot about it even though I’m pretty sure that osnews.com had posted something about it some months back. Personally, I wish OSDL, it’s partners, and some big players would take a stance on the future of the open source desktop. It would be nice to get some kind of concensus from these people on where the open source desktop is going instead of the status quo. E.g. Gnome vs. KDE. At the very least, work with freesdesktop.org to come up with some standards for interop. I wish Gnome would just ditch Bonobo and use DCOP(if that’s feasible) so we could possibly get something like embedding gnome components in kde and vice versa. I still hate having two sets of libraries though. I mean, say you only use one app(say Kdevelop) in a gnome environment. You’re still brining in nice chunk of the KDE/QT base libraries along with it.
Totally agree – especially about Bonobo. Paticularly gets me on my lower-powered machine (mostly used as a scanner-server, but my 19yo daughter has a habit of grabbing my ‘good’ machine before I get there) where I run Icewm for speed, but still need two extra full sets of libraries for a range of apps etc.
> I wish Gnome would just ditch Bonobo and use DCOP
> (if that’s feasible)
Unless I’m mistaken, Bonobo isn’t going anywhere. However, it would be interoperable with D-BUS and D-BUS will become more prominent in GNOME. Since D-BUS is a binary DCOP, it should be more efficient than DCOP and since KDE is also interested in a DCOP to D-BUS bridge, GNOME and KDE should interoperate more. ( http://freedesktop.org/Software/dbus )
As for embedding, you need something different since DCOP is not an embedding protocol, KPart is. Fortunately both KDE and GNOME are committed to XEmbed ( http://www.freedesktop.org/Standards/xembed-spec )
IMO, ultimately, having two desktops is a good thing precisely because it forces standards such as the Window Manager Spec, D-HUB Spec, XEmbed Spec, and several others to emerge. Without these specs, they would be defined by the code and code inheritance (e.g. you could only get the appropriate functionality if you inherit from QObject or GObject and use Gtk+ or Qt widgets). That means that lighter weight desktops and more innovative desktops would have to be married to “the one true desktop” code and thus be hampered by it.
Do you have anything to back up that statement? Sounds more like a troll to me.
He may not, but I do. How about the 3 security flaws found in the kernel a few months back? How about the Gnome servers getting breached? There are still parts of that site that are down and its been over 2 weeks.
Do you have anything to back up that statement? Sounds more like a troll to me.
I think we’ve read quite enough about security problems lately on this site and many others…
A troll? You mean as in Lord of the Rings or something? Or people living in their basements have their own vocabulary these days?
Ummm… 3 of 9 are Linux-related, the rest Windows.
http://www.cert.org/summaries/CS-2003-04.html
Neither are 100% secure, get over it…
As for embedding, you need something different since DCOP is not an embedding protocol, KPart is. Fortunately both KDE and GNOME are committed to XEmbed ( http://www.freedesktop.org/Standards/xembed-spec )
The sad part is that xembed is currently crap from my understanding of it, and would need much improving before it can be used as a replacement. Also, xemebed dosn’t use dbus (atleast not the last time I checked).
Btw, GtkPlug and GtkSocket are the gtk widgets that implement the xembed protocol.
Care to say in what way exactly XEMBED sucks instead of just making grand statements?
Bonobo and DCOP are not the same type of technology. Bonobo is components, DCOP is messaging/remote-method-invocation. The KDE counterpart to Bonobo is KParts.
you know this microsoft hating thing is going to be turned around to hate linux once linux is the most popular OS in the world.
Why not FreeBSD? Their license is looser.