| 10 Sep 2024 |
| @shinri:zince.net left the room. | 12:37:47 |
colemickens | no no | 14:57:14 |
colemickens | so the issue is that there's a module option for memSize, that is ignored in the impure/script route. | 14:57:29 |
colemickens | I can try to remember to send a small patch for that. | 14:57:38 |
colemickens | The postVM example is also ... wrong (you can't glob like that in a script), and ALSO a bit scary, because the script just clobbers $out/disk0.raw, no matter what is there, and worse, if the globbing worked, would just hit every "*raw" in whatever $out happens to be. | 14:58:30 |
colemickens | But also, yeah, it would be cool if it didn't use up a fair bit of ram just running 'cp' :) | 14:59:03 |
colemickens | * The postVM example is also ... wrong (you can't glob like that in a script), and ALSO a bit scary, because the script just clobbers $out/disk0.raw, no matter what is there, and worse, if the globbing worked, would just hit every "*raw" in whatever $out happens to be. (In "impure" $out is just where you run the image script from!) | 14:59:43 |
matthewcroughan | In reply to @colemickens:matrix.org But also, yeah, it would be cool if it didn't use up a fair bit of ram just running 'cp' :) the image builder occasionally ooms still to this day I think | 15:23:07 |
matthewcroughan | it's not very reproducible, just happens sometimes | 15:23:13 |
matthewcroughan | maybe we could replace xargs and cp with rust based things and see if it still happens | 15:24:16 |
matthewcroughan | There is rargs and fcp | 15:24:46 |
matthewcroughan | * There is rargs and fcp both written in rust | 15:24:54 |
matthewcroughan | * There is rargs and fcp or cn, both written in rust | 15:25:08 |
matthewcroughan | * There is rargs and fcp, both written in rust | 15:25:57 |
matthewcroughan | There's also https://github.com/uutils/coreutils | 15:27:50 |
matthewcroughan | IDK, I've played with 10,000+ arguments in xargs before, you run out of some limit like the stack size limit | 15:29:39 |
matthewcroughan | maybe rsync is a better idea than cp? | 15:29:56 |
colemickens | That's what I was surprised at too, I'd expect to have hit max cmdline size with the args. | 15:30:05 |
colemickens | Maybe? | 15:30:07 |
colemickens | Not really on my list to dig into beyond maybe filing an issue. | 15:30:23 |
matthewcroughan | hard to say, but it's really good to find that this might be the place where the issue is occurring | 15:30:28 |
colemickens | BTW, I gushed a bit in the ARM room, but disko is really nice, thanks y'all! | 15:30:39 |
Tumble | I wonder if I can happily forget fdisk now? | 15:42:26 |
colemickens | I only had to use it to sanity check! :) | 15:57:23 |
| moved to @amadaluzia:tchncs.de changed their display name from (lambda (u) (format nil "~A lost their email!" u)) "Artur Manuel" to Artur Manuel (on break). | 17:32:31 |
| moved to @amadaluzia:tchncs.de changed their profile picture. | 17:34:53 |
| moved to @amadaluzia:tchncs.de changed their display name from Artur Manuel (on break) to (lambda (u) (format nil "~A is not using Matrix right now." u)) "Artur Manuel". | 17:36:31 |
| 11 Sep 2024 |
mannp ⚡️ | Hi all. I am using disko on the root disk on quite a few machines now and its worked well. I am wondering if after adding a separate 2g "data" disk I can add that to my disko config, and it will too get formatted as per the defn. Is that something that is supported? Thanks. | 13:59:36 |
lassulus | you would have to run disko manually for that to work, there should be support now for incremental updates, but that is very new and can cause data loss. so do that with care :) I can you can also just run the commands for the new disk manually by inspecting the generated script | 14:08:57 |
mannp ⚡️ | I see, thanks for the quick response, just adding context in case it matters, I am using luks and btrfs for my main disk and have created the defn for luks and btrfs with one subvol /storage device in disko, but I am not sure if I am going to wipe out my main boot disk too 🙂 | 14:19:46 |