I need to upgrade my FreeBSD server from 13.2

Can you give me instructions on how to do that?

mane -> debugpoint.com/upgrade-to-freebsd-14

I found this one already, tjhankbyou :-)

Thanks you

no problem, mane

your welcome, mane

Thanks you

I don’t want to break my server ;/

mane: just don't (under any circumstances) run `zpool upgrade`.

Ok

Thanks for the hint

Hm damn autocorrect

you can do that if you updated bootloader first, and it supports new features of zfs. usually it is not the case

i don't know why i can't run my services on startup >.>

but thanks guys, i'm upgraded to 14.0 :-D

freebsd-version

14.0-RELEASE-p8

also openvpn refuses to run as nobody on 14.0

nxjoseph, hi!

About bugs.freebsd.org/bugzilla/show_bug.cgi?id=280591

There is a mess with names in the port: spoofdpi, spoof-dpi and SpoofDPI.

Ports dir can be spoofdpi or spoof-dpi, camelcase SpoofDPI not welcome.

rc.d script can have sign "-" in names and camelcase isn't welcome (or even forbidden) too. Allowed are spoofdpi and spoof_dpi.

PORTNAME can be spoofdpi, spoof-dpi and SpoofDPI.

hi, VVD

Even upstream use different names SpoofDPI and spoof-dpi.

Best is just spoofdpi, but this require:

post-extract:

${MV} ${WRKSRC}/cmd/spoof-dpi ${WRKSRC}/cmd/${PORTNAME}

no need to move it like this, i did so in second patch

"GO_BUILDFLAGS= -o spoofdpi" doesn't work.

i noticed that it doesn't work

Mk/Uses/go.mk line 248.

GO_TARGET= ./cmd/spoof-dpi:spoofdpi

this is how i fixed it

it becomes spoofdpi

:-o

i need to remove -o

ye, already

it's work!

go:1.21,modules - why hardcode version?

doesn't support 1.22?

it's what upstream use in go.mod file

BTW, 1.21 is default now.

Testing build with 1.22 now

I think we should use go 1.21 because the project is beign made with go 1.21

build without errors with 1.22 too

My suggestionis is: USES=go:modules

so it will use go 1.21?

yes, 1.21 is default now

okay

But if somebody want it can set other default locally.

s/it/he/

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

nxjoseph, check my comments - hove no time to create proper patches.

Just check is it ok for you, and I'll commit it later evening.

I saw your comments but I already have applied patches you said

i also run portlint and portclippy on Makefile and mine seems better

but there is one problem

I'm using this script from yesterday to run it as a daemon. :-)

me too but it needs args to work

did you change anything in rc script

if no args is specified in rc.conf, it doesn't run

hm

spoofdpi_args="-dns-addr 127.0.0.1"

Run fine for me without spoofdpi_args.

strange

But I have spoofdpi_enable="YES"

let me try rc script in your new comment

me too

Maybe copy&paste from comment broke the file…

You should generally not modify files under /etc/rc.d/ or /usr/local/etc/rc.d/ - pass settings to them via rc.conf

we do so, i pass settings to /etc/rc.conf

VVD, maybe

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.

CrtxReavr, we are preparing new port: bugs.freebsd.org/bugzilla/show_bug.cgi?id=280591

Create like. . . a /usr/opt/ prefix, with /usr/opt/etc/rc.d/ and put your scripts there.

isn't /usr/local/etc/rc.d is place for packages' startup scripts

With rc.d script.

VVD, oh. . . well that's different - just make use of rc.subr

VVD, i copy&pasted your rc script now service command doesn't see it

spoofdpi does not exist in /etc/rc.d or the local startup

directories (/usr/local/etc/rc.d), or is not executable

ok i solved it by marking it executable

but it doesn't seem to run

local_startup="${_localbase}/etc/rc.d" # startup script dirs.

That's how you'd add startup directories in rc.conf

also PORTNAME must be SpoofDPI, otherwise building fails

nxjoseph, build fine for me… I'll attach complete patch, but only later evening - must go now

ok bye

has anyone successfully injected a self signed trust store which curl/wget work with?

curl --cacert mycert.crt whatever.lan works but when it is part of the freebsd trust store chain it does not

works fine part of the chain in osx/linux

is there a specific format the crt needs to be?

ah SSL_CERT_DIR needed to be set

have there been recent cve's and/or exploits that succeeded against a FreeBSD system running with securelevel higher than 0 ?

just trying to gauge how useful that feature is or how much trust I should place in it

last1: wont a privilege escalation will suffice for securelevel 1?

 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.

.

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...

Am I doing something wrong?

/window hidelevel +joins +parts +quits

my bad

name

why are zfs send/receive so slow for incrementals ?