[00:50] <starsprout> howdy folks
[00:51]  * starsprout taps cyberanger
[00:51] <starsprout> you know how to change kernel boot options in crunchbang?
[00:51] <wrst> hello starsprout
[00:54] <starsprout> hi wrst
[00:54] <starsprout> tryin to get this old aetheros wifi pci card working at my local coffeeshop's new crunchbang machine :-)
[00:55] <wrst> cool starsprout any luck?
[00:55] <starsprout> compat_wireless seems to be the agreed upon solution
[00:55] <cyberanger> hey starsprout
[00:56] <starsprout> however, make says "kernel was compiled with CONFIG_WIRELESS_EXT=n" so it won't build it
[00:56] <starsprout> erm, "make" it
[00:56] <starsprout> hiya cr
[00:58]  * wrst rejoices
[00:58] <wrst> natty started up
[00:58] <wrst> yeah starsprout that certainly sounds like a cyberanger  issue :)
[01:00]  * wrst begins to pull in 200MB of updates it will probably never start again
[01:00] <starsprout> yeah, prolly just be easier to buy a usb wireless adapter than try to get this old pci aetheros to run
[01:01] <wrst> aetheros i have dealt just a little with them but seemed to be a pain
[01:02] <wrst> crunchbang its based straight up on debian now right?
[01:02] <starsprout> yep
[01:03] <wrst> ok i remember having to blacklist something on ubuntu to get an aetheros of some sort to work but that's been forever ago
[01:03] <starsprout> what does CONFIG_ITEM=m mean? what's the m? I see y, n and m
[01:03] <starsprout> yeah I read about that - blacklist the ath5k - how do I do that?
[01:04] <starsprout> didn't try that yet - I also read compat-wireless was a good way to go, but now I'm trying to rebuild the kernel with wireless_ext=y
[01:04] <wrst> in ubuntu it was a simple edit of a config file not sure about debian
[01:05] <wrst> oh goodness rebuilding a kernel seems excessive
[01:07] <cyberanger> starsprout: yikes
[01:07] <starsprout> lol
[01:07] <starsprout> i dunno
[01:07] <starsprout> nothing to lose here, just groping my way through.... :-)
[01:08] <starsprout> I used to not know a lot about unix that I do know now, so I'm ok asking stupid questions to learn my ways
[01:08] <wrst> starsprout: https://help.ubuntu.com/community/WifiDocs/Driver/Atheros
[01:08] <wrst> that's the solution for ubuntu
[01:08] <wrst> and i know that worked for me
[01:14] <starsprout> ok I blacklisted them and am rebooting now (seems better than editing the kernel config, heheh)
[01:15] <starsprout> heck yeah wrst!!! it worked - wireless networks are available :-D
[01:16] <starsprout> All hail, Linux in Tennessee!!!
[01:16] <wrst> starsprout: the easy way is good sometimes ;)
[01:16] <starsprout> or something like that
[01:16] <starsprout> thanks a lot y'all...
[01:17] <cyberanger> wrst: the command line is easy
[01:18] <wrst> no prob starsprout
[01:18] <wrst> cyberanger: doing whatever tothe kernel isn't!!!!!
[01:20] <starsprout> crunchbang actually looks pretty cool now that I'm using it a bit
[01:21] <starsprout> thanks as always y'all.  buh-bye!
[01:21] <chibihogoshino> i like how synaptic tries to fix a deb package but dosnt really do anything
[01:22] <cyberanger> wrst: ah, come on, it can be easy
[01:44] <wrst> well that broke wireless and some how my 10.10 install disappeared from grub
[01:44] <wrst> chibihogoshino: i guess atleast it tries?
[02:33] <wrst> cyberanger: you will not be happy with me
[02:59] <cyberanger> wrst: why's that?
[03:00] <cyberanger> wrst: what broke your wireless and caused 10.10 to be cleared out of grub?
[03:07] <wrst> natty did all of that, and I'm back to quassel again cyberanger
[03:15] <cyberanger> shame on natty
[03:15] <wrst> yeah cyberanger it has grub 1.99 so its even worse than before i suppose?
[03:16] <cyberanger> as for quassel, that's fine, your smartphone just will have to be neglected I suppose
[03:17] <wrst> yes cyberanger i think it will, as much as i hate to, I may change my mind but just so many things are irritating to me about using irssi
[03:17] <cyberanger> http://ubuntuforums.org/showthread.php?t=1631755
[03:17] <cyberanger> might that describe your issue ^
[03:18] <cyberanger> (with grub, not wireless)
[03:18] <wrst> yeah it sees the older natty kernel but the 10.10 kernel just flew out the window it think i will reinstall with 10.10 live cd grub
[03:19] <wrst> and the wireless, well actually grub is just all part of running alpha grade software :)
[03:19] <wrst> i just have a somewhat overly strong hatred for grub2 :)
[03:32] <cyberanger> oh, come on, you know you love grub 2 ;-)
[03:34] <wrst> well when they get it working i will love it actually, because the concept is great the execution... well... you know  how i feel about that :)
[03:36] <cyberanger> oh, come on, you know you love grub 2 ;-)
[03:37] <cyberanger> but yeah, I do know that it's had some hiccups
[03:37] <cyberanger> and ubuntu messing with it doesn't help
[03:51] <wrst> but when they get it all going it really should be great
[18:10] <mhall119> excid3|mbp: are fluttrly #hash lists not per-user?
[18:10] <mhall119> for that matter, are all fluttrly lists public?
[18:12] <excid3|mbp> they're all public right now
[18:13] <excid3|mbp> hashes just link two lists
[18:13] <excid3|mbp> I'm adding accounts and private lists this weekend though!
[18:20] <mhall119> cool
[18:20] <mhall119> I just git-cloned fluttrly and fluttr-desktop
[18:22] <excid3|mbp> ah sweet
[18:22] <excid3|mbp> I haven't done as much on is as I wanted because I realized I should focus on Keryx 1.0
[18:22] <excid3|mbp> but now that's finished enough, I'm going to do some more on fluttrly
[18:26] <excid3|mbp> mhall119: iirc we removed CSRF protection so the fluttrly-desktop won't work
[18:26] <excid3|mbp> but it can post to the site without having to grab the cookies and CSRF token
[18:26] <excid3|mbp> It's a bad API design, but I didn't know how to do it better at the time. We also want to figure out a way to order the items
[20:26] <mhall119> I'd have to learn Ruby to help with the server
[20:26] <mhall119> but maybe I'll hack on fluttr-desktop
[20:26] <mhall119> I'm also thinking of making a fluttrly backend to Tasque
[20:27] <mhall119> course, that'll all depend on changes to the API
[20:27] <mhall119> could I recommend a simple REST/JSON
[20:42] <mhall119> though if you feel like re-writing fluttrly in Django, let me know ;)
[21:58] <netritious> howdy locotn
[23:08] <cyberanger> hey netritious
[23:09] <cyberanger> mhall119: are you around?
[23:12] <cyberanger> netritious: how's your day
[23:53] <mhall119> cyberanger: I am
[23:54] <cyberanger> mhall119: a member in chattanooga's lug metioned qimo recently
[23:54] <mhall119> cool, someone in nashville was blogging about it too
[23:55]  * mhall119 was in both cities this week
[23:55] <mhall119> but totally unrelated
[23:55] <cyberanger> you were in chattanooga this week?
[23:55] <mhall119> yeah
[23:55] <mhall119> visiting friends of my wife
[23:56] <cyberanger> ah
[23:56] <mhall119> but we spent most of our time driving all over the state
[23:56] <cyberanger> I'm not too far north, but you weren't heading north to knoxville I bet
[23:56] <cyberanger> he did metion one thing
[23:56] <mhall119> the original intent of the trip was to take the kids up to see snow
[23:56] <cyberanger> "The first thing you do is setup a parent login, which is just a normal ubunt= u "admin" login (sudo access). I wish the installer highlighted that point m= ore clearly as I ended up renaming the login to be me (after install) rather= than my son as I had assumed. "
[23:56] <mhall119> so of course we picked the one week where temps where in the 70's
[23:57] <cyberanger> (poor c&p, whoops)
[23:57] <cyberanger> that was is only gripe, and that was easy to fix, he loves it
[23:57] <mhall119> cyberanger: the installer doesn't mention that because it doesn't apply anymore
[23:57] <cyberanger> and yeah, good luck on timing
[23:58] <mhall119> as of 2.0, we don't have "parent" or "child" accounts
[23:58] <cyberanger> hrm, outdated version I guess then, he cited version 2 though
[23:58] <mhall119> you can choose whether to use the Qimo session on any account
[23:58] <mhall119> he could have left the original account for his son
[23:59] <mhall119> but it would have sudo access
[23:59] <mhall119> I'm looking at adding the ability to create multiple accounts during the installer, but it seems like it's going to be more work than maybe it's worth
[23:59] <cyberanger> ah, that was his issue