00:36:31 <jaredj> cpet "shared-ip" as against "VNET"
00:39:39 <cpet> "ok"
00:49:42 <cpet> jaredj: if you only have 1 IP you can setup the jails with internal IPS and use rdr with pf
00:55:08 <specialbomb> I see we are still whining about pkgbase hehe
00:55:28 <LXGHTNXNG> whining will continue until morale improves
00:58:38 <cpet> specialbomb: thats just polarian being polarian
00:59:02 <specialbomb> I gathered!
01:02:15 <cpet> specialbomb: some people tend ot think change is bad
01:05:04 <specialbomb> david bowie - changes
01:06:46 <cpet> specialbomb: if the creator of freebsd-update hates it
01:06:53 <cpet> specialbomb: then why continue to use freebsd-update ?
01:08:32 <specialbomb> im all for basepkg honestly, as long as theres proper handling of the transition
01:08:50 <specialbomb> and I trust the freebsd team and community, so im not worried :)
01:11:43 <cpet> im not against it either i just wont use it until the first .1
01:14:35 <JetpackJackson> I think it's neat
01:20:05 <cpet> JetpackJackson: you think air is neat
01:20:06 <cpet> heh
01:21:39 <JetpackJackson> Lol
01:25:18 <cpet> JetpackJackson: look at the birdies..
01:25:31 <kerneldove> 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
01:33:33 <LXGHTNXNG> no
01:39:59 <cpet> kerneldove: that is still possible
01:40:15 <cpet> kerneldove: now normally you would delte a meta port and then do pkg autoremove
01:40:27 <cpet> that shouldn't touch the freebsd-\* stuff
01:45:11 <JetpackJackson> cpet: I like birds
01:49:05 <cpet> JetpackJackson: are they neat ?
01:49:13 <JetpackJackson> Yes
01:50:47 <cpet> JetpackJackson: hah
04:41:42 <SymbioticFemale> iwlwifi doesn't have hostap support?
04:49:27 <cpet> SymbioticFemale: nope
05:00:02 <cpet> 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.
05:51:31 * cpet works on mesen2
05:55:47 * cpet has forgotten how many ports he maintains
06:03:22 <rtprio> how often is it more than just bump the version and `make checksum`
06:03:38 <cpet> with emsen
06:03:41 <cpet> er mesen
06:03:46 <cpet> little more than that
06:04:05 <cpet> playing with emulatirs you hve to play with asm and all that cool stuff
06:05:03 <cpet> issue is mesen 2x moved to .net
06:05:15 <cpet> and pretty much anyone in the oss world dislikes anything MS
06:05:58 <cpet> but I like to play my occasional fzero and secret of mana so
06:13:17 <cpet> it would be nice if the people behind zsnes would upgrade/port/migrate to 64bit
10:22:04 <Remilia> rwp: did you manage to fix your pkg so that it can update FreeBSD-base packages automatically?
10:29:34 <ant-x> cpet, I vaguely remember I used to run ZSNES for DOS to play /Clock Tower (1995)/ inside DOSBox-X for pixel-perfect display...
10:31:54 <ant-x> Otherwise, ZSNES, as well as many other emulators, has no pixel-perfect integer scaling.
12:47:27 <dch> 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
12:47:46 <dch> the appropriate people are already aware
12:47:50 <dch> https://github.com/freebsd/pkg/issues/2575#issuecomment-3665875154
13:06:17 <JetpackJackson> Oh I was wondering what that was
13:15:58 <tinman> :1
13:37:43 <angry_vincent> someone told me that pkg-2.5.0 fixed
13:49:19 <SpaciousCoder78> is there some kind of a preconfigured VM image for freebsd that requires minimal setup?
13:59:09 <[tj]> the ones on the download page
13:59:22 <[tj]> they require 0 set up other than your vm host
14:09:14 <polarian> cpet: are they at least making it optional?
14:09:24 <polarian> or is bsdinstall going to be deprecated along with freebsd-update and later removed?
14:09:40 <polarian> oh wait they wouldnt be able to remove bsdinstall because what about servers
14:10:23 <polarian> SpaciousCoder78: never going to shut me up, never going to take me down :p
14:10:43 <SpaciousCoder78> ?
14:10:52 <polarian> I am responding to the backlog, apologies
14:11:33 <SpaciousCoder78> yeah but where did I come from for that message?
14:11:37 <SpaciousCoder78> wrongly tagged me?
14:44:39 <polarian> SpaciousCoder78: yeah
14:44:41 <polarian> sorry
14:44:50 <polarian> specialbomb: was the person I was meant to ping
14:45:04 <polarian> both your nicks start with "sp" so it must have autocompleted to yours
14:45:08 <polarian> apologies
14:45:37 <SpaciousCoder78> ah no problem
16:28:09 <luna> downloading 15 now
16:35:02 <knidos> set unread
16:35:48 <polarian> rm: /usr/local/jails/containers/mongodb/lib/libthr.so.3: Operation not permitted
16:35:50 <polarian> tf?
16:35:56 <polarian> rm -rf as root doesn't work?!!??
16:36:12 <polarian> (deleting a jail)
16:36:23 <polarian> the jail isnt running btw
16:36:25 <polarian> jls is empty
16:37:03 <CrtxReavr> polarian, ls -lo /usr/local/jails/containers/mongodb/lib/libthr.so.3
16:38:56 <polarian> -r--r--r--  1 root wheel schg,uarch 128128 31 May  2024 /usr/local/jails/containers/mongodb/lib/libthr.so.3
16:39:03 <polarian> read-only shouldnt matter with -f
16:39:23 <polarian> the rest of the jail deleted just fine
16:39:51 <CrtxReavr> polarian, chflags noschg /usr/local/jails/containers/mongodb/lib/libthr.so.3
16:39:59 <CrtxReavr> (And yes, it does matter.)
16:40:31 <polarian> CrtxReavr: whats schg
16:40:45 <CrtxReavr> the opposite of schg
16:40:49 <polarian> no shit...
16:41:08 <polarian> Catty: what does it stand for
16:41:14 <CrtxReavr> chflags(1)
16:41:23 <polarian> immutabilitty
16:41:48 <CrtxReavr>            schg, schange, simmutable
16:41:48 <CrtxReavr>                        set the system immutable flag (super-user only)
16:41:49 <polarian> its fine anyways I forgot the dats is on a zfs volume
16:41:53 <polarian> so I can just delete that
16:42:04 <CrtxReavr> immutable = you can't change it
16:42:06 <polarian> anyways thx CrtxReavr
16:42:09 <polarian> yes I know what immutable means
16:42:20 <polarian> little offensive you assumed I didnt :/
16:42:30 <CrtxReavr> Well, you wanna argue. . .
16:42:58 <CrtxReavr> Stop your feet and proclaim your root privledge.
16:43:13 <CrtxReavr> stomp
16:44:33 <CrtxReavr> I assume 'schg' is literally short for 'system change,' that's not mentioned in the manpage.
16:44:34 <polarian> ...
16:44:36 <polarian> what?!?!?
16:44:50 <polarian> I dont want to argue though!?!?
16:44:52 <polarian> I am confused
16:45:02 * CrtxReavr sighs.
16:45:50 <mzar>  system immutable flag
16:46:25 <CrtxReavr> Yes. . . but 'schg' by itself doesn't convey that.
16:46:41 <mzar> it's very proficient flag
16:47:55 <mzar> in the past this flag was set on many files, including the kernel
16:48:10 <mzar> now, it's only for the few
16:48:36 <polarian> mzar: why?
16:48:43 <mzar> simplification
16:48:55 <polarian> I dont see how a few libs require immutability
17:18:51 <rwp> 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.
17:19:32 <rwp> 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.
17:20:14 <rwp> polarian, Remove all flags, -x don't cross file systems (for safety), -R recursively: chflags -xR 0 /jails/sys1
17:20:43 <rwp> 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 {} +
17:21:20 <polarian> it seems the files copied just fine its just that mv cant remove the file after moving because immutable
17:21:21 <rwp> 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.
17:21:29 <polarian> plus I was going to installworld for -p1 anyways
17:21:31 <polarian> soooooooo
17:21:34 <polarian> it didnt really matter anyways :p
17:22:20 <rwp> Immutable files copy just fine.  That should not be surprising.  One just can't remove them, due to them being system-change immutable.
17:23:58 <polarian> yeah
17:24:16 <polarian> depends on the impl of mv though
17:24:32 <rwp> Hmm...  How?  Please say more.
17:24:36 <polarian> well *could*
17:24:48 <polarian> I assumed mv would just outright refuse to move the file as its immutable
17:24:55 <polarian> but it effectively did a cp
17:25:05 <polarian> mv could be written to check chflags for schg
17:25:15 <polarian> that is what I meant :p
17:25:48 <rwp> mv is not going to call either chflags or chmod!  Please save me from that sight!
17:27:23 <rwp> 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.
17:29:47 <polarian> rwp: :)
17:29:50 <polarian> just saying you *could*
17:29:52 <polarian> impl it that way
17:29:57 <polarian> its possible :p
17:30:21 <polarian> maybe I should impl this and submit it for review just to make rwp cringe :p
17:30:40 <rwp> 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.
17:31:51 <rwp> 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.
17:42:52 <ghodawalaaman_> Hello o/
17:43:27 <ximon> when I install rstudio in freebsd
17:44:13 <ximon> can rstudio send then outgoing attacks on my network?
17:45:24 <skered> How are there not more CVEs filed against openresolv?
17:45:55 <polarian> skered: why do you want there to be cves against openresolv
18:54:25 <polarian> err what is the process to getting old issues closed if they are no longer relevant
18:54:27 <polarian> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209479
18:54:29 <polarian> for example
18:54:36 <polarian> its left open but the page doesn't even have a nat rule in it anymore
18:54:42 <polarian> and its been dead since 2016
19:13:14 <skered> over come by events
19:13:15 <skered> I think
19:19:43 <polarian> also dch the pkg error yesterday I believe was due to the rename of the pkg repo
19:20:01 <polarian> its not -ports and -ports-kmods
19:20:03 <polarian> now*
21:52:26 <rtprio> do i need lib32 packages for any reason?
21:53:53 <skered> Do you run any 32-bit software?
21:59:08 <rwp> 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.
22:06:41 <ant-x> Such as running 32-bit Windows programs with Wine.
22:14:55 <rwp> How many people installing FreeBSD using the installer iso will be running 32-bit Windows under Wine?
22:15:57 <rwp> 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.
22:22:03 <polarian> rwp: does it hurt to have them?
22:22:05 <polarian> lol
22:22:21 <polarian> you can always fork the freebsd src and remove them yourself
22:23:19 <rwp> 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.
22:23:48 <rwp> I don't need to fork the source.  I already don't have them.  I uncheck the install box for them at install time.
22:39:25 <ant-x> I agree with rwp in that it is bad to have /anything/ installed and not used.
22:39:30 <polarian> rwp: you shilling pkgbase again
22:40:22 <rwp> polarian, I haven't actually ever tried pkgbase yet.  It's on my very long task list to do at some point though.
22:40:49 <polarian> rwp: of I forgot lib32 was in the sets
22:40:52 <polarian> heh
22:40:53 <polarian> nvm :p
22:41:16 <polarian> I am pretty sure installworld installs all sets
22:42:21 <polarian> I wonder if theres a way to customise what installworld installs
23:36:13 <Matt|home> o\