00:44:12 Hi 00:44:28 I installed some nerd fonts but still, I keep getting the squares in my terminalus 00:53:32 zyxer: how exactly did you install them? 00:54:16 Also, what's terminalus? 00:54:42 terminal 00:55:05 I uh... pkg install... I can't remember. 00:55:06 what Software? 00:55:31 How can I list packages I installed manually? 00:55:44 pkg noauto 00:55:48 thanks 00:55:59 ALso, even some manpages have the square 00:56:19 what's your locale set to? 00:56:21 nerd-fonts 00:56:26 is the package name 00:56:49 what is the locale var I shall echo? 00:59:23 * meena falling asleep 01:01:30 locale C.UTF-8 01:01:44 LC_ALL is empty 01:46:18 zyxer: packages you installed are in the log 01:46:40 zyxer: my LC_ALL is empty 01:53:38 Locales help the terminal to select the font. But the font still needs to be selected which supports the characters. 01:55:48 what terminal are you using, zyxer ? 01:58:42 I wrote up my own notes on XTerm and mention with a "UTF-8, Unicode, Locales" section: https://www.proulx.com/~bob/doc/xterm-notes/xterm-notes.html 01:58:43 Title: XTerm Notes 01:58:56 That's from a GNU/Linux system but I think XTerm is the same on FreeBSD. 02:04:32 xterm is xterm 02:04:48 there are quite a few better ones than xterm, tho 03:29:04 is there a name for the info about how a program is executed? like all the args and stuff 04:03:42 and env vars 04:05:12 A name? As in, "command"? 04:06:45 well when we start a program, the env vars and command line args all contribute to the starting state of the program. so different starting state can cause the program to operate differently. what do you call that? 04:07:23 kinda like environment, but instead of for a user, it's for ONE running of a program 04:07:39 Instance? 04:08:03 * kenrap thinks tmp_ nailed it 04:21:28 what's the diff between executing a program, invoking it, running it? 04:21:40 loosely synonyms but what're the right words to use? 04:33:18 polyex: All the same, with the exception that "invoking" suggests the thing running the program. 04:33:29 The user environment is passed to programs and becomes the program environment. See environ(7) man page for that part. 04:33:33 what about invoking? 04:34:54 I usually call the args the programs option arguments. And I think that invoking, executing, running, and in some contexts calling all make sense. 04:36:37 I think executing a program may be the most Unixy way to describe it given that all of the calls to do so are exec() family calls. (Until the recent spawn calls which are new in the grand timeline.) 04:37:16 See execve(2) and the descriptions there for example. 04:38:41 rwp does "program environment" include command line args? 04:38:46 or just env vars 04:38:57 I see a little humor in that on 13-2R the man page for fork() describes _Fork() and says, "The _Fork() function appeared in FreeBSD 14.0." 04:39:55 The arguments share the space with the environment but are not actually part of it. So... No. 04:40:11 hi rwp 04:40:19 Hello nomia. 04:40:34 i tried your suggestion but it still doesn't do anything when i try to boot 04:40:50 i think that image doesn't have u-boot 04:41:24 but i can't mount the image in linux to look inside 04:41:30 I have never booted FreeBSD on a Banana Pi so I don't know. But I have written a lot of SD cards and USB storage. I can help with that side of things. 04:42:03 I do have a Banana Pi M1, the older model to your M3, and so I want to try it now. But just not a lot of free time to play with it yet. 04:43:28 (: u might need days and days to try like me 04:44:20 polyex left before I might mention that in the early days there was an obsolete way to call main() with argc, argv, and arge a pointer to the environment. So in the C program one could read args and the environment mostly the same way. But later the environment pointer was deprecated and instead global variables were used to access the environment. 04:45:02 Also I would mention that "getconf ARG_MAX" returns the stated size of the combined environment and arguments together. Which is the entire reason that the xargs utility exists, to avoid hitting that limit. 04:46:47 nomia, The BPi M3 looks pretty interesting. I have used the M1 for a lot of random things booting Debian on it. It would be pretty useful to me to figure out booting FreeBSD on it. 04:46:57 Life and time is what keeps everything from happening all at once. 05:08:28 Huh, something must be up with the Release Engineering, since the team just recently promoted someone as the new Lead 05:54:30 rtprio, I know other people like other terminal emulators. There are many. But so far I have yet to find a terminal emulator I like better than XTerm. The others are all worse. 05:54:33 kenrap: meh, i wouldn't worry too much about it. colin's quite excellent as well 05:54:55 "Many forms of terminal emulators have been tried, and will be tried in this world of sin and woe. No one pretends that xterm is perfect or all-wise. Indeed it has been said that xterm is the worst form of emulator, except for all those other forms that have been tried from time to time..." --With apologies to whomever said that before Churchill. 05:56:25 Re: Release Engineering team lead: It's probably simply time to share the load and put someone else in the hot seat for a while. 06:49:15 kevans: I see, good to know :) 07:46:59 it would be nice if freebsd had a free nntp server for discussion, might get tagged with spam though 07:53:28 jonusenet: the problem with every platform is moderation. that usually costs way more resources than the initial setup 07:54:40 good point, i had the craziest idea for freebsd 07:55:13 we can have a little distro for pure development as a group, like setup a fb15dev server and you can use nntp irc and web apps 08:02:56 and yeah, an admin can check the patches and we can have images of the os catered to the groups feelings 08:03:39 * check the patches every night and compile the kernel and userland, so everyone could use it. could give git a run for their money 08:16:21 otis: thank you ! 09:59:17 rwp: releng lead seems like a thankless task 11:04:49 rafe: It probably is, but I still fail to see a point in delaying release notes while the mirrors have the images since more than a week. 11:06:58 armin: I agree this was bungled. There may very well be a good reason to delay but it has not been communicated at all. 11:10:17 rafe: exactly. 11:11:54 rafe: My naive understanding would still be to release both images and notes at the same time makes a bit more sense. 11:12:25 rafe: I don't see what the idea behind that is. 11:13:28 armin: I cannot speculate because I have zero information about the underlying issue, when they were discovered, etc. 11:15:13 rafe: I fail to see how the underlying issue is relevant, the release notes should have been written at the point of uploading the images. 11:15:50 The release notes are up. It's the announcement that's lacking 11:16:42 Sure we could nitpick this to eternity, but I don't believe having images downloadable for weeks while telling your users to not install these is bollocks. 11:16:58 s/don\'t// 11:17:39 I am not disagreeing with you 11:17:51 I will nitpick; however, it's been four days 11:18:58 rafe: not sure in what timezone you are, but 18-10 is "8" in my part of the universe: https://download.freebsd.org/releases/amd64/amd64/ISO-IMAGES/14.0/ 11:18:59 Title: Index of /releases/amd64/amd64/ISO-IMAGES/14.0/ 11:19:18 i think gjb is tired, https://lists.freebsd.org/archives/freebsd-stable/2023-November/001702.html 11:19:19 Title: Update to the Release Engineering Team Roster 11:19:33 it was supposed to be released on 14-10 11:19:39 it's now 18-10 11:19:44 rafe: Look at the timestamps. 11:19:52 *14-11 11:21:17 meena: I don't doubt it 11:21:28 armin: they were not posted on 10-11 11:21:55 armin: I can assure you of that as I was checking regularly 11:25:27 rafe: posted or built, these files obviously existed at that point. 11:25:56 rafe: So even if you rsync them and tell rsync to keep timestamps, this is still wonky. 11:43:55 <[diablo]> good afternoon #freebsd , is FreeBSD 14.0 now finally out please? 11:45:35 Good afternoon, [diablo], no it still is not. It's still the "upcoming" release, even though the final images for 14.0 were built more than a week ago. 11:45:47 <[diablo]> hi armin, yeah I've see the ISO is there 11:45:54 <[diablo]> hence the question ... 11:46:07 <[diablo]> so basically, I shouldn't treat this as the final /final/ release 11:47:07 [diablo]: I was just complaining about exactly this right before you asked, actually. 11:47:22 <[diablo]> haha 11:47:28 <[diablo]> a tad confusing I must say... 11:47:40 [diablo]: I fail to see a point in uploading images and then telling users to not use them. 11:48:05 <[diablo]> yup 11:49:13 If it says "don't use" that means you should use it 11:49:20 Just to check why 11:51:08 <[diablo]> I wonder when the official release will be then 11:52:50 I wonder when the release process will be adapted so that the delay between announcement and images will remain small enough to not confuse the majority of users. 11:53:15 (or images and announcement, even, in this case) 11:55:53 Anyhow, I expect some statement from the release manager once this is sorted out, there's probably a good reason which we don't know (yet). I hope this is being communicated more transparently in the future. 11:56:41 the whole development process in the git is open, too, you still would have the delay between the final commit for the release (even if not tagged) and the release announcement 12:01:05 <[diablo]> Still a belter of an OS. Looking forward to it being finally out 12:08:46 BelterOS 12:10:11 <[diablo]> hehe 12:10:35 <[diablo]> armin a fine Dutch name you have there btw 12:13:06 [diablo]: Thank you so much, I'm born german, my grandparents were jewish, polish, italian and something 4th unknown. :) 12:13:48 [diablo]: I vibe with the dutch, though, one of my favourite countries, and they have, hands down, the best liquorice and cheese. 12:14:42 [diablo]: So yea I'm just that rainbow dog. :D 12:14:53 <[diablo]> :D 12:16:14 <[diablo]> lived in NL,DE,BE,UK and ES... 12:16:20 <[diablo]> viva Europa 12:17:35 I actually loved Dublin the most, it was raining every single day (I love rain!), people are smoking and drinking beer upstairs in double-decker buses, record stores were just legendary, and the skater scene in the streets was really tangible. 12:19:32 Denmark was suuuuper nice, too, also Sweden. Never ever been to Belgium. :( 12:19:58 <[diablo]> FOSDEM is pretty cool, I've only actually been once , but was cool 12:20:38 <[diablo]> BRB... 12:20:42 have fun :D 14:58:40 when upgrading from stable/13 to stable/14 - are there any steps that differ from updating within the stable/13 branch? 15:04:11 jbo: do you mean in the command syntax or overall ? 15:04:20 mns_, overall 15:04:43 I assume I should also update the bootloader on the ESP? I never upgraded from stable/X to stable/Y before. 15:05:44 when going up a version it's much more important to do all the steps and in the right order 15:06:23 including doing etcupdate -p, installing the new kernel and rebooting before trying to install the world, etc. 15:06:27 I've not used stable and so not had to do a stable upgrade. I use release, and I usually follow the steps in the handbook and have not had an issue. I've gone from 10 -> 11 -> 12 -> 13 15:06:45 personally I do it by installing to a new image from scratch rather than going in-place 15:06:56 RhodiumToad, that would just be the normal workflow I also use to upgrade within the same stable branch, no? 15:07:30 jbo: yes, assuming you're following the documented workflow and not skipping steps 15:08:03 RhodiumToad, alright. so what about the loader on the ESP? does either buildworld or buildkernel build that and I copy it manually? 15:08:26 oh, right, you should do that yourself, yes 15:09:10 RhodiumToad, where do I "get it from" and during what stage of the process do I copy it to the ESP? 15:10:08 installworld will put it in /boot/loader.efi 15:10:30 it's not especially critical, older loaders have no problem with newer kernels afaik 15:10:33 RhodiumToad, so when I have my ESP mounted during installworld I'll be good? 15:10:54 I don't think installworld updates /boot/efi/... 15:11:22 ah, /boot/loader.efi is different ofc 15:11:41 I would update the efi after installworld and before rebooting 15:11:56 since that keeps loader.efi in sync with the rest of /boot 15:12:50 do I only update /boot/efi/efi/freebsd/loader.efi or also /boot/efi/efi/boot/bootx64.efi ? 15:13:06 if they're currently the same content, then update both. 15:13:33 they may be different if you're sharing disk with other OSes or have some boot manager setup. 15:13:51 yeah this is a dualboot with windows 10 15:14:46 bootx64.efi is the one that the firmware is supposed to boot by default, but EFI environment settings can override that 15:19:00 Is there a place in the freebsd handbook or documentation for simple user guides like: "creating windows bootable usb?". I would like to add such a guide because it would have been usefull for me earlier 15:19:20 "windows bootable usb"? 15:19:32 thank you for the info, RhodiumToad ! 15:19:41 RhodiumToad, ...windows installation medium 15:20:07 what has windows got to do with freebsd? 15:20:41 nothing? But forum posts on this topic are still very active 15:20:54 and outdated most of the time 15:21:13 https://forums.freebsd.org/threads/how-create-bootable-freebsd-usb-in-windows-for-freebsd-12-0-current-i386-20171213-r326820-disc1.63807/ 15:21:14 Title: How create bootable FreeBSD USB in windows for FreeBSD-12.0-CURRENT-i386-20171213-r326820-disc1 ? | The FreeBSD Forums 15:23:18 that's not creating a windows anything, that's using windows-based software to copy a freebsd image to usb 15:23:54 shit wrong link 15:24:05 https://forums.freebsd.org/threads/creating-a-windows-10-bootable-usb-stick-using-freebsd.77429/ 15:24:07 Title: Solved - Creating a Windows 10 bootable USB-stick using FreeBSD | The FreeBSD Forums 15:26:22 one has to format it correctly then use 7-zip and then fusefs-ntfs which for a dumbass like me took a couple hours to figure out. Since I was always trying to mount the windows.iso like on linux. 15:26:39 certainly that's nothing that belongs anywhere near the handbook 15:27:34 ok then, so where should it be? 15:28:17 "mount the windows.iso like on linux"? 15:28:49 Check out step 8: https://kb.adamsdesk.com/operating_system/create_a_bootable_windows_10_usb_using_linux/ 15:28:50 Title: Create A Bootable Windows 10 USB Using Linux - Adamsdesk KB 15:32:11 ok, on freebsd you'd need a -t cd9660 option or whatever, but basically the same thing 15:34:50 and yes, fusefs-ntfs for the ntfs-3g package 15:35:38 only part there which is unclear is what the ms-sys tool is doing. 15:36:27 (and using gpart in place of fdisk, obviously) 15:39:53 oh, mounting from a file you'd use mdconfig first of course 15:42:23 or for that matter if you're just copying files out of an iso, you can use tar 15:42:48 (bsdtar can read everything that libarchive can read) 16:20:31 RhodiumToad, seems like upgrade from stable/13 to stable/14 worked well :) 16:23:01 good :-) 16:24:44 I guess no fun for me today :D 16:28:04 hahaha 16:28:25 you could update from stable/13 to say maybe openbsd or netbsd if you want fun ? 16:28:42 that does not sound like fun 17:00:24 RhodiumToad, that's where you are wrong 17:00:35 What you just said doesn't work 17:00:58 only unzipping and copying worked for me. The windows.iso isn't truly a cd9660 apparently 17:01:09 ms-sys you don't even need to use 17:02:36 That's why there should be a wiki page even for stupid stuff like this. Because if you are installing windows instead of freebsd you are probably already under a time constraint, where you just want to test some hardware support or idk. 17:02:55 and the last thing you want is to go on a 2 hour rabbit hole of "I read that there and there and there" 17:03:45 the arch wiki is a great example of understanding this 17:25:53 Arch wiki is so great that it helps me even with *BSDs at times. Since third party software isn't always well documented 17:27:13 And it can help 100% of linux users. My linux go to is Void, and it doesn't run systemD or have much in common with arch except being linux. 17:28:04 Perhaps there is a wiki for BSDs other than handbook? And other than forums? 17:28:40 As said the handbooks are great on all BSDs I tried. But at times I find some manpages lacking, or entirely missing 17:59:27 RhodiumToad, you still around, sir? 18:02:15 I feel like poudriere is ignoring per-port options in /usr/local/etc/poudriere.d/make.conf 18:02:36 in there I have: x11_polybar_UNSET = I3 18:02:47 that should unset the "I3" option of port x11/polybar right? 18:45:34 any reason why my history is gone when i reboot my laptop ? my shell is sh im using the default shell from the install 18:46:38 one possible reason would be multiple shells competing to save their own command history 18:47:38 https://serverfault.com/questions/228510/how-to-change-default-shell-in-freebsd 18:47:39 Title: bash - How to change default shell in FreeBSD? - Server Fault 18:56:21 How can i get my chrome bookmarks to firefox even if i don't have chrome on any system i have ? on chrome for my android phone i have all the bookmarks 18:56:44 jb1277976, Which shell is it? Is a history file set? 18:57:05 parv don't know i'm just used to bash for so many years and tab completion 18:59:12 jb1277976: The "bookmarks manager" in your Chrome should have some way to export them as HTML. 19:01:39 jb1277976, What do this show in "sh" (I missed that earlier): "echo $HISTFILE ; echo $HISTSIZE" ? 19:01:56 jb1277976: and if you have that, you could just send a mail from your smartphone to yourself with that attached, and then later on import that on your computer into firefox (I believe???) 19:02:01 parv im already on bash no need anymore 19:02:10 jb1277976, Ok 19:02:16 jb1277976: Bit of a shot in the dark, but I reckon that MIGHT work at least. :) 19:02:41 Thanks 19:03:57 i use bash for user. ( not for root, there sh is set, unchaged ). 19:08:57 * parv compiles static zsh to copy to /bin; adds alias exz="exec zsh" in ~/.shrc 19:31:37 * parv s!zsh!/bin/zsh! 19:34:28 it's /usr/local/bin/zsh on my computer. :) 19:34:53 That too. 19:36:23 APROPOS locations on FreeBSD. Say I install a package or port, and that creates some /usr/local/etc/supercoolprogram - I got used to symlink these things to /etc/supercoolprogram, as well as symlinking /usr/local/etc/rc.d/supercoolprogram to /etc/rc.d/supercoolprogram - is it okay to do that? 19:37:39 armin, Yes. But why? 19:37:59 parv: just so I don't have to find out where it is, I already know before I type. 19:38:23 parv: "convenience" or "laziness" I believe? 19:39:35 parv: or let's just say OCD/ADHS? :) 19:40:26 armin, Be aware that "rc" system would start|stop supercoolprogram and that may fail due to order & some things not being available yet 19:41:52 parv: I'm not able to understand in detail what you wrote there. :( 19:42:19 *scratches head* 19:42:27 armin, See the manual page for "rcorder(8)" 19:42:37 parv: ty! 19:44:11 armin, Say "/usr/local" is on a different file system. During boot, "/etc/rc.d/supercoolprogram" will be used to start it; "/usr/local" not being yet mounted would cause that to fail. 19:44:28 parv: ah, AH! 19:44:41 parv: now I get where you're coming from, thanks! 19:45:37 ... then mix in networking ... 19:53:55 parv: Yea thx for explaining that, makes sense. 19:54:03 yeah, i don't think i would do that 19:55:09 armin, You are welcome 20:30:01 * _xor ponders to himself 20:31:21 <_xor> I need to figure out if ripping firmware from an embedded device and disassembling it is an IP violation, or at least at what point it becomes an IP violation. 20:31:59 <_xor> I know that if a protocol is spec'ed out via blackbox, then it's not a violation (a la Samba). 20:33:45 <_xor> I just can't remember directly pulling the firmware and stepping through can be a violation per EULA. I thought there was a case a while back that dealt with that specifically, but I can't seem to find it. From what I can tell so far, it's not a violation to do it directly via firmware either. 21:00:57 I'm installing freebsd on a Chromebook with no sound that's just given. Will the headphones work ? I'm thinking It should or do those need drivers also? 21:01:15 I'm going to load the snd drivers regardless since this is a fresh install 22:04:00 hey there! I'm confused about the FreeBSD 14.0 situation; is it out yet, or delayed? 22:04:49 The announcement has been slightly delayed, due to minor issues, apparently. 22:05:51 veg, https://lists.freebsd.org/archives/freebsd-current/2023-November/004980.html 22:05:53 Title: [HEADS-UP] Quick update to 14.0-RELEASE schedule 22:16:15 thank you, rwp 22:16:58 are we talking about the announcement communique alone being delayed, as opposed to the software release? 22:17:11 or everything being postponed a few days? 22:19:36 Everything appears to be in place, generally, and many people have already upgraded to what has been marked 14.0-RELEASE (I have not yet), but the official announcement not having been made I would say it is not officially released yet. But must be 99.44% okay at least. 22:20:34 thank you for the clarification, for some reason I thought it was released, and was surprised to not see the website updated when looking for the release notes 22:25:30 I don't have any special view into things. I am just repeating information that has been published. But I presume there is some small snag that they want to make correct before they announce it. Otherwise they will announce it and then someone will hit that snag and it would be a complaint. A complaint that is avoided if they fix it beforehand. 22:26:51 Put yourself into the hot-seat of release engineering. It's a big deal to announce a release! And if it does not go perfect even after hours, days, weeks, months of work, then you feel bad that other people have complaints that it did not go perfectly. 22:28:40 absolutely! 22:28:54 this may sound like a dumb question but my synology just died and will NOT boot. I am looking at external hard drive enclosures, that will work through USB 3.. are there any considerations (minus usb 3 sucks) to worry about adding these to freebsd 22:35:25 I have not had good experiences with USB for full time storage enclosure use on any OS. Seems to me that after a month or two I always have to power cycle the USB device. (Meanwhile USB networking has been rock solid for me. Go figure!) 22:36:33 If possible eSATA is a much better choice for an enclosure. Or if you build Frankenstein's monsters just cable SATA cables out and around is much more reliable. 22:37:48 Also, I don't know why but it seems very difficult to find disk enclosures to buy at an affordable price. They just don't exist. I mostly use rack mount cases that I have refurbished with quieter fans for my own use. 23:12:39 i'm on a new system and need to get headphones working. but really trying to understand it. here is sndstat https://dpaste.org/k1bNh and here is sysctl -a |grep hda https://termbin.com/k0uq 23:12:40 Title: dpaste/k1bNh (Python) 23:13:22 following this guide https://is.gd/8sHTIM not exactly the same but im subsituting what i have 23:13:23 Title: FreeBSD – No sound on headphones – Muktadiur's Blog 23:22:54 so, I just installed 14-0-RELEASE 23:23:09 and freebsd-update install issues that after all's done, lol 23:23:09 WARNING: FreeBSD 14.0-RELEASE is approaching its End-of-Life date. 23:23:09 It is strongly recommended that you upgrade to a newer 23:23:10 release within the next 2 months. 23:23:20 I suppose they do need to iron a few things out :) 23:31:47 veg: Things move fast. 23:35:11 Lol it came out like two days ago though 23:35:31 >Get on FreeBSD 23:35:38 >New ISO 23:35:56 >Installed 1 week ago the newly released version 23:35:59 >Update 23:36:10 Greentext doesn't work on IRC. 23:36:15 >FreeBSD is out of date 23:36:51 I don't expect the text to turn green