00:01:01 Stuck in postmaster update hell... 00:17:48 How do I change my ruby gem env settings? 00:17:58 I'm getting this: Could not find 'prawn-icon' (~> 3.0.0) - did find: [prawn-icon-3.1.0] 05:08:23 * Erhard ywans 05:08:32 * Erhard yawns too 05:14:55 EuroBSDCon 2022 starts in 46 minutes 05:30:35 only courses on the spot today and tommorow tough, but Social online tommorow evening and talk stream on Saturday and Sunday 09:44:06 luna: is URL for the stream known? 09:49:06 meka: not yet i think will be announced during tommorow 12:58:31 hi all 13:00:03 hey 13:15:59 is there some web interface / overview of the `pkg` binary repositories, like the linuxen have? 13:17:25 freshports? 13:17:35 freshports indeed 13:18:03 freshports has the versions of the non-binary packages tho 13:18:19 as in, the ports in the ports repo, not the actual version of the binaries 13:18:31 like it says restic 0.14 on freshports, pkg still has 0.13 tho 13:20:09 see https://www.freshports.org/sysutils/restic/ 13:20:10 Title: FreshPorts -- sysutils/restic: Fast, secure, efficient backup program 13:20:17 whereas `pkg` still installs 0.13.1_1 13:20:24 or am I doing something wrong? 13:22:33 i'm on 13.1-RELEASE-p2, amd64 13:31:22 maybe looking through this? https://pkg-status.freebsd.org/ , finding the jail and ports tree you are installing packages from, and looking at what was last built. although you need IPv6 to view the individual poudriere pages as they don't use IPv4 13:31:54 also making sure you are using latest and not quarterly 13:34:49 if I do pkg search restic then it shows me 0.14.0_1 though so I expect you're using quarterly and not latest 13:35:17 do pkg -vv and look at the url 13:37:07 ooh, is it possible my pkg installs the quarterly, not the latest? 13:37:20 ah, just read your commen :P 13:37:25 where would I change that 13:37:55 ah yes ` url : "pkg+http://pkg.FreeBSD.org/FreeBSD:13:amd64/quarterly",` 13:38:45 is it advisable to change to latest even? 13:41:00 it seems I have to create a `/usr/local/etc/pkg/repos/FreeBSD.conf`, is that still current information? its from some old forum post 13:42:18 yeah that. copy the one from /etc/pkg/FreeBSD.conf into that directory and change quarterly to latest 13:42:35 though that will then upgrade everything to the latest version, so be sure that's what you want 13:43:28 quarterly takes a snapshot of latest every 3 months, so you would probably have to wait until 1st October maybe for restic 14 to appear 13:50:03 I think, as this machine is mainly supposed to be stable and low maintenance, I'll stick with quarterly and just compile the port for now 13:50:23 I want the 0.14 mainly to play around with its new compression feature 13:50:29 the other option is to run "restic self-update" and pkg check -r restic 13:50:48 what doesn the pkg check do? 13:51:14 I assume it detects the mismatching binary? 13:51:34 restic is just a single binary with no dependencies which means you can download the binary from the github releases page, which is what self-update does, and then the pkg check -r makes pkg rehash it so that it doesn't complain in the daily security logs that the hash is different to what's expected 13:52:07 oh, the system checks all binaries daily? 13:52:08 that's neat 13:52:52 yep. think it's in /usr/local/etc/periodic/security/460.pkg-checksum 13:53:27 it complains in the daily email/log output that the hash is a mismatch, but if you run that check it changes the expected hash 13:53:39 ah yes, the mail stuff is also kinda arcane to me 13:53:48 the next time the port/pkg is upgraded it will just overwrite the restic binary with the new one 13:53:52 it tells me I have mail, but the `mail` program is kinda annoying to use :P 13:54:04 just saying, that is one option. otherwise you could compile from port 13:54:31 I think the truly prudent thing is to not mess with the backup system on that machine at all for now :P 14:04:50 Any idea why this won't work? portmaster -a -x freebsd-doc-en .... Postmaster insists on trying to rebuild freebsd-doc-en which fails every time 14:07:02 SpaceBass: For -x options, use double-quotes around them and specify the version. Ex: portmaster -a -x "freebsd-doc-en-1.0.40_1" 14:07:54 I'll try - the doc says it uses globstrip and will match anything that starts with the pattern. ek, am I using the updated port or current version in the quotes? 14:08:36 SpaceBass: It will glob if you use "-\*" to match. 14:08:48 You're specifying the currently installed version to exclude. 14:08:54 I tried * but it keeps saying no match 14:09:07 SpaceBass: -x "freebsd-doc-en-\*" 14:09:35 Might not need the escape the char inside the double-quotes but I think you do. 14:10:01 Thanks, I'll give it a try 14:10:11 Err... "freebsd-doc-en\*" 14:10:52 Testing 14:24:26 Drat, still tries to compile it, still fails 14:24:55 SpaceBass: What does "pkg info | grep -i freebsd-doc" say? 14:25:12 Not even a good error: https://paste.debian.net/1253971/ 14:25:14 Title: debian Pastezone 14:25:45 ek that returns the old version en-freebsd-doc-20220527,1 14:26:27 SpaceBass: portmaster -a -x "en-freebsd-doc-20220527,1" 14:27:33 I'll try - thanks. Worth noting that there are a ton of FreeBSD forum posts that just use the name of the port... eg: -x bash ... its confusing 14:30:55 SpaceBass: I've never tried just using the name of an already installed package. I do believe I have used the port location in relation to /usr/ports, though. Like portmaster -a -x misc/freebsd-doc-en 14:33:24 Also, the glob might work for just the name but you'd need the package name and not the port name. 14:33:45 portmaster -a -x en-freebsd-doc 14:33:55 As opposed to freebsd-doc-en 14:34:11 That's kind of a screwed up naming convention. 14:48:51 It looks like its working now ... fingers crossed 14:49:39 Honestly, its a good lesson in sticking with pkg vs ports whenever I can ... in this particular case, I have to use a port of Samba to get a specific compile-time option so I'm stuck 14:51:42 SpaceBass: It happens. You can always use pkg to install everything and then just (re)build Samba with your needed options afterwards. 14:52:02 That 14:52:08 That's the play 15:50:21 bah, why don't OpenBSD and NetBSD have sysrc? 15:59:38 Hello, I have a quick question about interfaces and promiscuous mode. 16:00:23 I have a VM where igb0, the physical nic, shares a bridgeo with vtnet0, all in promiscuous mode with no inet alias assigned to anything 16:00:48 Essentially it's just taking in traffic and passing straight through the VM, to my tap0 interface on host 16:01:48 My question: Is there any way to access the VM from the outside via those interfaces? 16:02:21 I'm assuming no, but I figure it's worth asking 16:07:17 Monegro: I'm somewhat confused about the actual connections 16:09:39 I create the virtual machine with PCI passthrough, so that it contains igb0 which is the physical NIC. 16:10:17 I use a tap to connect it to host, so the VM also has vtnet0 inside the VM, and host has tap0 16:11:12 Inside the VM, I put igb0 and vtnet0 on the same bridge, in promiscuous mode 16:11:33 Nonething gets an assigned IP address 16:11:54 Well, nothing inside the VM. On host, tap0 gets an IP address to connect to my external router. 16:12:33 So I'm wondering if this is at all insecure for the VM itself. I don't think it's possible to make a connection into the VM from the outside, because none of the interfaces have IP addresses to receive packets. 16:33:26 Monegro, what are you trying to do? 16:35:04 It's something that I'm already doing. 16:36:03 It's really a theoretical question -- Is it possible to access a machine through an interface in promiscuous mode, but with no assigned IP address 16:36:08 ? 16:42:16 Monegro: you might be able to read some traffic, but i can't imagine how you'd access it 16:45:02 Define "access"? It would have an Ethernet MAC address (or several), so it may work as a bridge to jails, VMs, or other baremetal hosts. 16:52:27 Thanks, that's what I thought. Just wanted to check. 16:53:05 By "access", I mean get a terminal on the VM or send commands that get run inside the VM. 18:17:24 is the debootstrap package broken? It keeps on failing to get release files no matter what address or options I give it 18:17:57 I just want to try out linux jails :-( 18:20:18 Ah, I found debootstrap.log 18:20:20 ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/bin/wget not found 18:25:40 What does "freebsd-version -kru" output? (fold to a single line or use a pastebin) 18:27:25 Also: output of "file /usr/local/bin/wget" 18:45:41 I have to wonder how wget was installed, via package or ports... (and if the package cache is up to date etc.) 18:45:47 I was still on 13.0 but with an upgrade to 13.1 all is fine :-) 19:28:26 hmm, what's the systemd equivalents to go into exec.start/stop in jail.conf? 19:33:13 Not sure what you have in mind (I know next to nothing about systemd), but you can run init(8) in a jail. 19:34:08 My goal really is just to run a linux jail 19:35:00 And for packaging reasons I'm looking at ubuntu bionic 19:36:47 Wait. Do you mean Ubuntu userland with the Linuxulator, or do you actually want a Linux kernel running? 19:37:43 Ubuntu userland with Linuxulator, I don't want a Linux kernel :-) 19:38:34 OK. I was asking because jails can't do the latter. 19:42:55 If you want a full userland for a distro using systemd, my guess is "put in whatever makes your distro go multiuser and start systemd, in whatever order it does that". 19:48:21 AÄ 19:52:44 I should figure that out tomorrow, but at least I got networking working now! 19:57:47 well that was shortlived 19:57:50 chmod() of /var/spool/rsyslog via /proc/self/fd/4 failed: No such file or directory 19:58:18 Oh wait, I don't need rsyslog 20:45:31 hi, in a 13.1 jail I installed vim, but when I try to execute it I get: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 21:55:55 listening to BSD Now, before heading to bed here in Sweden, hope people are having it nice at EuroBSDCon in Vienna 23:36:09 morning