Re: debian-installer-utils_0.06_i386.changes ACCEPTED
ons 2002-11-06 klockan 05.40 skrev Christian T. Steigies: installer-menu-item: 9 This last line is something I've never seen before? And its not only on m68k where that happens... I had some problems with my sign script, so I removed this line manually before signing. If this is a problem, please tell me and I'll change it back. That's because we have XBC-installer-menu-item lines in the control file, instead of XB-installer-menu-item. Do we really need the C, people? /Martin signature.asc Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signeradmeddelandedel
Re: debian-installer-utils_0.06_i386.changes ACCEPTED
* Christian T. Steigies | installer-menu-item: 9 | | This last line is something I've never seen before? And its not only on m68k | where that happens... I had some problems with my sign script, so I removed | this line manually before signing. If this is a problem, please tell me and | I'll change it back. It is supposed to be there (or rather, it's supposed to be in the binary file, but not the changes file, but that's our and not your fault). So, no need to edit it by hand, but no harm done. :) -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Differences between mklibs.py and mklibs.sh
* Clément Moreau | Btw, I'm not familiar with python, so, is there a good place where I | can find a guide to this scripting language ? http://www.python.org/doc/current/tut/tut.html for instance. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to debian-installer/tools/cdebconf/debian by tfheen
Repository: debian-installer/tools/cdebconf/debian
who:tfheen
time: Wed Nov 6 11:11:37 CET 2002
Log Message:
Fix warnings about missing ${shlibs:Depends} for libdebconf0.3-dev.
Make debian-boot maintainer, add tausq and self to Uploaders
Files:
changed:changelog control rules
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
problem with apt-get
hello i download debian-installer via cvs and i 'make build' inthe build directory and it displays: tiramisu:/home/sferriol/debian/debian-installer/build# make build if [ -e ./tmp/net/tree/proc/self ]; then \ sudo chroot ./tmp/net/tree bin/sh -c if mount | grep ^proc ; then bin/umount /proc ; fi /dev/null; \ fi mkdir -p apt/state/lists/partial mkdir -p apt/cache/archives/partial apt-get --assume-yes -o Dir::Etc::sourcelist=/home/sferriol/debian/debian-installer/build/sources.list -o Dir::State=/home/sferriol/debian/debian-installer/build/apt/state -o Debug::NoLocking=true -o Dir::Cache=/home/sferriol/debian/debian-installer/build/apt/cache update Hit http://http.us.debian.org unstable/main/debian-installer Packages Ign http://http.us.debian.org unstable/main/debian-installer Release Hit http://http.us.debian.org unstable/main Sources Hit http://http.us.debian.org unstable/main Release Reading Package Lists... Done Building Dependency Tree... Done apt-get --assume-yes -o Dir::Etc::sourcelist=/home/sferriol/debian/debian-installer/build/sources.list -o Dir::State=/home/sferriol/debian/debian-installer/build/apt/state -o Debug::NoLocking=true -o Dir::Cache=/home/sferriol/debian/debian-installer/build/apt/cache autoclean Reading Package Lists... Done Building Dependency Tree... Done # If there are local udebs, remove them from the list of things to # get. Then get all the udebs that are left to get. needed=di-utils-shell rootskel anna main-menu cdebconf-udeb udpkg busybox-udeb dash-udeb kernel-image-2.4.19-386-udeb choose-mirror net-retriever ethdetect netcfg-static netcfg-dhcp dhcp-client-udeb nic-modules-2.4.19-386-udeb nic-modules-shared-2.4.19-386-udeb modutils-basic isa-pnp-modules-2.4.19-386-udeb ; \ for file in `find localudebs -name *_* -printf %f\n 2/dev/null`; do \ package=`echo $file | cut -d _ -f 1`; \ needed=`echo $needed | sed s/ $package */ /`; \ done; \ if [ n = y ] ; then \ mkdir -p debugudebs; \ cd debugudebs; \ export DEB_BUILD_OPTIONS=debug; \ apt-get --assume-yes -o Dir::Etc::sourcelist=/home/sferriol/debian/debian-installer/build/sources.list -o Dir::State=/home/sferriol/debian/debian-installer/build/apt/state -o Debug::NoLocking=true -o Dir::Cache=/home/sferriol/debian/debian-installer/build/apt/cache source --build --yes $needed; \ cd ..; \ else \ echo Need to download : $needed; \ if [ -n $needed ]; then \ apt-get --assume-yes -o Dir::Etc::sourcelist=/home/sferriol/debian/debian-installer/build/sources.list -o Dir::State=/home/sferriol/debian/debian-installer/build/apt/state -o Debug::NoLocking=true -o Dir::Cache=/home/sferriol/debian/debian-installer/build/apt/cache -dy install $needed; \ fi; \ fi; \ Need to download : di-utils-shell rootskel anna main-menu cdebconf-udeb udpkg busybox-udeb dash-udeb kernel-image-2.4.19-386-udeb choose-mirror net-retriever ethdetect netcfg-static netcfg-dhcp dhcp-client-udeb nic-modules-2.4.19-386-udeb nic-modules-shared-2.4.19-386-udeb modutils-basic isa-pnp-modules-2.4.19-386-udeb Reading Package Lists... Done Building Dependency Tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Sorry, but the following packages have unmet dependencies: anjuta: Depends: gcc but it is not going to be installed or g++ but it is not going to be installed semi: Depends: emcs20 but it is not installable or mule2 but it is not installable or emacs21 but it is not going to be installed or xemacs21 or emacsen Depends: flim (= 1:1.14) but it is not going to be installed or clime (= 1.14) but it is not installable speedbar-beta: Depends: emacs21 but it is not going to be installed or emacsen E: Sorry, broken packages make: *** [net-get_udebs-stamp] Erreur 100 is there something that i've forgotten??? thanks sylvain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cvs commit to debian-installer/utils by kraai
* Matt Kraai | Had I fixed the original problem correctly, this wouldn't occur. | The right fix is to ensure that the shell has a controlling | terminal, so that /dev/tty will work. I don't know how to do | this, though, so you'll have to be patient while I figure it out | (or fix it yourself (please?)). /dev/console seems to work well, so I'm fixing applications to use that wherever I see references to /dev/vc/* now. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [d-i][patch] cdebconf and localized fields
* (Denis Barbier) | On Fri, Oct 11, 2002 at 01:20:53AM +0200, Denis Barbier wrote: | I am going to hack cdebconf in order to support UTF-8 encoded localized | templates files. As I am new to cdebconf, I prefer posting an early | patch, which is not tested, breaks modules (the template structure is | altered), etc. But at least there is a clean interface with localized | fields, and fixing the rest of the code should not be that hard. | Is it the way to go, or is this patch fully wrong? | | Okay, I fixed everything but wonder how to test it. It looks like | I need config and db files before being able to play with templates. | Would it be possible to have sample files in the CVS? build cdebconf using ./configure --with-frontend=text --with-db=rfc822db --with-conffile=./cdebconf.conf and just run make then enter the src/test directory, copy ../cdebconf.conf to ., change it to use ./templates.dat and ./questions.dat. run ../debconf-loadtemplate foo $templatefile and then finally ../debconf $configscript. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: todo?
On Wed, Nov 06, 2002 at 12:21:56AM +0100, Tollef Fog Heen wrote: Getting d-i to work on other arches than i386 is high-priority. I know talk is cheap, but I do intend to work on d-i for hppa and ia64. Just a matter of finding time to get started. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing with d-i: summary and notes
* Timothee Besset | Anyway the main problem is that once the params are entered, in case they | are wrong there is no way to enter them again. Use Alt-F1 or use Step 5 - | Open a shell to issue the reboot command, do network conf again, then run | through step 1 and try better params. We need to fix this somehow -- should we have a generic «reconfigure some item not on this list», which scans the status file, checks which are half-configured and configured and then runs dpkg-reconfigure on that package, or what? | You get spammed by messages like: | kmod: failed to exec /sbin/modprobe -s - net-pf-1, errno = 2 | that's noisy but harmless. see [4] FWIW, I have this fixed in my local build now. As you write: annoying but harmless. | Once base is installed, LILO setup. The direct step in the text UI can be | used, or directly issuing the command chroot /target liloconfig in the | shell. The strange thing is that I didn't end up with the same | /target/etc/lilo.conf wether I used one solution or the other. | | If rebooting now, none of the two LILO setup solutions would work. Kernel | panics with VFS: Unable to mount root filesystem. Tollef said to add an | initrd=/initrd.img to the lilo.conf. You can do this by echo | initrd=/initrd.img lilo.conf (in /target/etc) or use nano to edit the | file. The lilo setup is somehow broken; there is no initrd symlink in /target so just fixing lilo.conf won't help. I'm not sure how to fix this in a non-gross way. (A lot of the other issues noted here are already fixed or known issues with known, but unimplemented, solutions, so I won't elaborate further on them) -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to debian-installer/tools/netcfg/debian by tfheen
Repository: debian-installer/tools/netcfg/debian who:tfheen time: Wed Nov 6 12:25:57 CET 2002 Log Message: Make netcfg-dchp not ask about name servers and such -- those should be gotten from the dhcp server. Files: changed:changelog -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to debian-installer/tools/netcfg by tfheen
Repository: debian-installer/tools/netcfg who:tfheen time: Wed Nov 6 12:25:57 CET 2002 Log Message: Make netcfg-dchp not ask about name servers and such -- those should be gotten from the dhcp server. Files: changed:netcfg-dhcp.c netcfg.c -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udeb building in pbuilder fails?
* Mario Lang | This fails with some strange error, and I have no idea | why the pbuilder build should react differently then the dpkg-buildpackage | build. Does anyone have any hints? | | Here is the error I get when using pdebuild: | | dh_builddeb -pbrltty-udeb --filename=brltty-udeb_3.1-1_i386.udeb | dpkg --build debian/brltty-udeb ../brltty-udeb_3.1-1_i386.udeb | dpkg-deb: building package `brltty-udeb' in `../brltty-udeb_3.1-1_i386.udeb'. | dpkg-genchanges -mnobody@nowhere | dpkg-genchanges: warning: duplicate files list entry for package brltty-udeb (line 2) | dpkg-genchanges: warning: package brltty in control file but not in files list | dpkg-genchanges: warning: package brltty in control file but not in files list | dpkg-genchanges: warning: package brltty in control file but not in files list | dpkg-genchanges: warning: package brltty in control file but not in files list | dpkg-genchanges: including full source code in upload | dpkg-genchanges: failure: cannot open upload file ../brltty-udeb_3.1-1_i386.deb for |reading: No such file or directory | pbuilder: Failed autobuilding of package You need to use dh_gencontrol -Xbrltty-udeb dh_gencontrol -pbrltty-udeb -- -fdebian/files~ dpkg-distaddfile $(FILENAME) debian-installer $(PRIORITY) (with filename and priority set to the right values) -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Teach rootskel to call initscripts
* Mario Lang | As discussed some weeks ago on this list, some installer packages | may want to have some boot/initialize scripts run before | the actual installer action happens.. | | Since editing etc/init.d/rcS for every such thing is not | really nice, I've inserted a simple for loop there. | | Scripts should be put in /etc/init.d/SnnNAME. Uhm, no. if anything, they should be put in /etc/rcS.d. I have checked in a fix for this; can you please test that it works properly? -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to debian-installer/rootskel/debian by tfheen
Repository: debian-installer/rootskel/debian who:tfheen time: Wed Nov 6 12:32:17 CET 2002 Log Message: Run the scripts in /etc/rcS.d on bootup, if available. Files: changed:changelog -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to debian-installer/rootskel/src/etc/init.d by tfheen
Repository: debian-installer/rootskel/src/etc/init.d who:tfheen time: Wed Nov 6 12:32:17 CET 2002 Log Message: Run the scripts in /etc/rcS.d on bootup, if available. Files: changed:rcS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with apt-get
* sylvain ferriol | Need to download : di-utils-shell rootskel anna main-menu | cdebconf-udeb udpkg busybox-udeb dash-udeb | kernel-image-2.4.19-386-udeb choose-mirror net-retriever ethdetect | netcfg-static netcfg-dhcp dhcp-client-udeb nic-modules-2.4.19-386-udeb | nic-modules-shared-2.4.19-386-udeb modutils-basic | isa-pnp-modules-2.4.19-386-udeb | Reading Package Lists... Done | Building Dependency Tree... Done | Some packages could not be installed. This may mean that you have | requested an impossible situation or if you are using the unstable | distribution that some required packages have not yet been created | or been moved out of Incoming. | The following information may help to resolve the situation: | | Sorry, but the following packages have unmet dependencies: |anjuta: Depends: gcc but it is not going to be installed or | g++ but it is not going to be installed |semi: Depends: emcs20 but it is not installable or | mule2 but it is not installable or | emacs21 but it is not going to be installed or | xemacs21 or | emacsen | Depends: flim (= 1:1.14) but it is not going to be installed or | clime (= 1.14) but it is not installable |speedbar-beta: Depends: emacs21 but it is not going to be installed or |emacsen | E: Sorry, broken packages | make: *** [net-get_udebs-stamp] Erreur 100 The latter information here is only confusing. It has nothing to do with the real problem, which is that what's currently in the archive is non-working. You want to pull the udebs out of incoming or wait until tomorrow; I uploaded a huge bunch yesterday, which should get to mirrors tonight. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [d-i] libdebian-installer2
we don't need to bump soversion at all, unless we make backward-incompatible changes. just bump minor (and don't change the packaging name). Also, fix shlibs to depend on that version or later. But surely adding stuff to a data structure is a backward-incompatible change? It depends on the way you do it. You can add stuff to a data structure without breaking backwards compatibility. regards, junichi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Testing d-i with uml?
Hi. As mentioned, I'm working on accessibility support for d-i. As brltty will only fit on the cdrom target, I'll have to use cd install for testing. NOw since I don't have excess hardware, and esp. no cd burner, I need to find a way to test things in UML. The only thing I need there is /dev/ttyS0 in the UML-kernel connected to /dev/ttyS1 on the host system. That is so that I can connect a second braille dsiplay on the host system and use it like it were connected to S0 of the install-system. Now my questions are: 1. Does anyone already use uml for d-i cd testing? If yes, do you have any scripts written for that I could use? 2. Does anyone know if uml can do the device-forwarding I described above? I vaguely remember it does... -- CYa, Mario -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Teach rootskel to call initscripts
Tollef Fog Heen [EMAIL PROTECTED] writes: * Mario Lang | As discussed some weeks ago on this list, some installer packages | may want to have some boot/initialize scripts run before | the actual installer action happens.. | | Since editing etc/init.d/rcS for every such thing is not | really nice, I've inserted a simple for loop there. | | Scripts should be put in /etc/init.d/SnnNAME. Uhm, no. if anything, they should be put in /etc/rcS.d. Of course you're right. The reason I used init.d was that there was only one file there, and I wanted to avoid an additional inode for the /etc/rcS.d directory on the disk. But your way is certainly more UNIXish. -- CYa, Mario -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Testing d-i with uml?
On Wed, Nov 06, 2002 at 02:55:18PM +0100, Mario Lang wrote: Hi. As mentioned, I'm working on accessibility support for d-i. As brltty will only fit on the cdrom target, I'll have to use cd install for testing. NOw since I don't have excess hardware, and esp. no cd burner, I need to find a way to test things in UML. I don't know anything about UML, that may be a better way. But I've successfully used this strategy to test the CD-based pgi: I just use mkisofs as if I was burning the CD, but use a disk partition as the target. Then I boot that partition manually. -- *--v- Installing Debian GNU/Linux 3.0 v--* | http://www.debian.org/releases/stable/installmanual | |debian-imac: http://debian-imac.sourceforge.net | |Chris Tillman[EMAIL PROTECTED] | | To Have, Give All to All (ACIM) | ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cvs commit to debian-installer/utils by kraai
On Wed, Nov 06, 2002 at 11:26:02AM +0100, Tollef Fog Heen wrote: * Matt Kraai | Had I fixed the original problem correctly, this wouldn't occur. | The right fix is to ensure that the shell has a controlling | terminal, so that /dev/tty will work. I don't know how to do | this, though, so you'll have to be patient while I figure it out | (or fix it yourself (please?)). /dev/console seems to work well, so I'm fixing applications to use that wherever I see references to /dev/vc/* now. /dev/tty should work again, now that Erik has fixed BusyBox... Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: missing amigamouse device (?)
Hello Michel Am 05-Nov-02 schrieb Michel Dänzer: On Son, 2002-11-03 at 00:39, Andreas Wüst wrote: I couldn't find any mouse device for a normal Amiga mouse connected to the mouseport. I luckily had some advice from earlier days to create it as follows: # cd /dev/input Do you really mean this or just /dev? Ok, caught him. The problem is non-debian specific, so no need to send followups to debian-boot (to be precise, it is neither apus specific, it is specific to this strange guy who started this thread..). When helping Björn Johansson, I sent him my XFConfig, which contained this /dev/input/amigamouse thingy. He wrote back that this wouldn't work, so I advised him how to create the amigamouse device. But then I wondered why it isn't automatically included in the debian base installation. Well, it is, but not in /dev/input but in /dev. So how did I think it should be in /dev/input? I don't know!! I just don't know. I just sent him my config where it refers to /dev/input (which I neither know why this is like that), and he realised that this device doesn't exist. So please forget my post (lucky me i placed a question mark at the end of the subject, so I am not totally disgraced now..)! # mknod amigamouse c 10 4 Or either of MAKEDEV misc MAKEDEV m68k-mice fine. Or just forget it.. PS: It would still be nice to have it mentioned during X configuration (as well as that Amiga users have to choose the BusMouse protocol).. -- Best wishes, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Hi,
it seems nobody ever reported a successfull install with tftpboot.img.
Here's how I did it:
1. From .../woody/main/disks-i386/3.0.23-2002-05-21, I got the files
compact/tftpboot.img
images-1.44/root.bin
2. On my DHCP server, I installed the mknbi package and created an
etherboot image using the command
mknbi-linux --output=tftp-etherboot.img --param=root=/dev/ram
tftpboot.img root.bin
3. I configured the DHCP server:
group {
filename tftp-etherboot.img;
next-server xxx.xxx.xxx.xxx; # my DHCP server
host client { fixed-address yyy.yyy.yyy.yyy;
hardware ethernet aa:bb:cc:dd:ee:ff;
}
}
4. I got an etherboot image from rom-o-matic.net. I chose version
5.0.7, as .lzlilo file for my eepro100, and put it onto a bootable
syslinux floppy.
5. I booted from that floppy. Etherboot loads, identifies the network
card, gets an IP address, and tftp's my image file, which boots and
starts into dbootstrap normally.
May this be a confimation that the proposed patch by Michael Schwarzbach
indeed works.
HTH,
Alex
--
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to debian-installer/tools/netcfg/debian/po by barbier
Repository: debian-installer/tools/netcfg/debian/po who:barbier time: Wed Nov 6 12:59:25 MST 2002 Log Message: Update, by Philippe Batailler Files: changed:fr.po -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to debian-installer/tools/netcfg/debian/po by barbier
Repository: debian-installer/tools/netcfg/debian/po who:barbier time: Wed Nov 6 14:39:44 MST 2002 Log Message: Proofreading [Norbert Bottlaender-Prier] Files: changed:fr.po -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Goals for alpha release
I'd like to get an alpha release of d-i out the door soonish. Most pieces are there already, but some few crucial pieces are still missing. - ftp priorities need to be adjusted. They are used by anna for deciding what modules to install. - cdrom installs, checking whether it actually works at all. Fix bugs, test. - mkfs/mkswap, mkswap-udeb is not in the archive, mkfs is currently called by hand. I have code for doing this which I just need to test - testing. The whole installer needs to be better tested.. I can't test my own code well enough, so we need somebody to actually run through this code and try to break it before we let it loose on our users. Test cd installs, test net installs, test various partition setups, etc. - fix lilo-installer. lilo-installer doesn't do initrds ATM. That means booting is broken. Anything which creeps up on us and is obviously broken and must be fixed will also have to be fixed before we can stick the «alpha» label on it. A few more fluffy goals for beta release, as aj put it when I talked with him tonight: «well, i'd make my alpha release goal be something works, my beta be something works well.» So, my fluffylist is somewhat like: - slang, other frontends, gtkfb? Some work has been done, but nothing solid has come from it yet. We need to do something clever if we are going to have X-based installs. X udebs would be stretching the concept a bit far. - automated installs. I have begun hacking on cdebconf to support stacking. Once that is in place we need to have a http backend or something and this might actually fly. - porting. We need the ports going soon. BenC has said he is going to work on porting to SPARC in the next week or so, the powerpc port seems to have stalled, I am not sure about the alpha port status is, nor most of the others. That is, I assume they are non-existent until they prove otherwise. - testing drop-ins of components, like evms. d-i is modular. I think it should be possible to replace the normal fdisk and mkfs routines just by dropping in the right evms udeb and selecting that. We need to check that it works and fix any bugs there. - reconfigure arbitary package. Some packages, like choose-mirror use debconf when configured, but they are impossible to reconfigure. Having a method to reconfigure them would be useful. Actually, it might be so useful and easy to implement that I want it for alpha release. Anyhow, this is probably not a complete list at all, just me trying to organize my thoughts so we can actually get a working installer out the door in the not-too-distant future. Cheers, and thanks for the good work done so far, -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
