En Fri, Jun 30, 2000 at 02:10:06PM +0800, Ronneil Camara escribio:
#_
#_ I have encountered this before. Some of my FSCKing are successful and some
#_ are not.
#_
#_ Anyways, I have a case also wherein nagkamali ako ng response sa mga tanong
#_ along the way.
#_ What happened is that, my linux didn't boot anymore. I tried creating a
#_ bootdisk to force it to
#_ boot from a specific partition. Nothing happened pa rin. What I did is I
#_ reinstalled pero ibang
#_ harddisk. I mounted the old harddisk to find out what really happened. I
#_ found out that the data was moved to /lost&found and nothing on the root
#_ directory.
This happend to me before, nag brownout, nagkamali ako ng sagot, nabura ang
10MB+ na Blackdown JDK na dinownload ko. Pagkatapos kong umiyak, I added
this in my crontab:
# run-parts
* * * * * root /bin/sync
Since then, pag mag brownout very minimal lang ang corrections ng e2fsck, no
need for human intervention in fsck'ng <-this does not sound right ;-> I'm
just not sure if there is a performance hit.
--
Juan Miguel Cacho [EMAIL PROTECTED] �
Philippines [EMAIL PROTECTED]
...the poor count their blessings, the affluent count their calories.
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
