mason: #debian-bsd is the channel btw, #debian-kbsd was for the port that got killed. the new folks moved due to the hostility towards the idea of reviving the port. the new channel isn't very active though

how can I set the DCSP field for certain destinations on FreeBSD/PF?

also wondering if where exactly deauth packets are handled? nl80211 or in the rtwn/ath drivers?

Could a driver be rewritten to ignore certain kinds of deauth packets?

OK this is driving me crazy, every time I su to root it throws me into /root instead of leaving me wherever the existing shell is, what causes this?

crb running a login script

sfox I think a login script is already being run but I don't see anything in there that changes directory to /root

could you be a bit more descriptive

crb, try 'su' without the 'su -'

what command are you using to get root?

try doas -s

thanks!

if i did make config when im going to compile a port will it give me options on what i want or do i have to babysit it after i make my choices ?

jb1277976: After modifying the configuration, the build process would indeed apply stuff you've asked for, yes (if that is your question.)

question i want to put freebsd on a laptop right.. the flash drive i have is only 961M does freebsd have anything that small ? memstick is 1gb and so are the isos

i do see a boot only.. let me try that one

You could possibly use the bootonly image or do the installation over network.

kfv: i've put freesd on this laptop before.. my internal wifi card dosen't work so i bought a third party.. will i be able to configure it at boot ?

Configure the dongle? Sure, why not?

Thanks

kfv: you around ? I did make config and I chose everything I then did make install clean and it's promoting me to check stuff did I defeat the purpose ?

make config-recrusive && make install clean fixed it . Didn't know emacs had so many deps

Hey, sorry, wasn't around when you pinged. Good to hear you found out how to tackle the complication.

whats the point of BATCH when you can't see what you compile.. shouldn't you just install a port ?

s/port/package ?

trying to read SD cards on freebsd, I can see the sdhci in dmesg finding the reader... but I insert a card and it doesn't show up in geom

camcontrol doesn't show it either... I can see the SATA drive and the disk drive, no SD card

do you have MMCCAM? otherwise, it won't show up as a CAM device

the new behaviour of "bc" is grinding my gears, I've had to do ctrl-z , kill -9 %% , until I see that they changed it to require a "quit" command now. my ctrl-d to exit muscle memory will persist

but to be fair, it's been that way for a while it appears, switched sometime after freebsd 12 maybe :-)

/ignore -channels #freebsd-irc -network Libera * JOINS PARTS QUITS

I've been using marksman for LSP in Neovim historically. But on FreeBSD, it isn't supported. What are you using?

Before I compile something from ports is there a way I can check what does they have ?

date 0909102024 that should be todays date and time where i live right ?

ferebsd is giving me 2009

jb1277976: you can check synopsis in date man page to see that your assumption is incorrect

hi, how do i compile FreeBSD's tests? i had to add a new test function to an existing test in /usr/src/sys/netinet/libalias, but now I can't compile it, and when i run it with kyua test -k /usr/tests/Kyuafile sys/netinet/libalias, the old version is running

dacha: the test themselves seem to be in /usr/src/tests/sys/netinet/libalias/

yes sorry that's where i patched them. but now how do i compile that?

make?

"make test" apparently, in that directory

well, that's a bit more than just "compile" :)

aquamo4k, I don't understand your complaint about bc and Control-d not exiting bc. Works for me on 14 as it has always worked. FreeBSD bc quit is slightly different than GNU bc quit but more sane.

pabs3: Ah, thanks I'd only ever been in #debian-kbsd. I'll add the new one to my list. I guess I'd seen some traffic last year and that seems recent to me. :P

rwp: could be my term tty then? I can reproduce on 15-CURRENT on 3 different systems, on 11.2 it's "normal". looking into it to find out why

I would certainly be annoyed if Control-D stopped working but it would create a scripting problem too. Because I most often use it as a sub-process effectively "echo 2+2 | bc -l" and if it does not stop at end of file then that would create an infinite loop with bc reading endlessly from the pipe.

aquamo4k, What does "stty -a" say for you about "eof".

stty -a | grep --color eof

jb1277976, "date 0909102024" has 10 digits and matches yymmddHHMM so that would be 2009-09-10 10:24. To avoid Y2K type issues I always specify the full year these days but in the traditional format date setting format today now for me is 2409151158.

jb1277976, The way to set the date on your system is "sysctl ntpd_enable=YES ntpd_sync_on_start=YES" and then reboot. It will set the time correctly on boot from then forward.

rwp: tpaste.us/VYya

That is pretty bizarre! What happens if you type in just "cat" there? Same type of behavior?

i can exit cat with ctrl-d and ctrl-c just fine when it's taking STDIN as input if that's what you mean

I would start being paranoid about what command I am invoking when I typed in "bc" so I would double check with "type bc" where for me it returns "bc is /usr/bin/bc".

yeah, i mean i built all three systems from source cloned from github.com/freebsd/freebsd-src

you don't need to reboot after enabling ntpd, just start it

It's good to get all of the running daemons started from the start with the right time. Otherwise some daemons will be confused having the time jump while they are operating.

going to build a fresh 14.1 system and see what happens, vms are cheap

aquamo4k, What I see here: paste.debian.net/plain/1329478

rwp: kk, will quick try a vm

The FreeBSD difference around quit feels like a sanity fix to me. In GNU bc as soon as quit is *parsed* (parsed not executed) then it causes bc to exit at parse time. In FreeBSD quit will exit when it is executed. Which feels like a normal thing to me. The other behavior really just means quit is not a program statement but an interpreter short-but command. So it cannot be used in scripts in any type of portable way.

*short-cut command

> "Cannot mix incompatible Qt library (5.15.14) with this library (5.15.15)"

bc is a command I am very often using in my editor when I am working on anything with numbers for me most often bookkeeping. I use it to add up numbers and divide by shares and any math like that which is needed. I create the equation I need "(47.20+38.12+75.00)/5" and then pipe it to "bc -l" replacing the result in the editor file. It's the easiest way for me to do math in a file.

pkg upgrade is dangerous

Now I can't launch anything

nmz, Are you mixing precompiled binary pkg with locally source compiled ports?

i use it everyday on my workstation but only occasionally on these 3 servers running freebsed

nope

I did a pkg upgrade yesterday and today telegram is broken

nmz, Here is an example of qt progs installed here: paste.debian.net/plain/1329480

Looks to me like 5.15.15 is the current version now. Meaning you need to upgrade your Qt 5.15.14 pkgs then.

aquamo4k, What FreeBSD version there? I am running 14 so changes in CURRENT I haven't seen yet.

reinstalling seems to work

weird

Certainly after a major version upgrade "pkg upgrade -f" is required to reinstall everything. And I am always impressed by how fast it runs. Just a few minutes here!

but I don't want to reinstall everything, just whatever depends on qt

I said after a major version upgrade such as from 13 to 14 or 14 to 15. At major upgrade times it is required. Because otherwise the shared libs under them will not be guaranteed to be there across major version upgrades.

does anyone know if AMD FCH XHCI supports setting hw.usb.xhci.streams = 1?

seems it was only telegram that needs reinstalling, dunno if I should report it...

rwp: slightly different behaviour on 14.1: tpaste.us/medE

rwp: ctrl-c still emits the ready for input, ctrl-D now works

Need to go do some sunday chores for a while, my workstation is using alacritty terminal so I "export TERM=xterm; tset" after I login to make things work, might be a thing, not sure

aquamo4k, I have always had that behavior on Control-c but that's just not something I ever do. But it seems like it is working as expected for you on 14.1 the same as it is here.

Meaning that there might be a change in CURRENT that I have not yet seen. Which scares me! I am going to need to build current and then file bugs to get that changed as that would be a problem.

rwp: ack. it's cool that it is broken on 15-CURRENT now, I can do some looking there. I didn't see anything specifically about this on a quick look of the git log output but I might have missed it

aquamo4k, Just closing the loop on data points: paste.debian.net/plain/1329482

I could see someone filing a bug that they "accidentally" typed in Control-D and it exited bc and they didn't like that and then someone going, well let's just change that then, and changing it. That would be very, very bad of course. But I could see it happening.

Back in the day that was complained about for ksh and so "set -o ignoreeof" was added. Which created the infinite loop problem. So they added an eof counter. If it counted 10 EOFs then it would actually exit. Meaning you had to hold down Control-D and see many warning messages be printed and then eventually the shell would exit.

There are some people who like that behavior. Probably someone here will go, hey, I use that behavior. But to me it is just not Right. :-/

Cool

I had another crucial question.. can I install a port answer or add it remove what I want and install all deps without having to choose for each dep ?

If that made any sense

^

is there a way to get the system to list or report the bhyve instances running?

crb: ls /dev/vmm

well, technically that's all instances configured, not all instances actually running, i'm not sure the latter is possible

rwp: my bc issue was already a bug, cool: lists.freebsd.org/archives/dev-comm…-src-all/2024-September/045187.html

aquamo4k, Thanks for the follow-up. So this is a bug introduced in CURRENT which I have not seen yet. It would be a serious problem that would be noticed. Hoping that it is corrected soon then.

And this is definitely telling me that I need to start running CURRENT so that I can trip over these things before they sneak into a RELEASE. I would definitely have found that regression in my routine use of it.

ack, yeah. been broken since aug-26 so more eyes are always a good thing

tracking -current via source builds is much less painful in build time now since they don't default to doing a full clean everytime (clang/llvm seems like 80% of the time to build)

current + meta make + pkgbase is great

if only ports wasn't still such a shitshow (oh dear, i'm going on about that again)

^^ ack

it's cool that pfSense tracks current now too although I'm sure they have lots of brighter eyes on it than mine :-)

the build was broke for a few minutes yesterday when pf was updated but that's normal from time to time

rwp: Is there testing automation in place to check for recurring bugs once spotted?

lw: cool, I never knew that, thanks!

mason, I don't know.

Hi

make install missing depenancies is giving me a pkg-static error that it can't find a packet in the repo's.. any idea why ?

I got it working it was just that package that didn't have the deps

Hi there,

is there any way to identify what process is triggering/calling another binary?

Scenario is like "something" is calling the dhcpclient every hour (/usrshare/local/bin/dhcpclient) and I want to identify how and what process is calling it.

cybercrypto, I guess ktrace/dtrace could - but it's most likely an RC script or cronjob I imagine, especially if it's happening exactly at the same point every hour.

Tabmow: thanks for replying. would you give me an example capturing any sample binary calling? Any doc for me to start understanding it?

cybercrypto, I only know hackish ways to do it. I rename the binary to dhcpclient.real and then install a #!/bin/sh wrapper which <<exec dhcpclient.real "$@">>'s the real program. In between I place debug statements to write debug output to /var/tmp/something using /var/tmp because it is not cleared on a reboot here.

rwp: your suggestion is quite practical. I will try that.

The script can log the date and time, the calling environment, the process stack (ps auxdww), and whatever else is needed. Then undo the hackish wrapper when things are understood and no longer needed.

whatever is calling the binary will call it again... and it will call script made tailored to debug.

many thanks Tabmow and rwp.

I realize aux does not display the PPID column so maybe alx or a better set of options there.

procstat might be useful, and ports-mgmt/pkg-provides can help narrow down which package installed the binary if that fails

I think for me I would use "ps alxdww" for all of the information.

pd -d is quite useful, yeah

This laptop I installed freebsd on boots to a black screen with the mouse pointer white on the left corner.. kldstat shows nvidia.ko and nvidia-modset.ko checked 20-nvidis.conf and everything seems fine.. any ideas ?