Putting a complete file system in a version control system

I am currently working on a PXE boot environment that I would like to contribute to version control.

The file system and server will be Linux (SLES, if you know).

I considered using some kind of hack that retains file ownership / permissions through getfacl -R -P, but this does not apply to symbolic links or devices. And this is disgusting.

Difficult things I need to cover:

  • file ownership
  • File Permissions (No ACLs)
  • devices
  • symbolic links

Are there any version control systems that will cover my needs?

Note. Instead of “block volume”, I need to put the “file set” in the revision control and save the individual changes.

+3
source share
4 answers

I'm sure Perforce will handle all of these things. I believe that another group at work uses it for almost the same purpose as you (keeping the Linux option for the embedded device).

+2
source

etckeeper is a tool that places the contents of / etc in a version control (with a choice of version control systems). It has a layer on top that takes care of permissions, symbolic links, etc. I'm not sure if it handles device nodes - maybe not, but it could probably be easily expanded for this.

You may find that this tool can be adapted to handle the entire file system.

+2

, , .

:

, , .

: .

+1

, , , . , .

+1

Source: https://habr.com/ru/post/1722389/


All Articles