On the route down from Flagstaff to Phoenix, we stopped and stayed in Arcosanti. This experimental city is a unique place as it was imagined by an Italian architect who began its construction in the 70s with volunteers from all around the world. Today its construction is still ongoing and people come there to contribute for a certain period of time before going back home (we met a French lady from Britany there, this was weird).
The cool thing about this community is that you can book a room there to stay and live among them for some time. We had dinner and breakfast with them, everything was very cool and very tasty ! We didn’t really know what to expect when arriving there and were amazed by the place and its incredible athmosphere.
We had the feeling of being in another world, far from everything we’re used to. This is the kind of place where you can feel far from everything but close from the earth, a unique experience really. I even had the chance to take a dive in the swimming pool overlooking the surrounding desert.
I couldn’t help but feel strange about how the architecture of this place made me feel like I was walking in the video game Riven !
Today we did shutdown the oldest Gentoo Linux server of our oldest production datacenter. It was running since April, 5th of year 2006 so that’s a total of 2793 days of production level service as a stateful firewall. Its name was stabber, in reference of a vessel in the Eve Online MMORPG which I played a lot at the time.
Our company has been running on Gentoo Linux since 2004 for its Linux platforms and I often hear and experience the astonishment of the other persons I speak to about this : “Gentoo Linux in production, really ?” or “Wow you guys are a bunch of crazy hardcore Gurus”…
As if Gentoo Linux did not meet the production level requirements or the security level you expect from another major (usually not free) distribution and as if you had to master some major skills to have it done…
7 years later, stabber is in my opinion a proof that all those assumptions are wrong.
- I was a junior sysadmin at the time I made this server, we didn’t want to pay for having a proper firewall so we decided to make our own (that’s what Gentoo is to me : simple things done right, no added sugar)
- The rolling updates of Gentoo did not brake our system and it evolved along our infrastructure
- The GLSA kept our server immune to security breaches over the years (thx to the Gentoo security team)
- This server/firewall passed the security tests of both Paypal and Ebay, this looks production level enough to me
We did shutdown this server because it was a single point of failure on an old part of our architecture. Its role has been taken over by two fault tolerant servers/firewalls running… Gentoo Linux of course !
First emerge.log entry
Wed Apr 5 12:53:22 2006 >>> sys-kernel/hardened-sources-2.6.14-r5
Latest uname -a
Linux stabber 2.6.16-hardened-r11 #1 SMP PREEMPT Wed Aug 30 15:51:49 CEST 2006 i686 Intel(R) Xeon(TM) CPU 3.20GHz GenuineIntel GNU/Linux
stabber ~ # echo "je taime" >> last.letter
stabber ~ # shutdown now -h
Dear fellow Gentoo Linux developers, your work makes all this possible, thank you !
Another release, 3 months after the mighty 1.2.8. It seems like upstream has awaken !
- Jonas Johansson fixed VRRP sync group by sending prio 0 when entering FAULT state. This fix will send prio 0 (VRRP_PRIO_STOP) when the VRRP router transists from MASTER to FAULT state. This will make a sync group leave the MASTER state more quickly by notifying the backup router(s) instead of having them to wait for time out.
- Jonas Johansson fixed VRRP to honor preempt_delay setting on
- Jonas Johansson extended VRRP code for faster sync group
- Some nice bug fixes to unicast mode.
Full changelog here !
You should consider this important update if you have a cluster running v2.4.7. It contains a fix for the config servers which can have them possibly disagree on chunks hashes and thus prevent mongos to start or balancing to happen. See this bug for more info.
The famous message queuing server got a nice bunch of bug fixes on a lot of its modules along with some interesting additions such as :
- support for federated queues
- report client authentication errors during connection establishment explicitly using connection.close
- inform clients when memory or disk alarms are set or cleared
- allow policies to target queues or exchanges or both
- offer greater control over threshold at which messages are paged to disk
- allow missing exchanges & queues to be deleted and unbound without generating an AMQP error
- implement consumer priorities
Full changelog here and here.
This is a bug fix release, nothing too big about it as reported by Thomas D (thanks again).
Please note that rsyslog-7.4.4 is being stabilized, mainly for security purposes.
Forget about Marlboro, this Navajo nation area is way more than that. To be honest, you can see the money made from the tax you have to pay to enter the actual park is invested back in the community but I guess there’s more and some drawbacks to it.
Meet the first 10 minutes of rain we experienced during a whole month ! Actually, it was a localized storm and it happened at the perfect moment where we had the most beautiful view. We felt this moment was quite unique and we were excited and glad to experience it. I guess you won’t argue with me after looking at those pictures.
We then headed South towards the North rim of Grand Canyon, unfortunately the nights were already cold out there so the rangers did advise against sleeping in the car. We thus visited Point Imperial and stayed for the sunset. This was our first encounter with the Grand Canyon and it was amazing.
It was dark when we got out of there, we had to drive very carefully to avoid the numerous deers along the road. We had planned to sleep in Page but we hit a detour due to road work and had to take a huge detour which took us to Tuba City.
I could not stand driving one more mile but the only three hotels of the whole area were full. One person from the front desk of a hotel advised us to go to the nearby Greyhills Inn which remains one of the most exotic experience we had in Indian territory. We slept in a room in the Tuba City High School as they do rent rooms to outsiders ! We were welcomed nicely in this old fashioned place operated by the local Navajo people.
We visited Page and its (too) touristic area the next day along with the famous (and so crowded) Antelope Canyon and Horseshoe Bend.
After the Death Valley, we headed North to reach Bryce Canyon. On the way up, we did take a quick detour to cruise Las Vegas by car but didn’t stop there.
We had a pleasant night in a very old fashioned motel near Bryce Canyon where the tenant asked me if I really was French because “the French are usually blond and don’t have such dark hair as you mister”.
I’m willing to bet a great deal on the fact that the vast majority of us are brown/dark haired… Mister blond @Lujeni is NOT representative of us French people !
One of the reasons I switched from KDE to i3wm is that I love and need terminals. In my field of work you happen to spawn dozens of them and you always end up running out of space / workspaces.
Yakuake has been a real ally to me for years as I intensively use a drop-down terminal for sporadic usages. It is hard to match Yakuake’s efficiency and ability to split terminals but I couldn’t stand all those KDE dependencies anymore; I had to find a great drop-down terminal solution in i3.
So I started looking at other drop-down terminals such as Terra and Guake but they didn’t fit my low dependencies and features list requirements.
My current solution is to take advantage of the floating mode of i3, use it with my beloved terminator et voilà ! Nothing more to install, no extra dependency, using the same shortcuts of my main $TERMINAL and all of its features
The idea is simple, we’ll create a special profile in terminator and have it spawned in floating mode upon i3 start. This profile must cover the following drop-down behaviors :
- respond to a configurable show/hide key binding
- present a drop-down terminal at the center of the screen
- the interface should be dead simple and efficient and support splitting
Just edit your terminator configuration in ~/.config/terminator/config
hide_window = F1
exit_action = close
scrollback_lines = 10000
background_image = None
scroll_on_output = False
show_titlebar = False
That’s my minimal config, you can add your own stuff to it as well. Now we only need to configure i3 to spawn this profile at login and have it in floating mode.
exec terminator -c dropdown -p dropdown -T "Le Terminator" -H --geometry=1550x800
for_window [class="Terminator" instance="dropdown"] floating enable
That’s as simple as this.
There’s still one limitation which I didn’t come across yet :
- Unlike Yakuake, our drop-down terminator has a fixed geometry which you must set in the i3 config above and does not support percentage values. So if you have multiple screens of different resolutions it won’t adapt on them based on the screen you want to show your drop-down terminator.
So long, Yakuake !
First of all, I’d like to point out a quite big change in the Gentoo mongodb package. The Chromium team responsible for the v8 package decided to stop its maintenance as it was too much trouble to be used efficiently as a shared library (mainly due to upstream’s breakage behavior). Even tho I don’t like bundled libraries on sources, I understand my fellow developers point of view.
I’ve thus been asked and did switch the mongodb ebuild to use the bundled v8 library. This means that mongodb has no more v8 packaging dependency now. The mongodb v2.2.x users are advised that since upstream does not bundle the v8 lib in their source, I dropped the v8 USE flag and support altogether on this version (it’s not officially supported anyway) !
This being said, I’ll drop the old ebuilds from tree on the next releases iterations.
Yet another bugfix release on this unfamous 2.4.x series :
- Fixed over-aggressive caching of V8 Isolates
- Removed extraneous initial count during mapReduce
- Cache results of dbhash command
- Fixed memory leak in aggregation
BSON parser hardening and fixes in the connection pool mechanism. More info here.