Gnome 2.0 Beta 2 Released 238
plastercast writes: "Following the release of GTK2, the second beta of gnome 2.0 is available. There are also release notes here. From Gnotices: 'The GNOME 2.0 Desktop is a greatly improved user environment for existing GNOME applications. Enhancements include anti-aliased text and first class internationalisation support, new accessibility features for disabled users, and many improvements throughout GNOME's highly regarded user interface.'"
GNOME 2.0 (Score:4, Informative)
It behaves a bit like the BSD ports tree as it'll download and install all the necessary packages. Even better, it'll install them in an out-of-the-way place so you can keep running gnome1.2!
release codename (Score:5, Informative)
If the site seems a little slow (Score:2, Informative)
Re:GNOME 2.0 (Score:3, Informative)
If you want an easy way to install gnome, use Ximian's redcarpet or the garnome system.
Re:GNOME 2.0 (Score:3, Informative)
Because that would be Compeltely Retarded(TM) and go against the whole damn idea of having things installed as components.
On the other hand, a nice little gtk-perl/pygtk frontend to a downloader script would be great.
Also, if you use Ximian Gnome, there is a "Gnome 2 Developer Snapshots" channel that you can use to get everything in just a few clicks...
Re:call me jaded . . . (Score:3, Informative)
Gnome 1 programs will run FINE on a Gnome 2 desktop. Ever tried running a KDE app on Gnome, or vice-versa? It works fine. Gnome 1 apps on Gnome 2 desktop is just like that.
BTW, this is like your 3rd quasi-troll post on this thead. How exactly do you post with a +1 bonus?!
Explorer.exe (Score:2, Informative)
Explorer.exe and IExplore.exe are just regular processes. Why would they "partially remain" after they crash? Here's a Windows experiment. CTRL+SHIFT+ESC to open your Windows Task Manager and kill Explorer.exe. Your computer does not crash, but your shell just disappeared. From the Windows Task Manager, File \ New Task Run explorer.exe and your shell just came back.
Re:It's all so windowesque ... (Score:4, Informative)
I have a suspicion this is to do with the C++ linker problem. In a nutshell, GCC"s handling of relocating libraries when they address collide sucks. It's slow. Really slow. The KDE team have been attempting to get over this by creating one process that loads most of the libraries - kdeinit, then forking the process to be the individual applications. The long and the short of this is the libraries remain loaded at the same address, don't have to reload and relocate, and all the processes can share the same code pages since they're copy on write.
Don't worry, they know it's a hack too.
There's a lot of work going into making it such that the GCC linker can build libraries to different default virtual memory addresses, hence stopping the loader from having to relocate libraries. When this happens the individual distros can be built with non colliding libraries, the kdeinit hack can go away and all will be at peace in KDE land. Personally, I'd delay 3.0 until the situation is sorted, but it's not my project.
Dave
I recently installed both W2K Server and Linux... (Score:3, Informative)
I installed Red Hat 7.2 today. Again, it took me an hour. But I now have tons of useful software and even some of my favorite timesink games. Yeah, I know there's patching to do here too. But most of the patches don't require rebooting.
Don't get me wrong...I like Windows 2000. It's way better than 9x and arguably better than XP. And unlike Win2K I still have a lot to learn about Linux. But as far as tweak factors, installing Linux and installing 2K are about even. And Linux just plain gives you more good stuff to play with.