search for: si1

Hi everyone, After reading the external file into R it will become a R dataset. Now my querry is i want to dispaly only character variables from that dataset. please help me in this aspect. if possible send me the code. it will be very helpful for us. Thank you in Advance. -- View this message in context:

...rity"]] <- as.character(myDiamonds[["clarity"]]) myDiamonds[myDiamonds[["clarity"]]=="I1","clarity"] <- 1 myDiamonds[myDiamonds[["clarity"]]=="SI2","clarity"] <- 2 myDiamonds[myDiamonds[["clarity"]]=="SI1","clarity"] <- 3 myDiamonds[myDiamonds[["clarity"]]=="VS2","clarity"] <- 4 myDiamonds[myDiamonds[["clarity"]]=="VS1","clarity"] <- 5 myDiamonds[myDiamonds[["clarity"]]=="VVS2","clarity"...

Thanks to those who had suggestions on my last post, but none of those seems to have worked. I have narrowed down the problem a bit though, seems users can't write to a share that is not their primary group. For example: Bob's primary group is Bob and secondary group is Sally. Bob can write to the Bob group share but not the Sally group share. Anymore thoughts/suggestions. Thanks

...swd -j domain".) The last step may not be strictly necessary, but it confirms that Samba and the DC are on speaking terms again. Any ideas on how to avoid these problems would be appreciated. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Paul Taylor taylpm@si1.dod.gov.au Thanks!! I am also very interested in why that works and what causes the problem.

...a.lists.samba.org> List-Unsubscribe: <http://lists.samba.org/mailman/listinfo/samba>, <mailto:samba-request@lists.samba.org?subject=unsubscribe> List-Archive: http://lists.samba.org/pipermail/samba/ Did you check http://marc.theaimsgroup.com/ Ries Return-Path: <bentdp@hydrogen.si1.dod.gov.au> Delivered-To: samba@lists.samba.org Received: from hydrogen.si1.dod.gov.au (hydrogen.si1.dod.gov.au [203.10.130.1]) by lists.samba.org (Postfix) with ESMTP id EBD7A501C for <samba@lists.samba.org>; Fri, 13 Jul 2001 00:41:53 -0700 (PDT) Received: (from bentdp@localhost) by h...

(I apologise if this has already been reported - the archive isn't very searchable.) At present the NOESCAPE keyword seems rather useless, because a boot prompt is offered whenever attempts to load a boot image is interrupted using <Ctrl>C. Intuitively, I would expect "NOESCAPE 1" to lock this down also, and that {sys,pxe,iso.ext}linux would simply fall through to the