<clever>
it will -9 every process in the user it picks
<clever>
and you must not put your own user into the nixbld group
<clever>
hegemoOn: if you run nix tools as root, they will automaticaly drop privs down to a member of the nixbld group
<clever>
hegemoOn: you need to put build users like nixbld1 into the nixbld group
<clever>
joko: i just aim a hydra configured for native builds at my raspberry pi and then leave it for a week
<clever>
joko: and the hashes dont match up, so the first time you try to nix-env -i, it will want to re-build everything from gcc and up
<clever>
joko: some packages dont like cross-compiling, so you cant build the entire OS via cross-compile
<clever>
joko: both methods of cross-compiling would have their own hashes, and it would also differ from natively building the same expression on the target platform
<clever>
simukis: ah, ive done a mingw with libc before, but havent tried powerpc or mips
<clever>
simukis: what cpu do you need a compiler for, and does it need to have a libc or just kernel level stuff?
<clever>
then you dont need to maintain your own clone of nixpkgs
<clever>
you can also copy the default.nix for it into a packageOverride in config.nix
<clever>
joko: nixos-rebuild will overwrite the file with a symlink at the next switch
<clever>
joko: one thing i sometimes do, copy the contents of /etc/nix/nix.conf to a new file, delete the symlink, then rename the copy back to nix.conf, and edit it freely
<clever>
inflames: are you on nixos or another distro?
<clever>
you would need to create a dummy entry under ~/.nix-defexpr/ if you want to cease using channels
<clever>
but -f '<nixpkgs>' will force it to use the search path
<clever>
it uses ~/.nix-defexpr/ instead
<clever>
tilpner: nix-env is one of the weird tools, it will make no attempt to use the search path by default
<clever>
and a nixos system wouldnt use -iA nixpkgs.
<clever>
tilpner: the nixos service for syngery is currently broken
<clever>
inflames: and the server needs a config file that describes the layout of the screens
<clever>
inflames: you need to run synergs on the server and "synergyc <serverip>" on the client
<clever>
though you may need to tweak the bootloader
<clever>
this is a generic arm image Dezgeg has made, that will probably boot on most arm boards
<clever>
main issue is a lack of binary cache support, so it takes a week or 2 to recompile everything on channel updates
<clever>
hodapp: i have ran armv6l and armv7l builds of it on my pi's
<clever>
simpson: depends on if you want to use it as a nixos machine, or specialize it for just one task and leave it to run forever
<clever>
simpson: i have also ran full nixos on some raspberry pi's so that is also an option
<clever>
hodapp: ah, that would do it
<clever>
simpson: main thing to keep in mind, is that it lacks the nix package manager, so you cant just rebuild-switch, you have to nix-build an image elsewhere, and re-flash whatever hdd its booting from
<clever>
simpson: and depending on if you favor cpu time or disk space, the squashfs could be swapped out for something else
<clever>
simpson: the kernel attribute may need to be updated, and u-boot added if you need it
2017-05-01
<clever>
bbl
<clever>
hodapp: you may also want to see what happens if you set dontPatchELF=true; in the derivation
<clever>
sziszi: maxing out the DSL modem brought the cpu usage up to about 60%
<clever>
sziszi: and it wasnt a normal router, it was a pentium1 with 128mb of ram and 2 ethernet cards
<clever>
i used to run LFS on my router
<clever>
MichaelRaskin: and PR is open
<clever>
yeah
<clever>
i didnt notice it had left echo off until i tried to get the exit status
<clever>
just stating how badly nix-repl crashed, it failed to restore terminal settings on exit
<clever>
i do, but that shows how badly it crashed
<clever>
so i'm now typing blind in that shell
<clever>
nix-repl returned status 1, and didnt enable local-echo
<clever>
MichaelRaskin: this command causes the LED display on my motherboard to display 01
<clever>
$ sudo ./ioport/bin/outb 0x80 0x01
<clever>
nix assertion throw during tab completion
<clever>
seems i can still crash nix-repl, heh
<clever>
nix-repl> ioport.meta.deserror: getting status of ‘/home/clever/apps/nixpkgs/pkgs/pkgs/os-specific/linux/ioport’: No such file or directory
<clever>
description = "direct access to I/O ports from the command line"; look good for ioport?
<clever>
dont know, only joined the channel recently and it sounds like a long-term trend
<clever>
somebody in #ghc recently said "after seeing a bunch of questions asked here by Nix users, I've sworn off the idea of using Nix for anything ever"
<clever>
ah
<clever>
stdenv.lib.licenses.gpl2 looks like a good match for "This software is distibuted under the terms of the GNU GPL version 2 or above."
<clever>
so that would be under pkgs/os-specific/linux
<clever>
i believe its using a linux syscall to allow userland direct ioport access
<clever>
iopl() is Linux-specific and should not be used in programs that are intended to be portable.
<clever>
iopl - change I/O privilege level
<clever>
You must compile with -O or -O2 or similar. The functions are defined as inline macros, and will not be substituted in without optimization enabled, causing unresolved references at link time.
<clever>
MichaelRaskin: probably, checking the source to confirm
<clever>
taktoa has been saying that i need to just get commit access
<clever>
Jookia: that example should have worked with older nixpkgs i belive
<clever>
Jookia: bug
<clever>
2017-03-12 15:43:07< clever> viric: i think the cause was somebody changing how nixpkgs works, and they didnt test pkgs = import <nixpkgs> { platform = pkgs.platforms.foo; }