Mail Archives: opendos/1997/03/29/00:43:08
I could see opening this up as an option, probably better to include
rcs with opendos and have rcs do revision control on boot.log for
space saving purposes as well. That way the user has a date and time each
boot was done and probably rcs should also manage config.sys and autoexec.bat
too, that way it's potentially easy to back out of a recent change if the system
blows provided the user has a boot disk.
Should probably have a backout.bat file written to back one version up and
overwrite the current autoexec.bat and config.sys files too.
On Fri, 28 Mar 1997, Colin W. Glenn wrote:
> On Fri, 28 Mar 1997, Jude DaShiell wrote:
> > I just thought of something, the config.log and autoexec.log files should
> > always generate on a boot. If there were no errors in config.sys when
> > the machine booted then config.log could be erased.
>
> Hmmm, set up the erase as an option, people might want to review the log
> record for who knows what reason.
>
> > If there were no errors in autoexec.bat then autoexec.log could
> > be erased. Boots should do destructive writing of these log files.
>
> Yea, open the sucker in open-for-write instead of open-append
>
> > I know systems especially the faster ones boot up too fast even for
> > people with 20:20 vission to read the screen much of the time and this
> > feature were it implemented would remove that requirement.
>
> OpenDOS should also support single-stepping the boot as well.
>
> ---
> C*E*A <a href="http://www.amused.com/">.</a>
> Micromint Home Page <a href="http://www.micromint.com/">.</a>
> Totally Barbie <a href="http://www.primenet.com/~jesica/">.</a>
>
>
jude <jdashiel AT eagle1 DOT eaglenet DOT com>
- Raw text -