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.

Yes, ok. But when I install this package it also writes files to, for example, /usr/bin . There are also other files there, still this warning is not displayed there. It's not a big deal, just curious.

The difference is whether something is put in some existing directory, e.g. a link in /usr/local/bin/, or if the whole directory was created by the package (like /usr/local/appname/ ).
In the first case the files are deleted. In the second case, it want's to delete the whole directory.

The package likely included a create directive for /usr/share/man/man6, so that the directory would be created if it wasn't already there. If such an instruction isn't there, then the files for that directory likely wouldn't be copied.

The difference between that directory and something like /usr/bin is that /usr/bin is created by one of the aaa packages and it's impossible not to have it.

Ah, yes, I see.
Stille a question about this topic: if I remove this package, and I get this warning,
then I should check /var/log/packages?
Do a grep or similar to see if the files that are new, are from another package or generated by the application that was removed?

As the directory is a man directory in this case,
I think ls /usr/share/man/man6 will give you
a hint about what software install bring these
man pages, also section 6 of man is the game
man page section