RE: [MiNT] MiNTLib 0.52.3b

[darkchyld@pcc-uky.campuscwix.net (Ronald J. Hall)]

On Sat, 7 Aug 1999 03:50:56 +0200 (CEST), Maurits van de Kamp wrote:

MvdK ->Yes, it's luck that you apparantly never had errors to fix. Because if you
MvdK ->do, fsck won't actually fix them. It will, but due to the open files,
MvdK ->fsck's work will disappear immediately. Once you notice fsck keeps
MvdK ->reporting the same errors on each boot and claiming they're "fixed", it's
MvdK ->time to move the fsck-call out of rc.whatever and into mint.cnf. fsck
MvdK ->doesn't warn about not being able to sync or lock the device for nothing,
MvdK ->even though it's "ignored". :)
MvdK ->
MvdK ->So yes it's harmless, it's just useless as well.

  Hmm...okay-I'm not expert so slam me if necessary, but I've had fsck
  not fix a reported problem, after running it, and multiple reboots. What
  I was told to do was boot immediately into Bash, and then run it with
  nothing else inbetween. Seems that some caches interfere with fsck, so
  that when you run it "clean" it will do its job. Worked for me anyways.
  
  I even have these lines in MINT.CNF (to remind myself):
  
  INIT=c:\multitos\init.prg
  # Use the line below when running fsck to avoid cache interference.
  # Don't forget that you have to type the path directly to fsck.....
  #INIT=u:\bin\bash

  If this has nothing whatsoever to do with what you are talking about
  then I plead ignorance/temporary insanity/(or like Jo Even)I'm drunk!
  
  <grin>

       __________________________________________________________________
      /               /   SysOp of the DarkForce! BBS   /               /\
     /    --T--      /   Phone 1-606-886-9014 Today!   /     /\        / /
    /  -A T A R I-  /   The Fuji -still- Lives...!!   /  Dark><Chyld  / /
   /      --G--    /   My ICQ # is 2 0 6 2 3 9 0 4   /       \/      / /
  /_______________/_______________/_________________/_______________/ /
  \_________________________________________________________________\/