Back
    [00:01:12] <cradek> hey the stepper driver came today! 
    
[00:01:18] <jmkasunich> cool 
    
[00:01:28] <jmkasunich> so you can play with the lathe this weekend 
    
[00:02:10] <cradek> yep 
    
[00:03:27] <cradek> hmm, mystery connectors 
    
[00:03:36] <jmkasunich> which ones? 
    
[00:03:55] <cradek> it has a db25 and a db15 
    
[00:04:17] <jmkasunich> plus the motor connectors I assume? 
    
[00:04:21] <cradek> yes 
    
[00:04:30] <jmkasunich> db25 for PC, and db15 for the switches on the machine? 
    
[00:04:31] <cradek> I'll ignore the one I don't understand, and maybe it'll work 
    
[00:04:46] <jmkasunich> take the cover off and trace a few wires? 
    
[00:04:50] <cradek> the lathe has two db25s 
    
[00:05:57] <jmkasunich> the machine itself has two db25s? 
    
[00:06:23] <cradek> yes 
    
[00:06:30] <cradek> probably one goes to this, and one goes to the computer 
    
[00:06:35] <jmkasunich> seems like a lot of wires 
    
[00:06:39] <cradek> or ... maybe something else 
    
[00:06:58] <cradek> I think he wanted to make it interesting for me! 
    
[00:07:06] <jmkasunich> the lathe doesn't have a box or anything does it? wires go straight from the connector(s) to the switches and such? 
    
[00:07:19] <cradek> there are lots of wires all taped up so you can't see them 
    
[00:10:38] <jmkasunich> tape can be untaped 
    
[00:14:54] <cradek> I unwrapped some stuff, it's not as bad as I thought 
    
[00:23:12] <cradek> a simple picture would have really helped... 
    
[00:24:05] <cradek> crap, forgot to eat, brb 
    
[00:31:39] <cradek> ok I'm not getting this so far 
    
[00:31:54] <cradek> the connector I think goes to the computer has wires to 1-8, 11, 20,23,25 
    
[00:32:19] <cradek> 11 is an input, but 20,23,25 aren't 
    
[00:33:18] <jmkasunich> strange 
    
[00:33:50] <cradek> there's also a small black box (shrink tubing filled with epoxy) that I suspect holds something 
    
[00:34:01] <jmkasunich> drat 
    
[00:34:03] <cradek> that's between the switches and this connector 
    
[00:34:12] <jmkasunich> I hate mysterious lumps of epoxy 
    
[00:35:22] <cradek> I'm afraid I'm going to have to cut off at least some of this shrink tubing 
    
[00:35:35] <cradek> but there's no way to replace it without unsoldering 
    
[00:36:04] <jmkasunich> maybe you could ohm things out? 
    
[00:36:12] <jmkasunich> how big is the black box? 
    
[00:36:20] <jmkasunich> might just be some pullup resistors? 
    
[00:36:24] <cradek> AAA battery 
    
[00:36:41] <cradek> I don't get what they would pullup TO 
    
[00:36:55] <jmkasunich> hmm 
    
[00:37:42] <jmkasunich> you sure about those pin numbers? 
    
[00:37:57] <cradek> yes 
    
[00:38:12] <jmkasunich> 1 thru 9 are outputs from the PC, 10-17 are a mix of in and out 
    
[00:38:14] <cradek> it's one of the DBs that has the numbers on it 
    
[00:38:26] <jmkasunich> 18 and up are ground I think 
    
[00:38:39] <cradek> the 1-8 are one size of wire, 11-20-23-25 are bigger 
    
[00:38:53] <cradek> I would guess 1-8 go directly to the other DB (long cable) 
    
[00:39:03] <cradek> 11-20-23-25 probably go to the black box and then the switches 
    
[00:39:19] <jmkasunich> the data port (usually with step/dir) is pins 2-9, not 1-8 
    
[00:39:31] <cradek> right 
    
[00:39:44] <cradek> 1 is another output 
    
[00:40:00] <jmkasunich> yeah, but emc has never used that for step/dir 
    
[00:40:00] <cradek> the mightydrive has an outlet marked spindle, I bet pin 1 turns it on 
    
