3ware RAID selinux smartd

[Daniel J Walsh]

Kevin H. Hobbs wrote:
> Is this bug worthy? Creating the correct udev rules has defeated me.
>
> When a 3ware 9000 series card is present the devices /dev/twa* should be
> created, and they should have fixed_disk_device_t in their security
> context so that smartd can monitor the disks.
>
> Against what should the bug be filed, udev?
>
>   
udev,

Are you saying the device does not get created or does not get created 
with the correct context?

Dan
> On Tue, 2007-03-06 at 10:15 -0500, Daniel J Walsh wrote:
>   
>> Kevin H. Hobbs wrote:
>>     
>>> On Fri, 2007-03-02 at 12:00 -0500, fedora-list-request at redhat.com wrote:
>>>   
>>>       
>>>> semanage fcontext -a -t fixed_device_t -f "-c" "/dev/twa[0-9]*"
>>>>
>>>>
>>>> Will load the file context and then you need to restart udev and it 
>>>> should get labeled correctly.
>>>>
>>>>     
>>>>         
>>> I don't think it liked fixed_device_t. It seemed to like
>>> fixed_disk_device_t though. There seem to be a lot of those hanging
>>> about in /dev. I don't know how to restart udev so I set the context
>>> myself :
>>>
>>> sudo chcon user_u:object_r:fixed_disk_device_t /dev/twa*
>>>
>>>   
>>>       
>> Sorry my mistake.  Fingers and brain not connected.  fixed_disk_device_t 
>> is correct.
>>     
>>> I restarted smartd and it now can access the disks.
>>>
>>> I asked the same question on my local LUG and got two suggestions:
>>>
>>>   1. Put a rule in /etc/udev/rules.d/. This will take me a while to
>>> figure out.
>>>   2. Try the 3DM2 tool from 3ware. This thing is really slick, but not
>>> free, not rpm, ...
>>>
>>> Thanks for the help!
>>>   
>>>