Poudriere Image Question

[Phishfry]

I want to change the root user shell inside a poudriere image.

I could do this with -c /overlay if I knew where chsh stores its user settings.

What is a good approach to switching shell at image creation time?

 

[Phishfry]

More dumb questions.

I am trying to slim the size of the -t usb image and I see a huge directory.
/mnt/usr/lib/debug/usr/bin

 29M    llvm-size.debug
 32M    llvm-objcopy.debug
 33M    llvm-symbolizer.debug
 35M    llvm-ar.debug
 37M    llvm-profdata.debug
 38M    llvm-cov.debug
 39M    llvm-nm.debug
 40M    llvm-readobj.debug
 41M    llvm-objdump.debug
226M    ld.lld.debug
329M    lldb-server.debug
421M    lldb.debug
434M    clang.debug

It looks like the whole /usr/lib/debug directory is not needed.

How do I not build with this? Am I missing an option? Obviously I can add to exclude.list.
But to fix at poudriere jail would be best. DNODEBUG ?

poudriere jail -a arm64.aarch64 -c -j rock3a -v 15.0-CURRENT -K GENERIC-NODEBUG -b -J40 -m src=/usr/src -x

 

[Phishfry]

It looks like /usr/local/etc/poudriere.conf has a setting that is relevant.
Will this help me? I am literally guessing here.

# Set to pass arguments to buildworld.
# Default:
#MAKEWORLDARGS="WITHOUT_LLVM_ASSERTIONS=yes WITH_MALLOC_PRODUCTION=yes -DMALLOC_PRODUCTION"

I did exclude the debug files for a much slimmer build.

/dev/md0p2           1.8G    791M    932M    46%    /mnt

Poudriere Image is really what I need to replace many embedded builds.

This helped me too:

BSDRP/poudriere.etc/poudriere.d/excluded.files at master · ocochard/BSDRP

BSD Router Project. Contribute to ocochard/BSDRP development by creating an account on GitHub.

github.com

I just excluded the basics. 791M root directory is really nice.

*.a
usr/src
usr/lib/debug
usr/lib32
usr/tests

I got sick of waiting around and crosscompiled on amd64 with 40 cores.
poudriere image -t usb -s 2G -j rock3a -h rock3a -n rock3a -c ./overlay/rock3a -X excluded.files

 

[Phishfry]

As for root user shell question I see /etc/login.conf as a way to set shell without messing with master.passwd.
I would have to do something with database.

# Remember to rebuild the database after each change to this file:
#
#    cap_mkdb /etc/login.conf