Conference govt02::basingstoke

    I think, don't quote me on this, that I.S. used to be responsible for
    this. No doubt if you logged a call and said that the VTX databse on
    kernel was out of date you would get contractor who didn't know
    what/who kernel was. 
    
    Steven

    
    As a contractor I'd like to very quickly quash any extrapolation that
    ALL contractors don't know what/who KERNEL is.....
    
    KERNEL is the yummy bit at the centre of a nut (Pistachio is my fav.)
    
    KERNEL is the tiny little Executive bit in NT which talks to other
    Executive bits 
    like VMM, LPCF, PM, OM, HAL and last but not least the microKERNEL.
    You can get 16Bit KERNELS (KERNEL16.DLL) or 32Bit KERNELS
    (KERNEL32.DLL) 
    
    KERNEL is also the yummy little bit at the centre of UNIX (so as not to
    miss them out)
    and is the likely origin of the word as it's been around longer than NT
    (or nuts for
    that matters !)
    
    KERNEL is a Rank in the army with very little
    responsibility....err....mmm....
    I think that may be spelt Colonel however......
    
    So I hope that clears up our (contractors) VAST knowlege of word
    "KERNEL"
    
    Any more suggestions on this word to   KERNEL::horseyc
                                              ^
    Hey !!  There's another use of the word ..^..but I'm sure thats just a
    cooincidence.
    
    MMmmmmmm.... ;;-)
    
    C.
    B.
    X.
    

        
        >> KERNEL is also the yummy little bit at the centre of UNIX
        >> (so as not to miss them out) and is the likely origin of the 
        >> word as it's been around longer than NT
        
        KERNEL mode is also the most privileged processor access mode in 
        VMS - and is much more likely to be the origin of the word as
        all NT internals are ripped off from VMS anyway.
        
        ~Ian.
        

        Incidentally, to return to the base note, I think I'd prefer
        it if the Viables VTX pages were kept as they are, it's a bit
        of nostalgia.  If you find it annoying, just put the following
        in your LOGIN.COM and you'll never see them again:
        
        $ assign/nolog "chefs::""195=""" vtx$server
        $ assign/nolog "reprot::""43=""" vtx$server01
        $ assign/nolog "wendys::""195=""" vtx$server02
        
        ~Ian.

re 

        $ assign/nolog "chefs::""195=""" vtx$server
        $ assign/nolog "reprot::""43=""" vtx$server01
        $ assign/nolog "wendys::""195=""" vtx$server02

The last assign, wendys, is a bit redundant as that would 
be caught by the first assign, chefs, the cluster alias.


Simon

        
        > The last assign, wendys, is a bit redundant as that would
        > be caught by the first assign, chefs, the cluster alias.
        
        That doesn't make it redudant. There's a number of reasons for
        a connection to a cluster alias failing when connections to a 
        cluster member don't. I picked WENDYS (not entirely at random :-) )
        to cover that eventuality.
        
        I.

Well, under normal circumstances the definitions on CHEFS
are as follows.

  "VTX$SERVER" = "CHEFS::"43=""
  "VTX$SERVER02" = "WENDYS::"195=""
  "VTX$SERVER03" = "WIMPEY::"195=""
  "VTX$SERVER04" = "NICOS::"195=""
  "VTX$SERVER05" = "RDGE21::"195=""
  "VTX$SERVER06" = "BERNIS::"195=""
  "VTX$SERVER07" = "REPROT::"43=""
  "VTX$SERVER08" = "DELBOY::"43=""

Looks like I need to remove RDGE21 and DELBOY ;-)

Simon
UK VTX SUPPORT (Main menu and servers)

    re: .2 
    Chris I think you took my note out of context. I was refering to the
    apparant number of contractors on the CCS helpdesk who, at least the
    last time I called, knew not what/who kernel was. 
    
    Perhaps it should have read;
    
    `.....No doubt if you logged a call with I.S.......'
    
    Steven

>Looks like I need to remove RDGE21 and DELBOY ;-)


I thought someone did that a long time ago...