| 01:21:29 | Sammy | Yo everyone |
| 05:02:47 | BZFlag | Russ: you around? |
| 05:06:16 | Russ | ya |
| 05:08:40 | Russ | ew...you might formatting stuff k&r -i8 before commiting? |
| 05:21:38 | BZFlag | nah, just joined some lines. |
| 05:21:59 | BZFlag | load_kernel_test segfaults trying to fill the tables. |
| 05:22:28 | BZFlag | my original version of your patch works fine. |
| 05:22:53 | BZFlag | util/test/Makefile needs to be hacked to autograb the kernel path. |
| 05:56:53 | Russ | did you play with memset? |
| 05:57:43 | Russ | it could be the buffer used in load_kernel_test is too small |
| 05:57:51 | Russ | increase it by 10 |
| 06:08:30 | BZFlag | hmm... I use --pad on the mkfs.jffs2 line so it should already be padded. |
| 06:08:50 | Russ | the buffer in load_kernel_test.c is kinda small |
| 06:10:15 | Russ | cvs update utils/test/load_kernel_test.c |
| 06:17:06 | BZFlag | still seg faults. |
| 06:22:35 | Russ | can you send me the image? |
| 06:22:37 | Russ | (DCC) |
| 06:35:11 | BZFlag | can you get it to work on an image? |
| 06:35:47 | BZFlag | http://rikers.org/tmp/root.jffs2 |
| 06:46:30 | Russ | unable to find magic |
| 06:48:11 | erikm | morning, guys |
| 06:50:51 | Russ | o, my bad |
| 06:52:52 | Russ | ok, I see what happened |
| 06:53:02 | Russ | the cramfs_memset function got replaced by memset |
| 06:53:09 | Russ | I should have named it u16_memset |
| 06:54:08 | erikm | wow, you have been busy when I was asleep |
| 06:54:20 | BZFlag | morning. |
| 06:54:33 | BZFlag | what did cramfs_memset do? |
| 06:54:50 | Russ | set everything by a u16 instead of u8 |
| 06:55:16 | Russ | actually int, sorry |
| 06:55:29 | Russ | I'll name it int_memset |
| 06:55:45 | erikm | BZFlag: wow, an ext2fs reader! |
| 06:57:50 | BZFlag | disk.c? hmm. looks like the comment is wrong. |
| 06:57:55 | Russ | try that |
| 06:58:25 | BZFlag | oh, yeah. just says ms-dos partition. ;-) |
| 06:59:00 | erikm | BZFlag: I suggested seletz to look at libe2fs. this reader is smaller, but otoh libe2fs is more flexible |
| 06:59:27 | erikm | heads for breakfast |
| 07:01:42 | mmatten_ | morning -_- |
| 07:03:15 | BZFlag | Russ: that did it. |
| 07:04:45 | BZFlag | is frustrated with automake and friends. |
| 07:11:12 | BZFlag | util/test/Makefile.am needs help. it works, but it's not right. /me needs to read up on automake etc. |
| 07:12:07 | Russ | definately |
| 07:14:04 | erikm | BZFlag: explain me what you want in a message to blob-cvs-commit and I can give some advice |
| 07:19:49 | BZFlag | the make there should override gcc and ld command to get host binaries. |
| 07:20:11 | BZFlag | the sources used to build that app are the same as sources in other directories. |
| 07:20:25 | BZFlag | it now makes symlinks to each of the sources it needs. |
| 07:20:49 | BZFlag | ideally it would use them wherever they are and not have to have the symlinks. |
| 07:21:57 | BZFlag | the maintainer mode does not like the variables: load_kernel_test_OBJECTS load_kernel_test_SOURCES EXTRA_load_kernel_test_SOURCES |
| 07:22:38 | BZFlag | the two sources it thinks are unused, and the objects it says should not be defined. |
| 07:31:42 | erikm | Russ: there already is a memset in src/lib/memset.c |
| 07:32:20 | erikm | oh wait, this is int_memset |
| 07:33:21 | erikm | goes to work |
| 09:03:34 | seletz | morning |
| 12:01:21 | seletz | erikm: hi |
| 12:19:55 | | que tal, erikm |
| 12:19:55 | erikm | hi |
| 15:01:49 | | salut, seletz |
| 15:01:49 | seletz | prpplague: hi |
| 15:02:23 | prpplague | seletz: morning |
| 15:02:49 | prpplague | seletz: you use docbook? |
| 15:04:19 | seletz | prpplague: no, not yet. It's one of the things i want to have a look at. |
| 15:04:39 | seletz | prpplague: i use TeX tho. |
| 15:05:11 | prpplague | seletz: i need to find something to help collect document fixes/howto's |
| 18:26:52 | | here is a pic, the silk screening isnt perfect, it is more of a cream than white, but it was just a test http://www.tuxboxproject.com/images/Jan16_01.JPG |
| 18:26:52 | seletz | erikm: still here? |
| 18:27:45 | seletz | hmmm, guess not. |
| 18:28:13 | seletz | well, bye folks. Happy weekend! |
| 19:22:44 | BZFlag | we should extend the fs support so we have --enable-ext2 --enable-vfat (perhaps just fat is enough) |
| 19:23:07 | BZFlag | read from ide an read from flash should both be able to use the same fs drivers. |
| 19:24:41 | Russ | right |
| 19:25:06 | Russ | I'm thinking we should move towards a model more like grub, but not use grub as a model because it does a lot of things wrong |
| 19:26:54 | BZFlag | agreed. (on both points ;-) |
| 19:27:24 | BZFlag | why does lxrbot quit and rejoin from time to time? |
| 19:27:33 | BZFlag | log cycleing? |
| 19:27:37 | Russ | we should really lay out how we want to do it |
| 19:27:48 | Russ | log cycling? wha? |
| 19:27:58 | BZFlag | Russ: lxrbot |
| 19:28:09 | BZFlag | lxrbot: status |
| 19:28:09 | lxrbot | Since Fri Apr 26 21:30:12 2002, there have been 0 modifications and 0 questions. I have been awake for 1 minute, 8 seconds this session, and currently reference 6733 factoids. Addressing is in require mode. |
| 19:28:29 | | well, lxrbot is my fellow bot. he knows a lot about the linux kernel and normally lives on #kernelnewbies. |
| 19:28:29 | BZFlag | ibot: lxrbot? |
| 19:29:32 | Russ | BZFlag: erikm has lxrbot restart every now and then because it sometimes can't tell when it is disconnected |
| 19:34:19 | BZFlag | ah. happens with ibot from time to time too, but not often so we restart it by hand. |
| 19:34:58 | BZFlag | would be nice to have the infobot ping chanserv or some service from time to time and restart if it does not get a reply. |
| 20:02:58 | | hi, seletz |
| 20:02:58 | seletz | hi |
| 20:05:26 | prpplague | howdy seletz |
| 20:05:34 | prpplague | whats up? |
| 20:05:47 | seletz | :) |
| 20:08:19 | BZFlag | seletz: you saw the ext2 code I added from brad/duck ? |
| 20:08:38 | seletz | BZFlag: yup |
| 20:09:08 | BZFlag | what are your plans? you are going to put a tarball in flash? |
| 20:09:13 | BZFlag | or on a raw cf? |
| 20:09:24 | seletz | BZFlag: i'll try that code when i verified that i read from the CF card is correct |
| 20:10:05 | BZFlag | the board I'm on wants kernel from jffs2 and reflash from fat cf ide. |
| 20:10:09 | seletz | BZFlag: first I'll put a tar on the CF ("raw", no partitions) |
| 20:10:30 | seletz | BZFlag: then I'll move to FSystem code (FAT, ext2) |
| 20:10:46 | BZFlag | duck is now using that ext2 code to reflash his board. |
| 20:11:30 | seletz | BZFlag: I want a easy method for updating the complete OS of my board (easy for customers) |
| 20:11:48 | BZFlag | a file on fat cf would work? |
| 20:11:50 | seletz | BZFlag: First step is raw tar on a CF card. |
| 20:12:32 | seletz | BZFlag: yup, that's what i want. a file on a FAT FS (probably a TAR archive of blob, zImage, initrd.gz and cramfs) |
| 20:12:49 | seletz | BZFlag: final version, that is. |
| 20:13:08 | BZFlag | more unit testing is always good, so read from tar might be nice. this board just wants the two things though. kernel in jffs2 in flash and reflash rootfs from a file on fat cf |
| 20:13:46 | BZFlag | I just want a file called "rootfs" or similar and other for "romimage" that would also include a new blob. |
| 20:14:07 | BZFlag | a direct memory dump of all flash, or just the rootfs partition. |
| 20:14:15 | seletz | BZFlag: Have some FAT code? My code is 400kB (yuck!) |
| 20:15:28 | seletz | BZFlag: What about having the whole bunch in one tar arch? Would be a nice interface... |
| 20:16:10 | seletz | BZFlag: note that the tar code is block-aware, that is it does not rely on flat mem access. |
| 20:16:43 | BZFlag | no small vfat code yet. though bootldr include read and write vfat code. might borrow from there. |
| 20:17:02 | BZFlag | seletz: my users won't even know what tar is. |
| 20:17:08 | seletz | BZFlag: plain FAT 8.3 would do fone too. |
| 20:17:09 | BZFlag | in most cases anyway. |
| 20:17:30 | BZFlag | yeah, 8.3 would be fine with me too. |
| 20:17:46 | BZFlag | and not have to worry about the microsoft vfat patent. |
| 20:17:47 | seletz | BZFlag: My users for sure dont know even what an archive is. I'll provide the archive images. |
| 20:18:05 | BZFlag | good point |
| 20:18:41 | seletz | BZFlag: Note that all this is just thought as "here you have a file. Put it on your CF card. Plug it in. Power-on. wait. Done." |
| 20:19:05 | BZFlag | I'd add "hold down foo. and power on" |
| 20:19:27 | seletz | BZFlag: And that "put it on CF" is just drag'n drop on a laptop |
| 20:19:38 | BZFlag | right |
| 20:19:46 | seletz | BzFlag: yup, maybe. But maybe the archive is deleted on CF. |
| 20:20:14 | seletz | BZFlag: Our devices have CF for data storage (FAT FS) |
| 20:20:35 | seletz | BZFlag: so they could just stay where they are ... |
| 20:21:10 | prpplague | seletz: a word of caution, i've had problem with initrd |
| 20:21:26 | prpplague | seletz: and rootfs images coming from fat 8.3 cf |
| 20:21:30 | seletz | prpplague: what problems? |
| 20:22:10 | seletz | prpplague: my layout is: on-board-flash( blob, initrd, cramfs) CF( data ) |
| 20:22:28 | seletz | prpplague: so the update would be CF => on-board flash |
| 20:22:53 | prpplague | seletz: i've been using the flash utility from inhand electronics which reads from fat 8.3 formated cf cards |
| 20:23:16 | seletz | prpplague: opensource? |
| 20:23:48 | prpplague | seletz: not all of it |
| 20:24:05 | seletz | prpplague: the FAT code? |
| 20:24:07 | seletz | :) |
| 20:24:09 | prpplague | seletz: ya |
| 20:24:31 | seletz | Hmmm, can you put it on sf? |
| 20:25:06 | prpplague | i can check about it |
| 20:25:26 | seletz | BZFlag: Ok, so let us summarize: |
| 20:25:43 | seletz | BzFlag: we both want some sort of update CF => internal flash |
| 20:26:05 | seletz | BzFlag: we both want to keep it easy for customers (fool-proof) |
| 20:26:42 | Russ|werk | seletz: full cramfs code is smaller than tar code |
| 20:27:01 | Russ|werk | if someone wants small fat code, I'll make it for $$$ :) |
| 20:27:29 | seletz | well, but i dont have cramfs on my CF card |
| 20:27:44 | Russ|werk | seletz: ? |
| 20:28:30 | seletz | I have a file on CF card (FAT) which contains an system update (blob, initrd, kernel, cramfsimage) |
| 20:28:55 | Russ|werk | what is a system update? |
| 20:29:01 | Russ|werk | oh, I see |
| 20:29:07 | seletz | ATM i just want to leave away FAT and put a tar on the CF (raw) |
| 20:29:13 | Russ|werk | the CF card is fat so it can be written by a win machine |
| 20:29:18 | Russ|werk | then you put a tar on there with everything in it |
| 20:29:24 | seletz | yeah. Now you got it. |
| 20:29:35 | Russ|werk | I'm saying, why not put everything in a cramfs instead of a tar |
| 20:29:46 | seletz | win machine = customers laptop |
| 20:29:48 | Russ|werk | or, if you really wanted simplicity, a table |
| 20:29:59 | Russ|werk | ie: |
| 20:30:22 | Russ|werk | struct dir_entry { char filename[20]; long size; long offset; } |
| 20:30:24 | seletz | yeah, i know. But tar is simple |
| 20:30:42 | Russ|werk | struct root { long num_entries; } |
| 20:30:47 | seletz | (ok, it got some weird octal BCD stuff) |
| 20:30:55 | Russ|werk | root, then dir_entries, then files |
| 20:31:01 | Russ|werk | much simplier |
| 20:31:05 | seletz | yeah, would work. |
| 20:31:34 | seletz | but now i can do a "tar cvf /dev/hda blob initrd cramfs.image" |
| 20:32:27 | seletz | simpler in terms of: smaller header, easier to decode. |
| 20:32:53 | seletz | not simpler in terms of: portable, re-implementing the wheel :) |
| 20:33:04 | Russ|werk | right, thats why I suggested cramfs |
| 20:33:21 | seletz | (You'd have to write an archiver etc.) |
| 20:33:30 | Russ|werk | cramfs is actually pretty similar to what I described, but with block lists |
| 20:33:30 | seletz | ok, that apporach is ok |
| 20:33:48 | seletz | you could do mkcramfs ... |
| 20:33:50 | seletz | hmmm |
| 20:34:09 | Russ|werk | that would compress things a bit more, I don't think it would give you a crc tohugh |
| 20:34:11 | Russ|werk | er, though |
| 20:34:17 | seletz | well, ok. |
| 20:34:25 | Russ|werk | you probably want to do a crc or md5sum if you are including blob |
| 20:34:26 | prpplague | i like the tar idea |
| 20:34:53 | seletz | tar is useful anyways IMHO |
| 20:35:14 | Russ|werk | but the code is so big... |
| 20:35:49 | seletz | just do a xmodem download of an archive and flash every single file to different partitions |
| 20:36:32 | seletz | or even: have filenames match partition names |
| 20:37:00 | seletz | well, the tar code isnt written with code size in mind |
| 20:37:11 | seletz | erm, wasnt |
| 20:39:51 | BZFlag | reads |
| 20:42:29 | BZFlag | seletz: Russ has a point though the cramfs code in in there and debugged. |
| 20:42:43 | BZFlag | so a cramfs on cf would be easier to get to as a "first step" |
| 20:43:18 | Russ|werk | BZFlag: actually its not |
| 20:43:26 | Russ|werk | the current cramfs.c is very incomplete |
| 20:43:30 | BZFlag | I'm happy with partitions having names mapped in blob someplace, and then blob looks for those names on fat cf. |
| 20:43:34 | Russ|werk | but I have some here that I wrote for grub |
| 20:43:41 | BZFlag | that's what I want long term. no tar code. |
| 20:44:06 | BZFlag | Russ: I though you were using the cramfs code on aboard there? |
| 20:44:14 | Russ|werk | right, but it only loads /linux |
| 20:44:59 | BZFlag | ah. true. |
| 20:45:35 | BZFlag | well the reflash from cf would be files in the root too. |
| 20:46:26 | BZFlag | so /<partitionname> where the name is hopefully 8.3 or less. |
| 20:47:05 | BZFlag | blob,kernel,ramdisk params would all be fine. I'd like a "romimage" that is all of flash too. |
| 20:47:29 | Russ|werk | well, you'd want to flash things like blob in one peice asap |
| 20:47:41 | Russ|werk | not erase everything, then start flashing blob |
| 20:47:48 | BZFlag | agreed. |
| 20:48:06 | prpplague | not to be a pest, but have you guys actually tried storing initrd and rootfs images on fat 8.3 before? |
| 20:48:14 | BZFlag | I'd like that to happen automagically for "romimage". |
| 20:48:39 | BZFlag | prpplague: yes on the zaurus, bt that uses angel monitor, not blob (yet) |
| 20:50:01 | prpplague | BZFlag: hmm, i've done a couple of test where i transfered an initrd from ext2 to a fat8.3 then back to ext2, the resulting initrd was unusuable |
| 20:50:40 | Russ|werk | prpplague: I would guess something was wrong with the implementation |
| 20:51:03 | Russ|werk | ok, cramfs booting on doc2000 x86: check |
| 20:51:14 | prpplague | Russ|werk: implementation of what? the initrd? |
| 20:51:29 | Russ|werk | now I just have to figure out how to store config stuff on the doc200 |
| 20:51:32 | Russ|werk | er, 2000 |
| 20:51:41 | Russ|werk | prpplague: fat reader/writer |
| 20:54:12 | prpplague | Russ|werk: this was from one HD to another HD and back |
| 20:54:16 | prpplague | Russ|werk: http://www.abcsinc.com/yopy/tcsx1-rootfs.tar.gz |
| 20:54:42 | prpplague | Russ|werk: your welcome to look at the tcsx-1 rootfs for an example on how i handel configs |
| 20:56:10 | Russ|werk | did you check your kern.log to see if there were any IO errors or DMA problems? |
| 20:57:24 | Russ|werk | uncormpresses fine for me |
| 20:58:04 | Russ|werk | thats a big root |
| 20:58:32 | BZFlag | prpplague: sounds like you have bugs someplace. I've done the same hundreds of times. |
| 20:59:52 | Russ|werk | I work with an image that is 1.3M compressed including kernel |
| 21:03:54 | prpplague | BZFlag: ya thats what i thought but i never could trace it down |
| 21:04:16 | prpplague | Russ|werk: thats the rootfs for our little thin client |
| 21:04:54 | Russ|werk | I guess X really weighs in |
| 21:05:18 | Russ|werk | is it a ro fs? |
| 21:05:28 | prpplague | Russ|werk: ya something like 3mb for the xserver |
| 21:05:35 | prpplague | Russ|werk: ya totaly ro |
| 21:05:59 | prpplague | Russ|werk: except for when saving configs |
| 21:06:02 | Russ|werk | did you know that bb init has a mechanism for chrooting once booted an running? |
| 21:06:26 | Russ|werk | you can signal init, chroot to a ramfs, umount the rootfs, then flash it |
| 21:07:43 | prpplague | Russ|werk: that fs was done about two years ago and was my first attempt at an embedded system |
| 21:08:07 | Russ|werk | ah, well embedded stuff has come a long way |
| 21:08:19 | prpplague | Russ|werk: yes it has |
| 21:08:29 | prpplague | Russ|werk: and so has my education |
| 21:08:55 | Russ|werk | I also have an mkcramfs that works with the device table that mkfs.jffs2 uses, but it has a couple bugs I need to work out (non-fatal) |
| 21:09:23 | prpplague | Russ|werk: http://www.linuxdevices.com/articles/AT3193512578.html |
| 21:09:38 | Russ|werk | ya, I saw that |
| 21:10:04 | Russ|werk | be pretty usefull for MLS terminals (realestate thing) |
| 21:10:12 | prpplague | Russ|werk: lol i did get a good plug for it "Anyone trying to build their own embedded Linux device would do well to study how Advantage put the TCSX-1's software together" |
| 21:10:53 | Russ|werk | the one thing I would say is its probably a waste if ram=flash |
| 21:11:10 | Russ|werk | a ratio of 4 to 1 or 2 to 1 is probably better |
| 21:14:03 | BZFlag | Russ: it's just a DOM though, you could replace it with anything you want. |
| 21:14:05 | prpplague | Russ|werk: yes very wasteful, i've gotten a newer version on 2.4 kernel and using all bb and buildroot |
| 21:14:17 | prpplague | Russ|werk: yes including DOC |
| 21:15:26 | Russ|werk | prpplague: any good ideas on saving configurations to a DOC? |
| 21:15:45 | Russ|werk | (ie, revision stampted so you can use the most recent one that has a good crc) |
| 21:17:55 | prpplague | Russ|werk: are you talking stuff like ipaddress,passwords,iptables rules, that kind of stuff? |
| 21:18:12 | Russ|werk | and dhcp leases (saved every 2 - 3 hours) |
| 21:18:26 | Russ|werk | doing it on NOR flash is easy |
| 21:20:19 | prpplague | Russ|werk: well, what i like to do is use a small partition that i store the configs in a .conf file. when things change, the data is writen to a file in temp, the partion is re-mounted rw the file is copies, and then remounted ro |
| 21:20:37 | Russ|werk | what fs? |
| 21:21:00 | prpplague | Russ|werk: i've used both jffs and ext2 |
| 21:21:23 | Russ|werk | on NAND flash? |
| 21:24:06 | prpplague | i assume you are refering to using it on DOC, ya it works fine |
| 21:25:41 | prpplague | i've used the same tcsx-1 rootfs with DOC simply subsituting the /dev/hda with /dev/nftla and a modified lilo |
| 21:30:55 | Russ|werk | hmm...I have trouble trusting that |
| 21:32:22 | prpplague | Russ|werk: why? |
| 21:32:53 | Russ|werk | because a lot of gc and wear leveling goes on |
| 21:33:26 | Russ|werk | what if some sector is getting erased that is very important for the fs, and power is lost |
| 21:36:02 | prpplague | thats just it, the only section that is at risk is the /configs , nothing in the os |
| 21:38:11 | prpplague | Russ|werk: we have around 2500 units out since november of 2001 using the DOC2000 on this fs with less than a .0002% failure rate |
| 21:39:56 | prpplague | Russ|werk: my bad .0004% |
| 21:40:09 | Russ|werk | right, but I plan on writing the config every 2-3 hours |
| 21:41:01 | prpplague | Russ|werk: ya that would present a considerable more difficult problem |
| 21:41:47 | prpplague | Russ|werk: what kind of memory will you have on the x86 board? |
| 21:42:58 | prpplague | erikm: all hale the arrival of mr.blob |
| 21:43:09 | erikm | heh |
| 21:43:11 | erikm | bows |
| 21:43:48 | Russ|werk | prpplague: doc2000 |
| 21:44:20 | prpplague | Russ|werk: what about ram? |
| 21:44:43 | Russ|werk | just 72pin |
| 21:45:13 | prpplague | 16mb? |
| 21:45:44 | Russ|werk | 8M is enough |
| 21:46:27 | Russ|werk | getting mobo, power supply, CPU, and 16M ram for $25, then putting it is a custom cube case |
| 21:46:50 | prpplague | Russ|werk: cool |
| 21:46:55 | Russ|werk | add a couple nics, a 2M doc on an ISA card, and its set |
| 21:47:54 | prpplague | Russ|werk: both nics 10/100? |
| 21:48:43 | Russ|werk | yup |
| 21:48:49 | Russ|werk | RTL8139 |
| 21:49:15 | Russ|werk | the SA1100 design is much smaller and more reliable, but the CS8900A's are only 10Mbit |
| 21:49:29 | Russ|werk | with the x86 version, we get to put in other things besides nic cards though |
| 21:49:33 | prpplague | Russ|werk: i could send you tcsx-1 board, but you'd only have one 10/100 and one 10 |
| 21:49:42 | Russ|werk | (56k, a usb card for a 3com ISDN modem, etc) |
| 21:50:43 | Russ|werk | I'd really like to move everything over to the embedded arm due to reliability problems |
| 21:50:53 | prpplague | nods |
| 21:51:17 | prpplague | i know the "reliability problem" all too well |
| 21:51:36 | Russ|werk | altough a custom power supply/cmos battery combo may be able to solve that |
| 21:51:42 | Russ|werk | but would add considerable cost |
| 21:52:53 | prpplague | which mobo? |
| 21:53:30 | Russ|werk | some P120 ast thing |
| 21:53:52 | prpplague | Russ|werk: btw, you still want to play with that camion unit? i still have not been able to get any source, so your welcome to play with it |
| 21:54:01 | Russ|werk | course |
| 21:54:20 | Russ|werk | it may not end up being that difficult to RE |
| 21:54:39 | prpplague | Russ|werk: ok then, sometime next week, i'll ship it and a tcsx-1 board |
| 21:54:46 | prpplague | Russ|werk: want anything else/ |
| 21:54:47 | prpplague | ? |
| 21:55:11 | Russ|werk | if you have any devel docs at all to go along with the camion |
| 21:55:56 | Russ|werk | I might be able to get the tcsx reselling as a mls terminal (telnet terminal basically) |
| 21:56:06 | prpplague | Russ|werk: thats the deal, not a darn thing, i can't even get a return email |
| 21:56:38 | Russ|werk | not much you could do short of flying out to korea I suppose |
| 21:56:50 | Russ|werk | or trying to call the developers at their home |
| 21:57:55 | prpplague | lol, well, i've ftp'd to their server and left a ton of messages, sent about 1000 faxes, and flooded their email server, so guess the next is calling them at home |
| 21:58:14 | prpplague | its a real shame too, its a cute little unit for the price |
| 21:58:53 | prpplague | i wanted them to make a dev board without the case |
| 21:59:17 | Russ|werk | oh, my mailing address is changing in 2 weeks |
| 22:00:08 | prpplague | Russ|werk: i;ve got a bunch of arm+net toys too |
| 22:00:22 | Russ|werk | probably would want to mail it to 4121 E Vista Dr; Phoenix, AZ 85032 |
| 22:00:52 | prpplague | Russ|werk: ok noted |
| 22:01:07 | prpplague | moving to az? |
| 22:01:26 | Russ|werk | I'm in AZ |
| 22:01:36 | Russ|werk | I'm graduating and they are kicking me out of the dorm |
| 22:01:49 | prpplague | Russ|werk: ohh, for some reason i thought you were chicago |
| 22:08:21 | prpplague | argh, server is down in hawaii, guess i need to go and fix it |
| 22:09:17 | erikm | prpplague: lucky guy! |
| 22:10:24 | prpplague | erikm: not really, i don't like hawaii, my area is the bahamas |
| 22:11:34 | Russ|werk | they need that remote robot arms thing for techies like the have for surgeons |
| 22:12:46 | erikm | Russ|werk: a remote reset button is quite easy to build |
| 22:13:55 | Russ|werk | right, but that doesn't fix a crashed hd |
| 22:17:41 | prpplague | Russ|werk: sssssssshhhhhhhh, i'd never get to go anywhere |
| 22:17:56 | Russ|werk | is it on the big island? |
| 22:20:51 | prpplague | Russ|werk: honolulu |
| 22:21:00 | Russ|werk | bummer |
| 22:21:39 | prpplague | Russ|werk: doesn't matter they're back up, looks like a seagate dat went bad and was shorting out the scsi bus |
| 22:22:20 | Russ|werk | ouch |
| 22:23:05 | prpplague | ohh well, guess i'l head to beer store instead |
| 22:23:13 | prpplague | bbl |
