00:46:30 pikvm rox, happy owner of 1 06:28:36 hi all, how do i skip upgrade openssl from 1.1.1 to 3.0 06:28:36 ? 06:34:18 n30: did you figure out why you even have an openssl package installed? and from the pkg output you shared previously it seemed like you already have 3.0 installed; maybe pkg lock but no idea what other effects that will cause 06:34:44 na this is on a jail 06:40:37 then you could try pkg lock 06:43:52 * _xor really wants to get multi-machine parallel builds going for ports/poudriere 06:44:43 * _xor just changed DEFAULT_VERSIONS+=ssl=openssl111 to openssl and saw that it needs to rebuild 2100+ ports 06:46:20 pkg version|grep "<" say that perl5-5.34.1_3 needs to be upgraded but portmaster -aD say that nothing is to be upgraded 06:50:53 UPDATING has instructions for portmaster users to update perl, but you should have said that you build your packages yourself earlier, then I would have suggested that DEFAULT_VERSIONS+=ssl=openssl111 (ok, that also forces stuff that would use base openssl to use an openssl package 06:51:26 using poudriere makes managing that stuff a bit easier 06:51:51 n30, What OS version is running in jail? 06:51:54 i have upgraded perl 06:52:00 parv: freebsd 06:52:35 n30, I was asking for the version, not the name. Is it 13.2? 06:52:45 parv: ah then yes 06:52:54 n30, Thanks 06:57:29 but im srsly confused why pkg version says that i need to upgrade perl when i recently have done it and all the dependencies for perl 07:00:34 the default version of perl changed to 5.36 and it seems like portmaster gets confused by default version changes that don't change something else of that port or something 07:07:31 ah, that default version change changes the dependencies of every port depending on perl and I don't think portmaster checks if it should rebuild because of changed dependencies 07:09:05 n30: i suspect you're going to have a bad time 07:12:15 ahhh 5.36 then 07:14:03 wonder where i got from that 5.34 was the latest 07:17:03 oh seems like -> 5.34 was 20230730 07:20:37 yeah noticed that now ... then its just to upgrade :d 12:02:44 do I have to use .eli postfix for geli labels? 12:03:04 may i use eli0? 12:03:15 because eli0a looks much better 12:24:18 hello, could anyone link me to a manual that describes the steps for installing freeBSD manually without using the installer? i have tried search engines but the results were either incomplete or 5+ years old 12:25:04 exactly this is what i am doing now 12:25:13 i can give you my wscript 12:25:13 (stuff is going wrong and i think i know why, i don’t need further help at this point, just a complete list of steps to reproduce exactly what the installer would do, what partitions are required etc, so i can change the parts that i need to) 12:25:23 wikan: please and thank you 12:25:55 wait 12:26:09 which pastebin to use? 12:26:35 chat title seems to link one that looks good enough 12:26:38 wikan: bsd.to 12:29:41 https://pastebin.pl/view/bd8e9d7b 12:29:42 Title: script - Pastebin 12:29:47 this is old and BAD script 12:29:57 today i will have good, new version ;) 12:30:40 this script works fine up to 180 line 12:30:54 i know what i did wrong :) 12:31:28 and after all you need this -> https://gist.github.com/yzgyyang/4965d5673b5c79c644a695dd75fa8e05 12:31:29 Title: FreeBSD mount img files · GitHub 12:31:46 this script install freebsd on ecrypted / partition 12:34:55 today i will have correct script 12:35:13 and maybe in 2 weeks my own dialog based installer 12:35:51 if you want me to share with you, priv me your mail, so i will send it to you 12:37:08 wikan: thank you! i just want to get freeBSD running on my weird old laptop with a weird EFI, so i think i should be fine with this, i will probably be back if i can’t figure it out 12:40:21 in my code is a bug. script stops when creating users 12:41:32 so I had have to finish installation by hand :D 12:42:59 well this is my first script I wrote maybe 1 month after I started using freebsd :) 12:44:25 how do you all organize your poudriere runs? the automatic number of builders is dicey cause it fires 11 builders seeing as i have a ryzen which is swell for most packages until we get to the heavy hitters (llvm,rust,gcc,browser) 13:38:43 Gooooood mornininink 13:44:36 !gm 13:53:48 what does "Root mount waiting for: CAM" mean? 13:54:08 means just that 13:54:37 the CAM system is a physical layer that has to settle before a disk can be mounted 13:55:10 man -k cam will give you a bunch of man pages 13:56:17 hmh, and what does it mean when i get repeated errors and timeouts that mean it takes forever to boot and even when it’s finally finished booting keeps spamming my console? 13:56:27 man 4 cam will give you more than you need to know 13:56:41 skyenosaur: could be you have a failing disk 13:56:57 skyenosaur: could be a bad device driver 13:57:12 it would help to know the hardware involved. 13:59:32 it’s 10 year-old thinkpad that is kind of banged up anyway, but has so far been running smoothly under linux, i just need it as a freeBSD test machine 13:59:33 skyenosaur: pkg install smartmontools might help you 13:59:45 smartd will tell you what's up 13:59:57 skyenosaur: which thinkpad? 13:59:57 it keeps complaining about ahcich1 on different slots 14:00:21 Dianora: z50-75 14:00:29 it does have a broken cd drive, maybe it’s that 14:00:42 that would do it 14:01:17 man 4 ahci 14:01:40 hope that helps. I have to step out 14:01:56 yes i got it from here, thank you Dianora! 14:02:08 you are welcome. 14:04:58 skyenosaur: you should be able to disable it in device.hints 14:05:02 man device.hints 14:05:13 gotta go 14:08:18 i'll probably just disconnect the drive instead :) 14:31:36 Hey all, any LDAP fans out here? I wrote this article, and if you're interested in running LDAP+LDAPScripts, I would love if you can test this article to make sure it's all working fine. https://wiki.freebsd.org/LDAP/Setup 14:31:37 Title: LDAP/Setup - FreeBSD Wiki 14:42:15 antranigv: tks, will take a look! 14:42:43 cedb thank you! I will add the client side as well, using SSSD 14:44:02 antranigv: i dont see any pam related stuff, do you have a recomendation for a link on setting that up? its probably pretty simple just sanity/best practices yk 15:05:57 cedb so for that I use SSSD, I haven't documeented that yet, but lemme paste the code 15:06:14 sorry for typoes, texting iin a cabb 15:06:28 bsd.to is dead? sad 15:09:13 cedb here's the basic gist: https://reviews.freebsd.org/P614 15:09:14 Title: ✎ P614 SSSD config 15:10:37 cedb as you can see, I'm using NSSwitch instead of PAM, but the idea is the same. I used nsswitch because I'm more familiar with it, due to working with NIS for years. 15:13:41 antranigv: ahh okay not familiar with centralized auth i guess that makes a lot of sense to just nss into using ldap, theres just a bunch of pam modules id like (like u2f) hmmm 15:14:13 cedb u2f is for 2FA? 15:21:24 yep 16:25:25 cedb: I configured poudriere to work on 2 ports in parrallel each with 3 jobs as most stuff doesn't benefit from jobs anyway, but building 4 heavy ports in parallel was to much (as my cpu has 4 cores poudrieres default was 4 builds in parallel) 16:30:15 nimaje: I found that the limit on building packages in parallel is memory rather than CPU cores. 16:35:30 Schamschula: yep, but poudriere just looks at the cores for its default, well any default for that setting will be wrong, they should have just set it to 1 16:37:45 Yes, but "heavy" packages, like gcc, llvm and rust fail because of insufficient memory. 16:46:59 well i think my earlier question of what does this error mean has been succinctly answered by the hard drive dying, lol. my freebsd adventures are not off to a good start 16:54:42 skyenosaur: zfs or ufs 16:54:43 skyenosaur: I did say eh? ;) 17:02:40 Dianora: you did! and honestly i'm a little impressed that freeBSD started printing errors from the start, whereas linux didn't say a peep this whole time. the HD has been iffy for a while 17:03:17 cedb: not sure what your question relates to, sorry 17:08:46 your drive that is dying what is the fs on it 17:13:38 cedb: it was zfs, but i didn’t get file system errors, the system started freezing whenever it was running from hd (memory is fine, usb systems run) 17:14:43 i kind of gave up on it, its a 10 y/o laptop and i have other systems. i'm now preparing to install on my desktop 17:31:10 hm ya zfs sounds a little mean to old commodity hardware (why im asking in the first place) 17:37:01 cedb: why? (just trying to understand what’s so special about it) 17:39:24 but either way that can't really be the source of the problem. performance issues i could understand but not this, especially with the CAM timeouts and the system freezes and the way the HD has been excruciatingly slow for months. i was just waiting for it to fail tbh 18:35:36 can i mount a luks encrypted linux lvm partition under freebsd? sorry searching kinda hard bc no X yet and phone screen tiny 18:38:23 skyenosaur nope :( it works only on Linux. most encrypted disks are like that. However, you can use a bhyve VM to mount it using USB passthro 18:40:31 antranigv: aww okay thank you! its ok i will simply change it then 19:23:18 rwp: pikvm has been on my radar to check out for a while. Just had a closer look, and I'm very intrigued! In the mean time, I'm investigating installing an old FF in a jail for JRE (via ports-mgmt/portdowngrade probably), and I'll document my process just in case it works. :) 19:44:32 hi, i've got a bit of a problem: my boot ssd (for a manually installed fileserver) died (doesn't event speak sata anymore). i've got an `rsync -haHAX / /data/zroot-backup/` of the boot drive, _but_ i don't know the zfs dataset layout of the original system, and i don't know what freebsd version it was running in the end. what's the best way forward from here? 19:45:50 n-st: ugh. 19:46:03 i guess the blunt approach would be to reinstall from a boot iso (to get the partitioning, boot sector, and zfs datasets set up for me), then steamroll it over with the old filesystem contents? 19:46:16 n-st: that happened to me some months ago, which is why I ended up spending the $ to zfs mirror 19:46:22 n-st: yes 19:46:30 that's what you will need to do 19:46:35 (that would need the same freebsd version though -- how do i find that when i've only got the filesystem contents, including /boot though?) 19:48:08 or i could manually set up the partitioning and zfs datasets… would be more convenient since i can do it on my "proper" computer rather than hunched over with a portable screen -- but would have more room for error when it comes to dataset optinos 19:49:35 hmm, since i'll need to know that either way: how do i find out what version it was running? (i've got the zpool imported, but i'm on a linux machine, so can't just run `freebsd-version` from the backup) 19:50:05 n-st: man freebsd-version gives you one method in the man page 19:50:35 can you share any link to information about custom binary package repositories? 19:50:49 i wold like to make my own with my tools 19:50:51 so you could dig into /boot/defaults/loader.conf and /boot/loader.conf 19:50:59 wikan: poudriere 19:51:09 safest best bet 19:51:36 n-st: 19:51:37 To inspect a system being repaired using a live CD: 19:51:37 mount -rt ufs /dev/ada0p2 /mnt 19:51:37 env ROOT=/mnt /mnt/bin/freebsd-version -ku 19:51:49 good luck with it! 19:51:54 Dianora: `env ROOT=/mnt /mnt/bin/freebsd-version -ku`? that would need a running freebsd kernel, though… 19:52:13 you'd be using a repair cd or usb stick no? 19:52:45 Diamora, nope, I want my own repo 19:52:57 so you'd mount your old system copy on /mnt 19:53:38 wikan: lots of stuff about it on the ML and it's documented but start with man pkg. You could add your local repo 19:53:51 Dianora: oh, actually that's a shell script and (mostly) functions on linux. turns out it was a 13.2-RELEASE :) 19:54:17 thanks 19:54:26 I've never had to make my own binary repo. Unless someone else here has I'd suggest crawling the ML as well. 19:54:31 wikan: You are welcome 19:54:41 n-st: ;) that makes it easier 19:54:43 Dianora: i will be using a repair stick eventually, yeah, but first i needed to find out which version i should download and use 19:55:19 n-st: good luck... and mirror that disk preferably with two different manufacturers 19:55:29 would have been a bit tedious to download one version, then inspect the dead system and find out i'd need a different one after all ':D 19:55:45 ;) 19:55:51 but that's sorted, time to grab a 13.2 boot medium then ^^ 19:57:08 Dianora: i wish i could :/ that thing is built down to a budget and size, so it only has two sata ports. one used for the os ssd, one for a data hdd. most of the data is backed up offsite anyway, so it's a reasonable trade-off to trade a cheaper system for longer recovery time on failure 19:57:29 and looky what we've got now: a failure and long recovery time >.< 19:58:30 what i would do different, though: zfs send|receive for the backup, instead of the rsync. would make recovery of the os at least a bit more convenient 19:58:59 and i see that some of the data might not be backed up offsite at all right now, which needs fixed as well 19:59:48 fwiw, this is the current backup cronjob: 19:59:49 # makeshift backup because of failing SSD 2019-07-28 19:59:49 0 6 * * * root rsync -haHAX --exclude=/data/ --exclude=/dev/ --exclude=/proc/ --exclude=/tmp/ --exclude=/var/cache/ --exclude=/qua/ --delete --delete-excluded / /data/zroot-backup/ 20:00:11 n-st: fair enough 20:00:28 yes zfs send|receive is wonderful 20:00:36 the failing SSD in 2019 at least had the decency to throw SMART errors in advance, so i replaced it in time back then. but now the replacement has failed without any warning whatsoever… 20:01:33 n-st: that's exactly what happened to me 20:03:05 last question about the restoration: there really isn't anything special/"magic" stored somewhere, right? i.e. partition table + boot sector + default zfs options from installer + filesystem contents = the whole system, there's nothing missing from that? 20:04:18 n-st: You *are* doing gpt + zfs root? 20:06:11 in fact easiest for you is to install your 13.2 on that disk boot to make sure it works, then go back to install isk zap the /etc etc. etc. etc. 20:06:40 skip the second step if you want to save time 20:07:00 Dianora: uh, not sure to be honest… whatever was the default in 11.1 (bsdinstall_log says that's what i originally installed) 20:07:44 well it says it did `gpart create -s gpt "ada1"` 20:08:04 and `zpool create […] ada1p4` 20:08:10 so i guess that's that ^^ 20:08:44 n-st: This is why all sys admins should keep a paper logbook 20:08:57 ;) 20:09:06 Dianora: what do you log there? 20:09:25 I log the disk partition format, what is on each etc. 20:09:57 that's a bare minimum. saves a lot of time when recovering 20:10:28 log the commands needed to recover from a disaster etc. etc. 20:13:42 hmm, that's a pretty neat idea 20:14:52 until now that sort of information (if i even wrote it down) got lost in text files someplace or other, but i've had a logseq database for a while now, that would actually be a good place for that sort of documentation 20:19:15 what kind of stuff could trigger that? 'sh 91809 [zfs teardown inactive] 2095.72r 0.81u 8.37s 0% 4052k' 22:31:14 hmm, if I have a VM on a zvol, and the OS inside the VM uses ZFS, should I enable compression on both or just one of them, and if so, which? 22:43:11 I guess I'll disable checksumming and compression on the child and let the host handle that because VMs are slower 23:31:07 zwr, In practical terms it does not matter much if you enable compression both places or not. 23:31:47 The popular compressors like lz4 and zstd detect poor compression on already compressed data very quickly and auto-disable themselves quickly. 23:32:23 If it is compressed both places then the hosting storage will detect the already compressed data and it won't matter. Not much. 23:33:31 And then the VM will be configured just like any other. And the storage values for it will be on the compressed data. So I would tend to prefer it that way. 23:33:58 But if compression is turned off in the VM then the hosting storage will do the work instead. So don't think it really matters one way or the other.