[00:40:07] <jmkasunich> estop maybe? 
    
[00:40:08] <jmkasunich> or spindle 
    
[00:40:16] <cradek> no sign of estop 
    
[00:40:32] <jmkasunich> ok 
    
[00:41:03] <cradek> still the pins to the mightydrive(?) are 1-8, so one is probably missing (doesn't matter) 
    
[00:41:24] <jmkasunich> take the cover off the mighty drive yet? 
    
[00:41:39] <cradek> no, can't find the right size allen wrench 
    
[00:42:06] <cradek> my organized workspace strikes again 
    
[00:43:30] <cradek> aha, torx is close enough 
    
[00:44:06] <jmkasunich> heh 
    
[00:48:56] <cradek> aha, in the mightydrive, pin 11 is spindle control 
    
[00:49:28] <cradek> step/dir ARE 1-8 
    
[00:49:37] <jmkasunich> thats really strange 
    
[00:49:59] <jmkasunich> especially since pin 11 is an input 
    
[00:53:28] <cradek> pin 23 goes somewhere to the A axis driver 
    
[00:53:49] <cradek> the A axis driver is completely different from the other 3, including its connections to the breakout board 
    
[00:57:48] <cradek> 25 is ground 
    
[00:57:53] <cradek> 20 is a mystery 
    
[01:03:56] <cradek> http://www.microkinetics.com/optistep.htm 
    [01:04:01] <cradek> hey, a big clue here 
    
[01:04:27] <jmkasunich> heh, it wasn't designed for a parport at all 
    
[01:04:33] <cradek> nope 
    
[01:05:01] <jmkasunich> time to get out the slobbering iron 
    
[01:05:24] <cradek> no, I bet it's wired right in this cable 
    
[01:06:26] <jmkasunich> what cable? 
    
[01:06:39] <cradek> the one between the two DB25s that came attached to the lathe 
    
[01:06:49] <jmkasunich> ah, translator 
    
[01:07:10] <cradek> and the black box might be pullups, because there's +5 available on that pin 25 I think? 
    
[01:07:19] <jmkasunich> could be 
    
[01:08:38] <cradek> I don't trust this picture completely though - it shows pin 11 is a ground, but I know it's spindle control 
    
[01:09:09] <cradek> oh, wrong 11 
    
[01:48:42] <cradek> wooooo 
    
[01:48:47] <cradek> I have motion 
    
[01:48:50] <cradek> and switches 
    
[01:48:50] <jmkasunich> cool 
    
[02:03:32] <jmkasunich> what config are you using? 
    
[02:05:27] <cradek> I started with stepper-xyza but copied it to nist-lathe 
    
[02:05:31] <cradek> (I'll put it in cvs) 
    
[02:08:45] <jmkasunich> why xyza? there's no A (and no Y) 
    
[02:09:30] <cradek> well I have four drivers... 
    
[02:35:56] <cradek> X homes! 
    
[02:36:06] <jmkasunich> cool 
    
[02:36:51] <jmkasunich> CL is gonna be frustrating for a certain class of users 
    
[02:37:01] <cradek> don't know anything about it... 
    
[02:37:15] <jmkasunich> they want one or two rungs worth of logic, emc itself doesn't do that, and CL is overkill 
    
[02:37:29] <jmkasunich> for example, wholepair on the other channel 
    
[02:37:36] <jmkasunich> he wants an external estop button 
    
[02:38:30] <jmkasunich> simple with CL, but I dread trying to explain it to him 
    
[02:39:01] <jmkasunich> I pointed him at the wiki page that ray did that goes thru exactly the setup he needs for his estop 
    
[02:39:27] <jmkasunich> but thats a learning curve we really don't want to force "simple machine" guys to climb 
    
[02:39:55] <cradek> he just wants a button that signals emc to stop? 
    
[02:40:03] <jmkasunich> yeah 
    
[02:40:04] <cradek> or that turns off the hardware too? 
    
[02:40:09] <jmkasunich> yes 
    
[02:40:19] <jmkasunich> uhhhh 
    
[02:40:20] <jmkasunich> no 
    
[02:40:28] <cradek> ok, just a signal to emc 
    
[02:40:34] <jmkasunich> I don't think a hardware path occurred to him 
    
[02:40:49] <cradek> can't you put a button between two parport pins (the estop out and estop in)? 
    
[02:41:08] <jmkasunich> he has his estop hooked to pin 13 of the parport, and a drive enable hooked to pin 1 
    
[02:41:19] <jmkasunich> hmm 
    
[02:41:21] <jmkasunich> that might work 
    
[02:41:38] <jmkasunich> I normally think of buttons as being between vcc and input, or gnd and input 
    
[02:41:41] <jmkasunich> not from output to input 
    
[02:42:32] <cradek> maybe you need a resistor too 
    
[02:42:40] <cradek> I'm fuzzy about how it works, if you can't tell 
    
[02:42:41] <jmkasunich> but if he configured an output to go low when EMC is ready to go, then it could go thru the NC button and pull an input low 
    
[02:42:55] <jmkasunich> I'm pretty sure he already has a pullup on the input 
    
[02:43:46] <jmkasunich> yeah, he says "I want pin 1 (enable to drives) to go low when pin 13 (input from red button) goes high 
    
[02:43:57] <jmkasunich> and he said the button is normally closed, open when you hit it 
    
[02:44:09] <jmkasunich> so he must have a pullup (or the parport has one) 
    
[02:44:23] <jmkasunich> he could connect the other end of the button to an output instead of ground 
    
[02:50:48] <jmkasunich> this is incredibly frustrating - its one thing to tell folks how to use the software, but I don't want to, can't, and won't, teach them how to design a machine control system 
    
[02:51:01] <jmkasunich> thats not a job for the clueless 
    
[02:51:55] <SWPadnos> heh 
    
[02:57:21] <cradek> jmkasunich: do you know what acceleration homing uses?  It sounds much higher than mdi g0 accel 
    
[02:57:44] <jmkasunich> it should be the axis accel 
    
[02:57:47] <jmkasunich> same as jogging 
    
[02:58:01] <jmkasunich> it ignores traj accel tho, since that applies only to coordinated motion\ 
    
[02:58:28] <jmkasunich> try jogging and see if that sounds the same 
    
[02:58:44] <cradek> yep 
    
[02:58:48] <cradek> but g0 accel is lower 
    
[02:58:59] <cradek> maybe it's my 95% hack, but it seems like I wouldn't notice that 
    
[03:00:10] <jmkasunich> you could scope it (pita sticking the ddts in there) 
    
[03:00:24] <jmkasunich> your traj limit is the same as your axis limit? 
    
[03:00:42] <cradek> oh, I know what it is, it's the .5 issue 
    
[03:00:46] <cradek> forget I said anything 
    
[03:00:49] <jmkasunich> heh 
    
[03:04:20] <cradek> yep if I use g61, it sounds about the same 
    
[03:04:32] <cradek> so it's a feature *cough cough* 
    
[03:04:46] <jmkasunich> * jmkasunich smiles 
    
[03:05:10] <jmkasunich> g61 is exact stop? 
    
[03:05:15] <cradek> yes 
    
[03:05:40] <cradek> btw, there's a pinout printed on the encoder 
    
[03:05:51] <jmkasunich> thats helpfull 
    
[03:06:12] <jmkasunich> is hooking that up the next step? 
    
[03:06:31] <cradek> maybe... 
    
[03:06:51] <cradek> crap, I don't think I have enough inputs 
    
[03:06:58] <cradek> the switches take 3 
    
[03:07:06] <cradek> I think there are only 5 
    
[03:07:17] <jmkasunich> all pos limits, all neg limits, and all homes? 
    
[03:07:24] <cradek> yes 
    
[03:07:38] <SWPadnos> got a parport? 
    
[03:07:39] <jmkasunich> you could drop the homes and home on the limts 
    
[03:07:57] <cradek> SWPadnos: I want to continue to use my laptop 
    
[03:08:03] <SWPadnos> ah 
    
[03:08:28] <jmkasunich> or combine pos and neg limits (which is a pain, cause if you hit one, the sw doesn't know which end your're at so it can't let you motor off of the limit 
    
[03:08:40] <jmkasunich> actually thats a non-issue with a sherline that has cranks 
    
[03:08:51] <cradek> crap, and I just got homing and limits to work 
    
[03:09:05] <jmkasunich> so leave homing alone 
    
[03:09:17] <jmkasunich> just hook all the limits (pos and neg) to the same parport pin 
    
[03:09:34] <jmkasunich> so you wind up with 5 inputs: 
    
[03:09:37] <jmkasunich> 1) limits (all) 
    
[03:09:39] <jmkasunich> 2) homes (all) 
    
[03:09:46] <jmkasunich> 3) spindle enc A 
    
