On Thu, Dec 05, 2002 at 03:37:48PM +1000, Anthony Towns wrote: > On Thu, Dec 05, 2002 at 03:22:20AM +0100, Tollef Fog Heen wrote: > > The following stuff is still missing: > > - reporting tool (code to write, non-trivial) > > A good aim is probably to make this as trivial as possible. A possibility > is to store the udebconf database in /target just before rebooting (it > shouldn't be too hard to ensure udebconf has quit by then), and have > base-config propose a template mail based on /proc/cpuinfo, free, the > templates file, and allow it to be edited and mailed by the user. It makes > more sense to refine it once you know how it's going to be used, anyway. Since we must make sure nothing is printed to stderr by anything (it would screw up all frontends but text), we should somewhere redirect all of that into a log file, that could be copied into /target as well. I'm not sure what the best place for doing that is... The debian-installer script? main-menu? /Martin -- Martin Sjögren martin@strakt.com ICQ : 41245059 Phone: +46 (0)31 7710870 Cell: +46 (0)739 169191 GPG key: http://www.strakt.com/~martin/gpg.html
Attachment:
pgpqi3pyQ9hEx.pgp
Description: PGP signature