compiling duke3d is like watching bitchx compile

lol

cpet: just install it from packages

or use some quake variant from the same

i set hint.pcm.<n>.eq=1 in /boot/loader.conf for n = 0-3 – yet I don't get bass/treble knobs in mixer after rebooting. sysctl dev.pcm only shows me 0-3, as does ls /dev/mixer* – does the equalizer depend on some hardware feature or something?

(also not getting them if passing -f /dev/mixer0[-3] to mixer)

phryk, does the driver actually support the other channels

cpet: how would i even know? kldstat | grep snd doesn't show anything, so I'm not even sure what driver is used…

should see it in dmesg

Title: pcm0: <ATI R6xx (HDMI)> at nid 3 on hdaa0pcm1: <Realtek ALC671 (Rear Analog)> - Pastebin.com

I have 3 plugins it only shows one which is the middle green one

so yeah :)

now when I had a sound blaster audigy which was the sound card to have back in the day it showed all the plugins as that card is nicely supported

Can confirm that it was indeed the sound card to have

how do i just "start over" and reinstall freebsd without using an old cd? is it deleting everything in /usr/local/bin and unpacking base.tgz and all that?

only one DE works (xfce4) and well dwm works but the text is so small, nothing else not even twm

Is there anyway to escape variables in rc.conf? for example   node_exporter_args="--collector.ntp --no-collector.zfs --collector.filesystem.fs-types-exclude='^(devfs|nfs)$'"

A quick google search shows someone else has recently had this issue, but there is no resolution eg forums.freebsd.org/threads/need-hel…-in-rc-conf-for-node_exporter.78268

Title: Need help specifying args in rc.conf for node_exporter | The FreeBSD Forums

superblavman: seems to work this way: node_exporter_args="--collector.ntp --no-collector.zfs --collector.filesystem.fs-types-exclude=^\\(devfs\\|nfs\\)\\$"

Does anyone have experience building a Go program? I'm trying to build Aerc mail client with notmuch support and it requires a notmuch.h header. It's present in /usr/local/include but the linker still can't see it. I tried prepending the make command with 'GO_EXTRA_LDFLAGS=-I/usr/local/include' but the result's the same.

What the linker wants is likely not the include file itself, but the lib... never mind.

Anyway, if they come back: courtesy of "pkg provides notmuch", -I probably goes into the compiler flags instead, and the linker flags should probably have -L/usr/local/lib instead.

pmnw, think you want -I which include or ads a search dir for /usr/local/includ as it defaults to /usr/include

pmnw, so you would change build_cmd:=$(GO) build $(BUILD_OPTS) $(GOFLAGS) -ldflags -I/usr/local/include "$(GO_LDFLAGS)" -o aerc to include -I/usr/local/include

ugly but works if this isnt a port/start of a port

cpet: thanks for this - will try it as soon as I have the chance; it really is quite a mess of a workaround :)

pmnw, if you aren't making a port does it really matter how you compile it ?

anybody know if fbsd will function on a late2013 macbook pro?

may want #freebsd-ppc

2013'd be Intel I think

ppc in Macs is ancient at this point

well the point of that was != wrong channel

Oh, you mean "there might be Apple hardware people in there?"

why wopuld I spenr 3 grand on a laptop to install freebsd on it

heh

More likely, someone already has one and decides they want FreeBSD.

it will jujst a pain to install

I had one of them and it had a gorgeous display. I gave it away to someone who needed a machine.

may have better support with NetBSD

Some of this might be relevant, despite this being for older-than-2013: forums.freebsd.org/threads/success-…eebsd-13-0-on-macbook-pro-5-5.80458

Title: Success: Installing FreeBSD 13.0 on MacBook Pro 5,5 | The FreeBSD Forums

When you have a Universal Operating System, and you have some bit of hardware kit, you want to run that operating system on that kit. Makes sense to me.

What.

People wanting to install FreeBSD on a 2013 Macbook Pro.

I think I missed several memos.

I don't know why anyone would spend the Apple premium to buy a 2022 Mac and immediately want to install something else upon it.

Seems to me that 2013 and 2022 aren't the same year.

It was 28 minutes ago that someone asked about installing FreeBSD on a 2013 Macbook Pro. Makes sense to me.

So instead of helping you go on some tirade?

rwp wasn't on a tirade. There was earlier confusion about why one might want to install FreeBSD on a Mac, disregarding the age of the hardware in question.

One good reason for installing FreeBSD on a 2013 Macbook is that Apple no longer provides software updates for it.

At least they don't for the 2012 that I own, so I imagine 2013 is either in the same bucket or will be soon.

Here I was commenting upon someone else's tirade and didn't realize I was creating my own. I guess I now see how these things escalate quickly.

rwp: But look how fast it was de-escalated! :)

Thanks for being the adult in the room! It's appreciated it! :-)

For the record, wiki.freebsd.org/AppleMacbook is probably the best source of information, cf. things like asmc(4) which is still occationally updated.

Title: AppleMacbook - FreeBSD Wiki

Ah, good to know. I didn't notice that on a quick search, and pointed the person to a forum post instead that seems potentially close.

I am running FreeBSD on a year 2008 Thinkpad x201 with 4GB of RAM and it runs acceptably well. But...

WiFi is problematic. Buggy. I am chasing bugs. I'll make a bug report when I get time to converge on things a little more.

I have not tried WiFi Box ("wifibox") yet but that's soon on the list. I can see it being successful where native is failing.

rwp <no help at all> I was running FreeBSD on my x200 with 8GB of RAM and it ran acceptably well. BUT... wireless was terrible. While the wireless for me worked at home, when travelling - my mom's linux laptop connected to the various hotspots... my FreeBSD was hit-or-miss, at best. When I returned home, I installed debian back on my laptop :( FreeBSD Foundation has some initiatives to improve

wifi/wireless.

<offtopic> just to counter my last negative FBSD post - my htpc is currently running linux and is trying to delete TB off a zfs deduped-pool (after 3 days it's down from 11TB down to 6TB). I would "bet money" FreeBSD could do it a lot faster!

you mention FreeBSD yet its offtopic ?

"friends don't let friends run dedupe" <- a very smart FreeBSD person (think FreshPorts) said that. He's probably right.

more RAM could do it a lot faster

limit it

yuripv: LOL it typcially has 64GB... BUT right now it only has 16GB <- another cause, NOT regarding linux vs bsd!

give zfs 64GB it will gladly take it with a grin and a finger

i still have free ram, but linux doesn't show arc very well :(

more so with dedup

cpet: with dedup, that is true!

I never though I could use 64GB of RAM... dedup proved me wrong

ARC

different guides say ~16-20GB of RAM per TB of deduped pool, count yourself

you can tune it and still have nice speeds

i have 24gb of ram and I tunr zfs for 1gig

cpet: right now NFS is totally broken from that machine, to my FBSD desktop. I like FreeBSD's "the nfs server is not responding" error message, you don't get that on linux.

ok

any who turkey eat and watch movies with the pups

day*

happy turkey day!

i dont celebrate it just a reason to make decent food

freeze half and eat in in xmas so I dont cook

nice. enjoy!