<clever>
if you set nixpkgs.system, it could also deploy to an arm
<clever>
it just requires an x86-64-linux build slave to do the builds
<clever>
Miyu-chan: given that nixops works on a mac already, it should work with an arm client too
<clever>
nyanloutre[m]: nix-store --delete, dont force it
<clever>
sphalerite: ive heard horror stories about SSD's not handling trim properly
<clever>
pie_: it may be the pattern of syncs and random writes that zfs does
<clever>
which improves write performance
<clever>
some high end camera's have also gotten flack, because they dont let you erase a single clip, then only let you blkdiscard the whole ssd at once
<clever>
that lets you boost write performace short-term
<clever>
pie_: and if the ssd is brand new, or about to be sold, you should probably run blkdiscard on it, WARNING, IT WILL WIPE THE DISK
<clever>
so that lets it pre-erase a large chunk of the disk
<clever>
and erasing ssd blocks is a large chunk of write time
<clever>
pie_: if trim is enabled, and doesnt malfunction, it will tell the SSD to erase any blocks that zfs isnt using
<clever>
so you wont get metrics like this
<clever>
Percentage Used: 23%
<clever>
SMART/Health Information (NVMe Log 0x02)
<clever>
yeah, definitely not nvme
<clever>
pie_: what does iostat call it?
<clever>
pie_: sata ssd or nvme ssd?
<clever>
pie_: one min
<clever>
pie_: ive had the same question
<clever>
srhb: but if you have a foo.nix, that is only in imports on foo, there is no need for it to be conditional
<clever>
pie_: was the ssd previously used, or brand new?
<clever>
any shared stuff can just be imports = [ ./shared.nix ]; in both of them
<clever>
marek: simpler answer is to just have 2 files, and choose which one you put into imports = [ ./foo.nix ];
<clever>
which end has a higher util% in `iostat -x 30` (wait for the 2nd sample)
<clever>
first, you need to figure out if its read or write throttled
<clever>
it just hasnt found enough cachable data to cache
<clever>
its only using 2.5gig for you, but it wants to use 4.8gig
<clever>
it will dynamically change the goal, based on how much is free
<clever>
pie_: i never set arc max, and it automatically limited itself to 1.4gig
<clever>
pie_: zfs will never use more then 50% of the ram by default
<clever>
362be9608c3 is what i'm testing the fix on
<clever>
kalbasit: still building!
<clever>
kalbasit: maybe the new muslc stuff...
<clever>
yep
<clever>
ERROR: Got argument default_library as both -Ddefault_library and --default-library. Pick one.
<clever>
checking that rev...
<clever>
ah, but i can reproduce this if i use a newer nixpkgs temporarily
<clever>
trace: warning: The option `boot.binfmtMiscRegistrations' defined in `/home/clever/apps/nixos-configs/qemu.nix' has been renamed to `boot.binfmt.registrations'.
<clever>
arianvp: youll either want to fix nixpkgs to support the android ndk, or fix nixpkgs to support aarch64 muslc
<clever>
arianvp: and anything built normally with nix expects a /nix/store/, so you either need to do some funny stuff to make the libraries co-operate with /system/lib/ or just go full static
<clever>
arianvp: android doesnt obey the FHS, and all the libraries are in /system/lib i believe
<clever>
arianvp: pkgsCross.muslpi will cross-compile static armv6l binaries, which can then run on most android devices
<clever>
arianvp: this is the only option i can see existing right now, armv7 would be better but i dont see a preset entry for it
<clever>
> pkgsCross.muslpi.hello
<clever>
zeta_0: which is already in PATH, just run `cheatsheet`
<clever>
zeta_0: home-manager installs the packages to ~/.nix-profile/bin/
<clever>
zeta_0: if you run the cheatsheet binary in bin, it will tell you where to find the pdf
<clever>
petercommand: cant think of anything else to check
<clever>
petercommand: doesnt look like youve done anything wrong
<clever>
petercommand: you may need to run yarn outside of nix to update the lock file
<clever>
petercommand: maybe its not in the yarn.lock file?
<clever>
petercommand: yarn --offline
<clever>
that allows the build slaves to use their own cache config
<clever>
246 extraOptions = ''
<clever>
250 builders-use-substitutes = true
<clever>
213 nix = {
<clever>
averell: one sec...
<clever>
zeta_0: any package in nix can have multiple outputs, which can be GC'd independently
<clever>
> "${haskellPackages.CheatSheet.data}"
<clever>
> haskellPackages.CheatSheet.outputs
<clever>
zeta_0: split output packages
<clever>
the rpath on the binary must be modified before it can run
<clever>
zeta_0: $data has the pdf in it, but there is no easy way to access it, but that path will be in the Paths_CheatSheet.datadir :: String, which the code may make use of
<clever>
zeta_0: the $out has a bin/cheatsheet so you could probably run that binary
<clever>
__monty__: can you gist your current nix expr?
<clever>
iqubic: all of nixpkgs, search it for makeWrapper
<clever>
iqubic: it has to be added to PATH using makeWrapper
<clever>
iqubic: makeWrapper
<clever>
detran: youll need to override part of closure to use jdk11, check the default.nix for closure first
<clever>
detran: run `nix-store -qR` on the path of the closure binary
<clever>
you could do similar to get just gcc and clang, without the many utils they also contain
<clever>
this is how i get just strings and readelf, without getting all of binutils