It's funny how all of your specific examples are already solved, many years ago.
- "fsck" is not longer required with journalling filesystems.
- For faster boot, there is "ureadahead" which requests the block from the disk in the right order -- so time to start up the system with 1GB of memory used is roughly the same as read that 1GB from the disk drive.
- For "200 fonts", there is "fc-cache" tool which keeps the font cache -- and you only run it when a new font is installed.
Comments
It's funny how all of your specific examples are already solved, many years ago.
- "fsck" is not longer required with journalling filesystems.
- For faster boot, there is "ureadahead" which requests the block from the disk in the right order -- so time to start up the system with 1GB of memory used is roughly the same as read that 1GB from the disk drive.
- For "200 fonts", there is "fc-cache" tool which keeps the font cache -- and you only run it when a new font is installed.