If it turns out that the other implementations arn't close enough to what is
needed I'd like to know whether there are features which should be implemented
(in the hack program that is). Does it need to treat stdout/stderr in a
different way (we can capture both independently or let them through).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 17 May 2004 22:28, Jon Peatfield wrote:
> While reading debian-installer/installer/doc/TODO I spotted the
> following:
>
> * There needs to be a centralised logging method. Syslog will do, but
>we currently have a lot of nasty code that
[Jon Peatfield]
> While reading debian-installer/installer/doc/TODO I spotted the
> following:
>
> * There needs to be a centralised logging method. Syslog will do, but
>we currently have a lot of nasty code that appends messages to
>/var/log/messages directly. All of that would be conver
While reading debian-installer/installer/doc/TODO I spotted the
following:
* There needs to be a centralised logging method. Syslog will do, but
we currently have a lot of nasty code that appends messages to
/var/log/messages directly. All of that would be converted to pipe
it to logger.
4 matches
Mail list logo