**** BEGIN LOGGING AT Tue Jul 05 23:59:56 2005
Jul 06 09:42:55 <mike_gardner21> can anyone tell me how i can verify that the nslu2 is running on external rootfs
Jul 06 09:43:09 <NAiL> df
Jul 06 09:43:39 <NAiL> you should see it on the sizes
Jul 06 09:43:54 <mike_gardner21> when i originally started..root was mount at 81%.  i made some edits, and now it's showing 88%.  but the drives are mounted correctly.  for example, i see /share/hdd/data
Jul 06 09:44:25 <ByronT> Filesystem 1k-blocks Used Available Use% Mounted on
Jul 06 09:44:25 <ByronT> rootfs 153660192 6107884 145991192 4% /
Jul 06 09:44:25 <ByronT> /dev/sda1 6528 5316 1212 81% /initrd
Jul 06 09:44:25 <ByronT> /dev/sda1 153660192 6108004 145991072 4% /
Jul 06 09:44:25 <ByronT> /dev/sda1 153660192 6108004 145991072 4% /share/hdd/data
Jul 06 09:44:25 <ByronT> /dev/sda2 116661 4160 111297 4% /share/hdd/conf
Jul 06 09:44:32 <ByronT> that's what you should see
Jul 06 09:44:43 <ByronT> with df
Jul 06 09:44:48 <mike_gardner21> hmmm
Jul 06 09:45:15 <mike_gardner21> # df
Jul 06 09:45:21 <ByronT> but I can already state that if you see 88%, you didn't get a good unsling or your slug did not boot off of hd
Jul 06 09:45:37 <mike_gardner21> do i have to unsling every time i open a telnet session and want to edit?
Jul 06 09:45:45 <ByronT> unsling once
Jul 06 09:45:56 <mike_gardner21> because when i boot the nslu2, i do see activity on the usb hdd
Jul 06 09:46:03 <mike_gardner21> let me see if i can paste my df
Jul 06 09:46:16 <mike_gardner21> Filesystem           1k-blocks      Used Available Use% Mounted on
Jul 06 09:46:23 <mike_gardner21> rootfs                    6528      5712       816  88% /
Jul 06 09:49:35 <ByronT> you're just filling your flash now
Jul 06 09:49:41 <mike_gardner21> yep :(
Jul 06 09:49:58 <ByronT> that rootfs line shows that / does not equal /dev/sda1
Jul 06 09:50:41 <ByronT> telnet into redboot, re-flash unslung 5.5
Jul 06 09:50:52 <ByronT> (without hd attached!)
Jul 06 09:50:59 <mike_gardner21> i'm running an older version of the firmware
Jul 06 09:51:22 <mike_gardner21> i tried 5.5, but it would not mount the hdd automatically with the drive attatched
Jul 06 09:51:49 <ByronT> I believe that your timing might be a little off
Jul 06 09:52:05 <ByronT> after you reflash, and reboot without hd attached
Jul 06 09:52:21 <ByronT> telnet in (without hd attached!!!)
Jul 06 09:52:31 <ByronT> then hotplug your hd
Jul 06 09:52:42 <ByronT> make sure the web interface shows your hd
Jul 06 09:52:46 <mike_gardner21> when i would do that with 5.5, the web interface would not show the hdd
Jul 06 09:52:59 <ByronT> what port are you plugging the hd into
Jul 06 09:53:00 <mike_gardner21> with 4.x, it works fine
Jul 06 09:53:02 <mike_gardner21> disk1
Jul 06 09:53:18 <ByronT> the R29 linksys binary has an issue with port 2
Jul 06 09:54:00 <mike_gardner21> in 5.5, i had to run rc.bootbin just to get the drive to mount
Jul 06 09:54:18 <ByronT> what kind of drive / enclosure
Jul 06 09:54:32 <mike_gardner21> it's a western digital 120gb drive..the enclose is generic
Jul 06 09:54:56 <ByronT> all enclosures are generic - but they are still made by someone
Jul 06 09:54:59 <mike_gardner21> i would have no problem running 4.x, it's just that it's not booting rootfs.
Jul 06 09:55:12 <ByronT> I'm using bytecc's (as generic as generic gets)
Jul 06 09:55:42 <ByronT> which is essentially the same problem as you are seeing with 5.5
Jul 06 09:56:43 <mike_gardner21> #/dev/sda1            115205036     45000 113989624   0% /share/hdd/data
Jul 06 09:56:50 <mike_gardner21> that's the line i get when doing a df
Jul 06 09:57:02 <mike_gardner21> so it is mounting /dev/sda1
Jul 06 09:59:41 <ByronT> but not at boot
Jul 06 09:59:55 <ByronT> so you still have a problem with the drive mounting
Jul 06 10:00:10 <ByronT> that's why you have halfway filled your flash
Jul 06 10:01:26 <mike_gardner21> :(
Jul 06 10:01:51 <mike_gardner21> i can fix that by reflashing, right?
Jul 06 10:01:57 <mike_gardner21> and it'll go back down to 81
Jul 06 10:02:05 <ByronT> all that you have verified is that your drive will hotplug
Jul 06 10:02:45 <ByronT> which either means that something is funky with the drive / enclosure - or the unslinging process is not completing or done correctly
Jul 06 10:02:56 <ByronT> did you go to 4.x from 3.x?
Jul 06 10:03:24 <mike_gardner21> nope...i started by going to 5.5..when it wouldn't mount correctly with the drive attached, i went back to linksys firmware....after that, i reflashed to 4.x
Jul 06 10:03:45 <mike_gardner21> the drive now can be seen when booting with the drive attached, but it's not mounting rootfs
Jul 06 10:04:48 <ByronT> actually, the drive is still not seen while booting
Jul 06 10:04:59 <ByronT> it's just hotplugging before you check
Jul 06 10:05:04 <mike_gardner21> ultimately, i want this to run apache.  i can already see a problem.  because the built in webserver runs on port 80, apache runs on 8000.  i need to be able to change the default webserver to a different port and apache to 80
Jul 06 10:05:27 <ByronT> see if it were *seen* while booting, the rootfs would show as / on the /dev/sda1
Jul 06 10:05:54 <ByronT> plenty of ppl have no issues running apache
Jul 06 10:06:13 <mike_gardner21> but by default it runs on 8000, right?
Jul 06 10:06:22 <mike_gardner21> so the website would have to be http://mywebsite:8000
Jul 06 10:06:39 <ByronT> either, you set your router to port forward port 80 requests to your slugs port 8000 or....
Jul 06 10:08:49 <mike_gardner21> that makes sense.  that should work.
Jul 06 10:09:08 <ByronT> if you can get your hd/enclosure prob cleared up
Jul 06 10:09:39 <mike_gardner21> yeah, i think this nslu2 linux thing is great, it's just that it is acting quirky with me.
Jul 06 10:09:50 <mike_gardner21> i wish there was a manual way i could mount rootfs
Jul 06 10:10:05 <mike_gardner21> then i can add it to a boot script like rc.local
Jul 06 10:34:14 <ByronT> honestly mike, I would flash 5.5 and try to figure out why it is not being recognized
Jul 06 13:12:06 <NSLU2-IRC> "/nick demambero"
Jul 06 13:13:52 <plink212> ok i might be being a bit thick but.... I have installed dropbear and made sure i is running but when I try and log in i enter in the username root and the root password and it returns permissioned denied, does it use a difefrent passwd file or something as this password is workign the telnet interface?
Jul 06 13:15:25 <plink212> whoops
Jul 06 13:17:45 <plink212> so any ideas about my dropbear problem?
Jul 06 13:17:52 <caplink811> stay tuned
Jul 06 13:23:26 <caplink811> plink212,  you have read this doc http://www.nslu2-linux.org/wiki/HowTo/UseDropBearForRemoteAccess ?
Jul 06 13:25:04 <caplink811> plink212,  1st. which shell your user will use ? /bin/sh or /opt/bin/sh?
Jul 06 13:25:44 <plink212> yesyesye
Jul 06 13:26:01 <plink212> this java client is a bit fruity
Jul 06 13:26:14 <plink212> I am using /opt/bin/bash
Jul 06 13:26:23 <caplink811_log> time to try a proper client ;-)
Jul 06 13:26:46 * plink212 hangs head in shame
Jul 06 13:26:47 <caplink811_log> plink212,  and you've add /opt/bin/bash to /etc/shells? as valid login shell?
Jul 06 13:26:55 <plink212> yep
Jul 06 13:27:17 <plink212> am getting bash at telnet prompt
Jul 06 13:27:49 <caplink811_log> that's not the same... the password your use, is equal to the password which is in /etc/passwd for user root?
Jul 06 13:28:20 <plink212> how would one check that then?
Jul 06 13:29:32 <caplink811_log> cat /etc/passwd <enter> cat /share/hdd/conf/passwd<enter> and then compare the password (encrypted) fields
Jul 06 13:29:57 <plink212> yes sym linked
Jul 06 13:30:02 <caplink811_log> k
Jul 06 13:30:37 <caplink811_log> which client you've tried? putty?
Jul 06 13:30:47 <plink212> mac os x ssh
Jul 06 13:34:31 <caplink811_log> have you anything changed in /opt/etc/S51dropbear?
Jul 06 13:34:39 <plink212> no
Jul 06 13:34:48 <caplink811_log> k
Jul 06 13:36:54 <caplink811_log> which unslung version you're running?
Jul 06 13:37:14 <plink212> 5.5
Jul 06 13:38:17 <caplink811_log> mom, pls, must install dropbear..
Jul 06 13:42:58 <caplink811_log> installed, works out of the box
Jul 06 13:43:29 <caplink811_log> plink212,  hm, whats about the file permissions of /dev/ttyp* ?
Jul 06 13:44:07 <plink212> think I have shefted the passwd files with my symlinking doh
Jul 06 13:44:16 <plink212> shefted = shafted
Jul 06 13:45:37 <caplink811_log> hm, if your system boots with an attached hd, then /etc/passwd is a syslink to /share/hdd/conf passwd
Jul 06 13:46:06 <caplink811_log> if you're edit /etc/passwd then it is a real file, and the symlink is broken
Jul 06 13:48:17 <plink212> have broken the lot now, was the symlinking thanks for help
Jul 06 13:48:57 <caplink811_log> hm , a hurry customer...
**** ENDING LOGGING AT Wed Jul 06 23:59:56 2005