Semi fixed by deleting drive structure and recreate it using my winxp vm

1 million years later: Steam running, working on running a game :D

but long format not working.. only quick

it's a vm right?

cant build security/p5-Crypt-URandom

no clue why the url is forbidden

anyone else can reproduce?

`oops I meant to put this into -ports

how_dare_you.gif

rdr: yes

what's the deal with this vm then? you want to recover some files or... just "wipe" the virtual drive?

what? I just mounted the hard drive in it

then used windows disk manger for ntfs formating

oh i'm not sure what you're trying to do sorry

What is the proper way to make sure $PATH is sane for a RC script? Because apparently /usr/local/bin is not in the path by default.

yep, it's gone,

VVelox: like any script, `export PATH=$PATH:/usr/local/bin:/usr/local/sbin` near the top

Giving up on ntfs

no idea why you might have been putting up with it in the first place

it's not a great filesystem when you could use ZFS

nearly anything is better the ntfs

rtprio: yeah, not fond of having to resort to that given it can exist in multiple paths

honestly frustrating that it is 2026 and that is not in the default path despite

if you're the one writing the script, and it could exist in multiple places, then just use the full path

VVelox: i suspect you look at any script in /usr/local/etc/rc.d/ it's going to have a very similar line to the one i just pasted

rtprio: zfs on 500gb which I need every byte in it!?

ok

or you could get a drive from after 2005

"mkntfs completed successfully. Have a nice day." best sentence saw for days :D

Just needed to use dd if=/dev/zero of=/dev/da0 bs=1M count=10 after gpart destory

and leave few mb free when partitions

also NTFS_USE_UBLIO=0

Anybody using 15.1 with an Intel Axxx?

Macer: I'm not actively using the wifi at the moment, but I have an AX201 in the NUC on my desk. Firmware installs fine with fwget and sysctl net.wlan.devices shows iwlwifi0.

i've been daily driving an ax210 since before 15.0 came out, if that counts

Sorry I was talking about an Intel arc axxx

The gpu.

mosaid, I know we joke about dd being the disk destroyer but drives shouldn't actually be destroyed by use of dd on them, just the contents of the drives. It's really a drive content destroyer. You just need to write a new partition table and partition the drive again.

dd has saved me more drive fix time than probably any other tool out there.

I use dd quite a bit. It is a good utility. Maps low level system things to the command line. Nothing else is as general purpose.

Slowly over time the things I want are now being incorporated into other tools. pv for example now has a flag pv --direct-io which is new which allows me to use it when before I would have had to use dd iflag=fullblock oflag=sync,direct

Just for one example.

Sure.

But, pv isn't in base.

dd is like vi. Always there.

Once you know it, you're in good hands and don't need anything else.

True, it is not in base. On any system I am working interactively though it is rare for it to be a base only system. I'll have installed something from ports/pkgs.

spam

how do I find out what is trying to run freebsd-update every day at 03:00 ? Since I've swithed to pkgbase, this is no longer needed and it keeps sending me email from Cron, but there is no cron entry I can find for it

duh! never mind. I forgot about /etc/crontab

horray

polarian: yes, you need to set up the console at the boot prompt with set tty com0 then stty com0 115200

(#bhyve is always the better place to ping me for such things)

fellas... has anyone in here issued the 'freebsd-update rollback' command?

vortexx: yeah already remembered, but thx for the response :)

hello. i have an old T530 laptop with kde/plasma6 which is working well and i updated it from 15.0 to 15.1 using freebsd-update this morning. after the update, when starting kde, mouse and keyboard input no longer work...i can't even switch tty using ctrl+alt+2 anymore

i ssh to the laptop and did pkg upgrade -f but that didn't fix it. only way i can get it working, is if i select kernel.old and boot back in to 15.1-REL

sorry, i meant to say i updated it from 15.1-REL to 15.1-p1

i also tried external usb keyboard/mouse on 15.1-p1 and those do not work either. it's like the whole input subsystem just stopped responding on 15.1-p1

i have another laptop, an x280 also with plasma/kde6 which uses pkg-base, and i updated this one to 15.1-p1 a few days ago and it's been working fine. it's only the T530 that's having this issue. i see there was a lot of security fixes in 15.1-p1, i'm not sure which one would impact input

any thoughts?

polarian: yw

YESSSSSSS

FINALLY

GPL IS GONE!

I will celebrate by sending this to a Linux friend of mine who loves AGPLv3!!

ok, seems like the input issue is related to wayland somehow. plasma6 with x11 session, input is working...but when using wayland session, it's not working

in 15.1-p1

CorvetteZR1: you start kde from the command line?

well then

i guess at some point i should probably swap to and learn how to use pkgbase :/

<3 freebsd-update 4ever

I haven't looked into it yet, so therefor I ask here instead. Is it supported to convert to pkgbase?

CrtxReavr: I've been updating from src as well. Built once and installed on multple devices.

rtprio, yes

i use this command: /usr/local/bin/ck-launch-session /usr/local/lib/libexec/plasma-dbus-run-session-if-needed /usr/local/bin/startplasma-wayland

when i try to load plasma-wayland session with sddm, it crashes back to sddm login. if i log into plasma-x11 from sddm, it works fine. that's a seperate issue that's been happening to me since 15.0, the input thing started happening today after the update to 15.1-p1

and the sddm thing happens on the x280 too (which does not have the input problem)

What's so great about the loss of the GPL? Doesn't really benefit anyone except corporations.

Or anyone else using FBSD as the base of their projects.

How does the GPL stop them doing that?

If you want to close-source your project, you cannot?

It's not something I'm a fan of, but it is a thing.

And who does that benefit? Primarily corporations.

Well, sure. O,r any small developer trying to build something special to them that they can sell and support to make a living.

The thing is, corproations dont give a damn about the small developer. They'll drive over them in a second.

Corporations have already wiped out the GPL licensed stuff. The only benefit they have now is that they no longer have to maintain their own code to replace the previously GPL-licensed software (which they will since it's already in place.)

bsdrobert: Of course they will.

I think corporations should pay for open source software. They make millions and even billions off the back of people who do it for free and earn nothing, then give nothing back. It's not a fair system. So I don't rejoice at this news at all.

bsdrobert: I think you have a slight misunderstanding of the way fully open-sourced software works in this case. Many companies *DO* give back if they find the software/OS useful enough. That's usually what funds a majority of the project(s).

No that's not true. I speak from personal experience.

If FBSD is completely open for corporations, it makes it more desirable for them to use and pass along as their own product. In return, they fund the development of said product so they can continue to make money.

It might work that way for freebsd, but for the small developer it does. They take it run, make money, and not so much as a thanks.

Yes, there are plenty of businesses that will take advantage of this. But, most successful-ish companies will contribute back. Whether it be code, funding, marketing, etc...

bsdrobert: That happens to everyone. That's why every corporation is in copyright court every day of the year.

Well, this is why I switched to BSL. I give a waiver for small businesses, personal use, non-profits, charities, things like that, but if youre making millions, you gotta pay. That's where I found my peace.

Don't get me wrong. I understand your concern (or lack thereof) of the GPL deletion. But, it's really a "six in one hand, half a dozen in the other" situation.

bsdrobert: And that's fine! It's exactly why multiple licenses exist. :)

Indeed

Are you using FBSD as the base of your product you're charging money for?

... from the millionaires?

If not, well, now you can.

True, that's a good point.

It is *FREE* BSD, after all.

For FreeBSD it makes sense, for any small time developer, I'd recommend protecting yourself against exploitation.

If you're trying to make money, yes. If you're just contributing to the open-source community, there's no need for protection.

But, again, it's all dealer's choice and what you choose is fine.

This is an age-old debate, but it might be better had in #freebsd-social.

mason: Very true!

I'm not in #*-social, though. So, I'll just stop here. :)

I do have something FBSD-related to ask the channel, though...

Ah, I already commented in there. It's not bad lately.

Regarding what people are using for system/network monitoring, does anyone have recommendations for something that's either FBSD-specific or at least works well with FBSD?

ek: Any of the usual things should work. Nagios is popular.

I've tried Nagios (works fine, but lacks history/graphs), Monit (didn't work too well), Icinga2 (a disaster), Zabbix (looks nice but is wildly bloated and very difficult to configure).

Prometheus and Grafana (currently using) seem to work well, but also seem a little bloated and resource hungry.

Nothing terrible. But, once you get into Telegraph, Redis, Graphite, etc.. and have to store all kinds of random stuff for N days/years, it seems to really get slow.

mason: Yeah. I'm also still using Nagios in the background. I actually really liked Nagios with pnp and/or nagiosgraph back in the day. But, those died with PHP7 it looks like.

Hrm, I'd never used either but the notion of history and graphs is nice. I've only ever used it in the "what's red on the board" sense.

I got to like LogicMontor but that's commercial.

uptime kuma for telling me if stuff is borked, victora logs for logging, will deploy victoria metrics when I have time. i still have a very custom collectd + riemann setup.

got a kernel panic, at the db> prompt does `dump` not do a minidump by default?

it looks like its trying to dump all the RAM, and that won't fit in the configured swap on this system

dch: how far off are you? you probably want dumpon_flags="-Z"

(zstd, though there's also -z for gzip if that's your cup of tea)

kevans: thanks, I think I set that last time, lets reboot and see if I get anything

if not I will set up a netdump server

@mason / @rwp - just a late thank you for the amd/nvidia info above, very helpful - I do want to try to get into some gaming that's newer than like PS1 era stuff eventually, and I like the idea of SteamOS for that so I want to put a *little* (is that even possible now, lol?) money into a decent used card, but a lot of games I'm eyeing still are quite old.

@rwp - also that tip about understanding IPv6 and what the devs were thinking ("Power to the Client!") is really helpful. I find I can figure things out much better when I know the headspace ppl who built it were in at the time.

I learned enough IPv6 to get a block for one of my jobs, setup BGP with multiple transit providers, get it going for some DSL(!) customers and others, but then we had like zero people clamoring for it, couldn't get it at home without a tunnel, and forgot so, so much.

spork_css: Steam is always a challenge on FreeBSD. pertho might have some notes to share.

whatever PC desktop I throw together is going to be multi-boot, so I was hoping to just do SteamOS...

spork_css: i spent pretty much all of yesterday trying to get linux-steam working :)

SteamOS is basically an immutable Arch distro, which is what i'm using with KDE Linux

as for FreeBSD and linux-steam, i got it working after much work with Gemini, but then i accidentally hit "hibernate" and now my FreeBSD drive is unbootable :D

spork_css: Alright, dual boot would solve the issue.

Also, rdr - thanks. You've saved me some time trying. :P

yeah mason it's possible to get it working, but Gemini literally gave up on making Sonic Mania (one game i tested) have palatable audio (esp. music)

it was actually quite funny because i said "NO LINUXISM" when i started the AI chat thing, and it started spitting out Linuxisms then apologized for "hallucinating"

I wouldn't trust a chatbot as far as I could throw it for any of this.

Gemini is notorious for halluncinations, and halluncinations can be reducted by connecting the LLM to trusted sources.

I like how they use the benign term "hallucination" for when their product fails.

i was suprised it admitted that it did that

like, used the term

It was programmed

right, it's just usually used as a derogatory term for AI mistakes

My FreeBSD system crashed with a segfault... "no, FreeBSD hallucinated and thought it had access to memory it didn't"

lol :D

halluncinations generally occur when the answer is not known or in its training data, you can greatly reduce this problem by connecting the llm to external sources that dont rely on its training data, or supplement it. so no i dont think the product is failing. the solution is to avoid relying on training data alone.

lol lmao

This is just a fact. You can connect an LLM to the freebsd handbook and and man pages, and have it _only_ source answers from those sources. Then the chance of a halluncination is reduced by orders of magnitude. Not impossible, but highly unlikely.

the term "hallucination", like many other weird tech/AI-isms is more meant to make the failure sound better than it is and to perpetuate the myth that the LLMs "think" and are vaguely sentient.

which is kind of essential to the overall marketing blitz/haze/propaganda

So if you point it to factual data, it won't fail to provide factual responses. Got it.

Yes, and you can write your own system prompt, which the LLM will generally abide by. What you see on chatgpt.com or whatever is just LLMs for the masses. You can specialize them, and theyre much more useful.

ai sucks. I don't use it.

bsdrobert: The trick is all the destructive, immoral training prior to your feeding in the handbook.

Sorry, "ai".

Well, at least understanding how they work a little bit is useful to know. Theyre programmable tools. You can extend them, with code (tool calls). You can define the rules (system prompt).

mason: yep, "The FreeBSD handbook made reference to the term 'master'. This is white supremecy term is offensive to PoC and minority groups. I've hallucinated the new term 'primary' so no feel-feels have been hurt"

There's an LLM for that type too. It's called Grok.

Grok goes woke sometimes and I love that, but also feel a little bad for the staff that has to deal with it.

luser: We were on the same page until the racist tourettes. :/

Call me master

mason: yes, there is a moral argument to be made about that but mostly around copyright and pollution. However, you can train your own model too, and it can be done in accordance with your ethics.

That's where SLM (small language models) are becoming popular, and theyre generally hyper-focused on a certain task or area.

bsdrobert: From scratch? Because no one does that. My understanding is that... well. I'll actually finish this in -social.

yes, lets go there

master by itself to refer to something at the top hierarchically with regards to tech isn't an issue IMO. the problem is that it was used with the term "slave" in regards to drives--which is an unnecessary association with historically horrible connotations

i'm surprised connectors haven't undergone a change in naming conventions. refering to connectors as eithe male or female and describing how many times those connectors can be connected before wear and tear results in failure as "mating cycle"

lol. bsdrobert is "ai"

this seems a #freebsd-social discussion

you are how your name is spoken.

How many cycles did that take you?

try find a better use of your time than being a troll on irc.

Take it so -social.

s/so/to

you forgot to terminate your regular expression too. clearly AI halluncinating.