TSURUGI

Many special and hidden features have been implemented in Tsurugi Linux OS:

• A Write Blocker system has been enforced at kernel level to avoid device write access and integrity alteration

• Default configuration protection to prevent settings changes, potentially due to future updates, each time a user session starts, all values about device automount, device autorun and system hibernation options are put with default customized values

• Each time the system boot, a cleaner script (tsurugi_cleaner) runs to stop and disable services that have been started because of new updates. This feature has been designed to limit memory waste

• In live mode, during the boot phase, it's possible to disable specific graphic drivers in case of visualization problems or potential crashes

• OSINT Profile Switcher (profile_switcher_tsurugi) it's a feature that allows to quickly switch from DFIR to OSINT profile
The difference is that the Tsurugi menu became lighter because are kept only a few categories useful for OSINT activities. To easily differentiate the two profiles the default wallpaper also changes

• An hidden feature allows to reset all menus and wallpapers (DFIR and OSINT profiles) to default values
(command line: profile_switcher_tsurugi --default)

• To be able to easily customize the OSINT menu by yourself, an hidden feature allows to clone and replace the OSINT menus with the DFIR menus (command line: profile_switcher_tsurugi --rebuild)

• A graphical dashboard is available on desktop with many real time information (if needed it's possible to reset it by “Dashboard reset” button or “dashboard” command on Command Line Interface)

• A Mouse keys switch function has been added to easily move the mouse pointer with only the keypad if needed. The on/off button is available on the Desktop

• Automatic set HI-DPI zoom for high screen resolution with more than 2560 pixels. There is an option, inside graphics menu, where you can switch to the original screen resolution

• In some particular cases, it's possible to find faulty or incompatible hardware that generates huge quantity of error logs and so that, in live mode, saturates RAM. For this specific situation has been prepared a custom logrotate configuration, available clicking RAM saturation workaround button, that allows to work on this system despite this hardware problem