I was a little surprised by this Newsgroup thread that began with asking "With the chapter 11 filing and other recommendations, what is a good,
long time viable alternative to SCO OpenServer? "
Some posters apparently don't feel there's any need to move on.. and
I bet there are people reading this of the same or similar opinion.
OK, I agree with part of the argument: there is no reason to panic, and there's no reason to toss out SCO instantly. But I do insist that it is far past time to be looking into moving on. If you have easily moved apps, maybe there's nothing more you need to do than note the cost and leave it at that for now. If your apps are not so easily moved, you have more work to do, and harder decisions to make.
But don't get complacent. If you wait too long, you'll find yourself facing the kind of mess described at options you don't have for getting data off of a Xenix box. Note this paragraph particularly:
* hd transplant to new hardware to continue to run xenix - if you can find a 486-100 or slower box that actully runs, reliably. (think 20 year old dried out capacitors all out of spec making the circuit unstable at the very least, if not a fire hazard! Not kidding! Seen it! Caps out of spec, so voltage regulator circuit out of spec, cooked several parts of the board, dried up stickers on components and on circuit traces caught fire!
Yes, right now it's easy to find hardware that can still run SCO - the newer version will run even on brand new equipment. But that's going to change: as hardware advances, even SCO 6 will fall away and be "uninstallable". Sure, Ebay can keep you in spare parts for many a year, but those parts will be getting older and older.. just like the warning about finding old Xenix hardware, anything that can run SCO will be creaking and dusty. This is no great long range plan.
If you accept that sooner or later you WILL have to move off SCO (if you can't accept that at all, well, there's just no hope for you), you have to think about software, even if that is an easy migration now. Here's why: there's little doubt that app vendors will stop upgrading their SCO versions soon if they have not done so already. "So what?", you say, "This version is fine for now, and probably will be for years."
Yeah, maybe so. But come the day you do have to convert to the vendors Linux (or, shudder, Windows) version, will they still be able to convert your data? Maybe not: as they move forward while you stay stubbornly clinging to your old SCO, they may change file structures or even change the entire database system to take advantage of new capabilities on more modern systems. Maybe they still have something that can help migrate your data, but maybe not, and the longer you wait, the more chance you are left high and dry.
Don't put this off too long. There are plenty of resources here to help you: Self Defense for SCO Users is a good place to start. I also have a small pile of articles related to converting from SCO at Converting SCO to Linux.
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
Mon Oct 8 12:28:48 2007: BigDumbDinosaur
hd to hd copy to create partitions or cpio files that linux CAN read - if you can find a hard drive small enough that an old 486-66 motherboard bios can even see it.
This wouldn't be much of a problem if the old machine has a SCSI drive. It's probably the second-best argument against using IDE drives in any *nix box. Incidentally, in some cases the old BIOSs can be configured to only see the first 512 MB of an IDE drive, allowing one to set up a partition that can be written to from the old and read by the new.
Tue Oct 9 15:01:11 2007: TonyLawrence
Apropos ov moving on, someone just sent me this link:
"Linux for Business: 50 Apps to Get your Office on Open Source"
http://www.virtualhosting.com/blog/2007/linux-for-business-50-apps-to-get-your-office-on-open-source/
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar