Consider, for example, you upgrade from Ubuntu 20.04 to 22.04, and have updated the sudoers file. When upgrading, you get a prompt showing a diff between the new version and your customized version.
And quoting a bit from your reply... > compare the distributed /etc to what you already have to see if possible > other changes may be desired. "compare the..." Normal diff, git diff... /untouched/etc/ /custom/etc (git) diff against both to see what we customized. create a patch /new-untouched/etc/ /new-custom/etc/ Here, I'm saying /new-custom/etc/ can be created by doing a git apply of the patch from earlier. I mean... creating patches is quite common to keep just the delta, on a version-controlled repository. If it still doesn't make sense, it would be good to correct my understanding... without being pointed to the git website :) - KB ------- Original Message ------- On Tuesday, June 6th, 2023 at 9:29 PM, Mark Zelden <m...@mzelden.com> wrote: > On Tue, 6 Jun 2023 03:15:46 +0000, kekronbekron kekronbek...@protonmail.com > wrote: > > > I do wonder... with git now available, and this being normal USS, maybe > > zOSMF can start formally adopting/requiring git. > > Then, moving updates from these files onto newer versions is a matter of > > applying git patches on the new ones, where possible. > > Something that the zOSMF UI can accomodate. > > > > Do let me know if this doesn't make sense lol. > > > No, that makes no sense. Think of /etc as the SYS1.PARMLIB for z/OS Unix. Any > customization to > existing files should not be touched. That is why it only makes sense to copy > what's new into it > and also compare the distributed /etc to what you already have to see if > possible other changes > may be desired. I can't think of many required changes of the years but when > there are > they are (or should be) in the migration manual or upgrade workflow for > current versions. > > Regards, > > Mark > -- > Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS > ITIL v3 Foundation Certified > mailto:m...@mzelden.com > Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
