what do I put for ip4.addr and interface with a bsd jail so I can access the outside world?

AumShivaya: have you tried this and failed? docs.freebsd.org/en/books/handbook/jails

Title: Chapter 17. Jails and Containers | FreeBSD Documentation Portal

AumShivaya, The answer depends upon several things. There is no single correct way. There are probably dozens of ways that are correct and useful in their own environments.

I control my own LAN and use static IP address assignments. But you might be in a coffee shop and only have DHCP available. Or you might need to set up a local NAT router.

That's three different ways already for three different types of environments and no idea if any apply to you or not.

figured it out thanks :)

yeah the wheel and video group

i did the same thing

Do I really need to switch to another user to run the c7 steam thingy?

like create a non-wheel user?

1. Create a dedicated FreeBSD non-wheel user account for Steam. Switch to it.

I don't know how I am supposed to get this to work if I'm in an xsession with my regular user

xhost + yeah yeah, I know, does not work for me

imma ignore that

why does it say this?

hi FreeBSD People !

Hi.

Hi

I'm using ssmtp-2.64_7 package under FreeBSD 14, for my websites' sending emails via php, it was working fine so far, till FreeBSD version 13.2, after upgrade to 14, the maillog says:

/usr/local/etc/ssmtp/ssmtp.conf not found - Unable to locate mailhub - Cannot open mailhub:25

The file is there, was working correctly before. Any idea?

Maybe some permissions?

Owner and group ownership of that path and check permissions. "ls -l /usr/local/etc/ssmtp/ssmtpd.conf"

Zyxer: Thanks for your reply, I've just removed that ssmtp package completely, enabled the dma integrated into FreeBSD 14, it works fine so far.

IT seems the package is broken with RELEASE 14..

tercaL, 14.0 is a .0 release and so maybe file a ssmtp problem report? Though dma does look like a good alternative to ssmtp.

rwp: Filed, sent a report right now! Thanks.

hi me again

Hi you

Zyxer: how it is going on there ?

Somewhat worried. Apparently my CPU model, I got it second hand, had a design "flaw" that only appeared in the future. Causing cores to fail. Looking it up but it seems to be caused by overheating due to stock coolers.

Sorry about that is it something with kernelspace ?

That we can fix

I got it watercooled and it wasn't used that much in the past due to that the guy that gave it to me couldn't use his PC, disk was working overtime and was hanging by a thread.

Nah, it was back in the day when ryzen 3600 was made the bottlenecks used to be GPUs

So the CPU never worked that hard, but paired with newer GPUs for gaming then the CPU might be the bottleneck, in any case it gets way hotter than it should

got it

Now that I think about it the most powerful GPU this CPU was paired with has most likely been an RX580. I should have nothing to worry about

I am using it for game dev on freeBSD

Gonna make the easy to run games for as many platforms as practical. Meaning Linux, windows, and whatever else godot runs on (FreeBSD for example, which my PC runs on)

Which engine do you run for writing games ?

Godot

It is under the MIT license.

The main reason I picked it. Then others said it was good choice for beginner, and thought I had put more thought into it than I had.

yes Godot is a Free Software

Is this good for compiling? AMD Ryzen 9 5900X

I haven't really kept up with the modern hardware for the past like, 2 years

Nah I shouldn't find out, I don't need to upgrade my CPU

I'm not sure

I don't know

bugs.freebsd.org/bugzilla/show_bug.cgi?id=275586 o_0

Title: 275586 – Undocumented feature of ifconfig UP

where are the files for pkgs stored online? i wanna look at rc files for pkgs i don't have installed

tykling: huh.

polyex: cgit.freebsd.org/ports/tree

Title: ports - FreeBSD ports tree

cgit.freebsd.org/ports/tree/www/caddy so where's the rc file it installs so it can start up automatically?

Title: caddy « www - ports - FreeBSD ports tree

polyex: cgit.freebsd.org/ports/tree/www/caddy/files/caddy.in

Title: caddy.in « files « caddy « www - ports - FreeBSD ports tree

ty! i was expecting a certain filename but that was dumb i guess

tykling: I encountered this behaviour very accidentally many ages ago on a terminal that had capitals displayed only, but I forgot which flavour of *NIX that system ran

was very puzzled but then saw resolver logs

(this was in 1992 or 1993, with a laboratory machine at Panasonic)

fbsd 14 seems lame, going for 15 today

vlc: What

gonna install FreeBSD 15 right now

or should i just go for FreeBSD 14 with latest repos?

Filthy casual, I am already on FreeBSD 16 pre-alpha

i haven't dared to update my 13 to 14, because of all the commotion that came with the update

My main rig is on 14 I think, I just got the current ISO. Laptop is on 13

SKull: this one helped me a lot on several boxes: ozgurkazancci.com/freebsd-13-2-upgrade-to-14-0-proper-and-correct-way

