Try: run a command and inspect its effects before changing your live system (github.com)

Article summary

The article introduces a Linux command called 'try' that allows users to run a command and inspect its effects before changing their live system. It uses Linux's namespaces and the overlayfs union filesystem to create a semisolate environment. The 'try' command can be installed in various ways, including cloning the repository or using a source distribution. It provides features like committing changes, exploring overlays, and summarizing changes.

Main themes

• Linux command-line tools
• System management
• Customization vs portability
• NixOS and containerization
• Emacs and tool customization
• System administration best practices

What commenters say

• Some users appreciate the idea of 'try' and its potential to improve system management.
• Others note that similar functionality can be achieved with existing tools like NixOS or containers.
• There is a discussion about the trade-offs between customization and portability of tools across different systems.
• The complexity and steep learning curve of certain tools, like NixOS or Emacs, can be a barrier to adoption.
• Some users value the ability to customize their tools and environments, while others prioritize simplicity and ease of use.
• The idea of carrying customized configurations across different systems is seen as desirable, but challenging to implement in practice.