I like this scheme but I was kinda scratching my head wondering how
device autodetection would work. I suppose that would just be a
package, say, libdetect, which when you run the configure step, would
emit information on possible network devices (including hopefully
capability to do null
++ 15/09/00 14:38 -0400 - Adam Di Carlo:
Here are some excerpts from my attempt to build the Russian PDF:
Language: russianb 1999/04/05 v1.1j Russian support from the babel system
Package babel Warning: No hyphenation patterns were loaded for
(babel)the language
I've uploaded updated Release Notes and Installation Manual for Potato
to master.d.o. The main feature here is updates, especially in the
French, Croatian, Polish, and Czech translations.
I've had to disable the Russian PDF since it won't run for me anymore.
I'd appreciate any testing of
from cvs.debian.org
The Installer UI
[snip]
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 configuration.
i'd
Torsten Landschoff wrote:
On Sat, Sep 16, 2000 at 12:36:56PM +1100, Glenn McGrath wrote:
The way modules will work is that they should only be called (or loaded)
if needed, so its not a matter of disabling any modules, just only
calling the modules you need, this is the key to shrinking
On Thu, Sep 14, 2000 at 11:26:58AM -0500, Steve Greenland wrote:
Now, there are definitely places where the install could be improved,
(this is news?), but I'm really tempted to ignore people who can't be
bothered to read the owners manual. This is an operating system, not a
toaster.
This
On Sat, Sep 16, 2000 at 12:36:56PM +1100, Glenn McGrath wrote:
The way modules will work is that they should only be called (or loaded)
if needed, so its not a matter of disabling any modules, just only
calling the modules you need, this is the key to shrinking the installer
to 1 boot disk
7 matches
Mail list logo
