A problem with gnome-terminal in Fedora 21, and tracking it down
Today I discovered that Fedora 21 subtly broke some part of my environmentto the extent that gnome-terminal refuses to start. More than that, itrefuses to start with a completely obscure error message:
; gnome-terminalError constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 8
How to set up static networking with systemd-networkd, or at least how I did
I recently switched my Fedora 21 office workstation from Fedora'sold /etc/init.d/network init script based method of network setupto using the (relatively new) systemd network setup functionality,for reasons that I covered yesterday . Thesystemd documentation is a little bit scant and not complete, soin the process I accumulated some notes that I'm going to writedown.
First, I'm going to assume that you're having networkd take overeverything from the ground up, possibly
Why I'm switching to systemd's networkd stuff for my networking
Today I gave in to temptation and switchedmy Fedora 21 office workstation from doing networking throughFedora's old /etc/rc.d/init.d/network init script and its /etc/sysconfig/network-scripts/ifcfg-* system to using systemd-networkd.Before I write about what you have to set up to do this, I want toramble a bit about why I even thought about it, much less wentahead.
The proximate cause is that I was hoping to get
A gotcha with Python tuples
Here's a little somewhat subtle Python syntax issue that I recentlygot to relearn (or be reminded of) by stubbing my toe on it. Let'sstart with an example, taken from our Django configuration:
# Tuple of directories to find templatesTEMPLATE_DIRS = ( "/some/project/directory")
This looks good (and used to be accepted by Django), but it's wrong.I'm being tripped up by the critical difference in Python between' (A)
Why user-hostile policies are a bad thing and a mistake
One reasonable reaction to limited email retention policies beinguser-hostile is to saybasically 'so what'. It's not really nice that policies make workfor users, but sometimes that's just life; people will cope. I feelthat this view is a mistake.
The problem with user-hostile policies is that users will circumventthem . Generously, let's assume that you enacted this policy toachieve some goal (not just to say that you have a policy and perhapspoint to a technical
Limited retention policies for email are user-hostile
I periodically see security people argue for policies and technologyto limit the retention of email and other files, ie to enact policieslike 'all email older than X days is automatically deleted for you'.Usually the reasons given are that this limits the damage done ina compromise ( for example ),as attackers can't copy things that have already been deleted. Theproblem with this is that limited retention periods are clearlyuser hostile.
The theory of limited retention policies is that people will manuallysave the small amount
Using systemd-run to limit something's RAM consumption on the fly
A year ago I wrote about using cgroups to limit something'sRAM consumption , for limiting the resourcesthat make 'ing Firefox could use when I did it. At the time myapproach with an explicitly configured cgroup and the direct use of cgexec was the only way to do it on my machines; although systemd has facilitiesto do this in general, my version could not do this for ad hocuser-run programs. Well, I've upgraded to Fedora 21 and that's nowchanged,
Node.js is not for me (and why)
I've been aware of and occasionally poking at node.js for a fairly long time now, and periodically I've considered writing something in it ;I also follow a number of people on Twitter who are deeply involvedwith and passionate about node.js and the whole non-browser Javascriptcommunity. But I've never actually done anything with node.js andmore or less ever since I got on Twitter and started following thosenode enthusiasts I've been feeling increasingly like I never would.Recently
Link: Against DNSSEC by Thomas Ptacek
Against DNSSEC by Thomas Ptacek ( @tqbf ) is what it says in the title; lucid andto my mind strong reasons against using or supporting DNSSEC. I'veheard some of these from @tqbf before in Tweets (and others areambient knowledge in the right communities), but now that he'swritten this I don't have to try to dig those tweets out and makea coherent entry out of them.
For what it's worth, from my less informed perspective I agree withall
General ZFS pool shrinking will likely be coming to Illumos
Here is some great news. It started with this tweet from AlexReece (which I saw via @bdha ):
Finally got around to posting the device removal writeup for myfirst open source talk on #openzfs device removal!
'Device removal' sounded vaguely interesting but I wasn't entirelysure why it called for a talk, since ZFS can already remove devices.Still, I'll read ZFS related things when I see them go by on Twitter,so I did. And my eyes