14:22:43 <vibrant> hey everyone! I'm getting my feet wet with omnios after letting my vm sit for a while post-install
14:23:50 <vibrant> I'm trying to understand how to install third-party software. did some stuff with pkg so far, but this system doesn't have a ports like freebsd does. I see this https://omnios.org/info/ipsrepos -- but not really sure what to do with it
16:38:19 <m1ari>  vibrant: from memory core will be setup by default and has all the required stuff, omnios.extra you might have to manually add to pkg. For each of them you can get a list of the packages they include by opening the url for each of them and then chosing the relevant option near the end of text.
16:40:09 <m1ari> same should be true for the sfe.opencsw packages, although I'm not sure I've ever tried them.
16:41:06 <m1ari> Anything else you'll likely have to build from source - although maybe consider if it's something you can help contribute to one of the repositries.
19:38:49 <vibrant> I have never done package management for an OS project but who knows, could be fun
19:40:53 <andyf> The omnios extra repository has a fair amount of additional software in it. We like to keep it to just things which are used as there's quite a lot of overhead in maintaining it. The repository might already be in your list (try `pkg publisher`) and if not it's easily added.
19:43:32 <vibrant> for example, is there neofetch?
19:44:11 <vibrant> I'll do pkg search to see what I have
19:46:13 <jayjwa> You can download the source of it and use that. I have it here. 
19:58:18 <vibrant> okay, I shall do that!
20:22:49 <vibrant> thank you all
21:02:49 <jayjwa> Where is the kernel source on an illumos system? There's not much down in /usr/src.
21:17:51 <rmustacc> It's not usually shipped by default.
21:18:05 <rmustacc> So you generally manually clone a repository and build things.
22:35:27 <sjorge> So I wasted around 6 hours on this ... https://gist.github.com/sjorge/159444f7aa8af2cec1b974a825cde4d7
22:35:48 <sjorge> Am I missing something obvious? Or is that a bug or intended behavior?
22:36:46 <sjorge> I would have expected if i provide a cloud-init file with a network block and not set any of the properties it would take it from the file. But stub config seems to be generated anyway meaning the one in the file gets ignored. THe stub one just had dhcp4 and dhcp6 set to true.
23:10:39 <sjorge> What is worse is, even all the 'ways' to disable cloud-init's network config do not seem to work :| (cmdline, could.cfg.d/, disabling cloud-init-network.service, masking cloud-init-network.service) ...
23:11:06 <sjorge> basically if you specify a cloud-init filename, you will be forced onto dhcp