Help, errors with an ext3 partition by the end of startup of FC 5

[bad_user]

I installed a Fedora Core 5 on my desktop PC. Each time by the end of a startup, I can see the following errors on the screen. But the computer can work after that. I wonder what causes those errors. Is it a severe problem? How to get rid of them? Thanks.
(I also attached some information of my computer below the errors)

# Here come the errors
Jun 21 10:30:04 localhost avahi-daemon[2216]: Server startup complete. Host name is localhost.local. Local service cookie is 283868878.
Jun 21 10:30:05 localhost kernel: audit(1150857005.013:2): avc: denied { getattr } for pid=2236 comm="hald" name="/" dev=sda6 ino=2 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir
Jun 21 10:30:05 localhost kernel: audit(1150857005.177:3): avc: denied { getattr } for pid=2236 comm="hald" name="/" dev=sda6 ino=2 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir
Jun 21 10:30:05 localhost kernel: audit(1150857005.217:4): avc: denied { getattr } for pid=2236 comm="hald" name="/" dev=sda6 ino=2 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir
Jun 21 10:30:05 localhost kernel: audit(1150857005.313:5): avc: denied { getattr } for pid=2236 comm="hald" name="/" dev=sda6 ino=2 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir
Jun 21 10:30:05 localhost kernel: audit(1150857005.361:6): avc: denied { getattr } for pid=2236 comm="hald" name="/" dev=sda6 ino=2 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir
Jun 21 10:30:05 localhost kernel: audit(1150857005.381:7): avc: denied { getattr } for pid=2236 comm="hald" name="/" dev=sda6 ino=2 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir
Jun 21 10:30:05 localhost kernel: audit(1150857005.401:8): avc: denied { getattr } for pid=2236 comm="hald" name="/" dev=sda6 ino=2 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir
Jun 21 10:30:05 localhost kernel: audit(1150857005.493:9): avc: denied { getattr } for pid=2236 comm="hald" name="/" dev=sda6 ino=2 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir
Jun 21 10:30:05 localhost kernel: audit(1150857005.525:10): avc: denied { getattr } for pid=2236 comm="hald" name="/" dev=sda6 ino=2 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir

#my linux version
uname -a

Linux localhost.localdomain 2.6.15-1.2054_FC5smp #1 SMP Tue Mar 14 16:05:46 EST 2006 i686 i686 i386 GNU/Linux

#disk info
fdisk -l

Device Boot Start End Blocks Id System
/dev/sda1 * 2551 2600 401625 83 Linux
/dev/sda2 1 2550 20482843+ b W95 FAT32
/dev/sda3 2601 7600 40162500 83 Linux
/dev/sda4 7601 19457 95241352+ 5 Extended
/dev/sda5 7601 17600 80324968+ 83 Linux
/dev/sda6 17601 19000 11245468+ 83 Linux
/dev/sda7 19001 19260 2088418+ 82 Linux swap / Solaris
/dev/sda8 19261 19457 1582371 82 Linux swap / Solaris

#my fstab file
cat fstab

LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
LABEL=/home /home ext3 defaults 1 2
proc /proc proc defaults 0 0
LABEL=/share /share ext3 defaults 1 2
sysfs /sys sysfs defaults 0 0
LABEL=SWAP-sda7 swap swap defaults 0 0
LABEL=SWAP-sda8 swap swap defaults 0 0

[ppesci]

This is a problem with selinux package.
if you want to fix, you must to see in configuration files located under /etc directory.
I am not an expert and can't say how to configure. You have a home work.

Another way to solve this is disabling selinux and can be done selecting menu Administration>Security Level Configuration and then SELinux, select disable and try torestart. You don't see this problem again. The down side in this case is you aren't using a security tool but... is the easy way.

HTH

Pietro Pesci Feltri

[bad_user]

But why this? Can it be solved if I reintall FC? I don't wanna lose SELinux.

[ppesci]

1) you must disable SELinux and see if the problem dissapear.

2) the problem if with hald daemon. Is not serious, hald is for detect hardware, if your hardware is detected fine, the messages don will be a problem.

3) i think the problem don't dissapear if you reinstall but you can try.

HTH

Pietro Pesci Feltri

[ibbo]

Will a relabel not fix it?

Ibbo

[bad_user]

1) you must disable SELinux and see if the problem dissapear.

Yes. Switching SELinux from 'Enforce' to 'Disable' caused lot of such warnings. So I rebooted the computer and there were no such messages again.

2) the problem if with hald daemon. Is not serious, hald is for detect hardware, if your hardware is detected fine, the messages don will be a problem.

I am a newbie, how to judge it is with/without hald daemon?

3) i think the problem don't dissapear if you reinstall but you can try.

You are right. I have reinstalled. It seems this appears on each existing unformatted patitions.
HTH

Thank you, but ... what to do next? Should I always disable SELinux?

Pietro Pesci Feltri[/QUOTE]

[ppesci]

Hald daemon can't get attributes from this partition, but i think this doesn't matter, there are no problem really.
Do the command:

yum -y update

there are several changes in SELinux and hald that can solve this situation. Of course, if you have a fresh install, the update will be *huge*. Then reboot and see what happens.

If problem persist then:
The best is read manuals from SELinux to know how let hald daemon permorm it's works without complain.
Second is do nothing if you want SELinux running any way. Nothing serious is orcuring anyway.
third Disable SELinux

My opinion only. 3 choices. Select one.

HTH

Pietro Pesci Feltri

[bad_user]

Will a relabel not fix it?

Ibbo
But how? I am just looking for an easy way to get rid of this problem. I don't wanna read the whole mannual of SELinux or hald (I am both busy and lasy... :p ), and I am bored of the complaints showing in the screen (you can see them several times). And I don't wanna lose SELinux forever. Is there some possible one-touch solution. I know I am a bit greedy... :p

[ppesci]

2 choices then:

1) close your eyes on startup

2) disable SELinux on starting process and enable it after. You can enable as command in your rc.local file in etc directory.

HTH

Pietrp Pesci Feltri