10:32:42 Good afternoon all. I seem to be stumbling over something basic. I'm following the instructions to build OmniOS (bloody) for the first time and while running the omni tool. I reach a password prompt in order to install developer/illumos-tools, which failed because I hadn't setup sudo, so I created the sudo group and enabled sudo sudo rights for 10:32:43 that group. Now I am trying to add user to the sudo group using `usermod -G` and am getting the message `UX: usermod: marksmith is currently logged in, some changes may not take effect until next login.` Checking my `id` after logging back in (and rebooting), the sudo group is not listed. 10:34:09 There is no `userinfo` command that I can find, and `id` usually works fine in it's absence, so I'm sure I'm doing something silly. Could someone point me in the right direction please? 10:38:12 Ok, I got it! Apparently `id -a` is needed to print any additional groups. 10:38:52 If you're using the illumos `id` in /usr/bin then you would need either the -a flag, or the id in /usr/gnu/bin or /usr/xpg4/bin 10:39:54 Or I find the `groups` command a bit more readable 10:53:31 ptribble Thank you :-). `groups` is indeed more readable. 10:54:30 In general does Solaris/illumos/OmniOS include variants of tools from multiple userlands? 10:55:52 I'm used to it being either-or, in that on BSD I expect a BSD userland with BSD tools, and on GNU/Linux I expect a GNU userland with GNU tools. The inclusion of more than one system is very interesting. 11:09:53 It varies based on the distribution, but the illumos-gate includes a lot of userland, but not enough to make a distribution. 11:10:14 I think of it as somewhere between Linux (the kernel) and FreeBSD (the world). 11:10:33 Different distributions augment what's available in their own way - OmniOS adds tools from various places, including GNU. 11:10:52 Some distributions replace more of the illumos-gate userland with GNU 11:11:44 The GNU tools are also under /usr/gnu/bin, so some people like to set their path to have that directory first and have a slightly more familiar experience when coming from other systems. 11:12:35 OmniOS is illumos-gate + omnios-build, and there is omnios-extra for additional packages that are outside of the release cycle. 11:12:55 (there are small number of other pieces like pkg5, but that's most of it) 11:19:15 andyf That makes sense, and is kind of neat, thanks :-). I'm trying to learn illumos/OmniOS so I think I'll stick to the illumos userland as much as possible. 11:21:04 The more I learn about illumos the more I (think I) understand how it sits in the middle between Linux and the BSDs, even down to things like licensing. 11:37:17 Is it expected that you run the `omni` tool with root permissions? 11:39:14 Not in general, no. 11:39:36 `omni` has installed the required packages, prompting for permission where necessary, but now is failing with "fatal: could not create work tree dir '/build/illumos-omnios': Permission denied". That makes sense, and I can create the directory and set the correct permissions, but the instructions on the website would lead me to suspect this 11:39:36 shouldn't happen. 11:39:59 I'm following: https://omnios.org/dev/build_instructions 11:40:04 It will use pfexec or sudo (depending on configuration) to escalate when necessary, which is just when building media or using `onu` to put the built bits in a new boot environment. 11:40:39 It looks like there's a missing `chown` step in those instructions, yes 11:41:33 You just need to change the ownership on /build (the directory will be automatically created by ZFS since it's a mountpoint) 11:44:22 For future reference, how does one prompt `omni` to use `pfexec` instead of `sudo`? I'm quite enjoying `pfexec` and I've never been a big fan of `sudo` for complexity. 11:44:52 I'll `chown` the build directory to make myself the owner 11:44:54 You can put `PFEXEC=pfexec` in your ~/.omni configuration file 11:45:28 pfexec is a really nice system - it can be very granular and the binary is not even setuid. 11:46:08 One thing it's missing is the option to prompt for authentication for various things, but that will hopefully arrive at some point (I have a working prototype). 11:46:10 I'm sorry for not doing my homework and not figuring it out myself, but how does it work then if it is not setuid? 11:48:04 pfexec sets a process flag on itself, and then when it calls exec(), the kernel spots this and talks to the userland pfexec daemon (pfexecd) to determine what set of extra authorisations and/or privileges to apply, and whether to change the uid/gid for the new child process. 11:48:21 ah, cool 11:48:23 thank you 11:49:33 There is a bit more in IPD25 (fenix) 11:49:33 IPD 25: Authenticated pfexec (draft) 11:49:33 ↳ https://github.com/illumos/ipd/tree/master/ipd/0025/README.md 11:59:00 That IPD is a great read. 12:56:39 Aha a new build with all the new bhyve tsc stuff, let me install that 16:05:12 Odd question, but can someone please point me to what "braich" means in the context of omni build? 16:06:25 It's welsh for "arm" 16:06:58 It's the code name for the aarch64/Arm port of illumos, and the test omnios distribution built on it 16:07:00 :-) Erm... excuse me? 16:07:24 :-) Ahhh! Thanks fellas, I would not have got that on my own 16:08:51 and if at any point you fancy booting that, the last asciicase on https://omnios.org/setup/zadm shows the quickest way to boot it under qemu on an omnios system. 16:08:55 *asciicast 16:11:55 andyf mind blown! 17:41:04 What's the reason that building works in a zone but the media cannot be generated in a zone? 18:02:43 Generating media involves creating temporary ZFS pools and loopback mount devices and mounting filesystems and so on. I don't remember offhand which specific bit was hard to get going in a zone now, but some part of that doesn't work. 19:46:33 andyf That's logical. Is it possible to do the build in the local zone then build the media in the global zone?