Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.co   
   !border2.nntp.dca.giganews.com!nntp.giganews.com!news.maxwell.sy   
   .edu!sn-xt-sjc-05!sn-xt-sjc-08!sn-xt-sjc-09!sn-post-sjc-01!super   
   ews.com!corp.supernews.com!not-for-mail   
   From: "comp.database.paradox"    
   Newsgroups: alt.os.linux.ubuntu   
   Subject: LTSP - KDM Windows Manager   
   Date: Fri, 16 Feb 2007 15:32:41 -0700   
   Organization: Posted via Supernews, http://www.supernews.com   
   Message-ID: <12tcc8csqjc5i03@corp.supernews.com>   
   X-Priority: 3   
   X-MSMail-Priority: Normal   
   X-Newsreader: Microsoft Outlook Express 6.00.2900.3028   
   X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028   
   X-RFC2646: Format=Flowed; Original   
   X-Complaints-To: abuse@supernews.com   
   Lines: 21   
   Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:10545   
      
   Hello All,   
      
   I've got an ALMOST working TSP setup happening on my test bench.   
   What I'm trying to do is get KDM as the login manager.   
   I've got it installed on the server and KDM comes up at boot, just like it    
   should.   
      
   BUT...   When the Thin Clients boot (via PXE network boot - lovely!) the    
   standard Gnome GDM boot manager loads.   
      
   I really want to use KDM because of the flexibility of the auto login.   
   The whold aim is to have each terminal login under a user name that is    
   linked to that machine.   
   KDM supposedly does this very easily...   but I can't get KDM to start on    
   the client computers   
      
   Any help would be great,   
   Thanks,   
   John    
      
   --- Platinum Xpress/Win/WINServer v3.0pr5   
    * Origin: Omicron Theta BBS (1:261/20)