[3645] in Release_7.7_team
Next question from Ji-yong Wang
daemon@ATHENA.MIT.EDU (Bill Cattey)
Fri Dec 20 16:27:28 2002
From: Bill Cattey <wdc@MIT.EDU>
To: release-team@mit.edu
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 20 Dec 2002 16:27:24 -0500
Message-Id: <1040419644.1438.21.camel@tokata.mit.edu>
Mime-Version: 1.0
I gave Ji-yong a series of steps to get her going, and her system
updated to the latest rev of 9.0. Then I remembered to advise her to
add "9.1" as an arg to update_ws to go to 9.1. Unfortunately she's
still not out of the woods:
On Mon, 2002-12-20 at 13:14, Ji-yong Wang wrote:
Thanks! You are always the best helper to my problem.
I actually tried the update_ws 9.1 (or 9.1.18) to manually update to
9.1 version, the system started normally, but failed by giving me
this message:
......
installing package vixie-cron-3.0.1-64 needs 160 Mb on the /
filesystem
*** installation failed ***
......
May be it because of the size of the / filesystem? I have 3.4 Gb for
/ and used 2.6 Gb.
Actually, I don't care too much about the version of my Linux to be
9.1 or 9.029. What I am looking for is to enable SecureFX which
needs ssh2. This Linux will serve for students in next semester to
get data, etc. The allowed users can ssh into the machine, but no
secure ftp. Can you help me on this? then I can forget about the
updating stuff.
So first off, I guess our space analysis code for updates isn't working
well enough.
I've given preliminary advice to "clear space on your drive and get that
partial update to complete". I've recommended sticking with the nice
update process rather than kludging on top of a partial 9.1/9.0 system
to have specific packages in it.
Do others see more advice I can give? Is it possible/safe to back out
of 9.1 and then to offer packages to add to get the stated ssh need met?
-wdc
