Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

freebsd > 14.0-RELEASE uses /home not /usr/home #5850

Open
dch opened this issue Oct 31, 2024 · 2 comments
Open

freebsd > 14.0-RELEASE uses /home not /usr/home #5850

dch opened this issue Oct 31, 2024 · 2 comments

Comments

@dch
Copy link

dch commented Oct 31, 2024

In upstream the move of /usr/home to /home is documented, and there are several prior commits
that update the machinery during the installer and elsewhere.

This needs to be adjusted in cloud-init also, but only > FreeBSD 14.0-RELEASE:

home_dir = "/usr/home"

Currently I'm proposing to address this as a FreeBSD ports patch, where we have
tooling to accommodate per-version patching in the ports tree:

https://reviews.freebsd.org/D47338

Should this be upstreamed to cloud-init?
If so, what sort of trick would you suggest to make this OS version-aware?

@holmanb
Copy link
Member

holmanb commented Nov 1, 2024

Should this be upstreamed to cloud-init?

Yes, we can upstream it.

If so, what sort of trick would you suggest to make this OS version-aware?

Hmm, not sure. One approach would be to avoid carrying the patch forever by could upstreaming this change and then inverting the patch version check so that it only sets home_dir = "/usr/home" on ${OSVERSION} < 1400000. Whenever you drop support for pre-14.0 then the patch can be dropped.

Thoughts?

@emaste
Copy link

emaste commented Nov 1, 2024

FWIW the expected EOL for the final FreeBSD 13.x release is April 30, 2026.
https://www.freebsd.org/security/#sup

inverting the patch version check

Indeed, it seems that would clearly indicate intent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants