search for: unduplicate

An embedded and charset-unspecified text was scrubbed... Name: ??????????? URL: <https://stat.ethz.ch/pipermail/r-help/attachments/20100209/db12d14b/attachment.pl>

Hi, I would like to avoid the following situation: SRC has: -rwxr-xr-x 1 root staff 1596328 2005-04-29 17:34 libc-2.3.3.so -rw-r--r-- 1 root staff 193 2005-04-29 17:34 libc.so lrwxrwxrwx 1 root staff 13 2007-02-05 15:06 libc.so.6 -> libc-2.3.3.so DEST has: -rwxr-xr-x 1 dale dale 1558836 2008-02-07 12:25 libc-2.3.6.so -rw-r--r-- 1 dale dale 193 2008-02-07 11:46 libc.so lrwxrwxrwx

I am using rsnapshot <http://www.rsnapshot.org/> to make snapshots of my filesystem. rsnapshot uses rsync to do all the heavy lifting. I was recently browsing my snapshots and discovered that none of the excluded files or files deleted in the source are getting deleted from the snapshot. rsnapshot calls rsync like this: /usr/bin/rsync -a --delete --numeric-ids --relative --delete-excluded

https://bugzilla.samba.org/show_bug.cgi?id=4412 Summary: --dry-run output inaccurate due to implied symlink Product: rsync Version: 2.6.9 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

...ate function is defined to return the object itself: >> >> SEXP vector_dulplicate(SEXP x, Rboolean deep) { >> return(x); >> } >> > > So this is a violation of of the contract. <youraltrep>_duplicate *must* > do an actual duplication. Returning the object unduplicated when duplicate > is called is going to have all sorts of unintended negative consequences. > R's internals rely on the fact that a SEXP that has been passed to > DUPLICATE has been duplciated and is safe to modify inplace. > > > >> In R an ALTREP object will behave like...

Full_Name: Henrik Bengtsson Version: 1.6.0, 1.5.1 OS: WinXP Pro Submission from: (NULL) (128.250.252.82) The following example, which I tested on both R v1.5.1 and R v1.6.0 on WinXP Pro, shows the problem I encountered when trying to use the class attribute of an environment: # Define method print() for class Environment C print(e) # gives: # [1] "An Environment!" # Exit [R]

...in ALTREP > > If the duplicate function is defined to return the object itself: > > SEXP vector_dulplicate(SEXP x, Rboolean deep) { > return(x); > } > So this is a violation of of the contract. <youraltrep>_duplicate *must* do an actual duplication. Returning the object unduplicated when duplicate is called is going to have all sorts of unintended negative consequences. R's internals rely on the fact that a SEXP that has been passed to DUPLICATE has been duplciated and is safe to modify inplace. > In R an ALTREP object will behave like an environment (pass-by-refere...

Hello, I have encountered two bugs when using ALTREP APIs. 1. STDVEC_DATAPTR >From RInternal.h file it has a comment: /* ALTREP support */ > void *(STDVEC_DATAPTR)(SEXP x); However, this comment might not be true, the easiest way to verify it is to define a C++ function: void C_testFunc(SEXP a) > { > STDVEC_DATAPTR(a); > } and call it in R via > a=1:10 > >

I just subscribed to this list so in case this subject has already been discussed at length, my apologies. I have been waiting for btrfs forever. I have been waiting for it to become reasonably stable. In the wake of escalating problems with my old hardware RAID setup, I decided now was the time to make the transition. At this point I have been completely transitioned to btrfs for nearly

...n the object itself: >>> >>> SEXP vector_dulplicate(SEXP x, Rboolean deep) { >>> return(x); >>> } >>> >> >> So this is a violation of of the contract. <youraltrep>_duplicate *must* >> do an actual duplication. Returning the object unduplicated when duplicate >> is called is going to have all sorts of unintended negative consequences. >> R's internals rely on the fact that a SEXP that has been passed to >> DUPLICATE has been duplciated and is safe to modify inplace. >> >> >> >>> In R an AL...

...on containing a kernel revision less than this is vulnerable. ======================================================================= DETAILS TCP is a reliable connection-oriented protocol which requires the completion of a three way handshake to establish a connection. To implement reliable and unduplicated delivery of data, the TCP protocol uses a sequence based acknowledgment system. During connection establishment each host selects an initial sequence number which is sent in the first packet of the connection. Each subsequent byte transmitted in the TCP connection is assigned a sequence number. T...