**** BEGIN LOGGING AT Sun Feb 10 02:59:57 2008 Feb 10 11:01:47 Reedy_Boy: rebooted and on stick now ;) Feb 10 11:01:53 :) Feb 10 11:02:03 just going to do that mount by label stuff Feb 10 11:02:28 one wierd thing .. was that even though i formatted and ran mkfs, when i fdisk i see my new drive still as NTFS Feb 10 11:02:37 and i can mount it and read it fine as ext3 Feb 10 11:02:46 /dev/sdb1 1 91201 732572001 7 HPFS/NTFS Feb 10 11:03:15 lol Feb 10 11:03:19 did you format it as ext3? Feb 10 11:03:25 yeah Feb 10 11:03:32 weird Feb 10 11:03:35 NSUL2:/home/bb# mount -t ext3 /dev/sdb1 /media/hd/ Feb 10 11:03:39 mounts fine Feb 10 11:04:45 weird Feb 10 11:04:49 its just a bip then Feb 10 11:04:51 blip Feb 10 11:04:56 i remember when i formatedd it Feb 10 11:04:59 it moaned Feb 10 11:05:07 and said somethign about when restarted will be ok Feb 10 11:06:10 did you do this > mount with noatime Feb 10 11:07:17 sorry? Feb 10 11:07:26 err Feb 10 11:07:29 http://www.nslu2-linux.org/wiki/HowTo/UseAMemoryStickAsMainDrive Feb 10 11:07:33 stuff to reduce writes Feb 10 11:07:59 nope, i didnt Feb 10 11:09:30 and you swap onto the stick? Feb 10 11:10:42 on my unslung swap is off Feb 10 11:10:51 on my debian, its a mini hd, and yes, it swaps onto it Feb 10 11:11:11 lol i hope i dont end up burning my stick out too fast Feb 10 11:12:12 lol Feb 10 11:12:15 * Reedy_Boy shrugs Feb 10 11:12:21 im fiddling about with firefly again Feb 10 11:12:26 oh right Feb 10 11:12:29 i use that sometimes Feb 10 11:12:43 i upgraded to a svn snapshot thing Feb 10 11:12:46 1586 Feb 10 11:12:52 fixed the problems with it not starting Feb 10 11:12:57 now my soundbridge doesnt want to see it :( Feb 10 11:14:20 crap Feb 10 11:15:19 i'll sort it no doubt Feb 10 11:15:30 just have to catch ron when he's next on irc Feb 10 11:39:31 lol Feb 10 11:39:38 squid wont be stopped Feb 10 11:39:46 stopped from loading on startup Feb 10 11:40:11 And its sorted :) Feb 10 11:41:16 the soundbridge Feb 10 12:06:05 Reedy_Boy: Feb 10 12:06:12 ya Feb 10 12:06:19 yknow the mountdiskbylabel page Feb 10 12:06:32 did you have to do the stuff in Root filesystem bug Feb 10 12:06:49 which bit is that? Feb 10 12:07:17 At the time of writing the Debian / NSLU2 distribution has a bug which will cause the root disk that you specify on the kernel command line to be ignored. Feb 10 12:07:51 i didnt go off the main guide Feb 10 12:09:24 and did you have to do anythign clever, other than just label the drives and change fstab? Feb 10 12:09:51 i didnt even change the fstab Feb 10 12:09:55 link the guide please Feb 10 12:10:11 http://www.nslu2-linux.org/wiki/HowTo/MountDisksByLabel Feb 10 12:11:06 echo "ROOT=" > /etc/initramfs-tools/conf.d/my-root-device-hack Feb 10 12:11:06 update-initramfs -k all -u Feb 10 12:11:06 update-initramfs: Generating /boot/initrd.img-2.6.18-3-ixp4xx Feb 10 12:11:06 flash-kernel Feb 10 12:11:16 Thats what i did after making the label Feb 10 12:12:35 mother of god Feb 10 12:12:43 what? Feb 10 12:12:51 looks painful Feb 10 12:13:08 nah Feb 10 12:13:10 its quite simple Feb 10 12:13:53 i dont appear to have an update-initramfs Feb 10 12:14:03 :S Feb 10 12:14:46 logged in as root Feb 10 12:14:46 ? Feb 10 12:14:58 yup Feb 10 12:15:14 initramfs-tools - tools for generating an initramfs Feb 10 12:15:19 installed as part of that Feb 10 12:15:21 ? Feb 10 12:15:40 presumably Feb 10 12:15:43 it should be default Feb 10 12:27:18 tools installed Feb 10 12:27:26 echo "ROOT=" > Feb 10 12:27:32 this is the label you gave it? Feb 10 12:28:13 /dev/disk/by-label/labelyougaveit Feb 10 12:28:40 im guessing theres a danger that doing something wrong here will fuck the slug? Feb 10 12:29:30 well, your reflashing the kernel to the ram fs... Feb 10 12:29:31 but Feb 10 12:29:37 its only the same if your installing it Feb 10 12:29:40 OR updating the kernel Feb 10 12:29:48 so as long as you dont have a powercut, you'll be fine :) Feb 10 12:30:20 heh, and if something was to go bad, would i be in rebuild from scratch territory? Feb 10 12:30:38 reflash using upslug and carry on i suspect Feb 10 12:31:47 well here goes Feb 10 12:33:14 looks like a reboot after label Feb 10 12:33:16 back soon Feb 10 12:33:22 ok Feb 10 12:33:52 /etc/initramfs-tools/conf.d/my-root-device-hack Feb 10 12:34:03 my-root-device-hack Feb 10 12:34:10 the files in conf.d are just picked up then? Feb 10 12:34:13 regardless of name Feb 10 12:34:36 yeah Feb 10 12:34:40 k sweet reboot Feb 10 12:34:41 i presume it just builds them all up Feb 10 12:46:15 Reedy_Boy: what would happen if that stick happened to die, and i wanted to boot from somethign else (when i had changed my command line to boot from a label) i.e. would i have to label the next stick/device i wanted to boot from before slug would start? Feb 10 12:58:46 i'd suspect so Feb 10 12:59:48 hmm Feb 10 13:04:45 yeah, im not liking that much Feb 10 13:04:59 i swapped the sticks round in the slots, and restarted and it started from the stick Feb 10 13:05:06 as opposed to the disk Feb 10 13:05:15 i think i may live with this for a while Feb 10 13:05:17 The general practice if the Debian root device fails is a reflash anyway, so I don't think it's a big deal. Feb 10 13:05:42 ok thanks Feb 10 15:00:35 having some issues recognizing my external usb disk. i've flashed the slug w/upslug2 using latest debian image. at this point the status light is amber. it retains the default firmware (linksys v23..), as the debian installer never completes install process. i've reflashed a few times now. any suggestions would be great. Feb 10 15:22:34 nsunzofma: Can you ssh into the installer after you flash it? Feb 10 17:27:10 on my previous nslu2, i was able to send mail using "mail" command.. though, i cannot remember how i set this up, anyone know what ipkg package it is? Feb 10 17:27:29 i also need to make sure it uses my ISPs smtp server Feb 10 17:40:15 i have my slug set up as a webhost, but how can i get my router to point to it and the port it is operating on Feb 10 18:16:34 http://portforward.com/routers.htm Feb 10 18:22:04 ive found something on port forward and i type in my ip and the port number and it takes me to the server on my slug but how can i set this up to get dyndns to do this? Feb 10 18:22:38 You need an account, and something running the client to update dyndns Feb 10 18:22:44 then you can just use the friendly address Feb 10 18:35:30 ive created an account and im on dyndns now but where do i get my url? Feb 10 18:38:57 wanderingiii: http://www.nslu2-linux.org/wiki/HowTo/DynDNSupdate Feb 10 18:39:35 if your router has that feature, you can also it for that Feb 10 18:43:04 im on linux how do i telnet to the slug? Feb 10 18:44:14 telnet ipaddress Feb 10 18:44:15 ? Feb 10 18:44:51 You mean ssh, right? Feb 10 18:44:57 no didnt work. i tried ssh ip addess but it tried to log me in as my linux username rather than the root Feb 10 18:45:15 ssh username@ipaddress Feb 10 18:45:15 (nobody should be telnet'ing into slugs anymore, except to do the initial unsling) Feb 10 18:45:31 ah got it Feb 10 18:45:39 "man ssh" is helpful, often. :) Feb 10 18:47:48 i wonder how long before theres a default "man rtfm" Feb 10 18:47:58 lol Feb 10 19:04:18 any instructions on hwo to point your ip to the webhost on the slug? Feb 10 19:05:57 what do you mean? Feb 10 19:06:04 the ip points to your router Feb 10 19:06:10 then you forward the ports you need Feb 10 19:06:18 yes and i want to set it up to point to the slug and port Feb 10 19:06:38 for web interface? Feb 10 19:07:12 yes Feb 10 19:07:38 not for the slugs interface, for the web pages ive set up Feb 10 19:07:39 port forward http (ie tcp port 80) Feb 10 19:08:15 or whatever port is on your slugs webserver Feb 10 19:08:30 my slugs operating on 8089 so i need to point my ip to slug:8089 Feb 10 19:09:10 you may need to create a custom service Feb 10 19:09:21 and use the service for a rule on the router Feb 10 19:10:30 wanderingiii: Think of your IP as a phone number for a business -- that's insufficient to reach a real phone (you need an extension in addition to the main number). You need a port number as well. Feb 10 19:11:15 What you need to do on your router is set it up so that when it gets an incoming connection on your IP address, port # 80, it forwards that to your NSLU2's IP address internally, to the port number you have assigned to your web server on the NSLU2 Feb 10 19:11:27 That's what that URL I posted helps you set up on your router. Feb 10 19:11:28 yes ive a fair idea of what i need to do but just dont know how to carry it out. normally traffic would go to myip and port 80 but i need to point it to the slug and port 8089 Feb 10 19:11:40 Not all routers support port redirection Feb 10 19:11:51 so you may not be able to do externalip:80 --> slug:8089 Feb 10 19:11:53 Right. But that has nothing to do with the NSLU2 Feb 10 19:11:54 my routers is a netgear dg834g Feb 10 19:11:59 That doesnt Feb 10 19:12:00 for a fact Feb 10 19:13:07 If that's the case, then you have several options. You can try to move the Linksys web gui off of port 80, and move your web server to port 80 instead. Risky. Feb 10 19:13:29 You can just have users use :8089 for your address. Painful, but less risky. Feb 10 19:13:50 Or, you can get a better router. (Preferred, if you are going to do this sort of thing seriously) Feb 10 19:14:11 yea but problem with that is if they dont type port number they get access to my slug Feb 10 19:15:00 Yep. But if you try to move the Linksys GUI (I'm assuming unslung) off of port 80, you may lose access to your slug! Feb 10 19:15:46 yea i dont want to do that either so can i not point it automatically to port 8089 instead of 80? Feb 10 19:16:43 If your router can do it, the correct solution is to map :80 to :8089 --- but your router must support that feature. Feb 10 19:16:57 hmm no idea how to do that. Feb 10 19:17:18 That's why I posted you that URL. Feb 10 19:18:26 what url? Feb 10 19:25:33 http://portforward.com/routers.htm Feb 10 19:25:51 WanderingII, the DG834(G)?(T)? are home grade routers Feb 10 19:25:57 they dont have port redirection Feb 10 19:26:41 and its not like you can put dd-wrt/openwrt on them to do it Feb 10 19:27:25 Well, the web interface *doesnt* do port redirection Feb 10 19:27:29 but its getting off topic Feb 10 19:33:56 hmm so does that mean im stuck with ip:8089 ? Feb 10 19:34:10 yup Feb 10 19:34:12 as it stands Feb 10 19:38:02 what about this: http://portforward.com/english/routers/port_forwarding/Netgear/DG834G/default.htm Feb 10 19:42:51 WanderingII, thats just how you port forward Feb 10 19:43:00 so externalip:8089 --> slug:8089 Feb 10 19:46:09 ah ok Feb 10 21:12:36 having some issues recognizing my external usb disk. i've flashed the slug w/upslug2 using latest debian image. at this point the status light is amber. it retains the default firmware (linksys v23..), as the debian installer never completes install process. i've reflashed a few times now. any suggestions would be great. Feb 10 21:14:00 it shouldnt retain the stock firmware if the flash worked Feb 10 21:15:37 Reedy_Boy: So it is safe to assume that upslug2 isn't flashing with the new firmware. could it be that i have a defective slug? Feb 10 21:16:10 Reedy_Boy: i've watched the the flash process,but no error codes are provided. Feb 10 21:16:18 does it boot back up into the linksys firmware? Feb 10 21:17:55 Reedy_Boy: when the upslug2 utility claims to be complete, i quickly attach the USB drive and wait for the loud beep. it never seems to actually reboot. the linksys firware remains. Feb 10 21:18:23 so it will boot back up into the linksys firmware, so you can access the linksys web interface? Feb 10 21:20:23 Reedy_Boy: i've not tried the web interface lately. i only used it to change the IP address to support my subnet. Feb 10 21:20:32 right Feb 10 21:20:38 but when its booted, do you get it? Feb 10 21:21:04 Reedy_Boy: one sec.. i'll try it now. Feb 10 21:21:14 as if thats still there Feb 10 21:21:18 the flash hasnt worked Feb 10 21:23:26 Reedy_Boy: i can't ping device.. ready/status light is amber Feb 10 21:23:38 can you ssh onto it? Feb 10 21:23:55 Reedy_Boy: no linksys interface.. cannot ssh into it either. Feb 10 21:24:01 right Feb 10 21:24:05 how long have you waited? Feb 10 21:24:49 Reedy_Boy: quite awhile.. i'll try a cross-over cable. Feb 10 21:25:05 are you sure your using the right ip address? Feb 10 21:26:57 Reedy_Boy: yes Feb 10 21:27:24 what IP are you trying to use? Feb 10 21:28:28 Reedy_Boy: i changed the ip address to one that supported my LAN. Feb 10 21:28:42 ok, which is? Feb 10 21:28:55 Reedy_Boy: 192.168.0.25 worked fine for me. Feb 10 21:28:59 right Feb 10 21:29:17 i was just making sure, as there are some issues if you make it static on the default 1.77 Feb 10 21:29:37 Reedy_Boy: ok Feb 10 21:31:27 so, its not issues recognising the disk, or not at least Feb 10 21:31:53 your on linux, i presume? Feb 10 21:32:33 Reedy_Boy: yep, i want to flash it with debian firmware. Feb 10 21:32:44 right, which you should've done Feb 10 21:33:33 Reedy_Boy: upslug2 reports firmware re-write and verifies as appropriate. Feb 10 21:33:38 right Feb 10 21:35:56 Reedy_Boy: well the null cable doesn't see device. i probably corrupted the firmware. i'll reflash with default linksys firmware and then use the null cable again to verify the IP address. Feb 10 21:36:12 it seems it *may* not be on the IP your expecting Feb 10 21:36:32 Reedy_Boy: indeed. Feb 10 21:36:38 if your familiar with nmap or similar.. you could see if its responding on another ip Feb 10 21:37:08 Reedy_Boy: yep, i could use nmap 192.168.0.* Feb 10 21:37:20 Reedy_Boy: yep, i could use nmap 192.168.1.* Feb 10 21:37:21 probably 192.168.*.* Feb 10 21:37:25 yeah Feb 10 21:37:30 just to make sure its not on the default Feb 10 21:37:37 however Feb 10 21:37:47 if it was on the default ip, it would be taking a DHCP address Feb 10 21:37:49 hence me asking before Feb 10 21:38:03 do you have a router that does dhcp? Feb 10 21:38:13 Reedy_Boy: understood, but i'm not running dhcp. Feb 10 21:38:18 right Feb 10 21:38:31 so if it is on the default ip, for whatever reason it cant get a dhcp address Feb 10 21:39:23 Reedy_Boy: correct Feb 10 21:39:37 try sticking it back on a stock firmware Feb 10 21:39:45 see if it comes back to life on .25 Feb 10 21:39:51 Reedy_Boy: getting ready to do that now. Feb 10 21:43:00 Reedy_Boy: reflash in progress Feb 10 21:46:49 Reedy_Boy: reflash successful, i can ping the slug on .25 Feb 10 21:46:55 right Feb 10 21:47:03 and its come back up with the interface? Feb 10 21:47:21 Reedy_Boy: the ready/status indicator is now green. Feb 10 21:47:27 yeah Feb 10 21:47:45 Reedy_Boy: i'm checking out the web interface now Feb 10 21:48:38 http://www.cyrius.com/debian/nslu2/install.html Feb 10 21:48:47 If you have configured your network settings through the Linksys web interface to use a static IP address other than the default address 192.168.1.77, these values will be used (including the hostname). Feb 10 21:48:47 Otherwise, DHCP will be used. You can use the MAC address of your NSLU2 to tell your DHCP server to give out a specific IP address to your machine. Feb 10 21:48:47 If no address can be found via DHCP, the default value which Linksys uses will be used: 192.168.1.77 Feb 10 21:51:39 Reedy_Boy: understood. the real problem is that it refuses to accept the di-nslu2.bin image. Feb 10 21:51:55 the web interface refuses it? Feb 10 21:52:30 Reedy_Boy: i've been flashing it via upslug2. perhaps i'll try using flashing via web interface. Feb 10 21:52:44 Reedy_Boy: i'm a CLI junkie ;) Feb 10 21:52:51 lol Feb 10 21:55:23 Reedy_Boy: welp, i can see the slug with the web interface. i'll run through procedure again and try flashing with the web interface this time. apparently upslug2 doesn't like me. Feb 10 23:12:21 nsunzofma: if upslug2 completes the verification step (the "u"s in the bar change to "V"s), then it was sucessful - I'm not sure from the log here why you think the flash failed. Feb 11 02:50:18 has anyone a workaround for the "Known bug" http://www.nslu2-linux.org/wiki/Optware/AppWeb in the latest optware release of AppWeb? Feb 11 02:52:35 default:1 pool.0 Error: 404 "Not Found" for "/", file "/opt/var/appWeb/web/": Can't access URL Feb 11 02:52:39 :( **** ENDING LOGGING AT Mon Feb 11 02:59:56 2008