or we could simply make everyone happy:
make saving to anothet hard disk image an _option_. and just issue
a big fat warning when and if files in a freeze state has changed.
> Hey! Why shouldn't people be able to edit their disk images??? :-(
> I do it all the time when I use Windoze.... Quite fun to
> corrupt filenames, ya
> know... ;-P
>
> Eric Laberge wrote:
>
> > At 15:31 2000-12-15 +0100, you wrote:
> > >On Fri, Dec 15, 2000 at 08:14:08AM -0500, Drew Northup wrote:
> > >
> > > > How big are your disk image files? 640KB? Mine is
> 504MB!!! This IS NOT A
> > > > GOOD SOLUTION!!!
> > >
> > >Who fucking cares ? I have 40GB free disk space which cry
> to be filled ? ;-)
> > >And my image is ~900MB.
> >
> > 900MB? How did you get around the 1024/16/63 504MB limit? :-P
> >
> > > > Remember two things: Keep It Simple Stupid (why many of
> my Data Structures
> > > > Programs just didn't work)
> > > > and
> > > > whatever is the fastest, the smallest (least memory
> used--of any kind), and
> > > > the simplest--all at once--is the best code.
> > >
> > >Well, I can think of nothing which will work in more cases. I guess
> > >we can avoid copying the disk image if the user promises not to
> > >touch it :-) OTOH, copying it would always work, no matter what
> > >the user does. So this qualifies for me as "more simple".
> >
> > Can't we just save the file modification date, and only
> restore if it
> > wasn't changed?
> > Of course, the user could touch the file in which case it
> wouldn't work,
> > but who is stupid enough to do that?
> >
> > EL
>
>
