<wolfspraul>
need to automate some of those things, I hope Indefero just gets better over time by itself :-)
<wolfspraul>
right now the amount of time it would take me to automate this is more than occasionally fixing new projects manually
<wpwrak>
does it generate notifications so that you at least know that something needs doing ?
<wolfspraul>
don't think so, need to look into it
<wolfspraul>
my plan was to make project creation easier with a form
<wolfspraul>
but then I am also hoping it will just show up in Indefero magically one day :-)
<wpwrak>
btw, it would be nice if the downloads were a little more direct, not sourceforge-style with a number and via several intermediate pages. in particularly, it would be nice if one could, once at the place where the downloadable file is shown, just copy a clearly downloadable url.
<wpwrak>
if they're busy working on it, it might, eventually :)
<wolfspraul>
I agree. they have this get/ system, I don't really like that either.
<wolfspraul>
Indefero is definitely actively being developed.
<wolfspraul>
but it's largely a 1-person project
<wolfspraul>
my #1 priority in Indefero now is to do some kicad automation. but I have so many todo items everywhere it all takes some time.
<wolfspraul>
it took a year to get where we are now with the servers...
<wolfspraul>
the kicad stuff is important because I can later see us automatically generating not only schematics but also bom or other data views from the kicad files
<wolfspraul>
easily sortable components lists, etc.
<wpwrak>
yup, that sounds nice. of course, a few strategically places makefile would allow project members to generate them on their own as well - and see any errors as well
<wpwrak>
s/places/placed/
<wpwrak>
i'm curious what the memset speed with jlime is. with the openwrt build, it seems pretty horrible. the cpu shouldn't really find it difficult to saturate the bus.
<wpwrak>
rafa: ok, thanks ! by the way, do you want a counterweight for your Ben before the trip ?
<zear>
tuxbrain2, that looks great
<tuxbrain2>
zear: and sounds even greater :P
<zear>
:D
<wpwrak>
tuxbrain2: your counterweights are drying now. have tnt responded yet ?
<tuxbrain2>
on his return from holidays on 22th
<wpwrak>
wow. when will you release ?
<rafa>
tuxbrain2: YEAH!!!!!... I saw that .. but I was so jealous if that is the proper word to use!!!.. really cool! I want one of this.. definitely
<tuxbrain2>
wpwrak:Â Â on september(tm) trying to obtain a more precice date from the band...
<rafa>
tuxbrain2: yep, the sound of nn is great (headphones).. but we should put the metal music with speaker as well.. so old people start to feel fear again of metal guys!
<tuxbrain2>
we want to make it coincide with the new album release.. on semptember.
<tuxbrain2>
hehehe rafa: a NN in the shoulder instead of a monstrous radiocasette, times are changing :P
<rafa>
wpwrak: yes.. I want one of that.. just few days before the trip. So I would need to try to get one of this from you. No sure if I know well how to put that inside :)
<wpwrak>
rafa: reminds me of the days when i just had finished studying and got my first decent laptop (an IBM TP 700-something). i was riding the tramway in zurich and a teenager nearby was playing something beeping annoyingly on a gameboy. well, i took out my laptop and played a bit of doom, with all the sound. very satisfying :-)
<wpwrak>
tuxbrain2: well, if your agent returns on the 22th and schedules the pickup for the 23th, you'll have it still within august.
<wpwrak>
rafa: pretty easy. one minute maybe. open case, pop out PCB, swipe bottom with alcohol, put counterweight and two drops of glue inside, put isolation tape on the buzzer, put in pcb, close case, done.
<rafa>
tuxbrain2: I guess that a beta3 is ready around saturday.. no many changes. Just a great terminal, and calendar. And several fixes/adds useful for the final user: like a GUI to set date/time or audio volume. And other kind of stuff, like fn key working. SO if you have your job clean, then you could easily to use beta3 I guess.  Well, if you have already flashed all the machines then the work could be hard :)
<rafa>
wpwrak: hahahah :D.. .dooom "is the game"
<rafa>
metal game
<rafa>
wpwrak: you did well..
<wpwrak>
rafa: back then, doom was also pretty much state of the art :)
<wpwrak>
yup, 1994 :)
<rafa>
tuxbrain2: btw, IIRC there were doom level editors some time ago.. you could add a doom level with some new music stuff of that metal band.
<rafa>
wpwrak: wow.. yeah. I remember that year.. I was deciding if to start university or play doom another year more
<rafa>
;-))
<wpwrak>
just 16 years ago. feels like such a long time.
<rafa>
and it is still the best game for the new machines like nn perhaps
<bartbes>
love.graphics isn't feature-complete yet, but it's getting there
<bartbes>
and love.audio and love.sound are left, I started working on love.audio today, so that is getting there too
<bartbes>
(audio is playback, sound is decoding)
<bartbes>
to anyone interested
<bartbes>
also, while love.font runs, you can't actually draw fonts yet (that is one of the missing features in love.graphics)
<bartbes>
(this also means that love.thread is running and working)
<rafa>
wpwrak: hey, ready to test :)
<rafa>
wpwrak: Jlime$ time ./test
<rafa>
real    0m 4.45s
<rafa>
user    0m 4.43s
<rafa>
sys    0m 0.00s
<rafa>
wpwrak: what should we check exactly?
<wpwrak>
much faster than with openwrt ! you're getting 58 MB/sec, whle I go 38 MB/sec. so that's 150% the uClibc speed.
<wpwrak>
still not perfect, though
<wpwrak>
gotta run now. back in a few hours. let
<wpwrak>
s see if we can make this hum a little faster :)
<wpwrak>
thanks !
<rafa>
no problem!.. happy to help
<rafa>
wpwrak: so my system is 150% faster than yours??!.. HA!.. poor tortoise.. ;-))
<rafa>
50%
<Textmode>
why do I have the sudden urge to see if I can get a mush to run on my NN?
<tuxbrain2>
a mush?
<tuxbrain2>
what is a mush?
<wpwrak>
rafa: btw, did you check if there are any cpu-intensive background processes ? e.g., on mine, i killed the evil gmenu2x that was burning quite some cpu time, despite the system being perfectly idle
<wpwrak>
rafa: with gmenu2x, it was even slower ...
<Textmode>
tuxbrain2: MultiUser Shared Hallucination. do you remember playing on old MUD games? or failing that, text adventures?
<Textmode>
tuxbrain2: basically MUSHes were a more generalised offshoot of MUD development.
<nebajoth>
Textmode: I ran NakedMUD successfully
<nebajoth>
and yessss
<nebajoth>
misspent youth
<nebajoth>
dialup accounts with the university at the age of 14, and mudding until the wee hours
<wpwrak>
those were the days. i let a friend run an LPmud on "my" sgi at the university. it turned into an efficient death trap for students easily distracted from work necessary to further their career :)
<Textmode>
wpwrak: yeah, MUDs were famous in acedemia for just that reason.
<Textmode>
also good for soaking up wads of CPU time on the campus's computers, to the point where many outright banned them from being run on their machines :)
<rafa>
wpwrak: I have a little better time now.. no much though, and I did not change nothing. Also I guess that I have a lot more processes.. at least we have dbus, Xfbdev, matchbox window manager, matchbox desktop, torsmo, and few more
<rafa>
wpwrak: but that does not mean that those eat more cpu of course.
<wpwrak>
Textmode: in my case, most of the flak came from the central services, because all out dial-in ports were occupied with mudders
<Textmode>
hehehe
<wpwrak>
rafa: but none of them show up as doing something in top ?
<rafa>
wpwrak: no.. they are good boys :)
<wpwrak>
wonders if gmenu2x has since been taught not to do such things
<rafa>
wpwrak: I like gmenu2x.. but I would use it just as launcher if I would have a specific goal to accomplish. For example, when I was thinking gamerunner, gmenu2x was my prefered gui in my todo list. But no now that we have keyboard and of course linux, a multitasking OS
<rafa>
wpwrak: zear showed me gmenu2x as idea for gamerunner, one year ago, or more.. he always knows nice geek stuff no so common between linux users :)
<zear>
because i'm a fan of linux based game consoles
<wpwrak>
okay, so it may just need a little bit of fixing
<zear>
so i knew about gmenu2x since ever ;)
<rafa>
zear: ;-)
<mth>
wpwrak: I added Uli's fix for gmenu2x consuming lots of CPU when idle to the git archive on projects.qi-hardware.com
<mth>
and a lot of other fixes from me and Ayla as well
<mth>
it's still not perfect, but it's in much better shape than before
<rafa>
wpwrak: well, I still prefer a lot more a X+WM which does almos nothing, but let you run a few X applications at the same time and control them ;)
<rafa>
(for nanonote)
<wpwrak>
mth: great, thanks ! what i'm running at the moment is still the stuff it came with from the factory
<wpwrak>
hah ! my first ben-wpan board isn't dead. i just had mis-soldered the crystal.
<wpwrak>
now ... how do i measure if it's truly accurate to 40 ppm ... hmm ...
<wpwrak>
only the usrp2. that one's got a 20 ppm clock. all the other instruments are much worse. hmm .. there's a shop in town that has a frequency counter that does 1 ppm ...
<Textmode>
rafa: no ideas on that vid file?
<rafa>
Textmode: ah.. yes... I have some ideas.. but I have not checked.. been busy :)
<rafa>
Textmode: the mplayer complains about spacecolors
<rafa>
and then it scales the whole movie..
<rafa>
so it tries to use a bigger res than 320x240+.. and then it fails..
<Textmode>
...
<rafa>
but I also did the movie smaller in res.. and it fails as well. So now I was thinking to convert that spacecolor thing to check if something works :P
<rafa>
(at least)
<rafa>
Textmode: btw you have weirds movies
<rafa>
:)
<Textmode>
if it helps, I converted it from a ogv, made with "Istanbul" (screen recording software)
<bartbes>
btw, Textmode, would you like a status update on nlove (working name of the love port)
<Textmode>
yeah, its a recording/demo of a Kobold Runecrafter from my the nwn survival server "Dawn of New Dead" (I didn't name it :P). I was their scripter.
<Textmode>
bartbes: yeah?
<bartbes>
well, love.graphics isn't complete yet, but getting there (most obvious missing feature is fonts), I started work on love.audio and only love.sound has no port yet (love.audio doesn't run, I must admit)
<bartbes>
even love.thread runs
<Textmode>
bartbes: not even imageFonts?
<bartbes>
oh it's not too different internally
<bartbes>
I just haven't started on font rendering yet
<Textmode>
awesome.
<Textmode>
so definately looking good, then?
<Textmode>
does it have a repo?
<Textmode>
ah.
<bartbes>
no repo, no
<Textmode>
okay.
<bartbes>
I could however...
<bartbes>
supply you with my current makefile
<bartbes>
(which downloads the code from my comp)
<tuxbrain2>
will be lovely to have "n:new" in addition of Enter:ok, and ESC:exit in fileselector , being optinal to show it trough a command param , for example "fileselector.bin -n /blah/blah" and if pressed "n" a simple text box to put the name of the file, this way we can create for example new text files and use vi, joe, nano or even gtkedit avoiding the use of the messed "open/save dialog"
<wpwrak>
wolfspraul: an idea to make the mailing lists a bit better (feasibility depends on how the archiving happens): before sending out a mail, attach the url of the archived version to the header, similar to the URL in List-Archive:
<wpwrak>
wolfspraul: this way, one could look up archive locations directly in one's own mailbox, without having to wade through the much less convenient archives
<wolfspraul>
hmm
<wolfspraul>
you do want to innovate everywhere :-)
<wpwrak>
of course :)
<wolfspraul>
you mean you want to jump from your inbox straight to the URL?
<wolfspraul>
to see messages following in this thread, or why?
<wolfspraul>
or so send the URL of this message to someone else?
<wpwrak>
mainly for references. e.g., search my sentbox for the something i have sent in the past, and then copy the archive url in a reply to the same topic coming up now
<wolfspraul>
I like the idea, I'll add it to the todo list, but I doubt I will get to this anytime soon.
<wolfspraul>
you want this url just in a header, or in the message body? maybe in the footer would be nice?
<wpwrak>
kewl. anywhere in the mail where it's accessible will do. just no uuencoded .doc attachment :)
<wpwrak>
aah ! hardware counter plus GPS or NTP. cheap yet arbitrarily precise clock reference. i knew there was a reason for routing the clock output to the mcu :)
<wpwrak>
well, it would work if the timers could count external events. which they can't in the C8051F326. grumble.
<wolfspraul>
nice. Intel bought McAfee for 8 billion USD. That should make some people think more about hardware and software companies :-)
<wpwrak>
wolfspraul: btw, "mailman doesn’t send mails back to sender" doesn't seem to be true. at least not for mails i send to the list.
<kristianpaul>
obvious acquisition targets not only for chip manufacturers but also hardware providers, such as mobile device manufacturers.
<kristianpaul>
wpwrak: yeah i dint
<kristianpaul>
i must use groups response in mutt to follow the thread with my comments
<kristianpaul>
thats other good todo :)
<wpwrak>
ah, i always use "reply to group" (with mutt) but the reply-to overrides it with the list anyway.
<wolfspraul>
wpwrak: that's separate
<wolfspraul>
the mailing list purists like to not use the reply-to address to 'force' mails back to the list
<wolfspraul>
but if we would do this, I guarantee you _many_ mails that are intended for the list would end up being sent only to the sender of the mail
<wolfspraul>
the purists are saying that's great, you should err on the side of privacy
<wpwrak>
yeah, i prefer the unforced variant for myself too. maybe not for others, though ;-)
<wolfspraul>
I respect that in general, but it would create so much maintenance headache for me that I chose to use the more 'convenient' reply-to feature.
<wolfspraul>
I think 90% of all email users don't understand the difference between 'reply' 'reply all/group/list' whatever
<wolfspraul>
so I will not change the reply-to setting
<wpwrak>
and about 3/4 the ones that still arrive privately ought to go to the list anyway ;)
<wolfspraul>
the bug that is written up there is that for some reason, emails that people send to the list are not sent back to them, even though they are subscribed to the list
<wpwrak>
hmm. mine are.
<wolfspraul>
there is a configuration setting for each subscriber to turn this on or off (default is 'on'), but it doesn't work, at least not for many people
<wolfspraul>
I don't know why.
<wolfspraul>
need to debug it inside mailman/exim and also one of those many things that is just not high enough on the priority list.
<wpwrak>
am i the only one ? or it it perhaps a "sometimes" bug ?
<wolfspraul>
I don't know. But I don't get my own mails, for example, so at least I can easily reproduce this problem :-)
<wpwrak>
fire and forget ;-)
<wpwrak>
while packrats like me get their own stuff back. mailman knows its users pretty well :)
<kristianpaul>
:) n8
<kristianpaul>
tomorrow traveling to a town next to the pacific ocean :)
<wolfspraul>
nice
<kristianpaul>
just 2 hors from my home :D
<kristianpaul>
bye
<wolfspraul>
n8
<nebajoth>
lol
<nebajoth>
I guess dpkg is a bit of a memory hog on debian for the nn
<nebajoth>
we discussed this on the mailing list some time back
<nebajoth>
I've been using a microsd as swap space
<nebajoth>
and that's just about the only way that beast will work
<nebajoth>
so I was playing with it just now
<nebajoth>
and I discovered a neat little webpage that explained how to enable /proc/sys/vm/overcommit_memory
<nebajoth>
and let the linux kernel play a little more fast and loose with its memory
<nebajoth>
the negative ramification of which, of course, is that it (seemingly randomly) chooses processes to KILL when memory becomes in too great a demand
<nebajoth>
so I was just experimenting with that
<nebajoth>
and the process it chose to shut down
<nebajoth>
was my ssh connection
<nebajoth>
-_-
<nebajoth>
not gonna work
<wolfspraul>
:-)
<wolfspraul>
I read somewhere that more recent kernels like 34 or 35 introduced 'memory compression'
<wolfspraul>
no idea whether/how/how well this works
<nebajoth>
as if i/o on this thing weren't slow enough :P
<nebajoth>
well, I'll look
<nebajoth>
still tweaking overcommit_memory and overcommit_ratio
<nebajoth>
don't want to release an updated debian rootfs until it can be done without a microsd