**** BEGIN LOGGING AT Mon Apr 07 02:59:56 2008 Apr 07 03:02:51 scant: does it say anything when you plug/unplug a usb device? Apr 07 03:04:02 abliss: no, i don't think so Apr 07 03:04:15 i made a .rules file and put it in /etc/udev/rules.d Apr 07 19:58:59 does anyone use scponly? Apr 07 20:00:06 damn, damn, damn Apr 07 20:00:16 I reboot the nslu2 for the first time in 3 months and it doesn't come up Apr 07 20:00:27 and of course I was a big dummy and soldered the usb stick in internally Apr 07 20:00:59 I guess I could remove and trash the usb stick, and use an external one from now on Apr 07 20:01:32 o_O why did you do this? just for the look? Apr 07 20:01:38 yeah, and for the free usb ports Apr 07 20:01:54 not worth the trouble, really Apr 07 20:02:06 because I realized afterwards I couldn't troubleshoot it Apr 07 20:02:19 so it's hung somewhere booting up and I have no idea where Apr 07 20:02:52 did you try to reinstall the firmware? Apr 07 20:03:49 well, I can't talk to it over the network Apr 07 20:03:56 which is the problem Apr 07 20:04:08 I don't even know if the ethernet is up or now Apr 07 20:04:09 not8 Apr 07 20:04:11 not* Apr 07 20:04:15 which firmware? Apr 07 20:04:55 debian Apr 07 20:05:27 is there a page somewhere describing the LEDs during the boot sequence? Apr 07 20:05:56 n17ikh, have you other drives attached? Apr 07 20:06:28 nope Apr 07 20:06:36 I've got a ready/status light, green with flickering orange Apr 07 20:06:43 n17ikh: i mean did you try http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlash ? Apr 07 20:06:45 the disk led lights up if I plug something into USB Apr 07 20:06:59 green with flickering orange should mean its accessible Apr 07 20:07:06 so I'm thinking it's booted, with no ethernet Apr 07 20:07:07 well, that its booted Apr 07 20:07:09 because I have no ethernet light Apr 07 20:07:19 would sound like its not connected Apr 07 20:07:23 checked the cable and such? Apr 07 20:07:42 yeah, nothing has changed since I was ssh'd into it as it rebooted Apr 07 20:07:47 I just upgraded my nslu2 system using aptitude. The device boots fine, but my network device doesn't work! Apr 07 20:07:47 At some point the onboard nic switched from eth0 to eth1. Turn off the slug. Take your usb disk out and mount it on another machine, edit /etc/network/interfaces. Duplicate your eth0 config to eth1. Unmount the disk. Plug it back into the slug. Power the slug on. Apr 07 20:07:54 great Apr 07 20:08:30 wonder if I could just open it up, solder more connectors onto the usb stick, and hack it into working temporarily Apr 07 20:08:36 with another computer Apr 07 20:08:43 that'd be an awful hack, but it might work Apr 07 20:09:47 or maybe I could flash it with a flash-only OS Apr 07 20:09:56 and then fix my usb stick Apr 07 20:25:12 what's a good firmware to use for that? Apr 07 20:25:34 something that'll boot up, get an address from dhcp, and let me mount an ext3 usb stick Apr 07 20:27:34 putting the thing into reset mode made slightly more awkward by the fact it's taped to the back of a bookshelf Apr 07 20:40:20 well, that was annoying... it somehow has my old, old root password Apr 07 20:40:27 must store it in the bootloader area of the flash, or something Apr 07 20:41:18 what? O_o Apr 07 20:45:11 I dunno Apr 07 20:45:21 I flashed it with openslug and the root password was an old one I used Apr 07 20:45:27 ...on the linksys firmware Apr 07 20:45:39 so it must be stored in some special config area on the flash, or something Apr 07 20:45:47 that doesn't get overwritten when you write a new image Apr 07 20:46:19 so anyway Apr 07 20:46:20 Yes. That's the sysconf area. Used by Linksys, Unslung, SlugOS, and Debian Apr 07 20:46:32 I flashed it with openslug, and fixed the network misconfiguration Apr 07 20:46:40 now I need to get debian back on there, somehow Apr 07 20:46:47 I guess I should have thought of that first Apr 07 20:47:35 If you are going to use a soldered-in USB flash device, and lack a serial console, you would be better off with one of the firmwares that can boot to internal flash in event of a problem. Apr 07 20:47:38 Such as SlugOS. Apr 07 20:48:54 probably, yeah Apr 07 20:49:00 but I liked debian well enough Apr 07 20:49:28 I bet if I try the debian installer image it'll clobber my flash drive, though Apr 07 20:49:29 Serialise it then Apr 07 20:49:38 * mwester shrugs Apr 07 20:49:45 Presumably if you can solder a memory stick, serialising it cant be out of your capabilities Apr 07 20:50:01 well, I have one of those fancy usb to serial things Apr 07 20:50:06 I just never bothered to set it up :/ Apr 07 20:51:14 but now that I've solved this problem, presumably it'll boot fine from here on out. I can always use the same method to fix it Apr 07 20:52:01 does anyone use scponly? Apr 07 20:53:03 or what else do you use on unslung for sftp / scp? Apr 07 20:53:10 Nightwolf, you'll possibly have more luck posting on the mailing lists Apr 07 20:54:04 Nightwolf: what's wrong with scp with openssh? Apr 07 20:55:06 mwester: it's not chrooted Apr 07 20:55:49 * mwester decides to not even ask why someone would use Unslung in a secure environment Apr 07 20:56:34 lol Apr 07 20:56:43 No, scp with chroot is a pretty advanced combination, you are unlikely to find anyone else who has tried that on Unslung... Apr 07 20:57:03 sorry i'm a newbie, why should i not use unslung if i care about security? Apr 07 20:58:05 Unslung is Linksys' stuff, opened up. We have no source code for any of Linksys' software, so even if someone wished to audit it for security, we have no source to audit. Apr 07 20:58:19 mwester: there are two howtos (one that uses scponly) on the wiki Apr 07 20:58:26 There is simply no assurance that Linksys' stuff is secure. Apr 07 20:58:35 Nightwolf: the wiki is full of stuff I don't recommend. Apr 07 20:59:21 The community owns the wiki; they are free to do what they will, but I feel compelled to point out when someone is doing something that might result in their photo collection or personal data going drifting all about the internet... :D Apr 07 20:59:48 What is the problem with scp and chroot? Apr 07 21:00:05 mwester: well that's true, but on one page it was said unslung would be the best for new users - i mean i'm not paranoid, i just want don't want my friends to have access to / Apr 07 21:00:56 the server doesn't accept my key when i connect with the scponly user Apr 07 21:01:33 Have you started with basic (i.e. password) authentication, and without chroot? Apr 07 21:02:30 i have another normal account (because i also want to access /) that works without problems Apr 07 21:03:59 Good. Does it work with a key only? Apr 07 21:04:11 yes Apr 07 21:04:24 Excellent. Then the problem must be in how you've set up your chroot. Apr 07 21:04:46 Duplicate that account, incl. key, into the chroot environment, and troubleshoot from that. Apr 07 21:05:14 The most common problems are not unslung-specific at all, but can be debugged by googling for openssh chroot and scp (or similar). Apr 07 21:05:29 Permissions, missing files in the chroot, etc. Apr 07 21:06:14 Watch out for paths that are coded to "/opt/..." in openssh. Apr 07 21:06:16 mwester: the problem is that i'm absolutely not into scponly, i just installed it and used the script to create the user and his folders / files Apr 07 21:06:33 Well, you'll have to get into it to solve the problem, I think. Apr 07 21:06:39 :) Apr 07 22:18:50 howdy. anybody hear can help me wirh cron jobs? Apr 07 22:41:56 Dinkers: what's your problem? Ask away. Apr 07 22:42:17 Just be patient as we're pretty quiet much of the time. Apr 07 23:29:11 I'm having a problem now... I've chrooted into my debian install and am attempting to use flash-kernel to write my kernel and rootfs back to flash, but it complains that the kernel is too large to fit into flash Apr 07 23:29:24 as suggested here Apr 07 23:29:25 http://osdir.com/ml/debian.ports.arm/2006-12/msg00056.html Apr 07 23:29:46 I'm using slugos/le instead of the debian installer as the recovery image, if that makes a difference Apr 07 23:29:56 I've mounted dev and proc inside the chrooted os Apr 07 23:50:13 Can you shrink your kernel at all? Remove some drivers and make them modules? Otherwise I think you're going to need to reflash to make room for your kernel. Apr 07 23:54:00 well... it sucessfully wrote this kernel to ram before Apr 07 23:54:10 s/ram/flash Apr 07 23:54:16 so I don't know what's up Apr 07 23:54:35 it's too big for the 1 mb allocated for the kernel though, so I guess I somehow need to make it write the apex bootloader to firmware there? Apr 07 23:56:57 I mean, all my kernels have been bigger than 1mb Apr 07 23:57:26 I guess what I'm trying to say is, I don't know how debian has the system boot.. apparently they use apex in the kernel space on the flash area to make it boot the real kernel **** ENDING LOGGING AT Tue Apr 08 02:59:56 2008