search for: bdavies

Hello Samba folks, I have come across a problem with smbclient 3.5.6 when I use the tar 'x' feature. Pathnames that work out to be 100 characters long are extracted incorrectly: bash-3.2$ tar tvf ugh.tar -rw-r--r-- bdavis/Domain Users 137 2012-12-07 13:36:40 a50characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABCD/a49characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABC -rw-r--r-- bdavis/Domain Users

I've just gotten my first machine to join the domain, and now I'm trying to log in as a normal user. I get this error in windows "The system could not log you on. Make sure your username and password are correct (bla bla...)". However, when I check the log for that machine it says at the end that authentication succeeded? /var/log/samba/log.melisa: (log level=2, debug

Hi, I'm currently trying to translate LLVM IR language to VPO .dec file specification. I'm using LLVM source parser in the same way that it is used in tools llc or llvm-as. One issue I'm having is I cannot find any static values. For example, in a global declaration i.e. '@a = global i32 7, align 4' I cannot get '7' from the parsed structure. Similarly (sort

Looking through this mailing list's archives, I've found that the most common fix attempted for removing phi instructions is to use the reg2mem pass. However I'm also finding that this does no guarantee the removal of all phi instructions. I want to write a pass to remove phi instructions without changing register/memory usage. Does this sort of translation of phi

...the encryption functions into it. > In NT there was a registry entry to turn off the requirement for > encrypted passwords. Does anyone know of a similar entry for the > Win98 registry that I can put in so I can access my files? > Any help would be much appreciated.> Bob Davies> bdavies@sagus-security.com

Working with the LLVM source, if I have an Instruction object by itself (created by parsing a module using LLVM's parser), is there a way to get its operands/destination? e.g. '%add = add nsw i32 %tmp2, %tmp1' Being able to get some form of %add, %tmp2, and %tmp1? All I can pull is the operation itself, i.e. that it's an add. Thanks, Brandon

Hi, What I'm currently working on is a translation from LLVM IR to a register transfer list format used in VPO. If my understanding of ConstantExpr is correct, that they can be evaluated at compile-time, how can I simply have them be evaluated but have the code still remain in IR format? For example, in: store i32 1, i32* getelementptr [6 x i32]* @arr, i32 0, i32 0 the getelementptr

We have a Centos 5.8 32 bit server that has been printing fine since we installed it. Recently, we also installed a new server with 64 bit Centos 6.4. On both servers, we print all reports with a simple 'lp' command. The new server prints all reports with double spacing. We looked at the text file that is being printed and found that it contains both '<cr>' and

Hi, I'm working on translating LLVM IR to VPO register transfer list format (MIPS architecture). One problem I have is that static floating point values in IR are found throughout the module, but I need to move those constant values out to a .data section, and declare memory for them globally. Is there a way that I can (given a Module object after parsing a .ll file) run through all

Hi, I was wondering how exactly LLVM handles the ConstantExpr, specifically GEP ConstantExpr, in code generation. From what I'm reading, translating these Constant Expressions into Instructions can slow the code, so I'd like to be able to handle ConstantExpr in the same way that LLVM code generation does. Thanks, Brandon

Let's say I have the following IR code: 21> %tmp = load i32* @myrand.z, align 4 22> %tmp1 = and i32 %tmp, 5535 23> %tmp2 = mul nsw i32 %tmp1, 36969 24> %tmp3 = ashr i32 %tmp, 16 And I have an Instruction *inst that is the instruction on line 22. then have the code: Use *operand1 = &(inst->getOperandUse(0)); I expect that operand1->getNext() will return the the Use*

Somebody went away on vacation! The main site for r: http://www.R-project.org/ is just a generic index page (nothing there about R.) I was able to get info at the Austrian site, tho. Bob Davies -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or

I'm having a problem with the new vixie-cron rpm for CentOS 4.1 when updating via yum. It complains with the message: Error: Missing Dependency: pam >= 0.77-66.8 is needed by package vixie-cron I got this error from calling 'yum update' on a clean install from the 4.1 isos. This version of pam is available in the 4.2 beta repository, but not the 4.1 repository. Did something

We are running Centos 5.6. All was fine until yesterday. I attempted to tar a 14KB work file to a USB floppy (/dev/sdb) for transport to another server. Unfortunately, I keyed in 'tar cvf /dev/sda filename' instead of 'tar cvf /dev/sdb filename'. /dev/sda is our main (boot/root/apps) scsi hard drive. I realized my mistake, but it was too late. The system is still

Any rpart user: I am trying to construct an rpart tree using a subset of the data and it will occasionally fail when predicting a categorical response variable. The reason that rpart fails is that the subset does not contain each of the categories present in the original data. For example, in the car.test.frame example, a subset that has all the categories except "Small" will not

A few weeks back I posted that the subset feature of rpart was not working when predicting a categorical variable. I was able to figure out a simple solution to the problem that I hope can be included in future editions of rpart. I also include a fix for another related problem. The basic problem is that when predicting a categorical using a subset, the subset may not have all the categories

(Apparently, I posted this to the wrong place. I am hopefully posting this is the correct place now. If not, please advise.) A few weeks back I posted that the subset feature of rpart was not working when predicting a categorical variable. I was able to figure out a simple solution to the problem that I hope can be included in future editions of rpart. I also include a fix for another related