[03:58]  * chesedo silently waves a greeting
[05:05] <Kilos> morning everbody
[06:05] <thatgraemeguy> morning peeps
[06:17] <dlPhreak> Morning
[06:17] <Kilos> hi dlPhreak 
[06:17] <Kilos> hi there thatgraemeguy 
[06:18] <dlPhreak> Kilos, thatgraemeguy 
[06:19] <dlPhreak> How are you all doing?
[06:19] <Kilos> well ty and you?
[06:20] <dlPhreak> Still sleepy, haven't had coffee yet.
[06:20] <Kilos> lol
[06:51] <unlaudable> morning...
[06:52] <unlaudable> so.... http://blog.dustinkirkland.com/2016/02/zfs-is-fs-for-containers-in-ubuntu-1604.html
[06:52] <superfly> morning
[06:53] <superfly> i saw
[06:53] <unlaudable> happy sad?
[06:54] <superfly> neither to me, I know of ZFS's reputation, but I have no experience with it
[06:56] <inetpro> good mornings
[06:56] <inetpro> Kilos: 11mm
[06:56] <superfly> unlaudable: I know that the reason it's not included in the kernel by default is licensing issues
[06:57] <superfly> unlaudable: Canonical seems to think that there are none, but others disagree
[06:57] <inetpro> that licensing has been messy indeed
[07:15] <unlaudable> I thought this was interesting... http://news.slashdot.org/comments.pl?sid=8130489&cid=50676937
[07:15] <unlaudable> see the reply... 3rd comment
[07:16] <unlaudable> well that whole thread... unhide
[07:20] <unlaudable> lots of bleeting on slashdot about we should rally around zfs/btrfs, btrfs/zfs development is stagnant, btrfs/zfs has x feature the other doesnt, btrfs lost my data (no one complained about zfs losing data :D)
[07:26] <unlaudable> ok I lie found someone complaining about zfs corrupting there data... but what a weird setup...
[07:39] <unlaudable> this also makes me want to side with ZFS... http://news.slashdot.org/comments.pl?sid=8130489&cid=50675531
[07:41] <unlaudable> also this... http://news.slashdot.org/comments.pl?sid=8130489&cid=50674623
[07:41] <Kilos> inetpro 20mm ek wen die keer ne
[07:43] <Kilos> inetpro got an sms with clearance ref number
[07:43] <Kilos> yay
[08:16] <superfly> "But as you said in your comment that it's "rapidly getting there". That's been the story since day one. And it's not got there. Not even close."
[08:16] <superfly> That's how I feel about Wayland.
[08:16] <superfly> Mir is already out there. Where's Wayland?
[08:17] <superfly> I'm no fan of exactly how the Mir debacle played out, especially not Canonical's attitude, but the reality is that they actually have working code out there.
[09:40] <unlaudable> Wayland is just the protocol though right?
[09:40] <unlaudable> so its up to gnome and kde to just tart using it?
[09:40] <unlaudable> start even
[10:11]  * Padroni waves
[10:11] <Padroni> hi thatgraemeguy 
[10:11] <Padroni> long time
[10:25] <Kilos> hi oad
[10:26] <Kilos> Padroni 
[10:26] <Kilos> dunno what happened there
[10:27] <Kilos> min dae yet Padroni 
[10:27] <Kilos> ?
[10:31] <Padroni> hi Kilos 
[10:31] <Padroni> yeah - min dae
[10:31] <Padroni> 2 - 6 weeks
[10:31] <Kilos> sjoe
[10:31] <Kilos> how can it be 2 to 6
[10:32] <superfly> unlaudable: negative, Wayland is a display server
[10:32] <Kilos> hi qwebirc14648 
[10:32] <Kilos> hi tailon 
[10:32] <tailon> howdy 
[10:33] <Kilos> welcome to ubuntu-za
[10:33] <tailon> TA
[10:33] <Kilos> if you need help withj something just explain what you are battling with
[10:34] <Kilos> someone will have a cure
[10:35] <tailon> thankfully no issues , just poking around . See whats what 
[10:35] <Padroni> it's either 2 more weeks, or 6 more weeks
[10:35] <Padroni> hi tailon 
[10:37] <superfly> unlaudable: the reality is that both Gnome and KDE already support Wayland. It's just that Wayland doesn't work.
[10:40] <unlaudable> ... ok...
[10:41] <unlaudable> https://www.reddit.com/r/linux/comments/2uc3gx/when_well_wayland_finally_replace_x_as_a_default/co722j6
[10:41] <unlaudable> "Wayland is a protocol for a compositor to talk to its clients as well as a C library implementation of that protocol."
[10:41] <unlaudable> from https://wayland.freedesktop.org/
[10:42] <unlaudable> just throwing that out there, I'm no expert by any means...
[10:42] <unlaudable> its all rather confusing...
[10:44] <superfly> unlaudable: yes, it's technically BOTH
[10:47] <unlaudable> I think the issue is all X apps need to support it... thats going to take a looong time
[10:47] <unlaudable> as in X apps need to rewritten to support it... maybe?
[10:51] <unlaudable> https://www.youtube.com/watch?v=Ux-WCpNvRFM
[18:07] <Kilos> storming, power cut once already
[18:33] <Kilos> wb superfly 
[18:34] <superfly> thanks Kilos
 Kilos: kudos to your team!
[18:48] <Kilos> superfly thats for your 2 sites
[18:49] <Kilos> that comment was from the xubuntu dev guys
[18:49] <Kilos> x or l , i get mixed up
[18:49] <inetpro> what did we do wrong oom Kilos
[18:49] <inetpro> good mornings
[18:49] <Kilos> hi inetpro 
[18:50] <Kilos> wrong?
[18:50] <inetpro> or is it, what do they want from us?
[18:50] <inetpro> :-)
[18:50] <Kilos> you guys made sites too cool i spose
[18:50] <Kilos> no man
[18:50] <Kilos> one was looking at static site generators so i told him try nikola
[18:51] <inetpro> 7mm here
[18:51] <Kilos> he said why do i like it so i showed or sites
[18:51] <Kilos> i havent checked
[18:53] <Kilos> night all. sleep tight
[19:25] <superfly> hey, cal_py. Just some IRC etiquette: if you want to PM (private message) someone, generally it's regarded as bad form if you PM them without asking first.
[19:25] <superfly> cal_py: also, as an aside, sometimes if you're looking for help with something, the channel might benefit from it too
[19:27] <cal_py> apologies  i guess.
[20:54] <superfly> hi cal_py, have you ever used Telegram?
[20:59] <cal_py> Yeah superfly, looks like a good app
[21:00] <superfly> OK, might come back to that later. What where you wanting earlier?
[21:04] <superfly> cal_py: how can I help?
[21:06] <cal_py> just wanted to chat about python is all, no real agenda
[21:55] <superfly> cal_py: sorry, I'm busy with a dozen things here this evening :-( ask me again tomorrow? I'd be glad to help you.