01:15:44 is there any way to get any sort of status from freebsd-update? It's been sitting there saying installing updated (from an upgrade -R 14.0-RELEASE) for a while now, with no signs of progress. (h)top shows it's using like 0.2% CPU and doesn't seem to have many child processes, with the kernel using about 10% CPU 01:17:26 updates* -r* 01:20:04 are you upgrading from a directly previous release, 13.2; and did you run freebsd-update fetch and install commands before starting the upgrade to 14.0-RELEASE? 01:20:30 yep and yep 01:20:54 this is the post restart freebsd-update call 01:21:00 what does 'freebsd-version' say when you run it in a different terminal? 01:21:32 14.0-RELEASE-p4 01:22:13 that is the most recent version of freebsd on 14.0-RELEASE, iirc, so that is good 01:23:13 yeah, I just don't remember it taking this long after the reboot to complete the second freebsd-update 01:23:36 I just it's been a while since I did a major upgrade 01:25:14 understandable, it took a bit for me on my older laptop that runs most of my freebsd services; I'd say give it some more time. you can always run 'freebsd-update IDS' to confirm the system against a known good configuration after it completes to check 01:25:26 I would run "ps auxd | less" and inspect to see what is running. I would run top/htop and see if anything is spinning using cpu. 01:27:54 yeah I have htop running and not much is happening other than the kernel and a few services. I'm guessing there's a lot of calls to install happening which aren't showing up in htop since they're so quick 01:28:17 which would probably explain the kernel activity, since it's all file system changes 01:34:03 ok, running opensnoop shows a lot of callsa to install and gunzip, so looks like things are happening 01:34:10 how good is dtrace 01:35:42 is there a way to find out what zfs features are supported by the current kernel? I have a zpool that I exported from macOS, and I couldn't import it on 13.2 because it had features that weren't supported (I've seen comments online that 14.0 has them, but I don't know how to check) 01:59:45 @Axman6 "zfs version" will give you the version of zfs. My 14.0 box says 2.2.0. 02:00:05 You can probably do the same on the mac. Then, compare differences in version numbers. 02:07:08 is darwin running FreeBSD? 02:08:18 yes :) 02:08:30 Did you just do an install? 02:08:42 no; I did that the day 14 was released 02:08:46 oh okay 02:08:49 that was not so long ago 02:09:00 actually that was just an upgrade 02:09:07 my last fresh installation was maybe FreeBSD 11 02:09:21 you upgraded from 11 to 14? 02:09:26 big jump? 02:09:31 from 11 to 12 to 13 to 14 02:09:35 yeah 02:09:43 I see 02:09:48 but I don't always boot into it; recent years it's more that I boot into Slackware GNU/Linux for more hardware drivers *BSD doesn't have, but if I could learn to run Slackware in BHyVe I'd boot into FreeBSD maybe all the time 02:10:37 i did the same on my server (11 to 14 in the right order) but noticed it'd filled up the entire GBs of the server in some temporary directory not documented in installation instructions 02:11:54 does darwin use enlightenment on FreeBSD as his desktop? 02:12:33 no 02:12:41 i used KDE3 then XFCE 02:12:50 sometimes KDE4 & 5 but they're so damn slow 02:13:07 in the past or for short usage also TWM or something 02:13:17 use e 02:13:40 did you switch back to E from XFCE? 02:13:58 yes 02:14:13 it just looks cleaner, more stylish and more options to configure 02:14:17 the thing is, E doesn't handle multiple monitors as well as XFCE. In XFCE it's automatic but in E it was a major pain to get setup even partly right 02:14:30 just get one big monitor 02:14:37 i have a big one but I use three 02:14:44 dang, much head turning? 02:14:48 not really 02:15:23 my classic 1600x1200 (on KVM switch for current PC, classic P3/686, and servers) is above my 4K, and my drawing pad LCD is to the side but mostly used for occasional command-line stuff 02:15:41 so I have necessary uses for all these monitors 02:16:02 if E could return win3-style program management I'd consider trying it again 02:16:21 last time they said you used to be able to setup that manually but that that process was broken 02:16:32 yeah I forgot what that even is 02:16:38 manually would involve putting hundreds icons into program groups so not worth it 02:16:41 I just use a mac style dock 02:16:46 and tiling 02:16:57 well you could view a picture or video about win3. It was nicer than start menu or Apple equivalent 02:17:13 it's so easy to slip to a wrong menu or out of it entirely in that style 02:17:14 my .bashrc isnt being executed on login. However when I run bash it loads the file 02:17:30 program manager was windows containing program groups that all got moved to submenus later 02:17:40 so you can't slip out of it easily or go to the wrong one easily 02:17:58 additionally you can always see all programs of certain types you have available, reminding you if you want to do something. It was great! 02:18:54 XFCE and maybe some IBM GUI used to have this stlye also. MS allowed still using it in win95/98 but later removed it entirely. Companies always remove features with newer worse stuff they falsely claim is better then force everyone to use that 02:19:33 the program groups looked like a file manager in icon mode and the icons launched programs 02:19:42 well except had no menus or stuff to the sides 02:19:53 are you sure you have your shell set to bash, then mnathani ? 02:20:05 I do 02:20:17 try ~/.bash_profile 02:20:21 darwin: I'm running centos on bhyve, slackware shouldn't be too hard 02:20:21 i like ksh like on NetBSD UNIX 02:20:25 great 02:20:34 or symlink ~/.bash_profile to ~/.bashrc ? 02:20:43 well those files have different purposes 02:20:46 what is this bhyve? 02:20:51 is it pronounched "behave"? 02:21:18 yer a wizard AumShivaya 02:21:22 it worked 02:21:23 darwin, what about using e's "everything launcher" 02:22:16 it may be better to load one of those bash files in the other. They run in a certain order 02:22:24 bhyve ia pronounced like a bee hive the place were bees live 02:22:34 its a virtual machine 02:22:35 great mnathani :) 02:22:59 not like linux compat? 02:23:10 but more like virtualbox? 02:23:31 the order is: /etc/profile , ~/.profile , ~/.bash_profile , ~/.bash_login but I don't have a note on when ~/.bashrc runs 02:23:59 linux comp runs things under freeBSD, the program run but uses a sys call emulation later that translates linux sys calls, bhyve is more like virtual box or vmware 02:24:01 I guess, but I am not sure, that bash_login runs when you log in to a tty 02:24:02 in ~/.bash_profile at the end I source ~/.bashrc 02:24:16 but rc does indeed run for me when I open a terminal, say, terminology etc. in X 02:25:18 that is probably a good way to do it darwin 02:25:28 rather than a symlink 02:35:34 "bhyve" is pronounced "bee hive", and is the hypervisor of choice for FreeBSD hosts. 02:36:01 bee have 02:36:24 No, "hive". Like where bees live. 02:50:06 johnm: finally finished, using execsnoop was helpful for tracking that something was happening 03:31:28 becasue i basically have the worse luck in the world.. a machine that had 3 usb drives (setup to zfs) died.. my question is.. is it possible to "move" a zfs pool to another machine if you do not have backups? 03:31:55 i am currently looking at new machine.. to replace the dead one and now i have 3 drives setup with a zfs pool .. it is my synology dying all over again.. minus the linux filesystem 03:38:54 whats the difference between software found in the form of a package vs a port? 03:43:45 never mind looks like with a zpool import, that hsould allow me to do all this 03:57:48 mnathani, packages are precompiled, but you have to compile ports. 04:00:16 voy4g3r2: yes spool import is what you want to do and it should work fine, I've move rust between machines and just spool imported it. That's part of what make ZFS great NO hardware raid dependancy 04:30:56 crb: thank god, because i have a large disco biscuits, ryan adams, and everyone orchestra live setup 04:32:23 now time to see if this lenevo i have my eye on will work with freebsd 05:45:34 hmm, if i cherry-pick a commit from main to stable/14, then the commit is MFC'd, that shouldn't cause a merge conflict, right? because the MFC should be done via cherry-pick as well? 05:47:34 unixwitch: right, git should just drop your local commit when you rebase over stable/14 05:48:48 i cant get oss to pick up my subwoofer sound output. anyone know how to get that working? 05:49:47 i think it shoudl be under the surround sound channel but it doesn't show up in the sound options, only the two speakers work 05:49:52 kevans: thanks 05:58:19 spine-o-saurus: doesn't your sub have a crossover? i wouldn't expect a sub to be on its own channel 06:00:04 uhm, im using freebsd on my sdcard to rn opnsense, and i just noticed it isnt utilising the whole capacity of the sdcard.. how do i fix that? 06:00:47 pulled ports and run out of space heheheh 06:01:22 sams: use 'gpart resize' to resize the appropriate partition, then growfs to expand the filesystem (assuming you're using UFS). preferably take a copy of the card first just in case... 06:01:47 is that cli? 06:01:53 yes 06:02:14 ok great, im not worried about data there its just the opnsense router and have backed up the current config 06:02:16 oh you said opnsense, i don't know anything about that specifically, but i assume it offers a shell 06:02:47 yeah i only have web/shell access, cannot plug it into a monitor though so yeah headless 06:03:30 hmm... you might also try doing this with the /etc/rc.d/growfs script, which is intended to do this automatically specifically for the case of SD-card installations... but perhaps opnsense already uses that and it didn't work for some reason 06:04:21 otoh it's not hard to do manually and growfs script looks quite complicated, so perhaps don't do that 06:05:17 ok thanks 06:05:46 kid playing VR online atm will do it when she idle, if i get stuck i'll be back! 06:07:33 jwp, spine-o-saurus: depends what sort of sub it is... a surround sub would usually be on the dedicated lfe channel (assuming the hardware has one) but an audio sub nearly always uses a crossover which means the OS can't detect its presence... 06:11:38 ok that was painless 06:12:05 i had a quick window and did the growfs one and it worked 06:13:19 Avail 51G yay 06:14:55 i dont use the LFE port on the sub 06:15:29 it just goes straight to the mainboard sub plugin 08:23:29 if i install freebsd from source or install the system first then update from source and build a custom kernel would i be able to get sound working on this chromebook ? i've installed freebsd on it and had a working system for about a month already but sound never worked unless i used a dongle with headphones 08:30:30 jb1277976: the GENERIC kernel should include all available audio drivers, so i don't think building from source would make a difference 08:30:44 jb1277976: does it detect the built-in audio device at all? (cat /dev/sndstat) 08:31:28 also, is this amd64 or arm64? 08:33:21 unixwitch no I’ve taken FreeBSD off since I was upset. I only have hdmi/8 something I forgot. Nothing I’ve done in the past months have worked verbose boot has no other pcm0 devices I just thought building from source would give me some hope 08:33:26 amd64 08:34:47 there's a slight possibility that some weird audio device isn't included in GENERIC for some reason but it doesn't seem likely. hard to say more without more info, like a 'pciconf -lv' 08:35:17 Let me oull up a Freebsd fourm I posted 08:35:23 pull* 08:38:03 https://forums.freebsd.org/threads/trying-to-get-headphones-working-on-a-laptop.91214/ If your went to look over yet everything 08:38:04 Title: Solved - Trying to get headphones working on a laptop | The FreeBSD Forums 08:38:53 Actually unixwitch that was the wrontnthread it's buiried deep 08:40:11 I will install FreeBSD again and try 08:41:05 booting the installer may be enough to debug this if you don't want to wipe whatever OS is currently installed 08:41:24 i don't remember if the installer includes all the kernel modules though... 08:45:14 ok let me download the iso boot live cd and go from there brb 08:52:34 unixwitch it only has (play) default and that is pcm0 on normal machines like this old racer I would have more pcm0 devices 08:54:09 jb1277976: output from 'pciconf -lv' would be useful here, but if you're on the console i guess it's hard to paste the whole thing... do you see any other audio-related devices in the output though? 08:54:37 (especially if they're "none⊙p." which means no driver is attached) 08:55:05 those shoule have class=multimedia 08:55:10 s/shoule/should 08:55:23 yea let me post it 08:57:35 Did that post ? 08:57:41 one sec 08:58:29 i didn't see anything 08:58:48 did you paste it at bsd.to? you need to link the url here too, it won't post automatically 08:58:52 hdac0@pci0:0:31:3 but its comet lake PCH-LP cAVS 08:59:43 Normally on Linux I need sof-firmware 09:03:01 jb1277976: is hdac0@pci0:0:31:3 different from the pcm0 device? i think dmesg should show which pcm is attached to which hdac... 09:03:28 (your issue is that pcm0 is the HDMI audio output and there's no pcm1, right?) 09:05:49 Nope no pcm1 09:07:21 Let me install FreeBSD will take like 5 mins I have nothing important on this laptop. Need to setup WiFi also brb 09:07:35 i guess "sof" just needs some new sort of driver that no one has ported yet... 09:13:28 Yep 09:13:51 that was my only conclusion I spent a week trying to get it to work lol 09:15:24 I’ll give it another shot I got nothing to lose 😁 09:16:33 Looks like GPU-specific driver would be needed for sound-over-HDMI: https://forums.freebsd.org/threads/amd-gpu-sound-via-hdmi.74863/ ; https://forums.freebsd.org/threads/sound-over-hdmi.36130/ 09:16:34 Title: Solved - AMD GPU sound via HDMI | The FreeBSD Forums 09:17:50 parv: i think the issue here is with the non-HDMI output 09:18:44 unixwitch, Oh right!🤦🏽‍♂️ 09:23:26 so i've used zsh since forever, but i'm trying fish... it has no completions for poudriere though :( 09:24:18 That could be "Just a matter of programming" surely 09:24:31 yes, i had about 47 other things to fix first though :-) 09:25:01 (got my nfs bug fixed, ported sublime music, now i need to port mediaelch... i might have a look after that if i'm still using fish) 09:25:45 unixwitch, What does "mediaelch" do? 09:26:20 parv: it creates XML ".nfo" metadata files for Kodi/Jellyfin media servers 09:26:34 unixwitch, Thank you 09:27:01 hopefully won't be hard to port since it's just a Qt app and alreadys runs on linux and macos 09:28:45 actually i should also look at why Jellyfin is broken on freebsd, i had to convert my media server to linux temporarily... and also update/fix the navidrome port... 09:31:47 oh, and fix that kadmind bug too 09:32:05 think the next item on my todo list might be 'find a todo list manager for X' 09:46:10 hmm, if a port supports both Qt5 and Qt6, should that be done via options or flavours? 09:48:16 unixwitch: "it depends" is the correct answer here (imo), what is your use case? 09:50:08 TommyC: no particular use-case, it's just a normal desktop application. i checked an existing port (audio/pavucontrol-qt) and it doesn't seem to specify a Qt version... 09:51:05 oh, it does: qt:5 09:51:54 unixwitch: it's possible that that's the only version of Qt it can be applied to (either the developers of the original project use something specific to that version of Qt or the maintainer hasn't had a chance to try and build against Qt6 for the project yet) 09:52:09 * kenrap wonders if it supports a qt6 flavor as well 09:52:21 feels like only yesterday everything was on qt4 :( 09:52:30 am I getting old? no...it is the developers who are moving quickly 09:53:27 perhaps i'll just use Qt 6 for now (as it's the latest version) and see if anyone objects when i submit it 09:56:07 unixwitch: best of luck :) 10:19:09 ports-mgmt/submodules2tuple is handy 10:24:01 ok i'm treying to boot the intaler on a thinkpad x250 but i get error 19 10:25:53 it fails to mount the disk image] 10:31:07 i tried this https://forums.freebsd.org/threads/installing-9-0-release-mounting-dvd-failed-with-error-19.36579/ 10:31:08 Title: Solved - Installing 9.0-RELEASE: Mounting DVD failed with error 19 | The FreeBSD Forums 10:31:10 didn't help 10:33:13 i need a faster CPU for building these huge GUI applications... i keep thinking i should rewrite all the GUI stuff i use in C/Motif to reduce bloat 10:34:20 I'm a total noob with build systems. I have a little program using the header . On Linux you have to build that with $(CC) -lsctp, on Freebsd you don't need / must not have this flag. Why is that? 10:35:32 jemius: it's just an implementation difference. this has historically been fairly commonly for sockets... for example, Solaris used to require -lsocket to use the sockets API (rather than the XTI API), but BSD/Linux didn't. i guess Linux decided SCTP isn't important enough to include in libc. 10:36:20 other examples of this include the historical -lm (libm, for mathematical operations) which is often included in libc nowadays so it's not required, but oftena dummy libm is shipped to avoid breaking software that uses -lm 10:36:47 jemius: if you're using something like cmake or autoconf, you should just add a build-time check for whether libsctp exists, and link it if it does, otherwise don't 10:37:41 wait, sctp should always be a separate lib, shouldn't it? what is in libc and what is not is standardized 10:38:02 although, look at netinet/sctp.h, i don't see anything that would require a library... i wonder what's in linux's libsctp? 10:38:17 jemius: no, that's not standardised. POSIX defines things that *must* be in libc, but it doesn't say you can't include other things. 10:39:03 all it says if that if you're using a POSIX conformance macro (like _XOPEN_SOURCE) then certain things should be excluded from the headers on build, but they can still exist in libc 10:40:12 if you couldn't include non-standard things in libc, then functions like sysctl(3) couldn't be included, but they are 10:41:02 It seems to me that the sctp-helper-library is somehow separate in Linux: "client.c:(.text+0x4cd): undefined reference to `sctp_sendv'" 10:43:07 it seems like you're using a Linux-specific library called LKSCTP: https://github.com/sctp/lksctp-tools - i don't see it in ports... you might need to rewrite to use the APIs that FreeBSD providers, or port the library 10:43:08 Title: GitHub - sctp/lksctp-tools: The Linux SCTP helper library 10:45:10 FreeBSD does provide the functions sctp_sendv() and partners. They're specified by the RFC for the Sockets API, so it can be expected that they are provided 10:45:18 FreeBSD seems to provide them differently, though 10:45:25 hm does it? there aren't any manpages 10:45:55 Well, I can perfectly use my Linux program on FreeBSD if I build without -lsctp 10:46:03 So the function is there. Somewhere. 10:46:13 *oh* i see, i thought the linker error you showed was on freebsd, not on linux 10:46:24 yes, on freebsd it's in libc: lib/libc/net/sctp_sys_calls.c 10:47:10 https://cgit.freebsd.org/src/tree/lib/libc/net/sctp_sys_calls.c 10:47:11 Title: sctp_sys_calls.c « net « libc « lib - src - FreeBSD source tree 10:47:19 It should still have a manpage, though 10:47:23 yes, it should 10:47:52 it's not mentioned in sctp(4) either 10:48:16 there is a manpage for sctp_send(3), so perhaps sctp_sendv just needs to be added there 10:48:50 similar to how write() and writev() are both documented in write(2) since they're basically the same thing 10:49:08 https://datatracker.ietf.org/doc/html/rfc6458#section-9 10:49:09 Title: RFC 6458 - Sockets API Extensions for the Stream Control Transmission Protocol (SCTP) 10:50:37 Ah, anyways. I better start using Meson or sth 10:55:30 is "USE_GL= gl opengl" redundant? make stage-qa told me i need both but it seems like it should be one or the other 11:55:05 ok i got that working 12:06:42 14.1 in april? 12:46:30 polyex: sounds realistic 12:47:08 good stuff 12:54:39 anything bad about a pid file in /var/run having -rw------- perms? 12:54:48 owner is server's user:group 12:55:04 i saw other pid files are world and group readable 12:55:21 group being who? 12:55:56 is there not a periodic script to run zpool trim, or can i just not find it? 12:56:02 chrony is root:chronyd with -rw-r--r-- 12:56:27 polyex: PIDs are generally not secret unless you use see_other_uids=0 and are *really* paranoid about it 12:56:46 ok ty 12:57:10 oh, i guess you asked about the version that's 0600, that should be fine too. although it's a bit weird 12:57:26 pid files are generally only used by root when starting/stopping services so they don't need to be world readable 12:57:33 xrdp.pid is 600 12:57:37 root:wheel 13:14:18 patch to add daily_trim_zfs_enable to periodic.conf; does this seem reasonable? https://www.le-fay.org/tmp/zfstrim.diff 13:17:28 periodic is like a built in cron system? 13:17:55 Yes. 13:18:15 does periodic work with cron or they separate? 13:22:01 cron calls periodic. look at /etc/crontab 13:22:08 Is someone with amdgpu experience here and willing to help me? 13:22:08 I'm unable to get the thing to work... I'm stuck at 768p resolution. 13:23:07 isley cool!! 13:23:12 I'm trying to use 7800x3d integrated gpu. 13:52:02 unixwitch: why not just set autotrim? 13:52:36 rtprio: some SSDs dislike that sort of trim-behind behaviour and perform badly 13:52:48 oh 13:52:58 (this is mentioned in zpoolprops(7) under the description of autotrim) 13:56:17 went looking for a better source and apparently TrueNAS don't use autotrim because "for many SSDs it actually makes ZFS performance worse", which i guess is based on real-life feedback: https://www.truenas.com/community/threads/auto-trim-for-nvme-pool.99162/ 13:56:18 Title: Auto Trim for NVMe Pool | TrueNAS Community 13:56:53 does it really need done daily? 13:56:59 maybe autotrim fights some caching? 13:57:03 (i don't have many SSDs) 13:57:33 i don't know, it seems like something that could perhaps be configurable, except i don't think periodic(8) supports that. if you're doing a lot of writing to the device (oltp or something) you might want it trimmed daily... 15:19:09 unixwitch: re https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275965 thanks for the bug report, but patches are way easier to review on Github or Phabricator 15:19:11 Title: 275965 – periodic: add a daily zfs trim 15:19:49 meena: i thought phabricator was only for developers. is there a guide on how to submit patches like this somewhere? 15:21:39 unixwitch: pick a target (Github or Phabricator, whichever you find easier to work with) and follow procedures there. 15:22:38 meena: alright - i suppose i should move #275912 and #275915 at the same time? (those also have patches) 15:23:48 https://wiki.freebsd.org/Phabricator / https://wiki.freebsd.org/GitHub / https://docs.freebsd.org/en/articles/contributing/ 15:23:49 Title: Phabricator - FreeBSD Wiki 15:24:50 unixwitch: I haven't looked at those. but, yeah, also, you can just use the bugs URL field to point at phab / Github 15:26:10 and the commit messages should point at the bugs, see https://github.com/freebsd/freebsd-src/blob/main/tools/tools/git/hooks/prepare-commit-msg#L43 15:26:11 Title: freebsd-src/tools/tools/git/hooks/prepare-commit-msg at main · freebsd/freebsd-src · GitHub 15:27:46 unixwitch: I hope that's not too much (red tape) 15:30:12 meena: no that's fine :-) although the phabricator docs end with "use git push as usual", so i might try with github. is this only for src/ or should i be submitting ports like this too? 15:30:54 no ports have a whole sophisticated framework built around bugzilla 15:31:05 src, docs, etc do not 15:32:10 many of ports committers do complex stuff in Phab, but "update port" is usually handled via Ports 15:33:20 Github does not scale well to ports 15:41:56 do you guys have console none unknown off secure or insecure in /etc/ttys? 15:42:12 not sure which to go with 15:52:18 polyex: insecure is only useful if a) you have dialup modem lines, or b) you have a configuration where someone can get access to the console but not to the bootloader, which is fairly unusual nowadays (because usually those are on the same device) 16:07:18 well if someone can get access to the console i guess that means they are next to my physical computer? 16:07:26 unixwitch ^ 16:08:44 what situation is there where someone has access to the console but not bootloader? 16:09:17 what i wanna avoid is someone being able to bypass security by booting into single user mode and not needing to enter a pw 16:09:52 polyex: either they have physical access or, if it's a VM, they have access to the VM console or something like that. as to when you could have console access but not bootloader access, i can't think of any situation that would usually occur in. perhaps if you set a password in loader.conf... 16:10:32 if someone can boot single user, it usually means they have physical access and could just remove your disks to read the data. or boot from a USB stick. or any number of other ways 16:11:21 well if i have full disk encryption in the zfs, then they can't just take the disks out 16:13:13 i still don't totally understand this ttys feature. i feel like it's a way to bypass the user account security 16:14:00 if the disks are encrypted, you probably don't care that much about someone being able to boot single user, since they presumably can't actually boot without the encryption key 16:14:27 * unixwitch tries to remember how git works 16:15:55 anything bad if i just set them all to insecure? all that means is sometimes i'll have to enter password more often right? 16:18:03 DNSSEC errors for freebsd see https://dnssec-analyzer.verisignlabs.com/geo.freebsd.org 16:18:05 Title: DNSSEC Analyzer - geo.freebsd.org 16:18:57 "No DS records found for geo.freebsd.org in the freebsd.org zone" 16:20:02 "No DNSKEY records found" "No NSEC records in response" "No RRSIGs found" 16:20:13 whoa 16:20:16 we're so fucked 16:20:58 meena: before i submit a PR to freebsd-src... does this look right? https://github.com/freebsd/freebsd-src/compare/main...lexiwinter:freebsd-src:daily-zfs-trim 16:20:59 Title: Comparing freebsd:main...lexiwinter:daily-zfs-trim · freebsd/freebsd-src · GitHub 16:21:18 just needs a fixup. can't run package updates on my system. 16:31:15 unixwitch: periodic.conf.5 needs a .Dd bump, but otherwise this looks perfect 16:37:20 unixwitch: also, no harm running shellcheck over that script 16:39:09 oh, haskell, this will take a while to install :-) 16:41:09 unixwitch: pkg install, or https://www.shellcheck.net/ 16:41:10 Title: ShellCheck – shell script analysis tool 16:41:26 this Script is short enough to just do it on the Web 16:42:53 (Also, no need to follow blindly everything it says) 16:59:48 meena: i cleaned up that ugly $newline thing, which comes from 800.scrub-zfs, so i suppose i should submit another PR to fix it there too. or maybe not, if it works... 17:02:52 unixwitch: it's ugly, but it works is a great slogan. I personally don't subscribe to it, because if you have trouble understanding something, chances are someone else does too 17:03:17 So, yeah, just add a second commit to that PR to clean up the script you copied from 17:05:47 n.b.: I'm tidying and making dinner. my capacity for a proper review is slightly diminished, hence such very general advice 17:06:06 I expect better after kiddo is asleep or at least fed 17:12:50 * unixwitch wonders why sys/*/compile isn't in .gitignore 17:29:45 does anyone know of a good site that could help someone understand what can work with a freebsd install, hardware wise? 17:40:54 unixwitch: cuz no ones put it there yet 17:42:44 meena: it's such an obvious thing to be there that i'm wondering if there's a specific reason it wasn't added :-) 17:42:52 maybe everyone uses buildkernel/installkernel nowadays 18:05:57 I dunno, i mostly just build specific modules I'm working on 18:19:22 hmm, speaking of kernel modules, maybe i should try to fix the alc(4) bug where it doesn't work with MSI-X enabled (PR#230807). i'm not really sure where to start there though, it might just be a hardware bug... 18:20:37 actually i see there's a suggested patch on the PR 18:29:49 unixwitch i've come to realize that most desktop computers don't have sound working out of the box right ? they need some type of headphones/speakers i will just use my headset or by a dongle that plugs into my usb audio jack that i have already and i should be good 18:30:52 jb1277976: i wouldn't say that's true for "most" desktop computers, at least not in my experience. FreeBSD detected both my built-in HDA and my USB audio device without issues (although i did a fair amount of extra configuration, that was just by personal preference) 18:31:16 i haven't bought a new computer in a while though, this motherboard is about 5 years old (AMD X470)... maybe they're all "sof" now? 18:32:23 check out https://bsd-hardware.info/?id=pci:8086-02c8-17aa-22af&dev_class=04-03-80&dev_type=sound&dev_vendor=Intel&dev_name=Comet+Lake+PCH-LP+cAVS&dev_ident=4414f looks like the sound is detected in Current ? 18:32:25 Title: Intel Comet Lake PCH-LP cAVS 18:33:00 or is that old news ? 18:34:05 jb1277976: if it needs firmware, just detecting the PCI id might not be enough. but you could try booting a current snapshot and see: https://download.freebsd.org/snapshots/ISO-IMAGES/15.0/ 18:34:06 Title: Index of /snapshots/ISO-IMAGES/15.0/ 18:34:19 ok brb 18:34:45 that page says it's supported by "12.2 and newer" though so if it didn't work in 14.0, i doubt it'll work in 15. but it doesn't hurt to try 18:35:51 ok and current isn't like a release right i can't use freebsd-update and stuff ? 18:36:01 jb1277976: you might also try posting on one of the lists like freebsd-questions or freebsd-desktop if that doesn't help 18:36:15 ok 18:36:23 there are no freebsd-update binaries for -current as far as i'm aware. you'd need to build from source 18:37:01 also current can be a pretty unstable... although the last time i tried using it on a desktop was during the 5-CURRENT kernel locking changes which broke *everything*, maybe it's better now :-) 18:37:17 dam lol 18:37:56 ok rebooting 18:50:47 i moved a zfs pool to a new machine and when i try to do a zpool import -f, i get this message https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-EY/ 18:50:48 Title: Message ID: ZFS-8000-EY — OpenZFS documentation 18:51:28 the previous machine it was attached too died and the zfs did not dismount properly and when i do the zpool import -f, it also tells me a hard drive in the pool is corrupt.. 18:52:14 https://bsd.to/SfDq 18:52:16 Title: dpaste/SfDq (Plain Text) 18:52:44 so it seems i can not import this zfs.. but without importing it i can not fix the drive.. is there a way to "fix" the fault without impacting the zfs pool 18:58:53 voy4g3r2: Are there bits missing? That's only talking about potentially two disks, and it thinks there's data corrupted, which could conceivably mean there are more disks. 19:00:39 i did notice that myself.. there are 3 drives.. not sure why only 2 are showing 19:00:43 freaking usb!! 19:01:18 voy4g3r2: Ah. USB is suboptimal. Make sure they're all there, and specify them explicitly in your import line. man zpool-import 19:02:20 haha that is what it was 19:02:30 mason: agree. 19:03:23 all of the drives are now online but it is still giving me that another system thing.. even after zpool import -f 19:04:02 oh yeah.. never mind.. gotta name the pool name 19:06:08 i need someone that will tell me how to tune my tcp connectivity on freebsd ;-; 19:08:31 voy4g3r2: And if things are marginal, think about scrubbing and/or backing up data 19:13:05 mason: i am looking at another hard drive to move to another location on my property 19:13:14 i first had to see i can get this zfs pool oeprational on a pi 19:19:02 voy4g3r2: Also, I'm not sure how far I'd want to trust raidz1. I'd be more inclined to do a three-way mirror. 19:21:24 yeah i am looking at this, i got 3 2tb drives 19:22:03 right now my consumption si: https://bsd.to/JhNT 19:22:04 Title: dpaste/JhNT (Plain Text) 19:23:10 i gotta read up on this more.. either way, i take it the data would have to be moved "off" this array 19:27:18 yes 19:28:59 what hosts does freebsd connect to to run freebsd-update and pkg commands? i thought only pkg.freebsd.org and update.freebsd.org but i allow those in my fw but the commands still fail 19:30:59 polyex: i forgot to answer your last question about insecure: no, there's no disadvantage to enabling it, other than having to type the password sometimes. it can be an issue if you have a server located somewhere and need remote hands to work on it (and don't want to give them the password). 19:36:06 yay, bhyve can boot openbsd again 19:36:53 voy4g3r2: did you try import -f 19:37:05 also, i see three drives, third is /DISK-AAAABBBBCCCC0003 19:39:46 ty 19:45:08 i gotta read up on this more.. either way, i take it the data would have to be moved "off" this array 19:45:18 rtprio: yeah i got it to work 19:45:56 yeah, if a drive is bad that would be the safe move 19:51:58 i git pull the freebsd repo, but then when i build an installer image and boot it, freebsd-update fetch then gives me p9 updates. but why don't i have those already since the git repo is up to date? 19:52:17 i'm on branch releng/13.2 20:08:17 unixwitch: https://freshbsd.org/freebsd/src/commit/30ce26cacfd626552c647c9327dd510e7f421d97 it's merged! 20:08:18 Title: FreeBSD / src / 30ce26c / nfsstat: update option strings in docs - FreshBSD 20:23:16 is there no way to bypass freebsd-update to get the patch updates? 20:23:22 why does git pull not get them? 20:24:29 what repo are you 'git pull'ing 20:24:35 it does, you're probably just on the wrong branch. 20:24:37 freebsd-src 20:24:39 on github 20:24:43 releng/13.2 is my branch 20:25:11 it gets the updates but without an `make installworld` you're not actually updating anything 20:25:21 oh whoa 20:25:27 releng/13.2 definitely has the patch updates. 20:25:30 is that all i need to type or is there more? 20:25:47 yikes, you should just use freebsd-update 20:26:19 no 20:26:34 rtprio so i git pull then type make installworld then i can build the installer iso? 20:27:18 polyex: read https://docs.freebsd.org/en/books/handbook/cutting-edge/#makeworld 20:27:20 Title: Chapter 26. Updating and Upgrading FreeBSD | FreeBSD Documentation Portal 20:28:04 you're asking questions without enough context; what are you trying to do? 20:28:15 update your 13.2 via source? 20:38:04 Will ipfw in-kernel NAT support syntax like?: https://bpa.st/QCVQ 20:38:06 Title: View paste QCVQ 20:44:56 I'm specifically referring to the port ranges. 20:45:30 It's supposed to be a (mostly) drop-in replacement for natd, which supported them - but I haven't found any examples with the in-kernel NAT. 20:50:15 why does the raidz setup need to be so difficult.. i got 3 drives 20:50:39 rtprio: what would you recommend for storage with 3 drives.. for a setup.. right now i have 3 2tb drives, thinking of upgrading them to 4tb.. 20:51:09 i had a 3 drive raidz1 for a long time 20:51:29 and even ran 2 drives for 8 or 9 months (the RMA process took forever) 20:51:40 That would be fast. . . but you'd only get one drive's worth of space. 20:52:35 yeah, i would like to get 2 drives and one as "backup" 20:52:54 but i do not think this is possible.. the wife said, get it working and have a redundnacy in our pole barn.. i am sick of hearing you "fixing" your hard drive bays 20:53:46 i did not think another computer to do on me. 20:56:44 voy4g3r2: do you have the 3 drives for the mirror from different vendors/factories/batches? this reduces the risk, compared to two or three failures in batch where the drives fail in almost same time because of same defect 20:57:22 nedko: all bought different years 20:57:38 voy4g3r2, that sounds like raid1 plus a hotspare. . . still only one drive's worth of storage. 20:57:39 yup :) 20:58:11 You dould do raid5, which would give you two drive's worth of storage, and you'd be able to take a single drive failure, but. . . 20:58:33 Read speeds are fast, but write speeds are slow. 20:58:35 a 3x mirror setup can use it for a 3x read speedup 20:58:49 i basically want to stream music, movies, and some basic git stuff 20:58:56 Plus, if you're in a failure state, everything gets really slow. . 20:59:06 so i am more in the i want to have my catalogue available without lossing hundreds of gigs of my cds 20:59:52 Plus, with 2TB drives. . . if a drive fails, you're statistically more likely to take a second drive failure and lose all data, than you are to complete a rebuild with replacement drive. 21:03:47 yeah i have a large storage need but not htat big to go all out 21:04:13 Hey unixwitch been busy. Didn’t work on current. Gonna go back to a regular setup and post to the desktop list and the questions list. Thanks for the help 21:04:20 ls 21:22:26 meena is that page relevant if i want to build freebsd installers and NOT modify the freebsd of the current machine? 21:33:03 hello, anyone encountered "ERROR: Build failed for target 'images' in configuration 'bsd-x86_64-server-release'" while building openjdk17 on 14.0-RELEASE - amd64 ? 21:33:23 polyex: `man 7 release` 21:34:08 iirc- cd /usr/src; make cdrom 21:35:02 (Prolly less work to download an ISO.) 21:44:51 did git pull now doing sudo make buildworld buildkernel in the repo's dir. then i'll build an installer and see if it reflects the latest patchlevel 21:45:27 for some reason i thought the installer build was all that i needed but i guess i gotta build the repo's code, then build installer from THAT 21:48:27 i still don't follow why you're trying to do this 21:51:56 so i can make installer isos that have the latest patch level applied already 21:58:05 is that bad? 22:04:22 polyex: nope, sounds sensible 22:04:34 ty meena 22:04:44 (i wish i knew why we don't do that) 22:05:38 my idea is if i build my own installers with latest patchlevel, i can then deploy those so it's only 1 DL from the freebsd servers, not hundreds. so save the project money 22:26:36 anyone seen this one ? 22:26:39 ``` 22:29:22 # freebsd-update fetch 22:29:22 Looking up update.FreeBSD.org mirrors... 3 mirrors found. 22:29:22 Fetching metadata signature for 13.2-RELEASE from update1.freebsd.org... done. 22:29:22 Fetching metadata index... done. 22:29:22 Inspecting system... done. 22:29:24 Preparing to download files... done. 22:29:27 No updates needed to update system to 13.2-RELEASE-p9. 22:29:29 root@osaka:~ # freebsd-update install 22:29:32 No updates are available to install. 22:29:34 Run '/usr/sbin/freebsd-update fetch' first. 22:29:37 Now 22:29:39 ``` 22:29:46 What in the holy frack???? 22:29:47 please use a pastebin of some sort for longer outputs 22:30:04 never mind. 22:30:43 stupid thing wont upgrade past -p9. 22:30:55 isn't p9 the highest? 22:31:07 yeah, there is no -p10 22:31:17 yeah that is the highest 22:33:32 audit -F says there are a few security issues between p8 and p9. (server was running 12.x so I guess I should just thank my lucky stars except that we have 2 days to safely upgrade 10+ servers before everyone starts melting down) 22:34:55 so from 12.x we freebsd-upgraded -r 13.2-RELEASE and its stuck at -p8 22:38:31 according to one of our other admins "all the service boxes are stopping at p8 too" 22:40:19 audit -F just bitches about python libraries that would require someone to be on the box so I suppose we can wait. 22:40:45 our first attempts to run 14 were a trainwreck. 22:41:20 so I was wondering if anyone else had encountered this. 22:47:47 feurig: what's leading you to believe you're stuck at -p8? 22:48:37 it finishes the upgrade (13.2-release) and its at p8 and wont pass an audit. 22:50:16 so we run the above and it complains about the sshd config and then goes into the loop above. (sorry about the 10 lines) 22:50:43 sounds more like an audit bug than an update bug 22:50:50 The other admins upgrading our core service boxes found the same. 22:50:55 what does `freebsd-version -uk` say? 22:51:37 -p9 only touched ssh it looks like, so you'll probably find userland at -p9 and kernel at -p8 22:51:59 # freebsd-version -uk 22:51:59 13.2-RELEASE-p8 22:51:59 13.2-RELEASE-p9 22:52:15 yeah, that checks out 22:53:00 so you're not stuck at -p8 at all, everything is where it should be 22:56:11 except that unlike all of the rest of our p9s pkg audit gives us 4 problem(s) in 3 installed package(s) found. 22:56:45 kevans: thats really unintuitive. 22:57:08 I will have the other admins check. 22:57:20 packages aren't generally part of the base system 22:57:43 so why did the kernel not get the messege? 22:58:00 pkg audit might have some information about the base system, but its primary purpose are for things you've installed from ports 22:58:21 if I dont have to reboot this would not be an organizational nightmare 22:59:33 i don't really understand what you're asking anymore, but updating ports doesn't usually require a reboot, no 22:59:58 kevans: the two releases. 23:02:04 we have a short window to upgrade our infrastructure machines to the latest patch level, and to upgrade the packages to where they pass an audit. 23:02:42 And the machines dont appear to be getting to the latest patch level and wont pass an audit. 23:03:44 upgrading both on our internal servers worked fine. Just the machines that count aren't. 23:03:59 If thats normal. Ok as I said nevermind. 23:04:12 how large is the register space on a PCI device? 0x0000-0x1FFF? or does it vary? 23:05:27 feurig: your machines are at the latest patch level. your packages are failing audit. these are distinct facts 23:06:06 (i'm trying to work out what Linux is writing to when it enables MSI-X interrupts on this device by writing to 0x2000... is that device-specific or does the freebsd pci driver do that for you?) 23:06:10 the former we established above when you checked freebsd-version 23:06:37 Is there a way I can coerce freebsd-update to replace a locally-modified file? 23:11:29 so i clone the freebsd-src git repo, run sudo make buidlworld buildkernel, then i build an installer and use it, boot new vm, uname -a says 13.2 p9, BUT then freebsd-update fetch finds 52 files that it says will be updated as part of updating to p9!!! wtf? 23:18:46 is there any reason that you dont want to upgrade to 14 polyex 23:18:47 ? 23:18:55 kevans: Yes. And you are right and I appologize for being cranky. 23:19:06 ya 23:20:56 feurig: the unfortunate reality is that vuxml can probably be updated before the package builders finish a build of the fixed version, so the packages may just not be available yet at all 23:24:49 wow 23:25:52 so i cloned freebsd-src, built, built installer, installed, uname -a said 13.2 p9, freebsd-update fetch got 52 files needed to update to p9 (???) so i went ahead with fetch, then install, then reboot, and uname -a now says p8!!!! 23:27:16 polyex: oooo, that sounds like a freebsd-update bug 23:27:37 ya really think so 23:27:49 did you keep a list of what 52 files it thought needed updates? 23:29:52 no but i could get it again and throw it up if you want it? 23:31:44 hmm... probably better to just try it and debug from there instead of guessing from the list 23:32:15 Hm, shame there isn't an include directive to accomodate this sort of thing: https://bpa.st/RTKA 23:32:16 Title: View paste RTKA 23:32:36 what? 23:32:38 I ended up just fetching it from github (no /usr/src on this particular box) and that was what was different. 23:36:03 aah og my god it works! alc(4) now functional with MSI-X... or at least sort of... the rx is working now but the tx seems a bit wonky 23:39:35 unixwitch: NICE! 23:40:25 for some reason ICMP pings are delayed by exactly 1000ms, i think you need to do something else to set up the tx queue interrupt but when i try that the rx stops working... 23:41:56 kevans so anything we can do about this freebsd-update bug? 23:46:12 polyex: the kernel and userland can be at different patch revisions and be wholly up to date 23:49:35 but i had the latest repo source and built and installed from that. so why would there be any updates at all? 23:52:06 That's a good point. 23:54:24 I'm a little curious about your build from source saying -p9, also. Was it cloned from releng/13.2 or from stable/13? 23:56:00 bbiab, but will check in later 23:57:44 releng/13.2