09:51:57 Hello :) 10:00:31 hey 10:13:26 Trying OmniOS fir the first time. If everything goes well. I hope to use it for homelabbing and selfhosting stuff. Any advice for a newcomer ? :) 10:13:31 for* 10:18:10 not got much really, it'll run a mailserver and a webserver reasonably well if that's what you are asking 10:24:59 Ok I will continue to read the documentation and man pages then. Speaking of documentation, some links seems to be dead. Should I open an issue on the omniosorg.github.io project about them ? 10:33:03 you could indeed collect the broken links 10:33:16 OK I will do that then :D 10:36:12 Soo I run my first issue here. I setup the same resolv.conf as my desktop machine. On my desktop Machine I can ping fdn.fr but I cannot do the same on OmniOS. 10:36:43 For contexte, the OmniOS machine can ping the ip address of the nameserver of my ISP (fdn). 10:37:08 Try `cp /etc/nsswitch.dns /etc/nsswitch.conf` 10:37:28 The default `nsswitch.conf` file does not have DNS enabled - at least depending on how you installed it 10:46:19 Oh ? a quick diff /etc/nsswitch.conf /etc/nsswitch.dns confirmed what you said. Now it's work ! Thanks :D 10:46:42 No problem. It's a default that should probably be changed! 10:49:20 It should'nt be hard to change ? Am I right ? 10:49:55 It's an easy change, but there are a lot of omnios users that deploy en-masse with kayak, and the change may break there workflow. 10:50:19 We should perhaps change it for interactive installations if we don't already 10:55:02 The first installation was done without network configured. I wasn't able to enter an IPv6 link-local address on the gateway from the installer. Maybe I enter it in a wrong way ( fe80::1%rge0 ) or maybe this way is not supported yet. I dont't really know. 10:55:57 I will try with DHCP for the next time (I'm on v6only network). 10:56:14 on a v6only* 11:10:32 Something I curious about is why the IPv6 link-local on OmniOS is a /10 on GNU/Linux it is a /64. Any idea ? :) 11:18:50 I'm not sure the installer has support for IPv6 yet. 11:20:10 I don't know why Linux would use /64 for a link local, although the difference (the 54 bits) are always zero so it shouldn't matter 11:20:17 If not fully, at least partially, the installer recognise the static IPv6 IP I give to him. The problem I got was just on the gateway setting :) 11:20:31 Oh, interesting, so it should not be too hard to fix 11:23:10 One ather thing surprise me after the installation was the fact that I can ping a link-local without giving the interface to the ping command O.o 11:23:39 other* 11:26:07 example : generally to ping a link-local I do ping fe80::1%rge0 (That work, no problem). And I found by mistake that ping fe80::1 work as well and that was a surprise ^^ 11:27:59 Because this doesn't work on any other operating system I have tried before (FreeBSD, OpenBSD and some GNU/Linux distribution) 11:29:20 I don't know the answer to that one - if there's only one link local and no ambiguity about which interface to use, it seems ok if the scope ID is optional 11:30:31 I will try it again when I will setup some VLAN then :) 12:09:38 xD How to find a definition of a word who is not listed in the menu of the website but exist anyway :P 12:10:47 I was redirected to the how to use zadm. Didn't found any definition of sparses brand and found this page : https://omnios.org/ 12:11:07 https://omnios.org/setup/zones 12:11:38 This page doesn't seem to be on the menu of the website for unknown reason :) 12:37:52 Maybe we could add a quick explanation of each brand on the zadm man page. What do you think about that ? 12:38:38 I mean a quick explanation of what is a lx brand, sparse brand etc before explaning how to use zadm. 12:38:46 There is https://man.omnios.org/brands that gives an overview, and then each brand has its own page 12:39:41 It could make sense to reference that page from the zadm one, definitely 12:39:50 Hmmm, I didn't know that. then add a "SEE ALSO" at the end of the zadm man page could help them :) 12:40:08 then* 12:41:45 Great i'm gonig to be the newbie tester with a lot of feedbacks :D 13:31:07 IIRC will just grab the first interface it can match for fe80::1 netstat -nr -f inet 13:31:54 And it should have fe80::/10 entries that have the If colomn filled 13:32:15 If you have multiple it grabs the first (I think), unless you specify the interface too 15:30:39 Thanks for your feedback :) 16:43:24 Hmmm someone know why some webpage of OmniOS.org are only available via an external search engine ? :) 19:57:36 Someone already use a FreeBSD Guest using OmniOS as an hypervisor with zadm ? 20:07:31 4/7 VMs I run are freebsd 20:07:51 all 13.2-RELEASE at the moment 20:14:38 (also asked in #illumos channel) quick check, based on recent negative results, I just want to make sure a card we're getting in a new file server is actually supported. Does anyone know if a "Mellanox 25-Gigabit Ethernet Adapter ConnectX-6 Dx - PCIe 4.0 x8 - 2x SFP28" will work ok? 20:24:00 nomad: I believe the changes to make it work properly enough might not have made it into gate. @danmcd would know @kebe 20:24:40 I have some changes for that card nomad. CX-6 has extra registers current cxgbe isnt aware of yet. 20:25:23 When do you think it'll be available? We haven't purchased the server yet but we will probably order it this week. 20:25:50 I feel like I'm pushing OmniOS/Illumos a bit hard, given the still unresolved problems with the HBA and now this. 20:25:59 something about current hardware being a moving target. 20:27:40 Hang on. I saw your email too. Watch there. 20:32:15 nomad: You have new mail 20:34:13 email received. I'll reply there unless you think the conversation here would be useful. 20:35:33 I will say here that the 9500 HBAs have the SAS3800 chipset in them. We don't have /etc/driver_aliases entries for them, but last time I looked at FreeBSD's version of our own mpt_sas, it *seems* that the MPI interface for talking with them didn't change beyond recent-ish pushes from rmustacc for 34xx and 36xx(?) chipsets. 20:35:53 In a perfect world one just adds those driver_aliases entries and Bits Just Move. 20:36:02 Unsure if we're in a perfect world this time, however. 20:36:37 And the Mellanox CX-6 has been spoken of here as well. I did some custom hacks for Smithx10 to get it to report the speed properly, which unblocked use in aggrs. 20:37:05 we use aggrs for our 10G connectivity but won't be doing so for the 25G. 20:37:31 we're using two cards that have a special cable that connects to one switch port but they'll be on different broadcast domains. 20:46:43 or, I should say, we will be ... if we buy this card.