**** BEGIN LOGGING AT Fri Jun 20 02:59:56 2008 Jun 20 03:12:11 hi all Jun 20 03:14:16 Is anyone here? Jun 20 10:58:20 can I see it as safe enough open a port with ssh-dropbear with root login disabled? Jun 20 16:32:38 does slugosbe have /var/log/messages? Jun 20 16:35:52 yes Jun 20 16:36:27 hmmm, i don't see it Jun 20 16:36:50 do you know what i'm doing wrong? Jun 20 16:37:29 no Jun 20 16:39:02 ./var/log is a link to /var/volatile/log Jun 20 16:39:11 and messages isn't in /var/volatile/log Jun 20 16:40:53 If you do "turnup disk" you get /var/log/messages; if you "turnup flash" the messages are not logged (in order to reduce wear on the flash) Jun 20 16:41:17 If you are just running from internal flash, there's no logging of messages either. Jun 20 16:43:06 mwester: thx for the info Jun 20 16:49:55 'morning all Jun 20 16:51:28 I've been noticing a lot of ipkg users complaining about the transmission ipkg in both the transmission forum as on irc. Jun 20 16:52:56 the problem as i understand it is that optware follows svn instead of using released tarball Jun 20 16:53:07 eno: correct Jun 20 16:53:21 which is not correct behavior Jun 20 16:53:31 right, i agree Jun 20 16:54:03 i'll notify the package maintainer, or take a look at correcting that if i have some time Jun 20 16:54:45 Thanks! Jun 20 16:55:46 np Jun 20 16:57:25 I noticed that the wiki page is a bit chaotic. I had a hard time convincing myself that it was actually about transmission ;) Jun 20 16:58:00 unfortunately i'm not a transmission user myself Jun 20 16:58:21 so this would really need some help from experienced transmission user Jun 20 16:58:56 hmm, not necessarily... Jun 20 17:00:02 but I'm not an optware user ;) Jun 20 17:00:57 anyway, if you, or oleo have any questions, feel free to join our irc channel! Jun 20 17:02:05 sure, thx Jun 20 17:05:47 hey ho Jun 20 17:29:35 eno: note: the (Transmission related project) Clutch, is not, never was, a mac specific app, but a just a website. (though an integrated mac build exist) Jun 20 17:31:25 Waldorf: is transmissiond a CGI daemon added by oleo? Jun 20 17:32:42 dunno what he called his scripts... Jun 20 17:33:05 i'm inclined to take that out right now Jun 20 17:34:15 Transmission itself does not provide an cgi... Jun 20 17:34:31 eno: you're working on a working transmission package? Jun 20 17:34:51 k, i guess it's more important to have it work with clutch Jun 20 17:35:13 the chi is not needed for clutch Jun 20 17:35:20 *cgi Jun 20 17:35:38 right Jun 20 17:35:50 Clutch talkes to the transmission-daemon directly Jun 20 17:35:52 clutch is php based Jun 20 17:35:59 atm yes Jun 20 17:36:53 transmission has moved to JSON (in development), so clutch wil probably be able to run without php in the future Jun 20 17:37:15 that's cool Jun 20 17:37:21 very Jun 20 17:37:43 then what will be the replacing web stack? Jun 20 17:37:52 it even provides syntax to allow sever-side filtering and sorting Jun 20 17:38:12 eno: what do you mean? Jun 20 17:38:46 without using php, what would be the replacement? ajax? Jun 20 17:39:49 yes, ajax. but it could be that php will still be used for some site elements. it will just be possible to go without. Jun 20 17:40:53 (actually, the Clutch project has halted a bit, not enough spare time by their devs) Jun 20 17:41:16 i c Jun 20 17:42:46 on small NAS like slug, lua and cgi might be a good choice for server side Jun 20 17:43:47 in general? or how do you mean? Jun 20 17:44:29 just in general, like the web interface of openwrt Jun 20 17:45:15 in the case of transmission, since there's already a daemon, serving json is also a good idea Jun 20 17:46:16 yes, since the client side can do all the processing. Jun 20 17:46:28 once provided with the json objects Jun 20 17:46:51 + transmission is really low on resources... Jun 20 17:47:17 we even get stories of ppl running it on their nokia phones ;) Jun 20 17:47:34 cool Jun 20 17:49:45 yes, he asked how to make transmission's memory buffer bigger as to spare the flash drive... Jun 20 17:54:33 well, got to go Jun 20 17:54:39 cya! Jun 20 17:54:45 hope there'll be a better transmission package soon ;) Jun 20 17:54:51 cyall Jun 20 17:57:31 eno: the Transmission page, it would be nice it it focused on Transmission(-daemon) and compatibility first, third-party scripts/notes afterwards. Jun 20 17:57:45 i agree Jun 20 17:58:05 I have no idea what to expect when i would install this... Jun 20 18:08:39 Waldorf: http://trac.nslu2-linux.org/optware/changeset/8543 Jun 20 18:10:36 eno: does TRANSMISSION_SITE have to link to the download page? Jun 20 18:11:15 yes Jun 20 18:11:38 yes, i see, reading the full mk file is more explaining Jun 20 18:21:06 eno: our dev says, not to link to svn. Jun 20 18:21:50 also, if you do link to the svn, why not the latest, instead of on revision? Jun 20 18:21:52 link to svn is commented out Jun 20 18:22:09 we cannot support moving target Jun 20 18:22:54 in the few mk files we track svn, we use either a specific REV or tag Jun 20 18:23:18 this way, today's build and tomorrow's build would be the same Jun 20 18:23:28 isn't HEAD or LATEST supported (dunno much about svn though) Jun 20 18:24:03 it is supported by svn, but not a good idea to use HEAD for packaging Jun 20 18:24:19 today's HEAD will be different from tomorrow's HEAD Jun 20 18:25:02 then i suggest removing it completely. especially as long as the project is as active as now. Jun 20 18:25:57 i dunno, it's commented out and would not hurt any1 Jun 20 18:26:06 k Jun 20 18:26:35 what is this /opt/etc/transmission.conf file? it isn't from transmission Jun 20 18:27:55 it's probably something oleo added Jun 20 18:29:19 does eleo ever appear here? Jun 20 18:29:49 not as often Jun 20 18:36:49 eno: btw there is a difference in configure between release and svn Jun 20 18:36:52 ! Jun 20 18:37:36 eno: http://trac.transmissionbt.com/browser/trunk/README Jun 20 18:38:31 there is, svn using ./autogen.sh Jun 20 18:38:51 the optware/make/transmission.mk takes that into consideration Jun 20 18:39:58 ok Jun 20 18:40:56 the new ipk is in cs05q3armel, nslu2, and slugosbe feed Jun 20 18:42:35 eno: btw 1.30 is close to being released. However, feedback on the new JSON based rpc is highly desired, know anyone who would wanna go through the specs/try it out? Jun 20 18:45:15 i'd like to, but with optware i'm already quite busy Jun 20 18:45:30 I understand. Jun 20 18:45:42 maybe you can send a message to nslu2-developers yahoo group Jun 20 18:45:57 or if you don't want to sign up, send a message to me Jun 20 18:46:07 and i can forward it to nslu2-developers Jun 20 18:46:36 k, I'll see what our back-end dev says Jun 20 18:51:54 eno: Waldorf: ok, thanks for the info Jun 20 20:05:11 eno: would it be possible to have a transmission-devel ipkg? might be interesting for those who do want to want to try out the upcoming release... Jun 20 20:10:07 it's possible, but takes a bit more effort to maintain Jun 20 20:10:38 one thing is, although we have stable/unstable feed, they're the same right now Jun 20 20:10:51 lol Jun 20 20:11:03 and -devel probably should conflict with each other Jun 20 20:11:28 you know, we're not like debian, we only have limited resource Jun 20 20:11:59 I know, just wondering Jun 20 20:12:52 the obstacle really is what is the criteria and process, for moving packages between stable and unstable Jun 20 20:12:58 personally, I have very little experience with distros Jun 20 20:13:13 hmm, i c Jun 20 20:13:39 if that process is too manual, we cannot afford it Jun 20 20:13:40 on mac, it sometimes a lot more straight forward... ;) Jun 20 20:14:17 do you use macports or fink? Jun 20 20:16:27 macports occasionally, fink is always such a hassle (unless I remember wrong) Jun 20 20:17:10 transmission probably has its own distribution .app for mac Jun 20 20:18:24 well, it's packaged in a dmg, so just download and drag 'n drop install Jun 20 20:20:04 i know Jun 20 20:20:32 ipkg is more like macports and fink Jun 20 20:20:48 it needs to manage dependencies, conflicts Jun 20 20:20:48 ya, i know Jun 20 20:21:30 on mac, dependancies are just included in the .app bundle Jun 20 20:23:24 it's not as minimalistic and there maybe redundencies, but it works nicely there Jun 20 20:26:21 maybe not minimalistic, but it doesn't rely on (under staffed) distro maintainers ;) Jun 20 20:28:49 of course it all depends on the kind of app and its deployment target. Jun 20 20:29:25 you can't do drag 'n drop installs on an NAS, I suppose ;) Jun 20 20:31:52 eno: actually, you could. with LLVM installed on the NAS, one could compile once and easily deploy/install on different types/brands of NAS. even if they use different cpus Jun 20 20:40:00 i'll need to read up on LLVM, thx for the info Jun 20 20:42:19 eno: there's a new thing called LLVM-GCC, basically GCC which prepares the code for LLVM (same syntax, so most configure script need no change) Jun 20 20:43:19 m Jun 20 20:43:53 m' Jun 20 20:51:16 sorry,if, i sent weird msg my puter was amok **** ENDING LOGGING AT Sat Jun 21 02:59:56 2008