04:00:16 <rtprio> wipt: what version? what panic
05:44:28 <Koston> are you sure your disks are ok
09:22:08 <kerneldove_> anyone know why server ram prices have tripled and wtf?
09:23:32 <Oks4> kerneldove_: slop generation
09:24:43 <kerneldove_> by slop you mean ai?
09:25:32 <Oks4> yes
09:25:46 <kerneldove_> fuckers
09:25:59 <kerneldove_> atleast ai makes search engines actually good
09:37:03 <SomeVisitor> by stealing information and presenting it as its own. Well …
09:48:27 <black1> SomeVisitor: that's a based statement
09:50:32 <nerozero> hi, sh scripting question
09:50:55 <nerozero> what does this line expected to do? ': ${resolvconf_enable="YES"}'
09:51:27 <nerozero> not understood the behavior of ":"
09:53:00 <nerozero> if this assumes some kind of default value - this had 0 effect in sh -c ': ${resolvconf_enable="YES"}; echo $resolvconf_enable;'
09:55:39 <ridcully_> nerozero: `:` can be used to fill an empty then-branch with if e.g.
09:56:58 <nerozero> I had similar feelings, but it has 0 effect while testing in sh -c ...
09:57:01 <ridcully_> i think this is somewhat of a no-op allowed allowed char
09:57:35 <nerozero> somevar="" sh -c ': ${somevar}="abc"}; echo $somevar;' - empty
09:57:48 <nerozero> somevar="blabla" sh -c ': ${somevar}="abc"}; echo $somevar;' -> "blabla" ...
09:57:54 <ridcully_> yes, this looks like a no-op to me
09:58:27 <ridcully_> `:` is something like `true` - it behaves like a command
09:58:28 <nerozero> sh -c ': ${somevar}="abc"}; echo $somevar;' - empty ....
09:58:39 <ridcully_> and i guess it eats or ignores the arguments?
09:58:40 <nerozero> ah this is something like test ?
09:58:48 <nerozero> but there is [] option ..
09:59:05 <nerozero> it is on line 315 in `/sbin/dhclient-script`
09:59:33 <nerozero> it follows the "case $reason in"
11:04:15 <cyric> nerozero: somevar="" SETS somevar to empty value; that construct would only work if somevar was not set at all
11:13:31 <nerozero> cyric, so this assumes that statement `:{var="defaultvalue"}` ?
11:14:01 <nerozero> if variable not defined nor empty - its set to the default value right ?
11:15:50 <cyric> yes, set to defaultvalue iff variable was not set at all
13:05:11 <ketas> i wonder how well newer thinkpad will work with fbsd now
13:38:17 <black2> ketas: as long as you stick with conventional hardware
13:38:26 <black2> things should be fine
13:47:41 <ketas> black2: the hell is unconventional hw?
13:49:04 <black2> ketas: imo things like touch-screen display
13:49:14 <ketas> i'm impressed that https://dmesgd.nycbug.org/dmesgd still works
13:49:59 <black2> and radio modems that require special drivers
13:50:21 <ketas> oh yeah, that hw
13:51:00 <ketas> don't you get both working somehow tho?
13:51:04 <ketas> esp the modem
13:51:58 <ketas> wifi would have issues too :p
13:51:59 <wipt> rtprio: newest release, 14.3R
13:52:53 <black2> ketas: you can't be sure. you don't want to have a laptop at hand that doesn't work with the hardware
13:53:16 <wipt> Koston: I had the assumption, but I haven't checked.
13:53:19 <black2> to ba on the safe side, prefer older models and generic hardware
13:53:50 <ketas> a touch one is rare in secondhand anyway
13:53:56 <ketas> tho cool
13:56:27 <black2> they trying to get the customers impressed with very stunning designs
13:56:42 <black2> but usually that device doesn't last very long
13:57:35 <ketas> some t should still be ok
13:57:37 <Reinhilde> :-(
13:57:42 <ketas> it could break anyway
13:59:25 <ketas> lol, stupidest error i just heard of laptop going bust is, didn't charge suddenly, so owner took usb c off and plugged back, immediately smoke and machine gone
13:59:33 <black2> the best choices out there imo are the rugged laptops that I assume can work for 10 years plus.
14:00:15 <ketas> well there's no exact need for those i guess
14:00:28 <black2> durability
14:00:44 <ketas> what where those metal briefcase panasonics
14:00:48 <ketas> saw one
14:00:53 <ketas> yes but
14:01:11 <black2> they have hot-pluggable batteries so...
14:01:12 <wipt> Koston: I should check, might make sense why I was having issues with getting the encryption to work
14:02:13 <wipt> My last newest machine was a rooted chromebook. $30 something on ebay, essentially a disposable machine.
14:02:51 <black2> wipt: yeah. these are very nice deals. if you have termux installed it's basically a working GNU/Linux machine
14:02:53 <ketas> that's bit weird hw and low perf last time i checked
14:02:56 <ketas> but yeah
14:03:06 <ketas> those are nice too
14:03:11 <black2> extra-long battery life is an advantage
14:03:18 <black2> 14 hr+
14:03:21 <ketas> yeah
14:03:28 <ketas> those were all arms?
14:03:31 <wipt> black2: https://docs.mrchromebox.tech/ changed the firmware/bios
14:03:49 <black2> well a few made by acer and samsung I believe are intel-based ketas
14:04:06 <wipt> ketas: most are x86
14:04:31 <black2> wipt: that's better. if you can get it rooted and flashed with what you want.
14:04:47 <wipt> just have to steer clear of the really low performance ones.
14:04:53 <ke8cqc> I'm very new to FreeBSD and have been spinning my wheels trying to get bluetooth to headphones working for several weeks.  I've googled around for tutorials, but nothing has worked.  The lasest tuturial I'm trying to follow is the first post in this conversation:  https://forums.freebsd.org/threads/bluetooth-audio-how-to-connect-and-use-bluetooth-headphones-on-freebsd.82671/  Everything works fine until I go to start the
14:04:53 <ke8cqc> Bluetooth stack ubt0 twice.  It fails both times.  Please HELP!!!
14:05:24 <black2> wipt: yeah but honestly if you just do text-editing and no compilation tasks most models'd suffice
14:06:19 <wipt> I already have an old netbook, wanted something for AV1 codec video for family videos
14:06:28 <ke8cqc> I will be more than happy to pastebin any info you want to look at.
14:07:04 <wipt> ke8cqc: doesn't hurt to pastebin and maybe someone will see it in a few hours?
14:07:32 <ke8cqc> wipt:  What command would you like me to pastebin?
14:07:58 <ke8cqc> ... or contents of what file???
14:08:05 <ketas> unsure where to point for the next bt audio user
14:08:58 <ketas> i'm surprised it works at all :p
14:09:14 <wipt> ke8cqc: I've never touched BT on BSD, took me some time to get it to work under linux...
14:09:18 <ke8cqc> Is FreeBSD bt like Linux bt?
14:10:12 <ke8cqc> wipt:  BT for headsets doesn't work in Linux.  It only works for file transferring.
14:11:23 <wipt> ke8cqc: I've been able to pair audio
14:11:31 <ketas> did it work?
14:11:49 <ketas> well obviously it works on something
14:11:55 <ke8cqc> wipt: ... on which OS???
14:12:10 <wipt> yeah. Just a pain on a dual boot machine, after you pair in in windows, and move to linux, you have to reset the headphones.
14:13:30 <ke8cqc> Honestly, I can live without the audio part.  I would at least like to get it working for file transfers between this machine, my other lappy, phone, and tablet.
14:13:30 <wipt> My daughter is watching a movie with a BT speaker being driven from a Debian Linux machine right now. Works fine.
14:13:49 <ke8cqc> I haven't run Debian in years.
14:15:06 <ketas> apart from few more t60's i could hack up working, i guess maybe ~200€ t4xx something is good, you have to find best batt/cpu/ram/condition combination
14:15:09 <ke8cqc> The only way that would happen on this machine is if I installed Debian in Virtualbox... and I'm not sure if that would work.
14:15:19 <wipt> It's been decent for a desktop. I ran BSD on the desktop when I was younger, I was a bit of a masochist
14:15:34 <ketas> are you still
14:16:21 <ketas> i mean who said you need to have only one os :p
14:16:22 <wipt> FBSD for my servers, ZFS to samba shares for everything else in the house.
14:16:39 <ketas> a nice wipthouse
14:17:00 <ke8cqc> I'll try back later after my Buckeyes spank some Nittany Lions and send them back to Happy Valley with their tails between their legs.
14:19:16 <ketas> i feel kind of sad, i got n.o.s. t60 and i like used it up apparently
14:19:49 <ketas> lasted over 10y :p
14:19:52 <ketas> i mean..,
14:22:53 <ketas> one fucked up thing i found was that screen hinges seize up on them
14:23:27 <ketas> in one i managed to break part of frame
14:23:47 <ketas> still haven't taken it apart
14:24:01 <ketas> but at least i know what force it takes
14:32:53 <ketas> from what i did read later, apparently dust enters the stickgrease surfaces in hinges and you can't "work it" loose, gets worse even, and if you try to clean and lube it as obvious solution, it gets too loose
14:33:11 <ketas> and new one has cost of entire machine value :p
14:46:34 <SomeVisitor>  ke8cqc │ wipt:  BT for headsets doesn't work in Linux. ← I've been using BT-Headsets on Linux for years now …
14:56:06 <ketas> i guess it's - varies
15:22:36 <angry_vincent> stable/15 branch needs https://cgit.freebsd.org/src/commit/?id=e4f2a350955406ffd58dd3f0bb7610df0f36d647 backported, otherwise buildworld fails on pkg as described in commit message.
15:24:43 <ivy> angry_vincent: i'm sure it will be, it was only committed to main this morning.  Ed doesn't usually include MFC after in his commit messages, even when he plans to MFC something
15:26:43 <angry_vincent> ok. no problem
15:33:46 <rtprio> any way to get my fn keys working on this x1 carbon? i've tried loading acpi_ibm but not sure what else to try.
15:34:10 <rtprio> (they're not getting through with `wev` so it doesn't matter right now how they're mapped)
15:48:46 <ketas> ivy: funniest commits say mfc after 3 minutes
15:48:49 <ketas> :p
15:49:19 <ivy> ketas: that's pretty common during a release cycle since the point of the commit is to fix the stable build
15:49:30 <ivy> i often use MFC after: 3 seconds
15:49:55 <ketas> not mfc instantly?
15:49:57 <ketas> :p
15:50:05 <ketas> immediately or so
16:11:34 <kevans> most people can't stage a cherry-pick for an immediate mfc, there's clearly always some latency :-)
16:12:35 <kevans> odds are ~one second is the lowest you can manage, since the first push has to succeed to be certain that the MFC commit's cherry-pick annotation doesn't end up with a hash that the remote rejects
16:25:20 <ketas> silicon brains can do it
16:29:20 <ketas> wait, git hashes are actually calculated from real data?
16:29:24 <ketas> i had to look
16:32:46 <kevans> yes
16:33:25 <kevans> if you lose the push-race, you have to rebase: new parent hash changes the hash of your own
16:35:12 <ketas> o/` if you lose the push-race, you have to rebase o/`
16:35:25 <Reinhilde> docs and translations are the entering wedge
16:35:50 <rtprio> what is 'the wedge' ?
16:36:07 <ketas> who was wedgied
16:37:11 <ketas> so yeah i assumed git commit id is head -c 1024 /dev/urandom | sha1
16:37:17 <ketas> :/
16:44:29 <rtprio> yep