Perhaps instead appending "audit=0" to the kernel cmdline would do the same?
Might be easier than using recovery/rescue mode.
Regards,
On Fri, Apr 20, 2012 at 3:01 PM, Jon Masters <jcm@xxxxxxxxxx> wrote:
> Folks,
>
> As those who follow me on the facegoogblogs will know, I've used the
> nuclear option to track down what's causing the problem with 3.3+. I'll
> spare you all the boring details (working on that) and just suggest that
> you want to disable auditd if you want your system to boot 3.3. You can
> either boot into rescue (which won't start auditd so you have a chance
> to do this even on a system already only having a 3.3 kernel) or you can
> boot an older kernel. Then just disable the auditd.service:
>
> systemctl disable auditd.service
>
> I'll get it working properly soon, auditing is important, yada yada...
>
> Jon.
> _______________________________________________
> arm mailing list
> arm@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/arm
--
-Jon
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
[Linux ARM (Vger)]
[Linux ARM]
[ARM Kernel]
[Fedora User Discussion]
[Older Fedora Users Discussion]
[Fedora Advisory Board]
[Fedora Security]
[Fedora Maintainers]
[Fedora Devel Java]
[Fedora Legacy]
[Fedora Desktop]
[ATA RAID]
[Fedora Marketing]
[Fedora Mentors]
[Fedora Package Announce]
[Fedora Package Review]
[Fedora Music]
[Fedora Packaging]
[Centos]
[Fedora SELinux]
[Fedora Triage]
[Deep Creek Hot Springs]
[Coolkey]
[Yum Users]
[Tux]
[Big List of Linux Books]
[Yosemite News]
[Yosemite Photos]
[Linux Apps]
[KDE Users]
[Fedora Tools]
[Fedora Art]
[Fedora Docs]
[Asterisk PBX]