Is anyone here an old-timer who coded in the 70s-80s?

that generation doesnt often irc ime

vs gen-X and some millennials, where irc was in peak use in their youths, and unlike genZ and whatnot where they've seen someone use irc once, maybe...

Gen-X coded in the 80s too.

not generally professionally

but sometimes

I mean, I was dorking with basic in the 80s

does that count?

(I took the question to mean someone in the 70s through the 80s, my bad I guess)

Nevermind, got my question answered. :-)

I just had some questions about BASIC yeah.

But I got some info from elsewhere.

Thanks though. :-)

quackgyver: 80s

This is #FreeBSD, not #askrandomquestionsandexpecttohavethemansweredbecauseyoucan'tbebothered to use a search engine. ;)

It also couldn't be that, because that exceeds the maximum length of channel names. :P

how does one prevent a module from being loaded? I don't want to load intel wifi for instance

crb: what's it being loaded by?

And speaking of not that at all, freshports.org/sysutils/sndy seems like it could be useful.

It's hard to find answers to the kind of questions I had, so I opted for looking in places that were likely to have a lot of senior programmers with decades of experience. :)

Title: FreshPorts -- sysutils/sndy: Sound Switcher

debdrup: I'm not sure I see it in the boot messages but it's not listed in my loader.conf

quackgyver: That doesn't really address anything about what I said.

It addresses the being lazy and not wanting to use a search engine part. :)

crb: it's possible that it's kld_list in /etc/rc.conf

debdrup: nope it's not in /etc/rc.conf I believe it's being autoloaded because it's a hardware device that's present but I don't use it and compiled it out of my custom kernel

Outside of devd, I can't really think what could be auto-loading it. FreeBSD doesn't really have any facilities for auto-loading, which is partly why devmatch(8) exists to begin with.

Are you using FreeBSD or some derivative?

FreeBSD

well perhaps it's devmatch then, is there a way to disable it

I think you misunderstand.

perhaps I do

There's nothing that autoloads in FreeBSD (aside from maybe devd, like I said) - devmatch(8) exists to inform you which unattached devices have drivers available for them.

uh, i don't know about that

and module_blacklist in loader.conf doesn't work as one would expect

crb: devmatch_blocklist

rtprio: what would one expect?

debdrup: devmatch also loads those drivers by default, not sure if there's actually an inform-only mode

oh wait, maybe by manual operation

looking at the manpage, it's really missing some important details

kevans: where in rc.conf or loader.con or somewhere else?

crb: rc.conf

see /etc/rc.d/devmatch for details

kevans: thank you!

kevans: i would expect the module not to load

reality: i'm doing it wrong or the module still loads

rtprio: it's a loader-only knob

it prevents the module from loading in loader, unless you force it

it was kind of a rushjob because drm started killing off machines if it was loaded that early around 12.0 time, so the documentation probably sucks if it exists

using pkg to get chromium new version and its 8.2kb/s

is there something wrong?

13.1

i7

i know and i put it in loader.conf and it doesn't work as expected

concrete_houses: just a slow mirror, patience young skywalker

i don't know what to tell you, then

it works as designed

any chance anyone here has gone through a recent depenguinization FreeBSD 13.1 install on Hetzner? (Would be nice if it was in the new Hillsboro, OR location) - Hetzner and DigitalOcean have been disappointing and stopped supporting FreeBSD as some of you might know.

kevans: which one are you blocklisting?

i tried blocklisting zfs and zpool commands still load the module

right, that's not what the knob does

like I said, it's a loader-only knob

there's no way to stop zpool(8) from loading the module short of removing the module, afaik

kraptv: i've used mfsbsd recently, works fine with PX62-NVMe

otis: thank you very much for that - just trying to gauge that the mfsbsd method is still somewhat valid. sounds like it is!

patience luke!

kevans: ugh

that strikes me of limited use

meena: Line 19 where I pressed ctrl-c at the Y/n prompt

