<mindB>
Alright. If anyone could point a newbie in the right direction:
<mindB>
I'm seeing that my autocompletion engine is pulling in clang as a dependency which is fine, but the clang package is over 500MB which I don't understand. On arch the clang package is ~200MB. Having trouble figuring out what the difference is.
takle has quit [(Read error: Connection reset by peer)]
takle has joined #nixos
markus1199 has joined #nixos
markus1189 has quit [(Ping timeout: 248 seconds)]
FRidh has quit [(Remote host closed the connection)]
<gchristensen>
I'm not sure it is good to include the sd-image-raspberrypi.nix, since that is for an installer image and not for regular use
<LnL>
heh
<gchristensen>
I'm off for a while.
<alphor>
huh. okay, I'll try dumping the line. it was in the iso image by default.
<gchristensen>
happy new year, good luck :)
mkoenig has quit [(Ping timeout: 258 seconds)]
<alphor>
thanks for the help, and you too.
<LnL>
alphor: root login with an ssh should also be enabled by default
<LnL>
ssh key
ambro718 has quit [(Ping timeout: 268 seconds)]
mkoenig has joined #nixos
acertain has quit [(Ping timeout: 244 seconds)]
aarvar has quit [(Read error: Connection reset by peer)]
<alphor>
LnL: that could be useful. how do you pipe your configuration.nix on a local machine to a target machine, through scp? if you do, do you chown /etc/nixos or just do it as root?
mudri has quit [(Quit: WeeChat 1.6)]
<LnL>
I mean that I'm pretty sure it's just password login that's disabled by default
mizu_no_oto has joined #nixos
<alphor>
ooh
<LnL>
copying the file over with scp is probably the easiest, and I don't think the permission of the files matter
takle has quit [(Read error: Connection reset by peer)]
Sonarpulse has quit [(Ping timeout: 240 seconds)]
takle has joined #nixos
copumpkin has quit [(Quit: My MacBook Pro has gone to sleep. ZZZzzz…)]
<alphor>
let's hope not lol. works so far.
brh has joined #nixos
aarvar has joined #nixos
civodul has quit [(Quit: ERC (IRC client for Emacs 25.1.1))]
digitalmentat has joined #nixos
stepcut_ has joined #nixos
stepcut has quit [(Ping timeout: 245 seconds)]
ryanartecona has joined #nixos
ryantrinkle has quit [(Ping timeout: 258 seconds)]
ryanartecona has quit [(Client Quit)]
systemfault has joined #nixos
ryantrinkle has joined #nixos
pdobrogost has quit [(Quit: Connection closed for inactivity)]
digitalmentat has quit [(Ping timeout: 258 seconds)]
mizu_no_oto has quit [(Quit: Computer has gone to sleep.)]
eacameron has joined #nixos
eacameron has quit [(Ping timeout: 256 seconds)]
eacamero_ has joined #nixos
Cutu_Chiqueno has quit [(Ping timeout: 268 seconds)]
eacamero_ has quit [(Ping timeout: 246 seconds)]
Wizek has joined #nixos
aarvar has quit [(Ping timeout: 265 seconds)]
Shou has quit [(Ping timeout: 258 seconds)]
ryantrinkle has quit [(Ping timeout: 258 seconds)]
aarvar has joined #nixos
Sonarpulse has joined #nixos
Wizek has quit [(Ping timeout: 252 seconds)]
Wizek_ has quit [(Ping timeout: 258 seconds)]
Sonarpulse has quit [(Remote host closed the connection)]
ryantrinkle has joined #nixos
eacameron has joined #nixos
eacameron has quit [(Ping timeout: 256 seconds)]
derjohn_mobi has joined #nixos
derjohn_mob has quit [(Ping timeout: 246 seconds)]
<NixOS_GitHub>
[nixpkgs] Mic92 closed pull request #21538: rename sound.enableMediaKeys to sound.mediaKeys.enable and add sound.mediaKeys.volumeStep (master...media-keys) https://git.io/vMLjw
kampfschlaefer has joined #nixos
jgertm_ has joined #nixos
<the-kenny>
Has anyone found a nice way to create a Cargo.lock file with dependencies available in a given rust-registry from nixpkgs? If our registry version lacks behind buildRustPackage won't work
<the-kenny>
best I can come up with is building the registry, then pull out the latest versions specified in the json files and specify the same versions in Cargo.toml
<LnL>
oh we don't have a rust section in the manual?
<the-kenny>
not yet. There's an open issue about it
<the-kenny>
I'll add a note to the issue that we should document my workaround :)
jgertm_ has quit [(Ping timeout: 252 seconds)]
<LnL>
can't you start shell with the cargo registry from nix somehow
ambro718 has joined #nixos
<the-kenny>
Not sure to be honest. I'm using the rust-packaged cargo but it uses the "upstream" registry. It's likely you can point some env var to nix' registry.
indi_ has quit [(Remote host closed the connection)]
indi_ has joined #nixos
ebzzry has quit [(Ping timeout: 245 seconds)]
ixxie has quit [(Remote host closed the connection)]
indi_ has quit [(Ping timeout: 260 seconds)]
cjhowe has quit [(Quit: My MacBook has gone to sleep. ZZZzzz…)]
yumbox has joined #nixos
<yumbox>
hello, is nixos practically useable yet?
<MichaelRaskin>
Define «practically useable»
<gchristensen>
I've deployed a few thousand production boxes with it, another co has deployed probably 50k boxes this last month withit, and many people use it on their laptops, including me
<yumbox>
with practically useable i mean as easy to use as other linux distros
<gchristensen>
that is for you to find out, I guess, I find the way nixos to be leaps and bounds easier to use
<MichaelRaskin>
I have used it on my notebook for a few years, since 2008, I guess… Only stopped because right now _my_ «practically useable» includes a niche requirement which is very annoying with systemd (on-the-fly addition of X sessions)
ixxie has joined #nixos
<MichaelRaskin>
I would say that if you are good with shell scripting and know what are the low level settings you want to be set, NixOS is much more convenient and comfortable than most distributions
<NixOS_GitHub>
[nixpkgs] Mic92 pushed 2 new commits to master: https://git.io/vMtjD
<NixOS_GitHub>
nixpkgs/master 002f3c8 tg(x): mpd: listen on 127.0.0.1 by default
<MichaelRaskin>
The basic approach hasn't changed much
<NixOS_GitHub>
[nixpkgs] grahamc pushed 1 new commit to release-16.09: https://git.io/vMtj7
<NixOS_GitHub>
nixpkgs/release-16.09 64a1302 Peter Hoeg: dropbox: 16.4.29 -> 16.4.30...
<yumbox>
are there new, maybe GUI, tools that make it easier to use?
<MichaelRaskin>
But over time defaults get improved and more stuff get single-configuration-line level of support
<MichaelRaskin>
GUI or easier?
<ixxie>
Installation - for me and my brother - was difficult; getting used to the Nix expression language also has a learning curve; but overall, the declarative configuration - for me at least- is far easier to use than imperative installation of stuff
<MichaelRaskin>
there is nixos-option
<gchristensen>
kmicu: around? I think you're good at these questions
<MichaelRaskin>
For me installation was easier, because I always fight the partitioning tools and here I was fully expected to want to set up something unexpected by the system and just list it in the config afterwards
<yumbox>
I use the commandline for OS stuff on my current distro, but CLI programs can be really hard to use too :/
<MichaelRaskin>
I think nixos-option does make it simpler to look up how all the stuff is called
<gchristensen>
yumbox: what is your currest distro?
<yumbox>
arch
<gchristensen>
we get _lots_ of people coming from arch
<ixxie>
yumbok: mostly commandline is used to rebuild the system; you can edit the configuration file in a normal editor.
<MichaelRaskin>
I would say that reading the manual is still a good idea with NixOS, but nix-repl and nixos-option make finding how-stuff-is-called and checking if you understand things correctly much better than a few years ago
<ixxie>
so for the most part, you do *less* in command line in NixOS, as far as I can tell
<MichaelRaskin>
I would say that reading the Nix manual is still a good idea for comfortable NixOS use
<gchristensen>
yes
<gchristensen>
but you can find enough examples for many computers to get by without doing that at first
<MichaelRaskin>
I have read it before my first installation of NixOS to find out if Nix is consistent enough to be worth trying to use it…
<jluttine>
my webcam works on chromium but not on firefox. anyone else having similar issue? do i need to do something specific for firefox?
<MichaelRaskin>
Webcam? usually it is about the audio…
<yumbox>
the less i have to read before using something, the better it is ofcourse.
<gchristensen>
yumbox: I'd say try it
<gchristensen>
see what you find
<yumbox>
how much free space do i need?
<ixxie>
honestly I cannot wait for clever to finish his installer; I think it will make life so much easier for new users.
<yumbox>
and, how much compiling do i need to do?
<MichaelRaskin>
I would say three times the graphical installer ISO size
<gchristensen>
not a lot of compiling, most of the stuff is available pre-compiled
<yumbox>
modern webbrowsers are pretty much an OS, so do i have to compile firefox?
<MichaelRaskin>
«the less i have to read before using something, the better it is ofcourse.» — well, I would say NixOS is still not focusing on this definition of ease of use
<kmicu>
Hi yumbox: there is no GUI tools for Nix ecosystem, but if something is difficult or manual is unclear then we are happy to help. After learning couple of idiosyncratic commands you should be proficient with managing Nix systems.
<gchristensen>
yay, kmicu!
<kmicu>
Usually, you do not need to compile anything at all.
<yumbox>
MichaelRaskin: okay, good to know, thanks.
<MichaelRaskin>
My personal definition of ease of use requires «if you try to learn what goes on, you actually have a chance to succeed» — and NixOS is much easier to use from that angle
<kmicu>
Try NixOS and we will guide you step by step. As a former Arch users I think that Arch requires more learning than Nix(OS) *if* you are not familiar with both systems.
<yumbox>
MichaelRaskin: by that definition, one can learn how to program anything :P
<ixxie>
MichaelRaskin: yes! that! half a year into NixOS and I can gladly say its much easier to manage than ubuntu xD
<hodapp>
yumbox: not exactly; it's still making a statement about whether or not effort pays off
<hodapp>
yumbox: and on some systems, it really doesn't
<MichaelRaskin>
Sorry no, however much time you spend trying to understand what macOS does, in many cases you have no chance
<hodapp>
kmicu: yeah, former Arch user too. Grew tired of the once-every-few-months breakage that required me to manually hack out something
<ben>
NixOS never has breakage for you?
<yumbox>
MichaelRaskin: good one. i meant that if you learn about a libre OS, you can do anything :P
<hodapp>
not yet, but I've not been using it long
<gchristensen>
and if it does you can go back
<gchristensen>
that is a huge feature
<ben>
but then you sit in the past for an indefinite amount of time!
<MichaelRaskin>
yumbox: Ubuntu has grown large enough that having the source doesn't make tracing the complex configuration machinery _easy_
<yumbox>
hodapp: ah, yeah, you're right.
<ben>
nixpkgs is pretty large too
<simpson>
But the configuration system is much simpler than dpkg/apt.
<MichaelRaskin>
The main feature for me is that _the only_ way for two CLI programs in my profile to conflict is to have the same name
<MichaelRaskin>
In all the other systems there are many interesting ways for things to conflict on library versions
<yumbox>
MichaelRaskin: yeah, sure, but "succeed" means for the average person to run the programs they want to. that just requires apt install whatever on ubuntu.
<gchristensen>
"just"
<hodapp>
"average"
<gchristensen>
yumbox: they have to install it to their whole system and deal with the complexity / fall-out from that
<gchristensen>
like if you intsall a package that behaves differently depending on what else you have
<ben>
but otoh theres probably enough other people on ubuntu that the package works
<gchristensen>
here, I can fearlessly run `nix-shell -p <any-arbitrary-package-it-doesn't-matter>` and have it available to me, without having installed it globally
<kmicu>
You could also start gradually from Arch+Nix (the package manager) and move into NixOS which brings more benefits.
<hodapp>
Nix never worked right for me on Arch :-/
<yumbox>
i dont want to screw up my arch install
<kmicu>
I don’t think that lack of GUI tools is a big problem if you have a responsive help from the community.
<MichaelRaskin>
jluttine: for me the real problem is usually sound, and setting media.navigator.audio.full_duplex to false usually helps
<gchristensen>
"i dont want to screw up my nixos install" isn't something I've ever heard someone say
<hodapp>
I don't want to screw up my NixOS install.
* hodapp
runs off
<ben>
when i went to try out nixos i just moved /* into /blah
<ben>
figuring i can wipe nixos and move it back nbd
<yumbox>
gchristensen: maybe because not many people use nixos?
<kmicu>
Even when Nix does not work right on Arch it will break nothing, b/c it’s under /nix/store. You can safely remove it. Arch/Pacman is unaffected.
<MichaelRaskin>
gchristensen: I think I have. It involved moving to full-disk encryption
<yumbox>
kmicu: but then how can I "use" it?
<gchristensen>
MichaelRaskin: lol fair enough
<MichaelRaskin>
Also, bootloader configuration can be tricky or risky
<kmicu>
After installation, you can ‘nix-env -iA firefox’ and firefox will be available in your PATH.
<MichaelRaskin>
yumbox: if your change cannot be rolled back, it has to involve the bootloader or partitioning
<MichaelRaskin>
That reduces the mess-up surface area _a lot_
cjhowe has joined #nixos
<gchristensen>
anyway
<ixxie>
yumbox: once the some stuff (like the installer and package managemnt) get a GUI, I am sure that NixOS could become a very popular distro because it will become very easy to proliferate all sorts of custom flavors of it
<gchristensen>
yumbox: you could put it in a VM and try it out, no risk
<yumbox>
ixxie: any idea when that may be?
<ixxie>
clever is working on a beautiful gui installer
<gchristensen>
no real timeline on that
<kmicu>
Hah, like ‘once the some stuff (like the installer and version control managemnt) get a GUI, I am sure that git could become a very popular…’ ( ͡~ ͜ʖ ͡°)
<ixxie>
as for package management, its already just about as easy as ubuntu imo
<ixxie>
although I prefer the declarative approach
slack1256 has quit [(Ping timeout: 268 seconds)]
<ixxie>
kmicu: this is different because it wouldn't require technical knowledge
<kmicu>
yumbox: usability is not the highest priority for Nix project, that will not change in the near future.
<MichaelRaskin>
kmicu: unlike Git, Nix has a design whitepaper
<ixxie>
people familiar will nixos who wish to make a custom distribution can maintain it with far greater ease than in other distros
<yumbox>
kmicu: how can usability not be a high priority?
<ixxie>
so my bet is in a few years many people interested in developing distros for particular use cases will use NixOS as a backend
<ixxie>
I know I will ^^
<gchristensen>
yumbox: NixOS needs people who care about particular facets to drive them forward.
alx741 has joined #nixos
<ixxie>
I hope to eventually contribute towards usability myself, but at the moment I am still learning the ropes :P
<MichaelRaskin>
yumbox: usability means very different things to different people
<gchristensen>
yumbox: there are a lot of attributes around "usability" which we do have good usability in some areas, and not as good in others. I care a lot about security and keeping things up to date, so that is my main focus, for example.
<ben>
Yeah I'm thinking I might want to not use NixOS because I don't have the energy to like fix my email client package :(
<kmicu>
yumbox: the same way as in Arch usability is not something to brag about it.
<gchristensen>
ben: which one?
<ben>
evolution
<gchristensen>
what is broken about it?
<ben>
hasnt actually displayed emails for a while
<gchristensen>
shesh
<ben>
like the content area doesn't render
<ben>
lists emails just fine tho
<MichaelRaskin>
The optimal amount of stuff to read before installation for you (as you say) is zero, for me it is non-zero because I want people to commit that some basic design description is something for all power users to read.
<ben>
its a bit beyond "yeah someone forgot to tell evolution about this random-ass gnome library that's implicitly in scope under gnome, so"
<kmicu>
ben: I’m pretty sure that if you report the problem it will be fixed. You could also get a feedback from other Evolution users.
<yumbox>
gchristensen: can't you just have it all? security and an up-to-date system and easy to use?
<kmicu>
Oh, Nirvana fallacy is strong here :)
<MichaelRaskin>
yumbox: you can't have «easy to use»
<ben>
not a lot of confidence
<MichaelRaskin>
It misses the critical part «easy for whom»
<gchristensen>
yumbox: sure, it could be done, if enough people are working towards it.
<yumbox>
MichaelRaskin: for people
<kmicu>
Arch also has a plenty of broken packages, like any other distro. There is always something broken.
<MichaelRaskin>
OK, I'll bite.
<gchristensen>
yumbox: NixOS is small, no hiding it. we need more people interested in these attributes.
pdobrogost has joined #nixos
<ixxie>
I like the principle of designing a system which your grandma could use and yet still has transparency and accesibility for power users; not sure how possible it is xD
<MichaelRaskin>
«For people», statistically, default language being Chinese should improve ease of use
<ben>
also it's a bit of a drag not being able to clone random shit on github and doing the configure, make, install thing
<yumbox>
gchristensen: oh, okay.
<kmicu>
So you don’t want Nix! Problem solved.
<MichaelRaskin>
ben: that last part is simpler inside a FHS chroot
<ben>
some things on github just fight you to the death if they arent on a "normal" fhs kinda place
<ben>
yah i guess
<kmicu>
Nix by design makes global mutable ‘configure, make, install’ hard.
<MichaelRaskin>
Which is actually in a good shape by now
rmrfroot has joined #nixos
<ben>
in retrospect i didnt actually mean install
<yumbox>
fhs?
<MichaelRaskin>
That's what I assumed
<MichaelRaskin>
Filesystem Hierarchy Standard
<yumbox>
ah, okay.
<ben>
every couple of months i look at servo and its bespoke build tooling and just give up
<ben>
but i should probably learn to use fhs chroots :3
<ben>
(which also feels like giving up! a little!)
<MichaelRaskin>
Servo provides nightlies that are easy to patchelf into running
<MichaelRaskin>
(I have done that with a few of them)
mkoenig has joined #nixos
kynan_ has joined #nixos
<MichaelRaskin>
Honest installation requires being able to make the package build system work, and Servo is large and complicated (who would expect a web browser to be…)
<MichaelRaskin>
As for Evolution: I have to admit that some time ago I tried to package Empathy, and I have given up.
<gchristensen>
one little interesting thing is NixOS is in the top 10 most active projects based on reviewers: https://octoverse.github.com/
<MichaelRaskin>
Some Gnome stuff is Sage-level complicated to package
sigmundv has joined #nixos
<hodapp>
blugh, Sage
<kmicu>
yumbox: in summary, we are happy to help with any problems during NixOS installation/operation. Try it, check if you like it. Don’t expect any GUIs in the near future.
<ben>
It's a bit discouraging that gnome stuff as packaged doesn't work, tho
<hodapp>
is Sage the build where it builds it own version of GCC in order to build its dependencies?
<ben>
I don't wanna be the only guy off the beaten path, so if it doesn't work for me I just assume I'm not the target audience :/
<gchristensen>
ben: can you tolerate thunderbird? many people use thunderbird
<ben>
I'm using it right now but it seems buggy
<ben>
displays a bunch of emails that have only a time and no date in the timestamps as most recent, always
<ben>
I guess I have buggy emails...
<MichaelRaskin>
hodapp: I think that is the default, yes
<kmicu>
ben: GNOME is used by many NixOS users. It’s actively updated and maintained. It’s a big monolithic project though so for sure it is not perfectly packaged. If you participate in reporting problems I’m sure they will fix all of them.
<MichaelRaskin>
I wanted to be able to build it before the heat death of the universe, so I tried to use some system packages. At some point I failed to understand what was going on
<yumbox>
kmicu: okay, thanks.
<ben>
yeah thatd be nice.
<hodapp>
MichaelRaskin: I once tried to build it on an MK802, and it destroyed the SD card after a few days of building
<hodapp>
"The language is whatever the tools parse, duh."
<MichaelRaskin>
Hm, looks like no
<sphalerite>
lol
uu has left #nixos ["WeeChat 1.6"]
<MichaelRaskin>
hodapp: the true sad story is that Nix started out having a specification that was automatically converted to a parser. This ended up becoming too slow and being abandoned
<MichaelRaskin>
Vim also has a /* problem
cjhowe has joined #nixos
<sphalerite>
aww
jgertm_ has quit [(Ping timeout: 258 seconds)]
Guest21099 has joined #nixos
<sphalerite>
Well I might as well take a shot at writing a BNF, right?
* sphalerite
is armed with "CS311: Programming Language Definition and Implementation" and overly confident
<rmrfroot>
quote from the linked thread: "BNFC's LBNF grammar targets LALR(1) parsers generators which are not powerful enough to parse Nix."
<kmicu>
Yeah, the rest is an exception from the rule ( ͡~ ͜ʖ ͡°)
james is now known as james_rth
<rmrfroot>
gchristensen: haha
<kmicu>
Ah, and the trivial ones like reformatting README are also merged promptly.
kynan_ has joined #nixos
<rmrfroot>
i was thinking, is there a clear hierarchy in NixOS (as in who makes the decisions)?
* kmicu
looks at “Ok, so I can drop ac2c9a3 and then this one can be merged cleanly with ttuegel's PR, I think.” then looks at ‘Nov 17, 2016’ then predicts forks… 😺
<NixOS_GitHub>
nixpkgs/master d3f01c3 Joachim F: Merge pull request #21560 from Ekleog/kcov...
<gchristensen>
rob pretty well owns nixops, eelco pretty well owns nix, domen has broad authority on nixpkgs, but eelco is #1, but really my understanding is if you consistently do a type of thing, the community and them will look to you for leadership in that area
<rmrfroot>
gchristensen: ah ok, thanks for clarifying
<MichaelRaskin>
NixPkgs have this benefit of a lot of people having commit acces in various areas
<kmicu>
rmrfroot: they are different repos. Changes in Nix repo are important and can have a big impact therefore they require niksnut’s approval.
<gchristensen>
right
<MichaelRaskin>
Which sometimes doesn't help to prevent weird decisions, but at least helps about stalling
<MichaelRaskin>
And in Nix the current normal is neither rejected nor merged
<kmicu>
There is no chaos, but a lot of tribal knowledge. The structure of ‘power’ is not documented.
<MichaelRaskin>
Nix is the opposite of chaos — it is quite close to frozen
<gchristensen>
the ~400 PRs we've merged in the last 30 days isn't really frozen ...
<MichaelRaskin>
It is NixPkgs
<kmicu>
Yeah, those open PRs are in majority — new PRs.
<gchristensen>
" Excluding merges, 209 authors have pushed 1,087 commits to master and 1,379 commits to all branches. On master, 962 files have changed and there have been 31,557 additions and 13,991 deletions. "
<sphalerite>
I'm just going to look at all the oldest PRs and comment on those obsoleted by the flow of time :p
pstn has joined #nixos
<rmrfroot>
why it looks like chaos to me is because there are some changes that are commited directly and some are PRs. there doesn't seem to be a clear process on how changes are allowed into the project.
<MichaelRaskin>
Back when Nix was on SVN and commit rights were for all repos at once, I have implemented tryEval… which niksnut doesn't like much (for good reasons), but still there is no better idea for implementing Hydra's NixPkgs builds
<kmicu>
New year, new challenges. I’m still happy, b/c even with Nix repo frozen other things move ahead. Constant improvement.
<MichaelRaskin>
rmrfroot: most of the PRs would be OK to commit to master
kynan_ has quit [(Remote host closed the connection)]
<rmrfroot>
MichaelRaskin: sure, but what about the commits that aren't even reviewed by another person?
<MichaelRaskin>
PRs are needed to prove effort commitment/experience with Nix-based packaging
<kmicu>
One could even argue (not me) that the stable Nix repo gives a room for Nix{pkgs,OS,Ops} improvements.
<gchristensen>
kmicu: how do you mean?
<kmicu>
Recently, some changes in Nix (namespaces) resulted in a slowdown in Nixpkgs.
<gchristensen>
rmrfroot: once you're clearly doing consistently good work, you get commit access. there are many PRs and only so many reviewers, so being careful and committing to master reduces the overhead by reducing "almost-certainly-to-be-good" PRs
indi_ has joined #nixos
<kmicu>
(That could be avoided though by not using the latest Nix on Hydra… or something?)
<srhb>
Is the nix tool slated for a 17.03 release?
<gchristensen>
rmrfroot: yeah, that happens sometimes. the-kenny and peti are both respected members of the community. note, though, that this is on master which in `nixos-unstable` which isn't for every day users.
<kmicu>
rmrfroot: peti is a user of master. There is many breaking changes on master and we solve them before they hit channels releases.
<gchristensen>
did we wake the beast of nix-mergers? ;)
<kmicu>
rmrfroot: also it’s a little bit ‘funny’, b/c when peti switched from stable gnupg20 to gnupg21 that was ok :P
<rmrfroot>
gchristensen: yeah, no doubt about that, nothing against any of them. it just got me thinking, what if stuff like that happens with critical stuff? or that malicious code gets in to the tree.
tokyo_jesus has quit [(Ping timeout: 248 seconds)]
<rmrfroot>
maybe it won't be a problem if you don't use unstable
<gchristensen>
rmrfroot: it doesn't get released if it breaks things
<kmicu>
You can always use an older release of Nixpkgs. nix-shell -p emacs24 -I nixpkgs=nixpkgsWithEmacs24.
<kmicu>
It’s really difficult to break official releases. They can be delayed, but not broken.
<the-kenny>
rmrfroot: I'm sorry if this commit caused you any trouble. As you can see from the commits it was quite controversial even when I pushed it. I have since then adopted a slightly more laid-back strategy for updating stuff. However, I still think that we needed to update to emacs25 at some point, even with the risk of breaking stuff. Keep in mind that this was (and still is) only in the unstable channel and not
<the-kenny>
in any stable release yet.
<rmrfroot>
gchristensen: maybe it's really hard for malicious stuff to end up in a release, since it's so well tested/evaluated.
<gchristensen>
the-kenny: I didn't mean to ping you, I think this is just a discussion of "how does nixpkgs work"
roconnor has joined #nixos
<the-kenny>
gchristensen: no it's fine :) This commit still haunts me after months ;)
<gchristensen>
sorry (but you'rewelcome to participate)
<kmicu>
the-kenny: imo you did a good thing. Especially, that Nix(pkgs) has so many escape hatches to install an older stuff.
<rmrfroot>
the-kenny: hey, no worries! not trying to point any fingers here, it's just an example i came to think about.
<the-kenny>
I think that rmrfroot has some valid points - a better pr/review/merge plan might benefit nixpkgs quite a bit. I enjoy the process rust uses (nothing goes into master, everything is merged via an automated bot)
<the-kenny>
However, that needs a quite sophisticated infrastructure which we don't have yet
<the-kenny>
rmrfroot: it's fine :) Don't worry.
<rmrfroot>
i'm just using emacs24 as a private package, right now. that's the nice thing about NixOS, i could just copy the definition from your diff and use it within like 5 minutes
<the-kenny>
Your point is totally valid
<gchristensen>
rmrfroot: you migth be surprised to find how debian does it :)
<rmrfroot>
gchristensen: i don't want to know, to be honest :D
<gchristensen>
I didn't either.
<rmrfroot>
i mean, imagine not having nix and a central repo to manage everything.
james_rth has quit [(Remote host closed the connection)]
<gchristensen>
trusted maintainers build locally and push the compiled .deb's up to their server
<gchristensen>
oops I didn't mean to say that
<rmrfroot>
-triggered-
ck3d has joined #nixos
Shou has quit [(Ping timeout: 245 seconds)]
pstn has quit [(Remote host closed the connection)]
alx741_ has joined #nixos
alx741_ has quit [(Client Quit)]
alx741_ has joined #nixos
<gchristensen>
in comparison, nixpkgs is amazingly auditable
alx741 has quit [(Ping timeout: 265 seconds)]
<rmrfroot>
gchristensen: yeah, that's true
alx741_ has quit [(Client Quit)]
alx741 has joined #nixos
<rmrfroot>
maybe i should just run a release instead of unstable and take a chill pill ^^
<gchristensen>
I do recommend it
<rmrfroot>
i'm like the guy who wants to eat the cake, but still keep it :P
yumbox has quit [(Quit: leaving)]
ck3d has quit [(Ping timeout: 260 seconds)]
<ixxie>
NEL doesn't support any kind of regex substitutions right? I wanted to do something like imports = [ ./folder/*.nix ]
<rmrfroot>
anyway, thanks (kmicu, gchristensen and the-kenny) for sharing some insights in how the human machinery works. i have also been looking at some GitHub issues related to this topic and it seems like a lot of things *are* going to happen this year to improve the whole process.
pstn has joined #nixos
<gchristensen>
rmrfroot: the process develops slowly over time as people push it forward, we're all trying to make nixos the best it can be
<gchristensen>
:)
<kmicu>
Yuge improvement. Believe me. We have the best people.
<ixxie>
and you guys are doing an excellent job at it, I might add!
<gchristensen>
kmicu: you are so smart.
bennofs has joined #nixos
* kmicu
is tempted to use this awful ‘Sorry losers and haters, but my I.Q. is one of the highest -and you all know it!’ as a response. Too much.
<gchristensen>
way too much
cjhowe has joined #nixos
<kmicu>
[Dark joke] It wasn’t too much for ’Murica.
<yumbox>
"The CD contains a basic NixOS installation. (It also contains Memtest86+, useful if you want to test new hardware). When it’s finished booting, it should have detected most of your hardware."
<yumbox>
couldn't finish booting
<kmicu>
Ah, it’s a LiveCD problem?
<yumbox>
yeah
<NixOS_GitHub>
[nixpkgs] volth opened pull request #21569: garbage lines in mercurial.nix (master...mercurial-3.9.2) https://git.io/vMqUk
<martijn923>
What is NixOS general policy on /etc? To not have it at all (or as little in there as possible), or to have whatever we want/need in there as long as it is generated and read-only?
indi_ has quit [(Remote host closed the connection)]
<yumbox>
now im copying it again. maybe it'll work now.
indi_ has joined #nixos
yumbox has quit [(Quit: leaving)]
james_rth has joined #nixos
* kmicu
considers global /etc/ (or anything not under /nix/store) as a necessary evil.
<rmrfroot>
kmicu: then you must really love /var
<gchristensen>
martijn923: as little as possible, ready-only if we have to have it there, if possible
indi_ has quit [(Remote host closed the connection)]
james_rth has quit [(Ping timeout: 264 seconds)]
<martijn923>
i by no means want to poo on this particular pr, just wondering what is the most nixos way to solve it
<LnL>
it depends the service imho
indi_ has joined #nixos
<LnL>
for things that can reload their configuration it's useful
<Dezgeg>
e.g. my thinkpad needs rtsx_pci and others
indi_ has quit [(Remote host closed the connection)]
takle has joined #nixos
<martijn923>
in this case my first reaction was why don't these services just call gethostname(2) ?
<martijn923>
or instead of providing /etc/hostname (which doesn't really seem to be a standard) we could patch them to read /proc/sys/kernel/hostname or whatever
<kmicu>
rmrfroot: I love that NixOS at least try to minimize mutable parts. There is not enough time to patch everything and maintain it. Things like /run/opengl-* or /etc, /var are a reasonable trade off.
<gchristensen>
"minimize mutable parts"++
<LnL>
indeed, or use the hostname hostname command
<gchristensen>
!m minimizing mutable parts
<[0__0]>
You're doing good work, minimizing mutable parts!
bennofs has quit [(Quit: WeeChat 1.6)]
bennofs has joined #nixos
<kmicu>
*Realistic* alternatives have even more /* mutable surprises. I’m extremely happy with NixOS/GuixSD even though they are far from perfect.
cjhowe has quit [(Quit: My MacBook has gone to sleep. ZZZzzz…)]
bennofs has quit [(Client Quit)]
bennofs has joined #nixos
<kmicu>
perfection*
justanotheruser has quit [(Ping timeout: 245 seconds)]
bennofs has quit [(Client Quit)]
bennofs has joined #nixos
bennofs has quit [(Client Quit)]
bennofs has joined #nixos
<LnL>
we don't have /bin/bash either for example
justanotheruser has joined #nixos
cjhowe has joined #nixos
rmrfroot has quit [(Ping timeout: 245 seconds)]
Wizek_ has joined #nixos
Wizek has joined #nixos
pikajude has quit [(Quit: Quit)]
pikajude has joined #nixos
bennofs has quit [(Ping timeout: 258 seconds)]
<kmicu>
martijn923: systemd is already forked and patched https://github.com/NixOS/systemd so maybe patching/maintaining hostnamectl is not that big deal (and a better trade off than introducing yet another link outside of /nix/store).
<martijn923>
kmicu: yes that's a possibility, although i can see the trade offs
cjhowe has quit [(Quit: My MacBook has gone to sleep. ZZZzzz…)]
<MichaelRaskin>
I am not sure _only_ systemd wants /etc/hostname
danharaj has joined #nixos
Shou has quit [(Ping timeout: 240 seconds)]
FrozenCow has joined #nixos
<gchristensen>
I am sure systemd is _not_ the only one
<mpickering>
Where does the env-vars file live for my default environment?
uralbash has joined #nixos
<kmicu>
Are you asking about /nix/store/…-set-environment?
<kmicu>
(aka stuff set by environment.variables.* module)
zagy has joined #nixos
<ixxie>
how do you guys think GuixSD compares to NixOS?
<Acou_Bass>
ixxie: ive used both a fair bit - guix is far less polished and has far less features available
<kmicu>
It’s different, but have similar goals.
<mpickering>
I did "source env-vars" and wanted to know how to undo this
<mpickering>
in the end I just opened a new shell
<Acou_Bass>
BUT at the same time, having a fairly standard language (scheme) rather than whatever the nix expression language is supposed to be
<kmicu>
ixxie: if you are interested in Parabola/Trisquel then Guix(SD) is a Nix flavor for you.
<Acou_Bass>
not that nix is bad, but scheme is something some people will already know
<kmicu>
ixxie: Otherwise you can keep using Nix(OS).
<Acou_Bass>
that too ^ guix is free-only
<MichaelRaskin>
On the other hand, NixPkgs uses shell for buildscripts, and Guix uses Scheme, which makes familiarity arguments more complicated
<Acou_Bass>
i actually switched my laptop from guixsd back to nixos recently because guix is still missing features that i feel would be non-trivial to bring over (though not impossible i guess) :P
<kmicu>
It’s not only about Scheme — it’s only Scheme vs Nix… *+* Bash. But those are minor technical differences.
Shou has joined #nixos
yumbox has joined #nixos
<ixxie>
I was reading a while back about the pros and cons of scheme for packaging
<kmicu>
Acou_Bass: what features did you miss?
<ixxie>
where does bash come into it?
<yumbox>
trying to install nixos, but i get grub error
<kmicu>
ixxie: there is a ton of bash in Nixpkgs :)
<ixxie>
but not in scheme
<ixxie>
I mean Guix
<yumbox>
"must set option boot.loader.grub.devices"
<ixxie>
yumbox: edit /etc/nixos/configuration.nix
<yumbox>
but i already have grub installed, and i dont want to fuck it up
<Acou_Bass>
kmicu: just things like dnsmasq/crypt, syncthing, that sort of stuff
<Acou_Bass>
things i have come to expect from a desktop distro ;D
<yumbox>
ixxie ive edited grub out in there Lready
<yumbox>
already *
<Acou_Bass>
nixos also handles LUKS on root far better (guix 0.12.0 now supports it, but its still a bit hacky) XD
<kmicu>
Yeah, Guix(SD) is smaller/younger so it can have a missing features for some users.
<avn>
ixxie: licensing also matter, GuixSD is gpl3+, and all packaging boilerplate is gpl3, so releasing your own overlays under different license is doubtful
<Acou_Bass>
i do think eventually guixsd will be a really great distro though, i really like the scheme interface ;D
kynan_ has quit [(Ping timeout: 248 seconds)]
<Acou_Bass>
its just that *right now* nixos works and works awesome
<kmicu>
yumbox: NixOS needs to have control over boot process (GRUB) to create new entries for new versions of the system.
<yumbox>
well, thats a dealbreaker...
<kmicu>
Acou_Bass: NixOS is much better choice for users ok with binary blobs.
<Acou_Bass>
also because nixos is a lot less stringent on the 'purity' of its software, i could feasibly run it on my main desktop rig and my raspberry pi if i really wanted to
<Acou_Bass>
kmicu: yeah that too
<yumbox>
no other distro requires control over the bootloader
<kmicu>
You can use GuixSD on both, but you need to install binary blobs explicitly and the work is on you.
[0x4A6F] has joined #nixos
<Acou_Bass>
i ran nixos on my main desktop for a bit, it pretty much just works as good as any other distro, just a couple of pieces of software that i was too lazy to package myself (though i did make a few) XD
<kmicu>
yumbox: no other distro gives you rollbacks into older versions of the system.
<Acou_Bass>
opensuse does, though it does it via btrfs rather than nix rollback magic
<kmicu>
Trade offs everywhere :)
<yumbox>
isnt there a way i can install it without it fucking over my bootloader?
<kmicu>
Oh, btrfs snapshots are fileystem level. You can have that on NixOS too.
<hodapp>
yeah, some folks do it with filesystem snapshotting (e.g. ZFS) but I feel like that lacks a lot of the same benefits
<Acou_Bass>
i also have no idea how suse treats such rollbacks in a dual-boot scenario
<kmicu>
yumbox: you could try NixOS in a VM or we could ask clever if he has some ideas how to dual boot NixOS w/o control over GRUB.
<kmicu>
[Joking] Or you could try NixOS the next time Pacman bricks the system ( ͡~ ͜ʖ ͡°) That’s a common scenario.
danharaj has quit [(Ping timeout: 248 seconds)]
<hodapp>
:P
<srhb>
You could install it somewhere you don't actually care about and manually set up a NixOS booter in your primary bootloader. It would probably be messy. And if you don't chainload the NixOS bootloader (not sure if that's even possible) you'd be reverting to your first configuration always (if it still exists)
<yumbox>
well, that sucks
<srhb>
Why don't you want NixOS to take over your boot loader?
<srhb>
Out of curiosity, I've never felt that need myself. :)
<yumbox>
it should just work with osprober, like all other OSes
<Acou_Bass>
when nixos DOES control the bootloader, does it support dual boots? like, will it auto-setup the other distro in the bootloader?
<hodapp>
speaking of which I need to hack up NixOS on my laptop to be able to boot Windows too
<Acou_Bass>
cool
<yumbox>
kmicu can that be done automatically?
<srhb>
yumbox: I'm not sure I understand why that's important, but ok. :)
<yumbox>
like with osprober on arch
ixxie has quit [(Remote host closed the connection)]
<kmicu>
NixOS is different. Unfortunately (or not), that’s the whole point.
<yumbox>
srhb if you want to dualboot two distros that require control over the bootloader, it doesnt work
<srhb>
yumbox: Right, that makes sense. :)
<Acou_Bass>
as far as i know, arch doesnt require control over grub
<Acou_Bass>
(or whatever bootloader you choose)
<yumbox>
true
<kmicu>
I’m not sure if nixos-generate-config automatically generates a proper boot.loader.grub.extraEntries with existing distros already detected.
<hodapp>
on my laptop it didn't detect the bootable Windows partitions or anything
kynan_ has joined #nixos
<srhb>
It didn't detect my Arch installation way back either, I had to set it up manually.
<srhb>
(But that's been a while)
<kmicu>
Yeah, that’s why I think you need to manually set it up.
<yumbox>
ugh
<srhb>
If you have EFI it might be easier to just have separate bootloaders. That should be doable, since it's decoupled from disk.
<yumbox>
why cant nixos just use a "latest version" entry for gub?
<MichaelRaskin>
A rare case where proper UEFI does actually help: I have a separate EFI partition for my Nix-based system, and use the laptop firmware for switching
tokyo_jesus has quit [(Ping timeout: 264 seconds)]
<kmicu>
yumbox: if an update broke something you can immediately boot into previous *working* version of the system.
<yumbox>
latest + n older entries then
tokyo_jesus has joined #nixos
<Acou_Bass>
well, the nixos grub just lists the latest, and then the rest are under a submenu
<srhb>
yumbox: Those have to be updated whenever you update the system. The paths might change
<Acou_Bass>
so its not like it spams your screen unless you tell it to
<yumbox>
srhb symlinks
<srhb>
yumbox: That could be doable. Needs development though. :)
<srhb>
yumbox: It moves the mutation into the running system though, which is a bit ick.
<kmicu>
Symlinks in what sense, mutable one? nixos needs to generate boot entries or clean garbage collected entries. The control is still required.
<srhb>
Still, you could try writing a proposal
<srhb>
kmicu: You could defer that control to after the bootloader and just have the mutation be moving the symlinks instead of generating new boot entries.
<srhb>
kmicu: That should be doable, I'm just not sure it's something people want to do.
<kmicu>
If you want Arch like distro then do not use NixOS/GuixSD.
<srhb>
Yeah I'm not sure how this could actually be done without breaking a lot of assumptions. You'd have to set aside some space for these symlinks that is not in the store, but is still managed wrt. garbage collection etc.
<srhb>
It's messy.
oleks_ has quit [(Quit: leaving)]
<avn>
yumbox: latest + n entries done via rewriting grub.conf/menu.lst, but you can load grub.cfg from other grub, or just install grub to partition. Or use EFI to switch between distros, and nixos' grub for generations. So you have lot of options
oleks has joined #nixos
<srhb>
Option two sounds like the thing you probably want. Loading NixOS' grub from your primary grub. :)
<avn>
I use EFI and own grubs for debian and nixos (before I finally switch to nixos)
<avn>
s/use/used/
<ToxicFrog>
Is there a nix-shell equivalent that does for LD_LIBRARY_PATH what nix-shell does for PATH?
<ToxicFrog>
I have here a jar that has some JNI dependencies and I just want to run it, I don't want to write a complete package for it -- this is a one-off test of a friend's game
alx741_ has joined #nixos
alx741 has quit [(Ping timeout: 256 seconds)]
<avn>
ToxicFrog: for 1-2 times silly shell script with `export LD_LIBRARY_PATH=$(pwd)/lib:$LD_LIBRARY_PATH` should works ;)
<kmicu>
ToxicFrog: maybe ‘nix-build "<nixpkgs>" --no-out-link -A gcc’ could help.
<MichaelRaskin>
symm-: setfont iso01-12x22
<symm->
MichaelRaskin: thank you! :)
<MichaelRaskin>
Actually, you can install fbterm on the installation CD and then have full power of TTF in the framebuffer console
<MichaelRaskin>
But of course installing in the LiveCD environment consumes RAM
<symm->
not sure how to do that... but I think setfont works rn
<symm->
I see setfont only affects the current console
<MichaelRaskin>
That's true
<symm->
the NixOS Manual on console 8 is still tiny, can I change the font there too?
<symm->
I would exit the manual viewer, but don't know how to re-enter it
<kmicu>
man configuration.nix
<kmicu>
Zuruck. That’s only for options.
<MichaelRaskin>
Well, you can do "chvt 8; sleep 1; setfont iso01-12x22"
<symm->
didn't work... it changed the font in the current console, though:)
<MichaelRaskin>
It should change in the current console after switching so that the new current console is vt8
<MichaelRaskin>
You could put a sleep 2 and switch manually
<MichaelRaskin>
Or maybe these tricks only work in my hacked non-NixOS system that doesn't run systemd
yumbox has quit [(Ping timeout: 260 seconds)]
<symm->
it successfuly switches to 8, the problem is that 8 is running a document viewer of some kind
<kmicu>
‘BROWSER=w3m nixos-help’
<MichaelRaskin>
Right, it runs w3m
tokyo_jesus has quit [(Ping timeout: 260 seconds)]
<symm->
yes
<symm->
if I press q, it asks for confirmation to exit, then reenters w3m
<symm->
must be running it in a loop?
<srhb>
Can't you just background it with ctrl+z ?
<srhb>
Then change font size and fg it again
<srhb>
Oh
<MichaelRaskin>
you could run nix-build --no-out-link
<MichaelRaskin>
Ah no
<kmicu>
You could switch to another TTY, change font and execute ‘BROWSER=w3m nixos-help’ to open manual.
<symm->
hmm, ctrl-z doesn't do anything
<srhb>
:(
<MichaelRaskin>
the problem is that the browser is launched by a systemd unit
<symm->
yes that worked kmicu :) thanks a lot
<MichaelRaskin>
So there is no interactive console behind it
<srhb>
MichaelRaskin: That explains.
tokyo_jesus has joined #nixos
<andi->
I just installed ohmyzsh on my new nixos test box. I'd like to source it in my custom .zshrc but I can't figure out how I can get the path to the file. The example/documentation (in the .nix file) does seem to only cover cases where it is installed via nix-env and not using the nixos-rebuild stuff. Any pointers ? :-)
<kmicu>
hi andi- maybe you could use something like ‘programs.zsh.interactiveShellInit = ". ${pkgs.oh-my-zsh}/path/to/something";’ in your configuration.nix.
<andi->
I could.. but then again my dotfiles would not be portable anymore :/
<andi->
I also run a few ARch and Debian boxes and so far it just had to do some distro detection
mguentner2 is now known as mguennter
mguennter is now known as mguentner
<kmicu>
Do you want a global path like ‘/run/current-system/sw/share/oh-my-zsh/…?
<andi->
yeah
<andi->
I couldn't find it there tho :/
cjhowe has joined #nixos
<kmicu>
Did you install oh-my-zsh in systemPackages and nixos-rebuild switch?
<andi->
yes
<kmicu>
Hmm, then /run/current-system/sw/share/oh-my-zsh/ should exist.
<andi->
that is what I thought :-)
kynan_ has quit [(Ping timeout: 246 seconds)]
<kmicu>
Maybe we have here an oh-my-zsh user that could check that. (I want to avoid spawning a VM just to check :P)
<kmicu>
(There is ‘share’ in ‘ls $(nix-build --no-out-link "<nixpkgs>" -A oh-my-zsh)/share/oh-my/zsh/’ so it should be linked.)
<symm->
tty installer is over my head, not sure what to do with fdisk/gdisk; will try graphical installer
<symm->
is there a primer for complete newbs? every guide talks about fdisk, /dev/sda etc like it's common knowledge
<mpickering>
I have got about half of stackage to install with the GHC 8.0.2 release candidate, should I upstream the modifications I had to make or do you usually wait a bit for package maintainers to do new releases?
<kmicu>
(In graphical installer should be GParted so you could do the same by clicking.)
<symm->
thank you kmicu, reading now
<kmicu>
If you do not want to create multiple partitions then commands listed on ‘Example 2.1. Commands for Installing NixOS on /dev/sda’ should be enough.
<symm->
ok :)
<kmicu>
mpickering: usually, peti switches default GHC ~2 months after the release. Informal policy is to fix packages upstream and not in Nixpkgs.
kynan_ has joined #nixos
mizu_no_oto has joined #nixos
<mpickering>
and each user adds their own overrides if they want to use the new version of the compiler?
sitedyno has quit [(Ping timeout: 250 seconds)]
mizu_no_oto has quit [(Ping timeout: 264 seconds)]
joepie91_to_go has quit [(Ping timeout: 256 seconds)]
dgn has joined #nixos
<kmicu>
Yep, I guess there is not many users using unreleased GHC version which breaks half of Hackage.
tex has joined #nixos
<gchristensen>
hehe
<mpickering>
if packages are missing external deps then I should open an issue for peti? or make a pull request to where the derivations get generated from?
<tex>
Hello, I want to run Zathura (pdf viewer) with firejail so I need to modify .desktop item exec to "firejail zathura". I do the same for Firefox with overrideDerivation and makeDesktopItem. For Zathura it creates the .desktop item but it does not seem to be used. Any ideas?
<NixOS_GitHub>
[nixpkgs] joachifm pushed 6 new commits to release-16.09: https://git.io/vMqqB
<NixOS_GitHub>
nixpkgs/release-16.09 ba71746 Ruslan Babayev: dpdk: 16.07 -> 16.07.2...
<NixOS_GitHub>
nixpkgs/release-16.09 bff0046 Ruslan Babayev: odp-dpdk: 2016-08-16 -> 1.12.0.0...
<NixOS_GitHub>
nixpkgs/release-16.09 a10c24b Ruslan Babayev: pktgen: 3.0.13 -> 3.1.0...
<gchristensen>
symm-: from there you should be able to search the internet for how to use fdisk to make partitions
<kmicu>
symm-: that part is not covered by NixOS manual, b/c it’s common for all Linux distros (w/o graphical interface). After executing ‘fdisk /dev/sda’ (if you want to install on /dev/sda disk, ‘lsblk’ lists what’s available) there is a dialog box in which you set your desired file system layout. Using http://gparted.org/ in a graphical installer is probably easier method if you are not familiar with
<kmicu>
fdisk.
<symm->
>fdisk /dev/sda # Create a full partition, For quick setup use these commands in order: n, p, 1, <Enter>, <Enter>, w
<symm->
I managed to do this; but apparently I won't be having a swap partition?
<MichaelRaskin>
It is not in configuration, it is about BIOS options
<symm->
ah, bios is set to "legacy" (aka mbr I think)
<MichaelRaskin>
Then device setting is correct
<symm->
thank you
<symm->
nixos-install seems to be doing stuff
<MichaelRaskin>
And EFI boot partition is not needed. But BIOS boot partition is probably needed
<kmicu>
(The gist is about EFI and in that case only part/line about creating swap partition is helpful.)
<symm->
/nix/store/ seems to have some scary looking filenames
pstn has quit [(Remote host closed the connection)]
<symm->
I see kmicu
m3tti has quit [(Ping timeout: 258 seconds)]
<symm->
nixos-install seems to have failed at "Installing the GRUB 2 boot loader on /dev/sda..."
<symm->
should I somehow instruct it to use /dev/sda1?
bennofs has joined #nixos
<garbas>
gchristensen: pong
<NixOS_GitHub>
[nixpkgs] domenkozar pushed 1 new commit to master: https://git.io/vMqmF
<NixOS_GitHub>
nixpkgs/master 6da8b0d Domen Kožar: Time passing by
taktoa has quit [(Ping timeout: 246 seconds)]
<kmicu>
symm-: ‘mkfs.ext4 -L nixos /dev/sda1’ creates a filesystem on /dev/sda1 and create a label ‘nixos’ for it. Later by executing ‘mount /dev/disk/by-label/nixos /mnt’ you mount /dev/sda1 called ‘nixos’ on /mnt and nixos-install use it.
<symm->
just tried doing just that
<symm->
problem might be I previously (mistakenly?) did the same thing for /dev/sda3
<symm->
should I gdisk again?
<kmicu>
symm-: if you are on, so called, legacy BIOS, then maybe reformat you disk with ‘fdisk’ and create only /dev/sda1 for system and /dev/sda2 for swap.
kynan_ has joined #nixos
<symm->
ok
<kmicu>
Ideally, ‘Example 2.1. Commands for Installing NixOS on /dev/sda’ should show what created those /dev/sda1 and /dev/sda2.
cjhowe has quit [(Quit: My MacBook has gone to sleep. ZZZzzz…)]
<symm->
it doesn't ;(
mkoenig has quit [(Ping timeout: 258 seconds)]
taktoa has joined #nixos
<symm->
if I create 8G for swap and the "rest" for system, won't I end up with /dev/sda1 for swap and /dev/sda2 for system?
ryantrinkle has quit [(Ping timeout: 258 seconds)]
<kmicu>
Did you uncomment ‘networking.wireless.enable = true;’ in configuration.nix?
<symm->
I didn't x_x
<symm->
can I do that now?
<symm->
I'll just boot from usb again and reinstall, I think..
<kmicu>
Do you have an Ethernet connection (or smartphone tethering) to download something?
<symm->
unfortunately no
<kmicu>
Oh, now the good news: you can use nixos-install as many times you want. No need to partitioning again.
<symm->
heh that is good news
<symm->
but do I boot from the usb stick to do that?
<kmicu>
Also maybe there is a way to enable WiFi even if networking.wireless.enable = true; is not enabled. Let’s poll the #nixos community.
<MichaelRaskin>
I think the install lacks wpa_supplicant package right now
<LnL>
yeah most likely
<MichaelRaskin>
But! Reinstall can be done without re-partitioning or whatever, you just mount /dev/sda1, edit config and run nixos-install
<LnL>
you can create a closue and copy that over but that won't be easier :)
<MichaelRaskin>
And most of the stuff is already in the store, so installation will be even faster
<kmicu>
symm-: yeah, you need to boot LiveCD, ‘mount /dev/disk/by-label/nixos /mnt’, edit /mnt/etc/nixos/configuration.nix and ‘nixos-install’.
<MichaelRaskin>
except for reboots, it will take almost the same time as nixos-rebuild switch
<symm->
kmicu: nod, doing that now
<kmicu>
(That’s probably faster too ;)
<symm->
thank you
<MichaelRaskin>
Well, if I was trying to save reboots, I would mount the install media, chroot into it and export the closure of wpa_supplicant to import it on the installed system.
<kmicu>
symm-: I’m out for today and wish you luck. I’m sure Nix folks help you with everything. Go shopping on https://nixos.org/nixos/manual/options.html#opt-services.xserver.windowManager.awesome.enable and welcome in Nix community! ʕノ•ᴥ•ʔノ ︵ ♥❤❣💞
justanotheruser is now known as officialjustan
<symm->
really grateful for your help, kmicu! thanks and have fun
<symm->
nice link, thanks
<gchristensen>
!m kmicu for bringing in a new user
<[0__0]>
You're doing good work, kmicu for bringing in a new user!
<gchristensen>
!m symm- for getting things going
<[0__0]>
You're doing good work, symm- for getting things going!
<MichaelRaskin>
I think Nix uses a C++ buildenv, and the process doesn't look like it allows any hooks
<bennofs>
MichaelRaskin: aw :( it would be really nice if packages that are included in the buildEnv could specify hooks, similar to how setup hooks work
mizu_no_oto has quit [(Quit: Computer has gone to sleep.)]
<MichaelRaskin>
Well, that would allow nix-env -i to break in new and exciting ways
<bennofs>
hmm, but thinking about this a little longer I just realized that this wouldn't be right anyway
<bennofs>
I wanted it to use it to build mandb's cache, but that should really be a system option, because you also want man cache if the env doesn't contain 'man' itself but only manpages
<NixOS_GitHub>
nixpkgs/staging 5a67b13 Daiderd Jordan: Merge branch 'master' into staging
<bennofs>
MichaelRaskin: perhaps it would be possible to add a configuration option (not in nix.conf, some extra dir perhaps) that tells nix to do something else in addition to buildEnv to create an environment? It could be useful for all sorts of "merging"/"database/index update" that needs to be done, but only when certain features are enabled. For example, mandb generation, gtk pixbuf module cache, and so on
<bennofs>
nix would build this derivation in addition to the buildEnv it already does for each environment it creates
<bennofs>
or perhaps we should just stop supporting imperatively managed environments and introduce something like system.extraSystemBuilderCmds for user environments as well :)
edvorg has joined #nixos
james_rth has joined #nixos
<bennofs>
What's the current state of declarative managed user environments with nix? I've got quite a lot of stuff that would work a lot nicer if we had that
<MichaelRaskin>
You are already free to manage your user environment by nix-building an expression