Re: [nslu2-general] Problem with telnet & re-flashing
- Yep, it's hosed! I'm not sure what you replaced, but note that at least *some* of the "passwd" files are not the password database, but are the passwd program executable instead. I'm betting that you replaced one of those...
You'll have to reflash. This documented somewhere on the wiki, but the "upgrade firmware" page in the GUI on unslung does not function - it was never meant to be operational, and the pages should have been disabled to make it more obvious. The wiki documents the necessary step to put the unit into "upgrade" mode using the reset button (which is the proper way with Unslung), and then you can reload the firmware using the appropriate utility (sercomm or upslug2).
But I'm concerned about the phrase "fell foul of the root password issue" -- what issue is that exactly? AFAIK, the root password issues were all addressed in the unslung procedure for unslung 6.8 -- you should have been prompted for the password by the unsling utility, which then sets the password appropriately in all the correct places, with no further user action regarding root password required. Can you be a bit more clear on the issue you've experienced?
> I've had a slug for a while but now want to be able to
> run 'slimserver' on there. So I successfully applied the Unslung
> 6.8 using the Linksys interface. Then I fell foul of the root
> password issue so I followed the instruction to change the password,
> copy the password file and create the script to start telnet
> automatically. This last bit appeared to work as telnet was
> available following a restart....and there were plenty of those as I
> couldn't get the password to stick - luckily it always came back to
> the doucmented value on rebooting without any disk attached. I
> eventually used 'find' to find all occurrences and copied the file
> to locations for both USB1 & USB2.
> Now, I can't access telnet, I see a load of error message suggesting
> there is nothing there (see below). Worse still, trying to re-apply
> any firmware results in a 'bad command or file name' error . Can't
> be good can it? Is it toast?
> /bin/login: root:UjUjeDSjkEuW.:0:0:root:/root:/bin/sh: No such file
> or director
> /bin/login: bin:x:1:1:bin:/bin:: No such file or directory
> /bin/login: lp:x:4:7:lp:/share/spool:: No such file or directory
> /bin/login: mail:x:8:12:mail:/var/spool/mail:: No such file or
> ftp:x:14:50:FTP: No such file or directory
> /bin/login: nobody:x:99:99:Nobody:/:: No such file or directory
> ourtelnetrescueuser:sPuRQwXaya5YE:100:100::/home/user:/bin/sh: No s
> ch file or directory
> /bin/login: guest:sc50wKPq.zChw:501:501:::/dev/null: No such file or
> /bin/login: admin:cgwvsHpJSf6XU:502:501::/home/user/admin:/dev/null:
> No such fie or directory