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

Re: Changing how we handle non-free firmware



On Wed, Aug 31, 2022 at 05:50:17PM +0200, Bart Martens wrote:
>On Thu, Aug 18, 2022 at 08:58:21PM +0100, Steve McIntyre wrote:
>> So, I propose the following:
>> 
>> =================================
>> 
>> We will include non-free firmware packages from the
>> "non-free-firmware" section of the Debian archive on our official
>> media (installer images and live images). The included firmware
>> binaries will *normally* be enabled by default where the system
>> determines that they are required, but where possible we will include
>> ways for users to disable this at boot (boot menu option, kernel
>> command line etc.).
>> 
>> When the installer/live system is running we will provide information
>> to the user about what firmware has been loaded (both free and
>> non-free), and we will also store that information on the target
>> system such that users will be able to find it later.
>
>> The target
>> system will *also* be configured to use the non-free-firmware
>> component by default in the apt sources.list file.
>
>This means that non-free-firmware would be always enabled, also when the system
>would not determine that the included firmware binaries are required. Intended?

After a suggestion from Wouter I've agreed a change here for exactly
that reason - see Message-ID: <[🔎] 20220830200050.GZ2668594@tack.einval.com>
yesterday.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
  Mature Sporty Personal
  More Innovation More Adult
  A Man in Dandism
  Powered Midship Specialty


Reply to: