-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/22/2012 08:42 PM, Fernando Cassia wrote:
> On Sun, Apr 22, 2012 at 18:34, Adam Williamson
> wrote:
>> That is not 'the usual procedure'. The usual procedure is 'setenforce
>> Permissive', boot with 'enforcing=0' or 'selinux=0' (but the last is
On Mon, Apr 23, 2012 at 11:27 AM, Adam Williamson wrote:
> On Sun, 2012-04-22 at 21:42 -0300, Fernando Cassia wrote:
>> On Sun, Apr 22, 2012 at 18:34, Adam Williamson wrote:
>> > That is not 'the usual procedure'. The usual procedure is 'setenforce
>> > Permissive', boot with 'enforcing=0' or 'se
On Sun, 2012-04-22 at 21:42 -0300, Fernando Cassia wrote:
> On Sun, Apr 22, 2012 at 18:34, Adam Williamson wrote:
> > That is not 'the usual procedure'. The usual procedure is 'setenforce
> > Permissive', boot with 'enforcing=0' or 'selinux=0' (but the last is a
> > last resort to be used only if
On Sun, Apr 22, 2012 at 18:34, Adam Williamson wrote:
> That is not 'the usual procedure'. The usual procedure is 'setenforce
> Permissive', boot with 'enforcing=0' or 'selinux=0' (but the last is a
> last resort to be used only if permissive mode isn't enough).
Thanks. Well, it was "the usual pr
On Sun, 2012-04-22 at 17:27 -0300, Fernando Cassia wrote:
> What would be the right procedure to test why F17 doesnt' mount my sd
> card reader?
>
> F16 on the same machine worked just fine.
> Although on previous Fedora versions (F10 or thereabouts) I used to
> have to disable SELinux to get the
What would be the right procedure to test why F17 doesnt' mount my sd
card reader?
F16 on the same machine worked just fine.
Although on previous Fedora versions (F10 or thereabouts) I used to
have to disable SELinux to get the card mounted as I always got a
SELInux exception when plugging my SD c
