Iustin Pop: Short trip to Opio en Provence
Short trip to Opio en Provence
I had a short work-related trip this week to Opio en Provence. It was
not a working trip, but rather a team event, which means almost a
vacation!
Getting there and back
I dislike taking the plane for very short flights (and Z rich-Nice is
indeed only around one hour), as that means you're spending 3 as much
going to the airport, at the airport, waiting to take off, waiting to
get off the plane, and then going from the airport to the actual
destination. So I took the opportunity to drive there, since I've
never driven that way, and on the map the route seemed reasonably
interesting. Not that it's a shorter trip by any measure, but seemed
more interesting.
Leaving Z rich I went over San Bernardino pass, as I never did that
before. On the north side, the pass is actually much less suited to
traffic than the Gotthard pass (also on the north side), as you
basically climb around 300m in a very short distance, with very sharp
hairpins. There was still snow on the top, and the small lake had lots
of slush/ice floating on it. As to the south side, it looked much more
driveable, but I'm not sure as I made the mistake of re-joining the
highway, so instead of driving reasonably nice on the empty pass road,
I spent half an hour in a slow moving line. Lesson learned
Entering Italy was the usual Como-Milan route, but as opposed to my
other trips, this time it was around Milan on the west (A50) and then
south on the A7 until it meets the A26 and then down to the
coast. From here, along the E80 (Italian A10, French A8) until
somewhere near Nice, and then exiting the highway system to get on the
small local roads towards Opio.
What I read in advance on the internet was that the coastal highway is
very nice, and has better views of the sea than the actual seaside
drive (which goes through towns and is much slower). I should know
better than trust the internet , and I should read maps instead,
which would have shown me the fact that the Alps are reaching to the
sea in this region, so The road was OK, but it definitely didn't feel
like a highway: maximum allowed speed was usually either 90km/h or
110km/h, and half the time you're in a short tunnel, so it's sun,
tunnel/dark, sun, dark, and you're eyes get quite tired from this
continuous switching. The few glimpses of the sea were nice, but the
road required enough concentration (both due to traffic and the amount
of curves) that one couldn't look left or right.
So that was that a semi-failure; I expected a nice drive, but instead
it was a challenge drive If I had even more time to spend, going
back via the Rhone valley (Grenoble, Geneva, Z rich) would have been a
more interesting alternative.
France
Going to France always feels strange for me. I learned (some) French
way before German, so the French language feels much more familiar to
me, even without never actually having used it on a day-to-day basis;
so going to France feels like getting back to somewhere where I
never lived. Somewhat similar with Italian due to the language
closeness between Romanian and Italian, but not the same feeling as I
didn't actually hear or learn Italian in the childhood.
So I go to France, and I start partially understand what I hear, and I
can somewhat talk/communicate. Very weird, while I still struggle with
German in my daily life in Z rich. For example, I would hesitate
before asking for directions in German, but not so in French,
unrelated to my actual understanding of either language. The brain is
funny
The hotel
We stayed at
Club Med Opio-en-Provence,
which was interesting. Much bigger than I thought from quick looks on
the internet (this internet seems quite unreliable), but also better
than I expected from a family-oriented, all-inclusive hotel.
The biggest problem was the food - French P tisserie is one of my
weaknesses, and I failed to resist. I mean, it was much better than I
expected, and I indulged a bit too much. I'll have to pay that back
on the bike or running
The other interesting part of the hotel was the wide range of
activities. Again, this being a family hotel, I thought the organised
activities would be pretty mild; but at least for our group, they
weren't. The
mountain bike ride
included an easy single-trail section, but while easy it was
single-trail and rocky, so complete beginners might have had a small
surprise. Overall it was about 50 minutes, 13.5km, with 230m altitude
gain, which again for sedentary people might be unusual. I probably
spent during the ride one of the deserts I ate later that day
The
"hike" they organised for another sub-group was also interesting,
involving going through old tunnels and something with broken water
pipes that caused people to either get their feet wet or
monkey-spidering along the walls. Fun!
After the bike ride, on the same afternoon, while walking around the
hotel, we found the Ecole de Trap ze volant open, which looked way
to exciting not to try it. Try and fail to do things right, but
nevertheless it was excellent and unexpected fun. I'll have to do that
again some day when I'll be more fit!
Plus that the hotel itself had a very nice location and olive garden,
so short runs in the morning were very pleasant. Only one cookie
though each
Back home
and then it was over; short, but quite good. The Provence area is
nice, and I'd like to be back again someday, for a proper
vacation longer and more relaxed. And do the trap ze thing again,
properly this time.
The other interesting part of the hotel was the wide range of
activities. Again, this being a family hotel, I thought the organised
activities would be pretty mild; but at least for our group, they
weren't. The
mountain bike ride
included an easy single-trail section, but while easy it was
single-trail and rocky, so complete beginners might have had a small
surprise. Overall it was about 50 minutes, 13.5km, with 230m altitude
gain, which again for sedentary people might be unusual. I probably
spent during the ride one of the deserts I ate later that day
The
"hike" they organised for another sub-group was also interesting,
involving going through old tunnels and something with broken water
pipes that caused people to either get their feet wet or
monkey-spidering along the walls. Fun!
After the bike ride, on the same afternoon, while walking around the
hotel, we found the Ecole de Trap ze volant open, which looked way
to exciting not to try it. Try and fail to do things right, but
nevertheless it was excellent and unexpected fun. I'll have to do that
again some day when I'll be more fit!
Plus that the hotel itself had a very nice location and olive garden,
so short runs in the morning were very pleasant. Only one cookie
though each
Back home
and then it was over; short, but quite good. The Provence area is
nice, and I'd like to be back again someday, for a proper
vacation longer and more relaxed. And do the trap ze thing again,
properly this time.
The idea is simply to have one coherent place with pointers to all the stuff we have and provide, without repeating nor replacing other documentation.
Time for new release! We just updated rfoaas on
How to manage your photos? That is probably the biggest question for anyone doing anything with a photo camera. As resolutions of cameras grow, the data we have to manage is growing ever. In my case I am talking about more than 50000 photos and videos measuring up to about 200Gb of disk space, constantly growing. There are several photo management softwares out there, I guess the most commonly used ones are
There is no clear winner here, unfortunately. Both have their strength and their weaknesses. And as a consequence I am using both in parallel.
Before I start a clear declaration: I have been using Shotwell for many years, and have myself contributed considerable code to Shotwell, in particular the whole comment system (comments for photos and events), as well as improved the
So in short Shotwell distinguishes between disk layout and album/event names.
In digiKam there is a strict connection between disk layout and album names 1:1. Albums are directories. One can adjust the viewer to show all photos of sub-albums in the main album, and by this one can achieve the same effect of merging all photos of my friend and myself. The good thing in this approach is that one can easily have sub-albums: Imagine a trip to three different islands of Hawaii during one trip. This is something easy to achieve in digiKam, but hard in Shotwell.
Other organization methods
Both Shotwell and digiKam support tags, including hierarchical tags and rating (0-5 stars). Shotwell has in addition a quick flag action that I used quite often for initial selecting photos, as well as accepted and rejected. digiKam also has so called picks (no pick, reject, pending, accepted), and colors (not used by now). Both programs have some face detection support, but also this I haven t used.
So in the organization respect there is no clear winner. I like the Event idea of Shotwell, or better, the separation of events from the disk structure. But on the other hand, Shotwell does not allow for sub-albums, which is also a pain.
No clear winner draw
Offline storage
That is simple: Shotwell: forget it, not reasonably possible. One can move parts to an external HD, then unplug it, and Shotwell will tell you that all the photos are missings. And when you plug the external HD in, it will redetect them. But this is not proper support, just a consequence of hash sum storage. Also separation into several libraries (online and offline) is not supported.
On the other hand, digiKam supports multiple libraries, partly offline, without a hinch. I would love to have this feature in Shotwell, because I need to free disk space, urgently!!!
Clear winner: digiKam
Sharing
Again here my testing is very restricted I am using 
On the other hand digiKam has a very barebone interface to Piwigo you can upload photos to an existing album and resize them, but that is already everything. One also needs to say that the list of supported services in digiKam is by far longer than the one in Shotwell, but the main services (usual suspects) are supported in both.
Clear winner: Shotwell (but I haven t tested other upload services).
Editing
The editing capabilities of Shotwell are again very restricted: red eyes, resize, levels, .
Clear winner: digiKam
Conclusions
While I am still working with both, I actually would love to move completely to digiKam. I simply cannot stand the Gnome 3 philosophy of reducing functionality to a minimal for dummy users. There is a market for that, sure, but I am not one of it. Unfortunately, the missing Event support, and much more the completely minimal support for Piwigo sharing in digiKam is a big show stopper at the moment. Even after testing the upcoming digiKam 5.0 version for some time, I didn t see any improvement wrt to sharing.
That leaves me with the only option to continue working with both programs, and hope to get a new bigger SSD before the current one runs out of space. Of course I could start hacking into the digiKam source maybe I do this when I have a bit more time to add proper Piwigo support.





In the ARM world, to which I am still mostly a newcomer (although I've been already playing with ARM machines for over two years, I am a complete newbie compared to my Debian friends who live and breathe that architecture), the most common way to distribute operating systems is to distribute complete, already-installed images. I have
For testing kvm/qemu, prebaked images cloud images are nice. However, there is a few steps to get started. First we need a recent Qemu (2.5 is good enough). An efi firmware is needed, and cloud-utils, for customizing our VM.