[Erik Andersen]
> It can be configured to create archives if you need it. Since this
> far there was no need, there was no need to waste space on such
> things, so archive creation was disabled.
Yes, please. If the size change is neglectable.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
On Sun Dec 08, 2002 at 11:22:17PM +0100, Petter Reinholdtsen wrote:
>
> [Tollef Fog Heen]
> > lspci output would be good as well.
>
> I made a small udeb to store debug info on a floppy. Unfortunately
> this did not work as busybox tar is unable to create archives. This
It can be configured to
[Martin Sjögren]
> 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
> deb
[Tollef Fog Heen]
> lspci output would be good as well.
I made a small udeb to store debug info on a floppy. Unfortunately
this did not work as busybox tar is unable to create archives. This
udeb was going to copy all the content of /var/log/ into the archive,
and run the following script to fe
* Martin Sjögren
| I'm not sure what the best place for doing that is... The
| debian-installer script? main-menu?
/sbin/debian-installer would be best, IMHO. So it will just be run
when debconf is actually running.
You fix?
--
Tollef Fog Heen
* Anthony Towns
| 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 /tar
On Thu, Dec 05, 2002 at 04:23:17PM +0800, [EMAIL PROTECTED] wrote:
>
> [EMAIL PROTECTED] said:
> > 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 in
[EMAIL PROTECTED] said:
> 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... T
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 possibilit
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
I'm hoping for an alpha this weekend.
The following stuff is still missing:
- reporting tool (code to write, non-trivial)
- add mkswap (should be trivial, might need a busybox upload)
The following things are done, but could use a little testing:
- menu ordering (uploaded today)
- check that the
11 matches
Mail list logo
