i don't see why you'd want to do that, unless you
are using a linux-from-scratch-like distro or a
DIY one. considering most distros today update
their packages via internet, and that the binaries
may change.
another thing would be to use svn (or another
VCS) to store history or status of configuration
files, such as /etc, etc ...
i do this for many of the machines i use either
at home (with bzr) or at work (with svn).
2007/4/5, John Stile <john@stilen.com>:
> Can I get any advice or links regarding checking in an entire / of a
> Linux system?
>
> Are there any pitfalls?
>
> To deploy a new system, could i simply do a svn checkout onto an empty
> file system?
>
> I use gentoo, and when I do an update sometimes things stop working, but
> I need to be able to get back to what did work, and track what did
> change on an global system level. Just backing up config files doesn't
> help me version control the entire system.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 6 05:51:03 2007