07:49:43 <mane> I need to upgrade my FreeBSD server from 13.2
07:49:58 <mane> Can you give me instructions on how to do that?
07:57:31 <al1r4d> mane -> https://www.debugpoint.com/upgrade-to-freebsd-14/
07:58:05 <mane> I found this one already, tjhankbyou :-)
07:58:10 <mane> Thanks you
07:58:12 <al1r4d> no problem, mane
07:58:15 <al1r4d> your welcome, mane
07:58:15 <mane> Thanks you
07:58:40 <mane> I don’t want to break my server ;/
10:31:44 <SKull> mane: just don't (under any circumstances) run `zpool upgrade`.
10:32:19 <mane> Ok
10:32:23 <mane> Thanks for the hint
10:40:08 <mane> Hm damn autocorrect
10:44:13 <angry_vincent> you can do that if you updated bootloader first, and it supports new features of zfs. usually it is not the case
11:42:24 <mane> i don't know why i can't run my services on startup >.>
11:42:44 <mane> but thanks guys, i'm upgraded to 14.0 :-D
11:43:01 <mane> freebsd-version
11:43:01 <mane> 14.0-RELEASE-p8
11:45:01 <mane> also openvpn refuses to run as nobody on 14.0
12:05:38 * CrtxReavr casually runs 13.x with no issues.
12:32:12 <VVD> nxjoseph, hi!
12:33:05 <VVD> About https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280591
12:34:19 <VVD> There is a mess with names in the port: spoofdpi, spoof-dpi and SpoofDPI.
12:35:44 <VVD> Ports dir can be spoofdpi or spoof-dpi, camelcase SpoofDPI not welcome.
12:36:53 <VVD> rc.d script can have sign "-" in names and camelcase isn't welcome (or even forbidden) too. Allowed are spoofdpi and spoof_dpi.
12:37:25 <VVD> PORTNAME can be spoofdpi, spoof-dpi and SpoofDPI.
12:37:47 <nxjoseph> hi, VVD
12:38:01 <VVD> Even upstream use different names SpoofDPI and spoof-dpi.
12:38:42 <VVD> Best is just spoofdpi, but this require:
12:38:43 <VVD> post-extract:
12:38:43 <VVD>         ${MV} ${WRKSRC}/cmd/spoof-dpi ${WRKSRC}/cmd/${PORTNAME}
12:39:16 <nxjoseph> no need to move it like this, i did so in second patch
12:39:19 <VVD> "GO_BUILDFLAGS= -o spoofdpi" doesn't work.
12:39:35 <nxjoseph> i noticed that it doesn't work
12:40:12 <VVD> Mk/Uses/go.mk line 248.
12:40:24 <nxjoseph> GO_TARGET=      ./cmd/spoof-dpi:spoofdpi
12:40:24 <nxjoseph> this is how i fixed it
12:40:35 <nxjoseph> it becomes spoofdpi
12:40:37 <VVD> :-o
12:40:43 <nxjoseph> i need to remove -o
12:41:19 <VVD> ye, already
12:41:43 <VVD> it's work!
12:42:30 <VVD> go:1.21,modules - why hardcode version?
12:42:46 <VVD> doesn't support 1.22?
12:43:08 <nxjoseph> it's what upstream use in go.mod file
12:43:10 <VVD> BTW, 1.21 is default now.
12:44:02 <VVD> Testing build with 1.22 now
12:44:25 <nxjoseph> I think we should use go 1.21 because the project is beign made with go 1.21
12:44:52 <VVD> build without errors with 1.22 too
12:45:21 <VVD> My suggestionis is: USES=go:modules
12:45:35 <nxjoseph> so it will use go 1.21?
12:45:47 <VVD> yes, 1.21 is default now
12:45:53 <nxjoseph> okay
12:46:06 <VVD> But if somebody want it can set other default locally.
12:46:18 <VVD> s/it/he/
12:47:29 <nxjoseph> what do you suggest, should i include changes in third patch to bug report or should i send a full patch including full port with changes
12:49:32 <VVD> nxjoseph, check my comments - hove no time to create proper patches.
12:49:59 <VVD> Just check is it ok for you, and I'll commit it later evening.
12:50:10 <nxjoseph> I saw your comments but I already have applied patches you said
12:50:27 <nxjoseph> i also run portlint and portclippy on Makefile and mine seems better
12:50:41 <nxjoseph> but there is one problem
12:50:49 <VVD> I'm using this script from yesterday to run it as a daemon. :-)
12:51:01 <nxjoseph> me too but it needs args to work
12:51:10 <nxjoseph> did you change anything in rc script
12:51:22 <nxjoseph> if no args is specified in rc.conf, it doesn't run
12:51:29 <VVD> hm
12:51:44 <VVD> spoofdpi_args="-dns-addr 127.0.0.1"
12:52:15 <VVD> Run fine for me without spoofdpi_args.
12:52:27 <nxjoseph> strange
12:52:33 <VVD> But I have spoofdpi_enable="YES"
12:52:33 <nxjoseph> let me try rc script in your new comment
12:52:36 <nxjoseph> me too
12:53:06 <VVD> Maybe copy&paste from comment broke the file…
12:54:16 <CrtxReavr> You should generally not modify files under /etc/rc.d/ or /usr/local/etc/rc.d/ - pass settings to them via rc.conf
12:54:36 <nxjoseph> we do so, i pass settings to /etc/rc.conf
12:54:47 <nxjoseph> VVD, maybe
12:55:12 <CrtxReavr> And if you need to add your own start-up scripts, don't put them in either of those locations, as it may knock heads with OS upgrades and ports/package management.
12:55:41 <VVD> CrtxReavr, we are preparing new port: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280591
12:55:43 <CrtxReavr> Create like. . . a /usr/opt/ prefix, with /usr/opt/etc/rc.d/ and put your scripts there.
12:55:58 <nxjoseph> isn't /usr/local/etc/rc.d is place for packages' startup scripts
12:55:59 <VVD> With rc.d script.
12:56:09 <CrtxReavr> VVD, oh. . . well that's different - just make use of rc.subr
12:57:06 <nxjoseph> VVD, i copy&pasted your rc script now service command doesn't see it
12:57:11 <nxjoseph> spoofdpi does not exist in /etc/rc.d or the local startup
12:57:11 <nxjoseph> directories (/usr/local/etc/rc.d), or is not executable
12:57:27 <nxjoseph> ok i solved it by marking it executable
12:57:47 <nxjoseph> but it doesn't seem to run
12:58:05 <CrtxReavr> local_startup="${_localbase}/etc/rc.d" # startup script dirs.
12:58:30 <CrtxReavr> That's how you'd add startup directories in rc.conf
13:02:07 <nxjoseph> also PORTNAME must be SpoofDPI, otherwise building fails
13:10:26 <VVD> nxjoseph, build fine for me… I'll attach complete patch, but only later evening - must go now
13:15:28 <nxjoseph> ok bye
13:47:54 <mane> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275916
14:10:42 <victori> has anyone successfully injected a self signed trust store which curl/wget work with?
14:11:14 <victori> curl --cacert mycert.crt https://whatever.lan/ works but when it is part of the freebsd trust store chain it does not
14:11:24 <victori> works fine part of the chain in osx/linux
14:11:45 <victori> is there a specific format the crt needs to be?
14:41:52 <victori> ah SSL_CERT_DIR needed to be set
15:14:59 <last1> have there been recent cve's and/or exploits that succeeded against a FreeBSD system running with securelevel higher than 0 ?
15:15:18 <last1> just trying to gauge how useful that feature is or how much trust I should place in it
15:23:47 <polyduekes> last1: wont a privilege escalation will suffice for securelevel 1?
16:16:51 <tarel2>  I tried to set my system up for  xfce and kde so I could chose one or the other , that failed and I rebooted .  But  some  errors with zfs happen and then it could not find the kernel the bootloader.  I don't know freebsd , I'm new so I don't know what might be the problem.
17:59:55 <monkeybusiness> .
19:07:31 <dautor8518050867> jail_attach(2) fails with EPERM even though uid and gid are 0 and jail exists... The same process which created the jail is trying to attach to it and fails...
19:07:36 <dautor8518050867> Am I doing something wrong?
20:35:10 <timothias>  /window hidelevel +joins +parts +quits
20:35:28 <timothias> my bad
22:10:41 <nsoci> name
22:11:36 <last1> why are zfs send/receive so slow for incrementals ?