I am getting errors from Core 3 when booting they are as follows:
/etc/selinux/targeted/contexts/files/file_contexts: line 287 has invalid context system_u: object_r: crypt_device_t
and
/etc/selinux/targeted/contexts/files/file_contexts: line 888 has invalid context system_u: object_r: system_dbuser_var_run_t
any ideas why and how to fix them??
I am running a dual boot system Fedora Core 3 & XP pro w/ 2 80 GB western digital hardrives, AMD 1.3 Thunderbird processor, 1GB 400 SD-DDRAM, MSI 8 extreme Main Board

Let me know if more information is needed.
Many thanks,
Tim

Looks like this is a bug of some type with no known resolution: https://www.redhat.com/archives/fedo.../msg03700.html

Do you have a support contract with Redhat or are you just playing with it on your own? If you do have one, get them to sort it out.

If you want to eliminate the startup messages, the easiest thing to do is to disable SELinux.

SELinux as implemented by RedHat targets server functions (e.g., apache). So if you are just running a desktop, it isn’t doing much anyway (sendmail maybe?). And if you are running a server, all it tends to do is to make troubleshooting a problem extremely difficult. Usually, it IS the problem.

You can disable SELinux in the system security setup (i.e., the basic firewall setup config).

If you really want to know more about SELinux, you can read the RHEL4 SELinux manual ( http://www.redhat.com/docs/manuals/e...selinux-guide/ ), or at least read it until your head explodes.

Thanks, I think I'll opt for the head exploding; there must be a reason RH included SeLinux (other than to make life a living hell) and it's just a matter of time until they fix the error.

No, it was only added to make one miserable.

Thanx for the posting about the bug. I am just flying solo on getting Fedora Core 3 up and running. I guess maybe I should of tried the supported version (enterprise edition) first but I gotta learn somehow. I am using this to help me through college. I have a SQL server set up for right now and plan on setting up a file sharing server (for back ups of my Windows machines) and probably the firewall so that I can get rid of the Linksys router my ISP provided.

Looks like they have the bug fixed. I did a up2date last night and there were 8 new updates.
It appears as if the bug was with openssl, 5 0f the 8 were for that, the downloads were binutil, openssl, openssl-askpass, openssl-askpass-gnome, openssl-clients, openssl-server, selinux-policy-targeted,and Helix player. I rebooted just to check to see if the errors were still there and they were gone.
Thanks for all replies to my post