olejorgenb[m] has quit [Ping timeout: 256 seconds]
grahamc has quit [Ping timeout: 246 seconds]
codyopel has quit [Ping timeout: 246 seconds]
adisbladis[m] has quit [Ping timeout: 240 seconds]
regnat[m] has quit [Ping timeout: 240 seconds]
thefloweringash[ has quit [Ping timeout: 240 seconds]
rycee has quit [Ping timeout: 240 seconds]
hedning[m] has quit [Ping timeout: 240 seconds]
mbrgm has quit [Ping timeout: 264 seconds]
florianjacob has quit [Ping timeout: 246 seconds]
copumpkin has quit [Ping timeout: 256 seconds]
FRidh[m] has quit [Ping timeout: 256 seconds]
sphalerit has quit [Ping timeout: 256 seconds]
pstn has quit [Ping timeout: 276 seconds]
dtz has quit [Ping timeout: 255 seconds]
mbrgm has joined #nixos-dev
<gchristensen>
Dezgeg: any chance you're around?
alp has quit [Ping timeout: 240 seconds]
alp has joined #nixos-dev
<Dezgeg>
for a bit probably
<gchristensen>
Dezgeg: may I PM? I have some "off topic for every channel" questions
<Dezgeg>
go ahead
kmicklas has quit [Ping timeout: 264 seconds]
orivej has quit [Ping timeout: 240 seconds]
<samueldr>
hope niksnut looks at the IRC backlog (I may ask tomorrow too) hi! you can ignore the [big!] PR if you don't have the time for it; but unless there's anything wrong with them, I have three simple fixes with big impact for nixos-homepage https://github.com/NixOS/nixos-homepage/pulls/samueldr thanks!
mbrgm has quit [Ping timeout: 256 seconds]
mbrgm has joined #nixos-dev
Mic92 has quit [Ping timeout: 260 seconds]
goibhniu has quit [Ping timeout: 265 seconds]
Mic92 has joined #nixos-dev
mbrgm has quit [Ping timeout: 246 seconds]
mbrgm has joined #nixos-dev
Lisanna has quit [Quit: Lisanna]
pie_ has joined #nixos-dev
Lisanna has joined #nixos-dev
mbrgm has quit [Ping timeout: 240 seconds]
mbrgm has joined #nixos-dev
<Lisanna>
samueldr that's an awesome improvement!
obadz- has joined #nixos-dev
sphalerite_ has joined #nixos-dev
obadz has quit [Ping timeout: 266 seconds]
sphalerite has quit [Ping timeout: 266 seconds]
obadz- is now known as obadz
Lisanna has quit [Quit: Lisanna]
grahamc has joined #nixos-dev
ma27 has joined #nixos-dev
pie_ has quit [Write error: Connection reset by peer]
<domenkozar>
clever: I'd want just single a single executable statically linked
<shlevy>
dtz: ^ :)
<domenkozar>
obviously a single single, not double single :-)
<clever>
domenkozar: i'm not sure why nix-bundle avoided musl for arx, its either broken, or he was just avoiding a ghc rebuild for a build-time only tool, where binary size didnt matter
<domenkozar>
I think musl wasn't near ready at least a month ago when I looked, but I know there was work done on this front
<gchristensen>
samueldr: did you see the ruby proposal to collapse `end end end` with `ennnd`?
<zybell>
There is something like that in pod (but more visible)
<samueldr>
I'm sorry, I know you're (probably) busy, niksnut, but for those other three PRs on nixos-homepage, if there's feedback and changes, I'd like to know, thanks! https://github.com/NixOS/nixos-homepage/pulls?utf8=✓&q=is%3Apr+is%3Aopen+LGTM
<samueldr>
(and thanks for merging the other one earlier)
<Profpatsch>
Isabelle uses the cartouche « » as a symbol that is outside of the alphabet used by the languages embedded in it.
<makefu>
ckauhaus: you think it is a good idea to remove the example setup with pvcreate,lvcreate etc? because i am very sure not all users are 100% fond with the exact usage
<ckauhaus>
yes, this is exactly the problem
<ckauhaus>
when you type it as is it won't work
<ckauhaus>
so in my opinion it is better to leave out detailed but misleading instructions
<ckauhaus>
or do it right
<makefu>
at least we could provide a minimal working example
<ckauhaus>
makefu: would be nice of course, but in this case the text should be restructured
<ckauhaus>
there is no point in creating an ext4 volume on the bare partition first and then slapping a PV on it
<ckauhaus>
this will result in exactly the error the OP puts out in the ticket as second point
<ckauhaus>
so I think it's better to go along the line with mdadm mentioned below in the same text and only point out that these tools might be of use
<ckauhaus>
there are really plenty of LVM intros out in the 'net
<makefu>
mh,mh i see what you mean
<makefu>
the best thing then would be to have a minimal working setup with for example the boot partition and ext4 as root
<gchristensen>
I'd rather not push people towards LVM anywho. it is complicated to get it right, and is complicated to recover from when there are prodbems
<ckauhaus>
yeah
<makefu>
i think so as well, especially on single-user setups such as a laptop lvm can be overkill
<zybell>
ckauhaus:You could *link* to a LVM example from the LVM commands.
<ckauhaus>
yes
<ckauhaus>
well
<ckauhaus>
perhaps
<ckauhaus>
what about mdadm?
<ckauhaus>
I think the scope of the installation manual is to provide steps to get NixOS running
<ckauhaus>
this is not a generic Linux admin primer
<gchristensen>
+1
<ckauhaus>
but feel free to submit a PR - I'm not the owner of that document ;-)
* gchristensen
looks at the last committer
<gchristensen>
you are now! ;)
<ckauhaus>
uhm well
<zybell>
The problem is to get it running in a way that leaves options for later.
<gchristensen>
someone who needs that information will find it
<zybell>
especially if some ....enable=true would initiate a complete reinstall I would be very surprised!
<ckauhaus>
please go ahead, improve the text and come up with a better solution :)
thefloweringash has joined #nixos-dev
phreedom has joined #nixos-dev
<zybell>
did you look in the wiki? They do it with linking. Did you follow the link to LVM? Complete Description incl go back to Install link at the right place!
* zybell
is impressed.
<xCuri0>
How do I port NixOS to a new architecture ?
phreedom has quit [Remote host closed the connection]
<gchristensen>
xCuri0: I can't help, but what architecture?
<xCuri0>
gchristensen, arm64ilp32
<xCuri0>
its already supported by linux and debian has a port of it
phreedom has joined #nixos-dev
<gchristensen>
what is ilp32?
kmicklas has joined #nixos-dev
<xCuri0>
gchristensen, 64-bit using 32-bit pointers which reduces memory usage
<xCuri0>
which increases performance too but limits memory to 4gb (which is ok on 4gb or less systems)
<LnL>
git show bbbbbbc
<LnL>
:o
<gchristensen>
:D
<Mic92>
32bit pointers in 64bit allows to create Spectre mitigation.
<Mic92>
by limiting user space to 32bit while kernel pages reside in the 64bit one.
<zybell>
Mic92:A javascript from darkweb in firefox reading the memory of password cache in firefox is boring? I tend to disagree!
<clever>
Dezgeg: the issue they are discussing there, is that the GPU blob uses 32bit opaque fields, to pass hold userland pointers in gpu memory, and pass them back to userland at a later point in time
<clever>
Dezgeg: but with a 64bit userland, the pointers dont fit!
gleber_ has quit [Ping timeout: 276 seconds]
<clever>
s/pass//
<xCuri0>
how do i (try) to compile NixOS for arm64ilp32 ?
<xCuri0>
whoever does the porting to arm should now
<Dezgeg>
look up the commit that introduced e.g. risc-v and imitate that
<xCuri0>
Dezgeg, in which repo ?
<xCuri0>
nix ?
<Dezgeg>
nixpkgs
<xCuri0>
i see 16 commits about adding risc-v support to different packages
<xCuri0>
ill try to replicate those for ilp32
<Dezgeg>
probably no package needs to be changed
<Dezgeg>
hm, I don't actually know how this risc-v port even works since it's missing some stuff I thought it'd have
<gchristensen>
it seems I can't use nix-build if I don't have internet ...
<Dezgeg>
I guess you can try to imitate aarch64 then which added things like else if targetPlatform.system == "aarch64-linux" then "${libc_lib}/lib/ld-linux-aarch64.so.1" to various places
<Dezgeg>
but the commit that added aarch64 is much older so some things have probably changed
<xCuri0>
once i edit it how do i build it ?
<xCuri0>
do i manually build each package ?
<clever>
xCuri0: nix will automatically build the entire closure, so you just need to ask for hello world, and watch it run
<clever>
xCuri0: but, you need to decide on native or cross-compiling first
<xCuri0>
clever, so i just tell it to use my nixpkgs repo instead of the default and configure it for my custom arch ?
<clever>
xCuri0: yeah
<xCuri0>
what about building ?
<xCuri0>
native build would take too long probably
<clever>
if you are doing native builds, you need an existing arm64ilp32 build slave with nix installed
<clever>
if you choose to cross-compile, you have to set the right flags to nixpkgs to tell it to cross-compile
<Dezgeg>
pkgs/stdenv/linux/make-bootstrap-tools-cross.nix is a good starting point which already has the flags set
<jtojnar>
gchristensen: yes, it is pretty annoying, I had to use --option substituters ''
<gchristensen>
cc shlevy
<clever>
Dezgeg: i believe that one is only needed for bootstrapping native builds
<Dezgeg>
well yes, but it's a starting point still
<xCuri0>
anyone know how big nixpkgs is before i clone it ?
<gchristensen>
~1.4g
<clever>
mine is 900mb due to zfs compression
<viric>
clever: how do you know the compressed size?
<clever>
viric: du defaults to the on-disk size, rather then the raw sum of how many bytes are in the files
<clever>
so for zfs, that will be less then the real size
<clever>
and for all other fs's (and zfs without compression), more, due to the overhead of cluster size
<viric>
btrfs intentionally did not do that
jtojnar has quit [Read error: Connection reset by peer]
<Sonarpulse>
and I pinged you in a few other PRs too
<Sonarpulse>
(also sorry I alt-tabbed, if you `sonarpulse: pong` I'll hop back instantly(
<Dezgeg>
I saw it, just been a bit busy
<Sonarpulse>
Dezgeg: sure
<Sonarpulse>
I guess that and the general system localSystem platform stuff
<Sonarpulse>
I'd like to move forward writing the docs or whatever the next step is
<Sonarpulse>
I'm happy to do the work just need some agreement on direction first
__Sander__ has quit [Quit: Konversation terminated!]
<Sonarpulse>
Dezgeg: like if you are too busy to look over, maybe comment like "I guess this fine for now as long as you don't add more enableIfSupported"
<Dezgeg>
generally I feel this lib.enableIfAvailable sacrifices readability
<Sonarpulse>
Dezgeg: well that's what I mean putting that on freeze
<Sonarpulse>
like I think the allowBroken change is perhaps a good idea regardless?
<Sonarpulse>
I guess I'm just trying not to be blocked
<Sonarpulse>
if there's some way I can keep working without you needing to decide everything now, that would be great
<Dezgeg>
the allowBroken change is fine but the fact that it causes really unpredictable changes when enableIfSupported seems totally confusing
<Dezgeg>
I mean separating allowBroken and allowUnsupportedSystem
<xCuri0>
what toolchain does nixos use for risc-v ?
<xCuri0>
can't find anything about the toolchain in the commits
<sorear>
what do you mean by the question
<sorear>
there's only one toolchain that works, gcc
<Profpatsch>
Do we have a solution to the “one fixpoint to bind them all”-problem?
<Sonarpulse>
Dezgeg: great! well if you can comment as much on that PR
<Sonarpulse>
I'll do the docs and merge it
<Profpatsch>
As in integrate haskellPackages, pythonPackages … into the main fixpoint?
<Sonarpulse>
and we'll have a "stay" on further usage of enableIfSupported until you way in
<Sonarpulse>
Dezgeg: to be clear, I don't want to prevent you from having a say because you are busy at this moment :)
<xCuri0>
sorear, normally for building for other archs you do something like aarch64-linux-gnu-gcc
orivej has quit [Ping timeout: 256 seconds]
<xCuri0>
is the risc-v port finished since looking at the code it seems half done ?