cpet "shared-ip" as against "VNET"

"ok"

jaredj: if you only have 1 IP you can setup the jails with internal IPS and use rdr with pf

I see we are still whining about pkgbase hehe

whining will continue until morale improves

specialbomb: thats just polarian being polarian

I gathered!

specialbomb: some people tend ot think change is bad

david bowie - changes

specialbomb: if the creator of freebsd-update hates it

specialbomb: then why continue to use freebsd-update ?

im all for basepkg honestly, as long as theres proper handling of the transition

and I trust the freebsd team and community, so im not worried :)

im not against it either i just wont use it until the first .1

I think it's neat

JetpackJackson: you think air is neat

heh

Lol

JetpackJackson: look at the birdies..

was pkg and pkgbase cmds separated? seems pretty smart because there was some confusion when it's all through pkg. like deleting all pkg's wiping the base OS lol

no

kerneldove: that is still possible

kerneldove: now normally you would delte a meta port and then do pkg autoremove

that shouldn't touch the freebsd-\* stuff

cpet: I like birds

JetpackJackson: are they neat ?

Yes

JetpackJackson: hah

iwlwifi doesn't have hostap support?

SymbioticFemale: nope

Questions about development roadmap etc. are not suited for the bug database. There is no published timeline for adding hostap support to iwlwifi. The freebsd-wireless mailing list would be an appropriate place to discuss this work, priorities, alternate drivers, collaboration, and so on.

how often is it more than just bump the version and `make checksum`

with emsen

er mesen

little more than that

playing with emulatirs you hve to play with asm and all that cool stuff

issue is mesen 2x moved to .net

and pretty much anyone in the oss world dislikes anything MS

but I like to play my occasional fzero and secret of mana so

it would be nice if the people behind zsnes would upgrade/port/migrate to 64bit

rwp: did you manage to fix your pkg so that it can update FreeBSD-base packages automatically?

cpet, I vaguely remember I used to run ZSNES for DOS to play /Clock Tower (1995)/ inside DOSBox-X for pixel-perfect display...

Otherwise, ZSNES, as well as many other emulators, has no pixel-perfect integer scaling.

the SQLITE error reported yesterday during `pkg update` that hit 15.0-RELEASE amd64 /latest/ pkg repo, is present on 14.3-RELEASE amd645 /latest/ also

the appropriate people are already aware

Oh I was wondering what that was

:1

someone told me that pkg-2.5.0 fixed

is there some kind of a preconfigured VM image for freebsd that requires minimal setup?

the ones on the download page

they require 0 set up other than your vm host

cpet: are they at least making it optional?

or is bsdinstall going to be deprecated along with freebsd-update and later removed?

oh wait they wouldnt be able to remove bsdinstall because what about servers

SpaciousCoder78: never going to shut me up, never going to take me down :p

?

I am responding to the backlog, apologies

yeah but where did I come from for that message?

wrongly tagged me?

SpaciousCoder78: yeah

sorry

specialbomb: was the person I was meant to ping

both your nicks start with "sp" so it must have autocompleted to yours

apologies

ah no problem

downloading 15 now

set unread

rm: /usr/local/jails/containers/mongodb/lib/libthr.so.3: Operation not permitted

tf?

rm -rf as root doesn't work?!!??

(deleting a jail)

the jail isnt running btw

jls is empty

polarian, ls -lo /usr/local/jails/containers/mongodb/lib/libthr.so.3

-r--r--r-- 1 root wheel schg,uarch 128128 31 May 2024 /usr/local/jails/containers/mongodb/lib/libthr.so.3

read-only shouldnt matter with -f

the rest of the jail deleted just fine

polarian, chflags noschg /usr/local/jails/containers/mongodb/lib/libthr.so.3

(And yes, it does matter.)

CrtxReavr: whats schg

the opposite of schg

no shit...

Catty: what does it stand for

chflags(1)

immutabilitty

schg, schange, simmutable

set the system immutable flag (super-user only)

its fine anyways I forgot the dats is on a zfs volume

so I can just delete that

immutable = you can't change it

anyways thx CrtxReavr

