00:12:42 this is extremely low hanging fruit, but, does anyone know if i can make this sed expression https://github.com/canonical/cloud-init/issues/3501 POSIX *and* GNU compatible? 00:12:44 Title: sed expression in tools/tox-venv is not POSIX compatible · Issue #3501 · canonical/cloud-init · GitHub 00:12:44 3501 – rc.firewall changes removed URLs and added typos https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3501 00:16:46 what the fuck is that 00:16:49 er, sorry 00:17:56 wheeeee 01:07:15 rwp: ya it doesn't boot 01:07:34 it doesn't even turn on the video card 01:08:34 FreeBSD-14.0-RELEASE-arm-armv7-GENERICSD.img.xz: OK 02:01:10 So I borked my bootloader by running `gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i da0`. It doesn't detect a UEFI boot option anymore. How do I recover? 02:08:03 The handbook says to use boot1.efifat but I only have a boot1.efi on the USB disk 02:46:31 does this mean i need to be running freebsd before i can install? https://forums.freebsd.org/threads/freebsd-bananapi-m3-support.58728/ 02:46:33 Title: Freebsd BananaPi M3 support | The FreeBSD Forums 03:09:48 it just looks like you need to use dd? 03:16:22 sjuxax: gpart bootcode is for legacy booting. For EFI, you generally want to copy /boot/loader.efi into your ESP, maybe as /boot/efi/efi/boot/bootx64.efi or somesuch. 03:16:51 (The efi/efi is not a typo - inside your ESP there's typically an EFI directory that itself contains BOOT, but case doesn't matter to us.) 03:18:27 mason, I've tried creating a new ESP manually and copying it there, but it's still not detected. Only the FreeBSD memory stick is detected as bootable under EFI. I even created a variable in the efibootmgr and it was gone on next boot. 03:18:56 sjuxax: Some UEFI implementations are wildly flaky. 03:19:26 sjuxax: Try using the fallback naming, BOOTX64.EFI, and make sure it's in your ESP (vfat/fat32) inside EFI/BOOT/ 03:21:59 nomia, If you think you wrote the SD card okay then the resulting system not booting must be for some other reason. Your command would have written the card okay. You said your command did not write the SD card but I think that it did. However your command would have required a "sync" to ensure that the data was written to the card before you ejected it. 03:22:31 That's one of the reasons dd is often recommended. Because we can tell dd to use sync options while writing. Then when dd is done and exits the card is also done and okay to eject. 03:24:19 nomia, I suggest this command for you: xzcat FreeBSD-14.0-RELEASE-arm-armv7-GENERICSD.img.xz | dd bs=1M iflag=fullblock oflag=direct,sync of=/dev/mmcblk0 03:25:15 That command will work the same on FreeBSD as on a GNU/Linux system. When the command exits the SD card has been written and can be ejected. 03:26:56 sjuxax, I have rather hated buggy UEFI systems and I have several. Do not despair. We have all cursed UEFI when we have had problems. If your system has the capability to boot Legacy BIOS you might try that as that is generally simpler and trouble free. 03:37:53 I need to get this bootable again ASAP. I was using legacy booting before, but that died too. I've tried both and am falling back to UEFI in hopes that it works. I'm currently booting sysrecuecd and will make sure that the ESP I tried to create is correctly flagged as an EFI System Partition 03:39:55 If I have multiple ESP partitions flagged, are they just ignored? 03:40:42 depends on the firmware, the spec doesn't specify 03:41:04 i suspect the first is used the rest are ignored in most places, but i have no evidence to back that up 03:41:24 ("gut feeling") 03:45:13 I agree with the gut feeling. I suspect that the first ESP found, top to bottom through the partition table, will be the one used. 03:46:28 yeah. i mean, it just feels like the laziest and least complicated possible way to implement it 03:46:53 it's only natural to be inclined to stop there when there's only supposed to be one 03:47:48 A *huge* complication with UEFI is that it is not simply the files on disk that are needed to boot. UEFI also requires the EFI VARS in non-volatile ram to be set up too. efibootmgr updates those. 03:49:27 But UEFI booting of removable storage like USB and SD cards avoids the EFI VARS requirement since those are usually always set. Meaning that often a UEFI system will easily boot USB or SD card but be buggy booting off of the main storage. 03:50:09 i don't think uefi actually requires non-volatile storage 03:51:17 It's detecting ESPs on MBR-based USB boot sticks, both FreeBSD and SysRescueCD. It's not detecting the ESPs on my GPT-formatted FreeBSD boot disks. 03:51:47 sjuxax: do you have access to, e.g., a FreeBSD or linux live CD that you could boot via UEFI? 03:51:49 I would love to go back to legacy boot if it'd work but gpart bootcode doesn't load the bootloader there either 03:52:02 kevans, yeah, I have booted sysrecuecd right now 03:52:08 (via UEFI) 03:52:09 does it have efibootmgr? 03:52:11 you need somewhere to store variables. technically I think the storage duration might not be specified, but without useful non-volatile storage you can't implement secure boot for example 03:52:44 yes, it has efibootmgr 03:53:14 trying to figure out how linux's efibootmgr does this 03:53:40 on freebsd you'd just mount the disk and efibootmgr -c -l /path/to/loader.efi/on/the/esp.efi 03:54:00 I did that from the FreeBSD memstick and it was just gone on the next boot 03:54:07 dunno if i didn't save it correctly or what 03:54:46 gone gone, even from the firmware menu? 03:55:03 it's possible to not make it active, but if the acommand succeeds it should still be there as long as there's nvram backing efivars on this platform 03:55:03 if it shows when running efibootmgr and then disappears from efibootmgr when rebooting, that's probably a firmware issue 03:55:28 you can check with efivar 03:55:38 efivar -l | grep -- -Boot 03:55:58 then grab each one and... efivar -p --name I think 03:56:27 meena: if you can provide sample input and expected output, I'd be happy to takea shot at your sed challenge. 03:56:33 yeah, on this linux boxen I have over here *poitns acrosss the internet* that dumps out the path in a hexdump 03:57:36 sjuxax: If you used legacy booting before it ought to still work. You didn't lay down a new partition table or something, did you? What's there now? GPT or legacy/MBR? 03:57:38 if you find one that has the path, you can `efibootmgr -a -b ` 04:04:06 yes, gone from the firmware menu. booted into freebsd livecd again. if i want to use legacy boot, what's the fastest/easiest way to reinstall the bootloader on GPT? I didn't change the partition tables at all 04:08:33 can I just do something like bsdinstall bootconfig? It booted fine using the layout from the installer 04:12:03 trying `gpart bootcode -p /boot/gptzfsboot da0`, without the protective mbr segment 04:20:13 no dice there. pulling up sysrescuecd again, maybe i'll try installing refind 04:30:37 ok, suppose i just want to use the usb's bootloader to boot my current root 04:30:48 lszfs zroot/ROOT/default: says device not configured 04:51:29 Phew, I guess it was something in the SAS configuration. I exposed 21/21 drives to the system during the boot process and now it's finally booting. Dunno why the default disk exposed would've changed, haven't changed any of the SAS settings, but at least I'm booting again 04:51:32 thanks all 04:54:19 still doesn't detect any of the EFI partitions, but what can you do 05:21:00 sjuxax: Glad it's working, even if there's still a puzzle left. 05:38:43 Life and time is what keeps us from solving all of the unsolved puzzles that we run across daily. :-) 05:40:58 yes 06:30:15 rwp: ok 08:49:18 ghoti I know that people using FreeBSD are usually very skilled so they do not require documentation, but I have the feeling that thin jails with UFS are not widely covered by the documentation, and in particular, the specific procedure included in the handbook did not work for me 08:54:31 well the procedure in the handbook cannot work as it requires zfs 09:01:18 but the point of this stuff is rather limited. it's a matter of ensuring that the common base of 2 jails *at the time of their creation* is deduplicated on disk. 09:01:18 If you update your jails, the space saving disappears. 09:03:06 babz: I understood that the handbook covers both ZFS and UFS (with NullFS) 09:03:42 Are you sure that UFS is not covered? Did I misunderstand the handbook? 09:09:32 ok, I didnt see this part 09:10:36 ghoti: i might be able to provide that 09:14:34 uskerine_: where are you stuck ? 09:35:01 babz https://forums.FreeBSD.org/threads/issue-while-following-the-handbook-to-create-a-thin-jail-using-nullfs.91015/ 09:36:01 I am not sure if you can see it, maybe it requires aproval 09:36:42 505 not found 09:36:47 *404 09:36:56 I see, it requires to be approved at the forum 09:38:55 here is the copy and past of the forum thread: 09:38:57 https://bpa.st/5MDQ 09:38:58 Title: View paste 5MDQ 09:40:46 I implemented the recommendation from scoobybejesus (I think it was him the one suggesting it) to also create symbolic link for dev, but still the Jail wouldn't start, so I have not included and falled back to the handbook procedure 10:00:18 that procedure is ... convoluted 10:07:07 in /etc/jail.conf.d/thinjail.conf 10:07:07 you should have path = "/usr/local/jails/thinjail-nullfs-base" I think 12:40:13 why doesn't jexec have a CWD? 12:47:19 why the heck is yarn not idempotent??! 12:48:22 uskerine_: "so they do not require documentation"? I disagree with that one. They're skilled because good documentation exists. 12:51:34 hi everyone, has anyone had luck getting the shell zsh to work with the tmux plugin manager tpm? if i keep the package bash (even if not sourced) the tpm program does not error out.. remove the package bash.. it go boom. Quesiton is: has anyone een able to get tpm to work without bash installed 12:51:52 https://nick.groenen.me/posts/the-4-types-of-technical-documentation/ 12:51:53 Title: The 4 types of technical documentation - Nick's Blog and Digital Garden 13:00:39 voy4g3r2: looking at the github repository, the first line in the tpm script i see is "#!/usr/bin/env bash" - so no, bash is a dependency to run tpm. it might even use bash specific syntax 13:12:39 monkeys bash stuff... good devs keep /bin/sssshhhhhhhhhh 13:28:09 CueXXIII: yeah.. i see that, then i think zsh is a bash++ as they say.. so yeah.. figure maybe someone was able to "hack" it 13:29:27 voy4g3r2: i'm pretty sure bash and zsh have come up with different extensions to the posix specifications 13:30:03 as Luke Smith put it, bash has alot of "bashisms" that are not always portable to other shells 13:30:30 most likely.. i felt 13:30:50 "dirty" with the bash gplv3 so i am like.. i like zsh (on my mac) so might as well be consistent through all environments 13:31:01 but zsh has their own zshisms, too 13:31:08 and making a leap, without reading, will burn you 13:32:14 totally get that.. i did not realize how much bashism was prevalent in my setup until i removed it 13:32:27 temporary fix, add it back, then see if i can just "move" the line to zsh from bash :) 13:32:56 its good to be posix compliant as possible 13:33:37 zsh runs bash just fine 13:34:27 ln -s /bin/zsh /bin/bash ;) 13:35:17 CmdLnKid: try `read -p "Your input: " input` in zsh for example 13:35:35 yeah that could be a problem 13:44:21 CmdLnKid: that was going to be my first test but have to handle some work related activities, which is NOT working on freebsd unfortunately.. 14:33:28 armin well then unfortunately it seems that there might be some gap in the documentation for thin jails 14:38:33 uskerine_: did you try what I said ? 14:39:18 uskerine_: you've seen https://docs.freebsd.org/en/books/handbook/jails/#thin-jail already, I assume? 14:39:19 Title: Chapter 17. Jails and Containers | FreeBSD Documentation Portal 14:41:36 I'm afraid the handbook procedure is unnecessarily complicated, poorly explained, and apparently contains a mistake. 14:43:51 It's not exactly perfect, yea... 14:51:58 also, and here I don't know if there's a real reason, but I have the impression that people usually do it the other way around as it's simpler : 14:51:58 have the r/w skeleton with symlinks to the ro base nullfs mount point 14:58:48 armin Yes I have followed the handbook three times https://forums.FreeBSD.org/threads/issue-while-following-the-handbook-to-create-a-thin-jail-using-nullfs.91015/ 14:58:49 Title: jails - Issue while following the handbook to create a Thin Jail using NullFS | The FreeBSD Forums 16:12:18 who is supposed to be organising the fosdem bsd devroom this year? 16:22:49 uskerine_: i haven't had to chance to do this by hand to verify what's happening, but it could be helpful if you see a generalized working example, which is what bastille does when it creates jails. it's all shell scripts. here you can see which files are softlinked and which are copied, if it helps. https://github.com/BastilleBSD/bastille/blob/master/usr/local/share/bastille/create.sh#L359-387 16:22:51 Title: bastille/usr/local/share/bastille/create.sh at master · BastilleBSD/bastille · GitHub 16:23:16 seriously 16:23:41 why no just fix the jail.conf frst ? 16:53:00 babz: wanna judge my setup? https://codeberg.org/meena-co/bootstrap.sh :P 16:53:01 Title: meena-co/bootstrap.sh: Bootstrap infra - bootstrap.sh - Codeberg.org 17:41:51 yes, but. 17:41:51 why keep it simple when you can make it complicated? 17:48:31 that makes me think I should look into pkgbase 17:54:10 babz: i used to use Puppet… but then things happened 18:00:19 master of puppets, I'm pulling your strings 18:00:27 twisting your mind and smashing your dreams 18:00:37 blinded by me, you can't see a thing 18:00:50 just call my name 'cause I'll hear you scream 18:01:23 there is #freebsd-social 18:01:40 sorry 20:04:08 If I manually install FreeBSD what is the proper size for boot partition ? 512k is enough ? (zfs on root) 20:05:11 512k is the maximum size. the whole partition is being read into memory and "640k ought to be enough for everyone" limit applies. 20:30:29 Good evening. It's been ages since I was on IRC last. 20:30:47 hi 20:38:06 congrats 21:33:58 14 21:35:41 scoobybejesus thanks I will have a look to that 21:41:44 jensen_, I have bad news for you. 21:41:51 This is Discord. 21:44:18 babz btw I saw your message suggesting to change path in the jail .conf. I tried and then I get: jail: thinjail: getpwnam: No such file or directory jail: thinjail: /bin/sh /etc/rc: failed 21:45:57 I will try to go through bastille script and see if I can figure it out, I think it is a pity that there is no more documentation 21:46:02 man jail 22:28:03 my bad. dev is not a symlink to the release/base jail. it's copied in. you can see what's copied into the jail on line 378 22:37:52 it looks a bit weird in the handbook 22:40:10 what's our equivalent to linux' localectl set-x11-keymap https://www.linux.org/docs/man1/localectl.html or alpine's setup-keymap: https://docs.alpinelinux.org/user-handbook/0.1a/Installing/manual.html#_keyboard_layout ? 22:40:11 Title: localectl - Control the system locale and keyboard layout settings at Linux.org 22:40:45 hi 22:43:47 Looking at https://en.wikipedia.org/wiki/C_standard_library#BSD_libc - what are the portable versions of these? - It was libbsd and some old NetBSD thing IIRC - so like would I just throw in a cross-platform build system—like CMake—and carefully port each thing so that Windows (MSVC, OpenWatcom, MinGW, Cygwin, clang), and Linux/macOS/SunOS (gcc, clang) compilers successfully build? 22:43:48 Title: C standard library - Wikipedia 22:44:04 (i.e., would I take from FreeBSD's current source tree) 23:27:30 oooft netsplit