Ways to uninstall software

本文介绍了两种卸载Wine的方法:一是通过yum命令移除所有与Wine相关的rpm包及其依赖;二是利用rpm命令精确指定rpm包名称进行卸载,并在没有依赖的情况下彻底删除。第一种方法适用于不需要保留任何Wine相关组件的情况,第二种则更注重于精确控制。

1. yum remove wine-*

{

No need for precise rpm name

Uninstall all rpm include dependencies

}


2. rpm -e wine.x86_64.rpm

{

Precise rpm name needed

Alert dependencies without uninstall; uninstall when there is no dependency.

}

[R] ssc -- Install and uninstall packages from SSC (View complete PDF manual entry) Syntax Summary of packages most recently added or updated at SSC ssc new [, saving(filename[, replace]) type] Summary of most popular packages at SSC ssc hot [, n(#) author(name)] Describe a specified package at SSC ssc describe { pkgname | letter } [, saving(filename[, replace])] Install a specified package from SSC ssc install pkgname [, all replace] Uninstall from your computer a previously installed package from SSC ssc uninstall pkgname Type a specific file stored at SSC ssc type filename [, asis] Copy a specific file from SSC to your computer ssc copy filename [, plus personal replace public binary] where letter in ssc describe is a-z or _. Description ssc works with packages (and files) from the Statistical Software Components (SSC) Archive, which is often called the Boston College Archive and is provided by http://www.repec.org. The SSC has become the premier Stata download site for community-contributed software on the web. ssc provides a convenient interface to the resources available there. For example, on Statalist, users will often write The program can be found by typing ssc install newprogramname. Typing that would load everything associated with newprogramname, including the help files. If you are searching for what is available, type ssc new and ssc hot, and see [R] search. search searches the SSC and other places, too. search provides a GUI interface from which programs can be installed, including the programs at the SSC Archive. You can uninstall particular packages by using ssc uninstall. For the packages that you keep, see [R] ado update for an automated way of keeping those packages up to date. Links to PDF documentation Quick start Remarks and examples The above sections are not included in this help file. Command overview ssc new summarizes the packages made available or updated recently. Output is presented in the Stata Viewer, and from there you may click to find out more about individual packages or to install them. ssc hot lists the most popular packages -- popular based on a moving average of the number of downloads in the past three months. By default, 10 packages are listed. ssc describe pkgname describes, but does not install, the specified package. Use search to find packages; see [R] search. If you know the package name but do not know the exact spelling, type ssc describe followed by one letter, a-z or _ (underscore), to list all the packages starting with that letter. ssc install pkgname installs the specified package. You do not have to describe a package before installing it. (You may also install a package by using net install; see [R] net.) ssc uninstall pkgname removes the previously installed package from your computer. It does not matter how the package was installed. (ssc uninstall is a synonym for ado uninstall, so either may be used to uninstall any package.) ssc type filename types a specific file stored at SSC. ssc cat is a synonym for ssc type, which may appeal to those familiar with Unix. ssc copy filename copies a specific file stored at SSC to your computer. By default, the file is copied to the current directory, but you can use options to change this. ssc copy is a rarely used alternative to ssc install ..., all. ssc cp is a synonym for ssc copy. Options for use with ssc new saving(filename[, replace]) specifies that the "what's new" summary be saved in filename. If filename is specified without a suffix, filename.smcl is assumed. If saving() is not specified, saving(ssc_result.smcl) is assumed. type specifies that the "what's new" results be displayed in the Results window rather than in the Viewer. Options for use with ssc hot n(#) specifies the number of packages to list; n(10) is the default. Specify n(.) to list all packages in order of popularity. author(name) lists the 10 most popular packages by the specified author. If n(#) is also specified, the top # packages are listed. Option for use with ssc describe saving(filename[, replace]) specifies that, in addition to the description's being displayed on your screen, it be saved in the specified file. If filename is specified without an extension, .smcl will be assumed, and the file will be saved as a SMCL file. If filename is specified with an extension, no default extension is added. If the extension is .log, the file will be stored as a text file. If replace is specified, filename is replaced if it already exists. Options for use with ssc install all specifies that any ancillary files associated with the package be downloaded to your current directory, in addition to the program and help files being installed. Ancillary files are files that do not end in .ado or .sthlp and typically contain datasets or examples of the use of the new command. You can find out which files are associated with the package by typing ssc describe pkgname before or after installing. If you install without using the all option and then want the ancillary files, you can ssc install again. replace specifies that any files being downloaded that already exist on your computer be replaced by the downloaded files. If replace is not specified and any files already exist, none of the files from the package is downloaded or installed. It is better not to specify the replace option and wait to see if there is a problem. If there is a problem, it is usually better to uninstall the old package by using ssc uninstall or ado uninstall (which are, in fact, the same command). Option for use with ssc type asis affects how files with the suffixes .smcl and .sthlp are displayed. The default is to interpret SMCL directives the file might contain. asis specifies that the file be displayed in raw, uninterpreted form. Options for use with ssc copy plus specifies that the file be copied to the PLUS directory, the directory where community-contributed additions are installed. Typing sysdir will display the identity of the PLUS directory on your computer. personal specifies that the file be copied to your PERSONAL directory as reported by sysdir. If neither plus nor personal is specified, the default is to copy the file to the current directory. replace specifies that, if the file already exists on your computer, the new file replace it. public specifies that the new file be made readable by everyone; otherwise, the file will be created according to the default permission you have set with your operating system. binary specifies that the file being copied is a binary file and that it is to be copied as is. The default is to assume that the file is a text file and change the end-of-line characters to those appropriate for your computer/operating system. Remarks Users can add new features to Stata, and some users choose to make new features that they have written available to others via the web. The files that comprise a new feature are called a package, and a package usually consists of one or more ado-files and help files. The net command makes it reasonably easy to install and uninstall packages regardless of where they are on the web. One site, the SSC, has become particularly popular as a repository for additions to Stata. Command ssc is an easier to use version of net designed especially for the SSC. Many packages are available at the SSC. Packages are named, such as oaxaca, estout, or egenmore. At SSC, capitalization is not significant, so Oaxaca, ESTOUT, and EGENmore are ways of writing the same package names. When you type . ssc install oaxaca the files associated with the package are downloaded and installed on your computer. Package names usually correspond to the names of the commands being added to Stata, so one would expect that installing the package oaxaca will add command oaxaca to Stata on your computer, and expect that typing help oaxaca will provide the documentation. That is the situation here, but that is not always so. Before or after installing a package, type ssc describe pkgname to obtain the details. Examples Describe most recently added or updated packages at SSC . ssc new Describe the most popular packages at SSC . ssc hot Describe the package oaxaca . ssc describe oaxaca Describe the package oaxaca and save the description to the file oaxaca.log . ssc describe oaxaca, saving(oaxaca.log) List all packages, along with a brief description, that begin with the letter o . ssc describe o Same as above, but also save the listing to the file o.index . ssc describe o, saving(o.index) Install package oaxaca . ssc install oaxaca Uninstall previously installed package oaxaca . ssc uninstall oaxaca Type file whitetst.hlp that is stored at SSC . ssc type whitetst.hlp Copy file whitetst.ado from SSC to your computer . ssc copy whitetst.ado
11-08
Performance Endpoint for Linux (32-bit and 64-bit) File README Version 7.30 SP1 Copyright (C) 2003-2013 Ixia. All rights reserved. Ixia 26601 W. Agoura Road Calabasas, CA 91302 U.S.A. Web: www.ixiacom.com Phone: +1 818 871-1800 or + 1 877 FOR IXIA Fax: +1 818 871 1805 General information: Email: info@ixiacom.com Technical support: Email: support@ixiacom.com Thanks! We appreciate your interest in our software. We keep seeking ways to improve it; we welcome your feedback and suggestions. We continue to enhance and expand our Web site -- come and visit us. The latest versions of the endpoints are always available for free at http://www.ixiacom.com/support/endpoint_library/ Note that the Ixia Performance Endpoints have not been tested with NetIQ applications and may not function properly with NetIQ applications. Linux kernel 2.4.20 We've tested with packages that implement Linux kernel 2.4.20. We have not tested this version of Performance Endpoint with earlier versions of the Linux kernel. Only TCP and UDP/RTP support The Performance Endpoint for Linux uses the Sockets interface to the TCP/IP support shipped with Linux. IPX, SPX, or other network protocols are not supported in this version. For IPv6 support, kernel 2.4.18-3 or better is required. Here's what you need to run the endpoint program with Linux: - A computer capable of running Linux well. We recommend a CPU such as Intel Pentium III or better. For the 64-bit (x64) version of the endpoint you will need an AMD64/EM64T compatible CPU, such as AMD Opteron or an Intel Xeon with support for EM64T technology. For the 64-bit versions of the endpoint the corresponding 64-bit version of Linux is also required. - 64 MBytes of RAM. The total RAM requirement depends on RAM usage of the underlying protocol stack and the number of concurrent endpoint pairs. For tests involving over one hundred connections through a single endpoint, additional memory may be required. - A hard disk with at least 8 MBytes of space available. - Linux kernel 2.4.20 or better. Older versions of the Linux kernel may not support IPv6 properly. TAR-Based Endpoint Installation for Linux ------------------------------------------------------------------- Use the TAR-based installation if you are installing the endpoint on any Linux platform other than Red Hat (32-bit) or SuSE (64-bit). First, make sure that you are logged in as a "root" user. Also remember all commands and parameters discussed here are case-sensitive. Use the combination of uppercase and lowercase letters as shown below (for all the file names, "M" represents the major version and "m" represents the minor version). The following instructions describe how to install the endpoint on a computer with a CD-ROM drive. Put the CD-ROM in your CD-ROM drive. If you want to install the 64-bit version of the endpoint, replace the name of the archives (pelnx_Mm.tar.gz and pelnx_Mm.tar) from the following instructions with pelinux_amd64_Mm.tar.gz Enter the following commands, assuming your CD-ROM drive device name is /dev/cdrom and you are able to create a temporary directory named cdrom: mkdir /cdrom mount /dev/cdrom /cdrom The CD-ROM contains an archive of the endpoint package. First use the RM command to ensure a clean temporary install directory. Then use the TAR command to extract the archive contents from the CD-ROM: cd /tmp rm -fr temp tar -zxvf ./pelnx_Mm.tar.gz Next, run the endpoint's installation script to install the endpoint: ./endpoint.install The license agreement is shown, presented with the "more" command. Press the space bar until the end of the agreement is displayed. You are asked whether you accept the terms and conditions of the agreement. If you do, enter "accept_license" and press return. After the installation is complete, use the UMOUNT command to unmount the file system from the CD-ROM: umount /cdrom During installation, you will see several status messages. Pay close attention to the output. When the installation is successful, you see the message "Installation of endpoint was successful." The installation script and temporary directory are not removed automatically if the installation is successful. If you need the disk space after installing the endpoint, you may delete the temporary directory and installation script. Unattended Installation for TAR-Based Linux You can install the endpoint silently, that is, without providing any additional user input. Complete the steps, as described above, through the TAR command. Next, run the endpoint's installation, adding the "accept_license" parameter: ./endpoint.install accept_license Removing the TAR-Based Endpoint Package (Uninstall) You must be logged in as the root user to remove the endpoint package. If you need to remove the endpoint package from your hard disk, first stop the endpoint program (if running). Enter the following command: /usr/local/Ixia/endpoint -k Use the following command to remove the endpoint: /usr/local/Ixia/endpoint.remove If the removal is successful, you will see the following: "Removal of endpoint was successful." This removes the files from /usr/local/Ixia, except for any files added to this directory that were not present at install, such as the endpoint.ini file, but does not delete the directory. The remove program does not automatically delete files added to the directory that you may need if you reinstall the product. RPM-Based Endpoint Installation for Linux ------------------------------------------------------------------- Use the RPM-based installation if you are installing the endpoint on Red Hat (32-bit) or SuSE (64-bit). For installation, first make sure that you are logged in as a "root" user. Also remember all commands and parameters discussed here are case-sensitive. Use the combination of uppercase and lowercase letters as shown below (for all the file names, "M" represents the major version and "m" represents the minor version). The following instructions describe how to install the endpoint on a computer with a CD-ROM drive. Put the CD-ROM in your CD-ROM drive. If you want to install the 64-bit version of the endpoint, replace the name of the RPM file (pelnx_Mm.rpm) from the following instructions with pelinux_amd64_Mm.rpm Enter the following commands, assuming your CD-ROM drive device name is /dev/cdrom and you are able to create a temporary directory named cdrom: mkdir /cdrom mount /dev/cdrom /cdrom Copy the pelnx_Mm.rpm file from the CD-ROM drive to a local directory (for example, tmp). cp /cdrom/endpoint/linux/pelnx_Mm.rpm /tmp For RPM, use the RPM command to install the endpoint: rpm -Uvh /tmp/pelnx_Mm.rpm After the installation is complete, use the UMOUNT command to unmount the file system from the CD-ROM: umount /cdrom During installation, you will see several status messages. Pay close attention to the output. When the installation is successful, you see the message "Installation of endpoint was successful." Removing the RPM-Based Endpoint Package (Uninstall) You must be logged in as the root user to remove the endpoint package. If you need to remove the endpoint package from your hard disk, first stop the endpoint program (if running). Enter the following command: /usr/local/Ixia/endpoint -k Use the following command to remove the endpoint (you must be logged in as root to run this program): rpm -e endpoint If the removal is successful, you will see the following: "Removal of endpoint was successful." This removes the files from /usr/local/Ixia, except for any files that were added to this directory that were not present at install, such as the endpoint.ini file, and does not delete the directory. The remove program does not automatically delete files added to the directory that you may need if you reinstall the product. What We Do During Installation Here is what happens during the installation steps. The endpoint is installed into the directory /usr/local/Ixia. A directory is created with the following contents: - the executable programs. - the README file. - various install and uninstall programs. - the directory cmpfiles. This directory contains files with the .cmp file extension. These are files containing data of different types, such as typical text or binary data. These files are used by the endpoint as data on SEND commands. The different data types can be used to vary the data compression performance of your network hardware and software. - the file endpoint.ini. Our software ends any copy of the endpoint program currently running and starts a copy of the newly-installed endpoint. You can run tests immediately, without a reboot. Our software displays information on how to update your system to have the endpoint start automatically upon reboot. No changes are made to the PATH environment variable of the root user. *IxChariot is a registered trademark of Ixia. United States Patent Numbers 5,838,919, 5,881,237, 5,937,165, and 6,061,725. Other patents pending.啥意思
10-16
【无线传感器】使用 MATLAB和 XBee连续监控温度传感器无线网络研究(Matlab代码实现)内容概要:本文围绕使用MATLAB和XBee技术实现温度传感器无线网络的连续监控展开研究,介绍了如何构建无线传感网络系统,并利用MATLAB进行数据采集、处理与可视化分析。系统通过XBee模块实现传感器节点间的无线通信,实时传输温度数据至主机,MATLAB负责接收并处理数据,实现对环境温度的动态监测。文中详细阐述了硬件连接、通信协议配置、数据解析及软件编程实现过程,并提供了完整的MATLAB代码示例,便于读者复现和应用。该方案具有良好的扩展性和实用性,适用于远程环境监测场景。; 适合人群:具备一定MATLAB编程基础和无线通信基础知识的高校学生、科研人员及工程技术人员,尤其适合从事物联网、传感器网络相关项目开发的初学者与中级开发者。; 使用场景及目标:①实现基于XBee的无线温度传感网络搭建;②掌握MATLAB与无线模块的数据通信方法;③完成实时数据采集、处理与可视化;④为环境监测、工业测控等实际应用场景提供技术参考。; 阅读建议:建议读者结合文中提供的MATLAB代码与硬件连接图进行实践操作,先从简单的点对点通信入手,逐步扩展到多节点网络,同时可进一步探索数据滤波、异常检测、远程报警等功能的集成。
内容概要:本文系统讲解了边缘AI模型部署与优化的完整流程,涵盖核心挑战(算力、功耗、实时性、资源限制)与设计原则,详细对比主流边缘AI芯片平台(如ESP32-S3、RK3588、Jetson系列、Coral等)的性能参数与适用场景,并以RK3588部署YOLOv8为例,演示从PyTorch模型导出、ONNX转换、RKNN量化到Tengine推理的全流程。文章重点介绍多维度优化策略,包括模型轻量化(结构选择、输入尺寸调整)、量化(INT8/FP16)、剪枝与蒸馏、算子融合、批处理、硬件加速预处理及DVFS动态调频等,显著提升帧率并降低功耗。通过三个实战案例验证优化效果,最后提供常见问题解决方案与未来技术趋势。; 适合人群:具备一定AI模型开发经验的工程师,尤其是从事边缘计算、嵌入式AI、计算机视觉应用研发的技术人员,工作年限建议1-5年;熟悉Python、C++及深度学习框架(如PyTorch、TensorFlow)者更佳。; 使用场景及目标:①在资源受限的边缘设备上高效部署AI模型;②实现高帧率与低功耗的双重优化目标;③掌握从芯片选型、模型转换到系统级调优的全链路能力;④解决实际部署中的精度损失、内存溢出、NPU利用率低等问题。; 阅读建议:建议结合文中提供的代码实例与工具链(如RKNN Toolkit、Tengine、TensorRT)动手实践,重点关注量化校准、模型压缩与硬件协同优化环节,同时参考选型表格匹配具体应用场景,并利用功耗监测工具进行闭环调优。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值