Slashdot Mirror
Gentoo Announces OpenSolaris Port
A reader writes:"According to this week's Gentoo Weekly Newsletter, Gentoo is planning a port to Sun's partially-announced OpenSolaris. Something interesting to look out for, or just more hype from a developer often criticized even by Gentoo people for not looking before he leaps?"
GNU's not UNIX. Solaris is.
I don't need a signature.
You can always run `emerge depclean` to remove packages that aren't in your world file and aren't required by any packages that are. And there's `revdep-rebuild` in the gentoolkit which will rebuild any packages that might end up broken after a depclean. With those two commands, I've never had any problems keeping only the packages I want and need on the system with no extra cruft.
"You're older than you've ever been, and now you're even older."
Something interesting to look out for, or just more hype from a developer often criticized even by Gentoo people for not looking before he leaps?
No, I don't think so. There's been a installer for Solaris avalible from this self same developer for some time. As this is just an incremental update rather than inventing a whole new wheel I don't think anyone can be seriously worried about him pulling this off.
revdep-rebuild -pv is what you want. Run it before you go uninstalling packages.
because /dev/ROOT probably isn't your filesystem unless you're using symbolic links or UDEV. Since you didn't already understand that part I'm going to make an assumption that you don't have a raid or scsi, and guess that you need to use /dev/hda3 or something very similar. /dev/ROOT is not a hard drive nor a partition. /dev/hda is your first IDE hard drive. /dev/hda3 is your 3 partition on your first IDE hard drive. If you followed the gentoo install guide, it has you setup /dev/hda3 as your root partition... Try reading the guide really :)
You should change /dev/ROOT to you root partition, in my case that's /dev/hda3
Read the documentation: http://www.gentoo.org/doc/en/handbook/index.xml
200GB/2TB $7.95 Coupon: SAVE90DOLLAR
Can't access http://www.opensolaris.org Connection times out....
Something interesting to look out for, or just more hype from a [developer] often [criticized] even by Gentoo people for not looking before he leaps?"
Both the above links are irrelevant. The "developer" link is currently redirected to the Gentoo distribution, while the "criticized" to a web interface to the gentoo-dev mailing list. I've scanned said mailing list and it looks like a normal discussion to me, the so-called "criticism" is just a difference of viewpoints. I am unwilling to read the whole gentoo-dev and/or learn about the finer points of gentoo's portage just to validate the poster's point of view.
IMHO, only the first sentence looks like news; second is just fingerpointing.
Just
No, it doesn't resolve dependicies. I'll refuse to use any OS at home that doesn't have a ports system of some sorts as it just makes life so much easier.
:(
And yes, you can compile them manually under Solaris no problem. Sun also supply them on a bonus CD. The problem is, they don't update them. Vuln in libpng? Update it yourself.
Portage is a superb tool. I'd really like to have a good ports system on normal Solaris, let alone OpenSolaris!
Well as someone who does a lot of development I don't have any problems with high loads.
... so did 2.6.7 through 2.6.9) or you're just making stuff up for the sake of posting.
;-)
I've seen nessus scans eat up tons of cpu time on even my AMD64 but the machine is still responsive and operating just fine. Mind you that was a different story with earlier 2.4.xx back when I had my Barton.
So maybe you were using an old kernel (2.6.10 works great
Also that "pre-emptible kernel" checkbox in menuconfig... make sure that's checked eh
Tom
Someday, I'll have a real sig.
I know that there are several options to reduce the overhead on the production platform. Here are two of them that I can think of off the top of my head:
This isn't just an option, it's a necessity. You should never install new software, or a new version of currently installed software, without first testing it on a machine that mirrors the production setup. Only after testing has shown it's stable and doesn't adversly affect other software should it be rolled out on the production machine.
In the case of a source based distribution you should be rolling out the binaries you know work - i.e. the ones you built and tested for your test system.