How to Install and Uninstall picocom.x86_64 Package on Red Hat Enterprise Linux 8 (RHEL 8)

Last updated: October 08,2024

1. Install "picocom.x86_64" package

This tutorial shows how to install picocom.x86_64 on Red Hat Enterprise Linux 8 (RHEL 8)


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                picocom.x86_64
            
                    
    
    Copied

2. Uninstall "picocom.x86_64" package

This tutorial shows how to uninstall picocom.x86_64 on Red Hat Enterprise Linux 8 (RHEL 8):


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                picocom.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the picocom.x86_64 package on Red Hat Enterprise Linux 8 (RHEL 8)

Last metadata expiration check: 0:09:14 ago on Mon Feb 26 15:59:38 2024.
Available Packages
Name : picocom
Version : 3.1
Release : 9.el8
Architecture : x86_64
Size : 61 k
Source : picocom-3.1-9.el8.src.rpm
Repository : epel
Summary : Minimal serial communications program
URL : https://github.com/npat-efault/picocom
License : GPLv2+
Description : As its name suggests, [picocom] is a minimal dumb-terminal emulation
: program. It is, in principle, very much like minicom, only it's "pico"
: instead of "mini"! It was designed to serve as a simple, manual, modem
: configuration, testing, and debugging tool. It has also served (quite
: well) as a low-tech "terminal-window" to allow operator intervention
: in PPP connection scripts (something like the ms-windows "open
: terminal window before / after dialing" feature). It could also prove
: useful in many other similar tasks. It is ideal for embedded systems
: since its memory footprint is minimal (less than 20K, when
: stripped).