blacklisting/MOD_AUTOLOAD - what drove the change?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Archlinux <arch-general@xxxxxxxxxxxxx>
Subject: blacklisting/MOD_AUTOLOAD - what drove the change?
From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
Date: Sat, 11 Jun 2011 17:44:25 -0500
Organization: Rankin Law Firm, PLLC
Reply-to: General Discussion about Arch Linux <arch-general@xxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110414 SUSE/3.1.10 Thunderbird/3.1.10

Guys,

Just curious for the reason behind the changes to blacklisting andMOD_AUTOLOAD. What drove the change?


--
David C. Rankin, J.D.,P.E.

Follow-Ups:
- Re: blacklisting/MOD_AUTOLOAD - what drove the change?
  - From: Jan Steffens

Prev by Date: Re: Reboot - Versioned Kernel Installs
Next by Date: Re: blacklisting/MOD_AUTOLOAD - what drove the change?
Previous by thread: Dejavu sans mono fonts rendering issue.
Next by thread: Re: blacklisting/MOD_AUTOLOAD - what drove the change?
Index(es):
- Date
- Thread

[Index of Archives] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Share Photos] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Samba] [Device Mapper]

Powered by Linux