is anyone on here who manages the website? i'm wondering if maybe we could freshen up the home page a bit. mock up using mkdocs: freebsd.markmcb.com

anything more responsive would be nice, this is just a quick mock up

markmcb: you forgot the beastie artwork...

also the original contains a brief about the operating system which is crucial IMHO

haha, i knew someone would mention the missing graphic

that web page you made would be fine in freebsd.org/where

it's a copy of the existing home page, with minor additions

but the content isnt the focus, more the useability

the existing site doesnt resize well and is micro sized on mobile

then fix that

i did, lol

this is a responsive template

no you did reworked the front page

i get it, nostalgia ranks high

im sure you can just adjust css for the current webpage so it fits better on mobile

-> freebsd.org/css/fixed.css

maybe create a new one? :D

voy4g3r2, multiple mount= lines does appear to work for me; all after the first must be += of course

is there anything that would render a vnet jail incapable of pinging 127.0.0.1, with the message "permission denied"?

missing permissions to use raw sockets?

nimaje, i did enable those, if I'm not mistaken

possibly fork nonsense then

MelMalik: ipfw/pf with default drop?

ipfw is in use at host level; however behaviour didn't change when I added a low-numbered rule with "allow ip from any to any"

you added that in the jail, right? not on the host

i will have to try that next.

thanks for the hint.

in unrelated news I am now rebooting the host machine to do an acceptance test of the configuration I have put together..

on that note: the firewall was misconfigured :')

i have a lot of misluck with firewalls

ivy, it would appear there was a deny rule in ipfw in the jail; unfortunately /etc/rc.d/ipfw does not run inside of a jail so I am going to have to do some hacks (assuming that I can even use the ipfw tools)

can you not just enable ipfw the normal way (in rc.conf)? i don't use ipfw but that works with pf

rc.d/ipfw is nojailvnet which means it should run in a vnet jail

i tried service ipfw start and it complained about a kernel module; I suspect that adding `sh /etc/rc.firewall` to /etc/rc.local will have to do for now

if you have ipfw loaded and it's complaining that it's not loaded, that sounds like a bug

(the way this is meant to work is that if you have the module loaded on the host, or it's in the kernel, it won't try to load it in the jail)

ok so I think we have found the point where it's fork nonsense; in HBSD kldstat doesn't work in gaols

now I need to go open a window, holy hell it's hot in here

ok, so it is a bug, just not in freebsd :-)

working as intended, but creates bugs downstream. so, yes. as a workaround, as I said, I have put sh /etc/rc.firewall into rc.local.

hm, but you can observe some kernel modules being loaded in some other way, so is there really a point to hide these? especially if there is a reason to use them in a jail? how about a whitelist approch, where a module can be declared useable in a jail and then kldstat reports it?

p'rhaps

I might give that a shot in my own fork of the fork at some point. Or modify the script to detect ipfw by other means, as I'm weird that way

any idea if the forum is having issies ?

issues *

hello!

the pixman port is currently outdated (latest stable release is 0.46.0), where should I properly report this?

badkat: i made it more "as-is" freebsd.markmcb.com

i find it interesting that the foundation has branding guidelines and the project site ignores them, e.g., fonts, logs, etc.

bitblt: You should report this in either ports@ on the mailing list or on bugs.freebsd.org (especially if you can provide a patch update.)

ek: I see that here cgit.freebsd.org/ports/tree/x11/pixman/Makefile the maintainer is listed as x11⊙Fo, maybe this is a more appropriate email?

bitblt: Yes. You can email them directly and bring it the issue. However, that is also just a dev group for X11 on FBSD. Not a singular person.

If you can patch and test the updated version and provide that info, that will certainly get their ears perked up, though.

I generally find it easiest to create a PR on bugs.freebsd.org, and then email the maintainer address to let them know about it.

I'm not directly a user of freebsd, but a project that I currently contribute to (wlroots) has a freebsd CI, that currently needs the latest pixman port to pass :)

This way things can be easily tracked via Bugzilla as opposed to email.

I'll try to make the version bump myself, I'm just trying to find the correct way to report/communicate this

I also found this mailing list: lists.freebsd.org/archives/freebsd-x11

bitblt: there isn't really a way to report an out of date package other than mailing the maintainer (the list, in this case), if you do decide to update it yourself then you need to open a PR on bugzilla, the porter's handbook describes how to do that

Is freebsd-x11⊙Fo a different group from the x11⊙Fo?

The correct way is bugs.freebsd.org ports PR.

bitblt: x11@ and freebsd-x11@ should be associated with the same group.

thank you

how can I (from CLI) determine if there is a new freeBSD release to be used with freebsd-update upgrade -r .... ?

guntbert: freebsd-update fetch

will output:

No updates needed to update system to 14.2-RELEASE-p3