yes I know what immutable means

little offensive you assumed I didnt :/

Well, you wanna argue. . .

Stop your feet and proclaim your root privledge.

stomp

I assume 'schg' is literally short for 'system change,' that's not mentioned in the manpage.

...

what?!?!?

I dont want to argue though!?!?

I am confused

system immutable flag

Yes. . . but 'schg' by itself doesn't convey that.

it's very proficient flag

in the past this flag was set on many files, including the kernel

now, it's only for the few

mzar: why?

simplification

I dont see how a few libs require immutability

I don't understand why the paranoia for those 14 files that they would need schg system-change immutable flag either. I don't think it is needed. But someone probably thought it would prevent accidents and so here we are.

Fortunately it is your system, and mine, and we can change that if we want. I repackage the base.xz without that flag so the jails I create do not have that flag set. Simplifies things.

polarian, Remove all flags, -x don't cross file systems (for safety), -R recursively: chflags -xR 0 /jails/sys1

And then one can rm -rf it. One can find and list all files with the schg flag set: find . -flags +schg -exec ls -ldo {} +

it seems the files copied just fine its just that mv cant remove the file after moving because immutable

And if someone does have a good explanation for why those 14 files are set to system-change immutable I would be interested in reading about it.

plus I was going to installworld for -p1 anyways

soooooooo

it didnt really matter anyways :p

Immutable files copy just fine. That should not be surprising. One just can't remove them, due to them being system-change immutable.

yeah

depends on the impl of mv though

Hmm... How? Please say more.

well *could*

I assumed mv would just outright refuse to move the file as its immutable

but it effectively did a cp

mv could be written to check chflags for schg

that is what I meant :p

mv is not going to call either chflags or chmod! Please save me from that sight!

mv has two modes of operation. If the source and destination are on same file system then it can call the rename(2) to unlink from here and link there atomically in the kernel. If the source and destination are on different file systems then one can't rename it to the new location and therefore mv will cp first and if that is successful unlink it from the source location.

rwp: :)

just saying you *could*

impl it that way

its possible :p

maybe I should impl this and submit it for review just to make rwp cringe :p

But if it did then that would be an irregular thing to do. It's not simple to do it that way. It is simpler if commands do small things individually.

non-root users don't have permissions to remove system-change immutable flags either. (They do for chmod file permissions.) So then one would need to deal with errors layered internally too.

Hello o/

when I install rstudio in freebsd

can rstudio send then outgoing attacks on my network?

How are there not more CVEs filed against openresolv?

skered: why do you want there to be cves against openresolv

err what is the process to getting old issues closed if they are no longer relevant

for example

its left open but the page doesn't even have a nat rule in it anymore

and its been dead since 2016

over come by events

I think

also dch the pkg error yesterday I believe was due to the rename of the pkg repo

its not -ports and -ports-kmods

now*

do i need lib32 packages for any reason?

Do you run any 32-bit software?

I always uncheck the install of the lib32 software. I can't imagine why it is checked for install by default. The number of uses of it must be vanishingly few.

Such as running 32-bit Windows programs with Wine.

How many people installing FreeBSD using the installer iso will be running 32-bit Windows under Wine?

I am not saying there are none. But are there enough to make it the default for everyone? Because certainly a FreeBSD user running 32-bit Windows under Wine would need to install /something/ to make work, right? In which case installing the 32-bit libs would be a very small incremental amount more.

rwp: does it hurt to have them?

lol

you can always fork the freebsd src and remove them yourself

Yes. Yes it hurts to have them. They consume disk space. They need upgrades along with everything else on the system. There is a security surface to having them installed. So yes, it hurts to have them.

I don't need to fork the source. I already don't have them. I uncheck the install box for them at install time.

I agree with rwp in that it is bad to have /anything/ installed and not used.

rwp: you shilling pkgbase again

polarian, I haven't actually ever tried pkgbase yet. It's on my very long task list to do at some point though.

rwp: of I forgot lib32 was in the sets

heh

nvm :p

I am pretty sure installworld installs all sets

I wonder if theres a way to customise what installworld installs

o\