On Sat, May 25, 2013 at 3:08 AM, Turbo Fredriksson tu...@bayour.com wrote:
On May 24, 2013, at 8:54 PM, Aron Xu wrote:
What I can think of is to do the trick in d-i, since it already has
the ability to retrieve and load udeb on the fly, and even prompt
users for missing firmware.
Maybe even
On May 25, 2013, at 2:23 PM, Aron Xu wrote:
just use DKMS to build OOT modules at
image generation time? Seems to be a good idea.
If setting up a kernel-build-system on one of the
Debian GNU/Linux servers isn't an option, then this
would be a second best..
Then it will be up to the user
On Fri, May 24, 2013 at 11:53 PM, Turbo Fredriksson tu...@bayour.com wrote:
On May 22, 2013, at 3:52 PM, Ben Hutchings wrote:
Quoting from the report of our 2009 meeting,
20091015123106.ga16...@kyllikki.org:
out of tree modules
---
After a somewhat involved discussion
On Sat, May 25, 2013 at 2:45 AM, Turbo Fredriksson tu...@bayour.com wrote:
On May 24, 2013, at 7:04 PM, Aron Xu wrote:
and help d-i people to handle the brokenness
if a change in kernel makes the OOT module does not build
This should only happen when a new major version of the kernel comes
On May 24, 2013, at 7:04 PM, Aron Xu wrote:
and help d-i people to handle the brokenness
if a change in kernel makes the OOT module does not build
This should only happen when a new major version of the kernel comes
out, which means it should only happen in unstable..
And we could make it so
On May 24, 2013, at 8:54 PM, Aron Xu wrote:
What I can think of is to do the trick in d-i, since it already has
the ability to retrieve and load udeb on the fly, and even prompt
users for missing firmware.
Maybe even build them using dkms? I saw that you can make d-i build
all packages...
6 matches
Mail list logo
