James Hogarth wrote: >> Why? The current CentOS kernel isn't anywhere near the latest, nor is a >> fair bit of other stuff in CentOS 5.5. And there are lots of folks >> running yr-old releases. > > I... I... I don't really know how to answer this one... > > Anyone who is running *CentOS* from a year ago is strongly urged to > upgrade... they always have been on this list. There have been plenty I agree... but some won't, or can't. I've got someone here who insists on running RHEL 3, because of collaborators around the world who can't upgrade. <snip> > If you showed up on the Spacewalk mailing list saying you have a 0.5 > instance with X problem the first thing to be said is at least get up > to 1.0 as there have been so many bug fixes over a year that it > becomes difficult to troubleshoot an issue and any fix found will not > be backported to 0.5 but rather released as either a hotfix to the > current version or fixed in the next release. Fortunately, that was on a previous job, and we have something here that a) doesn't need a d/b, and b) is *nowhere* near as outright hostile to install and configure. I've been burned, badly, and don't care to use it again. <snip> >> I was on the mailing list. Did they ever put the change to the >> documentation that I sent in, that I found, about the settings required >> to make Oracle happy to work with it? >> <snip> > > I did mention a dependency on Oracle. I, and others, followed the > instructions on the wiki and got an instance running fine. What did > you mention specifically? Looking at the website there are steps to > follow for oracle: > > https://fedorahosted.org/spacewalk/wiki/OracleXeSetup > > Please only comment on stuff you have genuine *current* knowledge of > and not something you dabbled in a year ago... technology changes > quickly especially in a product under heavy and active development. > I didn't "dabble", my manager and VP insisted I get it up asap. And I just went to the page, above, and no, it does *not* mention what I found, which is that I had to go into Oracle admin, and up the memory available to, mmm, I think it was 995M, where the default is only 940M, and that was the *only* way to get around the stop-dead-in-my-tracks problem. mark