00:02:40 what is this? https://github.com/freebsd/freebsd-src/tree/main/stand/kboot good for? 00:02:41 Title: freebsd-src/stand/kboot at main · freebsd/freebsd-src · GitHub 00:17:02 It's an implementation of an API found in Linux, iirc. 00:18:49 It makes a kind of sense given who's paying for the work if you consider what they might want (or, more likely have, since there's a delay between something being tested in production at Netflix and it going into the FreeBSD tree). 00:20:03 Unless they've been making big architectural changes that they've yet to talk about, their front-end is Linux on a butt provider while FreeBSD provides the data-intensive part of the CDN in the form of Open Connect Appliances. 00:20:49 All of this is public information, and they've been fairly vocal about all of it - the secret sauce of how they can handle about a third of the internets traffic at its peak is in the configuration. 00:21:35 The configuration and its associated institutional knowledge (and by extension the engineers that configured it). 00:22:36 That latter part will, I believe, turn out to be more significant - a fact that might be dawning on people who're trying to run a certain bird site. 00:22:56 s/run/ruin/ :-) 00:23:57 Well, yes. 00:24:33 It's not like infrastructure degrades instantly if the people with institutional knowledge disappear, but usually by the time it does it'll be too late to do anything about it. 00:25:28 And institutional knowledge isn't really something you can document your way out of, because much of it is knowing 1) what has been tried in the past and 2) just as importantly, if not more, how those attempts failed 02:10:49 debdrup: so history is the best documentation 07:52:13 hello 07:52:28 can I set a static dns server in some other way then adding it to resolv.conf ? 07:52:38 wg-down quick empties resolv.conf 07:52:44 and I have to readd manually 07:53:29 you cant. but you should check what to do about that wg-down to get dns servers back 07:55:46 hehe yeah thats probably a better idea, thanks 07:55:58 removing DNS = from wg.conf was only thing needed 10:22:51 exit 10:51:47 https://man.freebsd.org/install(1)#COMPATIBILITY "Historically install moved files by default. The default was changed to copy in FreeBSD 4.4." — okay, but how do i get the old behaviour? 10:51:48 Title: install(1) 10:53:00 looks like there's no way, so you have to delete the old one yourself 11:46:25 ngortheone: that's not what I said. 11:50:16 * meena points at the fall vs decline of (Western) Rome discussion historians have been having for 150 years now 12:58:12 i'm having an issue with my server 12:58:39 all the 4 drives plugged to the controller are spamming dmesg with errors 12:59:03 and of the mirrors is stuck ain a resilvering loop 12:59:33 i would like to replace the disk controller but is it safe, provided the resilvering is going? 13:01:08 ISTR someone here saying resilvering is resumable across reboots, but don't take my word for it. 13:20:11 ZFS resilvers won't be affected by a reboot except that it'll add however long the reboot takes to finish the resilver. 13:20:57 Only thing that can cause problems during a resilver is if there's an URE and not enough data availability to fix the issue, or if there's catastrophic hardware failure. 13:37:41 ok, thanks 13:37:53 then i'll try to replace the controller 14:01:46 wouldn't it be really cool if Phab linked to bugzilla when someone opens a review with PR: pr-number ? 14:02:08 https://reviews.freebsd.org/D38370 14:02:09 Title: ⚙ D38370 certctl(8): Remove untrusted certificates from TRUSTPATH 19:26:01 so i'm using some command line utiliuties that werte normally built for linux and it looks like pipes are not working correctly or there is something with the /bin/sh. is there some shell debugging i can use to see what is going on? 19:27:38 CCFL_Man: first line 19:27:44 #!/bin/sh -x 19:28:00 to echo all commands including values of variables 19:28:38 use `set -x` to activate this from some line on, and `set +x` to turn it off again. 19:30:52 And you could write to stderr without disturbing stdout (which is mainly used by the pipes) by `echo "my Vari is ${vari}" >&2` or `printf "something %s here\n" "${vari}" >&2` or `date >&2` etc. 19:34:54 Echoing to a log file via setting a log file `LOG=/tmp/my.log` and using things like `echo "my Vari ${vari}" >> ${LOG} in the script, while using some `tail -F /tmp/my.log` in another terminal (`-F` means: stay on file, not inode, and continue cat-ing it.) You can use `\n`-Keys to add empty lines in the tail-output for your convinience, and can 19:34:54 even write there (is not added to the log file) 19:37:04 and to copy a pipes output to a log file (maybe using `tail -F /tmp/my.log` again) something like 19:38:02 `mycommand  parameters | tee -a /tmp/my.log | secondcommand params` as tee(1) does copy to the file (`-a` for appending) 19:38:18 does that help? 19:38:52 do we support set -o pipefail ? 19:40:58 according to the manual page sh(1) yes :-) (I take it, you did mean that.). One could write some test to test it. 19:42:55 yes 19:55:49 sh -x vtcat -vvv @vlf44:1 -- -,f4 | vtwrite -L /mnt/nas/vlf44/log/vtwrite_32k.log -G 3600 19:55:52 sh: cannot open vtcat: No such file or directory 19:56:40 vtcat exists and can be called directly, but with that pipe, vtcat returns no error 19:56:59 CCFL_Man: full qualified path instead? 19:57:08 ahh 19:58:36 that still returns the usage help output of vtcat 19:59:19 now, that command string will work fine on linux systems, but i'm trying to debug why it won't run on freebsd 20:00:53 in Linux the sh is a bash called sh, in freeBSD it is a real sh. Might there be the problem? 20:01:14 is vtcat a shell script? 20:01:17 Kalten: Depends on the Linux. Debian, sh is dash, like FreeBSD's ash. 20:05:31 mason: good to know. I thought, all Linux distributions used bash in place of sh. Interesting... 20:05:44 no, vtcat is a compiled program. do you think i should contact the author? 20:06:01 perhaps it's not a freebsd or shell issue 20:06:02 The real sh was Stephen Bourne, and ash was, of course, written by Kenneth Almquist. 20:06:07 was written by* 20:06:27 I had to look up their first names :( 20:07:04 CCFL_Man: mbut you have compiled it for FreeBSD? 20:08:03 yes. i can use the other functions of the program without issue 20:08:20 `truss /path/vtcat -vvv @vlf44:1 -- -,f4 | /path/vtwrite -L /mnt/nas/vlf44/log/vtwrite_32k.log -G 3600` would tell you far more. 20:08:34 let me try that 20:08:44 buckle up ;-) 20:10:24 'truss, right? 20:11:58 truss(1) traces system calls. plenty of output—hence: buckle up :-) 20:12:21 sometime it helps 20:15:07 what is this vtcat and vtwrite thing? 20:16:35 if I remember correctly, it's VLF signal processing software 20:17:15 i have vague memories of messing around with it when I was an active HAM 20:19:59 Kalten: Is that packaged? If so others might have an easier time looking. If it's not, maybe pull out that vtcat invocation and run it alone, see if it has a usage message, etc. 20:20:15 Sorry, tabfail. CCFL_Man ^ 20:20:31 debdrup: I meant that historical records can serve as a missing link, an addition to traditional documentation. As an answer to what was tried and how/why things failed. Sorry if my comment was a bit out of context :) 20:22:18 Kalten: that is good information. i think i'lk post it to the author 20:23:16 mason: it's not packaged, but i can use vtcat in other ways with a pipe, but with that spefic pipe and format output "-- -,f4", it fails on freebsd 20:23:44 debdrup: you used vlfrx-tools before? i use it all the time. have you done vlf study? 20:24:14 CCFL_Man: I was only messing around with it on a hobby level 20:24:45 mason: you are mistaken: CCFL_Man is the one using it, not I. ;-) 20:25:12 Kalten: Yeah, that's what I meant by tabfail. 20:25:26 ah! Did not read on prior to replying :-) 20:25:29 CCFL_Man: Why the sh -x out of curiosity? Can you just run it without that? 20:25:34 Kalten: No worries. :) 20:26:16 CCFL_Man: Also, if it's some funny shell behaviour, you can always try other shells. Like, pkg install bash and try /usr/local/bin/bash instead of sh 20:26:20 that was for debug output to see where it was failing 20:26:41 normally `--` means, that only filenames follow, no parameters. Normaly `-` stand in for stdout. Could the order of the parameters be a problem? 20:26:47 i have bash installed. using bash doesn't make a difference 20:27:41 maybe, but that was the order in the authors documentation which he runs it on linux 20:27:49 mason: He had asked for help how to debug sh, but it is not a shell script. 20:28:11 Oh, I see. I'd missed a bunch of scrollback. 20:28:30 CCFL_Man: by default it is tcsh as interactive user (and root) shell, not sh. 20:29:13 what do the parameters stand for? 20:31:33 You can also just run 'set -x' and 'set +x' to turn debugging on/off in sh (and bash) 20:32:18 -x mode will print how variables are being expanded. 20:33:20 Most often used in debugging shell scripts, I could see it being useful for debugging interactive shell settings as well. 20:33:53 CCFL_Man: I would write a shell script to wrapp your call anyway—it sometimes spares aou trouble with user settings in there shells. Far easier to handle that way, I think 20:37:51 Kalten: this is the script i wrote: https://bpa.st/2ICVC 20:37:52 Title: View paste 2ICVC 20:38:03 CrtxReavr: thanks. i put that in my notes 20:41:01 * CrtxReavr wonders who he has on /ignore 20:42:32 I would use /bin/sh on freeBSD. You might want to at least wait a bit after killing those programms: maybe in line 11 some `sleep 10` to be shure. Line 12: if there was no first parameter, the script would abort (at least in sh). better use `if [ ."$1" = ."start" -o ."$1" = "restart" ]; then`. line 39: should be `fi` not `f` I guess 20:43:52 Sorry: in line 12: forgot the `.` at ` = ."restart" ]; then` 21:08:02 Oh yes. . . 21:30:26 Kalten: no . before "restart" and '; then' after the closed bracket? 21:45:36 CCFL_Man: My line after the long one states . before "restart ;-) The `;` allows you to write the `then` in the same line as the `if` (I am just used to it). But the space after `[` and before `]` are necessary! Actually `[` is an alias for `test`, hence the manual page for `[` is the same as that for test(1) 21:49:14 one can spend quite some time to figure that space problem out :-( 22:22:10 Hello! As I wrote earlier in this chat, I've been reading the FreeBSD HandBook for several days now. At the moment I have a rather general question. Now the Gentoo Linux operating system is installed on my computer, I watch movies on my computer, listen to music, of course I visit the Internet (through the Firefox browser), I study the Emacs text editor (I want to keep my notes in it), I am interested in computer technologies if 22:22:10 possible and sometimes I play into games through the Steam game client installed through Flatpak. Can you please tell me what problems I might have if I install FreeBSD as the main operating system? 22:24:38 movies, music, firefox (including videos), emacs should work fine ...don't know about steam 22:24:43 Kit_Leopold: Probably no problems. Videochat can be a challenge maybe. If you have bluetooth peripherals, they can sometimes be problemtic. Exotic hardware (say, keyboard with uhids) can be exciting. 22:25:00 Oh, Steam. Steam is a perennial question. 22:28:29 Yesterday I started FreeBSD LiveCD on my computer, I was able to check the sound and my video card (AMD Rx 550) was detected in the system. But so far, I have not yet decided to install the system. I think we need to be better prepared. 22:29:35 la_mettrie: Thank you. 22:30:19 mason: Steam doesn't work well on FreeBSD? 22:32:00 Kit_Leopold: It seems challenging. I've only heard about it second-hand. My only gaming on FreeBSD is free software or Wine. 22:33:23 mason: Thanks for the answer. 22:34:19 Kit_Leopold: In short, anything that's actually free software should be a fairly safe bet. 22:37:44 With the exception of the Steam game client, the software on my computer is released under a free license. Thank you. 22:41:12 Kit_Leopold, there are some FreeBSD based pre-built desktop distributions. . . which might be good to start with. 22:42:31 Kit_Leopold, I have never tried steam, but I know that this port exists and is actively maintained: https://www.freshports.org/games/linux-steam-utils/ 22:42:32 Title: FreshPorts -- games/linux-steam-utils: Steam launcher for FreeBSD 22:43:15 Acutally, we may be down to only one: https://hellosystem.github.io/docs/ 22:43:16 Title: hello — helloSystem documentation 22:45:41 salvadore: Thanks for the link to the port, I'll definitely read it. 22:47:21 CrtxReavr: Thank you for the tip. I think it's best to be familiar with the underlying FreeBSD system for a better experience with the operating system. 22:48:50 There's an argument for that. 22:49:40 Kit_Leopold, this might also be very useful for you: https://github.com/shkhln/linuxulator-steam-utils/wiki/Compatibility 22:49:41 Title: Compatibility · shkhln/linuxulator-steam-utils Wiki · GitHub 22:49:52 it has been written by the port's maintainer 22:50:03 or at least edited 22:50:06 Sorry if I'm not clear, I'm using google translator. 22:50:51 My counter-point to that, however, is that I've maintained FreeBSD workstations over many years. . . using them for my professional "daily-driver." 22:51:04 And you can get 'em setup really nice, and doing what you like. 22:51:16 But. . . un-expected shit can break things. 22:52:00 And it can take some doing to get them right again. . . even if you're strong with FreeBSD, and the ports/package system. 22:52:46 A distro like helloSystem can insulate you from the majority of that, when you need a workstation/laptop to Just Work(tm). 22:55:54 If, after reading all the information about using the Steam game client, I decide that running Steam on a FreeBSD operating system is too complicated... I'll use a second Windows system and that's it. 22:56:43 You are very good people, thank you. 22:57:51 (Ha! Fooled them!) 23:15:36 TIL you can *set* the media type with ifconfig. 23:34:35 meena: this is how I usually test Gigbit ethernet :) 23:35:55 ngortheone: cool 23:36:34 well, anyway, i regret learning how to list infiniband devices… and if you're curious why, look up ibv_devices and how it's build 23:40:15 what is infiniband and why would a mere mortal need it? and where? (out of curiosity) 23:41:04 ngortheone: trying to refactor cloud-init network functions 23:41:30 infiniband is very very very low-latency networking, often used in either storage, or high-performance clusters. 23:42:16 so, even tho Ethernet can outperform Infiniband in speed these days, it's got nothing on it in terms of latency, and where that's important, infiniband is still often used. 23:43:02 TIL infiniband exists :) 23:45:13 I was watching Netflix's presentations about pushing 800 Gbps per core on a FreeBSD box, and the guy said that despite SCTP/QUICK and other things exist regular TCP has such an optimizied kernel impl. by now that it still outperforms new protocols. 23:45:29 I wonder if you can talk TCP over infiniband? 23:46:19 as I understand infiniband is the link-layer protocol, that requires different hardware (NICs and cables), right? 23:46:25 IPoIB, yes 23:56:01 and yes, different NICs, cables, switches 23:56:15 sometimes different nices :-) 23:56:18 nics, even 23:56:27 (there are nics that can do both if and eth)