Linked by Jordan Spencer Cunningham on Mon 31st Aug 2009 21:14 UTC, submitted by Henry
Thread beginning with comment 381751
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Your first mistake was using a distro that is known for cutting edge software and that has a life span of 13months
My first mistake was in putting any credence into the reports from people swearing that Fedora was production ready. That led to my second mistake, which was deploying Fedora.
If you want to use a Redhat flavour in a corporate environment...
Which I no longer care to do.
...you should use RHEL or CentOS.
No. RHEL/CentOS are not very good for this use. Been there, done that. Remember, we're talking XDMCP servers. And RHEL/CentOS take you in the opposite extreme. We deal with *lots* of documents from outside the company. And RHEL5/CentOS5 do not deal with that nearly as well as what we use now. And even with the dag repo, the package availability for RHEL/CentOS is absolutely anemic. Last I looked, EPEL was looking pretty disappointing, too.
My first mistake was in putting any credence into the reports from people swearing that Fedora was production ready.
Your first mistake was in using XDMCP for any kind of remote working, unless it's for legacy reasons. Even then, there are far better methods of using remote desktops and getting remote access to data these days that are seriously worth migrating to. Unless you're going to allow that I see little point at all to XDMCP these days with all the powerful, cheap fat clients and alternatives we have such as NX or even NFS mounting.
No. RHEL/CentOS are not very good for this use. Been there, done that. Remember, we're talking XDMCP servers. And RHEL/CentOS take you in the opposite extreme.
As far as I know there are a number of people using XDMCP with Red Hat and lots of distros, but again, there are better ways of accomplishing the same thing and more which is why I don't use it. Ever. You have to use it on a reliable and secured LAN, so if anyone starts asking for outside access via the internet you're stuck.
We deal with *lots* of documents from outside the company. And RHEL5/CentOS5 do not deal with that nearly as well as what we use now.
Well, I hope you don't use XDMCP for outside access so I'm assuming that means that you need certain documents to open and they only open with later versions of Open Office. It's a very hefty application to be running for multiple users on central remote machines though.
And even with the dag repo, the package availability for RHEL/CentOS is absolutely anemic. Last I looked, EPEL was looking pretty disappointing, too.
I'm not too sure why you'd want a large package repository for this kind of thing. Open Office 3, if that's your problem, can be installed fairly easily on CentOS/RHEL 5. You were best served getting a static and reliable distribution and set up you would leave in place for years before you planned a major upgrade. It's easier to work from there and get a reliable installation method for your applications rather than constantly getting into a muddle about what distribution you'd use and when to 'upgrade'. It shouldn't be hard.
If you were really clever you could simply forward applications from an 'applications' machine, that you could upgrade and drop in on a more regular basis, to a desktop. With NX you can even do this with Windows and Terminal Services applications.
Congratulations. It sounds like a disaster waiting to happen, or a nightmare at least.






Member since:
2007-03-13
Your first mistake was using a distro that is known for cutting edge software and that has a life span of 13months as a production/corporate OS. If you want to use a Redhat flavour in a corporate environment you should use RHEL or CentOS.