Conversation with #inferno at Sun Oct 12 17:48:47 2008 on powerman@irc.freenode.net (irc) (17:48:47) #inferno: The topic for #inferno is: Inferno and Limbo | Website: http://www.vitanuova.com/inferno/index.html | Documentation: http://www.vitanuova.com/inferno/docs.html | Wiki: http://canto.hopto.org/wiki/1/index.html | Tutorial: http://www.resc.rdg.ac.uk/twiki/bin/view/Resc/InfernoTutorial | Mailing list archives: http://dir.gmane.org/gmane.os.inferno.general (18:29:36) gualteri left the room (quit: "leaving"). (19:12:38) andguent [n=andre@p4FF653BF.dip.t-dialin.net] entered the room. (20:43:02) pierre- left the room (quit: Read error: 104 (Connection reset by peer)). (21:01:48) pierre- [n=pierre@89.179.89.45] entered the room. (21:11:42) powerman1: are there any guidelines for developing 9p applications available? something like list of known 9p weakness (latency issue come to mind, something else?), recommendations how to handle reconnection (in case remote system you mounted resources from was rebooted, for example), etc. (21:20:02) eekee: I guess how to handle reconnection would be described in the 9p docs somewhere... Might be worth asking in #plan9 (21:28:17) powerman1: Actually it isn't so hard to find out how to handle something you know must be handled. I'm asking more about checklist of pitfalls to keep in mind than about solutions to them (but having recommended solution in same checklist is better, of course :)). Right now my checklist contain only these two things (latency and reconnection), and I afraid it's too short to be comprehensive. (21:28:50) eekee: ahh ok (21:30:07) eekee: there's a lot more people in #plan9 so that's why I thought it worth asking there (22:36:29) pierre- left the room (quit: Success). (22:51:20) KillerX [n=anant@gentoo/developer/KillerX] entered the room. (23:39:13) defn left the room (quit: Connection reset by peer). (23:58:06) andguent left the room (quit: "Leaving"). (00:19:18) uriel: eekee: actually I don't think 9p says anything about how to handle reconnections (00:23:06) eekee: oh dear (00:23:21) olegfink: nemo says a lot about it, but that's plan b (00:26:12) eekee: ahh. I've forgotten what plan b is already. I've been concentrating on inferno because it can be hosted under linux including on my PDA. Hence also the "oh dear" since the PDA naturally gets disconnected often (00:27:38) olegfink: there's a good description of reconnection and service switching features of plan9 by nemo in one of 2005 irc logs on the wiki (00:28:05) eekee: cheers (00:29:37) olegfink: http://plan9.bell-labs.com/wiki/plan9/Town_Hall_Meetings/index.html (00:29:40) olegfink: those ones (00:30:20) olegfink: eekee: the first one seems to be the nemo part (00:30:32) olegfink: ...and the second is titled '9p reliability' (00:30:41) olegfink: I haven't seen it before for some reason (00:30:51) eekee: right ^_^ (00:33:24) olegfink: hmm, those logs give me a feeling that plan9/inferno community is suffering from some environmental problem (00:33:36) olegfink: I think it's called sands of time (00:35:01) uriel: eekee: 9p doesn't say much about some things because it doesn't need to (00:35:28) eekee: always sensible (00:35:42) uriel: there are many approaches to handle reconnections, see a paper from the first iwp9 for an overview of some of the solutions (00:35:42) eekee: *wry smile @ olegfink* (00:35:54) eekee: righty ^^ (00:39:50) olegfink: eekee: sorry to ask, but may you define what does 'wry smile' mean? Seems I understand it lexically, but not collocatively (00:40:53) olegfink: errr, not what it means, but rather what it means in the context you used it. (00:42:41) eekee: oh, refering to your 'sands of time' comment. I thought it a good comment; poetical (in a good way), so I smiled, but the subject of your comment is rather sad, so it's a wry smile (00:44:59) olegfink: aha, got it. it's just there isn't a comparable expression in russian. the dictionary would tell me that wry == ironic, but in russian an ironic smile (or ironic look)'s irony would definitely targeted at the one you smile/look at. (00:46:55) eekee: ahh (00:58:34) uriel: in this context I think wry ~= bitter (01:00:28) eekee: yeah, a soft form of bitter (01:00:45) eekee: oh wait, did you mean ~= to mean not equal? (01:04:51) powerman1: aprox.equal, i think (01:05:13) powerman1: sort of more-or-less-equal thing :D (01:05:50) eekee: that's what I always take it to mean *nod* (01:09:16) olegfink: haskellers use /= for !=, takes quite some time to get used to it (01:09:45) olegfink: (why said you can't use unicode compositions in ascii?) (01:11:02) olegfink: s/why/who/ (01:14:04) grai: I use sed preprocessors (01:14:07) grai: compiler <{sed 's/≠/!=/g' src/*} (01:14:20) grai: makes the code look much nicer :) (01:36:13) KillerX left the room (quit: ). (05:17:49) eekee: hum, I got emu triggering an illegal instruction in glibc on my zaurus (05:33:55) ooooo [i=none@201.80.219.33] entered the room. (05:36:42) defn [i=tao@silenceisdefeat.org] entered the room. (06:12:44) eekee left the room (quit: Read error: 131 (Connection reset by peer)). (06:12:48) eekee [n=eekee@cpc1-lanc4-0-0-cust860.brig.cable.ntl.com] entered the room. (07:28:05) newmanbe left the room (quit: Read error: 104 (Connection reset by peer)). (09:20:57) uriel: eekee: in a fair world, all glibc instructions would be illegal (09:21:10) ***eekee smiles (09:21:29) eekee: it's not a libc for mortal coders, that's for sure (09:40:00) uriel: eekee: you should try to get native inferno going in the zaarus ;) (09:40:11) eekee: %^&*() lol (11:29:00) KillerX [n=anant@gentoo/developer/KillerX] entered the room. (12:14:23) pierre- [n=pierre@89.179.89.191] entered the room. (15:36:18) pierre- left the room (quit: Read error: 110 (Connection timed out)). (17:22:34) pierre- [n=pierre@89.179.89.191] entered the room.