search for: netel

...as reposTools from bioconductor is using it. Then I was suggested to report this error here. In general our R-161 installation (Linux/i686) works well. Also running 'R CMD INSTALL ...' in a common shell is ok. Only above method fails. Does anyone have a suggestion for me? Thanks, Markus Neteler

...- fixed table export to PostgreSQL - added make.names() to polish column names for R usage (maybe some of these patches are already in the BioConductor-CVS) Now the interface seems to work smoothly. Thanks to Steno Fontanari and Dirk Eddelbuettel for their assistance. Kind regards Markus Neteler -- Markus Neteler <neteler at itc.it http://mpa.itc.it ITC-irst, Istituto per la Ricerca Scientifica e Tecnologica MPBA - Predictive Models for Biol. & Environ. Data Analysis Via Sommarive, 18 - 38050 Povo (Trento), Italy

Full_Name: Markus Neteler Version: 1.0.0 OS: Linux 2.2.10/i686 Submission from: (NULL) (130.75.72.37) Hi, I wanted to "check" the R.GRASS GIS interface from Roger Bivand: http://www.geog.uni-hannover.de/grass/statsgrasslist.html using R CMD check --vsize=10M GRASS but: [error message shortened] > G <...

While using 5.1-RELEASE, I find that if my application program seg faults, it produces "programname.core"; but it is 0 bytes. I ran the exact same program on another machine that was running 4.4-RELEASE, and I do get a core file that I can use with gdb. I'd really appreciate if someone could help me resolve this. Additional details: - It is not specific to the application

...this morning, and that didn't seem to help much. I'm running on a single-CPU Athlon (i386, not amd64) machine. Are other people here running nessus (2.2.6) with the "registered plugins"? (not the commercial registration). -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu

Hi folks, While investigating OpenBSD's cron implementation, I found that they set the systemwide crontab (a.k.a. /etc/crontab) to be readable by the superuser only. The attached patch will bring this to FreeBSD by moving crontab out from BIN1 group and install it along with master.passwd. This change should not affect the current cron(1) behavior. Cheers, -- Xin LI <delphij frontfree

...n is mounted: /dev/ad0s2g on /usr (ufs, local, soft-updates) This is only a test system, so it isn't much of a problem for me. I just thought that it was odd enough that I should mention it. Has anyone else seen behavior like this? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu

i am invoking op from a python proggy which does an op.system() of op chmod 640 /usr/local/etc/tac_plus.conf i get "Permission denied by op" % ls -l /usr/local/etc/op.access -r-------- 1 root wheel 149 Jan 13 07:41 /usr/local/etc/op.access % cat /usr/local/etc/op.access # 2007.01.13 # #DEFAULT users=src # chown /usr/sbin/chown $* ; users=src chmod /bin/chmod $* ; users=src

All: I'm posting this to FreeBSD-security (rather than FreeBSD-net) because the problems I'm seeing appear to have been caused by spyware, and because they constitute a possible avenue for denial of service on FreeBSD machines with default installs of the operating system. Several of the FreeBSD machines on our network began to act strangely during the past week. Some have started to

If yes, how do I set it up in the yml file? Thanks. - amateur Railist -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060818/6690a4e2/attachment.html

Dear All, Does anyone know of any GIS packages for R? I know that there are GIS facilities for S-Plus (eg Arc Info), and am looking for freeware equivalents. Best wishes, Sam Brown ----------------------------------------------------------- Sam Brown sam at zoo.cam.ac.uk Department of Zoology tel +44 1223 330933 Downing Street fax +44 1223 334466

I'm just getting into regular use with cvsup (way over do on that one), and I tried to specify a tag=. in the cvsup file. Here's the file: # This file specifies src files are to be uploaded. *default host=cvsup2.FreeBSD.org # *default tag=RELENG_5_1_0_RELEASE *default tag=. *default prefix=/usr *default release=cvs delete use-rel-suffix compress *default base=/usr/local/etc/cvsup

I spent some time debugging a failing Scp that turned out to be caused by the remote shell producing messages on Standard Output that aren't part of the SCP protocol. Scp from a remote system works by running another Scp on the remote system. The remote Scp writes SCP protocol messages (and file data) to its Standard Output, which the local Scp sees as Standard Input. But it's

All, Given the amount of NULL-pointer dereference vulnerabilities in the FreeBSD kernel that have been discovered of late, I've started looking at a way to generically protect against the code execution possibilities of such bugs. By disallowing userland to map pages at address 0x0 (and a bit beyond), it is possible to make such NULL-pointer deref bugs mere DoS'es instead of code

Dear FreeBSD users and system administrators, While the FreeBSD Security Team has traditionally been very good at investigating and responding to security issues in FreeBSD, this only solves half of the security problem: Unless users and administrators of FreeBSD systems apply the security patches provided, the advisories issued accomplish little beyond alerting potential attackers to the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On October 31st, FreeBSD 5.3 and FreeBSD 5.4 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Users of either of those FreeBSD releases are strongly encouraged to upgrade to FreeBSD 5.5 or FreeBSD 6.1 before that date. In addition, the FreeBSD 6.0 End of Life is presently scheduled

First, I hope that this message is not considered flame bait. As someone who has used FreeBSD for for 5+ years now, I have a genuine interest in the integrity of our source code. Second, I hope that this message is not taken as any form of insult or finger pointing. Software without bugs does not exist, and I think we all know that. Acknowledging that point and working to mitigate the risks