|
Back to the news-page
Gentoox Sparkle v1.4, Resctoox v1.2 + Manuals Pro v1.5/MCE v1.1 + More ...
>> From gentoox.shallax.com:
[QUOTE]
* Gentoox Pro(info) v1.5 and Gentoox Media Center(info) v1.1 manuals online.
In preparation for release, the manuals have been uploaded to here. Go check them out.
So thats two distros down, but I've saved the worst for last *shudders*. Gentoox Home(info) may take quite a bit of time to update :(
*UPDATE* If I ever want to get Home v3.2 released this side of Feb, I'm going to have to skip all the software updates. I'll resolve the virtual/modutils conflicts, but thats it. This was only ever intended to be a maintenance release anyway.
*UPDATE2* Okay, I'm building the final Home v3.2 package now. The previous one all went fine except I forgot to chmod 777 /bin/firstboot which meant I had to start packing it up all over again (which takes about 2 hours!)... but thats the only bug I noticed. So once thats done, I can upload them ALL tomorrow.
* New release: Gentoox Sparkle(info) v1.4
Nothing huge, just updated the kernel to the latest Gentoox kernel in hope that this will make it support large F drives. Also, updated the linuxboot.cfg included with it to the newest syntax.
Download: here
* New release: Gentoox Resctoox(info) v1.2
Another small update. While I'm syncing everything I may as well update this. Resctoox now uses the latest kernel in hope that the large F: support will help someone out ;).
Getting these releases out at this rate is killing me, I just hope I haven't added any bugs. If people could please check them out for me I'd be very grateful!
...Time to work on Home v3.2.
Download: here
* Further fixes for Xfree
Seems that when you run "emerge -Dup world" it now automatically _"UPGRADES"_ xfree to xorg... thats just wrong! So if you run magic now, it should fix this. For now, this fix will stop xorg from ever being upgraded.
* For people with Native installations and Loader v5.x
You may have noticed that Gentoox doesnt boot correctly. I'm now aware of this issue, and a simple fix is to just run "rm -rf /boot/*". If you're paranoid about this, run "fdisk /dev/hda" and toggle the "active" flag so that ALL partitions are non-active. This should solve your issues.
Note that this will be fixed in Pro v1.5 and Home v3.2.
[/QUOTE]
Back to the news-page
| |
|
|
|
|
|
|
