How to Install and Uninstall fstrm Package on openSUSE Leap

Last updated: May 19,2024

1. Install "fstrm" package

Please follow the instructions below to install fstrm on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                fstrm
            
                    
    
    Copied

2. Uninstall "fstrm" package

In this section, we are going to explain the necessary steps to uninstall fstrm on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                fstrm
            
                    
    
    Copied

3. Information about the fstrm package on openSUSE Leap

Information for package fstrm:
------------------------------
Repository : Update repository with updates from SUSE Linux Enterprise 15
Name : fstrm
Version : 0.6.1-150300.9.5.1
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 115.4 KiB
Installed : No
Status : not installed
Source package : fstrm-0.6.1-150300.9.5.1.src
Upstream URL : https://github.com/farsightsec/fstrm
Summary : Frame Streams implementation in C
Description :
fstrm is a C implementation of Frame Streams that includes a lockless
circular queue implementation and exposes library interfaces for
setting up a dedicated Frame Streams I/O thread and asynchronously
submitting data frames for transport from worker threads.
Frame Streams is a protocol that allows for the transport of
arbitrarily encoded data payload sequences with just 4 bytes per data
frame. Frame Streams does not specify an encoding format for frames
and can be used with data serialization formats that produces byte
sequences, such as Protocol Buffers, XML, JSON, MessagePack, YAML,
etc. Frame Streams can be used both as a streaming transport over a
reliable byte stream socket (TCP, AF_UNIX, TLS, etc.) for data in
motion, as well as a file format for data at rest. A "Content Type"
header identifies the type of payload being carried over an
individual Frame Stream and allows cooperating programs to determine
how to interpret a given sequence of data payloads.