Сергей, le Thu 21 May 2015 16:47:56 +0300, a écrit :
> Hello! Are there any plans of integrating non-free firmware
> (http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/) into
> Debian Installation CD/DVD images?
No, because the Debian social contract says that Debian shall be free.
>
On Sunday 26 October 2008, Frank Lin PIAT wrote:
> Would it be possible/sensible to add the disk drivers to the netboot
> and mini.iso image.
No, it would not. It would increase the size of the images by too much.
We've known about this issue for ages. We need to solve it, not work
around it.
W
On Sat, 2008-10-25 at 22:01 +0200, Frans Pop wrote:
> On Saturday 25 October 2008, Steve Langasek wrote:
> > On Sat, Oct 25, 2008 at 06:01:42PM +0200, Frank Lin PIAT wrote:
> > > If I understand the situation correctly, the fact that one introduces
> > > a usb key causes that key to be enumerated b
On Saturday 25 October 2008, Don Wright wrote:
> It happened on my netinst (from D-I daily) attempt when I left the USB
> stick inserted during startup. USB->sda, Promise SATA->sdb. The IDE
> drives were on hda and hdb, as I recall. I don't think any firmware is
> required, as this box has had etch
On Sat, 25 Oct 2008 22:01:23 +0200, Frans Pop <[EMAIL PROTECTED]> wrote:
>On Saturday 25 October 2008, Steve Langasek wrote:
>> On Sat, Oct 25, 2008 at 06:01:42PM +0200, Frank Lin PIAT wrote:
>> > If I understand the situation correctly, the fact that one introduces
>> > a usb key causes that key
On Sat, 25 Oct 2008 21:08:00 +0200, Bastian Blank <[EMAIL PROTECTED]> wrote:
>On Sat, Oct 25, 2008 at 12:20:29PM -0500, Don Wright wrote:
>> So since the installer must use (insecure) WEP instead of (also insecure[1])
>> WPA, then Debian should not be installable on computers with only a wireless
On Saturday 25 October 2008, Steve Langasek wrote:
> On Sat, Oct 25, 2008 at 06:01:42PM +0200, Frank Lin PIAT wrote:
> > If I understand the situation correctly, the fact that one introduces
> > a usb key causes that key to be enumerated before the sata hard disk,
> > which causes grub to write an
On Sat, Oct 25, 2008 at 06:01:42PM +0200, Frank Lin PIAT wrote:
> When a firmware is missing, DI now prompts for a device with that
> firmware. (great, I love that feature!).
> If I understand the situation correctly, the fact that one introduces a
> usb key causes that key to be enumerated befor
On Sat, Oct 25, 2008 at 12:20:29PM -0500, Don Wright wrote:
> So since the installer must use (insecure) WEP instead of (also insecure[1])
> WPA, then Debian should not be installable on computers with only a wireless
> connection?
Now you need to say more. The public papers don't show a cryptogra
On Sat, 25 Oct 2008 18:01:42 +0200, Frank Lin PIAT <[EMAIL PROTECTED]> wrote:
>Finally, since D-I doesn't seems to support WPA. I wonder if we really
>should prompt for wifi firmware... which would encourage people to use
>the very unsecure WEP protocol?
>I could work on a patch to use a blacklist
On Friday 20 June 2008, Joey Hess wrote:
> > We probably do still need to make sure
> > - if we install firmware from a package that licence requirements are
> > met (e.g. display a debconf message included in the package)
>
> What's an example of a package that needs to do this?
No idea if there
Frans Pop wrote:
> > Then the module would still fail to initialize[1] -- and hw-detect can
> > notice this file, and prompt the user for firmware, and then remove and
> > reload the module if it's provided.
>
> Possibly something like 'udevtrigger --retry-failed' might work too.
Just tried this,
On Friday 20 June 2008, Joey Hess wrote:
> hw-detect could be made smart about detecting when a module it's
> loading needs firmware. This is pretty easy to do by modifiying
> /lib/udev/firmware.agent to log the names of the module and firware
> file if firmware cannot be found. Something like:
>
>
As a followup to this old post of mine (that AFAIK no progress has been
made on), here's a new idea, to handle the case of firmware needed early
in d-i.
hw-detect could be made smart about detecting when a module it's loading
needs firmware. This is pretty easy to do by modifiying
/lib/udev/firmw
On Tue, Sep 19, 2006 at 04:24:17PM +0200, Wouter Verhelst wrote:
> On Mon, Sep 18, 2006 at 12:36:00PM -0400, Nathanael Nerode wrote:
>
> > Perhaps the correct structure is this: after choosing "Customization
> > modules", the user gets a menu of possible places to get them from (CD,
> > USB, flop
On Tue, Sep 19, 2006 at 03:01:19PM -0400, Joey Hess wrote:
> Wouter Verhelst wrote:
> > I've been thinking that the best way here is to just nuke the
> > configuration of the retriever before (or while) running
> > customization-modules in some way. We'll be assuming that there is at
> > least one
Wouter Verhelst wrote:
> I've been thinking that the best way here is to just nuke the
> configuration of the retriever before (or while) running
> customization-modules in some way. We'll be assuming that there is at
> least one way to get udebs onto the running debian-installer session; so
> the
On Mon, Sep 18, 2006 at 01:12:52PM -0400, Nathanael Nerode wrote:
>
>
> Wouter Verhelst wrote:
>
> > On Tue, Sep 05, 2006 at 11:35:25AM +0200, Wouter Verhelst wrote:
> >> Feedback is welcome.
> >
> > Since the only feedback I received thus far was Goswin von Brederlow
> > saying he liked the id
On Mon, Sep 18, 2006 at 12:36:00PM -0400, Nathanael Nerode wrote:
> Wouter Verhelst wrote:
> > Can people please have a look and comment? I'd like to avoid some
> > specific GR by making whatever is going to be voted upon moot ;-)
>
> We should have a way of doing the same thing, only with a custo
Wouter Verhelst wrote:
> On Tue, Sep 05, 2006 at 11:35:25AM +0200, Wouter Verhelst wrote:
>> Feedback is welcome.
>
> Since the only feedback I received thus far was Goswin von Brederlow
> saying he liked the idea, and since I didn't have much else to do today
> (other than wait for a supplier.
Wouter Verhelst wrote:
> On Tue, Sep 05, 2006 at 11:35:25AM +0200, Wouter Verhelst wrote:
>> Feedback is welcome.
>
> Since the only feedback I received thus far was Goswin von Brederlow
> saying he liked the idea, and since I didn't have much else to do today
> (other than wait for a supplier...
Joey Hess wrote:
> Wouter Verhelst wrote:
>> Since the most central point of disagreement seems to be around the need
>> to support non-free firmware from the installation (whether by doing
>> that through supporting the non-free repository, or by just dropping
>> these firmware blobs in main, or
On Fri, Sep 08, 2006 at 10:55:12AM +0200, Goswin von Brederlow wrote:
>
> Yoe recently checked in support for a trivial udeb image. You just
> dump whatever udeb you want on the floppy, cd, usb, whatever and then
> select a menu entry to install *.udeb from that medium.
> Please do test it.
Where
Rick Thomas <[EMAIL PROTECTED]> writes:
> On Sep 7, 2006, at 3:05 PM, Joey Hess wrote:
>
>> This won't be practical. They are just udebs, but they have complex
>> interdependencies and we can't expect users to pick the right set of
>> udebs to put on a driver floppy that both supports all the hard
Joey Hess <[EMAIL PROTECTED]> writes:
> Wouter Verhelst wrote:
>> * In case we're installing from the network, download (using a TFTP
>> client) a tarball with udebs from the same TFTP server we've booted
>> from (which would require us to figure out somehow where we booted
>> from). I *thin
On Thu, Sep 07, 2006 at 07:02:18PM -0400, Rick Thomas wrote:
>
> On Sep 7, 2006, at 3:05 PM, Joey Hess wrote:
>
> >This won't be practical. They are just udebs, but they have complex
> >interdependencies and we can't expect users to pick the right set of
> >udebs to put on a driver floppy that bo
On Sep 7, 2006, at 3:05 PM, Joey Hess wrote:
This won't be practical. They are just udebs, but they have complex
interdependencies and we can't expect users to pick the right set of
udebs to put on a driver floppy that both supports all the hardware
they
need to support and fit in its limite
On Thu, Sep 07, 2006 at 03:05:09PM -0400, Joey Hess wrote:
> Wouter Verhelst wrote:
> > Your mail suggests a number of things, but I feel most of those are
> > redundant; it should be possible to do just a subset.
>
> My mail tries to explore all the positibities, it doesn't suggest
> implementing
Wouter Verhelst wrote:
> Your mail suggests a number of things, but I feel most of those are
> redundant; it should be possible to do just a subset.
My mail tries to explore all the positibities, it doesn't suggest
implementing them all. However, a certian amount of redundancy is
necessary to get
> So there are cases of:
> * CD-ROM drives needing firmware somewhere along the path (IDE/SATA
> controller, drive itself perhaps?, more stuff...)
If you have a cdrom behind a firmware requiring scsi controller. Not so
likely, but not completely impossible. I have never seen
cdrom drives requiri
On Tue, Sep 05, 2006 at 04:07:10PM -0400, Joey Hess wrote:
> Wouter Verhelst wrote:
> > Since the most central point of disagreement seems to be around the need
> > to support non-free firmware from the installation (whether by doing
> > that through supporting the non-free repository, or by just d
Wouter Verhelst wrote:
> Since the most central point of disagreement seems to be around the need
> to support non-free firmware from the installation (whether by doing
> that through supporting the non-free repository, or by just dropping
> these firmware blobs in main, or whatnot), I'm trying to
On Tue, Sep 05, 2006 at 11:35:25AM +0200, Wouter Verhelst wrote:
> Feedback is welcome.
Since the only feedback I received thus far was Goswin von Brederlow
saying he liked the idea, and since I didn't have much else to do today
(other than wait for a supplier...), I went ahead and wrote it. It's
33 matches
Mail list logo
