**** BEGIN LOGGING AT Tue Aug 02 23:59:56 2005 Aug 03 06:17:49 build-optware-nslu2: mysql package fails to configure Aug 03 06:18:09 checking for correct ltmain.sh version... no Aug 03 06:18:23 *** libtool.m4 and ltmain.sh have a version mismatch! *** Aug 03 13:40:39 ehrm, for brevitys sake. what should /initrd/etc/fstab look like? Aug 03 14:08:15 becreuz: #/dev/ram0 / ext2 defaults 1 1 Aug 03 15:06:00 blah Aug 03 15:06:07 back Ivanmarcus Aug 03 15:06:18 ? Aug 03 15:08:36 rwhitby: roger. Aug 03 15:10:26 If you're unslung to an external disk in 5.5, then jut edit /etc/fstab cause / is on the external disk Aug 03 15:10:52 hmm but the changes does not stick between reboots Aug 03 15:16:30 i just received the used slug i bought off of ebay. all it came with was the slug and the power cable. i hooked it up to my LAN and powered it up, got a beep after about a minute and now have solid green ready lights. but i can't find it on my network. Aug 03 15:16:49 ping the subnet Aug 03 15:16:56 192.168.1.177, eh? i even tried resetting it. Aug 03 15:17:08 192.168.1.77 Aug 03 15:17:08 becreuz: I'm back - m$ problem! - rwhitby should be able to help you much better than I but I'd have thought that one I mentioned should do it? Aug 03 15:17:20 77, argh Aug 03 15:17:42 well we'll know in about a minute or less Aug 03 15:17:47 cool Aug 03 15:18:06 why do people buy NAV ?! Aug 03 15:18:41 geojeff|out, if you follow the directions to Reset the SysConf, you will set it back to 192.168.1.77 Aug 03 15:18:52 without affecting anything else Aug 03 15:19:08 argh Aug 03 15:19:14 * becreuz banks head against wall Aug 03 15:19:24 those directions on nslu2-linux.org? Aug 03 15:19:30 yes Aug 03 15:19:37 uh-oh Aug 03 15:19:39 ok. Aug 03 15:20:07 becreuz: no-carrier?? Aug 03 15:20:21 roger captain. i'm going in low Aug 03 15:20:25 glargh Aug 03 15:20:36 im about to regress into some primordeal ooze or something Aug 03 15:20:37 minties Aug 03 15:20:55 so last resort is to edit the files in /usr/local ? Aug 03 15:21:00 hmmm, well [damage-control mode] all is not lost methink Aug 03 15:21:18 geojeff|out, http://www.nslu2-linux.org/wiki/HowTo/ResetSysConf Aug 03 15:21:20 have you another linux box? Aug 03 15:21:27 oh yes. several Aug 03 15:21:54 cool - guess if it were me I'd mount that usb hdd on one of them & return the fstab file back to 'normal' Aug 03 15:21:59 ByronT, thanks. Aug 03 15:22:11 np... good luck Aug 03 15:22:16 Ivanmarcus: huh? Aug 03 15:22:20 then hopefull you'll be back to square one Aug 03 15:22:36 no the machine boots and everything but it's just like i didnt unsling it O_o Aug 03 15:22:52 oh Aug 03 15:23:24 this is just from changing /share/hdd/etc/fstab right? Aug 03 15:23:49 nah it was first /initrd/etc then /etc then /share/hdd/etc now share/hdd/conf Aug 03 15:23:58 oh Aug 03 15:24:01 and im contemplating /usr/local Aug 03 15:24:09 wow Aug 03 15:25:41 now lets see how much i shot my foot. Aug 03 15:25:47 so the final blow so to speak was share/hdd/conf Aug 03 15:25:54 yeah Aug 03 15:26:20 hmmm, well I don't have an fstab in there Aug 03 15:26:33 but Aug 03 15:26:38 i should probably tell what i'm trying to do here Aug 03 15:26:43 if I was to fix it Aug 03 15:26:49 i've moved /opt to another hdd Aug 03 15:26:57 I think I'd remove the hdd from the slug Aug 03 15:27:03 mount it to another machine Aug 03 15:27:10 and remove the offending file Aug 03 15:27:18 then re-install Aug 03 15:27:26 back the slug Aug 03 15:27:42 I mean put the drive back on the slug :-) Aug 03 15:27:50 then it should go again? Aug 03 15:28:05 oh, opt to another drive altogether? Aug 03 15:28:07 that' Aug 03 15:28:11 s interesting Aug 03 15:28:11 yeah Aug 03 15:31:34 hmmm, the world seems full of m$ users with virus problems today... so you've got 2 x hdd on the slug, opt on the 2nd - now I'm a bit slow (and interested), what's the reasoning here? Aug 03 15:35:27 room. and inadequate planning mostly Aug 03 15:42:06 oh, fair 'nuff :-) Aug 03 15:44:47 i'm on my local linux server, on which there is a cheap little hub. was hoping i could do the telnet catch from the server. so, when it says there is a 2 sec window, that's when doing hard reboot of slug, right? Aug 03 15:45:25 when it first starts Aug 03 15:46:06 ok, will try again :) (doing arping...) Aug 03 15:48:38 guess it has to work once before you'll believe it. so i do arping... first, then turn the slug on, then ctrl-c quickly? Aug 03 15:48:55 ehrm since coreutils and busybox conflict. is it "safe" to force overwrite when installing unslung-devel ? Aug 03 15:51:12 becreuz: sorry not a q I can answer - anyway I've done enuff damage today already! Aug 03 15:51:17 geojeff|reset. to be honest, I've never had success with the arping... I usually setup a telnet session ready to go. hit the power on on the slug, hit the enter to start the telnet session and whiz bang, the Ctrl-C prompt comes up Aug 03 15:51:36 Ivanmarcus: haha nah you have'nt. i did tha tmyself :) Aug 03 15:51:48 :-) Aug 03 15:53:48 ByronT, yeah, it never picks it up. Aug 03 15:54:14 what kind of hub / switch? Aug 03 15:54:33 and is your server doing auto-negotiation? Aug 03 15:55:18 it is a little sohoware hub. hmmm.. not sure about auto-negotiation. i know it is not running dhcp, if that is a must. Aug 03 15:56:28 on my wife's iMac, the only way to catch the redboot window was by forcibly setting the iMac to run the NIC at full duplex and 100BaseT (instead of detecting speed/duplex) Aug 03 15:57:16 well maybe i can try with a cross-over cable direct to my gentoo laptop Aug 03 15:57:23 geojeff|reset, you're working from these directions - http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot? Aug 03 15:57:31 ByronT, yes Aug 03 15:58:02 and the arp on that comp has the -f ability? Aug 03 15:59:37 hmmm, maybe not. it is redhat 7.3 on the one i am on. Aug 03 16:00:34 geojeff|reset: fwiw I set up a ping in one session (on my linux box) and had the telnet set to go in another so when the slug came on line I was straight into it.. Aug 03 16:01:35 both sessions open in a separate putty window on winbox :-} Aug 03 16:01:51 what is it that you see when the telnet window is hit? you get a prompt message? Aug 03 16:02:23 yes, and a statement stating how long until boot Aug 03 16:02:49 with Windows, I usually see 1.60 secs... with iMac, 1.20 secs Aug 03 16:03:23 course, I just put serial access on one of my slugs... which means I see 2.00 secs in terminal Aug 03 16:09:15 should i be able to ping the slug? (at either 192.168.1.77 or 192.168.0.1), which i can't. says unreachable. Aug 03 16:09:46 uh... the silly question at this point would be: what is the IP of the computer you're using to ping from Aug 03 16:10:24 in other words, can your computer even see the 192.168.0.xxx subnet? Aug 03 16:11:08 well i ain't no network guy really :) i just added ALL 192.169.0. to hosts.allow. something else to do? Aug 03 16:14:04 ok, this is a linux box? Aug 03 16:14:28 if so, go ahead and setup an ethernet alias with Aug 03 16:14:30 ifconfig eth0:1 inet 192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0 Aug 03 16:16:30 hmmm... looks like he just changed his ip.... Aug 03 16:16:56 oops :-) Aug 03 16:20:01 so, i probably have a basic network setup problem Aug 03 16:21:07 did you catch my post about ethernet alias? Aug 03 16:21:27 no, sorry, blew myself away. Aug 03 16:21:40 [18:09] ok, this is a linux box? Aug 03 16:21:40 [18:09] if so, go ahead and setup an ethernet alias with Aug 03 16:21:40 [18:09] ifconfig eth0:1 inet 192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0 Aug 03 16:21:40 [ Aug 03 16:22:45 that will setup an alias for your nic, after doing that, you should be able to "ping 192.168.0.2" and see some response Aug 03 16:23:20 yeah, getting response there. why isn't is 192.168.0.2? Aug 03 16:23:24 i mean 0.1 Aug 03 16:23:34 good deal Aug 03 16:23:41 that response is the server's nic... Aug 03 16:23:52 the 192.168.0.1 will only be alive for 2 secs Aug 03 16:23:59 ah, ok Aug 03 16:24:24 now try to telnet in... :) Aug 03 16:24:44 so, i really don't need to do the reset, now that i see i had a more basic problem. but i guess telneting in is a basic first step to learn :) Aug 03 16:26:06 the reset *sets* the permanent IP of the slug to a known IP - specifically the 192.168.1.77 address Aug 03 16:26:44 since you don't know the currect setting, you need to use the Reset of SysConf via the Redboot to set the slug to that address Aug 03 16:27:07 redboot is ALWAYS at 192.168.0.1 Aug 03 16:27:31 ok, gotcha. just getting it configured. Aug 03 16:27:46 but Yes, telnetting into RedBoot is a very basic, but needed step to learn... Aug 03 16:28:30 man arping gives me nothing about a -f param, so will step elsewhere. Aug 03 16:28:55 try to do it by timing... (which is how I have done it many many many times) Aug 03 16:29:28 setup a shell window with prompt$ telnet 192.168.0.1:9000 Aug 03 16:29:50 unplug the slug, plug the slug back in (sitting at no power...) Aug 03 16:30:09 press power button, and immediately press enter in that shell window Aug 03 16:30:34 btw, would telnet 192.168.0.1 9000 (with a blank instead of a colon) work? -- i copied that from the help page. Aug 03 16:30:35 watch the shell window for the "catching" (and you should have fingers over Control - C) Aug 03 16:31:09 depends on your OS... telnet 192.168.0.1 9000 is the correct way in windows XP Aug 03 16:31:28 telnet 192.168.0.1:9000 is how OS X needs it... Aug 03 16:31:53 it was that way under the Red Hat Linux example section Aug 03 16:32:10 but it looks like someone just copied their session, so probably ok Aug 03 16:32:51 I can only speak to XP and OS X... :) Aug 03 16:34:53 telnet 192.168.0.1:9000 gives me unknown host message Aug 03 16:35:15 oh, its the colon :) Aug 03 16:35:37 never question the docs Aug 03 16:36:29 I didn't write those docs... ;) Aug 03 16:38:29 telnet gives me "Unable to connect to remote host: Connection refused" and then pops off to a prompt, so it isn't "waiting" Aug 03 16:38:58 k, so wait a sec on hitting enter... :) Aug 03 16:39:24 i did it about 8 times before i got a nibble, but i was too slow to hit ctrl c i guess Aug 03 16:39:29 hehe Aug 03 16:39:47 it's like riding a bike... that first time is the hardest... Aug 03 16:39:57 after that, you know exactly how to do it... Aug 03 16:41:10 well, i missed it a bunch of times that go-round, and never got a nibble... Aug 03 16:43:51 you could try installing an arp that has the -f Aug 03 16:44:04 i was imagining things on the "nibble" i think. yes, will try updating arp Aug 03 16:44:46 today: the arp update... tomorrow: adding a serial port... :) Aug 03 16:45:37 yep, there will be no lapse in the fun Aug 03 16:54:36 i tried it on my gentoo laptop, which has arping with -f -- it said it received 1 response, but i guess i wasn't quick enough? man, that's quick. Aug 03 16:55:02 wow this is like using linux in 93 all over again. shooting from the hip. taking no prisoners, use of linux Aug 03 16:56:49 that's so quick that i think you'd have to guess at when it will come Aug 03 16:59:34 hah -- emerge telnet Aug 03 17:00:19 hmm.. Aug 03 17:00:52 yeah, that telnet window is short... with OS X, it's near impossible unless you use a cross-over cable or cut off the auto negotiation Aug 03 17:18:01 i guess i'll go get a crossover cable to try that route. seems too fast. Aug 03 17:18:33 I've got to head home... good luck in the meantime Aug 03 17:18:41 thx Aug 03 19:36:37 i have my gentoo laptop hooked up to the slug with a crossover cable now. i did the ifconfig cmd, and i can ping 192.168.0.2, but the arping/telnet cmd gets no response now. something special for crossover conn.? Aug 03 19:37:56 not at all Aug 03 19:38:21 with a crossover cable telnet 192.168.0.1 at port 9000 should immediately pop Aug 03 19:38:38 hmmm.. Aug 03 19:38:50 with crossover, I doubt you even need to arp... Aug 03 19:39:34 but i still need to restart the slug on a hard boot, eh? (and still catch it with ctrl c) Aug 03 19:39:42 yes Aug 03 19:40:03 redboot is *only* available on the first two seconds or so of powering up Aug 03 19:45:01 btw, nice wiki page (which is why I'm trying to get you up and running... :) ) Aug 03 19:45:12 hehe Aug 03 19:47:40 there is a lag of more than 10 seconds before telnet even says 'Trying 192.168.0.1...', so don't know if that is a problem. i'm getting nothing when i hit the own button, and then hit the telnet cmd. what do you see when it "catches"? Aug 03 19:47:57 on button Aug 03 19:48:07 ah Aug 03 19:48:36 that sounds like the NIC is doing some sort of speed/duplex negotiation Aug 03 19:49:49 what is your base computer? Aug 03 19:49:55 (what distro?) Aug 03 19:50:01 i can hook it directly to the rh 7.3 server Aug 03 19:50:42 i have rh7.3 server with win98 desktop and a gentoo laptop hanging off it, with server hooked to dsl modem Aug 03 19:50:43 let's figure this out from the computer that you would most likely be using to update the slug from.... Aug 03 19:51:05 so this is the gentoo laptop? Aug 03 19:51:11 yes Aug 03 19:53:22 i can ping 192.168.0.2, so i dunno if there is more network setup to do. i guess there isn't with a crossover cable. Aug 03 19:53:33 there isn't... :) Aug 03 19:53:44 that's a good thing Aug 03 19:53:54 does gentoo have mii-tool? Aug 03 19:54:23 i tried it and it says eth0: no link Aug 03 19:54:39 i mean with no params Aug 03 19:54:59 try this: mii-tool -F 100baseTx-FD Aug 03 19:55:37 nothing returned Aug 03 19:55:49 I think that is right Aug 03 19:56:10 meaning we just forcibly set the NIC to 100BaseT and Full Duplex Aug 03 19:56:38 k Aug 03 19:56:55 try the telnet before touching the nslu2... meaning let's see how fast it starts "trying" Aug 03 19:57:43 still same -- about 15 seconds Aug 03 19:57:58 well ouch Aug 03 19:58:26 with a cross-over cable, even! Aug 03 19:58:38 the ethernet led is lit on the nslu2? Aug 03 19:59:01 yes Aug 03 19:59:01 I mean when it fully powers up Aug 03 19:59:15 and ping seems responsive Aug 03 19:59:50 ping seems responsive? Aug 03 19:59:56 when telnet fails, it says no route to host, but i figured that is because the slug isn't listening at the time Aug 03 19:59:56 what do you mean? Aug 03 20:00:07 that would be the case Aug 03 20:00:18 normal, no lag Aug 03 20:00:42 you mean when you ping 192.168.0.2? Aug 03 20:00:46 yes Aug 03 20:00:56 that's your computer's IP address.... Aug 03 20:01:21 that response is like you knocking on your own front door and then asking "who's there?" Aug 03 20:01:30 oh, well i guess it would be quick :) Aug 03 20:01:35 :) Aug 03 20:01:51 very quick... ;) Aug 03 20:02:38 with the gentoo laptop, let's try one more thing Aug 03 20:03:05 k Aug 03 20:03:17 type in the telnet command and mentally time (try to be fairly exact) how long it takes before the "Trying...." starts Aug 03 20:04:23 that would be a 19 count :) Aug 03 20:04:38 ok Aug 03 20:05:06 so let's try it this way... with the power off on the nslu2, and the telnet command ready to go Aug 03 20:05:25 i'm there Aug 03 20:05:35 press enter on the telnet command, count to 17, hit power on nslu2, and be real ready to hit CTRL-C Aug 03 20:06:53 nah, missed, it popped out saying telnet: connect to address 192.168.0.1: No route to host Aug 03 20:07:44 ok... another thing... let's just prove to ourselves that the NIC can *see* redboot... Aug 03 20:08:06 type in ping 192.168.0.1 Aug 03 20:08:26 power up the nslu2 and watch to see if and how long the redboot responds Aug 03 20:08:53 k Aug 03 20:10:02 it saw it for 4 ping return lines Aug 03 20:10:14 so there it was... Aug 03 20:10:52 ok, leave the ping running Aug 03 20:11:11 open up another shell window and put the telnet command in Aug 03 20:11:50 when you see that first ping, hit enter on the telnet and be ready to hit Ctrl C Aug 03 20:12:29 k Aug 03 20:12:36 and before you get frustrated... I did this same thing non-stop for about an hour on an iMac.... Aug 03 20:13:48 hehe Aug 03 20:14:03 well, forgot about the telnet lag prob Aug 03 20:14:33 i see the 2 second window is a few (3 or 4) seconds after the power on Aug 03 20:16:16 I'm not sure that it's that long after.... but since I've added serial access, it's not something I really notice Aug 03 23:22:52 is ther ea log for the irc channels? like openjtag? Aug 03 23:26:10 landslide-wk: yep:http://loglibrary.com/ Aug 03 23:26:38 both the nslu2 channels are logged. Aug 03 23:51:33 hey, i just followed all the steps in installing unslung 5.5 Aug 03 23:51:51 the last step is to confirm after rebooting that linux is loading from the external drive Aug 03 23:51:55 how do i do that?? **** ENDING LOGGING AT Wed Aug 03 23:59:56 2005