Finnish Debian developers and others interested in Debian in or close to Helsinki: we're having a Debian jessie release party on Saturday, at 15:00 (Finnish time), in Helsinki, pub Kaisla in Kaisaniemi.
sazius likes this.
My current #backup setup at home: live data is all on my laptop; gets backed up to backup server at home, and online, and two USB drives.
There's also a file server at home, which also gets backed up to the backup server at home, and to USB drives. Due to the amount of data, it doesn't get backed up online, yet.
http://obnam.org/format-green-albatross/ is my current best idea for the next generation Obnam repository format. Review is welcome.
Wow, ditching the b-trees is a bold move.
Will this make obnam less sensitive to roundtrip latency? Sounds like you can stream out data into a bag and then do essentially one update at the end of the metadata..
The bag.1 format seems possibly suboptimal, if only part of a bag needs to be accessed to restore, you'd need to download the whole thing. An offset allowing random access might be better?
I suspect this will also make pruning old generations more expensive, since some bags will need to be rewritten with parts removed.The files storing B-tree nodes are not cacheable, since they get updated in place. Or rather, they are cacheable, but cache management is difficult and potentially quite expensive. The new design aims to not ever update files in place and so would be much, much more cacheable, avoiding a lot of rounttrips, I hope.
I expect bags to be somewhat small (perhaps as small as 64 k, but probably more like 1 meg), so that the overhead of wasted space and downloading too much is kept reasonable. I don't plan on rewriting bags when data is removed, normally, but there might be a "packing" function or option to force that.
I hadn't thought about random access to a bag file. I shall ponder on this.
Just had a two-hour chat with a remote friend, over Mumble. It's so much nicer than Skype: less distortion, much less lag.
At work, I'm written a big bunch of code and now i'm reviewing it before I show it to others. Such bad code, several methods are more than five lines long!
When I was young, I found it exciting that I could write functions that were several hundred lines long. Then I realised that was silly, so I shortened them to under a hundred. Than to under 50. Then to under 25. Now I go for 5. Old age and senility...
I recently refactored some signal processing code at work. My goal was to both make the code more maintainable as well as reverse engineer what it was doing. Most of the code was contained in a few large functions that could not be understood readily. I broke it up into many smaller functions that did one thing, keeping the code otherwise the same, and not only is it now easier to understand, but the compiler produced faster code. About 15 to 30 % reduction in runtime. (I verified the new code has exactly the same signal response as the old code.)
Made a new wallet for myself, out of duct tape and copper mesh.
It's not paranoia if you've just watched Citizenfour.
I quite like GNOME 3 (the version in jessie), even if it no longer works with xmonad. I make do with shellshape, though.
It bothers me that the visual difference between active and inactive windows is so slight. I would like a strong difference. Back many years ago Ubuntu's GNOME theme had an orange title bar for the active window, which was nice. I'd switch the theme from the default, but the default theme is otherwise very good.
That article discusss the gender discrimination suit by Ellen Pao against a ventrue capital firm, and quotes Fran Maier as "It puts pressure on venture capital to improve its numbers, because six percent is just awful".
That is, indeed, quite awaful.
Free software has much worse numbers. Still.
Happiness is cleaning up your own ugly code, when you have a good test suite. In this case, Obnam's backup plugin, which has grown rather big over the years, and hasn't really been clean up ever.
Obnam 4.1 released: http://blog.liw.fi/posts/obnam-april-2015/
Also, I read in Schneier that reversing your infinite one-time pad makes it more secure. Haskell makes this really easy to do thanks to its support for infinite lists you can simply
(reverse (show e))-- although it may need some work to run in constant memory.
Or you could use my implementation of a time-reversed infinite steam of Joycean conciousness, which I implemented in Haskell and already runs in constant memory.
Anyhoo, clearly rewriting Obnam in Haskell is your next logical step.
I've been told today that if I give a talk to a classroom of 15 and 16 year olds, and they sit quietly, look at me, but show now visible reaction to anything I say or do, it's a roaring success. One of them even put away his smartphone.
Someone who edits Wikipedia could perhaps update the Obnam page to say the current version is 1.9. See
for an authoritative reference.
Remember to make a backup of your backups before you backup with a new version of the backup program, so you can restore you backups if the new version is buggy.
This isn't a joke. It's what I do when I prepare a new Obnam release. :)
Agreed, I have seen many people burnt by bad backup software (usually propriety). People need to understand that the proper model to use with backup software is “trust but verify”. The people that I saw get burnt just trusted only to find out in an emergency that some clutch or other prevented them restoring from the backup, or that the backup software hadn't backuped important files.
Today I find it offensive that Jenkins doesn't keep its configuration in git.
I've built Continuous Integeration (or Delivery) systems around Jenkins that keep all config in git, and then instruct Jenkins via its API to do things according to the config-in-git, but it's a pain.
Software that's hard to deploy, or hard to package for a Linux distro, is probably not great software.
Software that's been grown in place and hasn't ever been installed to a fresh location is almost certainly not great software.
Claes Wallin (韋嘉誠) shared this.
Obnam version 1.9 released. It's my little backup program.
Have you made a backup today?
Greg Grossmeier shared this.