similar to: executable R scripts

We have a problem with shares that we would like to keep read-only for some users; it worked with 2.2.8a, but with 3.0.0 there is this odd behaviour: Users with read-only privilege can browse the files, can copy them out of the share (eg to their own hard disks) and open the copies, and can open the files in situ with Notepad; but if they try to open files in the share with Excel, for example, or

The first patch will make "make install-strip" work. The second spends a few cycles avoiding "1 files to consider." Both are trivial but IMHO useful. --- Makefile.orig Wed Mar 13 06:38:42 2002 +++ Makefile Wed Mar 13 06:40:58 2002 @@ -12,6 +12,7 @@ LDFLAGS= INSTALLCMD=/bin/install -c +INSTALLMAN=/bin/install -c srcdir=. @@ -56,8 +57,8 @@ ${INSTALLCMD} -m 755 rsync

Can someone suggest anything that will help with the following ext3 performance problem? (It's a Berkeley db issue at bottom, but the ext3 part is worth looking at, I think.) First, two paragraphs of background: A Bayesian spam filter called bogofilter uses Berkeley db to maintain two database files of identical format: one containing words found in spam email and for each word the number

Hi, I have an R script that takes its input in the form of command-line parameters. It works fine, but R complains about every unknown arg with the "ARGUMENT %s ignored" message, and this goes to stdout instead of stderr because R_ConsoleFile isn't set yet. Is it really necessary to process all command line args before setting R_ConsoleFile? It seems that only Aqua systems care

Hi, I have an R script that takes its input in the form of command-line parameters. It works fine, but R complains about every unknown arg with the "ARGUMENT %s ignored" message, and this goes to stdout instead of stderr because R_ConsoleFile isn't set yet. Is it really necessary to process all command line args before setting R_ConsoleFile? It seems that only Aqua systems care

I have a repetative task in R and i'm trying to find a more efficient way to perform the following task. lst <- list(roots = c("car insurance", "auto insurance"), roots2 = c("insurance"), prefix = c("cheap", "budget"), prefix2 = c("low cost"), suffix = c("quote", "quotes"),

Hello all, I am trying to create a corosync/pacemaker cluster using CentOS 6.0. However, I'm having a great deal of difficulty doing so. Corosync has a valid configuration file and an authkey has been generated. When I run /etc/init.d/corosync I see that only corosync is started. >From experience working with corosync/pacemaker before, I know that this is not enough to have a functioning

does wine opens and works Babylon 8 well ??!! if i installed wine,will Babylon work well on it ?!! hope you will answer me thanks

My target machine uses the same 64-bit registers for integers and floating point. Do I have to specify a different register class for floating point that uses the same set of registers? Is there a target which does this I can copy? thanks, brian

The BGL (Boost Graph Library) defines tie(), which is exactly what the tie() defined in STLExtras.h. The header files of GBL use boost::tie(), and other boost libraries use boost::tie() too. How to resolve the ambiguity for compiler? -- Tzu-Chien Chiu, 3D Graphics Hardware Architect <URL:http://www.csie.nctu.edu.tw/~jwchiu>

I've been doing some experiments with the Boost Graph Library (BGL) and interfacing to llvm's GraphWriter system. I'm using GBL for some custom work and needed a way to hook BGL's write_graphviz into GraphWriter to use the existing display infrastructure. To do this I added a HAVE_BOOST configure item and #ifdef'd the Boost support code in GraphWriter. Is this useful to

The following causes an assertion in recent svn pulls, but not in 2.5. The assertion: llvm-as: /home/bgl/work/llvm-work/include/llvm/ADT/SmallVector.h:125: T& llvm::SmallVectorImpl<T>::operator[](unsigned int) [with T = llvm::Constant*]: Assertion `Begin + idx < End' failed. The .ll code: target datalayout =

On Tue, 2012-05-01 at 19:58 -0500, Peter Bergner wrote: > On Tue, 2012-05-01 at 17:47 -0500, Hal Finkel wrote: > > By default it should build for > > whatever the current host is (no special flags required). To > > specifically build for something else, use: > > -ccc-host-triple powerpc64-unknown-linux-gnu > > or > > -ccc-host-triple

OpenSSH 2.5.1p1 was compiled on two different Linux machines, both with glibc 2.2, libz-1.1.3 and openssl-0.9.6. Both had been running 2.3.0p1 successfully. On both, the new sshd failed: # ./sshd -d -d -d -D debug1: sshd version OpenSSH_2.5.1p1 debug1: load_private_key_autodetect: type 0 RSA1 Disabling protocol version 2. Could not load host key RSA sessions worked. Generating a new DSA

Rebooting to try 2.4.7-ac4, I had Xfree86 crash on exit and hang the machine (it does that once a month or so; this notebook gets booted quite often). After fscking the root and another ext2 partition, the system got to the big ext3 partition and just went dead. No message, no disk activity, no keyboard response. I powered down and rebooted 2.4.7-ac3 patched with ext3-2.4-0.9.5-247ac3, and that

On Sat, 2012-05-12 at 00:47 -0500, Hal Finkel wrote: > On Tue, 01 May 2012 21:25:29 -0500 > Peter Bergner <bergner at vnet.ibm.com> wrote: > > By the strict letter of the 32-bit ABI, the save and restore of > > r31 at a negative offset of r1 is verboten. The ABI states the > > the stack space below the stack pointer is declared as volatile. > > I actually

The following code works on 2.7, but causes an assertion on recent snapshots. Has something changed regarding bitcasts that makes this illegal? The code is: target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:32" target triple = "x86-unknown-unknown" @aa = global [32 x i8] zeroinitializer, align 1 @bb = global [16 x i8] zeroinitializer, align 1 define

On Tue, 01 May 2012 21:25:29 -0500 Peter Bergner <bergner at vnet.ibm.com> wrote: > On Tue, 2012-05-01 at 19:58 -0500, Peter Bergner wrote: > > On Tue, 2012-05-01 at 17:47 -0500, Hal Finkel wrote: > > > By default it should build for > > > whatever the current host is (no special flags required). To > > > specifically build for something else, use:

I've noticed that the max.col function with the default "random" option often gives unexpected results. For instance, in this test, it seems clear what the answer should be: > # second col should always be max > x1 = cbind(1:10, 2:11, -Inf) > > # this works fine > max.col(x1, "first") [1] 2 2 2 2 2 2 2 2 2 2 > > # this gives random answers >

for Spam. In the process of setting up a more effective spam filtering system, I just noticed that bogofilter, which implements extensions of the (a?) "Naive Bayes" text classification approach, will dump out R data frames; the man page suggests how to "integrate" it with R for verification. (sort of, that is). Anyway, for those of you looking for silly and perhaps