01:09:43 anyone have a jexec bash completion? 02:45:28 anyone know how to program bash completions? really really want completion for jexec and jls to complete jail names based on any configured in /etc/jail.conf.d/*.conf 02:45:34 whether they're running or not 02:51:14 i'd learn how myself, i'm not lazy, i just don't have it in me to learn yet another lang (bash) for 2 completions 02:51:42 and bonus, if you help me you can sell your jexec and jls completions in the pkg store (for free) 02:51:55 so everyone will get to use them when using jails tech 03:51:32 alepzi, It's a bash specific syntax and for bash "." and "source" are the same thing. So it does not matter. Both are equivalent. The ". file" syntax is standard /bin/sh and so bash gets that from there. The "source file" syntax originates with csh and bash pulls it in from csh. 04:10:48 how do I identify where upstream is for contrib/nvi? 05:39:22 so someone on mastodon has come across a drive (memdisk specifically) exhibiting both slices and partitions 05:42:19 link? 05:46:00 * kevans notes that it's suddenly raining sheeps and cows outside 07:03:29 how does one find the current pkg build state of a specific package? 07:04:39 clairvoyance 07:20:24 how can i get same package list installed on new station as on old one? 07:26:04 etwas: on the original machine, you can run "pkg query -e "%a = 0" %o > pkglist.txt" and then copy that file to the new machine, and run "xargs pkg install -y < pkglist.txt" (please review the file before running the second command to make sure it is sane) 12:20:02 realdeimos: do you have a machine with IPv6 routed to it? If so, you can use https://pkg-status.freebsd.org/builds?type=package&all=1 to find the specific builder jail for the version-arch tuple that you're running, and click the little bomb icon next to the build you wanna look at, that'll take you directly to the builder. 12:20:44 The builders are IPv6-only, because typically all they do is send built packages to the package CDN once it's done building. 12:25:35 sfox: that's not really helpful at all. 12:38:02 LxGHTNxNG: that sounds like a disk with an old-style BSD label? 12:55:24 i'm currently having a hard time setting up a second, separated LAN. i set up isc-dhcpd and coredns and those components work fine. my client devices get an ip in the right range and the dns info. the server itself can reach the internet fine (it sits behind one of those enduser "router" boxes), but clients in the separated lan can't reach the internet. 12:55:52 my understanding was that gateway_enable and a default route were all that's needed for that to work, but i can't find any specific docs on what gateway_enable does in detail. 12:56:47 doing dns queries from clients in the separated lan works fine, i essentially just need the one line to tell the server to actually route client traffic to the upstream network. 12:56:58 phryk: gateway_enable enables IP forwarding, which means if the kernel receives a packet on one subnet with a destination address in another subnet, it will forward the packet. to start with, check the clients have a correct default route, and see what traceroute says 12:58:47 yeah, the default gateway is delivered via dhcp. it's the ip my server has on the interface on the separated lan. traceroute gets to exactly that host and then sits there spitting out asterisks 13:00:05 this is IPv4 traffic, right? there's a separate gateway setting for IPv6 traffic 13:00:29 yes. ipv4 only. upstream has only v4 so i saw no sense setting up v6. 13:01:03 does the router have a firewall running (ipfw/pf/ipf)? 13:01:08 my understanding of "enabling ip forwarding" was that if the server knows a route to a network (i.e. it can reach it itself) it will be able to forward client packets. 13:01:20 lw: usually yes, but i deactivated pf for testing. 13:01:21 yes, that's how it works 13:01:48 lw: okay that's weird because the server can clearly reach the upstream lan and the internet, but the clients can't. 13:02:12 is there maybe some weirdness because i set both gateway_enable and defaultrouter in my rc.conf? 13:02:27 phryk: run tcpdump on the router's outgoing interface (the one facing the internet) and see whether the packets are being sent but no the replies, or if nothing is going out at all 13:02:36 no, it's fine to have both of those set 13:03:03 k sec, lemme look up how to do src filtering with tcpdump again^^ 13:05:26 phryk: 'src host 1.1.1.1 or dst host 1.1.1.1' should work but i'd recommend trying to test this without filtering if possible, just in case something odd is happening 13:05:34 (not always possible if there's a lot of traffic though...) 13:06:08 ah yes, not wise to do this via ssh… thank you, feedback loop. 13:07:06 if it's just ssh you can try port not 22 13:07:14 (assuming your test traffic is not ssh :-) 13:08:13 na, just ping for now 13:09:26 okay, i can see "IP $clientip > $pingdestination: ICMP echo request…" 13:09:42 and no reply? 13:09:43 responses would be "$pingdestination < $clientip", correct? 13:09:52 no, just > 13:10:01 no, the response would be 'IP destination > client: ICMP echo reply' 13:10:18 ah, okay. but no, only echo request 13:10:48 same behavior for the upstream gateway (192.168.1.1) and hosts behind the nat of that gateway (wikipedia.org) 13:11:01 so it seems like the router is forwarding the traffic fine and it's being dropped later, perhaps at your "end user router"... if that's doing NAT, does it know to NAT the specific address space in the new subnet? 13:12:07 unless it just answers everything, no. but access to that box is lost, that's the reason i'm building a second lan. 13:12:31 so i guess my only option is introducing a second nat on my server? 13:13:25 if you need NAT and you can't configure the edge router to do the required NAT - probably, yes. are you intending to replace that router with this new freebsd router though? in that case you'd presumably need to do this anyway... 13:14:11 when i switch to a good isp, yes. i'm working based on my old setup where this was the edge router/fw anyhow. :P 13:15:00 but current uplink is from my roomie and they lost the pw, so in the interim there wasn't much else i could do except try and run a dictionary/bruteforce attack against the routers web ui thing and that seemed inefficient^^ 13:15:37 Hi, I did a pkg upgrade on my FreeBSD 14 and all the graphic applications stopped working 13:15:48 Firefox, etc. Now XFCE is broken 13:16:09 is there a way to restart it without rebooting?. 13:17:42 martinrame: log out, restart display manager, log in again. could work, should work, might not work. :P 13:18:27 phryk: let's try that 13:22:43 lw: reactivated my old nat rule and it immediately worked (written from formerly problematic client) :P 13:24:02 phryk: another option would be to just bridge the two networks, which may or may not be easier depending on what your goal is 13:24:05 phryk: mmm, the login manager shows "faled to run command" (or something similar). I had to ctrl+alt+f2, then login without seeing anything, and run startx, now I'm on XFCE again, but I'm afraid I'll have the same issue when I reboot. 13:24:41 btw, thanks to tmux I was able to re-attach this session ;) 13:25:21 martinrame: if you're on a tty anyhow you can try unloading and reloading the graphics driver module. 13:25:31 tho a reboot would also make it load the new driver^^ 13:25:52 phryk: but I am on a graphic session right now. The issue is with the login manager 13:26:50 Mmm: pkg: libxine has a missing dependency: libva-glx 13:28:20 yeah, no idea. i'm still sad slim broke for me and i had to set up lightdm which still confuses the hell out of me^^ 13:37:20 phryk, how did slim break for you? For a week or so a month or two ago, it displayed a blank screen for me, but that has been fixed about a month ago. 14:40:54 Soni: your netinet6 issue was fixed in main, you can cherry-pick this commit: https://github.com/freebsd/freebsd-src/commit/042fb58d009e7efc5b334b68fffbef9b1f620ec8 - you may also need 0478a0356272ab3907af9d97711f0bb8b14bf38b 122dd78c143e3d138b5d503a30da4c326f41002a 14:40:55 Title: sys/netinet6/in6_pcb.c: fix compile without INET · freebsd/freebsd-src@042fb58 · GitHub 14:42:31 Soni: there are also two unmerged PRs still going through review, https://github.com/freebsd/freebsd-src/pull/1159 and https://github.com/freebsd/freebsd-src/pull/1157 but you fix those by disabling the affected modules (if_bridge and pf) if you don't need them 14:42:32 Title: sys/net/if_bridge: support non-INET kernels by llfw · Pull Request #1159 · freebsd/freebsd-src · GitHub 14:44:02 (the pf fix should be safe, if_bridge i am not sure about and would like more review on) 14:47:31 lw: ty 14:53:07 debdrup: thank you. I was poking around earlier, but still can't find the specific package. It appears I have to click into each build and then search for the package 14:53:58 the port is current as of 06 april, just waiting on package to be built 14:54:39 and i'm not using quarterly packages, using current/daily whatever it's called for pkg repo 15:04:14 latest pkg repo is what I'm saying 15:07:36 * lw wonders what libicp_rescue is, seems to be related to zfs 15:25:24 so i got a separated lan NATing to the upstream lan and having working dhcp. i also got dns with coredns set up, and it works fine on the client machine in the separated lan. but vms (using bhyve-vm) seemingly can't talk to the dns server – even tho they *can* ping it and get dhcp leases from it just fine. 15:26:16 phryk: are you using a bridge(4) for the VMs? 15:26:44 lw: no idea, whatever "vm switch" creates. 15:27:04 ah, i personally dislike vm switch precisely because you have no idea what it's really doing :-) 15:27:11 phryk: can you paste the output of ifconfig -a? 15:27:16 it's not *called* bridge*, but i'm not sure how much of an indication that actually is. since i just added the lan interface to that with (vm switch add) it might be a bridge… 15:27:18 sure, sec 15:27:44 i'm fairly sure 'vm switch' creates a bridge, but i'm not sure how it configures it 15:27:48 https://paste.xinu.at/jikAC 15:27:54 seems like tap 15:27:56 :P 15:28:07 tap will be the VM interfaces, 'vm-public' is your bridge 15:28:38 phyber: you need to move the IP address of the host from re0 to vm-public, and adjust firewall rules as appropriate - unfortunately i'm not really sure how you do this with vm-bhyve's bridges 15:28:45 mhh, i thought it was either one bridge or separate tap interfaces per host. 15:28:57 that may not be the cause of this particular problem (although it's possible) but it is wrong to configure IPs on bridge member interfaces 15:29:44 sec, gonna adjust rc.conf 15:29:55 phryk: no, it's both - the tap interfaces provide the packets from the VMs, but without a bridge, they won't go anywhere. the alternative is to not use a bridge and instead route the traffic (i.e., assign a separate /30 or something to each tap interface) 15:41:06 tykling what is required for my freebsd 14 jail to have access to pool/backups inside my pzbackup jail? im using this in my jail.conf exec.created += "zfs jail pzbackup pool/backups"; allow.mount.zfs; enforce_statfs; but i keep getting cannot set permissions as root inside jail when i want to set zfs allow on the pool for my user .. any idea 15:52:30 lw: well, that did not work… 15:52:37 for one, '-' in interface names is something rc.conf really doesn't like, even with escaping. but even when i manually set it up so that re0 was just up without lease and did dhclient vm-public it did not change the reachability of dns in the vms 15:52:37 oh no 15:53:00 phryk: like i say i'm not really sure what the right way to configure this is with vm-bhyve's default bridge setup :-/ 15:53:09 i just create the bridge by hand and tell vm-bhyve to use it 15:55:07 Anyone else experiences /bin/sh occasionally "forgetting" that it's in vi mode, and entering a really strange mode where you e.g. cannot edit/delete the very last character, as the cursor won't move past it? 15:55:28 Dooshki: no, but does ^L help? 15:55:34 Interestingly enough, issuing "set -o vi" fixes it and makes it behave good again 15:55:47 /bin/sh has fairly primitive terminal handling and its line editing gets confused if there's any output before the prompt 15:55:52 huh… uh, wat. i added the log directive to the coredns conf, saw the queries arriving but vm didn't get a response. start coredns again and now it works, at least for the debian vm? o_O 15:55:52 lemme test the dinwoze one 15:56:16 lw: No, ^L does literally nothing 15:56:22 phryk: you should fix this anyway, having IP address on bridge member interface is wrong. it will cause uncommon but hard to diagnose problems 15:56:31 (it prints the character) 15:56:48 (and you're able to run it as a command) 15:56:54 Dooshki: ok i see, ^L doesn't work on vi mode. not sure then 15:57:04 maybe there's a vi-mode command to do the same thing 15:57:55 lw: Actually, it does work in vi-mode, it just doesn't work in the bugged in-between mode 15:58:08 when I type set -o, it lists "vi mode" as enabled 15:58:12 really? i just tested it here and after set -o vi (and nothing else) it didn't respond to ^L 15:58:24 lw: You have to exit into command mode first 15:58:30 ah 15:58:34 pressing 15:58:54 this is different to how zsh works, i never used vi mode in sh 15:59:16 I guess this is another idea for a weekend project, seeing if I can debug this 15:59:27 probably not this weekend though 16:01:28 oh this is annoying, because FreeBSD-utilities has its own pkg ucl, it doesn't automatically pick up library dependencies on things it needs 16:01:54 so i moved libpjdlog to another package and now: /sbin/decryptcore: libpjdlog.so.0 => not found (0) 16:02:17 i thought pkg was supposed to handle this automatically even if you don't explicitly list the dependencies though... 16:02:43 okay, i booted the windows vm and now it works on neither the windows vm, the debian vm *or* the host… i think coredns is just plain broken. :/ 16:03:18 ah i see the problem: it installed the lib32 package instead 16:05:47 tykling was missing the allow.mount, allow.mount.zfs wasnt enough 16:13:58 lw: lol, it works when i deliver the upstream dns via dhcp… but not if i deliver my own dns in there and set the upstream dns manually in the windows vm. go figure… 16:40:51 finding some method behind the madness: coredns either works for the host or the vms, and apparently whoever first queries the server gets dibs… 16:46:23 mhh, it looks like it works fine IFF i specify an interface to bind to… 16:57:35 phryk: did you fix the IP address being on the member interface? because this is exactly the kind of issue that can cause 17:04:22 i have 1 nvme ssd installed, so i know nda0 correlates to nvme0. how can i systematically know that, i.e., is there a command that shows that relationship? 17:08:17 markmcb: as far as i know, no. i'm not sure you can hardwire this with device.hints either. if you're trying to script something, i suggest using GPT labels instead of relying on device names 17:10:13 maybe camcontrol devlist 17:10:40 nda(4) suggests camcontrol devlist but i don't see this info there 17:11:36 at scbus8 target 0 lun 1 (pass1,nda0) 17:16:43 you might have to use inxi or parse dmidecode 17:35:52 anyone know how to program bash completions? really really want completion for jexec and jls to complete jail names based on any configured in /etc/jail.conf.d/*.conf, without them having to be started and running. can't bring myself to learn enough bash-completion to do it but i'll bet if you do it other ppl would use it (pkg install jail-bash-completion?) not just me 17:36:27 alepzi: have you tried #bash ? 17:37:08 tried yesterday didn't get anywhere 17:37:15 not too many freebsd users didn't seem like 17:40:50 Until 14 the default root shell was csh so knowing that it might explain why not so many bash completion enthusiasts present here. 17:41:11 rwp: as if anyone but 80 year old greybeards actually used csh :-d 17:41:43 I have used tcsh a lot:P 17:41:55 tsoome: what colour is your beard? 17:42:13 em, lets talk about something else..... :D 17:42:20 At a previous employer the entire design lab used tcsh almost exclusively. It was swimming upstream to use anything other than tcsh. 17:42:33 okok, not that grey:) 17:42:57 alepzi: maybe ask on questions@ in case someone has already done this 17:43:08 alepzi: if you do find the answer, you should submit a port for it 17:46:42 I am still tripping over the use of sh for the root shell because my fingers are used to bash key bindings and not all are supported. I need to spend some time with the new sh key binding docs and figure out how to do one mandatory thing that I use all of the time before I can use it. 17:47:51 rwp: do you ever actually log in as root? i normally use sudo -s which gives me my zsh 17:47:53 In sh command line how does one recall the last argument of the previous command? In ksh it is ESC-_ and in bash it is either that or ESC-. to past in the last argument of the last command. I use that all of the time. 17:49:25 Using "sudo -s" is incompatible with "sudo -i" and "sudo -s" leaves HOME set to my home, which inevitably drops root owned files in my $HOME which then I need root to clean up afterward. So... No. I never use sudo -s. I only ever use sudo -i or just sudo command. 17:50:15 sudo echo $SHELL tells me bash 17:50:39 Having root owned files in my home has snagged me regularly enough that I have a personal cron "test ! -d $HOME || find $HOME -user root -ls" to look for accidental files and report them to me. 17:50:42 alepzi: 'sudo echo $SHELL' will print exactly the same thing as 'echo $SHELL' because the $ is interpreted by your interactive shell 17:51:07 yikes 17:51:17 what's the right way to echo $SHELL as root then? 17:51:20 rwp: interesting, i haven't run into that issue. 'sudo -s' sets $HOME to /root for me 17:51:28 alepzi: sudo sh -c 'echo $SHELL' 17:51:28 You might try "sudo printenv SHELL" to avoid dollar expansion or quoting at all. 17:51:52 [25!] ilythia /src/freebsd/src/pkgbase-share-examples [lf/pkgbase-share-examples]% sudo sh -c 'echo $SHELL' 17:51:52 /bin/sh 17:51:52 [26!] ilythia /src/freebsd/src/pkgbase-share-examples [lf/pkgbase-share-examples]% sudo echo $SHELL 17:51:52 /usr/local/bin/zsh 17:51:57 csh! 17:52:30 sudo -s definitely sets HOME=/usr/home/rwp here. 17:52:47 For those lurking along try: sudo -s env 17:52:49 that's odd 17:53:06 % sudo -s env|grep HOME 17:53:08 HOME=/root 17:53:31 maybe we have different sudoers(5)? but mine is basically just the default with some extra rules 17:54:38 Hmm... I have "Defaults env_keep += HOME" in the sudoers file here. Where is the origin of that? Looking... 17:56:34 The origin of that for me seems to be lost in the sands of time. But probably it was a default setting at one time. I also have "Defaults env_keep += MAIL" too. 17:56:59 I am deleting the "Defaults env_keep += HOME" line and will see if the source of my complaint was self-inflicted all along. 17:57:49 i don't have either of those but i suspect that's the cause of your problem 17:59:24 I think you are correct. (But I am going to keep my crontab looking for errant root owned files anyway.) :-) 18:01:07 But anyway... I do often log in as root. And for example the last day I have been working trying to get IPMI SOL (serial-over-lan) working for (ahem, sorry) the Linux kernel. And decided that I just can't make it work with Linux. I think they have removed the ability. 18:03:10 The Supermicro BIOS works over IPMI SOL perfectly. GRUB works over the IPMI SOL perfectly. But Linux insists on using the graphical console rather than the hardware console and so far I have failed to make Linux work on the IPMI SOL. 18:03:16 The task is to get it going with Rocky 9 but I am going to take a diversion and fire up a FreeBSD system there to see how that works out over the IPMI SOL. 18:03:58 I feel certain that FreeBSD won't have this problem. But I will find out in an hour. Lunchtime here first though. 18:17:10 i would be quite surprised if freebsd handled ipmi serial better than linux, but you never know 18:17:38 although if it's a case of configuring it to use serial, yeah, freebsd is probably easier. always a hassle doing that on linux 18:18:14 anyone try nushell on freebsd? 19:33:12 Hi, I am considering buying a laser printer, I have a Samsung almost in new condition, but the driver is a pain. If you buy a Brother printer with PCL6 emulation, does anyone know if it would be able to work with LPR -no CUPS- 19:33:43 uskerine: yes it can, but it depends on the application you're using being able to generate PCL output 19:34:35 by LPR I mean LPD 19:35:43 I will only ever buy a network connected printer ever again. I am done with USB connected printers that require closed source drivers. 19:37:08 you can buy a tplink printer server 19:37:17 and attach it to any printer, then it is ethernet 19:37:35 where I have had issues is with the drivers when you do not want to use cups 19:38:49 HL-L2370DN I am checking this one, but I fear that the PCL6 support is a fake and then it is in reality done by the software driver 19:39:09 I am not recommending any specific printer because I have been very frustrated with most of them. 19:39:15 Rage against the Machine was never really specific about which type of machine they were furious with but I think it was probably a printer. 19:41:11 Agreed, same here 19:41:35 except for my Star EPSON compatible, that things prints everywhere, plus it is cool seeing the continuous paper 19:42:35 The Epson has tractor feed paper? That's so retro! 19:43:14 I looked at the HL-L2370DN that you mentioned, I see it says it has Linux drivers. I tried to download the driver to peek at it and the web page them breaks for me and I can't download it. 19:43:34 I suggest downloading it and unpacking the rpm/deb and inspecting it to determine exactly how they are shipping their driver for the printer. 19:43:46 If it is a binary only driver then I would run away from the printer. 19:45:10 the best thing would be a PS printer, that requires no driver 19:45:15 but they are no longer common 19:45:44 I think the most expensive ones still have it, but even in that you can not be sure a punk put that in the driver and not in the printer 19:46:56 So one of my clients has a Brother USB printer that he had previously been using on his Ubuntu system. Well it turns out that the Brother drivers were 32-bit binary drivers for Ubuntu 16.04 *ONLY* and nothing else would work. PITA! Note Ubuntu dropped 32-bit support entirely. 19:47:03 I ended up creating a VM running 32-bit Ubuntu 16.04 VM as a printer spooler. It's an appliance for my client now. 19:47:19 For my samsung I was almost sure that the driver was almost there, but somebody does something 10 years ago and the thing gets packaged and repackaged and it is no longer simple as ti shall be -so you can use the filter in LPR and that is- 19:47:51 that is a solution, but I am sure you do not like it that much 19:50:23 This is NOT a recommendation but I own an HP Color LaserJet MFP M283fdw network printer which is supported by HPLIP and works for me using the network interface. It's a native PostScript printer. 19:52:02 It also scans and I have it configured to scan and email the PDF scan to my other system on my LAN which then has a procmail rule to unpack the attachment and drop it into my NFS scan directory. 19:54:20 I do not want a color one, they are expensive. I just want to print my .PS diagrams and some PDFs 19:55:54 https://www.digitec.ch/en/s1/product/hp-4002dn-laserjet-pro-laser-black-and-white-printer-22819778 19:56:08 .ch 19:56:11 also new ones say they support PDF, does that mean that you can drop a PDF without any driver/filter from LPD? 19:56:12 I have also owned a series of HP InkJet printers over the years. I will never buy another one. The last two HP InkJet printers I have owned were endless trouble from start to finish. Never again. 19:56:31 uskerine, just wait for the next one to show up on daydeal 19:56:46 they come and go every couple of weeks/months 20:23:49 inkjet printers never last, the best printer is the one you do not have, but I miss printing some diagrams from time to time 21:50:36 lw ping 21:50:49 jbo: urrrrrrgh nooooow whaaaat 21:51:28 jbo: hang on i have to fetch more alcohol, ack in 10 mins 21:51:51 lw, regarding 276996, does that even still make sense given that you dropped maintainership of your other ports? we don't really want to add ports that we "know" will be orphaned in the forseeable future. 21:52:55 hey, I'm using auto-admin which is looking for meta.txt in http://pkg.freebsd.org/FreeBSD:14:amd64/quarterly/ but it's not there. Now... I checked a couple of other directories in there and they have a meta.txt including http://pkg.freebsd.org/FreeBSD:13:amd64/quarterly/. So... is there an update that make it so meta.txz is no longer used? 21:52:56 Title: Index of /FreeBSD:14:amd64/quarterly/ 21:53:27 looking for meta.txz, sorry, I'm working with text files for work, typo there. 21:59:02 jbo: ok to you, if you don't want to commit it i will just maintain it locally 21:59:06 s/ok to/up to 21:59:23 lw, the question is whether you have any intention of abandoning it as of now. 22:00:03 jbo: my frustration was mostly aimed at python packages, i think i'm okay to maintain to a single package with no dependencies, but honestly, no guarantees 22:00:34 my opinion that ports is completely fucked has not changed 22:02:07 is it just me or does apropos not parse the document description of any man(7) pages? 22:02:44 is anyone willing to check "apropos -s 1 dc" and/or "apropos gnupg" for me? 22:03:45 concussious: looks fine here: https://www.le-fay.org/tmp/30d/4WWdYg.txt - although i agree in general trying to find manpages is not easy 22:06:33 lw: thank you so much. that's what it's doing on my fx14p6 which is completely wrong 22:07:10 the description for dc is dc - arbitrary-precision decimal reverse-Polish notation calculator 22:07:34 ah you mean the output from apropos 22:07:38 bsd style man pages search really well 22:07:47 yeah, that seems wrong: dc(1) - dc 22:07:51 but linux style man pages are broken in our implementation 22:07:58 gpg is worse, it doesn't come up with anything at all 22:08:34 I don't have gpg installed, so I can't tell 22:12:07 do i mail the mandoc list? if this can get fixed, manual discoverability will be a solved problem 22:12:35 concussious, Did you find your question about the upstream of contrib/nvi? 22:12:50 idk where the right place to report that is off hand 22:12:59 i guess man/apropos are from some upstream 22:13:02 rwp: yes and the maintainer accepted my patch immediately 22:13:17 man and apropos are from mandoc.bsd.lv 22:13:19 Sven? Awesome! 22:13:29 well, man is actually our own shell script 22:14:12 but the rest of it is comming from mandoc.bsd.lv, those guys are using cvs and mailing lists, i don't yet understand how to interact with them politely the way they want 22:16:08 i got some params that are in all of my /etc/jail.conf.d/*.conf files. can i move those to /etc/jail.conf and keep unique params in the individual jail configs? 22:17:12 rwp: no vi upstream is lichray/nvi2 22:17:34 Ah... Yet another fork in the road. 22:18:13 * meena has contributed to lichray/nvi2 22:18:30 don't remember what it was, probably something super trivial 22:19:14 https://github.com/lichray/nvi2/pull/121 ah yeah 22:19:15 Title: fix last left-over K&R function declaration by igalic · Pull Request #121 · lichray/nvi2 · GitHub 22:19:39 alepzi: probably, try it and see 22:22:48 lw, I'll consult and report back - I prefer to ask $mentors about this one 22:22:55 (nothing personal, hopefully obviously) 22:24:44 jbo: this would be easy to fix if you just gave me a ports commit bit 22:24:52 although tbh... not sure if i would take it 22:26:07 people repeatingly asking for commit bits are AFAIK not the ones necessarily getting them :D 22:26:19 sounds good! 22:26:22 can i have a commit bit pls 22:26:27 are they trying to backdoor freebsd? 22:26:27 * jbo yells at autotools 22:26:34 oh you won't let me participate in this nonsense? too bad 22:26:43 alepzi: absolutely 22:26:50 that's what i think 22:26:50 lw, too much or too little alcohol rn? 22:27:01 jbo: too much ports. it annoys me. 22:27:02 commit bit is a responsibility noone should want, but they do for good of the project 22:27:31 my life has become notably more miserable since I got one. and I haven't done ports work the past few weeks :s #feelsBad 22:27:35 alepzi: that's kind of meaningless though because anyone with a commit bit should want to contribute to freebsd 22:27:53 otherwise like, why would they have it 22:28:08 duty 22:28:11 lw, I can't wait for space age, seriously 22:28:12 Volunteer work is the same everywhere. There is no minimum. There is no maximum. It is up to everyone to manage their own burnout. 22:28:20 haha, duty 22:28:36 -__- 22:28:55 * jbo yells some more at autotools 22:29:00 never heard of service beyond yourself lw? 22:29:26 lw, given that you're already in rage mode - would you mind telling me why a python thing is no longer running/working? I tend to stay away from python so... 22:30:08 alepzi: yes, i've heard of it, i think it's nonsense. used variously by neocons, neolibs and marxists to argue why people should conform to their political ideas "because it's for the good of all" 22:30:23 lw, starting cad/freecad shows the window but this error message: https://pastebin.com/Y5yVsuje 22:30:24 Title: 22:29:38 pyException: Traceback (most recent call last): File "", li - Pastebin.com 22:31:07 jbo: uuh, really not sure. looks like an issue with a C++ module. have you tried recompiling all packages? 22:31:23 lw, yeah, this cad/freecad comes from my poudriere repo 22:31:27 jbo: did this happen after you switched from 3.9 to 3.11? 22:31:51 lw i'm sorry ports hurt you in your nono spot. but you can overcome i believe in you!! 22:32:11 alepzi: why would i want to overcome it? it's much easier to just maintain my own local ports tree 22:32:48 alepzi: i am not the only person who has issues with how freebsd ports, works fwiw. although i won't name names. 22:33:00 s/ports,/ports works, 22:33:15 somebody forgot a \ 22:34:12 jbo: you might try pkg upgrade -f just incase somehint didn't get upgraded properly 22:34:19 well ya i think it's a problem pkgs doesn't keep the most 2nd most recent version of a package around. that's a big prob 22:37:33 you're talking a shitload of storage 22:37:42 it's only twice the current amount 22:38:16 it would fix a big hole in the native freebsd pkgs system. that a new pkg can have a bug the old 1 didn't and there's no seameless way to rollback 22:38:22 "only" 22:38:24 pkg install nginx@prior, fixed 22:38:44 2x is an easy multiplier in tech don't sass me 22:39:33 feel free to ask clusteradm how much space a single set takes up, and how doable 2x that is distributed across all the mirrors 22:39:51 they ever come on irc? 22:40:04 other than that, ABI issues. 22:40:53 not public spaces that I've seen, you'll need to email 22:41:25 actually, bapt might be ablr to grab a quote and he's around 22:41:32 i got into an argument with postmaster@ the other month so now i can never email any freebsd.org admins about this stuff 22:41:39 bapt ^ 22:41:42 well, not around right now. probably late in france 22:41:50 france is cool 22:42:03 alepzi: bapt isn't on this channel 22:42:11 i think he's just on efnet 22:42:19 lw, what did you do 22:42:23 jbo: ? 22:42:31 so we have ca 15000 ports, 7 architectures, 3 releases; I'm gonna guess we're talking about 4 TB minimum? 22:42:45 lw, w.r.t postmaster@ argument 22:43:10 jbo: oh, i got annoyed about how they do mail forwarding re: spf and sent a rather rude response 22:43:18 jbo: which was totally my fault 22:43:27 meena: twice as many ports 22:43:43 lw, ease off mate :D 22:43:50 ease of? I don't english very well 22:44:10 jbo: this was like two months ago so the off is eased 22:44:11 meena: that's a few HDs to throw at a permanent and total solution to the "omfg new pkg has bug in it but last was fiiiine" 22:44:24 a few HDs x machine x each mirror 22:44:42 build it and sponsorship will come 22:44:52 * kevans sighs 22:44:58 no datacenter already giving freebsd the homie prices will balk at a few more HDs 22:45:04 we can do it!! 22:45:04 no one is going to sponsor "pkg.freebsd.org but it's one release behind" 22:45:13 anyone who cares about that is bullding their own packages 22:45:38 I have an infant on my chest so I'm just gonna kinda step away and stare at him instead, better for my blood pressure 22:45:43 ya feels like @prior would be a nice middle ground 22:45:56 o/ 22:46:01 [] 22:46:36 alepzi, here's an idea: you could sponsor it. 22:46:57 only if lw gets commit bit 22:47:15 i don't even commit to ports, how would that help 22:47:39 chaos engineering 22:48:10 i think the important thing to understand about pkg.freebsd.org is it's terrible and no one uses it 22:48:19 anyone who is seriously using freebsd builds their own packages with poudriere 22:48:49 I wouldn't call it terrible. It's very difficult to have a "sane default" setup. 22:48:53 pkg.freebsd.org is just a trap for new users so we can pretend we have useful binary packages 22:48:55 i don't think it's terrible it's pretty good tbh 22:49:01 just has this 1 hole i found 22:49:22 alepzi: let's say i was off by a bit, and we're talking more like 12-20 ; to duplicate that means you need to have enough disks in each machine (and enough spares) serving pkg.f.o, and you need to pay for the bandwidth of replicating it. that's a lot of money 22:49:28 jbo: sane defaults is arguable, but waiting 3 weeks to get a security update... 22:49:42 jbo: like the latest issues with armv7/arm64 on the mailing list, fricking hilarious 22:49:59 meena: :( 22:50:01 yeah, bulk builds are a btch 22:50:31 imo easy bin install is table stakes for an OS. call it marketing budget if nothing else 22:50:47 you're right that serious stuff should build their own pkgs 22:50:53 alepzi: if we're talking about onboarding new users, i agree. pkg is better than what we had but it's still bad 22:50:58 the first thing about hardware you gotta consider is that it can fail, so if you want to double your resources, you also need to consider your spares 22:51:08 but this will never be fixed as long as ports czars believe everything is great 22:51:39 lw, I have yet to encounter a developer (or ports committer) who seriously things that everything is great. 22:51:45 this isn't just a pkg issue, the entire ports system is broken 22:52:18 I was referring to ports 22:52:31 okay, another night, another zero lines of code written thanks to IRC 22:52:39 biggest 1-2 ways ports needs to improve? 22:52:51 meena: you can do it!! 22:52:53 alepzi: 1. rearchitect the 2. whole thing 22:52:58 alepzi: i can do sleep, yes 22:53:09 lw funny but concrete shit? 22:53:17 debian solved binaries packages in 1996 22:53:33 freebsd will never solve it because we have ports and it's "good enough" 22:53:45 still not telling me specifics 22:54:01 alepzi: fix whatever needs fixing that makes our ports collection rebuild every time curl does a minor or patch release 22:54:04 yeah honestly i don't care about convincing you about my views on ports 22:54:33 like a hook to autorebuild from source when a new version is tagged? 22:55:11 that would be building hell 22:55:27 lw ya you're just a burnout that wants to shit on freebsd instead of talking about how to improve it that sucks but i want the best for you you can do it!! 22:55:32 what we need is a binary repository 22:55:43 with a release history? 22:55:45 that's what debian did and largely what redhat do and it works great 22:55:59 what do you mean by binary repo? 22:56:10 alepzi: shit on freebsd? sorry, how many patches have i contributed to freebsd this month and how many did you contribute? 22:56:28 big fat 0 my man, wonder why 22:56:29 okay guys, cool it off. 22:56:29 i am happy to talk shit about ports because it's shit, but i also work to improve things 22:56:37 (or of - still not good at english) 22:57:00 what month is it even 22:57:13 November 22:57:14 I think i got 0 the last two months 22:57:21 jbo: good grief, which year?! 22:58:09 meena, 1997! 22:58:15 so, everything is actually quite good :) 22:59:21 pretty sure we still had war in Ex-Ju in 1997 22:59:52 yeah I guess that was not the best of statements I ever made. 23:00:02 jbo: is 4.4BSD out yet or are we still on 4.3BSD? 23:01:10 alepzi: consider this, you can't make something better until you recognise why it's bad 23:01:31 lw that's why i was asking you specifically the 1-2 biggest ways it could improve 23:01:36 you're blinded by hate, burn in it 23:01:40 [00:00:10] [01] [00:00:00] Building devel/cmake-core | cmake-core-3.28.3 23:01:43 oh god... 23:01:46 "1-2" ways doesn't make sense, the entire thing is broken 23:02:00 ports works basically the same way it did when i started using it in 1996 23:02:00 'biggest' 23:02:21 alepzi, many problems/issues arise from design/architecture decisions. 23:02:36 it's not like we can incrementrally fix this 23:02:37 ya i do that all day 23:02:42 it's a redo from start problem 23:02:46 it's like saying "tell me the two biggest ways of transforming this bicycle into a skyscraper" 23:02:46 lw: i think it might be worth looking at what OpenBSD did differently since… 1996 and figure out if we can replicate that 23:02:59 because they don't seem to have the problems we have 23:03:07 yes, i UNDERSTAND, and yet you're still not giving specifics. what do you aim to SOLVE with a complete reengineering other than hand waving? 23:03:18 rearchitecting 23:03:20 meena: didn't openbsd not even provide ports security updates until really recently? 23:03:48 (i don't use openbsd but i heard this) 23:04:04 lw: i have no idea; I've only started trying to add a port to OpenBSD this year, and it seems… fine. mostly 23:04:23 (i don't use OpenBSD either, but, i felt compelled to do it for reasons) 23:04:35 meena, I remember when I added my first port to FreeBSD things seemed... fine. mostly. too :p 23:05:00 alepzi: do you want me to sit here on IRC and describe a complete rearchitecing of the ports framework? ... feel free to post to ports@ or something if you and care and i will respond there 23:05:35 from my limited understanding: OpenBSD doesn't try to do everything in Makefiles; when building Python stuff, they actually use python code 23:05:36 this is not a trivial problem i an explicate in 512 bytes 23:05:46 s/i an/i can/ 23:05:48 ya more blowoff. not surprised 23:06:13 dazzle me with your engineering fu 23:11:17 moved allow.raw_sockets;, devfs_ruleset = 5; and vnet; into /etc/jail.conf from each jail's config in /etc/jail.conf.d/*.conf, and starting jail fails: cannot start jail "testjail": epair42a, 1, ifconfig: siocsifvnet: file exists, jail: tstjail: /sbin/ifconfig epair42b vnet testjail: failed 23:11:28 i'll try putting vnet back in individual jail configs 23:13:42 ok that worked. so allow.raw_sockets; and devfs_ruleset = 5; can both be in /etc/jail.conf, but vnet; has to be in the individual jail config 23:15:48 looks like vars can't be in /etc/jail.conf if they're used in /etc/jail.conf.d/*.conf 23:16:42 exec.clean; can be in /etc/jail.conf 23:18:14 appreciate the hard work. this OS is second to none 23:18:24 exec.consolelog can be in /etc/jail.conf and it can even have the ${name} var in it! 23:18:33 ya freebsd is the best OS ever 23:18:37 :) 23:18:44 full customizable 23:18:46 yum 23:22:38 exec.prestart doesn't seem like it can be in /etc/jail.conf and global for all jails :/ 23:24:04 alright got my jail setup all tight. ty everyone! and even lw 23:41:24 man zfsconcepts doesn't have a section on what a Volume is, or what a File system is, or a Dataset