Title: FreeBSD 13.2 upgrade to 14.0 – properly detailed and (hopefully) correct way – Özgür Konstantin Kazanççı | Blog

tercaL: is all that really necessary? as far as i know it's enough to just make sure that my 13 is actually up to date before upgrading

there a guide showing how to turn our bin into a freebsd pkg so ppl can pkg install foo?

atm i just got a bin and the rc file

polyex: i might be wrong here, but i think all you have to do is make a proper port for it. there's a guide on freebsd.org in the documentation section on how to do it

polyex: and if your bin is running fine on freebsd, there's not much work involved

source: i went over the porter's guide once, while i was on the loo ^^

ty

/join ##news

polyex: you don't turn a binary into a pkg usually, you turn your source code into a port

see the porter's handbook docs.freebsd.org/en/books/porters-handbook

Title: FreeBSD Porter's Handbook | FreeBSD Documentation Portal

Hi! Now that we have 14.0, how "safe" it is to upgrade without a clean install from 13.2? This is my first major upgrade in FreeBSD.

working great for me fwiw

just remember that the version number means number of hours needed for the upgrade </s>

jvl: :D

yuripv: i.koumakan.jp/2023-12-07/1701952851.png my issue was almost definitely fixed \o/ two days with no spikes at periodic run time

Remilia: Congrats, happy for you. And how? :)

With latest ERRATA patches?

I mentioned it yesterday

and the day before I think when -p2 came out

Remilia: Sorry, I guess I missed, what was the reason/fix?

Lastly, I think you filed a bug report - no?

I did not

mvee: may I recommend using your status window for administrative commands? If the channel is more active, a message like that can sometimes be mistaken for channel advertising.

s/administrative/client/

It also has the practical benefit of making it much less likely that you leak passwords if you make a mistake ;)

/oper being done incorrectly has a long and sordid history on IRC, and even /nickserv and /auth commands can be abused if leaked by accient.

Upgrading FreeBSD from 13.2 to 14, on a box of mine, caused package removal of: mariadb-server/client.. Weird.

"cat /var/log/messages | grep maria" lists;

Dec 7 13:57:41 arshiv pkg[26561]: mariadb105-client upgraded: 10.5.21 -> 10.5.23

Dec 7 13:57:42 arshiv pkg[26561]: mariadb105-server upgraded: 10.5.21 -> 10.5.23

Dec 7 15:05:51 arshiv pkg[94177]: mariadb105-server-10.5.23 deinstalled

Dec 7 15:05:51 arshiv pkg[94177]: mariadb105-client-10.5.23 deinstalled

The thing is, FreeBSD 14 (amd64) doesn't has version 10.5.23 at all?

Package conflict

"pkg search maria" lists mariadb105-server-10.5.21

There's some way to detect conflicts through the ports tree, but I can't remember right now..

debdrup: I see. I use only packages, no ports at all. But yes, the packages are compiled from the ports I guess.

I have no idea, if FreeBSD 14 doesn't has mariadb-server version 10.5.23 at all, how come it states: mariadb105-client upgraded: 10.5.21 -> 10.5.23

Luckily, I had /var/db/mysql folder still there and I (re)installed mariadb105-server-10.5.21, had no data loss..

Does the default FreeBSD install of ZFS enable compression? Anyone done an install lately?

tercaL: packages are built from ports

dvl: According to zfsprops(7), compression defaults to on, which if memory serves means lz4.

I have fallen into pressure: reviews.freebsd.org/D42961 - update newsyslog.conf and remove compression by default

Title: ⚙ D42961 Do not compress log files

tercaL: pkg should (and has never, in my experienced) touched user-created or user-edited files.

dvl: would it be better to add a commented out include (in addition to the ones already there), that people can remove the octothorpe from to have them work? That way it wouldn't affect UFS systems which has no compression, but would still make it very easy for anyone on ZFS to enable it. It also nips any bikesheds in the butt.

debdrup: Sounds nice. Please comment.

I was just about to ask if I should add that as a comment instead :D

debdrup: I am aware of UFS still in use. I have not forgotten that. Now it's just a matter of choice: which group needs to modify /etc/newsyslog.conf for their needs?

dvl: since lz4 has an early abort, it won't actually try to recompress the already-compressed rotated logfiles, so by that logic I think it makes sense to not change it - but I can also see the sense in enabling it by default since ZFS is probably the default for most folks unless they know what they're doing and want what UFS offers.

debdrup: This is not about not compressing. This is about having the same extension and format on all the logs.

debdrup: not having to use bzgrep on some logs and grep on the others. It's a quality-of-life thing, not a save-space and time thing.

Hmm, that's a point I hadn't considered, and a good one.

That makes me wonder if zless/zgrep works on compressed files, though.

It does.

I mean, it would, since it's just a shellscript that wraps src/usr.bin/less/lesspipe.sh

obrien@ did it the right thing back in 2003

That's a name I've not heard in a long time.

