search for: unweildi

Displaying 11 results from an estimated 11 matches for "unweildi".

Did you mean: unweildy
2014 Jan 16
1
CentOS on this Laptop
Hi List, Just wondering if anyone has tried CentOS on this laptop. HP ENVY 15-j067cl 15.6 Sam's club is selling it for $699 right now. http://www.samsclub.com/sams/hp-15-6-touch-nb-intel-core-i7-4700qm/prod11610128.ip?navAction=push HP ENVY 15-j067cl 15.6" Touchscreen Laptop Computer, Intel Core i7-4700QM, 8GB Memory, 750GB Hard Drive Thanks, -- Stephen Clark *NetWolves* Director of
2001 Nov 24
1
Are you experienced in SAS ...
I'd just like to put in my two bob's worth: The ***only*** thing for which I prefer SAS to R/Splus, but it's a very important thing, is the analysis of mixed linear models. One can do the same analyses in both languages. The difference is that the SAS syntax for specifying such a model, and its output, is comprehensible to the human mind, which is what I'm equipped with. The
2010 Sep 08
3
Regression using mapply?
Hi, I have huge matrices in which the response variable is in the first column and the regressors are in the other columns. What I wanted to do now is something like this: #this is just to get an example-matrix DataMatrix <- rep(1,1000); Disturbance <- rnorm(900); DataMatrix[101:1000] <- DataMatrix[101:1000]+Disturbance; DataMatrix <- matrix(DataMatrix,ncol=10,nrow=100); #estimate
2002 Jan 27
1
[PATCH] Add user-dependent IdentityFile to OpenSSH-3.0.2p1
Here is a patch to allow private key files to be placed system wide (for all users) in a secure (non-NFS) mounted location on systems where home directories are NFS mounted. This is especially important for users who use blank passphrases rather than ssh-agent (a good example of where this is necessary is for tunnelling lpd through ssh on systems that run lpd as user lp). IdentityFile now accepts
2013 Jun 20
0
[LLVMdev] Proposal: type uniquing of debug info for LTO
+1 to roughly everything Eric said. On Thu, Jun 20, 2013 at 2:51 PM, Manman Ren <mren at apple.com> wrote: > > The intent of this proposal is to speedup compilation of "-flto -g" for c++ programs. > This is based on discussions with Adrian, David and Eric. > > --------------------------- > Problem: > A single class can be used in multiple source files and the
2002 Dec 11
3
Excluding levels in table and xtabs
I'm trying to form contingincy tables among a set of character variables which were read from a .csv file and have missing represented as "". I want to exclude the missing levels from the table. > levels(CPIC) [1] "" "N" "Y" > levels(Manix) [1] "" "N" "Y" > xtabs(~CPIC + Manix, exclude=c("",NA))
2013 Jun 20
1
[LLVMdev] Proposal: type uniquing of debug info for LTO
On Jun 20, 2013, at 3:27 PM, David Blaikie wrote: > +1 to roughly everything Eric said. > > On Thu, Jun 20, 2013 at 2:51 PM, Manman Ren <mren at apple.com> wrote: >> >> The intent of this proposal is to speedup compilation of "-flto -g" for c++ programs. >> This is based on discussions with Adrian, David and Eric. >> >>
2019 Jun 27
2
A libc in LLVM
On Thu, Jun 27, 2019 at 2:05 PM Chris Lattner <clattner at nondot.org> wrote: > Saleem, Owen, others on the thread who are concerned about this: it seems > that some of the concern is that the project goals are too narrow, and thus > the eventual result may not serve the full community well over time. > > Would any of you be interested in what we should consider as the list
2013 Jun 20
9
[LLVMdev] Proposal: type uniquing of debug info for LTO
The intent of this proposal is to speedup compilation of "-flto -g" for c++ programs. This is based on discussions with Adrian, David and Eric. --------------------------- Problem: A single class can be used in multiple source files and the DI (Debug Info) class is included in multiple bc files. The duplication of class definitions causes blow-up in # of MDNodes, # of DIEs, leading to
2012 Jan 15
22
Does raidzN actually protect against bitrot? If yes - how?
"Does raidzN actually protect against bitrot?" That''s a kind of radical, possibly offensive, question formula that I have lately. Reading up on theory of RAID5, I grasped the idea of the write hole (where one of the sectors of the stripe, such as the parity data, doesn''t get written - leading to invalid data upon read). In general, I think the same applies to bitrot of
2013 Nov 26
7
[PATCH RESEND 0/1] libxl: introduce an option for disabling the non-O_DIRECT
I think I posted this patch before, but it looks like it was in December 2012 (!). 1/1 libxl: introduce an option for disabling the non-O_DIRECT workaround Ideally it would go into 4.4, at least. Provided the corresponding qemu part has gone into qemu-xen, which I think it has. Can anyone confirm ?