01:40:01 how can I debug things in /etc/make.conf? I need to examine the value of a variable. @${ECHO_CMD} "hi" either in a Makefile or in /etc/make.conf does not work ("Need an operator 01:40:17 it seems to work for basically everybody else on the Internet 01:44:13 nor does '@${ECHO_MSG} "hello world"' as is documented here: https://docs.freebsd.org/en/books/porters-handbook/book/ 01:44:15 Title: FreeBSD Porter's Handbook | FreeBSD Documentation Portal 01:44:38 (§5.11 Slave Ports and MASTERDIR). it doesn't work in either make.conf or a Makefile. 01:47:48 moreover, I have a thing that is failing, how do I convince 'make' to show *ALL* of the commands it is executing? currently, I only get a very unhelpful error message referencing a file that appears over 600 times on my system 01:49:10 the first ~10 google results for "freebsd port build verbosity" are not helpful at all 01:50:42 most results seem to refer to the verbosity of the build system (eg. cmake) but not freebsd make itself 01:55:37 try this one something else, few days with somethimes error but it looks good https://websearchengine.net/?q=freebsd+port+build+verbosity 02:02:04 fury__: make -V ECHO_MSG ? 02:03:33 the resulting output is just "echo\n". no work is performed. 02:05:53 tuxy: unfortunately none of those results are at all helpful or ones that do not appear on Google searches. 02:08:27 I'm also having trouble overriding things in make.conf. if I manually edit this port's Makefile to include 'USE_PYTHON=distutils allflavors', things work as I (somewhat) expect - except that it's looking for an unknown file that doesn't appear. If I edit make.conf thusly: 02:08:52 .if ${.CURDIR:M*devel/boost-python-libs} 02:08:52 USE_PYTHON=distutils allflavors 02:08:52 .endif 02:09:05 it's as if make never sees this setting and doesn't respect it 02:09:16 and the change has no effect at all 02:10:13 (this is why I originally asked how to debug make.conf - I wanted to ensure my `.if` was being respected, but, it seems I'm doing everything correctly) 02:11:50 fury__: -V just prints the variable, it doesn't do any work 02:12:38 great. I still get "Need an operator" every time I try to use @{ECHO_MSG}. 02:13:03 how are you using it? 02:14:12 paste your shiz, man 02:14:13 eg.: @{ECHO_MSG} anywhere in a Makefile - at the top of it, at the bottom of it, in other blocks that use @{ECHO_CMD}, or anywhere in /etc/make.conf 02:15:10 i don't think you can do that, it needs to be in a target 02:15:40 ok. in a target has no effect, even in `pre-build:` - and I need to print to the console from make.conf. 02:16:14 that problem is secondary, though: I need to know which of the 627 'setup.py' files on my system it can't find 02:16:39 for that, I need make to output every command it is doing, which should be incredibly easy and very clearly documented 02:17:32 pre-build: 02:17:47 ^I@${ECHO_MSG} "wtf man" works fine for me 02:19:19 what I'm trying to do is `make FLAVOR=py311` in '/usr/ports/devel/boost-python-libs', because that python version is evidently not supported in the ports tree yet (although it should build fine). secondarily, I need to be able to modify make.conf to override USE_PYTHON to be "distutils allflavors", but just for this port. 02:21:53 lol, py311 doesn't even build on my system. 02:22:04 well "^I@${ECHO_MSG}" is very different from "^@${ECHO_MSG}", the latter of which is what is specified in the documentation, so, perhaps that's a documentation bug. 02:22:37 however, whitespace seems to be significant; I do get an echo if I use \t instead of spaces, so, that's progress 02:23:00 yes, makefiles use tabs. it is signficant 02:23:13 ^I = \t 02:24:32 so it sounds like that was on problem 02:25:09 ~20-year FreeBSD user here, did not know that hah 02:26:00 unless you've hacked on a makefile, it's probable you wouldn't be aware of it 02:26:20 (emacs editor colors wrong spaces in makefiles bright pink as an indicator) 02:27:18 ok, so, I can now see that make is respecting my make.conf changes, and while the USE_PYTHON variable is set by the time the `pre-build` step happens, it's not being respected or used unless it's in the actual Makefile and the changes to make.conf have no effect (but it works fine if I alter the Makefile) 02:27:38 and again, that problem is secondary: I need to know which of the 600+ 'setup.py' files it is not finding 02:28:22 re: hacking makefiles, I've just done a fresh `portsnap extract`, so, nothing is hacked. 02:28:40 hacked as in 'editing'. 02:28:54 understood. again, fresh `portsnap extract`, nothing edited. 02:29:13 aside from some currently commented-out lines. 02:30:35 i don't know flavors/ USE_PYTHON well enough to determine that 02:30:57 if you want to pastebin your build output for the setup.py mystry i can look 02:31:13 I think all you need to know is USE_PYTHON=distutils allflavors in the Makefile makes it able to detect my python version 02:31:22 ok 02:32:53 it may be a waste of your time, but, all that is needed to reproduce this is USE_PYTHON=distutils allflavors in /usr/ports/devel/boost-python-libs/Makefile and `make FLAVOR=py311` 02:33:36 the ultimate goal is to produce a make.conf change that can fix this issue 02:35:20 Python 3.10 has been out since October of 2021, and there's evidently no support for it in this port (or many ports, it seems), and, my team and I need to move on from 3.9 because the advantages of 3.10+ are significant. we have one dependency that relies on devel/boost-python-libs, and so, I need to be able to build it with FLAVOR=py310 (and FLAVOR=py311) from ports 02:35:56 i can't even build python311 so i don't know if i can duplicate that problem 02:36:42 well, either way, I don't think it's going to be helpful for you to run the same command as me and get the same output. I appreciate the input, but I really just need to know how to get `make` to print *EVERY* command it issues. 02:37:01 that should point me in the right direction 02:38:53 you might chcek out make -n or -N 02:39:09 you might have to manually recurse a bit but that might get you started 02:40:31 both produce the exact same output - a single line, and the output is not helpful at all. 02:40:54 Any of the 162108 could be invoking 'setup.py' 02:41:25 er, any of the 162108 files in this directory 02:41:39 is that single line something like cd /usr/ports/devel/boost-python-libs && make CONFIG_DONE_PY39-BOOST-LIBS=1 /usr/ports/devel/boost-python-libs/work-py39/.stage_done.boost-libs._usr_local 02:41:43 grep -R setup.py * shows a README.txt 02:41:50 so run make -n on that make 02:44:03 "Don't know how to make usr/ports/devel/boost-python-libs/work-py311...', or, the same exact output as naked -n if that argument is omitted. 02:44:34 sorry, there is a slash in front 'usr', lest you think it's a spelling mistake. 02:44:38 oh so your flavor is altering the workdir and that confuses it 02:44:58 there has *GOT* to be a way to get make to display every command it issues. 02:45:03 does that directory exist? 02:46:05 it does not, but, keep in mind that there are no Makefiles in this port. 02:46:42 ... 02:46:44 so, I will not be able to eg. invoke make from the work directory 02:46:58 instead, I need to know the exact commands that make is issuing 02:47:19 make extract should create it? does it not? 02:47:49 if you're unfamiliar with boost, it uses its own build system. it's quite nice and is better than cmake or make or gmake or whatever if you know how to use it, but, it doesn't use any Makefiles. 02:48:11 I have a work directory, but again, no makefiles. 02:48:18 i've used it; i wasn't super keen on it 02:48:28 but, the ports 'make' does something 02:48:35 after extract 02:49:51 sure. it extracts it to work-py311, applies patches, etc., but, no Makefile is ever available 02:49:58 cd .. 02:50:03 (er, woops lol) 02:50:08 you know, this would be a bit easier if you just pasted some output rather than transcribing or just describing what's happening 02:51:41 what output are you looking for? it's extremely minimal and doesn't contain much more than I've said 02:52:02 except for prompts, etc. 02:52:22 if there was more than one line of output, I'd maybe paste it if it was relevant 03:03:07 ===> Building for py311-cython-0.29.33 Unable to find pgen, not compiling formal grammar. 03:03:11 running build 03:09:39 so I'm just back to "I very simply need to know what commands make is invoking, as that will point me in the right direction." This should be incredibly easy. 03:10:20 I consider it a bug if it is either not easy, or not documented. 03:11:04 it appears it's neither 03:14:41 well obviously 03:14:55 but it sounds like you want boost build system to print out commands 03:15:22 perhaps, but, I'll start with make outputting the commands 03:15:31 which is clearly the first thing in the chain 03:16:09 and i told you how to do that 03:16:13 and neither of us know whether it's make or the boost build system issuing that command (it's very likely the former, but again, we'll see once I can see what make is doing) 03:16:29 and neither of us know whether it's make or the boost build system issuing that command (it's very likely the former, but again, we'll see once I can see what make is doing) 03:16:45 you did, but, `make -n` and `make -N` produce commands that do not work 03:17:03 then your build is broken 03:17:07 and reference files that do not exist by the time make exits 03:17:13 nothing on my system is "broken". 03:17:21 I frankly take offense to that. 03:17:43 I've just built this library on Windows of all places. it works fine. 03:18:10 the current issue is that I cannot get `make` to display the commands it is issuing. 03:19:24 I've been doing this a long time; were I able to see the commands being issued I'd be able to see what's going on. I cannot. That is frankly a bug. 03:21:07 ok, if it's printing commands that don't work, it's broken 03:21:29 it's printing commands that reference files that don't exist. 03:21:49 perhaps it deletes them after the make invocation (that should surely be another bug)? 03:23:41 i don't think so 03:23:56 go into your port; make extract; make -n and pastebin the result 03:27:27 https://bsd.to/OVm2 03:27:29 Title: dpaste/OVm2 (Plain Code) 03:29:39 as I said earlier, basically. make -n prints a command which does not work and references something that doesn't exist. 03:38:15 side note, `\t@${ECHO_MSG} "wtf man"` does not work *at all* anymore, it only worked the once. it has absolutely no effect. 03:38:30 (even after another fresh portsnap fetch extract) 03:40:16 the very worst experience you can have as a developer is something where you think something can happen, but the result is absolutely no effect at all. another bug. 03:47:36 it's a complicated system 03:47:52 fury__: if it was in pre-config, there's only one pre-config until you make clean 03:48:23 this is in pre-build, and, I already ran make clean 03:49:05 who knows if that portion of the Makefile is executing, though, becuase I cannot PRINT TO THE CONSOLE during it. 03:49:18 this is unbelievably frustrating 03:51:01 what should be an extremely simple issue to resolve is hampered by complete lack of documentation 03:51:01 i suspect you can't just toss around changes to USE_PYTHON like you're doing 03:51:59 well, perhaps, but again, if I could print to the console to debug, and if I could get make to output the commands it was be emitting, and if those things were documented, this would be a complete non-issue and we wouldn't be here. but here we are. 03:53:03 i'm looking at things printed to the console. 03:53:08 and, furthermore, USE_PYTHON is the documented way to tell make which flavors are availble (https://docs.freebsd.org/en/books/porters-handbook/book/ §5.11 Slave Ports and MASTERDIR). 03:53:10 Title: FreeBSD Porter's Handbook | FreeBSD Documentation Portal 04:05:24 ffs if I could even get it to invoke `python3.11 -v` as the python interpreter I could maybe get somewhere, but, I can't 04:07:23 `PYTHON_CMD+= -v` in Makefile produces "py311-boost-libs-1.81.0 depends on executable: -v - not found", another really bizarre bug 04:07:50 ALWAYS tell your user what they're doing wrong, and if you don't, you're the problem not the user 04:08:06 fury__: thing is, make has been around for 30 years 04:08:18 that's fine, document it 04:09:35 the search query "FreeBSD Makefile terminal output" on any search engine should have instrutions for this in the first result.FreeBSD" 04:09:57 woops. "in the first result" 04:10:31 ok, then write some documentation 04:10:54 26000 got made with this or lesser documentation 04:12:56 complaining on irc to a bunch of people who have mostly zoned out is not productive 04:13:09 I just wrote about 14KiB worth of documentation on how to build this on Windows. I'd love to. But, chicken-and-egg: I can't document this, as it's completely undocumented. I require two VERY simple things: printing debug messages from Makefiles (or make.conf), and, showing the commands that make generates. These two things are fundamental, and if they are missing, it is a bug. 04:14:09 I know. I'm venting, I appreciate your willingness to help and for being with me on this journey. I might have to make a mailing list post. I appreciate your patience and your company on this ride. 04:15:26 `make FLAVOR=py311` should have absolutely completed my journey here. It didn't, and, here we are. 04:26:58 if you're not super familar with the ports system from th businss end, this is probably not a great starter port to be modifying 04:28:19 it's a huge black box that reads your makefile and makes a port, unless you're quite familar with 12000 lines of port makefiles 04:28:42 i'm tring to bump one port a minor version and also am stuck 06:17:46 Hi 06:19:19 I have installed gtk-mixer and I think my USB mic is on /dev/mixer9 but I cannot speak in a meeting (ie mic not working). The sound (out) is working. I can see youtube etc. How can I fix this? 06:20:05 confirm the level of the mic and that it's not muted 06:25:11 rtprio https://imgur.com/W9jhe6e.png pulseaudio --version 06:25:11 pulseaudio 14.2 06:26:10 https://imgur.com/7NUHISs.png 06:27:35 rtprio https://imgur.com/N0QwDEn.png 06:31:33 rtprio do I need to do kldload snd_hda ref https://docs.freebsd.org/en/books/handbook/multimedia/#sound-setup 06:31:35 Title: Chapter 8. Multimedia | FreeBSD Documentation Portal 06:31:38 you want to look on the capture tab 06:32:07 rtprio surprisingly no capture tab in mixer9 06:32:24 when I unplug usb mic, mixer9 goes away 06:32:32 comes back as option when I plug in 06:32:37 so I guess thats the usb mic 06:32:58 rtprio that usb mic only has "playback" option. 06:33:17 maybe that is why its not recording/capturing 06:35:28 rtprio but cat /dev/sndstat 06:35:29 Installed devices: 06:35:29 ... 06:35:30 pcm5: (play/rec) default 06:35:30 ... 06:35:31 pcm8: (rec) 06:35:31 pcm9: (play/rec) 06:35:32 No devices installed from userspace. 06:35:43 pcm9 here says play/rec 06:36:04 but /dev/mixer9 has no rec in gtk-mixer (I am running as non-root user) 06:36:47 rtprio any ideas? 06:38:38 are you certain it's mixer9? 06:38:52 when I unplug usb mic, mixer9 goes away 06:39:29 try just `mixer` 06:40:55 rtprio https://termbin.com/0r9mq 06:42:58 mixer -f /dev/mixer9 mic.recsrc=+ 06:47:32 rtprio mixer: unknown device: mic.recsrc=+ 06:47:32 usage: mixer [-f device] [-s | -S] [dev [+|-][voll[:[+ 06:47:33 .. 06:47:33 devices: vol, pcm 06:58:48 mixer -f /dev/mixer9 -s 07:01:24 rtprio /dev/mixer9 -s 07:01:25 vol 100:100 pcm 100:100 07:01:47 it doesn't look like that particular mixer supports rcording 07:01:58 is thre a mixer8? 07:02:04 am.. but I was using that mic on linux before. 07:02:15 there is mixer 8 too 07:02:26 mixer -f /dev/mixer8 -s 07:03:03 mixer -f /dev/mixer8 -s 07:03:04 mic 100:100 07:03:41 https://imgur.com/3qk32Js.png 07:03:49 that's the one to use for recording then 07:06:08 rtprio but it stays there if I unplug, also no sound goes through . HOw can I check? 07:06:40 mixer -f /dev/mixer8 mic.recsrc=+ 07:06:55 that should enable the mic 07:08:27 rtprio mixer: unknown device: mic.recsrc=+ 07:08:28 usage: mixer .. 07:08:29 devices: mic 07:10:26 i don't know man, i don't use sound; read `man mixer` again 07:23:38 rtprio I found the issue. It is using mic of mixer5. How can I undo it and use mic of mixer8/9? 07:27:38 strange that this isn't working either `mixer -f /dev/mixer8 +=rec mic` 07:31:13 fury__: how about you read makes documentation and find the -d flag that lets you debug the build as much as make can let you, you probably want loud mode as a first step 07:32:15 How do I change my recording device? 07:33:40 I am trying to update a port but receive "[00:00:01] Error: Nonexistent origin net/sfwbar". Any ideas please? 07:36:17 mixer -f /dev/mixer8 =rec mic 07:36:17 what is wrong with this ? 07:43:11 https://forums.freebsd.org/threads/internal-microphone-setup-question.77091/ 07:43:12 Title: Internal microphone setup question | The FreeBSD Forums 07:43:15 simply not working for me 07:43:25 nor this tiny doc https://man.freebsd.org/cgi/man.cgi?mixer(8) 07:43:26 Title: mixer(8) 07:45:18 these commands work for mixer5 but not mixer8/9 07:45:24 so driver issue? 07:54:02 now I have the error "[00:00:00] Error: No such ports tree development". Any ideas please? 07:55:17 elgrande: where are you seeing that one 07:55:38 did you poudriere -c -p development … before? 07:56:51 and to your nonexistent origin from before: are you really trying to update it? I can't see net/sfwbar in my copy of the portstree 08:00:54 One or more devices has experienced an unrecoverable error. An 08:00:54 attempt was made to correct the error. Applications are unaffected. 08:00:55 action: Determine if the device needs to be replaced, and clear the error 08:00:55 errors: No known data errors 08:01:18 zpool status -v ^ 08:56:12 Putittali: what's smartctl say? 09:01:35 meena says https://termbin.com/bgwf 09:06:21 the only thing i see is unsafe shutdowns 09:07:09 yes and 6% use in 150 hrs 09:08:18 that's not much use. maybe it's bored? 09:09:40 ok :) 09:10:32 # mount /dev/nvd0p3 /home/user1/nvme0/ 09:10:32 mount /dev/nvme0p3 /home/user1/nvme0/ -> mount: /dev/nvme0p3: No such file or directory 09:10:33 # ls /dev/ |grep p3 -> ada1p3 dsp3.0 nvd0p3 nvd1p3 nvd1p3.eli 09:10:33 mount: /dev/nvd0p3: No such file or directory 09:10:34 https://termbin.com/rwzq 09:10:36 gpart^ 09:12:36 I'm reminded of those MFBF graphs: they're bathtub shaped, so 150 hours of operation for the first instance of failures to show sounds reasonable 09:13:21 How do I know what FS is it? 09:16:40 I installed https://www.freshports.org/sysutils/fusefs-lkl but cannot mount a partition that may be LUKs or BTRFS. What can I do? 09:16:41 Title: FreshPorts -- sysutils/fusefs-lkl: Full-featured Linux BTRFS, Ext4, XFS as a FUSE module 09:18:34 is the fuse kernelmodul loaded? 09:19:05 how do I know? 09:19:21 kldstat 09:20:07 nimaje grep fuse don't show anything 09:20:40 nimaje how do I load it? 09:25:30 kldload fusefs-lkl 09:25:31 kldload: can't load fusefs-lkl: No such file or directory 09:25:40 kldload fusefs.ko 09:26:18 kldload fusefs.ko loaded it 10:30:30 why is https://cirrus-ci.com/task/6091282020302848 running on 13.1-RELEASE despite the pull request is against main? 10:30:31 Title: Cirrus CI 11:40:08 elgrande: why not? 11:51:00 elgrande: the kernel build *of* (your patch of) main is running *on* 13.1-RELEASE 11:51:47 it's nice to be able to build CURRENT on a supported RELEASE, don't you think? 12:02:25 can anyone loop me in on what the latest re: openssl is around QUIC support, the v1->v3 shift, and kTLS? my understanding so far is openssl v1.1.1 is EOL this year, v3 breaks a lot of things, and OpenSSL is implementing their own QUIC that'll take half a year more. however, only OpenSSL has kTLS 12:04:30 is anyone using one of the alternative libs like boringssl, wolfssl, libressl, etc? do I keep kTLS with security/openssl-quictls? 12:09:32 domlaut: FreeBSD CURRENT has https://cgit.freebsd.org/src/log/?h=vendor/openssl-3.0 12:09:35 Title: src - FreeBSD source tree 12:09:53 oh, so freebsd is migrating to openssl 3 12:10:36 that, rather than 3.1, i reckon, is likely going to be what's will go into 14.0-RELEASE 12:11:18 we also have bearssl: https://cgit.freebsd.org/src/log/?h=vendor/bearssl 12:11:20 Title: src - FreeBSD source tree 12:11:20 yeah, on the QUIC thing, I don't think anything <3.4 will be all that useful to me (that's when they expect it 'done' IIRC) 12:11:50 not sure if that's got anything to do with kTLS, but it's used in the loader 12:12:31 loader? 12:13:47 the thing that loads the kernel 12:14:18 https://man.freebsd.org/loader(8) 12:14:19 Title: loader(8) 12:17:14 ah, thanks. interesting choice 12:19:15 well, it's absolutely tiny, so it's probably the most sensible choice (given that we also have to consider licenses;) 12:22:01 yuripv: I had expected that 14 is build on 14, but I did not know anything about it. 12:22:16 s/build/built/ 12:23:06 meena: so it is build in a jail, right? 12:24:13 elgrande: i don't think so https://github.com/freebsd/freebsd-src/blob/main/.cirrus.yml 12:24:14 Title: freebsd-src/.cirrus.yml at main · freebsd/freebsd-src · GitHub 12:25:31 meena: so it is crosscompiled for each platform under 13amd64 or under a separate 13 platform for each arch? 12:26:33 meena: yeah, I'm working with streaming stuff over the internet so my set of requirements is different (stuff like needing DTLS, etc). unfortunately due to how building the system works is I can only link against one ssl library for ingesting/broadcasting/serving static files/all of it :-) 12:27:14 so it seems what I'll have to do is depend on openssl 3 and then do static linking of boringssl/quictls/libressl just for quic 12:31:02 elgrande: not for each arch… only for the Tier 1 archs: amd64 & aarch64, but with different compilers 12:31:38 which compiler is used on aarch64? 12:32:21 read the thing, my brain is bleargh right now 12:32:41 I don't want to :) 12:33:09 well, i can barely read even when my brain isn't bleargh 12:40:17 what is the "correct" way to have neovim to be used instead of vim ( nvim instead of vim ) 12:40:21 if I don't have a vim installed 12:40:37 on debian there is something called /etc/alternatives which manages links to alternative binaries 12:40:52 in freebsd I just symlink nvim to vim and case closed or is there alternative to debian alternatives? 12:41:01 ... 12:42:11 merp: we don't really have such a system in place 12:42:51 so, yes, just add a symlink 12:43:49 and I did, thanks 12:55:08 Does anyone of you use a Yubikey with Firefox? 13:07:40 Hi 13:08:25 GELI encrypts disks while OpenZFS encrypts datasets . Which one I need? I heard there are issues with latter https://gist.github.com/rincebrain/622ee4991732774037ff44c6768085ab. What is the best way to a) formate and then b) encrypte a zfs in linux? is it any different than a *bsd ? 13:09:09 Latiute: geli is full disk encryption, like linux's LUKS. it's bsd only. zfs can run on top of the geli container. 13:09:19 zfs has encryption, but some metadata isn't encrypted, just the data. 13:09:28 that's very new 13:09:31 linux is openzfs, too 13:09:54 yeah 13:11:05 Demosthenex elgrande so geli is stable enough? also at installation time, what technique does zfs uses to encrypte drive? geli? 13:11:35 No. 13:11:43 geli has nothing to do with ZFS 13:11:48 I see 13:11:51 I have heard that there any more than one encrytption methods for zfs 13:11:57 how is the drive encrypted then? 13:12:07 Latiute: geli's fine. and if you use the installer and select encryption, it will setup zfs on a geli partition 13:12:14 symetric 13:12:18 it is FDE - full disk encryption, dealing with your disk blocks 13:12:37 you can install ZFS or UFS over it 13:12:44 Demosthenex what does the freebsd installer do/use at installation time encryption? 13:12:53 it uses geli 13:12:58 I see 13:13:14 so symtric fde 13:13:36 can I use geli in linux? Actually I am backing up data from btrfs drive to zfs drive (yet formated and to be used on freebsd ) 13:13:45 No. 13:13:45 *installer* can not offer anything else than geli, because we have not teached boot loader to grok zfs encryption yet. 13:13:48 you can use zfs in linux 13:13:49 Latiute: installer does root zfs on geli 13:14:11 angry_vincent no means i cannot use geli on linux 13:14:15 Demosthenex elgrande I see 13:14:21 Latiute: that's right, geli cannot be used with linux 13:14:28 manual installation does not provide encryption 13:14:30 no means you cannot 13:14:31 Latiute: linux uses LUKS 13:14:35 so my only stable option is to not use encryption 13:14:43 that would work on both linux and bsd 13:14:51 ya, bsd has no support for lUks 13:14:55 iirc 13:14:55 perhaps. you need similar zfs versions. 13:15:04 i wouldn't bet on sharing a disk between bsd and linux ;] 13:15:06 * Latiute only wants zfs 13:15:20 Demosthenex well just a one timer data transfer 13:15:45 sure. consider making your final storage geli on zfs, and just unencrypted zfs for the transfer 13:15:47 so in summary, zfs dataset encryption is NOT be used as its not so stable yet? 13:15:54 alternatively, look into zfs send/recv 13:16:17 it's new, and both bsd and linux have different support for it 13:16:37 which one is new and both l...? 13:16:45 like angry_vincent said, you can't boot with encrypted zfs for root because the bootloader doesn't understand zfs encryption. but you may for a data disk 13:16:49 Demosthenex rest udnerstood 13:17:04 Latiute: both. it's a new feature, and depends on what version of zfs bsd and linux are synced to 13:17:24 either way, for stability, i'd use LUKS+zfs on linux, or geli+zfs on bsd for now 13:17:29 both geli and zfs enc dataset? 13:17:39 No 13:17:43 without zfs encryption 13:18:20 one let me wrap: consider making your final storage geli on zfs, and just unencrypted zfs for the transfer <-- understood 13:18:26 for your data migration, look at zfs send/recv 13:18:51 either luks + zfs be used or geli+zfs. But not zfs dataset encrytion. Correct? 13:19:10 yep 13:19:13 Demosthenex first I have to foramte a drive. Then copy data into that froma a btfs drive 13:19:38 then maybe zfs.send() somewhere 13:20:00 oh, well that's right, if its btrfs to zfs, send/recv won't help 13:20:04 . What is the best way to a) formate and then b) encrypte a zfs in linux? is it any different than a *bsd ? 13:20:13 sorry 13:20:14 ignore b) 13:20:26 zfs encryption can be used with data pool. That is, pool without boot disk(s). 13:20:43 most folks say setup a partition table and then add zfs 13:20:51 i say use the disk raw, no partitions 13:20:53 tsoome yes but we just discussed that zfs encryption of dataset is not so stable 13:21:19 Demosthenex me too. I want to use raw disk too. do you know how exactly to do it? 13:21:33 Demosthenex I know its 1-2 commands onlinux but I am very confused from different articles from internet 13:21:39 have you done that before yourself? 13:21:44 Latiute: on bsd make a geli on the block device for the drive, ie: /dev/da1 13:21:46 or have any idea? 13:21:51 just a sec 13:22:06 you made it? 13:23:23 https://dpaste.org/mRn9n 13:23:24 Title: dpaste/mRn9n (Python) 13:23:34 i may have missed the geli attach call though 13:23:50 Demosthenex well that is ok. Will be useful at when I am on bsd but for now I have to read btrfs and bsd can't do that with luks encrypted btrfs drive. For that I have to use linux. In linux I can't have geli. So need simple zfs drive 13:23:51 it's geli init each disk, geli attach to open them, then zpool create 13:24:13 so how to formate a drive and create zfs in it 13:25:42 that paste 13:25:47 was when i setup my new server 13:26:02 i installed my OS to 2 ssd's, that was done by the installer 13:26:20 the paste is where i built a 4 disk RAIDZ ZFS on GELI 13:26:23 without partitions 13:26:32 what is the maximum compression comand instead of zpool create -O compress=lz4 -O atime=off -f zdata raidz da2.eli da3.eli da4.eli da5.eli 13:26:53 there are newer compressions, but i'm using an older one 13:31:40 zstd 13:33:32 is thsi ok zpool create -O compress=zstd ssd1 /dev/sda 13:34:13 Demosthenex ^ 13:34:18 if you want max compression, you probably want to read about zstd;) 13:34:45 elgrande VimDiesel I had a lot of issue sand work stuck. So don't want ot make mistakes after ready docs/blogs as an inexperienced person 13:35:10 tsoome yes, I have been using that in btrfs too. its nice 13:35:25 tsoome is the command I gave you correct and ok? 13:35:33 zpool create -O compress=zstd ssd1 /dev/sda 13:35:36 yea, I mean, compression=zstd will not give you maximum 13:35:45 oh it will not?then what will? 13:36:31 Latiute: honestly, use some compression, but don't worry about "max" 13:36:48 Demosthenex its for backup 13:36:50 need max 13:36:51 https://forums.freebsd.org/threads/thoughts-on-zfs-compression.80217/ 13:36:53 Title: ZFS - thoughts on zfs & compression | The FreeBSD Forums 13:37:05 tsoome ^ 13:37:33 sudo zpool create -O compress=zstd ssd1 /dev/sda 13:37:34 invalid vdev specification 13:37:34 use '-f' to override the following errors: 13:37:59 see zfsprops(7), it does explain 13:40:45 tsoome zst-1000 then :) You can specify the zstd level by using the 13:40:46 value zstd-N, where N is an integer from 1 (fastest) to 19 (best 13:40:46