Checkpoint Commander is a multi-purpose software that enables file management, viewing, archiving, and security across different platforms. It is a powerful tool for efficiently managing large volumes of data across different systems.
Checkpoint Commander is a comprehensive cross-platform tool that offers file management, viewing, and archiving and security features. Users can encrypt archives using AES-CBC-HMAC-SHA1, which is an added security measure. To use Checkpoint Commander, users must have root privileges and basic Linux system administration skills. This should include knowing how to do symlinks, change users, and make users. As for the Java2 runtime, the required version will be in the release notes of the product you're installing. Currently, Checkpoint requires version 1.4.2 or above. At this time, Sun implementation is the preferred choice.
The application distribution zip for Linux must be uncompressed into a specific directory, and users must have a GUI that is compatible with Java's AWT/Swing, such as X with a suitable window manager (e.g., IceWM or KDE). Alternatively, if the installation is onto a headless host that lacks a GUI, there is a separate procedure, but the user will need a "headful" Linux workstation to install Checkpoint.
Users can install Checkpoint by first changing to the directory where they unzipped the distribution zip from an xterm or similar (X must be running). Then, as the Checkpoint user (not root), users must run install.sh using the 'source' command. However, X access control can be tricky, and some configurations may not allow su sessions to launch graphical apps out of the box. Users can start X as the user they need to work as or modify X's permissions. Alternatively, if using KDE, users can execute "kdesu -u konsole" as the user who started X.
Limitations include the need to run browserset as the checkpoint user when installing Checkpoint as a server configuration and using only CPC.
The latest release features an improved installer and an improved audio player, better handling of folder loop-around, and performance improvements. Additionally, users can now find files or folders that report the total number and size of matching files, with result sets now containing multiple copies of the same file. The latest release also includes better error reporting support and source build fixes.
The application distribution zip for Linux must be uncompressed into a specific directory, and users must have a GUI that is compatible with Java's AWT/Swing, such as X with a suitable window manager (e.g., IceWM or KDE). Alternatively, if the installation is onto a headless host that lacks a GUI, there is a separate procedure, but the user will need a "headful" Linux workstation to install Checkpoint.
Users can install Checkpoint by first changing to the directory where they unzipped the distribution zip from an xterm or similar (X must be running). Then, as the Checkpoint user (not root), users must run install.sh using the 'source' command. However, X access control can be tricky, and some configurations may not allow su sessions to launch graphical apps out of the box. Users can start X as the user they need to work as or modify X's permissions. Alternatively, if using KDE, users can execute "kdesu -u konsole" as the user who started X.
Limitations include the need to run browserset as the checkpoint user when installing Checkpoint as a server configuration and using only CPC.
The latest release features an improved installer and an improved audio player, better handling of folder loop-around, and performance improvements. Additionally, users can now find files or folders that report the total number and size of matching files, with result sets now containing multiple copies of the same file. The latest release also includes better error reporting support and source build fixes.
What's New
Version 6.1.0: N/A