**** BEGIN LOGGING AT Wed Apr 09 02:59:57 2008 Apr 09 03:40:50 heh Apr 09 03:41:03 I got it to work by commenting out the lines that caused compiler errors in the driver's source code Apr 09 03:41:12 not the best idea, but when that's all you've got... Apr 09 03:41:17 hopefully it won't crash horribly Apr 09 11:31:33 Morning guys Apr 09 11:31:41 anybody home? :) Apr 09 12:10:53 . Apr 09 15:10:22 hi. I have installed debian 5 on my NSLU2 Apr 09 15:10:31 how to keep it updated? Apr 09 15:10:44 I mean, shoul I just run apt-get update from time to time? Apr 09 15:11:55 it's always a good idea to run 'apt-get update' and then 'apt-get upgrade' Apr 09 15:12:12 so you will keep your system up to date Apr 09 15:13:24 isn't there a way to let this run automatically? Apr 09 15:13:43 of course with cron but - maybe there is already an automated service or something Apr 09 15:14:44 cron is the easyest way to do that Apr 09 15:15:56 just use 'apt-get update && upgrade' in the crontab Apr 09 15:17:01 hmmm Apr 09 15:17:12 does this realy works? Apr 09 15:17:16 one moment Apr 09 15:23:39 hm, upgrade wait for a confirmation if it install the upgrades or not Apr 09 15:32:17 ah, thats it Apr 09 15:32:45 apt-get update && apt-get -y upgrade Apr 09 15:33:29 the -y flag confirm automaticaly all queries Apr 09 16:43:06 I think I'm using SlugOS/BE 3.10 (not sure, it's been a while since I did initial setup), and I have just conceived a need for jfs support, which doesn't appear to be in the default build or mentioned anywhere on www.nslu2-wiki.org (not findable via search, at least), nor is it mentioned if I do a grep through the output of ipkg list. Will an ipkg update help me? Are there any information sources I missed? Or do I need to look Apr 09 16:43:06 into setting up a working compile environment? Apr 09 23:56:33 out of curiosity, what happens if the root device you're using with Unslung (whether its an hd or a USB stick) fails? Apr 09 23:58:46 If I had to guess, I'd say "bad things". Apr 09 23:59:46 But I don't think it'd directly ruin anything other than the failed storage device. Apr 10 00:18:36 you think it would be possible to recover by reflashing the firmware? Apr 10 00:25:33 Yes. Further, I was under the impression that unslung, at least, didn't involve flashing the firmware in the first place? Apr 10 00:26:33 It's been a while since I was heavily interested in this stuff. Right now I'm only here because I have a problem with getting some fairly simple utility stuff working (jfs support, to access an existing filesystem). Apr 10 00:28:03 (Given that I'd almost be happy with read-only access, I'm considering checking for FUSE support in my current kernel. Of course, given that, user-mode usb would be nice...) Apr 10 00:34:44 MrWGW: if the root device you are using with unslung fails, you can recover without reflashing. Apr 10 00:35:19 Just remove the /.sda1root or /.sdb1root file on the flash filesystem, and re-unsling. Apr 10 00:37:26 mwester: Could you offer any advice on adding jfs support to a slugos system? Apr 10 00:37:54 It's apparently not in-kernel, nor are there any mentions in a quick grep of ipkg list. Apr 10 00:39:10 Yep, that certainly seems to be the case. Apr 10 00:40:30 You can try building the kernel with the module enabled, and seeing if the module will load in the flashed kernel. Apr 10 00:41:36 So whatever I do, I'm looking at setting up a build environment, and possibly flashing a new kernel if I can't just build the module I need? Apr 10 00:44:51 Yep Apr 10 00:45:17 I'm curious as to what specific need you have for jfs, however... Apr 10 00:46:26 Two hard drives, as an LVM2 setup, salvaged from a system that is too large to take with me when I go on a trip. Apr 10 00:47:25 I'd rather have the slug mediating access to the drives and sharing them over a local network than having to constantly disconnect and reconnect them from a laptop. Apr 10 00:48:02 (This is, of course, an obvious lead-in to wanting to use the slug as a firewall/NAT box as well.) Apr 10 00:49:50 I have no idea why jfs isn't enabled, unless perhaps busybox can't mount it (?) -- that's something that can be added for a future release, I expect. Apr 10 00:54:07 Do I just pull a kernel source tarball from kernel.org, or do I need some specific build environment and patch set? (Do I need to do the wget http://www.nslu2-linux.org/Makefile && make setup thing mentioned on HowTo >> SlugOSNativeCompileEnvironment, or is there some other setup I need?) Apr 10 00:56:29 You need the Makefile from www.nslu2-linux.org -- it will do all the rest for you. You'll need to build it using a cross-compilation env. as you can't do it natively (insufficient "oomph" on the NSLU2). Apr 10 00:57:01 So read the section on using the master makefile. Apr 10 00:57:32 What SlugOS version? Apr 10 00:57:44 I -think- it's 3.10, but I'm not sure anymore. Apr 10 00:58:14 For a laugh, the files I downloaded and installed from are on those two disks that I can't read right now. Apr 10 00:58:17 Yikes! that's old now. Apr 10 00:58:45 Okay, so a full upgrade is in order before I try anything else? Apr 10 00:59:09 No, your choice, as always. Apr 10 01:00:17 Indeed so. And I probably am better off with the upgrade. Apr 10 01:00:24 It may or may not build without lots of care, at this point -- you may have to go scrounging about to find some of the sources if they've been archived bythe various upstream folks. Apr 10 01:01:26 What does "cat /etc/issue" say? Apr 10 01:01:46 Let me turn it back on and I'll check. Apr 10 01:04:29 OpenSlug 3.10-beta \n \l Apr 10 01:05:51 ... and I see little customization here, so provided that I don't brick the thing I can safely wipe it all out without losing anything important. Apr 10 01:15:28 Do I understand correctly that, with SlugOS 4.8, the proprietary intel microcode for the ethernet interface is no longer required? Apr 10 01:18:08 (I suppose building from the source tarball would tell me that in fairly short order.) Apr 10 01:21:08 The intel microcode is still required; the intel driver is no. Apr 10 01:21:13 s/no./not./ Apr 10 01:21:39 Ah, okay. Apr 10 01:23:34 I guess one of my tasks for tomorrow is sorting out a new build host, then. Apr 10 01:24:52 Thank you for all the help. Apr 10 01:26:20 no problem. And you'll need a build host anyway. :D Apr 10 01:27:14 I guess so. At least I can build applications on the slug, though, right? Apr 10 01:27:24 It's kinda the geeky equivalent to those folks with all the sporting gear in the garage -- "Well, sure, I never go fishing, but *IF* we ever ran out of food and I *needed* a gill net to catch dinner, I'd have one!" Apr 10 01:27:46 Heh. Apr 10 01:28:08 I try to avoid some forms of that these days. Apr 10 01:45:15 Greetings peeps Apr 10 01:46:01 Anyone around that could assist me with a problem. Apr 10 01:53:41 if you just ask, someone might be able to help Apr 10 01:54:43 It's pretty simple but I am just messing with my slug box after several months. I just flash SlugOSBE-4.8-beta and after ssh into it I get only black and white text. Apr 10 01:54:58 None of the directories have colors. Apr 10 01:55:23 Debian Slug 3.10 didn't do this. Apr 10 01:56:36 oops Apr 10 01:56:47 anyway, anyone know how to change this or is it not possible. Apr 10 01:57:24 some kernels are built with the option to automatically display directory listings in colour coding. i guess SlugOS 4.8 was not compiled with that option Apr 10 01:57:45 i think "ls" command has an option to display listings in colour Apr 10 01:58:01 That would actually be a function of what was compiled into busybox. Try "ls --color" Apr 10 01:58:27 You could also install coreutils and see if that package has a different version of "ls". Apr 10 01:59:06 yep Apr 10 01:59:17 kk, checking now. thx =] Apr 10 01:59:43 ls --color works. Apr 10 02:00:07 :) Apr 10 02:00:13 Can I make an alias or something? Apr 10 02:00:59 i would guess thats possible. but im not sure exactly how Apr 10 02:02:25 ls --color [={always,never,auto}] seems to change it. Ill try it. Apr 10 02:06:32 alias ls to ls --color=auto in your bashrc file **** ENDING LOGGING AT Thu Apr 10 02:59:56 2008