dazuko-help
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dazuko-help] Failure and Success


From: scott092707
Subject: [Dazuko-help] Failure and Success
Date: Thu, 08 Apr 2010 14:55:01 -0400

Well, the combination of adding "dazukofs"  to /etc/modules, and an entry in the /etc/fstab file seems to
have done the trick - DazukoFS is loaded, and AVGuard finds it and runs in on-access mode.

However, at first there was a problem...

my entry in /etc/fstab was
/home  /home  dazukofs  defaults  0  0
as the README file suggests, (except naturally for which directory to watch)
but when I did so, Linux did not fully boot.  It first said it could not update ICEauthority file
(/home/scott/.ICEauthority).  Then a config server ...gconf-sanity-check-2 failed with code 256,
and finally Nautilus could not create /home/scott/Desktop, and  /home/scott/.nautilus.
I was left with a completely blank (but lovely Karmic orange) screen.  I tried many combinations of function keys to get a terminal (not remembering how), but was forced to press my computer's reset button, and then booted into recovery mode.

After much thinking and trying, I did the mount command with -haT options, and found that my /home partition had no entry except for dazukofs - and appeared to be based at the same point as /, as the disk space used and free exactly matched that for /, and not the values that should have been for the separate partition.
It seemed obvious that the system could not find or get access to the /home partition.

After learning a bit about how to use ed, I changed  /home  /home  to  /home/scott  /home/scott  and rebooted.
Success.  Full boot, and AVGuard functioned.  Separate mount listings for /home and /home/scott, with correct values.

I don't know if the problem was that /home was the "root" of a separate partition, or that the /etc/fstab line options should have been different (I honestly do not know what "0  0" accomplishes, and "defaults" seems to result in rw - maybe other options should have been added.  I also do not know why the directory needs to be listed twice: the implication is that the two entries can be different, but what that means I have no clue...)

Now all I have to do is find a way to have a window pop up when a virus is discovered - at the moment, I have to look at the log files...

-Scott Jacobs



reply via email to

[Prev in Thread] Current Thread [Next in Thread]