git blame seems to think he is, though.

dvl: he's been around on efnet a little bit

iirc

Gah, git is so...unintuitive...sometimes :/

_xor: I've come to like it after a while. Took a while.

Yeah, I mean once you're used to it. I tend to use git or fossil and used to use cvs/svn/perforce, so muscle memory makes me reach for intuitive commands at which point git laughs at me.

Like, you would think there's a simple command to determine if the working tree is dirty, right?

Dirty as in, has untracked/changed/deleted files. I need to get that status from a script.

So far, I've found several ways, each with variable levels of reliability. The leading contender so far is, "git update-index --really-refresh && git diff-index --quite HEAD"

Hello, a hardware question: I'm running 13.2 on a dell precision 7560 ( bsd-hardware.info/?probe=5d3e6e3bd4 ). I have a Dell WD19DCS 240W docking station (which is the recommended one for this laptop). I'm hesitating about hardware support - I don't care if something doesn't work, but I'd like to be sure that there is no risk of frying my laptop if I plug it in ^^ - can anyone confirm me that there is no such risk?

Title: HW probe of Dell Precision 7560 #5d3e6e3bd4

When you need an argument with the name "--really-refresh", it makes me cautious of design decisions :P

hm, trying to decide if that is better or worse then some compilers having -Ofast which should be named -Obroken-but-maybe-slightly-faster-than-3

We have a new contender: `local _out="$(git status -s)"` and then checking if _out is empty or not.

heh, had forgotten to start with 'screen'

Lol

One column for "Can boot from..." is named "Zip", but it turns out they're talking about IOMega Zip drives, not zip files.

I still have some of those Zip disks and the drive

_xor: I think you can only boot off the IDE version

not the more widespread parallel port one

(obviously)

jupiter_: I do not think you can fry your laptop by using that so-called docking station

it uses USB Power Delivery

we have these at work, using them with Lenovo laptops

(which means 90W only but that is enough for office software)

Ok thanks for the feedback ^^ - I take it those laptops from work also run FreeBSD. I'll wait a few more hours just to see if no negative feedback and will give it a try tomorrow night if none ^^

jupiter_: no they run Windows but it does not matter

you can literally plug that 'docking station' into a powered-off laptop and turn it on

I thought there might be some kind of driver supervising the charging through USB

I am not sure if they just do USB or full on PCIE passthrough but basically even on Windows boot loader stage (Bitlocker PIN) you could use the keyboard

no, USB Power Delivery is hardware

it does not use drivers

it can tell the OS that there is not enough wattage though

ok nice, if it's hardware then there should be no risks indeed (dell pc with their own recommended docking station)

for example when you plug that Dell thing into a Legion 5 and turn it on without the stock brick, which means 90W limit (Dell things only do 240 with Dell)

you get the BIOS complaining 'this is not enough to charge at full power'

there are many ways to fsck up USB-PD, like Nintendo did

jupiter_: just plug it in *before* powering the laptop on and you will see the charging LED light up

yes, that's why I wanted to check here if any experience ^^ - will plug in before powering up

jupiter_: it supports hot plug of course, I am just telling you how to check that it needs no drivers

dvl, (debdrup) Something to think about is that for a zfs user compressed logs don't hurt anything and have been the status quo. For ufs users uncompressed logs consumes more disk space and can fill up the disk, which does hurt them, unless they know to change back to compressing them.

anyone know how to set the cursor for X? My old trick of xsetroot -cursor_name left_ptr is not working. if I run lxappearance, it get's set though and works.

rwp: Good points. I understand the UFS concerns. My reasoning is not one of space of usability. A quality-of-life issue, perhaps. I guess it is based around not wanting to use bzgrep to review old logs and grep to review the current logs. Mind you, bzgrep works on messages and messages.0.bz

rwp: there are great point on both sides. I realize how contentious this is.

dvl: it's a good reason to open it as review then (and post it) to get the feedback

also @ [14:55:33] <tercaL> The thing is, FreeBSD 14 (amd64) doesn't has version 10.5.23 at all?

I am not sure what that means because the Makefile for mariadb105-server has "PORTVERSION= 10.5.23"

though I do not think I have built 10.5 recently since there was 10.6 and now 10.11

maybe quarterly has not been built yet

Freshports says 10.5.23 - 28 Nov 2023 09:28:34

arstechnica.com/security/2023/12/ju…ble-to-new-logofail-firmware-attack lol, said Yae Miko. lmao.

Title: Just about every Windows and Linux device vulnerable to new LogoFAIL firmware attack | Ars Technica

this is amazing

anyone who ever had ImageMagick could have expected this

i always thought it was imagemagik

hmm?

ASUS boot logo is ASUS In search of incredible

cringe

RedVWnoseatbelt: unfortunately, it's magick

magick is an actually existing word unlike magik (if we limit scope to English)

Remilia: Did Asus found yet? 8-)