<clever>
BlessJah: and you dont have to deal with the fine pitch of a cpu or the high freq
<clever>
BlessJah: so you could just take any small-ish lcd panel, a mini (or custom) usb keyboard&joystick/mouse, 3d print a case, slap in a pcmcia socket, and you can jam in an existing EOMA module for the processor
<clever>
BlessJah: the interface has the following things: sata, ethernet, usb, 18/24 pin RGB LCD, MMC, SPI, I2C,
<clever>
BlessJah: none that i know of right now
<clever>
YegorTimoshenko[: yeah
<clever>
sphalerite: this isnt as insane :P
<clever>
BlessJah: so the entire laptop body/screen/keyboard can be reused when you switch to that fancy new RISC chip thats coming out
<clever>
BlessJah: more that you replace the entire creditcard with a new module, but you can reuse everything else
<clever>
nixer101: every system generation is a root, and there are some other roots for other things
<clever>
nixer101: it has to be given an extra flag like -d or --delete-older-than, and ran as root, to delete those
<clever>
nixer101: by default, nix-collect-garbage doesnt remove the roots, so you can undo things still
<clever>
nixer101: so generation #1 and #2 of nixos had version 27.4.2, and nixos is keeping them incase you want to undo removing it
<clever>
nixer101: what does this command say? nix-store --query --roots /nix/store/pwplsdk340pad0irimfvmm0kxkxd3ail-palemoon-27.4.2
<clever>
nixer101: nix is only checking the links under /nix/var/nix/gcroots/
<clever>
nixer101: the rollback generations in your profile kept those versions around by chance
<clever>
nixer101: just delete those files and it should fix the issue
<clever>
nixer101: and thats now persisting, and making that old version, the default version
<clever>
nixer101: it looks like palemoon created those files when you ran it, to flag itself as the default browser
<clever>
jonge: i think nix can still be used in the same store though, but ive not looked into guix that much
<clever>
jonge: i think guix just doesnt have the allowUnfree flag, and doesnt allow unfree software
<clever>
nixer101: can you pastebin the contents of the 2 palemoon files?
<clever>
nixer101: do any palemoon files exist in /home/userp/.local/share/applications?
<clever>
jonge: from what ive heard, it uses a different language in place of nix, but still uses the same .drv files and daemon, and focuses more heavily on only open-source software
<clever>
nixer101: do you see it in one of these directories? ~/.local/share/applications ~/.nix-profile/share/applications/ or /run/current-system/sw/share/applications/
<clever>
nixer101: how are you starting palemoon?
<clever>
nixer101: just run it as your normal user
<clever>
nixer101: what does "type palemoon" say?
<clever>
nixer101: nix-env -q
<clever>
yeah, all untracked files
<clever>
-o appears to invert the action
<clever>
Dezgeg: not sure what it will do if a file is in both .gitignore, and the git index
<clever>
fearlessKim[m]: cleanSource should deal with .git already, maybe build?
<clever>
fearlessKim[m]: nothing that i know of, but you can still focus on just making the tree smaller, why is the directory so big that it runs out of memory?
<clever>
it needs a patchelf like tool, that goes by a different name
<clever>
i dont know much about how to package pre-built software on darwin
<clever>
if you have a darwin version of the above url, nix could be updated, but brew is probably simpler
<clever>
so it can only ever produce linux binaries
<clever>
ldlework: its hard-coded to download a pre-built linux binary, and patchelf it
<clever>
ldlework: allowBroken wont work
<clever>
cannot coerce null to a string, at /home/clever/apps/nixpkgs/lib/strings.nix:85:38
<clever>
error: while evaluating the attribute 'buildPhase' of the derivation 'dotnet-sdk-2.0.3' at /home/clever/apps/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:148:11:
<clever>
[clever@amd-nixos:~/apps/nixpkgs]$ nix-build -A dotnet-sdk --argstr system x86_64-darwin --arg config '{ allowBroken = true; }'
<clever>
ldlework: what happened when you tried to nix-env -i it?
<clever>
error: Package ‘dotnet-sdk-2.0.3’ in /home/clever/apps/nixpkgs/pkgs/development/compilers/dotnet/sdk/default.nix:48 is not supported on ‘x86_64-darwin’, refusing to evaluate.
<clever>
[clever@amd-nixos:~/apps/nixpkgs]$ nix-build -A dotnet-sdk --argstr system x86_64-darwin
<clever>
[clever@amd-nixos:~/apps/nixpkgs]$ ls result/bin/dotnet -lh
<clever>
copying path '/nix/store/63rsl125qchsggnk7dnr825kj0bzikzp-dotnet-sdk-2.0.3' from 'https://cache.nixos.org'...
<clever>
after checking out the latest master, on linux
<clever>
[clever@amd-nixos:~/apps/nixpkgs]$ nix-build -A dotnet-sdk
<clever>
ldlework: you may have some luck using nix-index and nix-locate on darwin
<clever>
ldlework: ah, it may have different contents on osx
<clever>
ldlework: on?
<clever>
if i have root on any hardware, i can convert it to nixos in under an hour :P
<clever>
thebardian: so you can just unpack the tar to /, run /kexec_nixos, and now nixos is running entirely from ram
<clever>
thebardian: also, the kexec.nix in the same directory, generates a tarball containing kexectools, a kernel, and initrd (which contains a rootfs, and justdoit)
<clever>
thebardian: and it can be pre-installed into the iso image, so you simply boot and run justdoit, lol
<clever>
thebardian: that script does the entire install, from formating the disk to nixos-install
<clever>
as in, what command would you run on a shell?
<clever>
what is the binary called on most distros?
<clever>
ldlework: which command do you want to run on the CLI?
<clever>
you cant even buy things that small nowadays
<clever>
fearlessKim[m]: so, i opted to put /boot onto a 64mb usb stick, lol
<clever>
fearlessKim[m]: for my zfs based nas with a 3 drive raid array, i wanted to avoid stealing 512mb for /boot, because then i loose 512mb on all 3 drives
<clever>
so you can always switch to stable if you have problems
<clever>
and you are free to change an install between channels whenever you want
<clever>
the nix-channel man page explains how to add/remove channels
<clever>
and if nixos is configured properly, it will do `cryptsetup open` on bootup
<clever>
with those 2 commands, you can make a luks protected block device, and then format it with any FS of your choosing
<clever>
`cryptsetup open --type luks /dev/sda2 rootfs` will create a /dev/mapper/root that points to the un-encrypted block device, and ask for the passphrase
<clever>
`cryptsetup luksFormat /dev/sda2` will create a new luks volume, and ask for a passphrase
<clever>
so you have several ways to unlock it
<clever>
luks will then use that master key for the actual drive encryption
<clever>
and all of those entries contain an encrypted copy of the same thing, a master key
<clever>
each entry can be encrypted differently (passphrase, keyfile, maybe smartcard?)
<clever>
mfiano: at the lowest level, the luks header contains a list of entries
<clever>
mfiano: but if i just want to boot ubuntu or windows without any fuss and fancy config, i use virtualbox
<clever>
mfiano: in general, i prefer qemu for most things, its better documented, more flexible, and open source
<clever>
though then you loose paravirtual some
<clever>
fearlessKim[m]: another option is to pass grub to -kernel, and then let grub read the config files, or just use a legacy MBR
<clever>
fearlessKim[m]: and if you lack an initrd, the kernel must support the rootfs
<clever>
318 also does similar things
<clever>
i think 562 then appends all kernel params
<clever>
which resulted in an unexpected hash in the url from the errors, and all the hashes we gave failing
<clever>
abathur: and we where editing the wrong one, because the --show-trace was clipped to omit the key detail
<clever>
abathur: when i was helping to fix that reflex-platform fetchnixpkgs issue, there was 2 fetchNixpkgs.nix files
<clever>
abathur: it also needs to be programed to detect users giving false answers to questions
<clever>
so they dont have to ask the same stuff
<clever>
gchristensen: and also to record the answers for a ticket that can be passed up to tier2
<clever>
gchristensen: something ive been wanting to find is a good tier1 support bot, you just give it a tree of questions&answers, with some invisible questions based on past state, and then it can be programmed to solve basic problems
<clever>
not sure about the state of the current one
<clever>
the last wiki was shutdown due to spam
<clever>
which is why the 2nd fault never came out
<clever>
that fault causes it to use the 1.11 method on 1.12pre
<clever>
michalrus: the test is only broken for 1.12pre, it works fine for 2.0
<clever>
michalrus: pass it 2 hashes, one from `nix-prefetch-url` and the other from `nix-prefetch-url --unpack`
<clever>
michalrus: yeah, i think i see the problem
<clever>
michalrus: i have some thoughts, checking...
2018-02-28
<clever>
MichaelRaskin: so shells i leave open on nfs dirs just break randomly
<clever>
MichaelRaskin: and nfs doesnt remount cleanly enough to restore that
<clever>
MichaelRaskin: ive found the systemd auto-mount stuff to not be aware of the working directory for processes
<clever>
sphalerite: basically, the nix-daemon will need to setup a listening unix socket in the build sandbox, and proxy multiple bytestreams back to the nix-build process that initiated the build
<clever>
sphalerite: to solve what i just said, i'm thinking there could be a util that accepts queries on stdin, and prints answers to stdout, and keeps its nix-daemon socket open
<clever>
each query process has to connect to the daemon, which initiallized an entire tempdir and a bunch of state, then tears ti down
<clever>
for example, for x in /nix/store/*; do nix-store --query --size $x ; done is horid slow
<clever>
also, ive wanted more of a repl to the daemon for things
<clever>
ahh
<clever>
sphalerite: nix also saves all logs in /nix/var/log/