kernel relink error - SCO

This is a discussion on kernel relink error - SCO ; SCO 5.0.5 im installing new network card and when kernel is relinked i have such message: cat: /var/opt/K/SCO/link/1.1.1.Eb/etc/conf/sdevice.d/$: No such file or directory (error 2) idbuild: The build process had errors. System build failed where can be error? file named ...

+ Reply to Thread
Results 1 to 10 of 10

Thread: kernel relink error

  1. kernel relink error

    SCO 5.0.5

    im installing new network card and when kernel is relinked i have such
    message:

    cat: /var/opt/K/SCO/link/1.1.1.Eb/etc/conf/sdevice.d/$: No such file
    or directory (error 2)

    idbuild: The build process had errors.
    System build failed


    where can be error?
    file named $??????

    how and where can i fix that problem???


  2. Re: kernel relink error

    On 23 Aug, 08:00, grzeg...@karnas.eu.org wrote:
    > SCO 5.0.5
    >
    > im installing new network card and when kernel is relinked i have such
    > message:
    >
    > cat: /var/opt/K/SCO/link/1.1.1.Eb/etc/conf/sdevice.d/$: No such file
    > or directory (error 2)
    >
    > idbuild: The build process had errors.
    > System build failed
    >
    > where can be error?
    > file named $??????
    >
    > how and where can i fix that problem???


    The kernel relink indicates an error under /etc/conf/sdevice.d.
    This directory is used when rebuilding the kernel and may
    indicate a corruption of the kernel.

    You dont say what driver you are installing, but it could be
    that either:

    1) The kernel was corrupt before the driver was installed and
    the install of the new driver is just highlighting the fact. In this
    case restore from a backup with a kernel that is known to
    be good

    2) The driver you are installing is not supported on 5.0.5 and is
    corrupting the kernel. In this case see if you can back out
    the driver and if not restore from backup

    If you need further assistance then you should contact your
    support provider.

    John


  3. Re: kernel relink error

    driver: rtl8139

    when im booting from: unix.old or unix.safe it is the same




  4. Re: kernel relink error

    im pretty new in that system so maybe it will be stupid question...

    ...."In this case restore from a backup with a kernel that is known to
    be good"...

    where from i can restore???


  5. Re: kernel relink error


    ----- Original Message -----
    From:
    Newsgroups: comp.unix.sco.misc
    To:
    Sent: Thursday, August 23, 2007 3:57 AM
    Subject: Re: kernel relink error


    > im pretty new in that system so maybe it will be stupid question...
    >
    > ..."In this case restore from a backup with a kernel that is known to
    > be good"...
    >
    > where from i can restore???


    Why, the tape that you make every night of course.
    If last nights happens to be bad or you don't have access to it, no problem,
    any one from your entire week or two (or more) rotation is fine.

    Then, after you're done spending whatever hundreds for some consultant to
    clean up the mess the hard way since you don't have backups, have him also
    provide a proper backup solution, tape drive and a copy of backupedge or
    lonetar most likely, which will be probably $1k minimum for drive, tapes,
    software and labor, could easily be over 2k really. 5.0.5 is pretty old and
    so it's bound to be very ovr due for some tlc fpr both software & hardware.

    Finally, don't install a realtek in a server. If a $20 intel pro/100 is out
    of reach at least get a 3com for ...$1.35 ??
    Punch in "3com nic" into ebay and there are a bezillion PCI 3c905B-TX cards
    for a dollar-fifty each, packs of 10 for $11, etc... That is a perfectly
    solid card for osr5.
    The very first item in the list is perfect, buy-it-now for $1.35 + 5.50
    shipping, not even an auction you hve to wait around for. For intel you have
    to look _slightly harder, to weed out all those extravagant $30 and $50 and
    gasp $100 gigabit cards, but in among them are perfect pro/100 cards for $5
    to $15

    Surely these parts are just as available over in EU.

    There is no excuse for putting a realtek/smc/kingston/etc... junk nics in
    your server. Or any other junk hardware.

    Brian K. White brian@aljex.com http://www.myspace.com/KEYofR
    +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
    filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!


  6. Re: kernel relink error

    it wasnt my system...
    i wasnt administrator of that thing till this week
    now i have a lot things to do with that "network"

    there is no backups, there is only unix.old but the result of booting
    from that is the same
    but what can mean that line in link_unix result
    cat: /var/opt/K/SCO/link/1.1.1.Eb/etc/conf/sdevice.d/$:

    i was thinking that there is some problem - should be $variable but it
    is $ in that variable so i have such error....


    grrrrrrrrrrrrrrrrr
    my head is to small for that stupid system... why they didnt use
    linux????


  7. Re: kernel relink error

    grzegorz@karnas.eu.org wrote:
    > it wasnt my system...
    > i wasnt administrator of that thing till this week
    > now i have a lot things to do with that "network"


    Why are you installing a "new" network card? Did the old
    card fail? If that's the case replace the old card with
    the same make and model.

    >
    > there is no backups, there is only unix.old but the result of booting
    > from that is the same
    > but what can mean that line in link_unix result
    > cat: /var/opt/K/SCO/link/1.1.1.Eb/etc/conf/sdevice.d/$:
    >
    > i was thinking that there is some problem - should be $variable but it
    > is $ in that variable so i have such error....
    >
    >
    > grrrrrrrrrrrrrrrrr
    > my head is to small for that stupid system... why they didnt use
    > linux????
    >
    >


    Well this advice is too little too late for you.

    SCO UNIX is not Linux: The administration of the two systems require
    specific knowledge and knowing one does not qualify you to work on
    the other. You can learn SCO and you are better prepared to learn
    SCO then someone with only a Windows background.

    Never change a kernel (install new hardware etc.) until you verify
    that you can rebuild the running kernel:
    # cd /etc/conf/cf.d
    # time ./link_unix

    The UNIX Operating System will now be rebuilt.
    This will take a few minutes. Please wait.

    Root for this system build is /
    n <- Answer "n" while the rebuild is running so that it won't
    wait for you to answer the question below: "...boot by default"

    The UNIX Kernel has been rebuilt.


    Do you want this kernel to boot by default? (y/n)
    The new kernel is in the directory /etc/conf/cf.d, to make
    this kernel bootable copy it onto the boot file system.

    Device node or inittab changes associated with this new kernel
    have not been made. These changes should be made by running
    touch /etc/.new_unix; /etc/conf/bin/idmkenv.

    real 0m23.51s
    user 0m5.19s
    sys 0m10.39s
    #

    This leaves the just built kernel in the current directory:

    # ls -l unix
    -rwxr-xr-x 1 root sys 3403085 Aug 23 08:39 unix

    And the booted kernel is in /stand/unix:

    # ls -l /stand/unix
    -r--r----- 1 bin mem 3403085 Aug 13 21:29 /stand/unix

    Compare the the just built kernel with the booted kernel:

    # cmp -l unix /stand/unix
    5 46 226
    6 216 23
    7 315 301
    #

    The two kernels above are identical with the differences at byte
    5,6, and 7 being expected:

    # mv unix unix.1

    # time ./link_unix
    ....
    real 0m13.78s
    user 0m4.75s
    sys 0m6.94s

    # cmp -l unix unix.1
    5 271 46
    6 220 216

    Note: Use "cmp -l unix /stand/unix | pg" The first time you try this.
    If there are major differences, pg allows you just quit without
    having to endure page after page of possibly long cmp listing.

    Once you KNOW that the current system can rebuild the running kernel,
    you can then add or remove hardware and relink the kernel as necessary.

    OSR 5.0.5 is particularly nasty when it comes to network cards.
    Search groups.google.com on comp.unix.sco.misc for
    "phantom NIC" and "fought that dragon before" to see problem and
    resolution on 5.0.5 changing NIC from 3C905 to Intel Pro100.

    Follow the advice given in the thread "phantom NIC" to properly
    change a NIC on a 5.0.5 system.

    As to your problem: Check /stand for older kernels. Identify them
    and possibly take steps to preserve an older working kernel.

    When you relink the kernel and allow it to install and boot by default,
    the installation script will rename the current working kernel from
    unix to unix.old. Check the dates on /stand/unix and /stand/unix.old
    to identify when the kernels were created (linked) and try to identify
    what has changed on the system since the last successful re-link
    (the date of /stand/unix).

    Also, since you are new to this machine, be sure to make a copy of
    /etc/inittab to /etc/inittab.last BEFORE your relink a working kernel
    and allow it to be installed. If you answer "Y" to rebuild the kernel
    environment (and you must answer "Y" when changing NIC's), /etc/inittab
    will be rebuilt from configuration files. If the previous administrator
    has edited /etc/inittab to change any settings and did not update those
    configuration files, the rebuild will wipe out the changes. This
    will cause you problems when things working before the rebuild stop
    working and you have to track down the problem.



    --
    Steve Fabac
    S.M. Fabac & Associates
    816/765-1670

  8. Re: kernel relink error

    In article <1187848809.818427.168010@j4g2000prf.googlegroups.c om>,
    wrote:
    >SCO 5.0.5
    >
    >im installing new network card and when kernel is relinked i have such
    >message:
    >
    >cat: /var/opt/K/SCO/link/1.1.1.Eb/etc/conf/sdevice.d/$: No such file
    >or directory (error 2)
    >
    >idbuild: The build process had errors.
    >System build failed
    >
    >
    >where can be error?
    >file named $??????
    >
    >how and where can i fix that problem???


    Look at /etc/conf/cf.d/mdevice. This file lists the drivers that may be
    linked into a new kernel, based on the contents of their sdevice files.
    Is there a line that begins with "$" in mdevice? If it's just a $ alone
    on a line, delete it. If it looks like some valid line was corrupted, you
    will have to try to figure out what the original contents of the line were;
    if it isn't obvious from the format of the file, post the line here.

    John
    --
    John DuBois spcecdt@armory.com KC6QKZ/AE http://www.armory.com/~spcecdt/

  9. Re: kernel relink error

    This reminds me a little of a problem I had on an Openserver 5.0.6
    system. 'man strcf' and review the information there. As I recall I
    had to empty the /etc/strcf.d directory and relink. This happened
    when a so-called 'expert' told my client they could remove one of the
    two 3Com NICs I had installed in the server. When they foolishly
    followed his advice the network blew up, no surprise. I was called
    back in to restore to the previous configuration, only to find I
    couldn't relink the kernel. Several hours of digging later I found
    the strcf problem.

    Good luck, Mark


    On Aug 23, 1:00 am, grzeg...@karnas.eu.org wrote:
    > SCO 5.0.5
    >
    > im installing new network card and when kernel is relinked i have such
    > message:
    >
    > cat: /var/opt/K/SCO/link/1.1.1.Eb/etc/conf/sdevice.d/$: No such file
    > or directory (error 2)
    >
    > idbuild: The build process had errors.
    > System build failed
    >
    > where can be error?
    > file named $??????
    >
    > how and where can i fix that problem???




  10. Re: kernel relink error

    grzegorz@karnas.eu.org wrote:
    > SCO 5.0.5
    >
    > im installing new network card and when kernel is relinked i have such
    > message:
    >
    > cat: /var/opt/K/SCO/link/1.1.1.Eb/etc/conf/sdevice.d/$: No such file
    > or directory (error 2)
    >
    > idbuild: The build process had errors.
    > System build failed
    >
    >
    > where can be error?
    > file named $??????
    >
    > how and where can i fix that problem???
    >


    what if you perform the

    ls -l /var/opt/K/SCO/link/1.1.1.Eb/etc/conf/sdevice.d/

    command?

    On a 5.0.5 system here's what I got:

    total 336
    -rw-r--r-- 1 root root 25 Mar 26 1999 Dsk
    -rw-r--r-- 1 root sys 162 Mar 26 1999 PnP
    -rw-r--r-- 1 root root 23 Mar 26 1999 Scfg
    -rw-r--r-- 1 root root 23 Mar 26 1999 Sdsk
    -rw-r--r-- 1 root root 24 Mar 26 1999 Sflp
    -rw-r--r-- 1 root root 22 Mar 26 1999 Sjk
    -rw-r--r-- 1 root sys 23 Apr 8 1999 Srom
    -rw-r--r-- 1 root sys 22 Oct 21 1999 Stp
    -rw-r--r-- 1 root root 25 Mar 26 1999 ad
    -rw-r--r-- 1 root sys 22 Mar 26 1999 aio
    -rw-r--r-- 1 root sys 92 Oct 21 1999 alad
    -rw-r--r-- 1 root root 22 Mar 26 1999 ams
    -rw-r--r-- 1 root root 23 Mar 26 1999 arad
    -rw-r--r-- 1 root root 249 Mar 26 1999 arp
    -rw-r--r-- 1 root sys 24 Mar 26 1999 astmf
    -rw-r--r-- 1 root sys 22 Mar 26 1999 aud
    -rw-r--r-- 1 root sys 22 Mar 26 1999 bio
    -rw-r--r-- 1 root root 92 Mar 26 1999 blad
    -rw-r--r-- 1 root root 88 Mar 26 1999 blc
    -rw-r--r-- 1 root root 33 Mar 26 1999 busmouse
    -rw-r--r-- 1 root sys 23 Mar 26 1999 byte
    -rw-r--r-- 1 root sys 22 Mar 26 1999 cdb
    -rw-r--r-- 1 root sys 22 Apr 8 1999 cdt
    -rw-r--r-- 1 root root 56 Mar 26 1999 cga
    -rw-r--r-- 1 root root 44 Mar 26 1999 cha
    -rw-r--r-- 1 root root 46 Mar 26 1999 ciha
    -rw-r--r-- 1 root sys 24 Mar 26 1999 clone
    -rw-r--r-- 1 root sys 21 Mar 26 1999 cn
    -rw-r--r-- 1 root root 27 Apr 8 1999 cpqs
    -rw-r--r-- 1 root sys 24 Mar 26 1999 cpyrt
    -rw-r--r-- 1 root sys 25 Mar 26 1999 cr_uni
    -rw-r--r-- 1 root sys 22 Mar 26 1999 csa
    -rw-r--r-- 1 root root 21 Mar 26 1999 ct
    -rw-r--r-- 1 root sys 21 Mar 26 1999 da
    -rw-r--r-- 1 root sys 23 Mar 26 1999 dda
    -rw-r--r-- 1 root sys 21 Mar 26 1999 dk
    -rw-r--r-- 1 root sys 22 Mar 26 1999 dma
    -rw-r--r-- 1 root sys 23 Mar 26 1999 dnlc
    -rw-r--r-- 1 root root 92 Mar 26 1999 dptr
    -rw-r--r-- 1 root sys 21 Mar 26 1999 du
    -rw-r--r-- 1 root sys 23 Mar 26 1999 dump
    -rw-r--r-- 1 root sys 22 Mar 26 1999 dup
    -rw-r--r-- 1 root sys 88 Apr 10 2000 e3H
    -rw-r--r-- 1 root sys 23 Mar 26 1999 ecc_
    -rw-r--r-- 1 root root 22 Mar 26 1999 efp
    -rw-r--r-- 1 root root 56 Mar 26 1999 ega
    -rw-r--r-- 1 root root 23 Mar 26 1999 eiad
    -rw-r--r-- 1 root sys 26 Mar 26 1999 eisarom
    -rw-r--r-- 1 root sys 23 Mar 26 1999 err
    -rw-r--r-- 1 root root 23 Mar 26 1999 esdi
    -rw-r--r-- 1 root sys 21 Mar 26 1999 ev
    -rw-r--r-- 1 root sys 23 Mar 26 1999 evld
    -rw-r--r-- 1 root root 25 Mar 26 1999 fd
    -rw-r--r-- 1 root root 24 Mar 26 1999 fdhb
    -rw-r--r-- 1 root sys 24 Mar 26 1999 first
    -rw-r--r-- 1 root root 26 Mar 26 1999 fl5
    -rw-r--r-- 1 root root 104 Mar 26 1999 flashpt
    -rw-r--r-- 1 root sys 27 Mar 26 1999 font8x14
    -rw-r--r-- 1 root sys 27 Mar 26 1999 font8x16
    -rw-r--r-- 1 root sys 26 Mar 26 1999 font8x8
    -rw-r--r-- 1 root sys 22 Mar 26 1999 fp
    -rw-r--r-- 1 root root 25 Mar 26 1999 ft
    -rw-r--r-- 1 root sys 21 Mar 26 1999 hd
    -rw-r--r-- 1 root root 27 Mar 26 1999 hf
    -rw-r--r-- 1 root root 251 Mar 26 1999 icmp
    -rw-r--r-- 1 root root 22 Mar 26 1999 ida
    -rw-r--r-- 1 root root 23 Mar 26 1999 ida0
    -rw-r--r-- 1 root root 23 Mar 26 1999 ida1
    -rw-r--r-- 1 root root 23 Mar 26 1999 ida2
    -rw-r--r-- 1 root root 23 Mar 26 1999 ida3
    -rw-r--r-- 1 root root 23 Mar 26 1999 ida4
    -rw-r--r-- 1 root root 23 Mar 26 1999 ida5
    -rw-r--r-- 1 root root 23 Mar 26 1999 ida6
    -rw-r--r-- 1 root root 23 Mar 26 1999 ida7
    -rw-r--r-- 1 root sys 23 Mar 26 1999 idaM
    -rw-r--r-- 1 root root 251 Mar 26 1999 igmp
    -rw-r--r-- 1 root root 158 Mar 26 1999 iiop
    -rw-r--r-- 1 root sys 133 Aug 1 2003 iknt
    -rw-r--r-- 1 root root 36 Mar 26 1999 ims
    -rw-r--r-- 1 root root 249 Mar 26 1999 incf
    -rw-r--r-- 1 root root 249 Mar 26 1999 ip
    -rw-r--r-- 1 root sys 22 Mar 26 1999 ipc
    -rw-r--r-- 1 root sys 22 Apr 7 2001 ipl
    -rw-r--r-- 1 root root 25 Mar 26 1999 ir
    -rw-r--r-- 1 root sys 25 Mar 26 1999 itimer
    -rw-r--r-- 1 root root 27 Mar 26 1999 kbmouse
    -rw-r--r-- 1 root sys 23 Mar 26 1999 kprf
    -rw-r--r-- 1 root sys 248 Mar 26 1999 ksl
    -rw-r--r-- 1 root sys 26 Mar 26 1999 ldterm
    -rw-r--r-- 1 root root 252 Mar 26 1999 llcloop
    -rw-r--r-- 1 root sys 22 Mar 26 1999 log
    -rw-r--r-- 1 root sys 24 Mar 26 1999 marry
    -rw-r--r-- 1 root sys 21 Mar 26 1999 mc
    -rw-r--r-- 1 root root 92 Mar 26 1999 mdac
    -rw-r--r-- 1 root sys 24 Mar 26 1999 merge
    -rw-r--r-- 1 root sys 21 Mar 26 1999 mm
    -rw-r--r-- 1 root root 57 Mar 26 1999 mono
    -rw-r--r-- 1 root sys 22 Mar 26 1999 mpm
    -rw-r--r-- 1 root sys 22 Mar 26 1999 mpt
    -rw-r--r-- 1 root sys 22 Mar 26 1999 msg
    -rw-r--r-- 1 root sys 24 Mar 26 1999 mskdb
    -rw-r--r-- 1 root sys 26 Mar 26 1999 namefs_
    -rw-r--r-- 1 root root 22 Mar 26 1999 ncr
    -rw-r--r-- 1 root sys 24 Apr 1 1999 net0
    -rw-r--r-- 1 root sys 24 Jan 24 2003 net1
    -rw-r--r-- 1 root sys 22 Mar 26 1999 nmi
    -rw-r--r-- 1 root root 23 Mar 26 1999 omti
    -rw-r--r-- 1 root root 25 Mar 29 1999 pa
    -rw-r--r-- 1 root sys 28 Mar 26 1999 pci
    -rw-r--r-- 1 root sys 22 Mar 26 1999 pic
    -rw-r--r-- 1 root root 116 Mar 26 1999 piiop
    -rw-r--r-- 1 root sys 22 Mar 26 1999 pit
    -rw-r--r-- 1 root sys 88 Jan 24 2003 pnt
    -rw-r--r-- 1 root sys 22 Mar 26 1999 prf
    -rw-r--r-- 1 root sys 24 Mar 26 1999 ptem
    -rw-r--r-- 1 root sys 23 Mar 26 1999 ptm
    -rw-r--r-- 1 root sys 22 Mar 26 1999 pts
    -rw-r--r-- 1 root sys 24 Mar 26 1999 pwr
    -rw-r--r-- 1 root sys 23 Mar 26 1999 ram
    -rw-r--r-- 1 root sys 25 Mar 26 1999 ramfs
    -rw-r--r-- 1 root root 250 Mar 26 1999 rip
    -rw-r--r-- 1 root sys 22 Mar 26 1999 rtc
    -rw-r--r-- 1 root root 250 Mar 26 1999 rte
    -rw-r--r-- 1 root sys 24 Mar 26 1999 scodb
    -rw-r--r-- 1 root sys 22 Mar 26 1999 sec
    -rw-r--r-- 1 root sys 22 Mar 26 1999 sem
    -rw-r--r-- 1 root sys 22 Mar 26 1999 shm
    -rw-r--r-- 1 root sys 54 Mar 26 1999 sio
    -rw-r--r-- 1 root sys 26 Mar 26 1999 sleeper
    -rw-r--r-- 1 root sys 92 Mar 26 1999 slha
    -rw-r--r-- 1 root sys 28 Apr 8 1999 smad
    -rw-r--r-- 1 root sys 658 Mar 26 1999 socket
    -rw-r--r-- 1 root sys 21 Mar 26 1999 sp
    -rw-r--r-- 1 root sys 22 Mar 26 1999 spm
    -rw-r--r-- 1 root sys 22 Mar 26 1999 spt
    -rw-r--r-- 1 root sys 21 Mar 26 1999 ss
    -rw-r--r-- 1 root sys 21 Mar 26 1999 st
    -rw-r--r-- 1 root sys 22 Mar 26 1999 str
    -rw-r--r-- 1 root sys 23 Mar 26 1999 suds
    -rw-r--r-- 1 root root 28 Mar 26 1999 sumo
    -rw-r--r-- 1 root sys 22 Mar 26 1999 sxt
    -rw-r--r-- 1 root sys 21 Mar 26 1999 sy
    -rw-r--r-- 1 root sys 26 Mar 26 1999 sysdump
    -rw-r--r-- 1 root sys 22 Mar 26 1999 tab
    -rw-r--r-- 1 root root 322 Mar 26 1999 tcp
    -rw-r--r-- 1 root sys 24 Mar 26 1999 timod
    -rw-r--r-- 1 root sys 25 Mar 26 1999 tirdwr
    -rw-r--r-- 1 root root 24 Mar 26 1999 tmcha
    -rw-r--r-- 1 root root 23 Mar 26 1999 tpic
    -rw-r--r-- 1 root sys 23 Mar 26 1999 ttsv
    -rw-r--r-- 1 root sys 23 Mar 26 1999 uapm
    -rw-r--r-- 1 root root 322 Mar 26 1999 udp
    -rw-r--r-- 1 root sys 24 Mar 26 1999 undyn
    -rw-r--r-- 1 root sys 22 Mar 26 1999 ups
    -rw-r--r-- 1 root sys 254 Mar 26 1999 usoclts
    -rw-r--r-- 1 root sys 338 Mar 26 1999 usocots
    -rw-r--r-- 1 root sys 24 Mar 26 1999 vdisk
    -rw-r--r-- 1 root root 55 Mar 26 1999 vga
    -rw-r--r-- 1 root sys 23 Mar 26 1999 vpld
    -rw-r--r-- 1 root sys 22 Mar 26 1999 vpt
    -rw-r--r-- 1 root sys 21 Mar 26 1999 vx
    -rw-r--r-- 1 root root 42 Mar 26 1999 wd
    -rw-r--r-- 1 root root 24 Mar 26 1999 wdex
    -rw-r--r-- 1 root root 28 Mar 26 1999 wdha
    -rw-r--r-- 1 root sys 25 Mar 26 1999 weitek
    -rw-r--r-- 1 root sys 22 Mar 26 1999 xsd
    -rw-r--r-- 1 root sys 23 Mar 26 1999 xsem
    -rw-r--r-- 1 root sys 21 Mar 26 1999 xt

    Best,
    Rob

    --
    Roberto Zini - r.zini<@AT@>strhold.it
    ---------------------------------------------------------------------
    "Has anybody around here seen an aircraft carrier?"
    (Pete "Maverick" Mitchell - Top Gun)

+ Reply to Thread