I am using FC 4 and I am not extremely new, but I am very new to this problem and I cannot seem to find any help. So here goes! During my boot process, right before it starts to load my drivers and such, it says, "Load Booleans", then it gives me a warning saying, "Booleans user_ping no longer in policy!"

Other than my up2date not seeming to work automatically like it should, everything else seems to be fine. Of course, I am not a programmer and maybe that is a problem in itself, but I haven't had a need to be one as yet. So I hope someone can help me at least understand the boot warning and what I should or should not do about it.

PLEASE!

1. do not use up2date ... use yum (see www.fedorafaq.org), it is much much better and faster. You can remove the RH updates notification icon too.

2. the user_ping boolean is associated with SELinux policy ... try: /usr/sbin/sestatus
This should give you a hint - basically this thing was giving headaches in FC2-3 ...

If you disable SELinux the problem should go away.

As well as the fedora faq, you should see www.mjmwired.net for the FC4 installation notes there. (As well as other things.)

Thank you Simon. At least I know the booleans problem is something typical. However, is it something I can just ignore?

Anyway, now I have another problem and I am mentioning it here because I am not sure if it is somehow related or not and you sound exceptionally knowledgeable. I decided to use yum but a package "libksba.i386 0:0.9.12-1.fc4" that would not update in up2date causes yum update to not work. I did not think about it before because I was able to just bypass it with up2date, but in there I was told it was needed newpg 0.9.4. However, in yum I am told newpg >= 0.9.2 is needed by package gpgme0316. Example is below:
_____________________________________________________________
yum update
Setting up Update Process
Setting up repositories
freshrpms 100% |=========================| 951 B 00:00
livna 100% |=========================| 951 B 00:00
skype 100% |=========================| 951 B 00:00
extras 100% |=========================| 1.1 kB 00:00
updates-released 100% |=========================| 951 B 00:00
base 100% |=========================| 1.1 kB 00:00
Reading repository metadata in from local files
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package libksba.i386 0:0.9.12-1.fc4 set to be updated
---> Downloading header for livna-release to pack into transaction set.
livna-release-4-0.lvn.5.4 100% |=========================| 2.6 kB 00:00
---> Package livna-release.noarch 0:4-0.lvn.5.4 set to be updated
---> Package gnupg2.i386 0:1.9.18-6.fc4 set to be updated
--> Running transaction check
--> Processing Dependency: newpg >= 0.9.2 for package: gpgme0316
--> Finished Dependency Resolution
Error: Missing Dependency: newpg >= 0.9.2 is needed by package gpgme0316
_____________________________________________________________

Here is where I am lost! I originally had newpg, but it was update and replaced by gnupg2. The package gpgme0316 is being used by a yahoo clone that works almost exactly like the one in windows in that it has functional voice and video which gaim does not have yet.

Anyway, I reinstalled newpg but that does nothing and I imagine it is because gnupg2 is still there. While I do not know how to get rid of one package, I would still think I would cause more problems if I did that anyway. In any case, can you tell me what I should do? Have I somehow screwed everything? I hope not!

Did you disable SELinux?

For the yum issues: use the yum.conf from www.fedorafaq.org and then try your luck. You can exclude a package from yum using the --exclude <package> option. See the yum man page for more on the flags and options. The FAQ has lots of tips for you too.

You should get used to figuring stuff out for yourself - however, when you get advise from quite knowledgable folk - it is useful if your reply indicates that you followed it and what happened when you did.

