<abathur>
I know, just noting that I'm still giving it to posterity :P
<abathur>
energizer: for now most-focused on the actual executable name, and the Nix package
<energizer>
i like the executable to have the same name as the project, and i prefer the name resholve over resholve(d|r)
<energizer>
i think nixpkgs should develop some naming conventions
<abathur>
can you reflect a little on why resholve over d/r?
<energizer>
what does the executable command do?
<abathur>
resolve relative commands in shell scripts to absolute paths (primarily, but not only, for Nix builds)
<abathur>
bare commands I guess I should say; things that would be resolved from PATH
<energizer>
it's a verb, it should use the english naming convention for verbs
<abathur>
I've been trending that direction in my preference over time, and I feel subjectively like commands named like this may be easier to remember
xd1le has joined #nixos-chat
<cole-h>
abathur: I agree with energizer -- resholved over others if the project name doesn't change, else change both to resholve.
<energizer>
*d is already a strong unix convention for names of daemons
<cole-h>
^
<samueldr>
time to make it a daemon
<cole-h>
lol
<abathur>
mkDaemonHandlerDaemon
<abathur>
<3 cole-h
<{^_^}>
cole-h's karma got increased to 87
<abathur>
assuming a resholved -> resholve change, thoughts on the Nix package layout and names, particularly the "builder", and maybe how a setup hook should fit in?
<NinjaTrappeur>
sphalerite: thanks, I'll have a look!
<sphalerite>
wow wtf
<Valodim>
I don't think the davx folks got a letter or anything, but they launched a small business venture and probably renamed it to be safe at that point
<aleph->
So does something seem off about my firewall extraCommands blocks? It seems to be generating my rules tripled up somehow... so instead of just `-A nixos-fw -i lan -p tcp -m tcp --dport 22 -j nixos-fw-accept && -A nixos-fw -i enp1s0 -p tcp -m tcp --dport 22 -j nixos-fw-log-refuse` for example, it also adds a `-A nixos-fw -p tcp -m tcp --dport 22 -j nixos-fw-accept` preceeding them, which ends up
<aleph->
just completely negating them and yet as far as I can tell my rule generating functions don't do generate anything like that third, far too open rule.... https://paste.rs/GmT
<joepie91>
Valodim: I already see two counts on which that article is wrong
<joepie91>
1) there is no such thing as a universal trademark on a term, whether it applies is highly contextual, and 2) "To keep a trademark active, one must vigorously defend it, sometimes excessively" is absolutely false
<joepie91>
(but a common claim)
<joepie91>
yes, you do need to prevent genericide, but that absolutely doesn't mean that you need to legally overreach or respond to every single case
<joepie91>
the more... realistic... explanation of the situation with Lucasfilm is that they just send scareletters to anyone using the term because people don't have the money to fight it anyway, and it doesn't matter whether they are in the right
<joepie91>
also, the comment on 'inactivity' in that article refers to the trademark actually not being used anymore, which is unrelated to whether someone sends legal scareletters or not :)
<joepie91>
TL;DR this is not how trademarks work, and really what is going on here is the usual legal bullying in capitalism
<Valodim>
joepie91: agreed. the fact remains: you have "droid" in a product name, you might need to change your name
<joepie91>
from a practical perspective, sure, that's probably the safer option. it's just the characterization of the reasons in that article that I take issue with :D
<Valodim>
plenty to take issue with on those matters all around, indeed
parsley936 has joined #nixos-chat
<sphalerite>
aleph-: → #nixos; but the reason for that is probably that the SSH module (pretty much the only one to do this) opens the port in the firewall by default.
<ar>
so, what is the oldest kernel nix still runs on? ;)
<ar>
(nix, not full nixos)
<ar>
because i have a funny little old device here, with this: Linux Sailfish 3.10.20+0.0.47 #1 SMP PREEMPT Sun Feb 16 14:29:29 UTC 2020 x86_64 GNU/Linux
<ar>
this is going to be fun
<ar>
tar: invalid option -- J
<sphalerite>
ar: pff who needs syntactic sugar for piping
<sphalerite>
ar: my guess is nix should work, maybe sandboxing won't
<ar>
well, after replacing that "tar -xJf" line with "unxz -c | tar", it worked, and i do seem to have nix running there
<samueldr>
so the main thing to understand here is that they're transparent enough, luckily
<samueldr>
not as transparent as a nix build though ;)
<samueldr>
might want the cpufreq things too?
<colemickens>
I'm still really surprised that search worked out. Hmph. And yeah, I'll skim through this, and another repo that I see is linked in a comment in w-p-p already and see if there's anymore goodies to pickup.
<samueldr>
I'm kinda surprised that search worked too
<samueldr>
try to get something useful out of debian
<samueldr>
I haven't tried since they switched to an internal gitlab though
<samueldr>
colemickens: w-p-p?
<colemickens>
wip-pinebook-pro
<samueldr>
oh
<samueldr>
hahaha, that repo name is so bad :)
<eyJhb>
we pee pee?
iqubic` has left #nixos-chat ["ERC (IRC client for Emacs 28.0.50)"]
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-chat
<worldofpeace>
colemickens: I'm a part of the elementary org
<worldofpeace>
I believe slack (the community one) is the best way to reach
<worldofpeace>
though tbh, when I wasn't a part of the org u barely get any response from the devs there
<worldofpeace>
so at that point it's pms. or if you have a question I could forward it
<samueldr>
luckily I believe it's all laid bare for what was desired
<samueldr>
+1 for elementary making their repos easy to reach, and not a complete mess like some other distros
<worldofpeace>
samueldr: yep, they're very organized in lots of ways 😺
<sphalerite>
I now have alerting for my devices' battery levels via prometheus. That's the normal way to do it, right?
<gchristensen>
I have that, and also for my SmartThings devices ...
<samueldr>
sphalerite: tv remote?
<sphalerite>
samueldr: I don't have a TV, much less a remote for it :)
<sphalerite>
gchristensen has it too, it must be the normal way. :D
noonien has quit [Quit: Connection closed for inactivity]
<worldofpeace>
I hope yall are studying the blade like good kids rn
<sphalerite>
oh btw gchristensen given that you closed nixops#665 but apparently had the need for it — how are you handling this nowadays, or do you no longer need multiple nixpkgs versions in one deployment?
<energizer>
sphalerite: laptop only, or also phone?
<sphalerite>
energizer: only the laptop, for now… Will monitor one or two of my phones when I get the mobile-nixos wifi working, and the other if I can be bothered to look for a node-exporter-like thing for android :)
<energizer>
there's actually a battery-level api in browsers, so you could probably just have your phone connect a browser to your own server and query for battery level
tokudan has quit [Remote host closed the connection]
tokudan has joined #nixos-chat
tokudan has quit [Remote host closed the connection]
tokudan has joined #nixos-chat
<sphalerite>
energizer: sure, if I want to have the web page open in order to get the alerts :p
<sphalerite>
also, my phone is usually going to be the device through which I receive the alerts, so eeeeh
<energizer>
sphalerite: yeah i'm not sure if it works in the background or not
<sphalerite>
I don't think it does
<sphalerite>
I could use a level of indirection like the home assistant app, then use the prometheus exporter for home assistant
<sphalerite>
but I can't use the home assistant app because it has a hard dependency on gapps
<sphalerite>
nonetheless something like that should be possible and probably exists.
<colemickens>
sphalerite: seems silly that it needs gapps given it feels like it's mostly a webview wrapper -_-
<sphalerite>
colemickens: is it really? I had the impression that it does a fair bit more
<samueldr>
I am using the web GUI instead on device
<colemickens>
oh wow, interesting sphalerite that's a well-documented page
<colemickens>
(and I stand corrected)
<colemickens>
samueldr: I continue to try the native app every few months and constantly find that I have to "swipe it away" on Android and re-open it to get it to 'load', versus the webapp that acts like I expect.
<samueldr>
:|
<samueldr>
good thing I don't really like home-assistant, and the only reason it's still setup is that it'd make it easier to tweak that one lightbulb that's not on hue
<colemickens>
very cool, a testament to how big H-A has gotten
<colemickens>
It's not as appealing to me anymore, but my dad has been able to do an impressive amount of stuff iwth it already.
<sphalerite>
yeah it's very powerful and convenient
<sphalerite>
* except for its nix packaging
* sphalerite
is ashamed to admit he runs it as a docker image because the nix stuff is too much of a pain
<sphalerite>
samueldr: why do you not like home-assistant?
<samueldr>
the experience to me felt... so bad
<samueldr>
it took restarting HA two times for the bulb to finally show up
<samueldr>
and it feels like HA is not what I want, either
<samueldr>
HA seems to rather be "MQTT toolkit where you fill it with many source of misc. data"
<samueldr>
what I want is "control my damn lights"
<colemickens>
samueldr: when did you last try it?
<samueldr>
couple months back
<samueldr>
so, other than the issue with getting the thing paired, it's more that I don't fir its use case
<samueldr>
so it feels like I'm having to carve a part out of it for my use, which gets clunky
<samueldr>
and, saying it again, it's more that I don't fit the use case it's apparently designed for
<sphalerite>
fair enough
<samueldr>
what I want is more of a "looking glass" over the state of the smart devices on my network, rather than some kind of historical almanach of data points
<samueldr>
looking glass where I can reach in and change the state
<samueldr>
and maybe make rules acting on instantaneous or time-based events, but that's not even strictly something I would like in the same software
<sphalerite>
I think I fit the use case quite well, but I do find it clunky as far as the automation language is concerned
<sphalerite>
and it's definitely not lightweight :D
* sphalerite
has just installed the minimal app :)
<sphalerite>
colemickens: thanks for prompting me to check again! I was very pessimistic about the whole thing because they'd reacted in quite a hostile fashion for the issue where it was asked about
<colemickens>
that's my home-assistant setup using the nixos module that mic\92 mostly maintains
Church- has quit [Ping timeout: 258 seconds]
<sphalerite>
colemickens: idk if I've been unlucky, but during the times where I used the nixos module, I constantly had failing rebuilds because of some python dep breakage
<colemickens>
sphalerite: yes, I have had to keep a separate nixpkgs around for it that progresses at its own rate for that reason
<sphalerite>
right
<sphalerite>
yeah I really couldn't be bothered with that x)
Church- has joined #nixos-chat
Church- has quit [Ping timeout: 258 seconds]
Church- has joined #nixos-chat
Church- has quit [Quit: WeeChat info:version]
aleph- has joined #nixos-chat
julm has quit [Ping timeout: 260 seconds]
disasm has quit [Ping timeout: 264 seconds]
disasm has joined #nixos-chat
<drakonis>
haha god damn it i'm back on nix
<drakonis>
nothing is as easy and painless as nix
<samueldr>
NixOS please :)
julm has joined #nixos-chat
<ashkitten>
,locate bin nfsd
<{^_^}>
Found in packages: nfsUtils, linuxPackages.bcc, linuxPackages_4_4.bcc, linuxPackages_4_9.bcc, linuxPackages_5_5.bcc, linuxPackages_4_14.bcc, linuxPackages_4_19.bcc, linuxPackages-libre.bcc, linuxPackages_hardened.bcc, linuxPackages_xen_dom0.bcc, linuxPackages_latest-libre.bcc, linuxPackages_latest_xen_dom0.bcc, linuxPackages_testing_bcachefs.bcc, linuxPackages_testing_hardened.bcc, linuxPackages_latest_xen_dom0_hardened.bcc
<ashkitten>
how do i get nfsd...
<Ashy>
drakonis: it really is ahead of it's time aye
<Ashy>
shame it still has such a high learning curve but i think a "batteries included" config for new installs would go a long way
<Ashy>
i might bash one together soon and see what people think
<drakonis>
NixOS sure
<drakonis>
laziness gets the best of me
parsley936 has quit [Remote host closed the connection]
<Church_>
Welp RIP my tt-rss setup
<Church_>
Seems tt-rss can't read any of my stuff in my pg db?
<abathur>
I don't always add dumb bugs to my tests, but when I do, they tend to obscure subtle problems with something I thought I'd already fixed