The new Dropbox

Post by slig » Thu, Jun 13, 2019, 1:40 PM UTC

rsync wrote: post #535

bubblethink wrote: post #500

Earlier quoted context omitted.

I have always been intrigued by your service, and will probably try it at some point for a smallish setup for important data, but whenever I think of backups in the TB range, it gets way out of budget (even after accounting for borg or other discounts). Do you have any plans to compete on pricing with other popular cloud/storage providers? I understand that this is a different product for a different audience.

"Do you have any plans to compete on pricing with other popular cloud/storage providers?" We try to keep out pricing very roughly inline with Amazon S3. If you know to look for the discount signup rates it should be very slightly cheaper than S3. We can't promise customers support from real UNIX engineers and also match B2 pricing. I'm happy with that and plan to continue on that path ... We would be very happy to ha…

Post by rsync » Thu, Jun 13, 2019, 2:16 PM UTC

dual_basis wrote: post #560

rsync wrote: post #547

Earlier quoted context omitted.

"I wonder if it has improved since." Unison is very interesting and it is, indeed, very special in that it solves the very specific use-case of my parent post. However, my own opinion, and that of just about everyone who cares about backup tools is that 'borg' is the "one true way": https://www.stavros.io/posts/holy-grail-backups/

What about restic? https://restic.net/

Post by ktpsns » Thu, Jun 13, 2019, 2:53 PM UTC

mzs wrote: post #541

bigiain wrote: post #536

Earlier quoted context omitted.

"Please wait: backing up /dev/urandom - 0% of NaN" (To be fair, anyone who tries to backup /dev deserves whatever they get...)

$ echo /dev/urandom | cpio -o | xxd -a 1 block 00000000: 3037 3037 3037 3737 3737 3737 3030 3030 0707077777770000 00000010: 3031 3032 3036 3636 3030 3030 3030 3030 0102066600000000 00000020: 3030 3030 3030 3030 3031 3737 3737 3737 0000000001777777 00000030: 3133 3436 3430 3530 3035 3730 3030 3031 1346405005700001 00000040: 3530 3030 3030 3030 3030 3030 2f64 6576 500000000000/dev 00000050: 2f75 7261 6e64 6f6d 0030 373…

Post by bradam » Thu, Jun 13, 2019, 3:18 PM UTC

Post by mzs » Thu, Jun 13, 2019, 3:49 PM UTC

ktpsns wrote: post #565

mzs wrote: post #541

Earlier quoted context omitted.

$ echo /dev/urandom | cpio -o | xxd -a 1 block 00000000: 3037 3037 3037 3737 3737 3737 3030 3030 0707077777770000 00000010: 3031 3032 3036 3636 3030 3030 3030 3030 0102066600000000 00000020: 3030 3030 3030 3030 3031 3737 3737 3737 0000000001777777 00000030: 3133 3436 3430 3530 3035 3730 3030 3031 1346405005700001 00000040: 3530 3030 3030 3030 3030 3030 2f64 6576 500000000000/dev 00000050: 2f75 7261 6e64 6f6d 0030 373…

How does this work? Looks like a bug in xxd for me (o.O)

  $ PAGER='col -bx' man 5 cpio | awk '$1 == "mode" { print; while (getline) print }' | head
  mode    The mode specifies both the regular permissions and the file
          type.  It consists of several bit fields as follows:
          0170000  This masks the file type bits.
          0140000  File type value for sockets.
          0120000  File type value for symbolic links.  For symbolic links,
                   the link body is stored as file data.
          0100000  File type value for regular files.
          0060000  File type value for block special devices.
          0040000  File type value for directories.
          0020000  File type value for character special devices.
  $ echo /dev/urandom | cpio -o | dd bs=6 skip=3 count=1 | od -tc
  1 block
  1+0 records in
  1+0 records out
  6 bytes transferred in 0.000025 secs (239675 bytes/sec)
  0000000    0   2   0   6   6   6                                        
  0000006