[16:03] <jcsackett> anyone who followed the install launchpad in an lxc tutorial wind up with the lxc not starting b/c it couldn't mount /dev/shm because it's a "symbolic link to nowhere"?
[16:07] <rick_h_> jcsackett: doh, let me know if you find an answer. I am running it that way right now but imagine I'll need to rebuild it on upgrade
[16:08] <rick_h_> actually, should start that upgrade now I guess :/ so behind
[16:08] <rick_h_> bah, so many PPAs to worry about
[16:22] <jcsackett> rick_h_: indeed. i did a clean install b/c i needed to upgrade drives anyway. thought it was a good time to do the lxc thing but it seems to be fail.
[16:23] <rick_h_> jcsackett: yea, I always do clean install so think that's safer for me anyway
[16:23] <rick_h_> yea, I did the lxc thing, but I didn't want it in my home drive so I did some manual overrides
[16:24] <rick_h_> actually wondering about doing it in a virtualbox server install this time
[16:24] <rick_h_> like having LP dev on a diff setup
[16:25] <jcsackett> fair.
[16:25] <jcsackett> i think i'll have to go the usual way; wanted lxc but i need to be able to work tomorrow and don't have much time to muck around today.
[16:53] <cjwatson> jcsackett: that sounds like /run erroneously not being (bind-)mounted
[16:54] <cjwatson> sort of thing you might get with instructions from pre-er-precise-or-so I guess
[16:57] <jcsackett> cjwatson: any thoughts on how to remedy it?
[16:58] <cjwatson> no idea what instructions you're following
[17:13] <cjwatson> jcsackett: I guess that in general it depends on whether the procedure in question is binding mountpoints from the host system, or constructing its own versions of important system filesystems internally
[19:58] <jcsackett> cjwatson: i was just running the directions in https://dev.launchpad.net/Running/LXC figure i should become familiar with lxc and i basically know nothing about it at this time.
[20:27] <lifeless> jcsackett: I haven't seen the symbolic link to nowhere happen before
[20:27] <lifeless> jcsackett: I'd check for bugs in ubuntu/+source/lxc - closed ones in particular
[21:30] <jcsackett> lifeless: thanks. i check through that, but found nothing too applicable. gary_poster pointed out there were some issues relating to dev/shm *after* starting an lxc, but nothing quite like this.
[21:34] <jcsackett> there's some indication that the basic handling of dev/shm changed in quantal. i think that may be the failure point, though i'm unsure how to approach it.