Re: [cobalt-users] New Guy (Ssh install)

[Kris Dahl <kris@xxxxxxxxxxxxx>]

on 2/22/00 3:30 PM, Rand at shawk@xxxxxxxxxxxxxxx wrote:

> Hey all,
> 
> Im a newbie here, and to linux, so forgive my lack of knowledge, Im hoping
> to make up for it in the future ;)
> 
> I followed the faq on cobalts site on how to install ssh, however, Im having
> no luck. It appears to install great, but I am still unable to SSH into the
> box.. Any ideas?
> 
> Im also interested in installing pine, whois, irc, if anyone had any success
> with these, please let me know.

I have gotten all of those to work at one time or another.

First things first: ssh
Make sure that sshd is running...

ps -x
as root should show it running

if not, do a 
whereis sshd
and if that doesn't work try a
locate -u 
locate sshd

That should tell you where the daemon is installed.  Then all you have to do
is run it.  I'd suggest setting it up to start upon reboot (I believe there
is a shell script that comes with sshd that will let you do this), otherwise
you'll need to create your own and use ntsysv to implement it.

Next: Pine.  Snag the source for pine (4.21 I think is the latest) from uw
(search on freshmeat for the exact link)... it'll have the stuff for pico,
etc. as well.  I've had a lot of problems with the standard pico that comes
with the Raq seg faulting on me.  Recompiling the latest version seemed to
help quite a bit.  You shouldn't run into any problems getting this part
going--standard automake stuff.

tar xzf pine_blah.blah.tar.gz
cd pine_blah.blah
./configure
make
make install

I beleive you can get a MIPS rpm from cobalt for whois--don't remember
precisely how.  I'd check ftp.cobaltnet.com in experimental and contrib
directories.

IRC--I'd use BitchX, which is pretty easy to compile... same process as
pine/pico, to the best I can remember.

Freshmeat is your friend.  http://www.freshmeat.net.  Big ol software
depository.  Most of the majorly supported packages (pine, BitchX, etc.)
have great documentation typically, including extensive FAQs,
troubleshooting, etc.

Crash course in Linux administration--let me know if any of this doesn't
make sense.

-k