The other day someone called me about removing hard drives previously added to the kernel configuration.. my mind went blank.
I said that I knew it was "mkdev dot-something" and told him to look in /usr/lib/mkdev with "lc -a". I was too busy to look there myself (and didn't have easy access to a SCO box right then anyway) but told him to look through the "." files in /usr/lib/mkdev to see if something looked right. I also told him that it could be done manually and quickly referred him to http://wdb1.sco.com/kb/showta?taid=105052 and hastily said "You need to take the stuff out of mscsi, remove the device files.."
And I didn't mention space.c and for some reason he didn't read that article (maybe he wasn't able to get email where he was) so he got all screwed up.. had to restore parts of /etc/conf from backup.
Here's the thing, folks: my knowledge of SCOish details is fading. My *interest* in things SCOish is going away even faster. Yes, I can still help you with most things, but that list of things is slowly getting smaller because I'm simply forgetting it - it's not getting used often enough, so it's going away.
It is time to get off SCO. Way past time. Think about it.
More Articles by Anthony Lawrence - Find me on Google+
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
Sun May 11 15:31:14 2008: markBrown
http://markbnj.blogspot.com
Don't feel bad about losing the SCO knowledge base.
But the good news is that it is really (but only theoretically) something like (but not really)
System V
I learned (and cut my teeth) on System V, and then Sun/OS, so I have both sides covered at least.
and now solaris (and linux) are (both!)
Sun May 11 22:17:41 2008: TonyLawrence
Of course: I did a lot of SunOS, a tremendous amount of Solaris, some AIX.. but it's the SCO admin stuff that I'm forgetting. Not the raw basics, but the little tricks and gotchas.
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