02:41:36 <hernan> almost 14, nov 14, fbsd 14. will they release at 14h14m14s ?
02:51:23 <jb1277976> Lol
05:41:32 <phryk> woop 14.0-RELEASE soon
05:57:34 <paulf> woop that means plenty of work
07:31:39 <n30> http://paste.purplehat.org/view/b55b1905 <--- anyone that can answer why portmaster says like this?
07:31:41 <VimDiesel> Title: portmaster - PHO Paste
10:15:59 <maccampus> Can FreBSD run Android Apps ?
13:19:44 <n30> http://paste.purplehat.org/view/b55b1905 <--- anyone that can answer why portmaster says like this?
13:19:45 <VimDiesel> Title: portmaster - PHO Paste
13:25:55 <nimaje> hm, not sure what portmaster uses to decide which are important packages and which are only there because they are build dependencies, are those included in portmaster --list-origins ?
13:27:46 <n30> nimaje: it seems all those packages that needs to update is in --list-origins to
13:28:11 <n30> openssl was not i noticed now
13:29:19 <n30> py39 openssl harfbuzz was not listed with portmaster --list-origins
13:32:28 <n30> had simular on another box to update but it worked flawless on that one
13:35:53 <zyxer> Hi
13:36:01 <zyxer> Good afternoon
13:41:44 <nimaje> n30: sorry no idea, maybe  portmaster --update-if-newer '*'  considers everything you have on your system, but you should consider switching to something doing isolated builds like synth or poudriere as your system isn't changed while building, so you don't have a partial updated system and you don't have the build dependencies installed on your system, only in the jails used to build the packages
13:57:45 <alxhr> Hi!
14:49:44 <zyxer> Hi
14:50:25 <tercaL> hi
14:50:42 <zyxer> I have this device (it is from OpenBSD host):
14:50:45 <zyxer> Ugen0 at uhub0 port 3 "Qualcomm Incorporated Qualcomm HS-USB" rev 2.00/0.01 addr 2
14:51:04 <zyxer> It is wwan interface, I inserted sim-card
14:51:36 <zyxer> But OpenBSD doesn't recorgnise it as an internet interface
14:51:58 <zyxer> So, where can I find info on what hardware is supported on FreeBSD?
14:53:33 <zyxer> Or better yet, can I get a live FreeBSD image to check? So I can check from FreeBSD host without having to install and delete my current installation
15:16:34 <BillyJoeBob> It's a USB device, right?
15:17:00 <BillyJoeBob> You could try installing FreeBSD in a virtualbox and attach the device and see if it works?
15:22:11 <zyxer> It is integrated
15:22:37 <zyxer> I think it is connected to internal USB on MoBo instead of connected to PCIe
15:23:28 <zyxer> (It is PCIe socket but I think it goes through USB bus lanes and is just PCIe to USB adapter so to speak, then connected to USB internals)
16:08:12 <zyxer> How can I get audio through hdmi? AMD APU(iGPU)
16:12:46 <nimaje> figure out which sound device it is, eg via  cat /dev/sndstat  and then change  hw.snd.default_unit  accordingly via sysctl
16:39:10 <zyxer> nimaje: Doesn't work?
16:39:32 <zyxer> Oh wait
16:39:42 <zyxer> That was setting default unit, not changing
16:40:05 <zyxer> But thanks! I can work from herr
16:41:41 <zyxer> Wait... Hmm...
16:47:51 <zyxer> I restarted mixer service but still no sound
16:48:11 <zyxer> I mean, sound is still on laptop speaker and not through HDMI
16:52:43 <zyxer> https://clbin.com/3ZINF
16:53:02 <zyxer> output of cat /dev/sndstat
16:53:57 <zyxer> I did: sysctl hw.snd.default_unit=0
16:54:33 <zyxer> still, device is the laptop speakers
16:56:11 <nimaje> hm, do you hear any sound? can you try  cat /dev/random > /dev/dsp0  and the same for 1 and 2? (just terminate it after a few seconds via ctrl+c)
16:57:05 <zyxer> That gave sound on correct device
16:57:13 <zyxer> nimaje
16:57:39 <zyxer> I tried restarting firefox as well, incase firefox was "cached" on wrong device
16:57:47 <zyxer> Wait, let me try to restart x
16:58:01 <nimaje> so dsp0 is the correct device and works? hm, no idea then
16:58:46 <zyxer> Restarting x did not help
17:05:15 <zyxer> ok so that command needs a restart of another service to apply
17:06:02 <zyxer> audio/pulseaudio according to wiki, or pacmd and then input set-default-sink 0
17:06:07 <zyxer> To change on the fly
17:06:32 <zyxer> The command you gave needs reboot (and I guess persists between boots, obviously, lmao)
17:07:42 <thorre> Hello everyone. With the 14-RELEASE just arround the cornor I would like to have your input on upgrading. More specific on when to upgrade. Is it considered best practice for production systems to wait for a .1 release?
18:37:12 <V_PauAmma_V> thorre, I don't know offhand how applicable that advice was beyond my own circumstances and those specific versions, but someone (I think kevans) steered me toward 12.3 instead of 13.0 (which came close to each other) when I asked which to upgrade my daily driver (and single FreeBSD computer) to.
18:42:08 <rwp> I feel that if one is asking that they should avoid the .0 releases.  Especially if it is their one single main computer that must work for them.
18:42:47 <rwp> On the other hand if you have a dozen machines all doing things and have been running it for a while then you definitely should install the .0 on a system and test it out and report bugs.
18:54:28 <thorre> Thank you for your feedback. I will not jump the gun next week when 14 is released but give it a little time before I upgrade my main machine.
19:10:23 <babz> In any case, I strongly recommend testing an upgrade on a non-critical machine before moving on to production machines (on Fridays).
20:22:00 <zyxer> /set irc.look.smart_filter on
20:22:06 <zyxer> oops
20:22:09 <zyxer> lmao
20:27:59 <plasma> :P
21:01:24 <meena> my look smart filter would probably just translate to /quit, so i stop embarrassing myself
21:22:31 <nimaje> zyxer: as stuff dynamically set via sysctl doesn't survive a reboot, it of course doesn't need a reboot, but no idea about pulseaudio, I just assumed you used sound directly and not pulseaudio on top, no idea if it notices when you change the default audio device that way
21:37:38 <fatalnix> Fi phy pho plum. I smell a bunch of ... Crap I can't rhyme that without being mean. Oh well. What's new?
22:11:45 <wikan> hi
22:12:07 <wikan> i think i have found a bug in bash but i am not sure. Maybe it is bug in my script
22:12:29 <wikan> but I have a problem with a weird behaviour or bash
22:12:53 <wikan> may I share my script with you?
22:13:56 <wikan> maybe first I check in #bash...
22:15:45 <RhodiumToad> put the script on a paste site
22:23:49 <wikan> http://paste.wooledge.org/26084
22:23:59 <wikan> 58 - commended export = works fine
22:24:26 <wikan> line 58 - uncommended export = eval in 59 runs 3 times and my desktop hungs
22:24:46 <wikan> i fixed regex =~ ^\?
22:24:51 <wikan> btw :)
22:26:07 <wikan> sorry - not 58 but 59 (export line)
22:28:15 <RhodiumToad> is that eval supposed to be re-executing this script?
22:28:46 <wikan> no
22:29:27 <wikan> i dont know how to push "value" with quotes but visible for child process as without them
22:30:17 <wikan> because "bash run $string" where string is (--x "hello") results with that, the child script has x as "hello" with quotes
22:30:42 <RhodiumToad> that's correct, yes
22:30:58 <wikan> anyway, without eval i had the same issue
22:30:58 <RhodiumToad> if you want to make it bash-specific, that's what arrays are for
22:31:17 <wikan> will change it but first must not hung my desktop :|
22:31:30 <RhodiumToad> what is ${arg_plugin}.sh whatever that is doing with XMENU_STRING ?
22:33:24 <wikan> arg_plugin is --plugin argument. It is for example (--plugin rofi)
22:33:48 <wikan> so when it is rofi then XMENU_STRING is a command to run rofi with theme and theme-str
22:34:07 <wikan> plugin does for example (ls -la | $XMENU_STRING)
22:34:12 <wikan> and rofi shows up
22:34:30 <wikan> otherwise any other xmenu like dmenu (plan)
22:34:47 <RhodiumToad> so XMENU_STRING is supposed to be a valid command and args after word-splitting
22:35:25 <wikan> word-splitting?
22:35:41 <wikan> but yes it is entire commad for plugins to run to show menu
22:35:55 <RhodiumToad> you know that when you write $var in a script, the value of var is split into words, yes?
22:36:29 <RhodiumToad> i.e. if you do var="1 2 3"  and then  somecommand $var   then the command gets three args, yes?
22:37:16 <wikan> yes
22:37:41 <RhodiumToad> and that word-splitting doesn't respect internal quotation inside the value of var
22:38:04 <wikan> plugin use eval
22:38:10 <RhodiumToad> i.e. if the value of var is 1 "2 3" 4, e.g. if you set it as  var="1 \"2 3\" 4"  then it splits into 4 words, not 3
22:38:32 <RhodiumToad> plugin uses eval how exactly?
22:38:34 <wikan> sorry right. Plugins use eval, so "ls -la | eval $XMENU_STRING"
22:38:49 <wikan> will change it to array
22:39:14 <RhodiumToad> ugh. eval $XMENU_STRING  and not  eval "$XMENU_STRING"   ?  the difference matters a LOT
22:39:47 <armin> it matters depending on what XMENU_STRING can hold
22:40:04 <armin> but as long as you don't know, quoting that is probably a good idea.
22:40:34 <wikan> wait...
22:40:39 <wikan> should be with ""
22:40:42 <wikan> is without
22:40:50 <armin> put differently, unless you WANT word splitting to happen on a " ", you want to quote that thing, yea.
22:41:26 <RhodiumToad> the problem is that eval $XMENU_STRING  ends up word-splitting the value, then concatenating it again
22:41:44 <wikan> dont understand
22:41:49 <RhodiumToad> so it messes up things like internal spacing in what you think are quoted strings
22:41:58 <armin> TMLP. too-many-layers-problem.
22:41:59 <wikan> as I see, rofi launches 3 times and hangs desktop
22:42:12 <wikan> hmmm
22:42:15 <RhodiumToad> i.e. "foo    bar"  is split into "foo and bar"  and then concatenated into "foo bar"
22:42:50 <RhodiumToad> yeah, pretty much any use of eval in shell is a Big Red Flag
22:43:05 <RhodiumToad> any use of word-splitting is a red flag, too
22:43:10 <jb1277976> Guys when i put in a ssd in this laptop how do i get my system to reognize it ? i know the bios must recgnoize it. after that do i jsut format it with the freebsd installer and i should be fine or is there somethign else i need to do ?
22:43:26 <armin> RhodiumToad: it depends, if you really really know what you're doing, and you control the input, and you can predict the input, in THAT one case I might not see a problem.
22:43:53 <RhodiumToad> jb1277976: as an additional disk? what do you want to use it for? or replacing the system disk?
22:44:32 <RhodiumToad> armin: anyone who thinks they know what they're doing when it comes to shell is probably wrong
22:44:34 <jb1277976> RhodiumToad: replacing the system disk
22:44:42 <armin> RhodiumToad: true.
22:45:05 <RhodiumToad> jb1277976: as long as the bios sees it, then the freebsd installer should be able to handle the rest
22:45:19 <jb1277976> Thanks
22:46:24 <RhodiumToad> armin: for example, the only reason why the whole of /etc/rc* doesn't explode and die is that key paths like /etc are known not to contain whitespace or special characters
22:47:26 <RhodiumToad> if I had infinite time I'd build a system where paths.h was modified to rename /etc to "/System Configuration" or some such, and document all the explosions
22:47:47 * RhodiumToad does not have infinite time
22:48:15 <armin> RhodiumToad: A large part of shell scripting is that you need to make assumptions. If the assumption you make is known to work in almost any damn case you can think of, why bother? Shell scripting is known as a "glue language" thing and I think that fits it quite well. You can use it to do almost anything you can think of, but you also get all possibilities to shoot yourself in the foot.
22:49:41 <armin> RhodiumToad: Of course, you *WILL* eventually shoot yourself in the foot while trying to master shell languages, no matter the interpreter, but that doesn't mean that interactive shell-use or shell-scripting is bad per-se, it's the other way around.
22:50:14 <armin> RhodiumToad: We need some kind of interface to speak to a computer and a shell is just a very perfect one.
22:51:10 <armin> RhodiumToad: for example you wouldn't check if a directory exists if you just mkdir -p'd it one line above...
22:51:54 <armin> RhodiumToad: but then again, someone evil might have created a file with that name before, what do you do? Check for all of these weird edge-cases? I don't think so.
22:53:03 <armin> RhodiumToad: I'd say many programmers will just live with that and assume that the user in SUCH a weird case knows what to do.
22:58:10 <wikan> i have no idea how to run rofi now
22:58:18 <wikan> eval hungs
22:58:24 <wikan> variable - errors
22:58:32 <wikan> bash is the pease of sh*
22:58:37 <wikan> piece
22:59:03 <armin> bash is a horror, yes, that's why I love it.
22:59:22 <wikan> i will try python wrapper
22:59:48 <armin> you can also just try to share your script (if you can share that data), I'll be happy to at least *try* to help you. <3
23:00:12 <RhodiumToad> this issue would be the same in other shells, it's not likely to be bash-specific
23:00:28 <armin> That's correct.
23:00:48 <wikan> but i can do system()
23:00:56 <wikan> only for this one command
23:01:07 <wikan> system(VALUE_FROM_ENV)
23:01:28 <wikan> i have no idea why eval hungs it is non sense
23:01:53 <RhodiumToad> doing system() from python or whatever is conceptually the same as eval "$var"  in shell
23:02:19 <RhodiumToad> it's not eval that is hanging, it's whatever you ended up invoking
23:02:33 <RhodiumToad> have you used set -x to see what's actually being run?
23:02:58 <wikan> garbage
23:03:16 <wikan> this mode isn't helpful hre
23:03:37 <RhodiumToad> of course it is helpful
23:04:06 <armin> Well set -x shows *exactly* what's actually being done, it could be.
23:04:38 <wikan> it doesn't help me at all
23:04:46 <wikan> but i will try -x to plugin
23:04:58 * armin throws winegum bears in wikan's general direction.
23:05:11 <RhodiumToad> the script you pasted isn't the one with the issue.
23:05:28 <RhodiumToad> $HOME/.xmenu/plugins/${arg_plugin}.sh  <-- that's the one you need to be looking at
23:06:44 <wikan> wait
23:06:50 <wikan> this command is hanging
23:06:55 <wikan> i copied it to xterm
23:06:57 <wikan> and hungs
23:07:04 <wikan> wtf
23:07:08 <wikan> must check it
23:07:17 <wikan> it is rofi fault
23:10:07 <wikan> great
23:13:37 <wikan> found a problem
23:13:56 <wikan> you can'tchange rofi position by -theme-str
23:14:02 <wikan> if you try rofi hungs
23:15:43 <wikan> wrong - you must set location AND ancor
23:17:00 <wikan> thanks for your time
23:19:09 <wikan> i need something better than htop
23:19:21 <wikan> can you suggest something guys?
23:19:29 <armin> tried "btop" or "bpytop"?
23:19:52 <wikan> htop require double pressing F9 to kill
23:19:58 <wikan> it is annoying
23:20:10 <armin> ctrl-c works for me
23:20:21 <armin> ah you mean to kill a process?
23:20:24 <wikan> btop is to fancy
23:21:10 <wikan> yes
23:21:30 <wikan> when you move with arrows then you need press F9 twice
23:21:45 <wikan> or maybe not
23:21:55 <wikan> so htop has lags
23:22:03 <wikan> not it is working well
23:22:09 <wikan> i have no idea why
23:22:20 <wikan> it didnt
23:23:21 <wikan> ok thans for you time
23:23:26 <wikan> again :)
23:23:32 <wikan> must restart my computer
23:23:47 <wikan> bye