01:18:58 yes! everything about this page inspires absolute confidence! https://www.freedesktop.org/wiki/Software/xlibs/ 01:18:59 Title: xlibs 03:16:47 dammit, I hate it when I forget to mount large data drives with nosuid 03:17:10 (or noexec) 03:17:35 I wish there were a persistent attribute for that 03:29:31 is it possible to setup the following: partition a drive in 2: 1 part for OS , second part as special device 03:29:45 oh, in zfs, and it has to be mirrored 03:30:11 special device? 03:30:53 yeah, you can use it to store the metadata 03:31:14 aka: data on spinning hdd, metadata on ssd. gives huge speed boost 03:31:49 Do not see the point of partitioning the same disk to separately store the metadata 03:32:27 there is a point. the os and metadata are on ssd, data is on hdds 03:32:47 *metadata for the hdd pool 03:33:43 So the partitions are on a SSD with OS & metadata for the data on a separate disk? 03:34:19 last1, I see you had already mentioned that. Ok then 03:40:14 how many hdds are involved? 03:40:25 RhodiumToad: I just alias mnt to mount -o noatime,nosuid 03:40:59 44 03:41:33 wow 03:42:22 the only part I'm not sure about is how mirroring of the special device would be handled 03:42:44 my question was more like: can I partition ada0 in 250GB for the OS, rest for metadata and then install FreeBSD on ada0p1 with ZFS 03:43:11 I would do the same with ada1 so the OS would be zfs mirrored on ada0p1 / ada1p1 , and the special vdev would also be a mirror on ada0p2/ada1p2 03:43:12 in terms of partitioning, you can do almost anything, because zfs is basically ignorant of the underlying geom layout, it just consumes whatever providers you give it 03:43:41 my problem is that in the installer I can't choose ada0p1 , just ada0 in the Auto-ZFS installer 03:43:52 you have two separate ssds to use for the OS/special bits? 03:44:02 no, just one 03:44:15 anything non-standard and you have to do manual partitioning, obviously 03:44:19 last1, you would need to do that manually 03:44:53 ugh, a manual zfs zroot install, I wanted to avoid that :) 03:45:34 last1: I think you'd have to do manual partitioning from the shell. which is a PITA with ZFS if you want the default dataset layout that the installer creates (and you should because they're good) because you have to create them by hand. 03:45:54 you should be able to do the partitioning in the installer 03:45:57 yeah, that's what I had started on, I created the partitions with gpart 03:46:07 but then I wanted to jump back in the installer 03:46:10 I would install just the OS partition manually, and set the rest up later 03:46:12 and have it use ada0p1 03:46:46 but then I haven't used the installer in anger for a while 03:47:09 last1, You could parition via the installer. Then choose the partition to install ZFS (there will be no separate datasets, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262461 ) Later make the mirror after the installtion. 03:47:12 Title: 262461 – bsdinstall: After manual partitioning the disk, installer installs "ZFS on root" directly on the pool not under separate ZFS datasets 03:47:54 ugly business, I might just get 2 dedicated mirrored OS drives 03:48:15 but I wanted to save on 2 SSD slots and do it all on those 2 drives 03:48:43 what's ugly about it? 03:50:24 ok, let me try this one more time. 03:50:48 * parv had installed ZFS on a single partition, on 2-SSD mirror, but not on a mirrior on 2 partitions 03:51:19 so in the Installer, I go manual route, create just one 250Gb partition as freebsd-zfs and try to install on that 03:51:27 and after, I add the second drive as mirror 03:54:57 yup 03:56:46 https://imgur.com/a/9rbKLi1 03:56:47 Title: Imgur: The magic of the Internet 03:56:56 if I try to set mountpoint as / , the installer crashes and restarts 03:57:09 parv: how did you manage to do auto-zfs on just part of the disk ? 03:59:08 unfortunately I don't have a VM spare to test it in right now 04:11:10 any way to know when this page dates from and if it's still to be used ? https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot 04:11:12 Title: RootOnZFS/GPTZFSBoot - FreeBSD Wiki 04:11:29 ah, it says at the bottom: last edited 2022-06-12 04:12:45 so fairly recent, but this line in the beginning: newfs_msdos -F 32 -c 1 /dev/ada0p1 gives me an error: 1542 clusters too few clusters for FAT32, need 65525 04:17:17 is that for an ESP? 04:17:57 apparently it's for the UEFI boot partition 04:18:00 I'm doing it by hand 04:18:19 yes, that's what an ESP is 04:20:40 1542 clusters of 1 sector looks very small 04:22:32 eh, I'll just do legacy boot instead 04:22:34 are you trying to make it just big enough for loader.efi? that's a very bad move 04:22:50 well, I was just following that document: https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot 04:22:51 except on install media, you should make it at least 64 megs 04:22:51 Title: RootOnZFS/GPTZFSBoot - FreeBSD Wiki 04:23:08 it's apparently wrong 04:25:35 you can make the partition larger, or use fat16, or both 04:27:34 try -c 8. I *think* it's better to stick to FAT32 for the ESP... 04:28:03 -c 8 will make it worse 04:29:02 that'll push the minimum size up to ~256MB 04:29:53 RhodiumToad: maybe I remember wrong but I think it's what I did not long ago. it gave me 4K clusters which seems fine. the error message is very confusing. 04:30:20 I've never had any issues with fat16 for ESP 04:30:40 oh alright 04:31:01 4k clusters is fine in itself, it's just that newfs_msdos wants the device to be large enough for 65525 clusters to use fat32 04:31:07 why is iocage making me update every single file in /etc/ by hand for every single jail just to upgrade from 13.1 to 13.2? 04:31:18 so the larger the clusters, the larger the minimum device size 04:31:20 i didn't change weird things like ssh moduli 04:31:29 surely something has gone wrong? 04:31:38 The following file could not be merged automatically: /etc/mtree/BSD.debug.dist 04:31:38 Press Enter to edit this file in /usr/bin/vi and resolve the conflicts 04:31:38 manually... 04:32:42 huh, that shouldn't need a manual update, it should just be replacing it 04:33:03 yeah 04:33:07 but I have no idea why it would do that 04:33:11 but there's no option to replace it 04:33:33 what are the conflicts? 04:34:25 almost everything in /etc/ 04:34:30 from where debug files 04:34:32 weird 04:34:38 to sshd_moduli 04:34:45 no, I mean if you edit the file, does it show any conflicts and if so, what 04:34:50 oh 04:34:51 yes 04:35:03 basiclly all the stuff you'd normally expect from the new release 04:35:08 version identifier changes 04:35:15 small additions to hostapd's init script 04:35:31 most of the merges are things that should be totally doable automaticlly 04:35:39 like inserting lines where these was none before 04:35:51 is it invoking etcupdate to do the work, or using its own code? 04:36:28 i don't know i'm just running iocage upgrade -r 13.2-RELEASE ALL 04:36:32 IIRC etcupdate on recent enough 13-STABLE (& 14-CURRENT) had handlled those files 04:36:55 you could look at the process list and see if etcupdate is running 04:39:31 alright i'm restarting to upgrade on the jail to check if it's using etcupdate 04:39:37 but if it is what would that change? 04:40:02 just whether it's an iocage bug or an etcupdate bug 04:41:07 one second 04:41:39 /bin/sh /tmp/tmp_onnvkjc -b /zroot/iocage/jails/mumble/root -d /zroot/iocage/jails/mumble/root/var/db/freebsd-update/ -f /zroot/iocage/jails/mumble/root/etc/fr 04:41:42 sweet, I've done it: https://imgur.com/a/LNBVH4v 04:41:44 Title: Imgur: The magic of the Internet 04:41:54 eebsd-update.conf --not-running-from-cron --currently-running 13.1-RELEASE -r 13.2-RELEASE upgrade 04:42:10 i don't know 04:42:28 i can't find etcupdate 04:42:30 so now zfs is on ada0p3, and I would just add a mirror to ada1p3 to have it redundant ? don't I also need to mirror ada0p1 and ada0p2 ? 04:42:36 The following file could not be merged automatically: /etc/mtree/BSD.debug.dist 04:42:36 Press Enter to edit this file in /usr/bin/vi and resolve the conflicts 04:42:36 manually... 04:43:31 last1: there's no sane way to mirror the ESP, but you can make a copy of it on the other drive as a backup (nothing on it should change in normal use) 04:43:47 what's ada0p2 ? swap? 04:44:18 RhodiumToad, is there some other way to tell? 04:44:34 if you want to avoid crashing if ada0 dies, you can use gmirror to mirror the swap partition 04:44:37 yes, swap, that I can ignore I guess 04:45:00 oh, good idea 04:45:09 and set the swap to the mirror 04:46:00 you'd probably want to set it to 'prefer' and give the ssd the higher priority 04:49:00 well shit, i'm just going to roll it back 04:49:13 thank goodness for zfs snapshots <3 04:54:08 I left some unpartitioned space on a nvme to install Windows later on. I assume that this just works (and that it'll use the existing ESP without issue) but if this wrecks my freebsd install I'm going to be a little bit annoyed... 04:56:36 it may overwrite the bootx64.efi, you may want to keep an extra copy handy 04:57:16 if you have multiple OSes you probably want some form of EFI boot manager anyway 04:57:45 RhodiumToad: ah right. well if it's only that it's something that can be fixed from a USB key. 04:58:37 RhodiumToad: can setting up some EFI "boot menu labels" (or however that's called) be enough to dual boot them? 05:00:38 heh I haven't bothered trying to dual boot in forever. small SSDs are so cheap. but with nvme it makes sense to try to share them again. 05:02:22 I've not tried dual booting from EFI 05:02:36 but I know in theory how it works 05:03:35 alright. well, I'm just gonna hope that messing with efibootmgr(8) can make it just work. 05:03:50 i.e. in theory it's just a matter of having all the various OS boot loaders on the ESP and either telling the firmware which one to boot via an EFI environment var, or having a menu program on the ESP to handle that part 05:04:47 efibootmgr works by setting those EFI env vars 05:05:22 if you want a boot menu, there's things like rEFInd 05:06:31 RhodiumToad: that's an intermediate boot loader right? you boot into it and then it chain loads some other ESP boot program? 05:06:40 yup 05:07:27 I'm hoping that I won't need anything like that. If I have to press the "boot menu" key while booting to pick from the EFI's built-in boot meny that's fine. if that works... 05:31:47 hm, my buildworld looks nearly done 05:31:56 after 130 minutes 05:40:41 hm, not as nearly done as I thought 07:14:24 hi. is there a package that reports pcie 10gb nic temperatures? 07:19:48 it looks like at least some high-speed NIC drivers report chip temperatures via sysctl? 07:24:29 <_xor> I'd look at IPMI/SMBus as well. 07:25:25 ok, I'm checking things right now 07:30:38 can pcie cards be on smbus? 07:36:14 tried sysctl dev | grep ix | grep -i temp but nothing relating to the temperature 07:39:27 ixgbe driver? 07:39:51 yes, i think so.. Intel(R) X520 92599ES 07:43:36 looks like ixgbe adds sysctls for temp only on certain device IDs, specifically IXGBE_DEV_ID_X550EM_X_10G_T 07:46:37 sorry, i mis-typed. its a 82599es 07:52:17 <_xor> RhodiumToad: Not sure, I thought I remember seeing one of my servers show me NIC info via the embedded management interface, and I thought it was getting it via SMBus, but not sure. Couldn't hurt to take a quick look though, should be easy to eliminate if it doesn't. 07:54:01 FETCH_DEPENDS+= ${GO_CMD}:${GO_PORT} \ 07:54:05 fucking hell. 07:54:59 how am I supposed to fetch all my distfiles in advance if any go port needs to build go just to fetch itself? 08:29:08 sfox: iocage hasn't seen updates in quite some time 08:29:24 why is that? 08:29:30 it's not abandoned is it? 08:29:48 hopefully this is just a matter of rolling back and waiting for a proper fix upstream? 08:47:43 sfox: https://github.com/iocage/iocage/issues/1289 08:47:45 Title: Last Accepted Pull Reqest was Oct 2021 · Issue #1289 · iocage/iocage · GitHub 08:47:45 1289 – errno breaks in thread-safe c++ compiles https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=1289 08:52:26 ugh 08:52:31 i just migrated from ezjail too 08:54:36 am I really supposed to just go use linux? 08:54:58 i switched to FreeBSD cause I couldn't stand Linuxisms any longer 08:55:18 now this new update even implements /etc/machine-id 09:09:39 sfox: Linux is now the new standard without a standards body 09:11:01 if we don't follow some of directions or sets you won't be able to run any applications, because people who pretend they program for the POSIX platform don't test on anything than their macOS they developed on, and the Linux ci 09:11:28 anyway. ezjail hasn't seen updates even longer than iocage. 09:12:15 if you want a thing that's actively developed, please do the research or ask for recommendations 09:12:25 So OpenBSD (sans ZFS)? 09:19:09 https://wiki.freebsd.org/Containers and there's also https://github.com/illuria/jailer 09:19:10 Title: Containers - FreeBSD Wiki 09:19:41 parv: oh, yeah, OpenBSD will definitely stay what it is. I think 09:22:37 cue OpenBSD integrating a kernel bus 09:22:59 tho, honestly, i'd love to see that, because i think they'd do a fantastic job 09:28:10 btw, jailer might be a bit volatile https://weblog.antranigv.am/tags/jailer/ but the work coming out of jailer (lol) and landing in base is there to stay 09:28:12 Title: Jailer | Freedom Be With All 09:37:30 it's almost orwell 09:45:17 sfox: anyway, to summarise: the real reason to join a BSD community isn't the technology, so much, although we have some cool tech, it's the process behind how that tech comes together, and the kind of communities that make that possible 09:45:53 I like the tech. 09:49:29 the fact that i can get a one line patch into the base system, without having twenty decades of kernel hacker credentials tells you something about our process: https://github.com/freebsd/freebsd-src/pulls?q=is%3Apr+author%3Aigalic+is%3Aclosed 09:49:30 Title: Pull requests · freebsd/freebsd-src · GitHub 09:50:03 GitHub doesn't tell you that only one of those wasn't merged 10:38:29 I love that morse(6) is a game (section six) but it also implements an ITU standard: https://freshbsd.org/freebsd/src/commit/82a036d86acaac75b1ff6d4f8b767bbb117694f1 10:38:30 Title: FreeBSD / src / 82a036d86acaac75b1ff6d4f8b767bbb117694f1 - FreshBSD 10:38:54 Nice. 10:39:13 Freaky: what'd you think of displaying the subject line in the title when linking commits? 10:40:08 the commit hash isn't as useful to the casual observer as the commit subject line, imo 10:55:01 seems like games is also meant for stuff that was made for fun and not for some serious need, like caesar too, totaly usable and implements frequency based guessing of the right rotation, ah wait that has a serious need, how else would you solve #ircpuzzles if caesar wasn't in base? 12:08:30 no rc.d script for if_wg in 13.2? 12:08:49 does this mean that wireguard-tools should still be used? 12:18:48 Hello again. Looks like there was an power outage during package installation. Now pkg complains about malformed local package database image. Is there any way to recover it without re-bootstraping pkg? 12:22:26 <_xor> Do you have a list of packages that were installed? (I do wonder how it got corrupted though, is there a *.wal file in /var/db/pkg somewhere?) 12:22:54 <_xor> ...also, anyone know if there's a setting in Firefox to get it to release /dev/dsp when audio isn't actively playing? 12:23:49 mage: I think it's in ports 12:24:13 * _xor had USB audio stop working randomly several times in the past few days until he finally noticed that the end of of his USB-C cable was frayed and was causing power issues 12:25:02 <_xor> Replaced the cable and hasn't happened since, but would still like to avoid the sound device being locked and unable to release/re-create without reboot. 12:25:34 <_xor> (...or at least, that was the only way I found to fix it, though I found a couple of blog posts that seemed to confirm that's the case) 12:26:39 _xor: Unfortunately, neither. There is only some shell history, but would it be really enough? 12:27:37 <_xor> No idea. You mainly need to know which packages you explicitly installed were, the rest of it can be installed as automatic dependencies. 12:28:52 <_xor> I know it's "normal", but seeing a bunch of "pid 12345 (conftest), jid 321, uid 0: exited on signal 11 (core dumped)" messages in my logs still feels...odd. 15:13:26 meena: that's a surprisingly invasive change 15:17:36 Freaky: hmmmm… I figured it might be 15:24:02 https://freshbsd.org/freebsd/ports/commit/23612e19c7ea25fc1a94c70aa3da2905df7da6af 15:24:03 Title: FreeBSD / ports / 23612e19c7ea25fc1a94c70aa3da2905df7da6af / www/onlyoffice-documentserver: Fix path in documentserver-jwt-status.sh - FreshBSD 15:24:36 maybe not *that* invasive :) 15:29:51 shortened the ids too 15:34:19 https://freshbsd.org/freebsd/src/commit/77f0e198d9134b6ca2650d3a84d7db2d786ec0c0 15:34:20 Title: FreeBSD / src / 77f0e19 / procctl: add state flags to PROC_REAP_GETPIDS reports - FreshBSD 15:34:28 Nice! 15:35:03 now my only complaint is that some diffs are too hard to read on mobile 15:37:49 the line numbers take up way to much space https://im.eena.me/uploads/8b910d392321b60c/Screenshot_2023-04-16-16-37-13-23.jpg 15:38:21 turn phone landscape? 15:49:59 _xor: I reported the reason for that conftest segfault years ago, it could have been fixed but has not been 15:55:10 Freaky: why does it show older commits to main as being on e.g. releng/13.0, related to git switch? 15:55:31 <_xor> RhodiumToad: What's the actual fix for it? 15:55:39 <_xor> (brb, picking up lunch) 15:55:48 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236165 15:55:50 Title: 236165 – crash in malloc with ld.lld and -Wl,--export-dynamic -static 15:56:27 yuripv: branch names in git are a clusterfuck 15:57:20 that answer works :D 15:57:20 with svn you just extract from the filenames in the commit, with git you.. shrug 15:58:08 branches are just names for tips on the commit graph 15:59:20 "older commits to main"? you mean ones from before releng/13.0 was branched? 15:59:49 I use git name-rev and it tries to pick one vaguely sensible branch name for the given commit, which is far less than ideal 16:01:31 git just has no concept of what branch a commit was made to, you can only vaguely infer it from walking the commit history from the tip of a branch and going back through history until it seems to merge with main or another branch 16:05:36 RhodiumToad, _xor: https://reviews.llvm.org/D42748 16:05:37 Title: ⚙ D42748 [ELF] Don't create a .dynamic section when linking with -Bstatic 16:11:28 hey there; for an 8 x 22tb disks NAS storing movies, would I be better off doing a zpool of 2 x RAIDz1 VDEVs (containing 4 disks each) or 1 x RAIDz2 VDEV (8 disks)? 16:12:24 I've consistently read that the more VDEVs the better performance wise, but wouldn't using 2 RAIDz1 VDEVs reduce redundancy by only allow a single drive failure per VDEV? 16:12:55 also, I'll be using 10gb NICs soon enough, hence my worrying about having better IOPS 16:16:23 * _xor clicks link while opening his lunch from Chipotle(TM) 16:16:34 <_xor> I really should try Nandos sometime. I've heard good things. 16:21:16 if you have Moe's Southwest Grill, it's like Chipotle but a slightly better. I like both, _xor 16:22:00 Yeah. Fast food chains are, oddly enough, one of the things I miss most since moving to a small village in South America where those options don't exist. 16:23:09 meena: tried removing line numbers for small displays but Chrome told me to die in a ditch 16:23:38 Freaky: that's okay, i don't use chrome 16:29:10 <_xor> omg, it's a stupid global nodejs dependency that's causing this 16:29:48 * _xor noticed his system getting sluggish and CPU utilization rising...then noticed a ton of bash processes being spawned 16:30:09 <_xor> Looked like some stupid race condition or possibly intentional DDoS (sadly, not uncommon with nodejs ecosystem). 16:34:41 Freaky: a quick look at GitHub, gitlab, and codeberg tells me they all do that. it's just your site that i mostly look at: https://codeberg.org/FreeBSD/freebsd-src/commit/b1a00c2b136841b84b8ffdc703a1afeee5d0e268 / https://github.com/freebsd/freebsd-src/commit/b1a00c2b13 / 16:34:41 https://gitlab.com/FreeBSD/freebsd-src/-/commit/b1a00c2b136841b84b8ffdc703a1afeee5d0e268 16:34:43 Title: Quiet compiler warnings for fget_noref and fdget_noref · b1a00c2b13 - freebsd-src - Codeberg.org 16:34:44 Title: Quiet compiler warnings for fget_noref and fdget_noref (b1a00c2b) · Commits · FreeBSD / FreeBSD src · GitLab 16:37:06 meena: I'll sort something out, one way or another 16:45:44 and then the others will follow suit I'm sure ;) 16:55:58 veg, Both of your proposals allow for two failing devices but the first one only if the second failure is from the other VDEV while the second allows any two. 16:56:25 Both are good configurations. It depends upon your own judgement as to which is better for you. 16:56:55 If you expect to be able to react to the first device fail by replacing the redundancy of the failure before a second one in the set of four fails then it is fine. 16:57:31 That would be typical in a corporate enterprise datacenter situation with spares handy and someone on call to make the replacement every day. 16:58:31 The raidz2 configuration allows any two devices to fail. Allows a little more slack in your schedule if one fails and you don't get to it before a second one fails then things are still okay if you then replace the failed devices and restore redundancy. 16:58:59 At the cost of somewhat less performance than the striped VDEV configuration of the first proposal. 16:59:32 In my home setup I decided I might be away on vacation for a couple of weeks and I did not need that performance. YMMV. 17:00:22 Also remember that if one has an identical collection of storage devices and they are all running identical hours in identical environments then systematic type failures are more likely to cluster together. 17:01:31 Twice in my career I have had two sibling spinning disks die within a few days of each other. One I caught okay. 17:01:36 The other failed before the client decided to replace the redundancy and I had to do a full restore from backup. 17:16:44 rwp: oooooooooof 17:20:18 oooooooooof? 17:23:46 that just sounds like no fun. 17:26:40 For the one that I caught I copied the data to a different NAS and switched over to it. But left the original running since it was remote. 17:26:45 And then two days later the second drive in the mirror failed causing the loss of the entire array. But the data had already been moved. So all okay. 17:27:36 For the one that needed full recovery from backup the entire tale was just snafu because that client needed to be convinced to do something about it causing time to drag on. Could have saved it. But not after the second drive failed too. 17:28:13 Experiences like those are why I am a huge fan of raidz2/raid6 which gives a little more safety. Sometimes just enough more. :-) 17:31:44 I wonder how drives from different vendors that have same specs… fail 17:32:34 .epi 17:32:40 Failures modes from different vendors should be completely decoupled. Which is what you want. 17:34:48 For my own stuff I often split lots of drives. I mean I have two drives that are identical and been running mirrored for a year. 17:34:52 I buy two more identical drives. I then split those lots up so that each system has one new drive and one experienced drive. 17:34:57 Hoping that being a year apart that any failures will not be coupled failures. 17:38:28 Corporations though often have SLAs with service vendors and those vendors will often require arrays to have identical drives and identical firmware. Because they don't want the client to be complaining about weird issues that might be due to drive firmware or behavior. 17:38:35 But they might have a 4-hour service agreement to replace any failures very quickly. Which makes up for the potential problems. 17:47:32 Since veg mentioned 22TB disks I will mention in passing that I sure hope they are not SMR Shingled Magnetic Recording. Because those are completely unsuitable for purpose in a RAID. 17:48:54 If I were _given_ that much SMR storage I would probably still use the drives. But not in any raid. I would use them only as singles. 18:01:59 * RhodiumToad grumbles about make's spurious "read-only file system" warning 18:21:22 hello I was trying to make the sound work in a user account and then I followed some instructions from the BSD chapter on multimedia now for some reason the sound seems like it works on the user as well as root 18:21:33 but xorg stopped working in the user account but it still works in root 18:21:42 any ideas what to do to make it work? 18:22:29 Xwrapper. 18:22:42 https://termbin.com/mpqo 18:23:42 not sure why it stopped working but that was working before 18:23:55 Ok no Xwrapper then 18:24:38 sixpiece: what error do you get from X when starting as non-root 18:25:23 not* 18:26:08 I just get the 3 screens 18:28:25 it's like 3 terminal screens that are small 18:28:32 I've had it on these issues 18:28:35 how are you starting X? 18:28:38 startx 18:28:51 it's supposed to automatically start however and it works as root 18:29:17 and what is in your .xinitrc, and did you change that file recently? 18:29:32 you have it enabled in /etc/ttys? or where? 18:29:36 no but I might have made a command that screwed it up 18:30:01 https://docs.freebsd.org/en/books/handbook/multimedia/ 18:30:02 Title: Chapter 8. Multimedia | FreeBSD Documentation Portal 18:30:05 I did commands in there 18:30:20 sysctl hw.snd.default_unit=4 an extra one or two of these 18:32:03 # kldload snd_driver 18:32:03 -=- and this command as well that could have interfered the other thing that I did was I added the user to several groups not only pulse but pulse-access and _sndio I then pw groupmod pulse-access -d kiwichap to try and repair the situation 18:32:26 ah, did you take the user _out_ of the video group by mistake, perhaps? 18:33:09 try the 'id' command to see 18:33:28 I added the user to video group but it shouldn't matter when it goes to sddm since it could be any user of the system I think 18:33:45 I mean they don't know specifically that I am that user until I login is what I mean to say 18:34:20 you're using sddb started from where? rc.conf, or ttys? 18:34:26 *sddm 18:34:33 rc.conf 18:34:51 and sddm starts ok and prompts for the user? 18:34:56 https://termbin.com/cihg for the id command 18:35:04 no it does not start ok 18:35:11 what happens? 18:35:29 good observation I will try 18:36:05 cannot mix incompatible Qt library (5.15.5) with this library (5.15.8) 18:36:26 i had the same issue recently 18:36:38 i did `pkg update -f; pkg upgrade -f` and it got resolved 18:37:15 somehow you have 2 qt libraries core versions or something 18:37:31 > if you want a thing that's actively developed, please do the research or ask for recommendations 18:37:31 yes, i'm looking for a reccomendation of iocage development 18:37:54 i mean yes i'm looking for a reccomendation for a replacement of iocage since it's no longer developed 18:39:13 right I installed chromium browser 18:39:52 rwp: thanks a lot for the thorough reply! My disks are 22tb WD Gold, AFAIK they do not use SMR technology 18:39:55 doing the upgrade now , although it doesn't explain why the root still works 18:40:33 * gzar shrugs 18:40:45 i had the same issue with screengrab 18:40:55 found the solution on the freebsd forums 18:41:20 after forcing and update and upgrade it worked for most people 18:41:55 its like your binary is compiled against an older version of QT then your current library 18:42:26 it says notice: this port is deprecated you may wish to reconsider installing it uses python 2.7 which is EOLed upstream 18:42:29 it must have gotten updated and left the other packages that still relied on the older one unupdated 18:42:52 you have some python2.7 installed, pkg upgrade -f upgrades all your packages 18:43:05 chromiumm is still stuck on python 2.7 18:44:07 ok sounds good 18:44:17 stupid chromium 18:44:21 thank you 18:44:27 no problem 18:44:43 or was when I last looked, anyway - not sure if it's fixed 18:47:12 hm, no, that should have been fixed apparently 18:47:29 so I could go up to 6 18:47:46 ? 18:48:39 qt6 18:49:07 * RhodiumToad doesn't know 18:51:48 does anyone know how to do the secure boot is it really not possible or very difficult? 18:52:08 it is not that bad 18:52:14 if your bios will let you enroll your own key 18:52:25 then it is just some commands to sign the loader.efi etc 18:52:41 helped a customer with in last month 18:52:52 it has a key already it's like a trio boot of windows, linux and freebsd 18:53:27 signing the freebsd loader with microsoft's key would require having microsoft's private key 18:53:37 I'm not an expert on this to say it has a key already 18:53:39 vs, you can add a 2nd trusted key, and sign the freebsd loader with that 18:53:58 correct it worked for ubuntu so it must be able to make a 3rd key 18:54:13 ubuntu has a shim loader signed with microsoft's key 18:54:23 so it doesn't require loading your own key 18:54:33 but yes, it is doable 18:54:38 ok 18:55:02 sounds very interesting 18:55:45 these instructions are rough, and a bit old, but, they talk about the process if you are interested: https://freebsdfoundation.org/freebsd-uefi-secure-boot/ 18:55:47 Title: FreeBSD UEFI Secure Boot | FreeBSD Foundation 19:01:18 thanks I believe I tried something like this and got stuck or something maybe that one is updated 19:01:49 I'm just upgrading the laptop to 13.2 19:24:23 Allan: one day, when PkgBase hits, we can just add WITH_BEARSSL as a standard, imagine that 19:25:08 when is "one day"? 19:26:00 yuripv: my reading is that it's planned to go beta in 14.0 19:26:41 yay 19:27:29 https://hackmd.io/JczFDHtiQYSeEyeK9182jw?view needs more work tho 19:27:30 Title: FreeBSD 14.0 Planning - HackMD 19:27:41 any way to query pkg info for only packages that are not dependencies (i.e ones that were installed with pkg install)? 19:27:55 yes 19:29:24 pkg alias --list has something, which i cannot remember 19:29:30 i got it i think 19:29:33 I think it's leaves? 19:30:15 i have no aliases 19:30:53 nvm i need to copy the sample pkg.conf 19:31:14 noauto 19:31:34 sweet, thanks! meena 19:34:03 btw i made a forum post about my uaudio problem 19:34:11 no one cared to comment yet 19:34:29 i'm about to stay up all night and dig into the kernel driver and start hacking it up 19:35:02 ah, to be young again… 19:35:10 i'm old 19:41:17 yes, but, is anyone actively leeching the marrow from your bones, every waking hour of the day, and sometimes at night, too? 19:41:59 yeah kinda 19:42:42 i don't know what kind of child eats bone marrow though 19:42:56 unless i'm missing the poetic reference 19:44:17 it just feels like it 19:44:27 it's poetic, alright. except, in utero: if a foetus doesn't get enough calcium, it does leech it from the mother's bones 19:45:33 congrats on the news 19:45:48 it gets worse 19:47:06 anyway, our kiddo is four, and, yes, i know 19:47:14 oh nevermind then 19:47:27 thought you had a marrow-eater in the oven 19:56:05 I've just updated the base for several jails. all went well except for one jail which is no longer able to update packages from a remote repository due to: 'Certificate verification failed'. All other jails are happily pulling from the same repo. I am not sure how to resolve this. I tried to workaround by bootstrapping from pkg-static but that didn't work either. 19:56:12 where does one usually go from here? 19:56:50 why is it failing, exactly? 19:57:15 not sure. it seems that the jail is lacking ca_root_certs tho. 19:57:25 can't install it easily tho as that would happen via pkg :p 19:57:40 huh? 19:57:50 is this FreeBSD's repos, or your own? 19:58:16 my own. but shouldn't matter. all other hosts & jails are happily working with that repo. 19:58:39 yes, 19:59:09 it's just that FreeBSD's base system supplies the key for the FreeBSD repo 19:59:41 yeah I have my own cert installed. same as on all other hosts & jails 19:59:51 i would use a downloaded/ cached ca_root_certs from one of the other jails and manually install it into the jail, and try again 19:59:58 Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1 19:59:58 34378686464:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1921: 20:00:26 can curl/wget/fetch verify it? 20:01:05 sure, I just successfully fetched the HTML of the poudriere dashboard form that jail 20:01:25 actually, it's ca_root_nss and that is installed (brainfart with ca_root_certs) 20:05:34 wtf, I am getting the same error when doing a 'pkg install' on a .pkg 20:07:10 pkg-install -U did the trick. just updated pkg from 1.19.0 to 1.19.1 on the jail but still getting the same error :( 20:10:54 pkg add would skip some things that install does 20:11:14 but that doesn't explain why you're getting those errors 20:11:21 I've manually installed ca_root_nss from the jail's host in the jail and now things are back to working :s 20:11:48 weird 20:12:56 not sure what happened there 20:14:37 meena, also thanks for the pkg-add note 20:22:23 jbo: does the log tell you anything? 20:27:41