**** BEGIN LOGGING AT Mon Feb 07 23:59:56 2005 **** ENDING LOGGING AT Tue Feb 08 00:30:09 2005 **** BEGIN LOGGING AT Tue Feb 08 00:33:05 2005 **** ENDING LOGGING AT Tue Feb 08 00:36:12 2005 **** BEGIN LOGGING AT Tue Feb 08 00:39:05 2005 **** ENDING LOGGING AT Tue Feb 08 00:39:55 2005 **** BEGIN LOGGING AT Tue Feb 08 00:46:05 2005 Feb 08 01:36:05 hello ^_^ Feb 08 01:36:14 howdy Feb 08 01:36:53 alright. trying out the unslung bios upgrade now, bbias Feb 08 01:37:08 follow the directions word for word! Feb 08 01:37:13 I should know... Feb 08 01:37:28 sounds like the voice of pained experience :) Feb 08 01:37:58 :) Feb 08 01:38:12 more of open mouth, insert foot really Feb 08 02:48:02 hi all, I have an external USB2 250GB maxtor HDD, and I want to put it on a NSLU2, but I want multiple shares that are restricted to different users, will the default f/w do this or do I need to delve into changing the f/w please? Feb 08 02:48:12 howdy Feb 08 02:48:32 that's covered with basic Linksys functionality Feb 08 02:48:43 different shares dirs and perms? Feb 08 02:48:51 heya Byron. how long would you say the upgrade should take? (3.18) Feb 08 02:49:06 they would be considered as private directories Feb 08 02:49:38 but yes, the basic functionality should be enough if that's all that you need Feb 08 02:49:50 dzimet78, it can take a while.. Feb 08 02:49:59 ok cool thanks, and the format will be ext3 still? Feb 08 02:50:01 oh good. ;) Feb 08 02:50:16 No, yes Feb 08 02:50:23 thanks :) catcha Feb 08 02:50:30 dzimet78, how long has it been going? Feb 08 02:50:56 since my last comment. about an hour? Feb 08 02:51:01 or maybe it just seemed like an hour. Feb 08 02:51:04 too long. Feb 08 02:51:12 ooooh... Feb 08 02:51:23 well, the red blinky bit is still going. Feb 08 02:51:31 how can I best use my unit as a doorstop? Feb 08 02:51:40 horizontally, or vertically? Feb 08 02:51:49 no hd attached when upgrading, right? Feb 08 02:51:53 correct Feb 08 02:51:55 Send it to me. I have a door that fits a NSLU2 perfectly. Feb 08 02:52:03 heh. Feb 08 02:52:34 hrm. Feb 08 02:52:45 any suggestions as to what may have happened? Feb 08 02:53:09 what kind of connection are you using to do the upgrade? Feb 08 02:53:09 What method did you use? Feb 08 02:53:27 going through a hub. Feb 08 02:53:39 wired on both ends Feb 08 02:53:45 had no trouble connecting to the webserver Feb 08 02:53:52 but the unit had seemed a trifle flaky. Feb 08 02:55:30 you tested redboot access... http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlash Feb 08 02:56:02 and you can load the 3.18 firmware with the Sercomm utility Feb 08 02:56:39 that's why we really really really try to get ppl to test redboot access first.... Feb 08 02:59:45 heh. well - are there units where redboot does not work? Feb 08 03:00:20 I don't know of any... Feb 08 03:00:30 Also, unrelated - what does the alternating red/green status readout indicate? Feb 08 03:01:39 it sounds like something went wrong with the uploading of f/w from your computer to the sluf Feb 08 03:01:45 err.. slug Feb 08 03:02:19 SerComm should get you running pretty quick Feb 08 03:04:42 Red/Green means your slug is still in upgrade mode. Feb 08 03:07:03 dzimet78, how did you initiate the firmware installation? Feb 08 03:08:44 or better yet, were you running Stock f/w and upgrading to 3.xx?? Feb 08 03:11:44 dzimet78, did we lose you? Feb 08 03:21:25 * ByronT is away -( zzzZZZzzz )- at 05:21a -( P:On / L:On )- Feb 08 03:25:29 interesting questions. and now you went away :) Feb 08 03:25:58 answers being: yes, stock firmware Feb 08 03:26:19 and initiated via web interface. the readme indicated to go that route... Feb 08 03:26:50 but even before that point the unit was behaving oddly... staying in yellow during boot for inordinate periods of time Feb 08 03:27:07 Disc attached or no? Feb 08 03:32:11 disc attached? no. Feb 08 03:33:53 also, now it arbitrarily detects or does not detect the network connection. Feb 08 03:34:14 and I'm kinda thinking it was doing that before, but I can't remember for certain. Feb 08 03:35:29 ...and now it boots fine. Feb 08 03:35:41 * dzimet78 opens up Amazon's RMA page :p Feb 08 03:37:32 yeah. no changes to the firmware were made, apparently. Feb 08 03:38:30 i mean... does this sound at all familiar? Feb 08 03:38:32 There have been reported issues with it being plugged to certain branded hubs Feb 08 03:38:36 or switches Feb 08 03:39:26 an intel inbusiness 10mps hub? :p Feb 08 03:39:34 mbps also Feb 08 03:39:48 but even then - some of the issues are re: booting. Feb 08 03:40:06 that shouldn't be affected if the hub is the problem Feb 08 03:44:16 also, it would occasionally crash whilst I was trying to access redboot. anyway, I got an RMA label and requested a substitute. Feb 08 03:45:45 yeah. power cycled it just now, and it's hanging (yellow light) Feb 08 04:02:56 ...right :) g'night. Feb 08 13:25:56 * ByronT is back -( zzzZZZzzz )- gone 10 hr 4 min 31 s Feb 08 13:29:38 I would rant in here, but it would be logged Feb 08 15:36:28 "Welcome" Feb 08 15:43:05 ipkg -force-remove busybox Feb 08 15:44:30 hello JefferyS Feb 08 15:45:41 Hello ByronT Feb 08 15:46:17 I read your question in channel, what version busybox on you slug? Feb 08 15:46:27 err, your Feb 08 15:46:34 I have both the origional busybox and the new 1.x Feb 08 15:46:54 ok Feb 08 15:49:09 there is a way to install coreutils over busybox, but I'm checking to see if busybox has later utils than core Feb 08 15:52:26 ok... just checked slugbug and found that busybox and coreutils really really conflict Feb 08 15:52:40 so you have to make an either/or choice Feb 08 15:53:14 I'm installing the packages on the NativelyCompileUnslungPackages list so I can compile programs Feb 08 15:55:07 so you need coreutils more than busybox upgrade ipkg -force-remove busybox (check by looking at ipkg command at your slug) Feb 08 15:59:50 It says i have the current version of ipkg, but there doesn't seam to be a -force-remove option for it Feb 08 16:00:11 one sec Feb 08 16:03:14 ah.. -force-depends Feb 08 16:03:59 "ipkg -force-depends remove busybox" Feb 08 16:05:14 It said No packages removed Feb 08 16:05:33 * ByronT kicks at ipkg Feb 08 16:07:48 do you think that if I reinstalled busybox and then removed it, that it will remove all the files? Feb 08 16:08:29 you certainly can try and there would be no harm in doing it that way Feb 08 16:08:53 ok, I'll give it a try Feb 08 16:09:59 as you can probably tell busybox has been a PITA Feb 08 16:12:13 ya, its not being very friendly Feb 08 16:12:20 Installing busybox (1.00-6) to root... Feb 08 16:12:20 ERROR: Package busybox (parent busybox) is not available from any configured src. Feb 08 16:12:20 Failed to download busybox. Perhaps you need to run 'ipkg update'? Feb 08 16:12:20 An error ocurred, return value: -1. Feb 08 16:12:34 you have run ipkg update, right? Feb 08 16:13:14 yes, ran it after I got the error then tried to install again and got the same message Feb 08 16:13:27 ipkg update ran ok? Feb 08 16:13:44 yes Feb 08 16:13:48 then run ipkg upgrade Feb 08 16:14:14 get the latest of the latest packages on your system... then let's try removing busybox Feb 08 16:15:26 ok, its running, downloading a new bash, it may take a bit, on dialup Feb 08 16:15:55 ah... I can relate.. I had to do a bk clone over dialup (120MB_ Feb 08 16:16:26 ouch! Feb 08 16:35:33 how are things progressing? Feb 08 16:38:00 it finished ok, but still can't install or remove busybox. I downloaded the busybox package file to see if it will install from that. Feb 08 16:38:24 it's time to check depends... Feb 08 16:38:53 possibly something else is depending on your upgraded busybox and as a result won't let busybox uninstall Feb 08 16:42:35 [18:11:37]- / >ipkg whatdepends -A busybox Feb 08 16:42:35 Root set: Feb 08 16:42:35 busybox Feb 08 16:42:35 busybox Feb 08 16:42:35 What depends on root set Feb 08 16:44:57 try the ipkg whatdependsrec -A busybox Feb 08 16:46:17 same message as last one Feb 08 16:47:21 ok... ipkg -force-overwrite -force-depends remove busybox Feb 08 16:47:32 I tried to list the files in busybox, ipkg files busybox, it came back with "Package busybox not installed." Feb 08 16:48:08 yet when you telnet in, it shows busybox 1.##? Feb 08 16:48:15 or busybox 0.6? Feb 08 16:52:45 I switch to using the bash shell on my login, but on root which i didn't change anything it shows the .6, I can change my login back to busybox to see if it shows the 1.0 Feb 08 16:53:01 ahhhh Feb 08 16:53:21 I know I had 1.0 before I switched to bash Feb 08 16:53:33 you might need to work backwords Feb 08 16:53:45 as bad as that would be (dialup) Feb 08 16:55:03 not sure what you mean by work backwords Feb 08 16:55:29 remove bash, restore login shell to busybox Feb 08 16:55:54 oh, ok Feb 08 17:21:13 uh... everything ok, or are you really messed up Feb 08 17:21:51 hi all Feb 08 17:21:58 hello Feb 08 17:22:27 If I install a disk on the standard linux f/w, then I want to upgrade my f/w down the track to the project f/w, will my disk ahve to be reformatted or will the data appear on the new firmware? Feb 08 17:22:55 you won't *have* to reformat your disk Feb 08 17:23:15 but it would be a good idea? Feb 08 17:23:38 it is a "pre-installation" consideration to use an unformatted disk... Feb 08 17:24:10 Well I finally removed busybox 1.0, but it is in a different spot than the .6 version, so I still have the .6 version. Do I need to manually remove the files for busybox, looks like mostly simlinks. Feb 08 17:24:29 leave the .6 busybox! Feb 08 17:24:44 ok, well if I use a project f/w that will still allow me to have multiple share dirs for different users (I assume there is one)? will I still be best to reformat the disk down the track whenever I use a new project f/w (say openslug?) ? Feb 08 17:25:08 openslug is a whole different animal... Feb 08 17:25:14 ok forget that. Feb 08 17:25:26 unslung is more of Linksys functionality PLUS Feb 08 17:25:43 yep, like vfat etc? Feb 08 17:25:44 coreutils is still complaining about busybox, should I have it ignore it? Feb 08 17:26:00 JeffreyS, now you can ignore it Feb 08 17:27:18 Tthanks ByronT you have been a great help! Feb 08 17:27:27 no problem Feb 08 17:27:58 Well time to take a break cya, and thanks again Feb 08 17:28:12 time for me to head home... Feb 08 17:36:59 hi again, I am trying to reflash my slug abck to linksys using sercomm, and it cant find the slug, does it have to be on 192.168.1.77 or 0.1 ? Feb 08 17:37:24 uh... why use the sercomm utility? Feb 08 17:37:41 cos I cant be stuffed firing up my laptop in linux mode?! Feb 08 17:37:53 and gos the howto said I could! Feb 08 17:38:00 *cos Feb 08 17:38:20 you can use the web interface and just flash back the latest Linksys firmware Feb 08 17:38:56 oh.. couldnt see where in the web interface... hang I'll look again :) Feb 08 17:39:17 Administration, Advanced.... Feb 08 17:40:04 * NoRemorse blushes Feb 08 17:40:19 it's much easier that way... :) Feb 08 17:40:36 thanks :) Feb 08 17:44:47 I'm out of here Feb 08 17:45:25 * ByronT is away -( Gone for night! )- at 07:45p -( P:On / L:On )- Feb 08 19:55:19 hi all, is there a utility to allow me to hook up an ext3 slug drive to a windows xp pc, but be able to wrute with cirrect permissions? if not, can I use one of the normal utilities that writes as root, then somehow change the permissions once back on the slug? **** ENDING LOGGING AT Tue Feb 08 23:59:57 2005