Re: f2fs-tools and file locations

On Mar 21, 2019, at 01:46 PM, Ken Moffat <[email protected]> wrote:
On Thu, Mar 21, 2019 at 07:10:46PM +0000, Hans Malissa wrote:
Hi,

I'm playing around with the "Flash-Friendly File System" (f2fs), and I've installed f2fs-tools (https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/about/), the utility package for the f2fs. Building and installing worked nicely, and the mkfs and fsck tools seem to be functioning properly. The only thing that I'm not sure about is where to place the installed files in a LFS-compatible way. I'm aware that f2fs is not part of LFS or BLFS, so I'm addressing this question to the lfs-chat group only.
I've followed the instructions given in the f2fs-tools package closely. I did not specify a --prefix when running ./configure, which makes it default to /usr/local (which is okay for a first test). I disabled static libraries and se-linux support, and enabled shared libraries.
Here's a list of the files that were installed in /usr/local (the default prefix):

/usr/local/sbin/parse.f2fs
/usr/local/sbin/f2fstat
/usr/local/sbin/sg_write_buffer
/usr/local/sbin/mkfs.f2fs
/usr/local/sbin/fsck.f2fs
/usr/local/sbin/fibmap.f2fs
/usr/local/sbin/f2fscrypt
[...]
/usr/local/lib/libf2fs_format.so.5.0.0
/usr/local/lib/libf2fs.so.6.0.0
[...]

Now I'm wondering where to place these files for a system-wide installation (and possibly for using f2fs as a root file system in the future):

1. I guess the man-pages can go into /usr/share/man - I don't see any alternatives to that.
2. I'm not sure about the headers; I'm guessing /usr/include would be appropriate.
3. The *.la files in /usr/local/lib can be deleted.
4. The shared libraries in /usr/local/lib and the the programs in /usr/local/sbin: I'm really not sure. Should it be /usr/lib and /usr/sbin or /lib and /sbin? During the installation of e2fsprogs in LFS, we specified /lib and /sbin. During the installation of dosfstools in BLFS, we even used '--prefix=/' in order not to place the files in subdirectories in /usr.
Any thoughts on this?
Greetings,

Hans

I don't know what most of those programs do, but it is fairly
obvious that if you have a split /usr, which LFS still (claims to)
support, and the rootfs is using f2fs, then its fsck needs to be in
/sbin and whatever libraries it uses needs to be accessible when
/usr is not mounted.

Same for any of the other progs which are essential to your normal
operation.

I say LFS still claims to support split /usr because I'm not aware
of anyone who actually puts /usr on a separate partition. I expect
I'll now be deafened by the people who do that ;)

And if the f2fs filesystem *is* encrypted (I assume fsfscrypt is for
that) and is the rootfs, you might need to use an initrd. But for a
root on flash you might want to do that anyway, to use the UUID for
mounting an external stick.

For booting f2fs, the Arch wiki suggests that grub might need to be
patched (or a separate boot partition).

ĸen

Thanks for the explanation. Generally speaking, does this mean that the strict separation between /usr/sbin and /sbin (same for /bin and /lib) is non-essential for systems with /usr on the same partition as root?
I'm not using encryption, and I'm also not using grub (I'm booting from an efistub kernel), so I won't need an initrd or a patch fro grub.

Hans

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-chat
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page