[03:09:50] <jmkasunich> 4) spindle enc B 
    
[03:09:59] <jmkasunich> 5) spindle enc Z 
    
[03:10:37] <cradek> ok then! 
    
[14:52:22] <SWPadnos_> SWPadnos_ is now known as SWPadnos 
    
[17:37:30] <SWPadnos> I love those responses to bo^dick :) 
    
[17:37:50] <jmkasunich> he's really starting to piss me off, I should just ignore him 
    
[17:38:10] <jmkasunich> all the auto-tools in the world ain't gonna turn him into a circuit designer overnight 
    
[17:38:16] <jmkasunich> I dunno what he is thinking 
    
[17:38:17] <SWPadnos> heh - I've been thinking that myself 
    
[17:38:33] <SWPadnos> he's trying to write an eagle script to do it, I wish him luck 
    
[17:38:44] <SWPadnos> I think he doesn't realize it's a hard problem 
    
[17:51:08] <rayh> * rayh wonders why he doesn't try that on an eagle list. 
    
[17:51:31] <jmkasunich> because he is without clue 
    
[17:53:22] <jmkasunich> there are some things the human eye and mind are just plain better at 
    
[17:54:45] <rayh> assumption forced to reality is a fascinating thing to watch. 
    
[17:55:01] <SWPadnos> itr's a long process with him 
    
[17:55:06] <SWPadnos> it's 
    
[17:55:28] <rayh> some never complete the journey. 
    
[17:55:50] <SWPadnos> heh - this may be one of those cases 
    
[17:56:12] <SWPadnos> He's trying to lay out the board for his stepper driver, because he doesn't want to buy Geckos 
    
[17:56:35] <SWPadnos> one thing -> 5 things -> 100 things -> ... 
    
[17:56:54] <rayh> PMDX is showing off a stepper drive at NAMES this weekend. 
    
[17:57:18] <SWPadnos> interesting.  is it a design of Steve's, or his gecko "motherboard"? 
    
[17:57:30] <rayh> rumor has it the lowest ability is 48 volt 5-6 amp. 
    
[17:57:51] <jmkasunich> I actually thought about going to NAMES 
    
[17:57:52] <rayh> highest ability 80 volt 8 amp. 
    
[17:57:59] <jmkasunich> only 2-2.5 hours from here 
    
[17:58:06] <jmkasunich> but then I said fsck it 
    
[17:58:11] <rayh> stand alone or plug in to a 4-5 axis mobo 
    
[17:58:17] <SWPadnos> hmm - cool 
    
[17:58:22] <SWPadnos> not servo though ;) 
    
[17:58:41] <rayh> Roland was at the same gathering place NAMES is using this year. 
    
[17:58:56] <rayh> last weekend and said parking was near impossible 
    
[17:59:23] <rayh> I nearly cried about not being at names. 
    
[17:59:37] <jmkasunich> why? you miss it? 
    
[17:59:37] <SWPadnos> it sounds like there's a lot of neat stuff there 
    
[17:59:38] <rayh> That was a good time for quite a few years.  But hey... 
    
[18:00:01] <rayh> I remember your jmk's year of the HAL. 
    
[18:00:18] <rayh> A lot of stuff got worked out there. 
    
[18:00:28] <jmkasunich> mostly after the show tho 
    
[18:00:52] <rayh> And the constantly long line waiting to talk to Hassan about his home made mill. 
    
[18:00:59] <rayh> enough. 
    
[18:01:06] <rayh> * rayh goes back to halconfig. 
    
[18:07:18] <rayh> rayh is now known as rayh-away 
    
[19:56:16] <rayh-away> rayh-away is now known as rayh 
    
[20:29:01] <rayh> when I ask halcmd to show me pid.1.maxerror i get pid.1.maxerrorD pid.1.maxerrorI also. 
    
[20:29:24] <rayh> I thought there was a way round this so that I got only the info for one. 
    
[20:33:41] <jmkasunich> hmm 
    
[20:34:01] <jmkasunich> it treats any string you give it as if it ended in * 
    
[20:34:14] <jmkasunich> so foo = foo* which matches foo, food, and foobar 
    
[20:34:33] <rayh> I thought that a get or something worked around. 
    
[20:34:49] <SWPadnos> gets 
    
[20:35:24] <SWPadnos> show treats the parameter as a part of the string to match, gets will only return exact matches 
    
[20:35:53] <jmkasunich> there is gets for signals and getp for params 
    
[20:36:03] <rayh> does it return the whole "show" string. 
    
[20:36:03] <jmkasunich> is there a getpin? I don't think so 
    
[20:36:50] <jmkasunich> no, it returns only the value 
    
[20:37:03] <jmkasunich> (thats the reason for get existing, to get just the value) 
    
[20:37:42] <rayh> okay I see that.  Thanks 
    
[20:38:23] <rayh> the -s makes no difference there? 
    
[20:38:33] <SWPadnos> nope 
    
[20:38:44] <rayh> okay. 
    
[20:39:10] <SWPadnos> at least, that's what I think ;) 
    
[20:39:17] <jmkasunich> I wonder how hard it would be to change the string match "exact match unless they specify a * " 
    
[20:39:42] <SWPadnos> or add a -e option for exact matches only 
    
[20:40:01] <SWPadnos> the * thing is just a subset of the real change, which is to use regexp 
    
[20:40:15] <rayh> exact would be nice for some things. 
    
[20:40:42] <jmkasunich> I'd rather not do -e 
    
[20:41:23] <jmkasunich> because options apply to all commands passed to an instance of halcmd, and in theory at least, the decision between exact and wildcard is made on a command by command basis 
    
[20:41:41] <jmkasunich> I agree that regexp would be really nice 
    
[20:41:51] <jmkasunich> but more work than I want to tackle right now 
    
[20:41:59] <rayh> I do like the current show param 
    
[20:42:02] <rayh> or show pin 
    
[20:42:07] <rayh> and get the whole list 
    
[20:42:15] <rayh> or even show pin axis.0 
    
[20:42:25] <jmkasunich> right - I don't want to give that up 
    
[20:42:27] <rayh> We would loose a lot without that. 
    
[20:42:40] <rayh> "fishing expedition" 
    
[20:42:49] <jmkasunich> if we had regexp you would do "show pin *" 
    
[20:42:57] <jmkasunich> or show pin axis.0.* 
    
[20:43:06] <jmkasunich> or even axis.*.motor-pos-cmd 
    
[20:43:21] <SWPadnos> that last is what I'd like 
    
[20:43:30] <jmkasunich> except it probably wouldn't just be *, it could be [0-3] 
    
[20:43:32] <SWPadnos> and regexp is probably the easiest way to do it, believe it or not 
    
[20:43:58] <jmkasunich> is there a libregexp? 
    
[20:44:04] <rayh> oh that would be nice.  axis.*.motor-pos-cmd 
    
[20:44:25] <SWPadnos> yes 
    
[20:44:50] <SWPadnos> you call one function to prepare the expression, then you call another function to do the search (I think) 
    
[21:34:15] <jmkasunich> drat 
    
[21:34:25] <SWPadnos> drat? 
    
[21:34:46] <jmkasunich> I'm trying to unstall linux on a little (formerly) diskless client box 
    
[21:34:57] <jmkasunich> got hooked up a disk and cdrom drive 
    
[21:35:05] <jmkasunich> got it to boot the cd, and begin the ubuntu install 
    
[21:35:26] <jmkasunich> was looking good, then a kernel panic 
    
[21:35:40] <SWPadnos> bummer.  what kind of client box? 
    
[21:36:07] <jmkasunich> Neoware Neostation 3000 
    
