Suse/NovellThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Locked: This package is installed and should not be modified, especially not because of unresolved dependencies that other packages might have or get. Use this status for third-party packages that should not be overwritten by newer versions that may come with the distribution.
This has nothing to do with RPM, it's a setting of the package manager (yast) and can only be set through it. You can see the locked files when you select "installation summary" as a filter in software management.
That will happen if you install a package using the rpm command instead of using yast.
If you downloaded media related packages from a packman site, the package versions don't match the SuSE versions of the same packages. So they are locked to prevent a SuSE update from replacing these packages during an update.
If you have a packman repo added as an installation source, you can use "Installation Source" as the filter list, then in the right hand side pane, right click and select "all in this list..." -> update if newer available.
That allows you to update the xine, mplayer, audacity, etc. packages from another repo, such as packman.
If you simply installed a SuSE package using rpm, you could unlock it if you wanted.
If you select installation summary, you can list just the locked packages.