Hi again Simon. I must be doing something wrong because nothing seems to be working. I just tried the --exclude <package> routine and as you can see below it failed. The primary.xml.gz just kept going.
______________________________________________________________
Setting up Update Process
Setting up repositories
livna 100% |=========================| 951 B 00:00
updates-released 100% |=========================| 951 B 00:00
extras 100% |=========================| 1.1 kB 00:00
base 100% |=========================| 1.1 kB 00:00
freshrpms 100% |=========================| 951 B 00:00
Reading repository metadata in from local files
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package bind.i386 24:9.3.1-10_FC4 set to be updated
---> Package glibc-headers.i386 0:2.3.5-10.3 set to be updated
---> Package bind-libs.i386 24:9.3.1-10_FC4 set to be updated
---> Package bind-chroot.i386 24:9.3.1-10_FC4 set to be updated
---> Package cvs.i386 0:1.11.19-9 set to be updated
---> Package bind-utils.i386 24:9.3.1-10_FC4 set to be updated
---> Package libksba.i386 0:0.9.12-1.fc4 set to be updated
---> Package gnupg2.i386 0:1.9.18-6.fc4 set to be updated
---> Package glibc-devel.i386 0:2.3.5-10.3 set to be updated
---> Package nscd.i386 0:2.3.5-10.3 set to be updated
---> Package glibc-common.i386 0:2.3.5-10.3 set to be updated
---> Package glibc.i686 0:2.3.5-10.3 set to be updated
--> Running transaction check
--> Processing Dependency: newpg >= 0.9.2 for package: gpgme0316
--> Finished Dependency Resolution
Error: Missing Dependency: newpg >= 0.9.2 is needed by package gpgme0316
[root@speedy gary]# yum update --exclude libksba.i386
Setting up Update Process
Setting up repositories
livna 100% |=========================| 951 B 00:00
updates-released 100% |=========================| 951 B 00:00
extras 100% |=========================| 1.1 kB 00:00
base 100% |=========================| 1.1 kB 00:00
freshrpms 100% |=========================| 951 B 00:00
Reading repository metadata in from local files
primary.xml.gz 100% |=========================| 354 kB 00:06
primary.xml.gz 100% |=========================| 344 kB 00:06
primary.xml.gz 100% |=========================| 354 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:06
primary.xml.gz 100% |=========================| 344 kB 00:05
primary.xml.gz 100% |=========================| 344 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:10
primary.xml.gz 100% |=========================| 354 kB 00:07
primary.xml.gz 100% |=========================| 354 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:06
primary.xml.gz 100% |=========================| 340 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:06
primary.xml.gz 100% |=========================| 354 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:06
primary.xml.gz 100% |=========================| 354 kB 00:06
primary.xml.gz 100% |=========================| 354 kB 00:05
primary.xml.gz 100% |=========================| 340 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:08
primary.xml.gz 100% |=========================| 344 kB 00:05
primary.xml.gz 100% |=========================| 344 kB 00:05
primary.xml.gz 100% |=========================| 344 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 01:04
primary.xml.gz 100% |=========================| 343 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 01:30
primary.xml.gz 100% |=========================| 340 kB 00:05
primary.xml.gz 100% |=========================| 340 kB 00:06
primary.xml.gz 100% |=========================| 354 kB 00:06
primary.xml.gz 100% |=========================| 344 kB 00:06
primary.xml.gz 100% |=========================| 354 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:06
primary.xml.gz 100% |=========================| 354 kB 00:07
primary.xml.gz 100% |=========================| 344 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:06
primary.xml.gz 100% |=========================| 354 kB 00:05
primary.xml.gz 100% |=========================| 354 kB 00:06
______________________________________________________________

I finaly said that is enough, killed yum, did a yum help and tried again but got the following;
______________________________________________________________


Usage: yum [options] < update | install | info | remove | list |
clean | provides | search | check-update | groupinstall |
groupupdate | grouplist | groupinfo | groupremove |
makecache | localinstall | shell >

Options:
-c [config file] - specify the config file to use
-e [error level] - set the error logging level
-d [debug level] - set the debugging level
-y - answer yes to all questions
-R [time in minutes] - set the max amount of time to randomly run in
-C run from cache only - do not update the cache
--installroot=[path] - set the install root (default '/')
--version - output the version of yum
--exclude=package to exclude
--disablerepo=repository id to disable (overrides config file)
--enablerepo=repository id to enable (overrides config file)

-h, --help - this screen

[root@speedy gary]# yum update --exclude=libksba
Setting up Update Process
Setting up repositories
livna 100% |=========================| 951 B 00:00
updates-released 100% |=========================| 951 B 00:00
extras 100% |=========================| 1.1 kB 00:00
base 100% |=========================| 1.1 kB 00:00
freshrpms 100% |=========================| 951 B 00:00
Reading repository metadata in from local files
Could not find update match for --exclude=libksba

