[05:42] <vish> !grub2
[05:42] <vish> hmm , ..^ that needs an update from "in Karmic" to "since Karmic"
[05:44] <Myrtti> !grub ~= /in Karmic/since Karmic/
[05:44] <Myrtti> !grub2 ~= /in Karmic/since Karmic/
[05:45] <h00k> Myrtti: he decided to quit, thanks for stopping by, though!
[05:45] <Myrtti> yeah, I had a word with him before he did
[05:46] <h00k> Myrtti: ah, yeah, he did say someone squealed.
[05:46] <Myrtti> several people, in fact
[05:46] <h00k> I'm not surprised, a lot of us were trying in the chan, at least.
[05:48] <vish> Myrtti: thanks
[05:49] <h00k> Myrtti: I randomly hit your site today making my rounds and didn't see any update in the past few months
[05:49] <h00k> :(
[05:50] <Myrtti> h00k: time/health/work issues
[05:51] <h00k> Myrtti: I understand, I hope all is okay
[06:36] <jussi01> m4v: rww: just read back on scroll back. its in the roadmap that we will have a queue for factoids that have been requested, so that nothing slips through the cracks. Im hoping that is allows us to notify you when its been processed also.
[06:37] <rww> jussi01: ah, awesome :)
[06:38] <jussi01> If you want to help with coding stuff for the new issue tracker etc, have a chat to Pici and have a look at this: https://edge.launchpad.net/bantrackertwo
[06:39] <jussi01> Id really like to encourage people to help out, as Pici could do with all the help he can get.
[06:50]  * jussi01 prods at rww... :D
[07:26] <rww> jussi01: I'll look into it :)
[08:20] <rww> I'm poking at nhand1er's Operator Guide draft. There isn't an equivalent to /msg chanserv QUIET for bans, is there? One would only use /mode +b?
[08:20] <bazhang> +q
[08:20] <ubot4> Factoid 'q' not found
[08:21] <bazhang> or in chanserv.py m still works
[08:21] <rww> bazhang: I know. I meant is there a ChanServ command to ban a user, like there's a ChanServ command to quiet one.
[08:21] <bazhang> rww, yep +b
[08:24] <bazhang>  /mode #channel +b nick/ident/etc
[08:25] <rww> bleh, I am bad at explaining myself :)
[08:25] <rww> Alright. For quiets, one can do /mode +q whatever or /msg chanserv quiet #channel whatever. For bans, one can do /mode +b whatever; is there also a /msg chanserv something command for bans?
[08:25] <bazhang> sorry
[08:28] <rww> No problem. I probably should have asked in #freenode, now that I think of it :)
[08:28] <bazhang> too many trolls in -ot at the moment :/
[08:28] <rww> isn't there always :(
[08:30] <jussi01> rww:
[08:31] <jussi01> err
[08:33] <jussi01> rww: there isnt one for bans iirc and even if there is, we really prefer the op uses the /mode +b because then the bot can record who did it.
[08:34] <rww> jussi01: makes sense. I was going to add it for completeness, since /msg chanserv quiet is on that guide already
[08:34] <rww> but this way I don't have to, because it doesn't exist, so yay.
[08:49] <jussi01> rww: "/msg chanserv help" is awesome :P
[10:16] <m4v> jussi01: I thought bt2 was meant to replace bt, is for factoids as well?
[10:43] <jussi01> m4v: no, but it should have a factoid queue in it. its part of the whole "Issue Tracker" idea.
[11:58] <IdleOne> anybody got an easy way for me to figure out what type of RAM I have in my system?
[12:21] <gord> IdleOne, open it and look at it?
[12:21] <IdleOne> gord: yeah, thought that is what would end up happening
[12:21] <IdleOne> ok well I guess I will have to pull it out and look
[12:21] <gord> IdleOne, maybe you can cat something in proc but i'v just always looked at it
[12:22] <IdleOne> wish hardinfo package would give that info :/
[12:22] <IdleOne> guess it can't
[12:22] <IdleOne> tells you practically everything else
[12:22] <k1l> lshw should give some info
[12:27] <IdleOne> k1l: nothing that leads me to figure it out
[12:27] <IdleOne> but I am googling mother board
[12:27] <erUSUL> IdleOne: dmidecode or lshw
[12:27] <erUSUL> IdleOne: this is not the support channel btw ;)
[12:28] <IdleOne> erUSUL: yes I know
[12:28] <IdleOne> but you folks are so helpful :)
[12:28] <IdleOne> erUSUL: dmidecode was the answer btw, thanks :)
[12:28] <k1l> IdleOne: you can have a look at the bios at startup. maybe it will tell you smth. more
[12:28] <IdleOne> Type: SDRAM
[12:32] <erUSUL> IdleOne: i know you know hence the ;).
[12:33] <IdleOne> erUSUL: had I asked in #ubuntu you would of told me #hardware :P
[12:33] <IdleOne> hehe
[12:33] <erUSUL> IdleOne: no; i look much more clever to everyone pointing out obscure tools like dmidecode ;P
[12:34] <IdleOne> lol
[13:59] <jpds> dmidecode doesn't know about DDR3.
[14:29] <erUSUL> jpds: well it only decodes the dmi data of the mobo BIOS afaik. So i'd say it is more a bios's fault in that case
[14:29] <jpds> erUSUL: No, it's dmidecode's; I've read the source.
[14:30] <erUSUL> jpds: i stand corrected
[14:30] <jpds> (lshw trunk picks up DDR3 fine).
[15:11] <guntbert> maco: are you there?
[15:12] <maco> guntbert: yes
[15:12] <maco> guntbert: but i'm doing some homework/kde stuff right now
[15:13] <maco> (yes, i've found a way to make kde count as homework)
[15:13] <guntbert> maco: could you try to tell yolanda in ubuntu not to talk random chatter in spanish?
[15:13] <guntbert> if it doesn't keep you too much :-)
[15:15] <guntbert> maco: or wait - she quit already -sorry to disturb you
[15:15] <maco> heh
[16:10] <erUSUL> doesntwork
[16:10] <erUSUL> !doesntwork
[16:27] <ubot2> In ubot2, CyL said: !offtopic is <reply> Olá, este é um canal de cunho técnico para sanar dúvidas do GNU/Linux Ubuntu. Se o seu assunto não possui cunho técnico, por favor entre no ##ubuntu-br
[16:27] <Myrtti> ##ubuntu-br???!!!
[16:30] <erUSUL> looks like it exist ... but it chlashes with freenode policy; doesn't it?
[16:30] <erUSUL> clashes*
[16:33] <Myrtti> yup
[16:33] <Myrtti> Canal Social e NAO OFICIAL da comunidade
[16:34] <nhaines> I thought ## channels were free-for-all.
[16:35] <Myrtti> nhaines: Ubuntu has a claim on the name, so ## isn't kosher
[16:35] <nhaines> Myrtti: works for me.
[23:16] <m4v> those users with weird nicks (the ones that start with a number) what are they?
[23:19] <Tm_T> m4v: victims of nick collision or similar, they couldn't use the nick they chose so server gave them random id instead
[23:19] <Tm_T> well, not necessarily random but...
[23:19] <m4v> there are a lot of collisions in #ubuntu
[23:20] <m4v> Tm_T: ty
[23:20] <Tm_T> m4v: I have seen only one person
[23:21] <m4v> I mean, every day I look at #ubuntu there's one or two of those nicks
[23:21] <Tm_T> and I suspect he has nick protection on and doesn't remember to identify himself -> cannot keep the nick
[23:21] <m4v> no, I have a couple of those in #kubuntu-es, if they have nick protection the nick changes to Guest
[23:22] <Tm_T> oh, right
[23:23] <Tm_T> well, similar
[23:52] <Tm_T> good night all