-
dlyundGood evening all. I'm sure I must be doing something wrong but I can't for the life of me figure out what:
-
dlyundI've made a small change under oamuser to remove some unwanted output when creating the users home directory using `cpio`; I've compiled and installed the change into the proto area using `make install`, created a boot environment using `omni onu oamuser-quiet-cpio`, and booted into it (confirmed using `beadm`), but the version of `useradd` I'm
-
dlyundexecuting does not appear to be mine (I added a `printf` to `main` after going through this cycle a few times and no output.) I am following the basic workflow in illumos Developer's Guide with the exception of using the `omni` command enter the build environment using `omni env` and creating the boot environment using `omni onu`.
-
dlyundAny suggestions would be most welcome!
-
dlyundI have confirm that my changed binary is under the `*-nd` directory, and the help output for `omni` states that `omni onu` uses the non-debug packages by default, so I would expect it to use the binaries from the `*-nd` directory.
-
andyfThe `onu` command uses the packages which are under `packages/` in the root of your tree.
-
andyfpackages are built from proto, but if you have just done a `make install` to install the new binaries to proto, you need to rebuild the packages
-
andyfI assume you're in a bldenv since you were able to make install, so just go to `usr/src/pkg` and do `dmake install`
-
andyf(dmake will run things in parallel by default, make runs things serially by default, they're otherwise the same and you can also use either with -j to set the parallelism)