01:38:09 <aesthetikx> Assuming I have an IIC trackpad, how would I be able to verify that?
01:38:44 <aesthetikx> In short, it doesn't work (tried iichid, synaptics, moused, etc etc) but I want to be able to at least identify the make and model of the trackpad so that I can research it more, or look at a driver.
02:04:10 <sig`> dmesg
02:04:43 <sig`> aesthetikx: using x11?
02:17:27 <V_PauAmma_V> If dmesg (or "less /var/run/dmesg.boot") doesn't give any hint, you could also try "i2c -vs".
07:02:49 <nwe> good morning, I looking to by a new laptop and wondering how is the support for FreeBSD on ThinkPad X1 Carbon Gen 13 ?
11:21:05 <divlamir> nwe: you might have a look here, search for individual devices, like wifi, etc... https://bsd-hardware.info/
11:24:03 <divlamir> I've never had one of those heterogenous cores Intel CPUs, sounds too messy. How is FreeBSD dealing with that?
15:11:14 <vhBEYjqK4f> hello ?
15:20:46 <ivy> hello
15:24:39 <V_PauAmma_V> They left.
15:26:58 <ivy> well, bye
15:34:00 <mzar> no ALPHA3 yet?
15:35:00 <ivy> mzar: the build was meant to start at 6AM UTC today, i'll see if Colin has an update when he's around
15:36:19 <mzar> no problem for me, but I believed it's automated at least by at(1) pushing the commit ;-p
15:42:18 <kevans> no, this is a manual process (to kickoff, at least)
15:43:01 <ivy> we're talking about the actual release, right?  the pkgbase builds for pkg.f.o are automated, but the release builds are manual
15:45:41 <kevans> yes, pkgbase builds are automated, snapshot/release builds are all manual kickoff
15:46:30 <kevans> (and there's no alpha3 until re@ pushes the name change commit)
15:53:39 <mzar> yep
16:02:47 <ivy> i really want to add an rm(1) flag to unset noschg if it's set
16:02:53 <ivy> like super -f
16:14:23 <CrtxReavr> ivy, step away from the rm(1) src.
16:15:25 <ivy> CrtxReavr: would you object to that change?  it wouldn't be enabled by default or by -f, it would be a new flag
16:15:42 <mquin> --yes-i-really-mean-it
16:16:06 <CrtxReavr> https://en.wikipedia.org/wiki/Unix_philosophy#Origin
16:16:27 <ivy> CrtxReavr: if this is a "unix philosophy" issue, we should also remove -f, since you can do the same thing with chmod
16:16:47 <ivy> mquin: i believe, according to POSIX.1, this should be spelled "-Wyes-i-really-mean-it" :-)
16:16:59 <ivy> or did they ditch the -W thing?
16:17:26 <CrtxReavr> -f overrides permissions.
16:17:44 <CrtxReavr> chflags modifies flags, which are an entirely different filesystem feature.
16:18:30 <ivy> -f overrides permissions, which you can also do with chmod.  --fix-the-schg-thing would override flags, which you can also do with chflags.  what's the difference?
16:18:52 <ivy> both are simply attributes of files which already have utilities to manage them
16:29:09 <V_PauAmma_V> Isn't chflags restricted to securelevel <= 0 or something?
16:29:47 <ivy> yes, but that's the default and is what most users use.  if you increased securelevel you'll just get an error, same as -f as a non-root user
16:30:02 <ivy> actually the default seems to be -1, but either way
16:37:13 <CrtxReavr> V_PauAmma_V, also that.
16:39:23 <ivy> mzar: <fbsdslack> <cperciva> ivy: ALPHA3 is coming as soon as I manage to head main to build
16:42:24 <mzar> no rush, let the release process run undisturbed
16:42:51 <divlamir> hm, immutable stuff is meant to be *difficult* to change
16:43:47 <mzar> that will be really really sad if we can override schg with rm option, regardless to securelevel
16:44:12 <mzar> but yes, it can happen
16:45:18 <mzar> I am only a user, and this OS is driven by committers
16:45:49 <mzar> so perhaps some users will appreciate and use new rm option
16:46:33 <mzar> or maybe multiple -f
16:46:38 <mzar> like -fff
16:46:43 <mzar> rm -rfff /
16:47:10 <ivy> i think that's a bad idea, because if you do something in a script like "RM='rm -f'" and then later do "$RM -f /some/file", it will change the behaviour in a surprising way
16:47:48 <mzar> the whole idea isn't IMHO good, but rm -rfff / looks cool
16:47:49 <divlamir> hope you don't have a twitchy inde xfinger
16:48:46 <divlamir> or fall asleep with your hands over the keyboard like me the other day XD
16:49:01 <mzar> if you script it, you can run rm -rf || chflags -R  .. && rm -rf
16:49:03 <kevans> i think you just want to spam a number of 'f' that 'feels right'
16:49:12 <mzar> it's still doable
16:49:15 <kevans> gate it on -fffffffff
16:49:28 <mzar> that's even better
16:49:31 <divlamir> and then prompt twice
16:49:47 <divlamir> and then just use chflags bcs rm is so annoying
16:51:06 <ivy> fwiw, the use case for this is that i frequently do something like "pkg -r /tmp/test install freebsd-set-base; rm -rf /tmp/test; pkg -r /tmp/set install freebsd-set-base" and currently this doesn't work because you need to chflags first
16:52:02 <divlamir> easy to make a wrapper