On Sat, Mar 31, 2018 at 11:03:39PM -0400, Jude DaShiell wrote:
>If in the course of a debian install I need to execute a shell and logs are
>being preserved, will what I type in the shell also be saved to one of the
>log files?
Not by default, no.
>I have a procedure to get a secure wifi login do
If in the course of a debian install I need to execute a shell and logs
are being preserved, will what I type in the shell also be saved to one of
the log files? I have a procedure to get a secure wifi login done after
reboot and post-install and this way I could send logs and it would be
avai
Quoting Joey Hess (jo...@debian.org):
> Christian PERRIER wrote:
> > Do you think that the feature you wished to have in D-I (ability to
> > run D-I from a script with all output logged as well as timings
> > recorded...and ability to save installation logs in the target) is
> > addressed by change
Christian PERRIER wrote:
> Do you think that the feature you wished to have in D-I (ability to
> run D-I from a script with all output logged as well as timings
> recorded...and ability to save installation logs in the target) is
> addressed by changes we made since then in D-I (for instance the
>
Dear user (aha...),
Do you think that the feature you wished to have in D-I (ability to
run D-I from a script with all output logged as well as timings
recorded...and ability to save installation logs in the target) is
addressed by changes we made since then in D-I (for instance the
installation-r
Package: installation
Severity: wishlist
If there were a udeb with /usr/bin/script in it, then we could arrange
for the linuxrc to run d-i inside script, logging all output. We could
even collect timings data too. This information could be saved to
/target/var/log, and whole installs could then be
Massimo Dal Zotto wrote:
> I've not explained myself. I'm not speaking of starting the install
> process from the /etc/init.d scripts, which would have the inconvenient
> that you described.
> Instead I'm proposing of using the initscript(5) optional script which,
> if present, will be used to co
> Atually you can, you just have to be creative. See base-config for one
> creative way to do it with $SHELL.
>
> (I filed a bug on script asking for an easier way to specify a command
> to run some time ago.)
>
You can fool script with the $SHELL trick but you can't supply an argument
to the c
Massimo Dal Zotto wrote:
> Another thing I did in my installer was to copy the logs produced by the
> bootfloppy installer during the first phase into the final logfile in the
> target partition.
Well the boot floppies have done that for a while now.
> Regarding the implementation of the whole t
> I've got an idea -- I think it'd be nice if base-config runs all or part
> of itself under script, with output going to /var/log/something. The
> idea being this will produce very handy typescripts for testing now, and
> later on will be useful too. (No more incoherent whining "something
> broke
I've got an idea -- I think it'd be nice if base-config runs all or part
of itself under script, with output going to /var/log/something. The
idea being this will produce very handy typescripts for testing now, and
later on will be useful too. (No more incoherent whining "something
broke"? Probabl
11 matches
Mail list logo
