#emc | Logs for 2004-12-06

Back[00:00:55]<paul_c> dang... anaconda.condig needs some additional work. [00:02:01]<robin_sz> annaconda ... vaguely remmeberthat [00:02:31]<robin_sz> I vaguely remember seeing it crash during RH installs anyway :) [00:32:21]<asdfqwega> A quick question for cradek or jepler: How demanding is AXIS as a system load? The box's I have available to try it on are Duron 600/Celeron 400, with Nvidia/TNT cards [00:34:29]<asdfqwega> robin_sz: I thought 'digimatic' calipers used a magnetic scale with a vernier method [00:35:20]<paul_c> Some are capacative, others inductive, and a few magnetic. [00:35:41]<asdfqwega> As a machinist, I hate 'em - they lose position, same goes for micrometers [00:36:05]<asdfqwega> They do have a use around abravisive contamination [00:36:17]<asdfqwega> er, abrasive [00:36:49]<asdfqwega> A friend uses one, making pool queues - super micro-fine wood dust [00:38:07]<asdfqwega> But they're not good for production use - you never know when they're going to 'slip', so you have to calibrate and set the zero often [00:39:45]<asdfqwega> Back to cleaning [sigh]...cables and tools and debris, oh my [00:42:44]<robin_sz> * robin_sz pays attention again [00:43:05]<robin_sz> my christmas project is to pull everything out of the workshop into the yard [00:43:09]<robin_sz> and then put it back [00:43:14]<robin_sz> in some sort of useful order [00:43:19]<robin_sz> wait ... [00:43:39]<robin_sz> my christmas project is to put a new cylinder gasket in the fork truck ... and then ... [00:43:56]<robin_sz> sodding hting uses more oil and water than propane [01:28:36]<CIA-11> 03Zathras 07BDI build system * 10Babylon Cluster/comps.xml: File changed. New revision:1.14 [01:44:38]<paul_c> * paul_c wonders if jmkasunich is still awake... [02:55:54]<jepler> asdfqwega: These are the machines Chris or I have been developing AXIS on: 1.5GHz Pentium M, 2.8GHz Pentium4, "2400+" AMD Athlon. If you have accelerated OpenGL, duron 600 and celeron 400 should do OK, but not be silky smooth. [02:56:37]<jepler> asdfqwega: I know cradek has actually tried axis on a a <400MHz Pentium II laptop with no 3d accel, and it runs but not well [03:00:40]<jepler> asdfqwega: but opengl accel should make a big difference [11:33:35]<alex_joni> hello [11:35:53]<paul_c> Morning alex_joni [11:36:04]<alex_joni> morning paul_C [11:36:26]<alex_joni> difficult to wake up :-) [11:43:03]<paul_c> You disappeared a fraction too early last night [11:43:54]<paul_c> was going to let you download the beta test... [11:49:23]<alex_joni> but now you changed your mind ;) [11:49:32]<alex_joni> last night I was at home.. on dial-up [11:49:38]<alex_joni> now I could do that... [11:52:23]<paul_c> daytime will knock my bandwidth. [11:53:41]<alex_joni> ok.. I can cron the dl [11:55:19]<paul_c> I found a couple of "interesting" issues that need to be fixed first. [11:56:32]<alex_joni> ok... I can wait [11:56:48]<alex_joni> btw, before I forget.. I'll go away on Wednesday [11:57:08]<alex_joni> going on a business trip to germany, I'll be back next week [11:57:17]<alex_joni> so I guess I'll miss the chat on sunday [11:58:05]<CIA-11> 03Zathras 07BDI build system * 10Babylon Cluster/isolinux.cfg: File changed. New revision:1.2 [12:35:14]<alex_joni> * alex_joni is right back [12:43:13]<alex_joni> * alex_joni is back [12:43:38]<alex_joni> I had a very brief chat with zwisk last night [12:47:38]<paul_c> 'bout install targets ? [12:48:28]<alex_joni> yeah... a little, but he didn't have much time :( [12:48:33]<alex_joni> maybe the next time [12:48:44]<alex_joni> he was complaining about no thaving a working rtai.rpm [12:49:28]<alex_joni> he was complaining about not having a working rtai.rpm [12:50:21]<paul_c> I had the same problem with rtlinux for bdi-2.xx [12:50:51]<paul_c> and to a lesser extent, with the rtai deb package. [12:51:08]<alex_joni> I can imagine [12:54:30]<paul_c> There isn't much I can do to help zwisk on that front.... It is something he'll have to work on. [12:56:25]<alex_joni> I know.. [12:56:31]<paul_c> arrgg... Got rtai.spec from the TNG somewhere.... along with a tweaked kernel spec. [12:58:49]<paul_c> back in a bit. [13:03:01]<alex_joni> * alex_joni is gone for today [13:30:50]<paul_c> cd [13:37:09]<Timbo> what's the second worst thing you can type on irc? [13:37:11]<Timbo> su [14:12:41]<jepler> morning guys [14:15:42]<paul_c> Morning jepler [14:16:33]<paul_c> Doesn't look like axis will run with the 2.6.9 build of EMC. [14:16:46]<cradek> hello [14:16:57]<cradek> can you give more details? [14:17:21]<paul_c> cradek: Thanks for correcting my error in the abort bug fix in emc2 [14:17:32]<cradek> no problem [14:17:50]<paul_c> damned maze of switch statements... [14:17:51]<cradek> I tested it, and I still had the bug [14:17:59]<cradek> I would have never noticed it by looking at the patch [14:18:03]<cradek> yeah it's nasty in there [14:18:35]<jepler> what, did the patch helpfully apply to the wrong switch statement entirely? [14:18:44]<paul_c> As soon as I looked at the full source file, I saw the error in patching. [14:18:50]<cradek> jepler: it was a meat-patch [14:18:55]<cradek> jepler: (I think) [14:47:09]<cradek> paul_c: give me more information about why axis isn't working for BDI [14:49:02]<paul_c> This build uses libnml from emc2 with the directory layout of emc1 [14:49:39]<cradek> that sounds strange but I don't see it as a big problem [14:50:48]<paul_c> agreed, it isn't a problem. [14:51:14]<cradek> so what problem are you having with axis? [14:52:01]<paul_c> Haven't tried to run it yet, jist a quick look at the code indicated that there would be problems. [14:52:15]<cradek> like what? [14:52:59]<paul_c> headers and libs for the C stuff [14:53:37]<cradek> it just takes some changes to setup.py to make it build with emc2 only [14:54:25]<cradek> yes, the names of the directories and libs are a little different, but that's no problem [14:55:27]<paul_c> yup. minor problem. [14:55:39]<cradek> so is there anything else? [14:55:43]<cradek> I'll help you fix it however I can [14:56:03]<cradek> I think it's important for it to work on this BDI, otherwise many people won't be able to try it [14:56:16]<paul_c> nope - Just got to get emc to compile on the main dev. box [14:58:17]<paul_c> Once I get this to compile, I'll have a go at axis. [14:58:38]<cradek> ok [14:58:56]<cradek> I'll be here until at least 2200UTC [15:02:01]<paul_c> I'll probably be around till much later than that. [15:18:55]<les> cradek: would you happen to have a screenshot of AXIS? [15:20:30]<cradek>http://axis.unpy.net[15:20:44]<cradek> lots of info about it there [16:10:48]<jepler> les: screenshots in the "about" link [16:33:27]<jepler> paul_c: I'll try to be around too [16:35:10]<paul_c> resolved the compile errors, now building another CD ready to try an install. [17:12:38]<les> wow the axis screenshots look great...I will want to try this out for sure [17:16:19]<les> hope those old computers have enough system resources left to run it... [17:23:31]<cradek> les: thanks [17:26:07]<les> yw chris...great job [17:27:16]<cradek> let me know if you have trouble building or installing it [17:27:37]<cradek> there are a couple fixes already, mostly for older systems, described on the web page [17:28:16]<les> I will just follow the instructions....I assume I do not have to rebuild emc? [17:29:32]<cradek> you do need a built emc source tree [17:30:44]<les> have that...several in fact...I keep old versions intact when making a change [17:32:47]<les> often when I try to do individual makes I get garbage (don't know enough about gcc I guess) so I just build the whole thing [17:33:30]<cradek> les: it's probably the build system, not you, but a full build doesn't take long [17:34:44]<les> right..it's real quick so no problems [18:49:52]<les> hmm got an email from another happy customer with his emc carved teak sign [18:51:40]<les> looks like many thousands of customers will end up with products made with emc [18:52:09]<les> I wonder if anyone else is using the program for production? [19:17:31]<cradek> who was making those TPS sensors? [20:40:00]<les> sorry went to the shop [20:40:21]<les> heh the TPS was me too... [20:41:53]<les> but that was just all the design protos...we have cut injection molds now [21:57:50]<paul_c> Wahooo.... [22:00:26]<paul_c> axis is running on 2.6.9 [22:00:34]<cradek> YAY!! [22:00:47]<paul_c> * paul_c is feeling smug [22:01:01]<paul_c> hacked python al by myself ;) [22:01:10]<cradek> setup.py? [22:01:16]<paul_c> yup [22:01:16]<asdfqwega> Yoing! [22:01:17]<cradek> congrats [22:01:39]<asdfqwega> Half a cheer for Paul - Hip! Hip! Hoo- [22:01:40]<cradek> if you don't want it to be the default, let's put a commented out DISPLAY=axis in the ini [22:02:04]<cradek> it will be great if people can try it easily [22:02:20]<paul_c> Will add an entry in the run script for axis so that we don't have to symlink it [22:02:36]<cradek> ok, cool [22:03:08]<paul_c> Now how do we create a deb (with the required deps) ? [22:03:25]<cradek> I don't know, jeff did the first one [22:03:51]<asdfqwega> I plan on trying AXIS before the week is out - been doing to much computer fiddling of late [22:04:17]<cradek> if you have a modern OS install it's really easy [22:04:29]<cradek> if you have to build all the python stuff from source, not so easy [22:04:39]<paul_c> a suggestion for the build instructions [22:04:41]<asdfqwega> I'm using the Live rc46 - it should be easy enough [22:04:52]<cradek> asdfqwega: there's a binary package on the web site [22:04:59]<asdfqwega> Cool [22:05:03]<cradek> paul_c: shoot [22:05:21]<paul_c> aptget python-dev, xlibmesa-gl-dev, & xlibmesa-glu-dev [22:05:45]<cradek> jeff had xlibmesa-dev [22:05:47]<cradek> is that wrong? [22:05:54]<alex_joni> g'evening [22:05:57]<cradek> alex_joni: hello [22:06:25]<alex_joni> got the mail to the list? [22:06:35]<cradek> about axis? yes [22:06:42]<cradek> glad to hear you like it so far [22:06:48]<alex_joni> ;) [22:07:22]<paul_c> OK... xlibmesa-dev is a meta package for gl & glu dev [22:07:38]<alex_joni> hi paul [22:07:40]<cradek> aha [22:07:46]<paul_c> Yo alex_joni [22:07:49]<cradek> paul_c: ok, I'll leave it as the simpler one then [22:08:20]<cradek> paul_c: will this be called BDI-3? [22:08:46]<paul_c> Dragging axis across the screens, I have noticed it doesn't redraw on screens 2 & 3 [22:09:31]<cradek> we'll look at that as soon as we can run this BDI! [22:10:19]<paul_c> How many will be running multiple heads [22:11:09]<paul_c> It's a problem with openGL - I find most things will only run on screen 0 [22:11:13]<alex_joni> paul: 2 & 3 are multiple heads on your setup? [22:11:24]<cradek> paul_c: ahh that would explain it [22:11:45]<cradek> I thought you meant virtual desktops, which would be extremely strange, but you do actually mean screens [22:13:48]<paul_c> Have three monitors on one box here [22:14:34]<cradek> paul_c: will this be called BDI-3? [22:14:52]<paul_c> sorry... Should have answerd that... [22:15:11]<cradek> assumed you just missed it [22:15:23]<paul_c> Not sure what to call it. [22:15:31]<cradek> ok [22:15:37]<cradek> I'm calling it "the upcoming BDI release" then [22:15:49]<paul_c> Had BDI-2.xx, BDI-TNG, umpteen BDI-Lives [22:16:23]<paul_c> How about BDI-6 ? [22:16:41]<cradek> BDI-2005? [22:17:01]<cradek> Mongoose BDI? [22:17:08]<cradek> I dunno, you tell me :-) [22:17:39]<paul_c> TNG should have been -3.xx [22:18:12]<paul_c> so BDI-4.00 [22:19:16]<paul_c> Hah... [22:19:38]<paul_c> * paul_c finds a file that doesn't plot fuly. [22:19:52]<cradek> you mean the preview is incomplete? [22:19:57]<paul_c> yes [22:20:13]<cradek> it gets coordinate systems and a few arcs wrong [22:20:20]<cradek> it will all be fixed in 1.0 [22:20:38]<cradek> (we are already making progress on 1.0) [22:20:47]<paul_c> This is previewing about 1/3 of the full plot. [22:21:02]<cradek> send me the file? [22:21:29]<paul_c> will do [22:22:06]<cradek> does it use g92, g54....g59.3? [22:22:32]<cradek> those will certainly display wrong [22:23:11]<ottos> day gents.. [22:23:17]<cradek> hello [22:23:28]<alex_joni> hi [22:23:46]<ottos> anything new and exiting? [22:23:56]<cradek> we just heard AXIS will be on BDI-4 [22:24:08]<paul_c> 14833 lines, and just G0 & G1 moves [22:24:09]<jepler> it's the first step to world domination! [22:24:20]<ottos> nice... [22:24:22]<cradek> paul_c: yeah I definitely want to see that [22:24:50]<cradek> jepler: ssshhhh! [22:25:19]<jepler> cradek: sorry [22:27:56]<paul_c> Ah.. jepler - Just the lad we need.. [22:30:58]<ottos> say for when is the new release due? [22:30:59]<paul_c> Two questions [22:31:10]<paul_c> ottos: Soon. [22:32:08]<paul_c> Can the "programs" dir default to emcsourcedir+programs ? [22:33:34]<cradek> paul_c: would you make up a list of things you find [22:33:41]<cradek> I will add them to the wishlist or buglist as appropriate [22:34:00]<paul_c> well... The only other question was how to build a deb [22:34:26]<cradek> ok, well I can't help with that [22:34:28]<cradek> but about the directories: [22:34:43]<cradek> I already added a wishlist item that it should default to the directory you last loaded a file from [22:34:53]<cradek> that's a separate issue from the first default directory, I know [22:34:58]<cradek> but it will make it better [22:35:10]<cradek> I'll add another wishlist item saying the initial directory should be programs/ [22:35:35]<paul_c> what if the default program dir was read in from the ini file ? [22:35:46]<cradek> that would be fine too [22:35:50]<cradek> might be kind of nice [22:36:00]<paul_c> probably be better in the long run [22:36:12]<cradek> agreed [22:36:30]<cradek> we would have to fix all the guis [22:36:33]<cradek> but that wouldn't be hard [22:36:36]<paul_c> where's the feature request page ? [22:36:48]<cradek> right now, it's the TODO file in our cvs [22:36:59]<cradek> * file open dialog should remember the directory from previous open [22:36:59]<cradek> * file open's initial default directory should be read from the ini [22:37:07]<cradek> it now has these two things [22:37:42]<paul_c> and needs to be able to handle ~/foo correctly (which emc doesn't at the moment [22:37:50]<cradek> it already does [22:38:36]<cradek> it's a smart dialog, you can type a dir name and hit enter, and it will show you that dir [22:38:54]<cradek> or you can type ~/file.ngc and it opens it directly [22:39:14]<paul_c> One advantage of using a higher level language. [22:40:19]<cradek> gotta go, I might be back in a few hours [22:40:40]<cradek> I'll read /msg later if you have other thoughts [22:41:01]<alex_joni> paul: wanna hardcode the path to the inifile? [22:41:11]<alex_joni> I meant in the inifile [22:41:54]<paul_c> * paul_c waits for python-axis to add to the CD. [22:41:56]<alex_joni> I think this will get of an issue when doing a make install (this path needs to be changed) [22:45:24]<asdfqwega> Does G64 (motion blending) operate only between G01/2/3 moves? [22:45:34]<paul_c> alex_joni: The alternative is to follow the example of many other packages and enforce an install in order to run. [22:45:57]<asdfqwega> I'm working with my image->gcode python script, and I'm working with G00/1 moves [22:46:34]<paul_c> asdfqwega: Would have expected G64 to work with G0 moves. [22:46:43]<asdfqwega> And I don't see any difference [22:46:56]<alex_joni> paul_c: I don't think emc2 is there yet [22:47:26]<paul_c> emc2 has a long way to go. [22:47:28]<asdfqwega> Hm...would it be too much to hope that there's already an .ini variable to control the amount of blending? [22:47:37]<alex_joni> what if the path in the inifile points to the installed path (emc2 developers who run-in-place can handle that) [22:48:33]<paul_c> asdfqwega: No such variable that I know of in the ini file [22:49:05]<paul_c> alex_joni: The answer is simple - Pass an ini parameter on the command line. [22:49:24]<paul_c> emc.run -ini /foo/emc.ini [22:50:17]<asdfqwega> paul_c: Probably wouldn't matter anyway...I need a better machine before G64 would really pay off for this [22:50:33]<alex_joni> paul_c: so a different emc.ini than the one installed? (if I understand you right...) [22:51:16]<paul_c> On the next BDI release, there is only one master run script [22:51:43]<paul_c> all desktop icons call the runscript with an ini file name. [22:52:15]<alex_joni> I agree there [22:52:38]<alex_joni> what I was talking about was the programs path inside the ini file (emc.ini) [22:53:07]<alex_joni> if you fix the programs path inside emc.ini it must get modified during install (not that good) [22:54:34]<paul_c> Not really... the run script would prefix any relative paths with $(pwd) [22:55:06]<alex_joni> so the runscript reads the programs path from the ini and passes it to the DISPLAY? [22:57:09]<paul_c> Hmmm. The GUI program would be responsible for reading the ini file if it needs any variables of it's own. [22:58:31]<paul_c> One of the tenants of the EMC design is that each part can operate as a standalone program and use NML messaging. [22:58:41]<alex_joni> yeah but the gui would only know of the inifile and the folder of the inifile [22:59:09]<paul_c> Only the task controller & the kerenl modules need to run as an "item" [22:59:15]<alex_joni> and of course the location from where it was run (but that can easily be /usr/bin) [23:00:25]<alex_joni> but all the locations are modifyable by ./configure, so that complicates it a little [23:02:03]<alex_joni> anyways.. that's not that important right now.. I'll stop bugging you ;) [23:02:35]<paul_c> I still don't see it as an issue.. [23:03:28]<dave-e> ottos...you running the motenc-100 board? [23:03:46]<alex_joni> we'll address it when time comes [23:03:57]<paul_c> alex_joni: If [23:04:03]<alex_joni> yup [23:04:37]<ottos> sorry back... [23:04:47]<jepler> only thing I've wanted from the .run file would be to take a filename to open immediately. That way you could double-click a g-code file and AXIS will open with that file [23:04:55]<ottos> well...still getting all the cables/etc [23:05:30]<alex_joni> jepler: you could do that if you have one implicit inifile to open (and of course inifile-location) [23:05:53]<dave-e> ottos- maybe send me an email dengvall@charter.net so we can stay in touch [23:06:06]<paul_c> set a mime data-type for ngc files. [23:06:18]<ottos> sure..you have the same? [23:06:31]<dave-e> I'm having problems and i suspect I may be the only one [23:06:56]<paul_c> ottos: I also have a Vital card (for testing) [23:07:09]<dave-e> well i thought you said something about the vsi motenc-100 board yesterday [23:07:54]<dave-e> do you have a good compile of vital.o and vitalmod.o yet? [23:07:57]<ottos> questions about pinouts/etc... [23:08:07]<paul_c> dave-e: Have you tried messing with the offset values for the SCALE ? [23:08:25]<dave-e> paul...no i haven't [23:09:02]<dave-e> I think my problems are more fundamental [23:09:06]<paul_c> If you have drift in the DAC outputs, try a little bit of offset [23:09:26]<dave-e> well right now I have a stability problem. [23:09:48]<dave-e> even at low P I oscillate [23:09:56]<dave-e> enough to fault the amp [23:10:19]<dave-e> did bad things to the test servo motor [23:10:33]<paul_c> * paul_c could do with flying over to see the setup & play. [23:10:47]<dave-e> oh how i wish [23:11:20]<paul_c> Dec 20th for two weeks OK ? [23:11:39]<dave-e> wish had that kind of $$ [23:12:24]<dave-e> just to restore my confidence i moved the stg setup from my small mill to the mazak. took a couple of hours but [23:12:54]<dave-e> it is running fine on two axes with minimill...now I need to add homing [23:12:54]<alex_joni> * alex_joni is going to sleep [23:12:55]<alex_joni> bye [23:14:11]<ottos> Dave , did you consider omron D5A/B for home switch? [23:15:06]<dave-e> the mazak has all the home switches, etc already...I do have some automation direct switches to use on the small mill [23:15:27]<ottos> nice.. [23:15:34]<dave-e> my servo amps have + and - inhibits on them which is really nice. [23:15:46]<ottos> brand? [23:15:53]<dave-e> that way you have both a soft and hard limit [23:16:08]<dave-e> amps are servo dynamics [23:16:18]<dave-e> 1525BR [23:16:59]<ottos> i've snatched some Yaskawas SGDA, want to see them in action... [23:17:16]<dave-e> hmmm...are those ac? [23:17:26]<ottos> yup..220VAC [23:17:33]<dave-e> nice [23:17:44]<dave-e> you have amps for them yet? [23:17:56]<ottos> all sets.. [23:18:00]<dave-e> wow [23:18:50]<ottos> say for PID tunning any suggestios? [23:19:18]<dave-e> no really .... just bring up logging and pick your way thru. [23:19:31]<ottos> the hard way..:D [23:19:50]<dave-e> send me and email and I'll send you some stuff on tuning. [23:20:01]<ottos> ok. [23:20:16]<dave-e> gotta go pick at the system...............later [23:20:28]<ottos> ok.. [23:20:34]<ottos> night gents.. [23:28:14]<paul_c> Bump the version number up on the emc.deb. [23:35:46]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/Make.rules: File changed. New revision:Makefile [23:35:47]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/emc.ini: File changed. New revision:generic.ini [23:35:48]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/Makefile: File changed. New revision:1.15.2.1 [23:35:49]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/Makefile: File changed. New revision:iosh.cc [23:35:49]<paul_c> Standby [23:35:51]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/Makefile: File changed. New revision:dro.c [23:35:51]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/Makefile: File changed. New revision:1.13.2.1 [23:35:51]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/Makefile: File changed. New revision:emctaskmain.cc [23:35:52]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/Makefile: File changed. New revision:1.7.2.1 [23:36:22]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/- New directory: File changed. New revision:NONE [23:36:38]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/- New directory: File changed. New revision:NONE [23:38:06]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/emc.png: File changed. New revision:hello.gif [23:38:07]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/G code editor.desktop: File changed. New revision:Sherline_inch.desktop [23:43:12]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/comps.xml: File changed. New revision:1.15 [23:45:04]<CIA-9> 03paul_c * 10emc2/src/emc/task/emctaskmain.cc: Didn't quite get all of Chris Radek's bug fix in. [23:46:44]<paul_c> That should kick off the farm in a little while ;) [23:47:23]<jepler> cradek: is the test for 'cutting' something you added to emcplot3d? [23:47:47]<CIA-9> 03Zathras 07BDI build system * 10Babylon Cluster/picax.xml: File changed. New revision:1.12 [23:48:59]<paul_c> jepler: What's the quick'n'easy way to package axis in a deb ? [23:49:41]<robin_sz> brown paper and string [23:50:19]<cradek> jepler: line #? [23:50:24]<jepler> paul_c: I took some stuff from the web called bdist_deb, and put it in my local tree. It's not even in CVS yet [23:50:52]<jepler> cradek: around 793 [23:51:34]<paul_c> jepler: OK... I'll get a CD ready for Ray and we can add axis at a later stage. [23:51:48]<cradek> I'm going to have to look in cvs [23:51:59]<cradek> I think it doesn't work right anyway, but I'm not sure [23:52:07]<jepler> paul_c: I could tar up the "debian" directory that bdist_deb created [23:52:58]<paul_c> That would do - I can create a package here with the tweaks needed for the 2.6.9 build [23:53:06]<jepler> OK, e-mail? [23:53:31]<cradek> jepler: yes, in 1.12 [23:53:51]<cradek> jepler: but I'm not sure it always works right