Re: "cps is not executable", Re: Graphics Window, one more time

From: Bill Vermillion (bv_at_wjv.comREMOVE)
Date: 10/18/03 

Date: Sat, 18 Oct 2003 00:45:09 GMT

In article <rNWjb.25738$Z86.5869@twister.socal.rr.com>,
Don Williams <dwilli10@san.rr.com> wrote:
>
><tony@aplawrence.com> wrote in message news:bmosoc$23q$2@pcls4.std.com...
>> Bela Lubkin <belal@sco.com> wrote:
>>
>> >There's absolutely nothing about this problem to suggest that the kernel
>> >is bad. This is like saying "The turn signals on my car weren't
>> >working, so for a test I replaced the engine..."
>>
>> Well, often people don't understand the relationship of the kernel
>> to the rest of the system. And, to draw the analogy out even more,
>> if the turn signals aren't working because the battery is dead because
>> the engine won't run.. by which I mean to suggest that sometimes
>> people learn that inexplicable problems go away by rebooting or
>> booting with an older kernel, so they apply that magic to situations
>> that really don't make sense: the engine is obviously running, the
>> headlights are on, so the dead turn signals aren't going to be helped
>> by an engine transplant. But: that transplant may necessitate rewiring
>> the electrical system, and that might fix the problem, so once again
>> our neophyte learns the wrong lesson.
>> --
>> tony@aplawrence.com Unix/Linux/Mac OS X resources: http://aplawrence.com
>> Get paid for writing about tech: http://aplawrence.com/publish.html
>>

>My experience is that unless you are someone working with the
>internals of Unix, you don't know for sure what is in the kernel
>and what is not.

>This is complicated by the fact that the SCO OpenServer Handbook
>suggests booting with unix.old or unix.safe if something doesn't
>work which did work in the past.

>Regarding "cps is not executable", a link rebuild fixed all
>that. No idea why some of the symbolic links got lost, or why
>the permissions on tcbck got changed, but the system repaired
>them when asked to.

You can see that yours is not isolated otherwise an OS would not
need a tool to restore things. :-(

The concept of the links looks good on paper and I've seen the
whitepaper and charts on it - but transfering from concept to the
real world it turns out to be one of the worst things SCO did as
the general consensus indicates.

Bill 

-- 
Bill Vermillion - bv @ wjv . com

Relevant Pages

  • dpkg not changing files in /boot after kernel upgrade
    ... I have been using the 2.6.18-4-powerpc kernel on my system for a while now ... Not updating initrd symbolic links since we are being updated/reinstalled ... (2.6.21-6 was configured last, according to dpkg) ...
    (Debian-User)
  • Re: Problem with kernel upgrade.
    ... I have fixed the problem of Linux booting up with the wrong kernel ... System.map both had their own symbolic links. ... Then I created a link to the new initrd as well. ... My new problem is that I am getting modprobe errors. ...
    (Fedora)
  • Re: Transferring SCO Drive to Another Server
    ... Does the machine boot? ... >> maybe give some error messages when you try to boot? ... >unix.install kernel. ... Bill Vermillion - bv @ wjv. ...
    (comp.unix.sco.misc)
  • Re: Good reasons4 NOT choosing freebsd
    ... >> running limited applications all of which get security patches as ... It has been very rare for the need to patch the kernel. ... And since the machine is in a colo I try to keep the rebooting ... Bill Vermillion - bv @ wjv. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: rm "fig[1].gif" fails
    ... >> What are the permissions on the file? ... >Is your kernel is more recent then mine? ... some problem with your un-named shell. ... Bill Vermillion - bv @ wjv. ...
    (comp.unix.bsd.freebsd.misc)