00:38:18 hi 00:38:22 how does tar --exclude work? 00:38:48 tar vczf qwebirc.tgz qwebirc --exclude 'qwebirc/log/twistd.log.*' 00:38:55 ^ not like this apparently 00:39:25 nor any of the other things I tried (adding ./, and even some weird \/ trick I found on stackoverflow) 00:40:16 ah 00:40:27 brain fart 00:40:57 BSD getopt stops processing options after the first non-option argument, GNU getopt doesn't 00:41:41 well, the synopsis is "tar {-c} [options] [files | directories]" 00:49:36 did you read `man tar` before asking? 00:50:45 yes 00:55:50 and then I remembered that things work differently on GNU. and that what tripped me up was the fact that tar has longopts which practically none of the other BSD tools do 00:56:03 but thanks for assuming I'm ignorant 00:56:08 goodbye 01:00:04 you're not passing the arguments properly, i'm not assuming anything 11:37:23 morning 11:38:31 Hi. 11:39:16 =) 13:29:15 Is OpenBSD's httpd available on FreeBSD? 13:49:33 antranigv: yes, in package obhttpd 13:50:14 kopiyka huh, it's not available on -CURRENT, weird. kopiyka thank you! <3 14:31:54 has anyone measured how much faster CPU equipped with AVX instruction will calculate checksums and other ZFS related stuff on FreeBSD? 14:32:43 in theory AVX should help with some non-multimedia stuff too 14:34:26 I don't think FreeBSD's binary releases use AVX at all, if I understand right 14:34:30 you'd need to compile it yourself 14:35:59 xtile, thnx for clarifying :) 14:41:08 by default, if I understand, most open-source OSes use only the base features of amd64 from back when it came out 14:41:20 https://en.wikipedia.org/wiki/X86-64#Microarchitecture_levels 14:41:22 Title: x86-64 - Wikipedia 14:41:22 the v1 baseline 14:41:32 though RHEL has moved to the v2 subset 14:41:48 Arch GNU/Linux was considering moving to v3 (with measured performance improvements) but I don't think they did 14:41:54 I don't keep up with GNU/Linux much 14:42:22 I'd be interested in a v3 binary release of FreeBSD 14:42:36 considered as a port/architecture like other architectures 17:59:15 ksx4system: AVX2 will be used for raidz2/raidz3 in sufficiently new versions of OpenZFS - but it's just about the only thing in the base system that makes use of it, because as is the case with most kernels, they operate with data at such frequency that the latency of individual assembly instrustions account for a significant amount of the total runtime. 17:59:51 So if you turn on SIMD instructions like MMX and SSE, it can actually make things run slower. 18:01:05 https://cgit.freebsd.org/src/tree/sys/contrib/openzfs/module/zfs/vdev_raidz_math_avx2.c this is the specific code that's responsible for the AVX2 acceleration 18:01:07 Title: vdev_raidz_math_avx2.c « zfs « module « openzfs « contrib « sys - src - FreeBSD source tree 18:02:24 https://agner.org/optimize/instruction_tables.pdf has a complete list of each amd64/x86_64-capable CPU, and how much latency each instruction adds - to give an idea of how big the problem can be. 18:03:25 aha, interesting 18:03:31 It's entirely possible to build FreeBSD that's optimized for the v3 and v4 sets, but the problem is that you then cannot then run it on older systems. 18:04:22 Currently, FreeBSD is optimized for a Pentium Pro aka the i686: https://cgit.freebsd.org/src/tree/contrib/llvm-project/clang/lib/Driver/ToolChains/Arch/X86.cpp#n115 18:04:23 Title: X86.cpp « Arch « ToolChains « Driver « lib « clang « llvm-project « contrib - src - FreeBSD source tree 18:05:40 I think the ideal would be, if FreeBSD project had the computer resources for it 18:05:45 to have a v1 release and v3 release 18:05:51 but I know that takes human and computer time 18:05:59 to support two architectures instead of one 18:06:20 It's not really a question of computer resources, though. 18:06:47 There is nothing in the base system that would benefit from using SIMD instructions in v2 or v3, aside from OpenZFS - and it already uses it. 18:07:52 The data amounts that the kernel operate on and the frequency that it operates on them at are so low and high, respectively, that it'd make things slower for the majority of people. 18:08:02 * xtile nods 18:08:04 makes sense 18:08:11 But it could make a difference for packages 18:08:20 i.e. having not just a v3 release but all the v3 packages 18:08:31 since I know someone studied it for Arch GNU/Linux and did get a performance improvement 18:08:34 rather than slowdown 18:08:42 Package servers already take up +12TB. 18:08:55 FreeBSD isn't Linux. 18:08:58 exactly, it's resources :B 18:09:03 * xtile also nods 18:09:30 Also, please show the work. 18:11:05 https://openbenchmarking.org/result/2103142-HA-UARCHLEVE55 18:11:07 Title: Uarchlevels Performance [2103142-HA-UARCHLEVE55] - OpenBenchmarking.org 18:11:11 https://lists.archlinux.org/pipermail/arch-general/2021-March/048739.html 18:11:13 Title: [arch-general] RFC: Use x86_64-v2 architecture 18:11:17 v3 shows improvement, v2 doesn't 18:14:04 Where's the student Ts, mean vs median vs average values, data confidence, and how have they accounted for the measurability bias that's mentioned in https://www2.ccs.neu.edu/racket/Performance/mytkowicz.pdf ? 18:14:19 ah :B 18:16:07 If you want to build third-party programs with optimizations for a narrow use-case that benefits you, go ahead. 18:16:46 Expecting the project to refactor the entire build infrastructure to solve that problem for a tiny portion of the userbase who have systems that're new enough to take advantage of it is an entirely different can of worms. 18:17:41 * xtile nods! 18:18:04 i wish i knew why i kept crashing 18:18:44 And that's assuming any of that holds up after you've controlled for the statistics principles mentioned above. 18:19:27 Measurability bias alone can produce 40% performance depessimization through the code being linked slightly differently. 18:19:33 interesting 18:20:00 This isn't news, Emery Berger has done two talks on it - called "Performance matters" and "Performance (really) matters" 18:20:52 Also, it isn't the FreeBSD project you should be asking to do this - it's the upstream projects which are responsible for their own build environments. 18:21:22 Packages are built from ports, but ports are just a set of makefiles instructing how s omething should be built using the software's own build tooling. 18:33:23 Anyone happen to have sysutils/openzfs installed? Could you pastebin etc/bash_completion.d/zfs ? 18:33:30 /usr/local that is. 18:35:23 skered: you could just extract the distfile and pick it out by hand, if that's what you're going for 18:40:41 Yeah, just hoping someone already had it. 18:49:47 I know that FreeBSD 14 now has `uuidgen -r` for real random UUIDs, but on other releases, does anyone know if there's a chance of collision? 18:50:33 the whole point of uuid is to avoid collision 19:09:34 skered, My 13.1R system uses zfs and has bash and bash-completion installed but has no zfs file. https://bsd.to/FZyJ/raw 19:09:35 Title: FZyJ 19:10:01 antranigv, I think the v1 UUIDs are unique enough, but they leak the generating host's primary Ethernet MAC address (a privacy concern) 19:47:12 we're now at v4, aren't we 19:51:09 jilles: if a MAC address is a privacy concern, whoever's targeting you can likely see you. 19:57:27 debdrup, the creator of the Melissa virus was tracked down using UUIDv1, so I don't think it's an irrelevant concern 19:58:02 jilles: I think maybe a bit has happened since 1999. 19:58:34 Also, his ISP snitched on him. 19:58:54 That's legitimately the only way it can be used. 20:00:06 https://www.fbi.gov/news/stories/melissa-virus-20th-anniversary-032519 FBI posted quite an interesting retrospective on it a few years ago. 20:00:08 Title: The Melissa Virus — FBI 20:08:09 meena, v4 (random bits) is often suitable but UUID "versions" are really different generation methods and a higher "version" isn't "better" 20:14:04 rwp: You need the port installed not just have zfs from base. But I've already extracted it. 20:14:44 Oh, okay. 20:16:28 Hmm... What is the executive summary of the advantage of having the port installed rather than the one from base? Wouldn't the zfs in base be preferred? 20:17:59 The OpenZFS port exists for people on FreeBSD 12, which has an updated and maintained version of the fork pjd@ made from Illumos back in 2006-7. 20:18:46 If you're on 13 or newer, there's no reason to use the port. 20:20:08 Awesome! Thank you for the information. That is all excellent information for me. I am on 13.1-RELEASE now. Having upgraded from 12 previously. 20:55:27 How much support is there to get freeBSD running on an "older-ish" laptop? 21:01:01 AntiThesis: if you mean something like thinkpad X220 (2011), should work fine 21:01:15 I've ran 12.x and 14-current on a ~2014 laptop, and am currently running 13.1 on another (refurb) that's about as old. 21:02:27 la_mettrie, no, Dell Inspiron 15 21:02:47 i7 processor, touch screen 21:03:15 UEFI was it's only purpose and I am repurposing it 21:03:55 no UEFI, straight legacy, already ripped out the UEFI partition and placed all the BIOS data back on chip 21:04:41 It's acting real skiddish, but I believe a good OS will whip it into shape 21:15:20 jilles: are you telling me you can derive my mac address from cfa343c7-bb9a-11ed-91a1-003048c4c0b6 21:18:02 rtprio: That suggests your box is a SuperMicro. Yes? 22:10:59 AntiThesis, The two areas where FreeBSD kernel is behind the Linux kernel is WiFi driver support and power management for lower power on laptops. 22:11:31 For WiFi there is the wifibox workaround. For older laptops with expired batteries there are power cords. 22:11:57 If those things are not showstoppers for you then everything else is fully functional as any other system. 22:12:48 I have had problems with Dell Inspiron laptops having the bad Broadcom WiFi chips without free driver support anywhere. Beware. 22:21:49 rwp: Does FreeBSD do tick scheduling as well? 22:24:25 mason, I have no idea. Sorry. 22:24:32 I have FreeBSD installed on my Thinkpad x201 which is rather a spare machine for me and don't yet have everything completely to my happy state yet. 22:25:25 WiFi in particular is a challenge. I think I have a bug found in the wpa_supplicant area. I need to find the time to debug more on it. 22:25:29 But on my desktop and servers FreeBSD is performing excellently. 22:25:57 Tick management would be more power savings than performance 22:27:12 Ah, so there might be variations in implementation, but it's there: https://en.wikipedia.org/wiki/Timer_coalescing 22:27:13 Title: Timer coalescing - Wikipedia 22:27:25 I don't have real benchmark data for battery life with FreeBSD on my x201 but... The system is always physically warmer than with a Linux kernel. And it seems like it has much less battery life. But it is also an older battery in that system. 22:32:58 Oh! And as of yet I don't have suspend-resume happy on the x201 either. It resumes the kernel but the display is always stuck dark. 22:33:19 rwp: have you disabled the TPM? 22:33:29 People have suggested trying a few things. I have tried a few workarounds. Haven't really spent a focused effort on it. But nothing suggested has worked yet. 22:34:04 I believe the TPM is disabled on that machine. I'll say yes. But honestly it's been a while and I should look before I commit. 22:34:54 TPM is the one thing that consistently makes suspend/resume work on all the ThinkPads I've owned. 22:35:21 Work by disabling it? (I am pretty sure I have it disabled. Because I just normally disable it.) 22:35:41 It's something to do with FreeBSD not having a driver for it, since it has no use on FreeBSD. 22:35:42 After a suspend-resume I can ssh into the machine. It's alive. But the graphics side of things is not happy. 22:36:06 Have you tried switching vtys? 22:36:20 Have tried switching vt's. Yes. No joy. 22:37:16 If I think of something else, I'll be back. 22:38:29 Sorry. I really wasn't wanting to debug my laptop problems at this moment. (I am trying to do taxes!) 22:38:34 But I was simply giving feedback to AntiThesis about FreeBSD functionality on a laptop. These are the areas that I find most troublesome. 22:38:40 Wish it were better. But other things can make the compromise worthwhile. 22:40:30 I will say, though, that I much prefer having FDE to having suspend/resume - especially when my system boots as quick as it does. 22:41:07 FDE and suspend/resume isn't compatible because S3 STR keeps the encryption key in memory, meaning anyone with access to DMA on the machine can read out the key in memory with very little effort. 22:41:24 Right. I am just doing a full shutdown and full bootup on my x201 right now and it's not seriously a problem for me. 22:41:48 Which is why I had almost forgotten I was having that problem. The main thing I am hitting is what seems to be a bug in wpa_supplicant. 22:42:26 I can't debug it at this moment but it seemed to lock dhclient out of the network device with some exclusive access or something which broke dhclient. 22:42:51 If I manually hacked around it then everything worked okay. But I could not get the two to work together in a native configuration (native without wifibox). 23:25:46 So... I have a stack of old Mac Minis in my closet that won't run any macos newer than 10.6.8. Is it reasonable to turn them back into useful workstations with a modern i386 build of FreeBSD? Trying to figure out what to do with them. 23:27:18 If you try one then you will know and then you can let us know! :-) 23:31:51 They boot up just fine, but I haven't figured out if I can update root certificates, and I can't find any modern browsers with i386 builds. Even palemoon has no i386 version. It's as if everyone things this is obsolete... 23:33:53 I have run into forced obsolescence of other 32-bit hardware in other systems too. :-( 23:34:56 Github website is marginally usable in "w3m" 23:37:27 That's annoying.. I have some Alix systems that absolutely do not need to be replaced, but should be kept current. 23:38:11 parv: thanks, but I'm hoping to make a first workstation for my 8-year-old son. I don't think w3m is in the cards quite yet... ;) 23:39:05 ghoti, No Doubt