just as a sugguestion, you could mount the drive in antoher system, and
clear them that way. When your done there, just unmount it and run fsck
on it.
-----Original Message-----
From: Mikes work account [mailto:mrock@stewartsigns.com]
Sent: Thursday, December 12, 2002 1:42 PM
To: slug@nks.net
Subject: [SLUG] are you interested
You have probably read my rants about our firewall dying. Well, it is
possible that the logs( which have not been cleared in quite while) just
filled the available space on the drive and now the system will no
longer boot.
We are looking for someone who could access this drive and clear the
logs and run fsck for us. This is beyond my abilities or I would do it
myself.
I suspect the logs created the problem when I accessed the drive via
partition magic and found all the available space taken. Not even one
byte was available for use. I am assuming that what I am looking at is
correct of course. I believe the drive is BSD.
It is either that or the firewall designers deliberately filled all the
available space to prevent someone from adding code to the drive for
their own purposes.
If you are interested please contact me and I will attempt to fill in
the blank spaces in what is known about the drive and it's os.
Michael C. Rock
Systems Analyst
JM Stewart Corp
Registered Linux User # 287973
"The time has come the walrus said to speak of many things,,,"
"Christians give up what they cannot keep to gain what they cannot lose"
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:12:41 EDT