[17:16] <larsks> Anyone: is the difference between _read_hostname and _read_system_hostname supposed to be that the former returns the current (transient) hostname, and the latter return the persistent hostname?
[17:24] <larsks> In particular, can _read_hostname be implemented pretty much for all distributions just by calling the `hostname` command, leaving the distro-specific stuff in _read_system_hostname (and, presumably, _write_hostname)?
[17:27] <smoser> larsks thats a good question. i'd bzr blame to see if there are any hints.
[17:28] <larsks> Not really.  It all stems from harlowja 's work in 11b9899c4eec7a73e5dc2ae1fa25184b2ca5c8e1.
[17:28] <larsks> Hey, harlowja, around?
[17:28] <larsks> Err, sorry.
[17:29] <larsks> That's a git commit hash that won't do anybody any good.
[17:29]  * larsks tries to figure out how the bzr reference...
[17:39] <larsks> ugh, I don't get bzr.  If I clone cloud-init using git-bzr-remote (git clone bzr::lp:cloud-init) and run "git log", I find commit 11b9899 "System config niceness".  But if I clone it with bzr (bzr branch lp:cloud-init) and run bzr log, I can't find that revision.
[17:39] <larsks> Not really important.  Just whining.
[18:02] <harlowja> sorta :-P
[18:02] <harlowja> ha
[18:02] <harlowja> lol
[18:02] <larsks> harlowja: can you elaborate on that "sorta" ?
 Sort of.
[18:04] <harlowja> :(
[18:05] <larsks> harlowja: Specifically, I want to rewrite the hostname handling so that the distro/__init__.py doesn't need to know anything about filenames (keeping that all contained to specific distro classes).
[18:06] <larsks> But there are these weird relationships between _read_hostname and _read_system_hostname, and I want to make sure I"m doing the right thing.
[18:15] <larsks> harlowja: I guess ping me when you're around again...
[18:23] <harlowja> i'm medium around, trying to do some release stuff for oslo
[18:25] <harlowja> larsks i think the weird relationship was because some operating systems give u the fqdn and some don't
[18:25] <harlowja> but i might be forgetting :-P
[18:25] <larsks> Bleargh.  Okay, I will muddle my way through, then, and see what happens.