Magnus Ekdahl wrote:
> * When one finds a bug report containing only one issue I assume its
> correct just to reassign it to its respective package? An alternative
> line of thought would be to collect all installation-reports in one
> place, hence every bug needs to be cloned.
Since we're not
Joey Hess wrote:
...
We are hoping to process at least 75 of these installation reports
this week, with the help of the larger group of Debian developers,
and so we have written a tutorial that should get developers quickly up
to speed on processing installation reports. You can find it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Sat, Jan 31, 2004 at 01:43:29PM -0500, Joey Hess wrote:
> 6. lintian/linda checks for udebs
I just submitted bug #231292 for linda which implements some
udeb checks mentioned in the mini-policy.
Another patch (bug #230986) allows the checking
Matthew A. Nicholson wrote:
On Sat, 31 Jan 2004 13:43:29 -0500, Joey Hess <[EMAIL PROTECTED]> wrote:
7. graphical boot screen
We would like to drag Debian kicking and screaming into the .. er,
late 90's by giving its installer a fancy graphical boot screen. We
have two candidates, but w
Matthew A. Nicholson wrote:
> On Sat, 31 Jan 2004 13:43:29 -0500, Joey Hess <[EMAIL PROTECTED]> wrote:
>
>
> >7. graphical boot screen
> >
> > We would like to drag Debian kicking and screaming into the .. er,
> > late 90's by giving its installer a fancy graphical boot screen. We
> > have
On Sat, Jan 31, 2004 at 01:43:29PM -0500, Joey Hess wrote:
> 3. PCMCIA
> 4. low memory support
I can at least test d-i on low mem + PCMCIA network machine
w/o CD-ROM.
> 9. everything else
What's about RAID1 support? I remember someone is working
on that. Would this clash with GRUB? Again, I'm
On Sat, 31 Jan 2004 13:43:29 -0500, Joey Hess <[EMAIL PROTECTED]> wrote:
7. graphical boot screen
We would like to drag Debian kicking and screaming into the .. er,
late 90's by giving its installer a fancy graphical boot screen. We
have two candidates, but would be glad to see somethin
On Sat, Jan 31, 2004 at 06:22:49PM -0500, Joey Hess wrote:
> Matt Zimmerman wrote:
> > Isn't the usual problem with wireless that the drivers for most cards must
> > be built from source because they aren't in the standard kernel? Are we
> > going to try to provide binary modules?
>
> Between or
On Sat, 31 Jan 2004 18:54:46 -0500
Joey Hess <[EMAIL PROTECTED]> wrote:
> Glenn McGrath wrote:
> > Is the only reason we need a writable filesystem so that the install
> > reoprt can be stored there ? Is that a permanent feature ?
>
> There are dozens of places where the installer writes to its
Glenn McGrath wrote:
> What are the ideas ?
>
> I may be interested in working on them...
The best ideas I've seen are:
- debix (http://alioth.debian.org/projects/debix)
- a udeb that turns on swap earlier, using a spare partition or drive,
before the whole installer is loaded and before pa
Matt Zimmerman wrote:
> Isn't the usual problem with wireless that the drivers for most cards must
> be built from source because they aren't in the standard kernel? Are we
> going to try to provide binary modules?
Between orinoco and orinoco_pci and a few others, the kernel actually
has reasonab
On Sat, 31 Jan 2004 13:43:29 -0500
> 4. low memory support
>
>d-i barely supports installations on systems with 32 mb of memory.
>It's unlilkely to ever support lesser systems unless someone steps
>up to work on it. We have some ideas, that should work, but no
>time.
What are the
On Sat, Jan 31, 2004 at 01:43:29PM -0500, Joey Hess wrote:
> - security fixed, 2.4.24 kernel (with SATA support)
> (done for stock i386 (but not SATA, probably?))
I actually installed woody (bf24) onto a system with only SATA disks a few
days ago. It worked, but things were a little
13 matches
Mail list logo
