sed means any non-linux person can copy/paste those two lines and do it safely.
Yep. Notably, GNU '
sed -i' –– the one used in the Rigol –– uses the safe modification pattern, where the output is saved to a new file in the same directory under name starting with
.sed, then closed, and if successful thus far, hard-linked over the old file. In all inode-based filesystems, this is the correct, safe pattern. (The only thing one
might ask is for an option to do a
fsync() after closing the new file before the hardlinking.)
For non-Linux/non-command line users, I recommend
nano (
nano-editor.org) for modifying files by hand. It is controlled via Ctrl+
Key, and the main commands shown at the bottom of the screen, with
Ctrl represented by
^ as is common in Unix/POSIX-land. If the distro contains a full installation, it even has syntax highlighting. It's no vi or emacs, but it is simpler, more lightweight, and newbie-frendly: a ten second explanation suffices to get users going (^ = Ctrl key, commands are Ctrl+
key, press Ctrl+G for help). However, I do not know whether it is included in the Rigol installation.