DocScrutinizer05 changed the topic of #qi-hardware to: Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
pcercuei has quit [Ping timeout: 240 seconds]
rz2k has joined #qi-hardware
xiangfu has quit [Ping timeout: 245 seconds]
xiangfu has joined #qi-hardware
panda|x201 has joined #qi-hardware
panda|x201 has quit [Ping timeout: 272 seconds]
wolfspraul has quit [Quit: leaving]
rz2k has quit [Read error: Connection reset by peer]
rz2k has joined #qi-hardware
qwebirc66132 has joined #qi-hardware
qwebirc66132 is now known as rjeffries
rjeffries has quit [Ping timeout: 250 seconds]
panda|x201 has joined #qi-hardware
rz2k has quit [Read error: Connection reset by peer]
panda|x201 has quit [Ping timeout: 245 seconds]
rz2k has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
wpwrak has quit [Ping timeout: 265 seconds]
panda|x201 has joined #qi-hardware
wej_ has quit [Ping timeout: 264 seconds]
wej has joined #qi-hardware
bzb has joined #qi-hardware
bzb has quit [Read error: Connection reset by peer]
panda|x201 has quit [Ping timeout: 240 seconds]
apelete has joined #qi-hardware
wpwrak has joined #qi-hardware
rz2k has quit []
xiangfu has joined #qi-hardware
panda|x201 has joined #qi-hardware
nickoe has joined #qi-hardware
<nickoe> Do wolfspraul hang around in here sometimes?
<kyak> !seen wolfspraul
<qi-bot> kyak, wolfspraul (~wolfsprau@wsip-174-79-250-235.sd.sd.cox.net) was last seen quitting #qi-hardware 5 hours 58 minutes ago (17.10. 02:55) stating "Quit: leaving" after spending 6 hours 54 minutes there.
<nickoe> kyak: oh, great :)
<kyak> nickoe: unfortunately, "hang" is the best word to describe him being here -\
<nickoe> kyak: ok
<nickoe> Are all of you actively doing qi-hardware dev (except wolfspraul)?
viric has quit [Ping timeout: 240 seconds]
viric has joined #qi-hardware
dos1 has quit [Ping timeout: 260 seconds]
<roh> i've seen him in person some time ago
<roh> few weeks.
<roh> he'd doing some kind of long-term project. one of the kind that takes 18 years till 'release'
<larsc> 18 years is very optimisic, usually there are some delays ;)
xiangfu has quit [Ping timeout: 245 seconds]
<nickoe> roh: ohh, well, then I guess he is kind of busy at times.
xiangfu has joined #qi-hardware
pcercuei has joined #qi-hardware
panda|x201 has quit [Ping timeout: 245 seconds]
dos1 has joined #qi-hardware
porchao has joined #qi-hardware
porchaso0 has quit [Ping timeout: 246 seconds]
porchaso0 has joined #qi-hardware
porchao has quit [Read error: Connection reset by peer]
FDCX has quit [Remote host closed the connection]
xiangfu has quit [Remote host closed the connection]
FDCX has joined #qi-hardware
dos11 has joined #qi-hardware
dos1 has quit [Ping timeout: 245 seconds]
porchao has joined #qi-hardware
porchaso0 has quit [Read error: Connection reset by peer]
dos11 is now known as dos1
kilae has joined #qi-hardware
dos1 has quit [Quit: Kabum!]
dos1 has joined #qi-hardware
wej has quit [Ping timeout: 245 seconds]
wej has joined #qi-hardware
dos1 has quit [Quit: Kabum!]
kilae has quit [Quit: ChatZilla 0.9.90.1 [Firefox 24.0/20130910160258]]
unclouded has quit [Write error: Broken pipe]
woakas has quit [Ping timeout: 246 seconds]
woakas has joined #qi-hardware
pcercuei has quit [Ping timeout: 272 seconds]
valhalla has quit [Read error: Operation timed out]
valhalla has joined #qi-hardware
<DocScrutinizer05> growing chips built by germs on a substrate of dry ice?
<wpwrak> what's the name of that scifi/horror movie again ? :)
<wpwrak> ubuntu has an interesting approach to upgrade conflict resolution: if something goes wrong, it rolls back to some semi-updated state. this takes a long time. then you can try to fix the conflict, which usually just takes a few minutes (the original error message if hidden somewhere in thousands of lines of rollback noise, so you won't be able to find that one and have to experiment).
<wpwrak> then you can try to upgrade again, which again takes virtually forever ...
<DocScrutinizer05> buntkuh, meh
<DocScrutinizer05> steer clear of canonical, all times!
<wpwrak> (just updating some ancient systems to 13.04 ... not touching just released 13.10 yet. let others find the bugs :)
<DocScrutinizer05> good luck! 13.04 also killed maemo servers
<wpwrak> well, so far it still doesn't give me too much trouble. it's getting worse, though. you can feel them pushing towards a proprietary environment
<wpwrak> 13.04 works fine for me. it's what i have on my workstation.
<roh> hm.. why run anything besides lts on servers?
<DocScrutinizer05> yeah, maybe you don't have NFS mounts
<wpwrak> oh, tons of them
<roh> i am just updating everything to 12.04 ;)
<DocScrutinizer05> good luck then
<wpwrak> none of my ubuntu machines are really servers. at least not all of the time.
<whitequark> canonical :/
<DocScrutinizer05> 13.04 comes with a "smart improvement" that allows more than 16 groups per user: it simply uses target machine's etc/groups
<wpwrak> my one full-time server still runs gentoo. of course, completely un-upgradeable by now ...
<whitequark> :/ :/
<DocScrutinizer05> REAL fun!
<wpwrak> luckily, firewalls didn't change much in the last seven or so years
<wpwrak> yeah, oldest files in /usr/bin are from august 2006. back then, they still made hardware that lasts ;-)
<DocScrutinizer05> sounds like my dd-wrt
<DocScrutinizer05> Firmware: DD-WRT v24-sp2 (07/22/09) mini
<wpwrak> one of the infested ones ? :)
<DocScrutinizer05> nah, the linksys DR-615 is retired
<roh> i recently found an plastic router with openwrt from 2003 or so i think
<DocScrutinizer05> err D-link DR-615
<roh> or 2004?
<DocScrutinizer05> this is a linksys wr54g(ß)
<DocScrutinizer05> (?)
<roh> it was doing nat on an blue original wrt, jup
<whitequark> blue original = wrt54gl?
<DocScrutinizer05> maybe gl
<roh> but i really started using it on white russian on the white wl500gp lateron
<roh> g
<roh> no l back then
<whitequark> right
<whitequark> well, g = gl pretty much
<DocScrutinizer05> you know those critters have no decent boiler plate
<whitequark> and it's a really crappy device :/
<whitequark> broadcom, seriously underpowered also
<wpwrak> long-lasting :)
<DocScrutinizer05> well
<whitequark> wpwrak: rocks last even longer !
<DocScrutinizer05> got it for free and just works
<whitequark> well, if you never want to transmit more than like five megabits
<whitequark> it works ;)
<roh> jup. ugly as hell hw. optical as well as electrical. but solid enough
<DocScrutinizer05> Time: 01:41:40 up 117 days, 18:59, load average: 0.16, 0.04, 0.01
<roh> then kamikaze on fonera boxes, and the last few years mainly tplink ar71xx stuff
<wpwrak> i have three categories for technology: 0) the kind i don't care about. 1) the kind i want to play with. 2) the kind i just expect to work. and i really hate it if something from category 2 tries to force its way into category 1.
<roh> we still have some wl500gp in use. (asus brcm)
<whitequark> lol, my router (openwrt attitude adjustment, cheap tplink thingy):
<whitequark> 03:41:14 up 44 days, 16:34, load average: 0.00, 0.01, 0.04
<roh> tops out at 50mbit flatline... while doing iptables and routing with lots of vlans (~12)
<whitequark> my notebook: 03:42:01 up 76 days, 3:46, 5 users, load average: 1.19, 1.38, 1.63
<whitequark> completely accidental, even
<roh> but soon it will be a fresh atheros one with gbit and routing >100mbit
<DocScrutinizer05> this thing now just does switch, DHCP, and AP
<whitequark> roh: it's really bad if your isp wants l2tp
<whitequark> because it does aes in sw
<roh> whitequark: hehe..its pppoe usually here
<DocScrutinizer05> ooh, and NAT
<whitequark> roh: same difference
<DocScrutinizer05> and I guess there it already starts to suck
<whitequark> DocScrutinizer05: yes
<whitequark> it's about 20mbit/s nat iirc
<whitequark> maybe 15
<DocScrutinizer05> well, I got a max 16Mbit downlink 2 up here
<DocScrutinizer05> and this linksys is 2nd level NAT and not exposed to intarnets
<DocScrutinizer05> 1st level NAT is a fritzbox at my neighbour's and THAT sucks!
<DocScrutinizer05> you can't even handle the damn SIP-ALG on that shite box
<DocScrutinizer05> since it's in the chain, my SIP clients frequently have connection issues which cure when getting a new DHCP lease
<DocScrutinizer05> obviously STUNlib and SIP-ALG on fritzbox don't play nice together when a 2nd NAT is between them
<DocScrutinizer05> and for the life of mine I can't get SIP-ALG on the friggin fritzbox disabled
<DocScrutinizer05> a PITA when you don't have either physical access or a IPMI console to a device. You become reluctant to flash new bios/firmware and the like
<DocScrutinizer05> and on this particular model of fritzbox it's really hard to get any telnet or ssh into the thing
<DocScrutinizer05> sucks
<DocScrutinizer05> I'm honestly planning to replace that crap by a panasonic CF-25
<DocScrutinizer05> the CF-25 at least has a decent handle to smash it against the wall
<DocScrutinizer05> (poor wall!)