[21:36:16] <jmkasunich> 233MHz CPU, 256M ram 
    
[21:37:04] <cradek> did you try memtest86? 
    
[21:37:13] <jmkasunich> good idea 
    
[21:37:31] <cradek> the only time I've seen kernel panics during install was bad ram on my desktop machine 
    
[21:39:21] <jmkasunich> duh 
    
[21:39:34] <jmkasunich> I think I must have misread the BIOS display of ram size 
    
[21:39:42] <jmkasunich> memtest says there is 29M 
    
[21:39:53] <jmkasunich> which is a weird amount... 
    
[21:40:01] <jmkasunich> it has an empty DIMM slot 
    
[21:40:08] <SWPadnos> either that or there's an error the BIOS is detecting, and assuming that's where RAM ends 
    
[21:40:14] <jmkasunich> could be 
    
[21:40:42] <jmkasunich> fasking splash screen hides the bios memory test 
    
[21:43:14] <jmkasunich> bios reports 30208K total memory 
    
[21:43:30] <jmkasunich> it has a little laptop style memory module 
    
[21:43:40] <jmkasunich> gonna stick a 128M dimm in there and see what happens 
    
[21:43:56] <SWPadnos> is video using 2.5M of system RAM? 
    
[21:44:13] <jmkasunich> that sounds familier 
    
[21:44:15] <SWPadnos> (that would be 1024x768x24bits) 
    
[21:44:26] <SWPadnos> + a little 
    
[21:44:36] <SWPadnos> then it's a 32M module 
    
[21:44:48] <SWPadnos> or it has 32M that's good ;) 
    
[21:45:22] <jmkasunich> heh, 161M now 
    
[21:46:03] <jmkasunich> bummer tho, with the DIMM installed, access to the PCI slot is blocked 
    
[21:46:13] <jmkasunich> (It has a riser board with one pci slot 
    
[21:47:01] <jmkasunich> (actually one PCI/ISA slot, it has both connectors) 
    
[21:47:32] <SWPadnos> you need a low profile dimm 
    
[21:47:40] <SWPadnos> or a no-profile dimm ;) 
    
[21:49:09] <jmkasunich> well, it detected 161M, but then the BIOS memtest failed 
    
[21:49:34] <SWPadnos> can you use only one module, or is the 32M soldered down? 
    
[21:49:41] <jmkasunich> Cyrix MediaGX CPU at 233MHz, no idea what the frontside bus is 
    
[21:49:44] <jmkasunich> it can be removed 
    
[21:49:52] <SWPadnos> try just the 128 then 
    
[21:49:59] <jmkasunich> the DIMM I tried is PC100 
    
[21:50:15] <jmkasunich> here goes 
    
[21:51:50] <jmkasunich> bios memtest passed, running memtest86 just for the heck of it 
    
[21:52:15] <jmkasunich> the shared video arch means it won't be a good RT box I don't think 
    
[21:53:55] <cradek> yay, midi cables work to extend the steppers on the lathe 
    
[21:54:23] <jmkasunich> you had some laying around? 
    
[21:54:36] <jmkasunich> or you actually went out and spent money on them? 
    
[21:54:37] <cradek> no, I bought them 
    
[21:54:40] <jmkasunich> sicko 
    
[21:54:42] <cradek> I do have some somewhere... 
    
[21:55:12] <cradek> but buying them is faster than finding them in the basement 
    
[21:55:18] <jmkasunich> actually I should shut up, I just bought the 40 to 44 pin IDE adapter so I could stick a laptop drive in this box 
    
[21:58:56] <cradek> hmm, my inches are only half as long as I'm used to 
    
[21:59:25] <jmkasunich> different screw pitch? microsteppint? 
    
[21:59:32] <jmkasunich> ing even 
    
[21:59:47] <cradek> I think it's off by a factor of 2, no big deal 
    
[22:04:52] <jmkasunich> wonder how many hours it will take to install... 
    
[22:05:13] <jmkasunich> I'm only doing the server install, so at least there won't be "fonts of the world" for three hours 
    
[22:05:23] <jmkasunich> (I hope) 
    
[22:06:21] <cradek> those are the worst part aren't they 
    