did you disable SELinux?
did you use the yum.conf I suggested?
did you read the FAQ?

I do not even know what happened to my other message, because I wrote first to tell you that I got rid of Selinux and do not have the warning anymore. Then I went and read the fedora faq page and ran the yum.conf routine as stated below;
______________________________________________________________
Open a Terminal.
Become root.
Run these commands to remove your yum.conf file and replace it with a fresh one (Updated 29 July 2005):

cd /etc
rm -f yum.conf
wget http://www.fedorafaq.org/samples/yum.conf
Now, install my yum configuration (Updated 25 July 2005), using this command:

rpm -Uvh http://www.fedorafaq.org/yum
______________________________________________________________

Then this happened;
______________________________________________________________
Retrieving http://www.fedorafaq.org/yum
Preparing... ########################################### [100%]
file /etc/yum.repos.d/freshrpms.repo from install of yum-fedorafaq-4-2005.07.25a conflicts with file from package freshrpms-release-1.1-1.fc
______________________________________________________________

I even removed the freshrpms.repo to see what would happen and I got the same conflict message. So I wrote to you to thank you for the help I have been given in relation to the Selinux and to show you what happened otherwise.

I put the freshrpms.repo back since it didn't make a difference but I could not and cannot find anything in the fedorafaq page about my problem. So I then tried the exclude package routine as shown in the other message. As you can see in the other message yum sort of freaked out and then just did not recognize the command. Can you see anything I am missing or doing wrong?

try ... I think you need to remove this package first. (Have you, perhaps, installed something from freshrpms before?) Then repeat the attempt to set yum.conf ...

(or... yum remove <offending package>, following this discussion)

Excellent.
The faq assmes you're doing this from a fresh install ... which, if you find yourself hopelessly tied in knots, is what you do.

You can also get information from this yum faq at Duke University.

in this situation I did not attempt your suggestion yet.

"(or... yum remove <offending package>, following this discussion)"

First problem is the "discussion" link did not work. So I am paranoid of the "yum remove".

Second, the reason for my fear is that I tried a "yum remove" on my first install of fc4. The last time I was trying to get rid of Mozilla because I wanted to only have Opera. So I did a, yum remove mozilla and it went nuts and started removing every darn package or file it could find. I had to close the terminal but it was way too late. Hardly anything worked and I had to reinstall fc4. Does such a total removal only happen if a package is part of a larger group of packages or is it perhaps an error I made in the way I did it last time?

Should the remove option work for just one package as long as the spaces and such are correct? If I type, yum remove freshrpms-release-1.1-1.fc, will it work or is there something special I am supposed to do that I would have found in the "discussion" link?

I hate failure!

THANK YOU VERY MUCH SIMON!!

I will first apologize for not putting my glasses on before I wrote the last message to you. If you can accept some humor. I normally only wear my glasses when I am tired, but in any case I finally noticed the "-e· in between the "rpm" and the "freshrpms-release-1.1-1.fc" you presented to me. DUHHHHHH!!

So I determined that you were suggesting to attempt removing the rpm that way first OR use the "yum remove package" idea. DUHHHH AGAIN!! I am just going to have to wear my glasses more often if not always.

In any case, to stop rambling with my excitement, the "rpm -e" routine works beautifully. I even went and used it for some other rpms and it worked flawlessly.

SOOOOOO; THANKS AGAIN!!



This may be asking way too much, but is there a web page that teaches Linux programming to total beginners for free?

Great to hear it - I was beginning to worry

There are tons of tutorials for shell programming ... just google "bash shell tutorial" and select your favorite.

You can also learn a lot with the man and info pages ... at the end there is usually a list of related commands whose man pages are also worth some effort.

A cute trick is to pipe the output of info to a text file, print the text file, and read at leisure (or use a text editors search/processing abilities to look through large man pages). Say you want to know more about yum...

info yum > yum.txt

All this involved some sweating on my part - please take some time to click "thanks" and follow the affero page. Ta.

THANK YOU VERY MUCH!!