neuroserve: thanks, I never heard of it. I’ll give it a look.

Any suggestion about that error with sccs? It happen me only in OmniOS by now.

Reading back, Git is a great tool for managing a larger code project and plenty of people do understand it. There is a bit of a learning curve to it though

I would suggest its not the right tool for managing an odd config file or data file in /etc though

reading the man page man.omnios.org/man1/sccs#create~2 it looks like the ,test.conf is the original file.

I'm also wondering what happens if you try with a fresh file in your home dir (im wondering if there's a perms issue or stuff hanging around from earlier tests)

Already tried in different path and using different OmniOS hosts. Same error everywhere.,test.com is supposed to be safely manually removed after test.conf entered SCCS, and in fact in FreeBSD it works, but not in OmniOS :(

No test.conf file appears in current dir after the “ge23” error. SCCS/s.test.conf however is created, but any checkout command fails.

I just tested again in fresh-installed systems: sccs in FreeBSD works like a charm, even though I still have to learn how to do a lot of stuff, but I'm able to do basic check-in/out, show diffs, and change history log. I'm stuck only in OmniOS with that error.

Here is the version running in OmniOS: "sccs schily-SCCS version 5.09 2019/01/02 (i386-pc-solaris2.11)"

The one in FreeBSD: "sccs schily-SCCS version 5.09 2020/10/07 (amd64-unknown-freebsd14.1)"

no one here is successfully using SCCS in OmniOS?

warden: I just had a play in a zone and get a similar error to you, it looks like the part with the error is the sccs get step (I get a similar error issuing /usr/ccs/bin/sccs get test.conf)

also a similar error using /usr/xpg4/bin/sccs create -o test.conf

m1ari: maybe I hit my first bug in a OmniOS package!? :)

I wonder if there's something about the format of the history file in SCCS/ the get command doesn't like

I'll try to compare history file contents between FreeBSD and OmniOS versions of sccs ASAP

Other than that I'm afraid I don't have much idea, I'm guessing not many use sccs these days

I think most people either just edit files and forget what they've done, or have some external documentation of changes.

of they're managing enough systems that it makes sense to use one of the many config management tools (ansible, salt, puppet, chef etc)

surely I guess there are not many sccs users out there nowadays. May I ask if someone here is using something to manage config file revisions, and what?

m1ari: in this regard, I started using salt months ago and I liked it very much, but I didn't find in omnios neither omnios.extra repos. What are you using to manage config files revision in your servers, if may I ask?

currently just a wiki/documentation as it's only things I'm playing with. In the past I've used chef for managing a range of systems