00:13:22 * meena should add "subscribe to these mailinglists" onto https://alpha.pkgbase.live 00:13:23 Title: Unofficial FreeBSD pkgbase repository 00:15:02 SamuelMarks: looking at string.h, you need __BSD_VISIBLE; but it should be already set in default compilation environment 00:15:42 yuripv: Define it to what? - This gives an error: /usr/include/sys/limits.h:73:19: error: invalid token at start of a preprocessor expression 00:15:45 #if __BSD_VISIBLE || __ISO_C_VISIBLE >= 1999 00:15:56 * SamuelMarks did `#define __BSD_VISIBLE` 00:16:30 ah, to something non-zero, the check is #if __BSD_VISIBLE, not #ifdef, so it wants some integer 00:16:42 ok `1` should do the trick 00:16:57 Hmm I'm still getting `ld: error: undefined symbol: strnstr` 00:17:13 compiling on FreeBSD? :) 00:19:27 yuripv - Yep, here I just pushed it up https://cirrus-ci.com/task/6010050590801920 00:19:29 Title: Cirrus CI 00:21:08 OH wait that actually worked, weird, OpenBSD it didn't 00:21:12 SamuelMarks: I don't need to define anything to use strnstr() 00:21:26 I'm on 13.2-RELEASE 00:21:43 It should be visible by default if you're not messing with things 00:21:54 I'm having fun: #if defined(__FreeBSD__) || defined(__NetBSD__) || defined(__OpenBSD__) || \ defined(__bsdi__) || defined(__DragonFly__) || defined(BSD) 00:58:21 Hello, is the ue network driver able to do 2.5gb speed? 01:12:43 I would guess no due to being USB && RealTek being involved 01:12:52 s/being// 01:21:14 Wait, there is one another manufacturer with name starting with "A" 01:21:50 * parv gives up for that might have been a WiFi one 01:25:21 parv: AX88179 adapter? 01:27:01 kenrap, Right, that one. Name is "Asix". 01:27:18 It seems that many 2.5gb usb ethernet adapters available are rebranded realteks, so that's disappointing. 01:28:36 https://www.asix.com.tw/en/product/USBEthernet/Super-Speed_USB_Ethernet/AX88179 "NOT FOR NEW DESIGN" 01:28:38 Title: AX88179 USB 3.0 to Gigabit Ethernet | ASIX 01:31:45 parv: I appreciate the help and insight. I'll look for a pcie adapter instead now. 01:32:36 I guess the safest to look for would be an intel nic 01:33:24 Note that I could only guess. Do not have any experience with the hardware you are looking into 01:53:42 Mailling list archive is producing: "Error 503 Backend fetch failed". Is that due to ongoing maintanance or something? 02:01:12 parv: try running a rediculously overclocked RTL8139 /s 02:01:50 wrt 2.5gbps 02:01:54 whoosh 02:02:59 fonks, ^^No idea about your context 02:03:59 eck, I may have pinged the wrong person 02:04:06 joke is ruined :P 02:04:20 kenrap is who I meant to 02:04:36 For shame, fonks! 02:04:46 😞 02:05:26 There's a thought experiment though, could an 8139 run at gigabit speeds 03:17:19 hello everyone, after compiling emacs from ports with changed compile-time options, `pkg upgrade` is trying to upgrade it (28.2_3,3 -> 28.2_4,3). what will happen next? will i lose the compile options and stay with the binary one? or it will compile again to the new version? 04:08:41 crzjp: cant mix and match ports and pkg's 04:09:35 pkgs are compiled with the default compile time options if you need custom pkg's either go all ports opr use poudriere and build your own repo that overrules the default 04:11:42 cpet: thanks for responding, search for more info found i can `pkg lock` the package so `upgrade` will not touch it. is this a good approach? 04:12:00 personally I would do the poudriere approach 04:12:06 but I wouldnt lock it 04:12:48 ok, ill take a look 04:13:07 or send in a PR asking for yourtions to be the default 04:13:23 can be anther approach but it's emacs really doubt you actually need to do that 04:16:03 dunno, the compile option i altered is "--with-nativecomp" (or something like) that permits compiling .el files using libgccjit, there must be a good reason to be off by default 04:20:37 we use clang by default ? 04:21:59 cpet: sorry but I dont know, I'm new to freebsd system and its userland packages 04:22:22 yeah the base compiler is clang we dont use gcc unless required for whatever reason 04:22:55 hmm good to know 04:25:23 emacs with nativecomp is exactly reason for gcc, due to JIT. it is just no one upstream tried clang for that, hence the deal 04:27:25 nice to know too, thank all to the explanation 04:30:02 ill take a look on the mentioned tools and read some docs 04:30:12 good night for everyone! 09:49:37 Demosthenex: i mean nix/guix for defining reproducible systems. more like nixos or guix system i guess 10:28:50 dcunit3d_: ah, yeah, i suggest things like puppet 10:30:00 so i'm troubleshooting a *weird* wifi issue, wireshark shows lots of retransmits and duplicate acks, and ssh behaves *very* poorly, often hanging or disconnecting. then i dropped my mtu in half (1500 -> 800) and though a bit janky, suddenly it's responsive. i drop mtu to 400, and another increase in responsiveness. wtf 10:41:55 yeah, the sweet spot appears about 80 10:41:59 800 :P 10:50:47 Demosthenex: which wifi driver? 12:06:21 meena: iwm ? 12:06:43 its weird, i can ping ok, with some variance in RTT, but if i ssh, it stops and hangs up constantly 12:06:54 wireshark shows dupcliate acks, tcp retransmits, etc 12:15:11 wild 12:16:40 hello folks, i'd like to ask if someone here has experience with a wacom tablet on fbsd. its doing weird things for me like droping inputs rather randomly and i dont know how to approach fixing it. I suspect dbus or other input busses fighting for priority of some sort 12:25:49 meena: so i dropped the mtu to 800, and... it felt more responsive, further decreases didn't help 12:43:44 Hello, on FreeBSD, are the permissions of socket files irrelevant when a user wants to read/write data through the socket? 12:43:44 Is it the permissions of the socket's directory that matters for controlling reading/writing to the socket? 13:08:03 ns12, named pipe? https://en.wikipedia.org/wiki/Named_pipe 13:08:05 Title: Named pipe - Wikipedia 13:08:32 VVD: No, I am talking about unix domain sockets. 13:09:08 what is "socket's directory"? 13:10:04 VVD: e.g. in /path/to/the.socket, the "socket's directory" is /path/to/. 13:11:02 dirname "${socket}" 13:12:02 permissions work same as on files on FS 13:12:39 isn't it? 13:18:30 Demosthenex: wanna check bugzilla for existing bugs and report your findings? 13:28:44 meena: i'm not sure it's freebsd. the wifi is laggy, i'm trying to find out why the mtu impacted it 13:28:56 bad side of the house if you will 13:46:33 hi there, after upgrading 13.1->13.2 i got this message: pkg: Repository MyPudriere has a wrong packagesite, need to re-create database 13:48:43 nevermind... mistake in url ... 14:24:47 Is it possible to explicitly block a hardware, specifically GPU, from recieving power? or to run? 14:53:20 sozuba: yes, in the bios 14:54:02 my nios doesn't have such option, I'll check again though 14:59:40 re-checked, no such option, guess I amjust unlucky 15:09:32 Silliest question ever - I want to get into mailing list for current - if I click on that - just a popup comes and nothing else - cant find application to run ---- any advise ? 15:09:49 freebsd-current⊙Fo 15:10:11 is there a web access to read the discussions 15:29:47 https://lists.freebsd.org/ 15:29:48 Title: FreeBSD Mailing lists 15:30:41 As for opening an application when you click an email; the key word you're looking for is "URI handler" (probably combined with your choice of desktop experience or whatever) 15:33:26 hi :) 15:34:08 i use xsetkb to set keyboard language but I noticed after some time (sleep of monitor) keyboard language resets to defaults 15:34:33 how can I set it permamently or set it automaticaly after sleep? 15:41:12 * wikan must lie down 15:48:33 debdrup: thanks a bunch --- I was wondering why it is such a gap of communication about the FreeBSD 14 status ---- I think people who take care of freebsd.org could link this https://lists.freebsd.org/archives/freebsd-current/ 15:48:35 Title: freebsd-current⊙Fo 16:35:23 cross-posting from Matrix: how would I go about debugging an OpenCL lockup? I cannot seem to run `clpeak` without it locking up my card (AMD Vega 11). Using `clover` and `drm-kmod`. Now if I swap `clover` for `pocl` (i.e. doing the work on the CPU) it works fine. This is on 13.2-RELEASE. 17:00:55 acu: mailing lists have been available on lists.freebsd.org for at least 20 years and is linked from several places (both on the main site, and in addition it's also mentioned in the handbook in the section that specifically talks about updating from source for -current (and -stable)) - so I think maybe it's on you if you somehow missed it. 17:01:40 ShinyCyril: what does "lockup" in this context mean? 17:01:52 ShinyCyril: first step would be to grab the symbols from the kernel-dbg and base-dbg distribution sets and extract them in the root filesystem, then rebuild the relevant ports as described on https://wiki.freebsd.org/DebuggingPorts 17:01:53 Title: DebuggingPorts - FreeBSD Wiki 17:03:12 Even if you could get it to crash rather than lock up (which I take it to mean, it doesn't generate a beep when you hold down more than 6 keys on a keyboard (which is an old trick to generate an NMI which results in beeps), you wouldn't be able to tell what's wrong without debug information. 17:03:44 deebdrup: for sure it is me, thanks for the pointer :) I just humbly suggested that this webpage would link to the lists not start your own desktop email application - https://www.freebsd.org/releases/14.0R/schedule/ 17:03:45 Title: FreeBSD 14.0 Release Process | The FreeBSD Project 17:05:03 meena: the X session basically locks up. If run from a virtual console then the process becomes totally unresponsive and can't be interrupted. 17:05:33 what does dtrace say? 17:06:20 there's an option for control-T to have it print the kernel stack of the process, that might be worth a try 17:06:27 acu: that's the release engineering schedule, which doesn't have anything t o do with the -CURRENT branch; by the time something is being handled by the release engineer, it's already well on its way to a -STABLE branch and will become a -RELEASE in time. 17:06:32 also procstat can print the kernel stack of another process 17:06:54 it's getting stuck on a _umtx_op: https://pastebin.com/ntS14r8v 17:06:55 Title: openat(AT_FDCWD,"/home/mike/.cache/pytools/pdict-v4-pyopencl-invoker-cache-v41-p - Pastebin.com 17:07:33 the above paste is from a different OpenCL application than clpeak, but symptoms are the same. 17:08:19 _umtx_op is the back end of the pthread mutex/condvar functions 17:11:16 acu: also, for what it's worth, those links are there because you're meant to be subscribed to the mailing list (because you can't send to it without being subscribed) 17:13:08 acu: agreed, i'd expect a list info page link, not mailto link 17:13:21 Really? I wouldn't. 17:13:34 debdrup: thanks, sometimes you want just to read :) I am not using 14 current - though it seem I will .... 17:14:34 If I am in 10 mailing lists - my box is flooded - and if I do not have things to say... anyhow thanks again 17:15:08 another question ---- is there a graphic depiction of FREEBSD architecture --- something like this https://developer.ibm.com/articles/l-linux-kernel/ ? 17:15:09 Title: IBM Developer 17:17:40 I like the figures - the depictions give you such a nice gestalt - 17:19:31 RhodiumToad: Control-t output seems to line up with dtrace capture from earlier. I will do some digging with the suggestions provided and see if I can get the callstack. I suspect I'm going to be in the guts of the AMD driver though - not sure what hope there is for me. 17:20:20 Only someone with deep knowledge and years of presence in FreeBSD can build such an useful graphic depiction of freebsd architecture - which is so fundamental for new comers and aspirational FreeBSdears :) 17:22:56 There's https://nullrouted.org/uploads/freebsdobservabilitytools.svg - which is more meant to give you an overview of what tools can be used to get information out of certain subsystems (though argualy that's more useful). 17:23:20 Brendan Gregg made that almost a decade ago, I just converted it to a svg at some point. 17:25:26 that's a great diagram! Brendan Gregg is a fountain of knowledge. 17:25:28 very nice - thanks debdrup and brendan - it is a good start - but I like that it mentions tools you can use to dig in :) nice ... 17:26:02 I have to print it an pin it on the wall :) 17:26:17 That's why it's an svg ;) 17:27:54 that is awesome diagram, thx 17:34:48 I think the IBM article about linux kernel architecture can be used to make one about FreeBSD - I know all the info is there I assume --- https://docs.freebsd.org/en/books/arch-handbook/book/- it just needs someone who knows to put it together ---- 17:36:51 This article is so well written - even I can understand it :) https://developer.ibm.com/articles/l-linux-kernel/ 17:36:52 Title: IBM Developer 17:37:38 It was writen in 2007 - I wonder how valid is today 17:38:38 debian released version 12 with kernel 16 I think - https://www.debian.org/News/2023/20230610 17:38:39 Title: Debian -- News -- Debian 12 "bookworm" released 17:40:36 It will be interesting how far the split is between Linux and Unix (FreeBSD) ---- comparing Debian 12 with FreeBSD 14 would be an amazing article :) 17:41:20 Why does a USB device change from /dev/ttyU0 to /dev/ttyU1 (and back) w/o being unplugged? I have a daemon that hangs if the USB device changes. 17:41:47 Slowly, applications written for Linux will be more and more difficult to port to FreeBSD - I assume --- I just see that a new gimmick was included - systemd-resolved... other neurons required :) 17:42:43 makes sense why Linus Torvalds does not like distributions :) 17:43:27 Hi, got a quick question about the GELI/root-on-zfs combo in the installer: where are the GELI keys if you want to change your user key? /boot after the system is up does not contain them, and the boot pool's mount point is empty despite the pool showing as mounted 17:44:00 I believe the installer only sets a password 17:45:30 right, I'm pretty new and ignorant and thought there was no such thing as "only a password" from poking through the manpage. So I can just change it without specifying any keyfile? 17:46:40 if it's already attached, you can change keyfiles and/or passwords freely 17:47:44 hrm 17:47:50 but if you set a keyfile, then you have to be careful about whether the boot sequence can get at it early enough 17:50:16 are you using uefi or legacy boot? 17:50:16 I'm not at all interested in doing so if I can go without, so that's fine. The manpage just made it sound like a master key was a mandatory part of the setup 17:50:20 UEFI 17:51:14 the master key is mandatory, that's stored (encrypted) on the provider and nowhere else 17:51:56 there are two slots for storing the encrypted master key, each of which can be encrypted by a different keyfile/password combination 17:53:11 oh, there is also usually a backup of the provider metadata in /var/backup, which contains the encrypted master key under the user key(s) in effect at the time the backup was made 17:53:33 but for a root filesystem that's not much use unless you copy them elsewhere :-) 17:53:59 thank you 17:54:03 so just specifying the provider e.g. /dev/nvXpY is enough? 17:54:27 to change a user key? yes 17:54:39 yep, just want to nuke the old one 17:54:40 alright 17:56:15 I guess I also need to destroy the old copy of the master key once this is confirmed to work 17:58:40 when i look at the associated /dev/blahblah.eli in geli list, is UsedKey the keyslot? 17:59:48 or uh, can I otherwise somehow confirm what keyslots I use on a provider? 18:01:48 hm no 18:06:32 UsedKey seems to be which slot was used to attach the provider with 18:09:41 ok thanks, looks like all is well now 18:09:53 huh. looks like geli setkey on a detached provider is broken 18:12:00 huh ok, I found a bug report on that... like so? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254966 18:12:02 Title: 254966 – geli setkey not working with detached provider 18:14:03 wonderful, another two-year-old bug not handled 18:14:19 with a patch, too! 18:15:02 * meena with be at the computer after putting kiddo to sleep 18:15:11 did you just assign it to geom@ or was that already done? 18:15:21 In an hour or eight 18:15:42 RhodiumToad: i just set it from new to open (and probably added myself to cc) 18:16:12 makes me wonder who geom@ is 18:16:26 it's a mailing list 18:17:22 I was wondering why it didn't appear on the twice-monthly list of open bugs, but apparently that only gets bugs marked Open/In progress and not ones marked New 18:18:06 so thanks for setting it to Open, at least that should make it show up :-) 18:19:36 🤦🏻‍♀️ 18:20:09 RhodiumToad: does that Patch make sense? 18:21:27 I absolutely loathe seeing #if 0 in code 18:22:46 the patch looks plausible? I haven't looked at the surrounding code in detail 18:24:28 I'm trying to, but my focus is kinda hosed 18:33:33 loads of new bugs that aren't open / properly assigned 19:00:58 there also seems to be something wrong with geli setkey's choice of number of rounds of key distribution 19:04:02 i don't know posix well enough to know if this is a bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271817 19:04:05 Title: 271817 – sed: range change with N results in no output 19:07:23 why can i assign these ppp crasher bugs to? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271843 19:07:25 Title: 271843 – ppp can crash due to wrapping subtract in FsmRecvEchoReq() 19:09:14 that sed one is tricky, I don't think either the actual result or the reporter's "expected" result are correct 19:46:48 anyone ever wanted/needed a threadsafe way for a process running as root to open a file using the creds of a non-root user? 19:47:49 there's a bunch of cases in base where programs do that, but only by using seteuid to temporarily switch the whole process's creds 19:55:07 RhodiumToad: feels like something you'd be able to do with mac(4) 19:55:48 I don't think so 19:56:35 the main case where it comes up is where root needs to read files from a user's $HOME. Due to the vagaries of NFS, it can't assume that it can do that with root's creds 19:57:49 re: sed, nowadays it's usually "what gnu sed does" (that matches the "expected" output) 19:59:05 gnu sed is clearly wrong 20:00:30 here's how the spec interprets it: 20:00:54 first we read the line "a" into the pattern space and start the first cycle 20:01:14 the start address of the c command matches, so we then delete the pattern space 20:02:26 we are not addressing the last line, so the N command appends a newline and the line "b" to the pattern space 20:05:49 the spec isn't 100% clear what happens next, but on reaching the end of the script, it should write the pattern space, delete it, and start the next cycle. 20:06:15 Wonder how the SysV Unices behave in reality. 20:06:21 Since the standard's usually written to match them. 20:06:31 I'm not sure why this doesn't write "\nb\n" to the output, unless the pattern space is somehow still being considered as "deleted" thanks to the c command 20:07:16 anyway, the next thing is that we read the line "c" into the pattern space, it doesn't match /b/ so it gets deleted, 20:07:38 then we append a newline and "d" and the same happens as at the end of the first cycle 20:09:01 and again for "e" and "f", but notice that we just read the last line using N 20:09:30 and at that point we terminate without writing "x" (because the c command never ran on the last line of the input) 20:11:46 so the only thing I know is wrong is the "expected" output in that report, there is no way to justify that based on the spec 20:21:56 RhodiumToad: do you wanna update the bug with your analysis? 20:22:16 I literally just hit send 20:22:25 I'm just wondering, what's this delay about with FreeBSD 14-RELEASE? 20:22:40 it seems to have been on track since 25 April but then? 20:22:48 https://www.freebsd.org/releases/14.0R/schedule/ 20:22:49 Title: FreeBSD 14.0 Release Process | The FreeBSD Project 20:23:03 wildeboskat: openssl 3.x 20:23:11 Ah ok 20:23:14 Compile problems? 20:23:24 Word on the st... what RhodiumToad said. 20:23:25 No, updating OpenSSL 1.1.x to 3.0. 20:23:33 There's a thread on current@ about it. 20:23:42 Ah what's current@? 20:23:45 I'd like to follow it 20:23:51 Good that they update OpenSSL tho 20:23:55 https://lists.freebsd.org 20:23:56 Title: FreeBSD Mailing lists 20:23:58 everything that uses openssl, in base and in important ports, has to be updated to allow it to use the openssl 3.x API 20:24:36 Thanks debdrup 20:25:02 It's a pretty significant amount of work, yeah. 20:25:52 Yeah that sounds like a lot 20:26:32 but with openssl 1.x going EOL so soon, it's not an optional task 20:27:22 I'm surprised they only decided this at the last moment but ok, it's a good thing to take on board 20:28:07 wildeboskat: it's a lot of work, and we've only now gotten a dedicated person on the task 20:28:43 And there's no hurry, 13 works fine :3 20:28:57 I was just wondering what happened 20:29:56 Also llvm 15 20:30:43 usually emaste would have worked on OpenSSL, but he was also very busy with LLVM integration work 20:33:16 what's in llvm15? 20:33:18 It's only 14-CURRENT that gets OpenSSL 3.x. 20:33:35 (13-stable has llvm15 too, fwiw) 20:33:40 Err, it's only what'll become 14.0-RELEASE that'll get OpenSSL 3.0* 20:34:48 RhodiumToad: i dunno, but loads of ports were failing to build with llvm 15 20:40:56 Conflicting types for dma_buf_stat ? 20:42:07 looks like it's stricter about warning about integer conversions 20:46:07 On console (in vt, 13/stable), why do I not get color in manual page rendered with "env MANCOLOR=1 man man"? 20:47:30 Bold & underline or italic rendered text is also misisng 20:50:34 is it missing in "man man" without messing with the environment? 20:50:49 Yes 20:52:06 I don't even get color in xterm, trying it now. 20:52:26 FreeBSD VM runs in VirutalBox if that would matter (though I would doubt) 21:04:16 TERM is set to "xterm" after log-in; I do not set that anywhere (set "xterm-color" for X11 session). I see root ~/.profile sets that 21:04:58 does CLICOLOR=1 ls -l get you colorized output? 21:05:26 Yes 21:06:04 what's the output of tput Co ? 21:06:43 No success with env TERM=xterm-color MANCOLOR=1 man man 21:06:53 RhodiumToad, That prints 8 21:08:05 and tput AX; echo $? 21:08:33 "1" 21:08:58 looking at man (it's shell script), all MANCOLOR does is modifying the MANPAGER to be `less -sR` (-R to allow ansi color codes) 21:09:22 something has to output those colors, and mandoc doesn't? 21:09:52 my $LESS is '-SsiXR' 21:11:54 I see expected colors and/or text with bold (depending on xterm configuration), etc attributes in X11 session on xterm 21:12:37 when doing what? 21:13:07 RhodiumToad, Asking me? Seeing a manual page 21:13:29 can you give an example of what manual page and what specific text you see in color? 21:17:10 Did "man man". "Name" header & name "man" are in green (for bold text); "Synposis", "man" & option names are in green, option values are in yellow (for underline or italic). Screentshot coming up 21:17:37 what freebsd version? 21:19:15 FreeBSD gaia 13.2-STABLE FreeBSD 13.2-STABLE zfs-arc-unit-B-n254945-b6310a2f8eaa INVM-efi amd64 21:21:06 if it's your xterm configuration, why do you expect vt to follow it? 21:21:45 vt uses xterm control sequences and termcap entry 21:22:00 but it does not use xterm configuration 21:22:39 parv: what do you have in the environment? 21:22:55 yuripv, I never did 21:24:46 Does "man man" supposed to display a manual page without any bold/italic or colors on vt? 21:25:09 I have so far failed to display any manpage in color on any terminal 21:25:45 Do you get bold or italic or underlined text? 21:26:02 yes, but note that it's less that renders that, not man 21:26:37 Yes, I understand. Here I am getting nothing 21:27:09 what do you have in the environment 21:27:45 env (on vt in zsh): https://termbin.com/1syh 21:32:11 Screenshot promised of xterm: https://files.mastodon.social/media_attachments/files/110/567/349/654/700/294/original/3135eb1a91f3d47b.png 21:33:31 How interesting. 21:33:47 parv: what is your TERM set to under vt? 21:34:13 meena, "xterm" 21:35:19 your colorized prompt works in vt, or not? 21:35:26 appres XTerm? 21:35:36 also what's the env when running in xterm 21:36:02 RhodiumToad, env in X11 session: https://termbin.com/geqp 21:36:37 RhodiumToad, Yes colorized prompt produces color on vt 21:37:52 do you still get colored output from man on xterm if you do env -U TERMCAP man man ? 21:37:54 er 21:37:57 do you still get colored output from man on xterm if you do env -u TERMCAP man man ? 21:38:02 Ok here is the thing: I need to restart VM in order to see text on vt after switching from Xorg. Will star X11 to show the resources for xterm 21:39:04 don't get uploaded into a pdp-11 21:39:11 oh right, i've been meaning to ask another thing 21:39:32 i have a host where the anope package segfaults for me on start 21:40:45 yuripv, I do not have "appres" installed, so Xresources: https://termbin.com/6cca 21:41:44 RhodiumToad, Re env -u TERMCAP, yes still same colors are produced in xterm 21:41:44 well, i should probably do some more troubleshooting on this first, so disregard 21:42:31 parv: what's the output of type mandoc 21:43:02 RhodiumToad, "mandoc is /usr/bin/mandoc" 21:43:22 and the output of man -dd man 21:44:16 man -dd: https://termbin.com/wwyb 21:44:40 that's in the vt? 21:44:52 No that is in xterm 21:46:13 where'd that get \less from? 21:46:31 That is from $PAGER 21:47:26 man -dd output looks similar enough on vt 21:48:12 I don't see a PAGER in the env you posted for xterm? 21:49:20 After "unset PAGER", output of "man -dd" changes to "zcat ... | mandoc | less -s" 21:50:58 and do you get color in that case if you omit the -dd ? 21:51:49 No. 21:51:56 note that PAGER is ignored if MANCOLOR is set 21:52:37 with MANCOLOR set, what does man -dd man output on xterm? 21:56:27 you have the colors set for bold, underline in those resources 21:56:48 aha. 21:57:37 In vt. Seems like I could differentiate between bold & not-bold text with "Terminus BSD Console, size 32" font. After unsetting PAGER (env https://termbin.com/ody0), "man man >x " produced escape codes that I see in the editor but cannot differentiate in pager 21:58:07 s/could differentiate/could NOT differentiate/ 21:58:08 I have 1 for $MANCOLOR but I never managed to get colour. An ELI5 guide would be nice. 21:58:37 you won't get colors unless you modify mandoc to output them 21:58:40 redirecting output of man may change the behavior 21:59:09 Thank you RhodiumToad, yuripv, meena 21:59:12 (Too much for me to follow here.) 21:59:33 grahamperrin: as far as I can tell manpages can't actually produce color unless they're using groff, which base system ones don't 21:59:41 parv: i see bold in vt in vmware vm 21:59:57 grahamperrin: parv was using an xterm configuration that changes bold/underline to colors 21:59:57 Oh right :-( 22:00:20 and obviously that doesn't work in vt 22:00:26 I wonder what happened to the project to get better manual pages online. 22:00:58 no underline though (as well as no italics) 22:01:44 grahamperrin: you mean the web ones? 22:02:07 iirc, the web thing was doing something differently to what mandoc's html output does 22:02:28 (possibly it existed before that mandoc option did) 22:02:54 I need to find something that would make those (bold, underline) attributes in a manual page more obvious ... 22:03:06 ... on console 22:04:34 With "MANCOLOR" listed in "man(1)" I thought I should be able to see such. But as RhodiumToad mentioned earlier, that is not to be 22:05:18 .oO( Man(!), what a goose chase .. ) 22:05:21 parv: how does it look like for you in vt? 22:06:45 RhodiumToad: it certainly looked very different, more importantly the anchoring was great. I hope it happens. 22:06:54 yuripv, All text look the same; cannot identify if some important note easily without a search (found term is shown in reverse-video) 22:07:14 vbox right? 22:08:05 Yes 22:08:49 also uefi or bios? 22:09:57 yuripv, Screenshot of "man man" on vt: https://files.mastodon.social/media_attachments/files/110/567/496/978/742/583/original/0a1f36bfbe2e75c5.png 22:10:57 yeah, i have the bold text shown as bright 22:11:09 same terminus font 22:11:57 yuripv, UEFI, well "EFI" in VirtualBox settings. /boot/efi is empty on FreeBSD side 22:13:22 i mean vga, or efifb, or kms driver for vt 22:14:09 so far for me vmware/efifb/terminus shows bold as bright, no underline/italics 22:20:23 The only relevant "vt" or "fb" I see in "dmesg" output is "VT(efifb)" 22:21:01 the backend for vt shouldn't have much effect on its behavior, afaik 22:21:24 it's basically manipulating a framebuffer 22:23:55 Changed "kern.vt.color.(7|15).rgb" in "/boot/loader.conf" to #f0f0f0 (near bright white) & #f0c0c0 (pinkish) to no difference other than text is now pinkish 22:25:22 https://termbin.com/alox0 22:26:19 you said you had color in vt with ls (with CLICOLOR=1), so color escapes are obviously working, no? 22:27:57 RhodiumToad, Yes, color in ls output & shell prompt are visible 22:28:52 Now I am just testing if I might have decreased intensity of "bold" text 23:15:08 Checked that disabling "allscreens_flags='-f terminus-b32.fnt'" does not produce text of different intensities|colors in "man" output 23:15:50 Next is to test disabling "blanktime" ... 23:18:40 ... nope 23:20:29 I give up 23:22:33 meena: I finished with that sed bug report.