Tweet
Hi,
I am using BitLinux V.2 (1006) on a SLAX USB, and I see that even though the test configuration tells me it is testing (/dev/hdc1) [/mnt/hdc1] it is actually writing/reading the test files to /root/, which is a ramdisk location.
It fills up fast, and if I started BitLinux from my test script it will exit with a message that the process was killed.
If I start BitLinux manually it will tell me that there is no more space, but BitLinux will not exit, just report errors in infowindow and test log.
The only edits I have done to the script file provided with BitLinux is I added some arguments ( -M -C -R ).
Is this a known bug?
I am using BitLinux V.2 (1006) on a SLAX USB, and I see that even though the test configuration tells me it is testing (/dev/hdc1) [/mnt/hdc1] it is actually writing/reading the test files to /root/, which is a ramdisk location.
It fills up fast, and if I started BitLinux from my test script it will exit with a message that the process was killed.
If I start BitLinux manually it will tell me that there is no more space, but BitLinux will not exit, just report errors in infowindow and test log.
The only edits I have done to the script file provided with BitLinux is I added some arguments ( -M -C -R ).
Is this a known bug?
Comment