>Uses are many. Mostly I got them from user feedback. >For instance, if you wanted to demo some software and >let users muck with it as much as possible, you could >use this. Then you always revert back to a known >state to undo their damage. > >If you want to install some software, but it hoses your >configuration, then you can revert. > >When I say "revert", I mean only to bother committing >changes since the last commit. We don't have to >do any complex roll-back. Hm, but aren't these things for os'es and admins? Or perhaps tools for os'es? plex86 is for virtualizing only, no? jens
- Re: Disk access architecture for plex86 Phil Levis
- Re: Disk access architecture for plex86 Kevin P. Lawton
- Re: Disk access architecture for plex86 Ulrich Weigand
- Re: Disk access architecture for plex86 Christian Laursen
- Re: Disk access architecture for plex86 Kevin P. Lawton
- Re: Disk access architecture for plex86 Julian Hall
- Re: Disk access architecture for plex86 Alexander Kellett
- Re: Disk access architecture for plex86 Kevin P. Lawton
- Re: Disk access architecture for plex86 Ramon van Handel
- Re: Disk access architecture for plex86 Kevin P. Lawton
- Re: Disk access architecture for plex86 Jens Nerche
- Re: Disk access architecture for plex86 Kevin P. Lawton
- Re: Disk access architecture for plex86 Phil Levis
- Re: Disk access architecture for plex86 Kevin P. Lawton
