/usr/local on separate partition

[balanga]

When installing FreeBSD, is it possible to have /usr/local on a separate partition?

 

[DutchDaemon]

Yes.

 

[DutchDaemon]

Well, local/ on a separate partition , mounted inside /usr/.

 

[mer]

My opinions only.

UFS or ZFS? That can be a big factor in the answers you get.
If UFS, then sure, you probably need to drop to a shell or manually partition from the installer

If ZFS, the answer depends on if you want to use Boot Environments. If no BEs, then sure you can probably put /usr/local in it's own dataset but since some services during startup may also live in /usr/local I'd be careful about when datasets are mounted.

 

[Alain De Vos]

I have done /usr/local on a separate partition.
But it gave me a linker problem.
I had to explicit run a command to tell the linker to also look in /usr/local for libraries.

 

[jbo@]

I had to explicit run a command to tell the linker to also look in /usr/local for libraries.

Why not just mounting it appropriately? As long as "the data" is accessible via /usr/local it generally shouldn't matter where it is actually stored physically.

 

[Alain De Vos]

Note : I did a appropriately mount...
My wild guess is some linker commands are run before the mount happens.

 

[mer]

Note : I did a appropriately mount...
My wild guess is some linker commands are run before the mount happens.

man ldconfig
"configure the dynamic linker search path for shared libraries"

is about the only thing I can think of that could do this. But: in theory if something lived at /usr/local/lib where local was a subdirectory on /usr partition moving it to /usr/local/lib where /usr/local was a new partition it should still be fine.
But I could be wrong.

 

[Alain De Vos]

This was the command i had to run to fix it:

ldconfig -v -m -R /usr/local/lib

 

[PMc]

I'm wondering if a /usr/local directory does even exist after installing. It shouldn't. It is only used for things managed by pkg.
At a new quarterly ports branch I do pkg upgrade -f, and then find /usr/local -type f -ctime +1, and there are no old files there (except config files I created).

 

[mer]

This was the command i had to run to fix it:

ldconfig -v -m -R /usr/local/lib

Yep that I would have expected to fix it.

As for /usr/local existing after installing, I'd guess "the directory would exist but may not be populated". PMc since pkg upgrade installs new ports I find your output "expected".

 

[PMc]

PMc since pkg upgrade installs new ports I find your output "expected".

Yes, that's simple and fast housekeeping. If there is anything there except config files, it probably shouldn't be there.

 

[yuripv79]

If there is anything there except config files, it probably shouldn't be there.

It all got much better with "staging" step that will fail the build if there are extra files being installed compared to plist.

 

[yuripv79]

This was the command i had to run to fix it:

Use service ldconfig restart instead; though I'm wondering why you had to do that at all, did you break the cache by running the command manually without specifying -m?