It won’t be of interest to everyone, but Crux 2.6 hit the streets a few days ago. I was a little surprised that it was only nine months between 2.5 and 2.6, but I’m always glad to see updated packages on the installation ISO — less time to compile up to current, I suppose.
I have one machine — the Thinkpad — that was running 2.5 and I’ve already switched to the 2.6 repos, by editing the rsync files in /etc/ports. Change the reference to 2.5 to 2.6, update your ports directory, and if you use prt-get, do a quick prt-get sysup to start the dirty work.
You could always upgrade from the ISO, but I feel guilty doing that. 😉
And just as a note, compiling gcc 4.4.1, running rtorrent to seed the Crux 2.6 ISO, showing a DVD rip against the framebuffer and meshing it all together with screen-vs is only taking up 34Mb of memory on a 550Mhz machine. Like I keep telling you, life without X can be a very liberating experience. … 😈
Guess that disproves the ‘rumors’ that Crux wasn’t actively developed anymore 😉
“Like I keep telling you, life without X can be a very liberating experience. … :twisted:”
i heard rumors that Google Chrome OS will skip X and use directfb
http://directfb.org/
CAUTION: Parts of the following may be misconstrued as flamebait. They are merely statements, I honestly am not sure how I feel on the paticular controversies associated.
Well, that’ll work, if they feel like recompiling things to use DirectFB. If this rumor is true, however, and Google puts *everything* under a GPL-compatible license, it’s awesome news for DirectFB and *possibly* bad for X Windows
Why do I say that? Google developers + DirectFB = rapid development + really good DirectFB. 😉 Also, it’s conceivable that X Windows – developers who leave for DirectFB = slower development for X Windows. Although that might be a good thing — with few developers, maybe they’ll stop sticking in new features as often and work on performance, bugs, compatibility, etc instead. 😐