00:23:07 10$ 02:10:14 lw, your mediaelch PR is now the next in the queue 02:10:23 exciting! 02:10:37 i hope it's actually fixed this time 02:11:32 I hope so too because each run eats up like 2 to 3 hours of my build machine time :p 02:13:32 i wouldn't mind giving you a shell here to test it, except since this is the last one (other than sublime which is fairly quick) it's probably not worth it... 02:14:01 that's nice - thanks. but all good 02:14:10 it's just part of the job, nothing wrong with that :) 02:56:24 do we not have nv(9) in userland? 02:56:44 that library was so useful on solaris 02:59:33 meena: i have created a git repository for dladm (except it's called dlctl now). let's see what happens! 03:07:03 lw, unless the Solaris library is something different, that's a work in progress in Phabricator, IIRC. 03:08:09 V_PauAmma_V: yeah, it's the solaris library that (iirc) was imported for zfs 03:29:58 what is the connection between netlink(4), genetlink(4) and rtnetlink(4)? it looks like rtnetlink can configure interfaces, so if that's all i want to do, i should just use that? the manpages are a bit vague 03:30:56 I think rtnetlink is for routing? 03:32:16 you'd think that given the name, but the manual page says it's for "interfaces, interface addresses, routes, nexthops and arp/ndp neighbors" and it deals with creating/destroying entire interfaces 03:34:03 what i'm trying to do is get a kqueue event whenever an interface/address/route/whatever is modified, it's not really clear to me if rtnetlink even does this 03:34:42 i know this functionality exists though because things like BIRD use it 03:44:18 That's beyond my ken. My window into available APIs is constrained by (what I understand and remember of) the docs and manual page reviews I see pass. 03:49:32 ah, seems like you can use NETLINK_ADD_MEMBERSHIP with the various RTNL_GRP_* constants for this 03:50:45 what's this doing here /usr/include/netlink/route/common.h:RTNLGRP_DECnet_IFADDR, 03:50:53 did freebsd *ever* support decnet? 03:51:04 i know we had XNS at one point... 04:05:59 lw: wow just wow with this checkout and branch 04:08:18 screw up something, just go back to the main branch.. get rid of branch that is bad.. make a new one.. start again.. what has taken me so long to find just beauty 04:09:28 CVS? Subversion? 04:10:49 parv: i believe we're talking about git 04:11:07 voy4g3r2: wait until you find out about interactive rebase. messed up a commit? just make a new commit, then squash it into the commit you want to fix 04:11:56 lw: I was replying to rhetorical question of "what has taken me so long to find just beauty" 04:13:44 voy4g3r2: git's philosophy is very much about mutable history, so you can commit stuff, then edit your commits, or rearrange them, or whatever, so the final set of commits you submit to be merged is exactly what you want 04:20:58 lw: my horror started with cvs and that hell.. then i got "smart" and wrote our requirements and other "stuff" and gave it to someon with more patience than me 04:21:24 yeah, CVS was... fine for its fine. but i'd never go back to that from git 04:21:24 there was some microsoft product i use to use in like 2005ish time frame.. which just sealed the hell of source code repositories 04:21:48 Microsoft Team Foundation Server? 04:21:56 https://en.wikipedia.org/wiki/Microsoft_Visual_SourceSafe 04:21:57 Title: Microsoft Visual SourceSafe - Wikipedia 04:21:57 this! 04:22:01 horrible just horrible 04:22:29 ah yeah, i never used that but i've only ever heard bad things about it 04:22:33 that is when is tarted the journey.. before i made a major change, i would just "backup" the tree.. to another directory and pray i did not break it too much 04:22:51 freebsd used perforce for a while as a replacement for git... i think a lot of video game developers still use that because it handles binaries better than git 04:23:02 s/replacement for git/replacement for cvs/ 04:25:13 sourcesafe HATED excel documents, i remember that 04:25:29 yes, make fun of me now, i did a lot of vba coding and data analysis with access+excel 04:25:32 so route(8) called snl_read_message_dbg() which... doesn't exist? what am i missing here 04:25:50 voy4g3r2: when i was in high school i wrote a nethack-like RPG in Excelt VBScript :-d 04:26:59 oh, it's an inline function in netlink_snl.h 04:27:48 interesting.. a lot of this manual page stuff references.. mac os x uses blah.. i found something that is the other way around xlocale.. appeared in Drawin 8 and was incorporated into freebsd 9.1 04:27:53 interesting.. 04:28:47 btowc_l has no man page but btowc does.. and the different is the data type it works with.. 04:29:11 put good ole #include 04:37:36 a category 4 man page referencing a category 8 man page.. 04:37:42 * V_PauAmma_V used Mercurial for a while. 04:38:26 tslog(4) -> boottrace(4) which is actually boottrace(8) 04:39:17 seems valid.. change going in 04:42:52 hrm.. dialog4ports(1) is only available through ports but a base package references it.. 04:45:11 whoo! i can execute 'ifconfig wg1 create; ifconfig wg1 1.1.1.1/32; ifconfig wg1 1.1.1.1/32 -alias; ifconfig wg1 destroy' and my program sees all of these events via netlink 04:45:24 this interface is actually quite easy to use, it's just really badly documented 04:46:13 wireguard? 04:46:38 isn't 1.1.1.1 cloudflare dns? 04:47:06 yes, but i only added it for 5 seconds to test 04:47:25 the important point is i can detect interfaces and addresses being added and removed 04:48:27 lw, patches/pull requests/suggestions for improvement of the manual page(s) welcome. 04:49:03 i don't even understand the api yet so i don't think i'm the one who should be writing the manpages :-d 04:49:13 still waiting for my sctp(4) manpage updates to be merged anyway... 04:49:50 You're the one having trouble using them. I can't think of anyone better suited. :-) 04:51:04 haha 04:52:00 maybe if i finish this app i'll consider it 04:52:11 Fair enough. 04:52:33 i appreciate the impetus behind "you should fix this thing you're complaining about" but i have like ten thousand projects on the go at once + my actual work i get paid for 04:52:42 i do try to submit PRs for things that can be fixed relatively quickly 04:53:24 Fair enough. *eyes his own to-do list and grimaces* 04:53:48 ... the reason i mention this stuff is because i try to fix things when other people mention this here. like i submitted my sctp(4) PR because someone here was (rightly) complaining that sctp(4) is missing a bunch of docs 04:53:55 so maybe someone will see my messages and do the same 04:55:05 i guess this can come across as complaining but the way i mean it is more like "hey, it would be cool if someone could fix this if they felt like this" 04:55:35 Ping me in a few days? I'll be happy to turn your pain points into better manual pages. 04:57:03 when i install freebsd zfs on root with bsdinstall, boot up disk select shows my 2 nvme drives but also a FreeBSD i can select. any 3 will boot freebsd. but doing an unattended bsdinstall only the 2 drives show in the boot device menu. where's the "FreeBSD" line? 04:58:23 alepzi: what does efibootmgr say? usually freebsd installs two copies of the boot loader, \EFI\BOOT\BOOTX64.EFI and another one called something like \EFI\FREEBSD\LOADER.EFI, possibly your firmware is picking up both 04:58:44 (i don't really understand why it does this) 04:59:45 sudo efibootmgr says boot to fw: false, bootcurrent 0002, bootorder 0002 0003 0001, boot002 uefi os, boot003 uefi os, boot001 windows boot mgr 04:59:52 alepzi: you can check the contents of the ESP to verify this, it's usually mounted on /boot/efi by default iirc 05:00:39 e.g. `find /boot/efi` ... if it has two copies of freebsd loader, delete one of them and reboot, and see if the mysterious third boot option goes away 05:01:01 although as to why unattended would work differently here, i have no idea 05:01:40 got /boot/efi/efi/freebsd/loader.efi and /boot/efi/efi/boot/bootx86.efi 05:01:58 bootx86.efi? are you on 32-bit x86? 05:02:22 no 05:02:25 amd 64 05:02:37 hmm 05:02:48 alepzi: please show the output of `file /boot/efi/efi/freebsd/loader.efi /boot/efi/efi/boot/bootx86.efi` 05:05:03 https://termbin.com/yg4i 05:05:32 you said you had bootx86.efi, but your paste shows bootx64.efi 05:06:21 (x86 != x64) 05:06:24 lol i'm sorry it's 64 05:06:27 ah ok 05:06:44 so it's normal i guess? 05:06:55 alepzi: delete /boot/efi/efi/freebsd/loader.efi and reboot. that will probably make the freebsd option disappear from the menu. or, if you prefer, leave /freebsd/loader.efi and delete /boot/bootx64.efi 05:07:28 it doesn't show up already. i was asking why it didn't 05:07:59 hm, you said "boot up disk select shows my 2 nvme drives but also a FreeBSD i can select" - i thought that meant it was showing a third option you didn't expect, which might be .../freebsd/loader.efi 05:08:20 ya when i... 05:08:42 when you...? 05:08:47 nvm 05:09:07 well in any case i suggest deleting loader.efi because there's no reason for this to exist 05:09:15 why is it there then? 05:09:22 who knows? 05:09:37 shouldn't the freebsd devs remove it? 05:09:50 probably. feel free to file a PR and/or ask the mailing list 05:10:03 i always delete loader.efi when i do a new install 05:10:49 i do a new install about once every 10 years though so it never bothered me enough to do something about it 05:11:13 i do a new install for every point release like 13.1 to 13.2 05:11:26 then just freebsd-update patch levels 05:11:37 well, file a PR, someone will probably look at it. i do think this behaviour is wrong 06:07:58 i'm so mad that we can't write K&R func definitions anymore 06:08:07 they're so much more readable than this ANSI crap 06:08:08 uh, no, removing loader.efi is a terrible idea in general 06:08:45 kevans: why? the EFI firmware will load \EFI\BOOT\BOOTX64.EFI. there is absolutely no reason for \EFI\FREEBSD\LOADER.EFI to exist, it's just a redundant copy of BOOTX64.EFI 06:08:55 we don't want to claim bootx64.efi 06:09:02 but you *do* claim that 06:09:09 we don't if it already exists 06:09:09 bsdinstall puts both files onto the ESP 06:09:32 and we want to prefer the vendored copy, that's the entire point of the efibootmgr entry 06:09:50 removing it isn't going to remove the boot entry, it's just going to break it for no apparent reason 06:10:56 ok, for the 0.01% of users who have multiple EFI loaders on their ESP, this might make a difference 06:11:15 for the vast majority of users, this just creates two copies of loader.efi for no apparent reason 06:11:37 ideally we move away from bootx64.efi in general, but there's a lot of crap firmware out there 06:12:06 i stand by my advice that most users should simply delete \EFI\FREEBSD\LOADER.EFI as it serves no purpose if the disk only has freebsd on it 06:12:29 ok, but that doesn't make it good advice 06:12:44 ok, but installing two identical files isn't good practice either. your move... 06:12:58 lol 06:13:13 fwiw, this confused me a lot when i came to replace the loader after zpool upgrade 06:13:30 i discovered there are two copies of the loader. so what do i do? replace them both? but why are there two copies? 06:15:00 ideally you follow the steps in the release notes for this exact scenario 06:15:17 it gives precise steps to follow to determine what's in use 06:17:14 the release notes just say to update the current EFI loader as described in efibootmgr -v, but this is wrong. this will teach the user to replace bootx64.efi (if that's what the firmware loader) but ignore loader.efi 06:17:40 which will create issues if, for example, the disk is moved to another system that loads \EFI\FREEBSD\LOADER.EFI before BOOTX64.EFI 06:18:35 having two copies of the loader where one might be out of date cannot possibly be the correct behaviour 06:18:39 why would your new system magically use the vendored path? swapping out freebsd installs under a different firmware is kind of weird 06:18:43 ideally we'd have a tool to deal with all of this 06:19:21 kevans: i don't know why it would "magically" do that, but as we just discovered in this channel, some firmwares will notice the FreeBSD loader and display it as an additional boot menu entry 06:19:36 they do not notice it, no, we explicitly add the entry at install 06:19:53 so imagine you switch from a system that doesn't do that, to one that does, and your \EFI\BOOT\BOOTX64.EFI is up to date, and your \EFI\FREEBSD\LOADER.EFI isn't 06:19:53 rEFInd might notice it, yes, but all firmware I'm aware of will not 06:20:05 now when you select 'freebsd' at the boot menu, the system won't boot 06:22:32 i don't really care to argue about this anymore, but installing two identical copies of a file, and requiring the sysadmin to update both copies, and then not telling them that they have to update both copies, is bad practice 06:33:43 how do you determine what event happened on an fd from kevent()? does the kernel set ev.filter? 06:38:17 yes, the kernel fills in the good bits to describe the event 09:14:44 Hi folks! I am confused by this filesystem behavior. I mount_nullfs one folder onto another, and I get different outputs from "ls" for the same folder when accessing it from the concrete and the nullfs-mounted entrypoints to it: https://dpaste.org/vCom8 09:14:45 Title: dpaste/vCom8 (Markdown) 09:15:24 oh rubber duck debugging :) 09:21:18 is it just me or is freebsd terminal a lot faster than linux? when i run commands, even from a remote ssh, the output is like really fast? 09:21:32 or is it zfs? 09:44:05 <_xor> heh 09:44:12 * _xor uses rEFInd 09:44:25 <_xor> I was somewhat surprised to see it pick up all loaders on my ESP. 10:03:26 jbo: how did mediaelch go? 10:15:02 ok, so i maintain a port. i want to submit a patch. how do i do that? i don't see anything in the porter's handbook about this 10:22:21 lw: been ages since I did that procedure. But in short, https://bugs.freebsd.org/bugzilla/enter_bug.cgi?product=Ports%20%26%20Packages&component=Individual%20Port%28s%29. Summary: ": Update to v1.2.3", Add some description, attach the patch/diff from your local ports-tree. 10:22:24 Title: Log in to FreeBSD Bugzilla 10:22:35 An old ports-update I did https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256595 10:24:16 that's basically what i did https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276347 but i wasn't sure if i should set maintainer-feedback or not... the wiki TriageTemplates is a bit vague on that 10:24:20 Title: 276347 – net-im/toot: mark as BROKEN since devel/py-urwid is broken 10:24:52 this was basically, bump the version number in the Makefile, 'make makesum' (?) to get the new packages ( port tracked github releases of the matterircd service ) 10:50:02 i'm going to regret this lexi⊙lo | + 1 Jan 15 freebsd-python+help⊙Fo ( 17) Welcome to freebsd-python⊙Fo 10:50:26 soon my entire life will consist of nothing but reading mailing lists 10:57:44 meena: how do i get this committed https://github.com/freebsd/freebsd-src/pull/1057 should i just add bsdimp as a reviewer? 10:57:45 Title: service(8): direct user to rc(8) for a list of valid commands by llfw · Pull Request #1057 · freebsd/freebsd-src · GitHub 10:59:09 lw: that's mostly documentation, so I would bug someone who's does docs. 10:59:36 meena: this sounds like good advice. please give me @usernames of people who does docs :-) 11:00:59 lw: I just posted it in #bsdocs (EFnet) and #documentation (discord) 11:01:35 meena: #bsdocs on efnet does not seem to exist? 11:02:55 ah #bsddocs 11:03:35 meena: how do i get a src commit bit? 11:03:46 lw: yeah, I wonder too 11:03:59 heh 11:04:24 i had a weird conversation with j.bo about this the other day 11:04:40 the answer seems to be "commit bits are magic and not understandable" 11:05:31 Yeah, and, honestly, I don't like it. 11:05:37 although j.bo claimed, from what i remember, there are ~4,000 src committers and ~192 ports committers 11:05:44 which, by itself, is kind of hilarious 11:06:13 it makes sense when you think about the structure of the Org, but, yeah 11:06:14 <_xor> I thought there was voting process after you've been a proven contributor for a while. 11:06:18 (this is not a criticism of j.bo, who i'm sure has nothing to do with who gets a commit bit) 11:06:33 I highly doubt that all 4000 of those are active… 11:07:32 _xor: who knows. Is it documented anywhere? If it isn't, everything we think we know is hearsay. 11:07:38 meena: i also find this unlikely 11:07:59 although, perhaps Netflix has 4,000 people working on freebsd. who knows 11:08:08 probably not though 11:08:33 netflix has at least two people working on FreeBSD. 11:09:28 passive-aggressive pr of the day https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276347 11:09:32 Title: 276347 – net-im/toot: mark as BROKEN since devel/py-urwid is broken 11:10:02 <_xor> https://docs.freebsd.org/en/articles/committers-guide/ 11:10:04 Title: Committer's Guide | FreeBSD Documentation Portal 11:11:13 _xor: that's not how to become a committer 11:11:15 <_xor> I think it's delegated by people in those specific areas, and those people are probably appointed/elected by the core members. I'm pretty sure I've seen the details documented somewhere. 11:12:14 i feel like my various manpage updates are trivial and should just be committed. it annoys me that they aren't 11:12:16 <_xor> https://wiki.freebsd.org/BecomingACommitter 11:12:17 Title: BecomingACommitter - FreeBSD Wiki 11:12:29 it's not like i'm comitting a replacement pmap or something 11:13:13 lw: re #freebsd-python: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122 11:13:18 Title: 273122 – lang/python311: backport netlink support 11:13:19 "As more and more companies leverage FreeBSD for projects" ah got it, i need to add Sponsored by: in my commits 11:13:21 lw: i documented a pmap! 11:13:27 <_xor> https://www.freebsd.org/internal/members/ 11:13:28 Title: FreeBSD Project Members | The FreeBSD Project 11:13:43 <_xor> Those two links should give a starting point answer. 11:13:48 wait there's a #freebsd-python? 11:14:09 yes 11:14:24 maybe I should subscribe to the ML… 11:14:38 meena: why did you link me PR #273122, idgi 11:14:43 273122 – lang/python311: backport netlink support https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122 11:15:08 i mean i'm doing netlink stuff, but in C, not python 11:15:31 lw: just, take a read across the PR when you have some time, and nerves to spare 11:15:52 is this going to make me angry 11:16:16 probably 11:17:24 Hello. I can't access my micrphone in ungoogled-chromium 11:17:33 Could anyone kindly help with that? 11:17:40 microphone* 11:18:02 Installed devices: 11:18:02 pcm0: (play/rec) default 11:18:02 pcm1: (rec) 11:18:04 meena: i can't comment on this because the other person is on this channel, i guess 11:18:47 which one is active? 11:18:55 this one is definitely not working 11:19:01 at least in ungoogled-chromium 11:31:23 how do i switch microphone in freebsd? 11:33:42 i have only one rec devices 11:34:59 i switched recording device to "dsp0" in audacity. i also tuned fossmixer a bit, though not sure if it was needed. 11:35:16 in me@x200:~ % sudo mixer =rec 11:35:17 mixer: no recording device specified 11:37:35 V-T60: i havent used pavucontrol but maybe it can help you https://vermaden.wordpress.com/2024/01/13/freebsd-desktop-part-29-configuration-audio-improvements/ 11:37:36 Title: FreeBSD Desktop – Part 29 – Configuration – Audio Improvements | 𝚟𝚎𝚛𝚖𝚊𝚍𝚎𝚗 11:45:40 taking someone's advice to nag people about stuff https://lists.freebsd.org/archives/freebsd-python/2024-January/005480.html 11:45:41 Title: Re: devel/py-urwid and devel/py-setuptools_scm (PR# 274411) 11:45:56 but the chance this will actually fix the problem is like, zero, right 11:49:45 i don't really understand how a port can be broken for months and literally no one cares enough to do anything to fix it 11:49:51 why even have ports then 11:50:11 i don't understand how that might help 11:52:19 % pactl list sinks | grep 'Name: ' 11:52:19 W: [(null)] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support. Name: oss_output.dsp0 11:58:54 so i'm trying gpu passthru to win on bhyve but not having any luck. gfx card is detected in guest, but can't start 12:12:54 crest: https://reviews.freebsd.org/D41318 would be a nice thing to have IMO 12:12:56 Title: ⚙ D41318 Add the "missing" WireGuard rc.d script 12:13:13 maybe you can move it along a bit at some point 12:14:05 Bheam: there's a bhyve specific channel for this, you should post your bhyve command invocation there, and a bit more info (what h/w device, what guest OS, how its detected etc) 12:46:54 dch: the easiest way to move it along would be to have more reviews / tests / patches to it 12:48:30 more reviews but only magical know about phab 12:48:45 so you have to find magical people who like your commit 12:51:30 looks like this diff will never be committed because of bikeshedding, sorry, bye 13:04:54 Smartctl open device: /dev/nda0 failed: INQUIRY failed , how to get the total writen bytes of device /dev/nda0 ? 13:05:19 smartctl /dev/nda0 13:16:56 hi all 13:33:30 occ: do you have any '/dev/nvme*' devices? 13:52:47 norrland: yes,there is one 13:53:26 try querying the '/dev/nvme0' device instead. 13:53:31 use /dev/nvme ? 13:54:12 https://dpaste.org/PHhtb 13:54:13 Title: dpaste/PHhtb (Bash) 13:55:32 yes , smartctl -a /dev/nvme0 gives information. 13:57:40 but smartctl -a /dev/nvd0 gives "Smartctl open device: /dev/nvd0 failed: INQUIRY failed" 14:07:24 Yeah, could be that it's not providing that interface on non '/dev/nvme*' paths. 14:52:48 smartctl -d nvme -a /dev/nvme0 15:24:17 arg, i really didn't want to recompile llvm and rust in a manually installed port 15:29:25 Has something changed with poudriere, "Inspecting ports tree for modifications to git checkout..." now takes ~1h for some reason. 15:31:02 poudriere-3.4.0 16:54:47 openzfs rpm for EPEL9 (I'd suspect all supported distro binary packages) has arcstat and arc_summary. I see them in the contrib src repo. Does FreeBSD not include them? locate can't seem to find anything if they were not in a binish dir. 16:55:46 I'd guess maybe the kmod port might include them? 16:57:31 oh it's all python. So I guess that would explain it... disabled by default in the port too. 17:03:56 Quarterly patches successfully installed (to the best of my knowledge). 17:20:19 lw: meena: the number of active src committers is exactly names still listed in https://cgit.freebsd.org/src/tree/access?h=internal/admin, which is... under 200 17:20:53 ports number is pretty close, and they have a tighter reaper policy: https://cgit.freebsd.org/ports/tree/access?h=internal/admin 17:20:54 Title: access - ports - FreeBSD ports tree 17:22:12 (doc and src requires one commit per 18 months to avoid reaping, ports requires one commit per 12 months) 18:14:12 hello! where can I see the package description of dmd? 18:17:14 ah, apologies, I think the question is for OpenBSD, not FreeBSD (doesn't seem to have a dmd package: https://www.freshports.org/search.php?query=dmd&search=go&num=10&stype=name&method=match&deleted=excludedeleted&start=1&casesensitivity=caseinsensitive) 18:30:56 kevans: i had to hand in my ASF membership formally, i wonder if i can still commit, if i can remember my password 18:36:05 what desktop files are neeeded to make the gdm greeter work? By default as on `pkg install gdm` there are none in the configdir 19:07:43 why there is 4.7G used and 7.7G free on a 14G volume? 19:14:25 dlfke: compression? 19:14:29 i am trying to start greeter on freebsd whose pkg manager puts no files at all in the gdm config directory, consequently greeter GUI does not start when i boot but GDM is running 19:14:53 what files are neeeded to make the gdm greeter work? By default as on `pkg install gdm` there are none in the configdir 19:14:55 no compression. it's 1.5 GB missing 19:15:26 Oh, right. Wrong way. dlfke: Snapshots maybe, then. 19:42:11 can I remove /usr/freebsd-dist? 20:23:34 using freebsd as a desktop system is not easy due to a crazy amount of junk that is installed by the package system 20:41:04 https://hostit.tfnux.org/obj/6snv65lewvypakujt6ytaeys72irezhm/NETWORKING.png 20:41:17 hu hum... I see now... 20:43:46 That looks fun, what are those relations exacly? 20:47:15 the dependencies between /etc/rc.d/* scripts, as they are parsed by rcorder(8) 21:11:02 that one looks much better: https://hostit.tfnux.org/obj/k2hkfkyta7snyrf7vsuxwmd66plz57dd/twopi.png 21:38:47 dlfke, space reserved for root? 21:40:14 Look at tunefs(8). 23:18:53 tsoome: this looks good to my eye, but you might wanna take a look, too https://github.com/freebsd/freebsd-src/pull/1063 23:18:54 Title: vt.4: explain console fonts by concussious · Pull Request #1063 · freebsd/freebsd-src · GitHub 23:21:29 seems good, but its 01:21am here, so I'm rather sleepy.... :D 23:24:10 back to bed, mister! 23:28:24 tsoome: it's 23:28 here, and I just put my daughter to sleep