Hi Reuben, Thanks for all those bugs, I have fixed them already locally.
I finally got you, you forgot a ")" on the 2nd paragraph you quote here :) I am not really happy with this text: "Step 3 is mandatory, because the init.d script modifies the FSH before most of the processes start running." This is my proposal: "Step 3 is mandatory, because the init.d script modifies the FSH before most of the processes start running. This means some processes have some open files on the tmpfs, and you cannot safely unmount that tmpfs. " Here is my propsal: <start> If you want to enable this package you only have to do three steps: 1) create the directory /ram 2) modify the value ENABLED in /etc/default/flashybrid 3) reboot Step 3 is mandatory, because the init.d script modifies the FSH before most of the processes start running. This means some processes have some open files on the tmpfs, and you cannot safely unmount that tmpfs. To modify any configuration you need only to modify the configuration files, and reboot. Currently there is no alternative alternative to rebooting, since I have not found a way to move the move the open file handles from one filesystem (the tmpfs) into another (your real flash or HD). If you want to remove this package, you should first disable it, reboot the machine, and ONLY WHEN THE MACHINE HAS BEEN REBOOTED WITHOUT FLASHYBRID RUNNING, remove the package itself. If you do not to do it this way, you can potentially loose data (things like configuration files in /etc/ will not get synced to the real drive, stay only in the tmpfs and lost on reboot). You cannot restart this "service", since some file descriptors may open on the tmpfs. The reload and restart actions are NULL, and I only put them to keep lintain happy about LSB. </start> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
