**** BEGIN LOGGING AT Sun Sep 16 02:59:57 2007 Sep 16 09:57:05 damn. i somehow screwed up my nslu and can't login anymore via telnet and ssh. is there a way to "reinstall" the firmware without losing the data on the usb hd? Sep 16 10:20:52 phil: Did you check the "how to recover from a bad flash" page? Sep 16 10:25:07 uh, thx Sep 16 10:29:38 http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlash Sep 16 10:30:45 yep Sep 16 10:30:52 and it will not lose any data on the hd? Sep 16 10:33:43 I just did it a few seconds ago and my hard disk is still intact :) Sep 16 10:33:53 phew, ok :) Sep 16 10:34:25 and it will restore a original, fresh unslug, right? Sep 16 10:42:09 I think the trick is to flash it without a disk attached, let it reboot into unslung from flash. Then you can re-attach your disk and do whatever you need to do to fix it. Sep 16 10:42:30 ah ok Sep 16 10:42:31 but I'm new to this myself, so I'm not that experienced with this stuff Sep 16 10:42:43 so it's unslung after i upslugged it? Sep 16 10:43:40 I just re-flashed mine with upslug2 with the hard disk detached, and it's rebooted into the stock unslung running from flash Sep 16 10:44:29 ok Sep 16 10:48:46 hello Sep 16 10:49:22 Yo. Sep 16 10:59:04 Frijj: are you using os x? Sep 16 11:01:42 No, I run Ubuntu on my desktop Sep 16 12:58:13 Frijj: does you nas works again now? Sep 16 13:04:27 I still have the same problem with the network not working except right after it has been flashed Sep 16 13:04:53 I put the Linksys firmware back on and confirmed that it does work okay with that Sep 16 13:05:08 except now it won't read my disk anymore, which has confused me Sep 16 13:05:24 It mounts it but then hangs as soon as I try to do anything to it Sep 16 13:06:14 Unslung won't read my disk either. Neither firmware will actually boot with the disk attached, but they boot okay without it attached. Sep 16 14:01:31 i tried to upslug my nslu, but i can't find the arp adress Sep 16 14:01:41 it says the following when i run 'arp -s' Sep 16 14:01:42 http://www.nslu2-linux.org/wiki/Main/UpSlug2onOSX Sep 16 14:01:43 oops Sep 16 14:01:49 ? (192.168.7.77) at (incomplete) on en1 [ethernet] Sep 16 14:02:03 any ideas what to do? Sep 16 14:04:05 ah got it Sep 16 14:14:11 erm Sep 16 14:18:22 how can i delete the previous installed system? Sep 16 14:18:41 i've successfully upslugged my system Sep 16 14:19:03 and then recopyed the data to my disk Sep 16 14:19:16 but somehow there still seems to be some old data which keeps me from logging in via telnet Sep 16 14:19:29 is there a way to delete the stuff previously stored on the hd? Sep 16 14:30:24 anyone? :/ Sep 16 14:39:47 If you boot it without the disk attached and log in via telnet, and *then* plug the disk in you should be able to do whatever you need to do to the disk Sep 16 14:40:11 Without the disk plugged in, the root password will be the default: uNSLUng Sep 16 14:40:19 yes Sep 16 14:40:30 but after i unslung i have the same old configuration Sep 16 14:40:36 some files on the hd don't seem to get overwritten Sep 16 14:40:50 so i guess i have to delete some files manually Sep 16 14:40:57 I guess you'll have to manually delete the stuff off the disk and then re-unsling Sep 16 14:41:02 yeah Sep 16 14:41:06 but do you know which files? Sep 16 14:41:13 and where they're located? Sep 16 14:41:29 I'm afraid I don't know Sep 16 14:41:34 ok, np :) Sep 16 14:41:48 I'd be tempted to just nuke /etc, /opt and all of the other system directories and re-unsling Sep 16 14:41:54 but I've not tried it :) Sep 16 14:41:57 ok Sep 16 14:42:18 Watch out for any directories that actually contain data you want to keep, of course Sep 16 14:42:58 hehe, yes Sep 16 14:50:43 phew :) Sep 16 14:50:44 got it Sep 16 15:00:26 i've still got another question: isn't it quite dangerous to do http://www.nslu2-linux.org/wiki/Unslung/UpgradeBusyBoxUsingIpkg? Sep 16 15:00:45 couldn't it create problems when the default busybox is replaced? Sep 16 16:08:10 phil: do you know what is busybox? Sep 16 16:08:25 yeah Sep 16 16:08:27 of course Sep 16 16:09:00 i don't know so Sep 16 16:09:22 i even wonder if upgrading busybox can bring something Sep 16 16:10:01 even if you miss the upgrade, you can reflash your nas Sep 16 16:13:30 There are mutiple busyboxs installed on Unslung; the one managed by ipkg is not essential to correct operation of the core system. However, attempting to upgrade or remove it once installed can be problematic. Avoid it if possible. Avoid installing busybox in the first place, if you can. Sep 16 17:39:57 anyone here who runs rtorrent on his nslu? Sep 16 18:09:09 hi there Sep 16 18:19:44 if "ipkg info" shows me the following maintainer, who should i email then? Sep 16 18:19:47 maintainer: NSLU2 Linux Sep 16 18:19:49 really the yahoo group? Sep 16 18:26:56 phil: i ran rtorrent on slugosbe and debian slugs Sep 16 18:28:19 if maintainer == nslu2-linux@yahoogroups.com, means any developer can step up and make changes to that package Sep 16 18:28:53 okay Sep 16 18:29:05 eno: did you have problems with the progressbar? Sep 16 18:29:17 on which firmware? Sep 16 18:29:25 unslug Sep 16 18:29:36 it shows me things like: Sep 16 18:29:37 0.0 / 0.0 MB Rate: 57.1 / 50.3 KB Uploaded: 0.0 MB [13%] 0d 2:35 [ R: 0.00 high] Sep 16 18:29:54 rtorrent is known to have problem on unslung Sep 16 18:29:57 which seems weird .. when it's at 13%, i can't be that it has downloaded 0.0MB up to now Sep 16 18:30:01 oh really? Sep 16 18:30:17 and how's the chance that these bugs are getting fixed? Sep 16 18:30:56 chances are slim, search mailing list archive for details Sep 16 18:31:53 see the link on http://www.nslu2-linux.org/wiki/HowTo/BitTorrent Sep 16 18:32:49 oh ok Sep 16 18:34:00 the downloading probably is working and just the display problem Sep 16 18:34:11 but i'm not very sure Sep 16 18:34:34 on unslung, i use btpd instead Sep 16 18:35:07 yeah, that's pretty much what it's like atm Sep 16 18:35:10 btpd? Sep 16 18:35:39 a command line bt client Sep 16 18:35:45 i've tried ctorrent but it seems to be blocked by most trackers Sep 16 18:36:50 it is stupid blocking certain clients Sep 16 18:37:28 force ppl to masquerade as other client Sep 16 18:37:30 f course it is Sep 16 18:37:40 yep **** ENDING LOGGING AT Mon Sep 17 02:59:57 2007