On Mon, 16 Apr 2001, Jeff Bailey wrote: > > Off the top of my head, > > > HDD partitioning tools > > cdrom part of apt working > > Using a Hurd ramdisk for the installation. (Nice, but not vital) > > Working df > > Fully functional dselect? > > Task packages for the Hurd? > > Stopping here, getting depressed. > > How much of this is critical for a release? (knowing that a release > is a year away) I realize that the stable release is supposed to be > good and 'perfect', but I'm sure (with focus) in a year we could have > the cdrom part of apt, and the HDD partition tools. > > I've never used dselect (I always abort at that part of the install > and apt only the packages that I need), what's broken?
It aborted when it started on contrib, hence my crazy main only file system on the CDs. dselect has the advantage of installing the important, base etc packages during the initial install. An apt (with cdrom support), tasksel and task packages method is superior and can cope with the pool file system. I have a cdrom installation in mind. > What needs to be done on task packages? I don't know anything about this. task packages are empty packages with carefully chosen dependencies, eg, task-hurd-devel would list in its dependencies those packages which would be needed for a Hurd development machine. tasksel identifies these task packages and lists them. The operator can then chose the task packages to install. This can be done at any time. The next Great Debate (tm) will be "Should the Hurd have its own task packages". task packages are easy to build, even I can do it. I forgot that woody is now a year away, which is a bad thing as Debian 2.2 is already dated. Phil. - Philip Charles; 39a Paterson St., Dunedin, New Zealand; +64 3 4882818 Mobile 025 267 9420. I sell GNU/Linux CDs. See http://www.copyleft.co.nz [EMAIL PROTECTED] - preferred. [EMAIL PROTECTED]
