https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161481
Nick Hibma <n_hi...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |n_hi...@freebsd.org
--- Comment #3 from Nick Hibma <n_hi...@freebsd.org> ---
In our NanoBSD builds we use nullfs to provide a dir with packages to install.
I changed the MAKEOBJDIR to include the full path to working directory to
provide a means to separate multiple images and versions of images.
nullfs couldn't handle the length of that path. I am -very- surprised that
nullfs is not able to handle MAX_PATH length paths.
Our workaround is the use the MD5 of the full path instead of the path itself:
# XXX Take the MD5 of the path as mount_nullfs (for packages) does not handle
long paths. See
# FreeBSD PR kern/161481.
p="$(echo "$PWD" | sed -Ee 's#^/((usr)?/home|Users)/##' | md5)"
NANO_OBJ=${NANO_OBJ:-"/usr/obj/nanobsd/$p"}
I do understand that this is actually a rather complex little bug, as it goes
across a number of APIs.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