anyone experienced getting code 5 error on startup with chromium?

has someone

the problem feels familiar. Think I had this problem in OpenBSD caused by memory limits. But I cant understand why I get crashes and the errors in freebsd on a fresh install

If there is some debug or increased verbosity option, you could try running with that

ill do that, lets see if get any wiser

no error on chrome startup

here

concrete_houses: note sure if the error message is the cause.

ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address - not sure what the problem is

every time I get a paste from some infiniband devices, I feel like half my assumptions are invalidated

you should never have asked :)

kevans: huh, I didn't realize that - from the escription subheader in the manual page and wiki.freebsd.org/AutoLoad it's not really evident

Title: AutoLoad - FreeBSD Wiki

The rc.d script is pretty unequivacle though.

ugh, drm-kmod now synced with linux-5.15, hopefully, my long standing hangs with i915 will be fixed

Funny that we're ahead of Debian now.

mason: in?

Demosthenex: Re: angry_vincent's noting: "drm-kmod now synced with linux-5.15"

mason: fun, indeed :)

interesting

debdrup: yeah, devmatch(8) has a vague SEE ALSO to rc.conf, but IMO it'd be nice if it actually described the devd/rc integration a little bit more

angry_vincent: which long-standing bug?

I've had issues with the i915_request uma(9) zone ballooning to many GB (currently it's just shy of 4GB) and eventually starving all other parts of the VM of memory (including ZFS ARC) - but so far this only seems to happen after +40 days of uptime, which is much less than my 14-CURRENT upgrade schedule (and is also longer than most periods between SAs for -RELEASE)..

"Build 14-CURRENT with KASAN is also on the TODO list", but... it seems to be append-only, currently. :(

#259670

very similar #266315

I think I've seen that very rarely.

switching to CURRENT improved little bit, but still i getting sporadic freezes/hangs which appear out of nothing

I think the last time I looked into it, I got stumped by not being able to look up the error code in any documentation on the other side of the pond.

Without knowing what the error codes mean, we can't even determine if the multiple bugs in the report are the same issue, or not.

don't they use -errno?

If it does, I'm not sure it makes sense that it's throwing an ENXIO

So, I have a linux guest running in bhyve using vm-bhyve for management. The guest has its IP, but when I ping external addresses, tcpdump shows my ICMP as coming from the main IP of my host, not my guest. What could I be missiung?

otakon: it's generally not considered very polite to send private messages to people without asking first.

And I'm pretty sure I already made it clear that I don't want to be on the hook whenever you need help.

If you have a question about FreeBSD, just ask it in the channel and if someone knows and has time, they'll help.

/mode +g helps :)

I thought the question was about FreeBSD bhyve's network routing. No?

Then I guess ghoti needs to generate a FreeBSD guest in vm-bhyve and then it becomes a FreeBSD question due to lack of needing to mention anything else.

there's a #bhyve channel here on libera as well, I believe?

I was going to ask you, for if you have any info since the last conversation here, to repost it here. sry for being intrunsive

All traffic out from my bhyve instance seems to have a source IP of my host, not the bhyve guest. Any idea why that might be happening?

nat?

does that warning on the freebsd handbook 4.5. (using the ports collection) mean that PKGs and ports should not be used on the same system at all or does it mean that you shouldn't use pkgs and ports of the same program on the same system?

i mean... if i have used pkgs so far but a program is available only as port, i guess i can use it

hubertm: there are some points you should keep in mind when mixing ports and pkgs (and I heard years ago it was even more); use the same branch of the ports tree (easiest probably to switch to the latest pkg repo and use the main branch to build your ports; if you build ports with changed option, stuff depending on it may need to be build against that version too, so better play it save and also

build reverse dependencies yourself then, (did I forgot something?); to make it easier to work with ports you can use poudriere, the -devel version has an option to fetch packages from the official repo too and then check what needs to be rebuild, so that you don't need to build stuff where you didn't change options in many cases