[22:06:42] <jmkasunich> yeah 
    
[22:07:08] <jmkasunich> another annoying part is how it does a bit of install, then stops and asks questions, then a bit more install, and more questions, about 5-6 times 
    
[22:07:33] <jmkasunich> I'm gonna have to try to trashpick a bigger drive 
    
[22:07:39] <jmkasunich> this ones only 800M 
    
[22:14:20] <cradek> jmkasunich: there still a bug with jerking after machine-off 
    
[22:14:49] <cradek> I hit a limit switch and it stops, and when I hit f2 for machine on, I get a big jerk and sometimes even following error 
    
[22:16:36] <jmkasunich> what mode? manual (jog into limit) or mdi/auto? 
    
[22:16:54] <cradek> mdi 
    
[22:17:10] <cradek> g0z3, poke the switch while it's moving 
    
[22:17:18] <jmkasunich> the fix I did would only affect the free mode planner 
    
[22:17:32] <jmkasunich> in mdi, its probably coming from the tp or interpolators 
    
[22:17:41] <cradek> oh hell 
    
[22:17:48] <cradek> I don't want to work on that, so forget I said anything 
    
[22:17:54] <jmkasunich> lol 
    
[22:46:46] <jmkasunich> can you think of any reason why catting a 2496 byte file would print absolutely nothing? 
    
[22:47:07] <jmkasunich> (a log file, which I would expect to be human readable) 
    
[22:47:51] <jepler> use 'od' or 'file' on it and find out if the contents are binary 
    
[22:48:57] <jmkasunich> od, file (and less) aren't available 
    
[22:49:09] <jmkasunich> I'm trying to read a log after getting an error during install 
    
[22:49:21] <jmkasunich> guess they're not installed yet 
    
[22:49:21] <jepler> oh 
    
[22:49:41] <jmkasunich> ls -l says its 2496 
    
[22:49:50] <jmkasunich> cat gives nothing 
    
[22:49:58] <jepler> use "cat -v" ? 
    
[22:50:39] <jepler> $ printf '\0\1\2\3\n' > /tmp/test; cat -v /tmp/test 
    
[22:50:39] <jepler> ^@^A^B^C 
    
[22:50:48] <jmkasunich> no -v 
    
[22:51:01] <jmkasunich> turns out the cat is part of busybox 
    
[22:51:04] <jepler> oh 
    
[22:51:49] <jmkasunich> there are three files in /target/var/log with non-zero lengths 
    
[22:51:58] <jmkasunich> I can cat one of them the other two give nothing 
    
[22:52:28] <jepler> no other ideas are coming to mind 
    
[22:52:46] <jmkasunich> cat lastlog | wc returns 0 0 2496 
    
[22:52:54] <jmkasunich> so the bytes are coming out of cat 
    
[22:53:10] <jepler> 0 0 means no lines and no words: so none of those characters are whitespace 
    
[22:53:24] <jmkasunich> and none of them are printable either 
    
[22:53:52] <jmkasunich> on top of that, the file that the error message said to read isn't even there 
    
[22:54:00] <jepler> I think the odds are it's all zeros 
    
[22:54:16] <jmkasunich> it says to read /target/var/log/bootstrap.log 
    
[22:54:20] <jmkasunich> but there isn't one 
    
[22:54:42] <jmkasunich> it failed installing initrd-tools 
    
[22:55:01] <jmkasunich> I think I'll just tell it to continue and see what happens 
    
[22:56:03] <jepler> initrd-tools sounds pretty important to getting a bootable system 
    
[22:58:32] <jmkasunich> yeah, its part of the base system 
    
[22:58:39] <jmkasunich> it won't let me go on 
    
[22:58:56] <jmkasunich> I tried to reinstall the base system, it bitches about the partially installed files 
    
[22:59:20] <jmkasunich> tried to repartition, it starts to load the partitioner, then bails 
    
[22:59:27] <jmkasunich> disk might be frotzed 
    
[22:59:37] <jmkasunich> I should get a bigger one anyway 
    
[22:59:49] <jmkasunich> I have lots of 3.5" disks, but I think this is the only 2.5 
    
[23:00:24] <jmkasunich> or not... just found a 6G one