I recently bought a PlayStation 3 80Gb. When I tried to install Yellow Dog Linux (YDL) on the PlayStation, I came across a message saying something like:

The partition table on device PS3DA was unreadable.

It also warned me that it would destroy all the data on the drive.

I didn’t like the idea of installing and updating all those games again, so I googled for this warning. I found out that YDL doesn’t have access to the entire disk, but only to the part it is allowed to by the PlayStation Firmware. So the only data it could destroy, was the data on the partition which I had created in the PlayStation 3 menu. This means it doesn’t destroy all data on the disk, but only on the empty partition, where no data is stored.

After the installation and booting into the GameOS, it seemed all my savegames and gamedata was still available. So no worries when you come across the warning I described above, your data will not be lost.

You still might want to backup your savegames before installing YDL, you never know what could happen…

To get Gentoo Linux to boot faster, you can disable unnessicary services (with rc-update).

But Gentoo also provides some exceptional rc scripts. These scripts allow parrallel loading of services. The result is a system which boots much faster. To enable the parallel startup of services, add or change the following line in the file /etc/conf.d/rc:

RC_PARALLEL_STARTUP="YES"

Now, when you boot your Gentoo distro, it will be ready at a glance!

To scan the current folder, with it’s underlaying folders,  use the following command (only when clamav is installed):

clamscan --log=$HOME/clamscan.log --quiet --recursive

In your home directory, the file ‘clamscan.log’ will appear. You may execute the following command to view the (filtered) results:

grep -v "Empty\|Scanning\|WARNING:\|Excluded" $HOME/clamscan.log

If the memory is very full (on Linux), you may execute the following command:

sync; echo 3 > /proc/sys/vm/drop_caches

All the caches are cleared now. Your system may respond a bit slower now, while the caches are being refilled.

To start a ‘fsck’ (for Windows users: a ‘checkdisk’ for Linux), you may execute the following command in your shell:

touch /forcefsck

fsck will run at next boot.

This command creates a file called ‘forcefsck’ in the root folder (‘/’). At boot time, fsck checks whether this file exists. When it does, fsck checks the harddisk.