Glenn McGrath wrote:
> We still have to take into consideration that someone somewhere may need
> that 2nd floppy.
Well of course. Someone might be installing by just floppies, or they
may need something else that won't fit on just one. I'd still like
one to be doable in some situations.
> I thi
On Wed, Sep 13, 2000 at 03:11:32PM +1100, Glenn McGrath wrote:
> We still have to take into consideration that someone somewhere may need
> that 2nd floppy.
>
> I think that it should be easier for the end user to customise there
> installer based on space limitations and required features, tha
On Sep 12, Joey Hess wrote:
> > Amigas (PowerPC or m68k) could do some autodetection for AutoConfig
> > devices; the question is, does anyone want to code it? I don't know
> > if we even build any hardware modules in the m68k kernels... (If
> > AutoConfig detection were coded, it could easily fi
Package: boot-floppies
This is a really quick report, I'll dig into more a bit later once I get
Debian GNU/Linux installed, but this one seemed to be worthy of note.
Nowhere in this document is anything about actually getting Debian GNU/Linux
covered. If this is intended to be something that's d
"Michael S. Fischer" wrote:
>
> On Tue, Sep 12, 2000 at 08:23:16PM -0700, Joey Hess wrote:
>
> > If the choice is between one floppy with minimal detection and two floppies
> > with detection of everything, I want one floppy, every day.
>
> I'm with Joey on that.
>
We still have to take into
On Tue, Sep 12, 2000 at 08:34:50PM -0700, Joey Hess wrote:
> Chris Lawrence wrote:
> > PowerPC will probably work with libdetect out of the box (at least the
> > PCI-based ones). I remember something about PPC in the changelog lately.
>
> I wonder what other, non-pci hardware there is to content
On Tue, Sep 12, 2000 at 08:23:16PM -0700, Joey Hess wrote:
> If the choice is between one floppy with minimal detection and two floppies
> with detection of everything, I want one floppy, every day.
I'm with Joey on that.
--
Michael S. Fischer <[EMAIL PROTECTED]>, AKA Otterley
Lead
Chris Lawrence wrote:
> PowerPC will probably work with libdetect out of the box (at least the
> PCI-based ones). I remember something about PPC in the changelog lately.
I wonder what other, non-pci hardware there is to content with on PPC?
> Amigas (PowerPC or m68k) could do some autodetection
On Sep 12, Joey Hess wrote:
> Dan Helfman wrote:
> > Not to mention confidence in x86 hardware..
>
> Well that made me realize the big thing we've missed in this hardware
> detection discussion so far: what about other architectures?
>
> (I'm not a multi-arch kind of guy, so I occasinally need t
Ben Collins wrote:
> The thing is, most of these autodetection libraries just do "detection,
> suggest module". They don't care whether it is an ethernet card or video
> frame grabber.
That's not how libdetect works. Which library were you thinking of?
> There's no need to duplicate this just fo
On Tue, Sep 12, 2000 at 07:18:23PM -0700, Joey Hess wrote:
> Glenn McGrath wrote:
> > The 2.4 kernel can handle isa-pnp, so there shouldnt be problems with
> > assigning irq and io value for isa-pnp network or sound cards which
> > there are probably a fair few of.
>
> Two problems there:
>
> 1)
On Tue, Sep 12, 2000 at 07:57:23PM -0700, Joey Hess wrote:
> Dan Helfman wrote:
> > Not to mention confidence in x86 hardware..
>
> Well that made me realize the big thing we've missed in this hardware
> detection discussion so far: what about other architectures?
>
> (I'm not a multi-arch kind
Dan Helfman wrote:
> Not to mention confidence in x86 hardware..
Well that made me realize the big thing we've missed in this hardware
detection discussion so far: what about other architectures?
(I'm not a multi-arch kind of guy, so I occasinally need to be reminded
to consider them..)
Is hard
On Tue, Sep 12, 2000 at 07:07:44PM -0700, Joey Hess wrote:
> Dan Helfman wrote:
> > Libdetect is modular in terms of detecting different classes of hardware
> > (CD drive, sound, ethernet, etc) via separate functions, so it can be
> > stripped down for the boot disks quite easily. After just a few
Glenn McGrath wrote:
> The 2.4 kernel can handle isa-pnp, so there shouldnt be problems with
> assigning irq and io value for isa-pnp network or sound cards which
> there are probably a fair few of.
Two problems there:
1) I have a box that pnpdump locks solid. Ok, I haven't tried the new
kern
Ben Collins wrote:
>
> On Tue, Sep 12, 2000 at 06:46:44PM -0700, Joey Hess wrote:
> > Ben Collins wrote:
> > > The good thing about PCI hardware detection is that there is no probing,
> > > and the PCI layer/driver handles allocation an IRQ and I/O. So basically
> > > the gist is, atleast include
Ben Collins wrote:
> > Maybe that's all the hardware detection we should bother with. Is there
> > really any point in worrying about making life easier for owners of ISA
> > hardware these days?
>
> IMO, we shouldn't. Trying to autodetect ISA is probably more harm than
> good anyway.
On the oth
Dan Helfman wrote:
> Libdetect is modular in terms of detecting different classes of hardware
> (CD drive, sound, ethernet, etc) via separate functions, so it can be
> stripped down for the boot disks quite easily. After just a few of
> minutes of commenting out detect calls, I was able to compile
"Michael S. Fischer" wrote:
>
> On Wed, Sep 13, 2000 at 12:48:36PM +1100, Glenn McGrath wrote:
>
> > Debconf should be able to solve problems for mass and non-interactive
> > installs.
> >
> > debconf has an option for non-interactive installs by using the default
> > value.
>
> Could you pleas
On Tue, Sep 12, 2000 at 06:46:44PM -0700, Joey Hess wrote:
> Ben Collins wrote:
> > The good thing about PCI hardware detection is that there is no probing,
> > and the PCI layer/driver handles allocation an IRQ and I/O. So basically
> > the gist is, atleast include PCI detection, which maps PCI d
On Wed, Sep 13, 2000 at 12:48:36PM +1100, Glenn McGrath wrote:
> Debconf should be able to solve problems for mass and non-interactive
> installs.
>
> debconf has an option for non-interactive installs by using the default
> value.
Could you please define "default value" for me? Is this a defa
"Michael S. Fischer" wrote:
>
> > Joey Hess wrote:
>
> > > Since retrievers are debian packages, they can have a postinst that is
> > > run to set them up.
>
> > > During setup, they may need to prompt the user for
> > > information (using debconf). For example, a nfs retriever will probably
>
Ben Collins wrote:
> The good thing about PCI hardware detection is that there is no probing,
> and the PCI layer/driver handles allocation an IRQ and I/O. So basically
> the gist is, atleast include PCI detection, which maps PCI device ID's to
> modules, and can prompt for which ones to load.
Ri
Michael S. Fischer wrote:
> I rather wish I'd seen the beginning of this thread so I could gain
> some context. I'll see if I can find it at the archive so I can be
> better educated, but for now I'll try to offer my comments as is.
The context you're missing is that we're going to rewrite debia
On Tue, Sep 12, 2000 at 05:24:41PM -0700, Joey Hess wrote:
> Hartmut Koptein wrote:
> > Another important point is an hardware detection database.
>
> This is left up to the modules that provide support for the various
> hardware. We need to pick a good hardware detection library for those
> modu
>
> We really need a hardware detection library that is modularized or can
> be modularized. There is no need to have code in the installer to detect
> your sound card. And if you're installing from a floppy and the network,
> you need NIC detection code, but code to detect a CD drive is
> unne
> Joey Hess wrote:
> > Since retrievers are debian packages, they can have a postinst that is
> > run to set them up.
> > During setup, they may need to prompt the user for
> > information (using debconf). For example, a nfs retriever will probably
> > need to prompt the user for a nfs server na
I rather wish I'd seen the beginning of this thread so I could gain
some context. I'll see if I can find it at the archive so I can be
better educated, but for now I'll try to offer my comments as is.
I should introduce myself first. I am the operations team lead for
AuctionWatch.com (the .sign
Joey Hess wrote:
>
> Retrievers
> --
>
> Retrievers are modules that can download or otherwise retrieve
> files[1], including other modules and Packages files. It is expected that at
> least the following types will eventually be implemented:
>
> - cd retriever
> Ensures an inst
(Dan, search for 'detect' to see why I cd'd you.)
Hartmut Koptein wrote:
> > After the kernel boots up, the first thing the user will see is whatever UI
> > is being used, configuring itself. This is equivalent to the current
> > installer asking if the screen supports color, and keyboard configu
Hi,
> Modules
> ---
> Retrievers
> --
> The Installer UI
>
> The user's view
> ---
>
> After the kernel boots up, the first thing the user will see is whatever UI
> is being used, configuring itself. This is equivalent to the current
> installer asking if
I think I said I'd have this design draft done 3 weeks ago. Real life
intervened, and the rest of this month is going to be even worse. So I'm
going to post this rough draft of the design now, with the caveat that
it needs a lot of work. Please help me make it better.
Note that all documents are
32 matches
Mail list logo
