<clever>
spinus: yeah, that will wrap the bash with more bash
<clever>
boomshroom: lib.intersectLists i believe
<clever>
and nixpkgs.config in configuration.nix can take the exact same values, and is used for any package that configuration.nix refers to (like systemPackages or services)
<clever>
config.nix is uses for nix-env/nix-shell/nix-build
<clever>
spinus: you need to modify the $PATH inside the bash script to include references to the things your running, or embed absolute paths into the bash scripts
<clever>
spinus: and propagatedBuildInputs are only present at build-time for things depending on your package
<clever>
spinus: buildInputs are only present at build time
<clever>
yeah, i think 100% for extended perioids would wake the neighbors...
<clever>
and let me do a quick experiment...
<clever>
at 0% its just gone
<clever>
at 5% its too loud
<clever>
one tick lower, and its on mute
<clever>
the volume in the website only moves in 5% increments
<clever>
the volume controller in the browser is at 5%, chrome in pulse is at 53%, the master is at 94%, and the external volume on the speakers is at 21
<clever>
as an example, i am playing a song on a website right now
<clever>
yeah, so i can just type in an absolute number
<clever>
so i get 4 times the resolution on the sliders
<clever>
under pulse, i can use the master sliders to cut the total volume by 1/4th
<clever>
that window isnt resizable
<clever>
nope
<clever>
and the mouse just isnt sensitive enough to set that well :P
<clever>
i had to keep it like 3 or 4 pixels from 0 at all times
<clever>
the problem, is that my headset is too loud, by default
<clever>
so if you turn the master down to 5%, then you can only use 0% to 5% on the applications
<clever>
the master volume slider in its mixer, doesnt scale the applications, it sets a max
<clever>
i recently had the "pleasure" of running windows again, lol
<clever>
oh, and speaking of audio problems
<clever>
in a pure manner
<clever>
it would let you sed the libc or openssl path, recursively, on an entire nixos build
<clever>
and where did i even leave that patch? ... lol
<clever>
so i had to patch pulseaudio to even get that working
<clever>
and pulseaudio doesnt support using an index in the profile config
<clever>
but every mux has the same name
<clever>
the card has a mux for every port, so you can switch them between the internal pipelines
<clever>
and also, pulse doesnt support a critical feature i needed
<clever>
the profiles are stored in the pulseaudio derivation
<clever>
and nix requires all of pulseaudio to be recompiled to change those config files
<clever>
my card is missing a lot of profiles
<clever>
yeah, as viewed by pulseaudio
<clever>
i have played with that area of pulse before, because my card happens to have 3 pipeliness, and can potentialy drive the front, rear, and digital all at once, with different content
<clever>
which mutates all of the routing config within pulseaudio
<clever>
ah, because the profile on the configuration tab changed
<clever>
and i even loose the option to send the audio back to the digital output
<clever>
sphalerite: the instant i plug headphones into the front jack, it says headphones
<clever>
sphalerite: heh, i opened pavucontrol, went to the "output devices" tab, and the built-in audio was on digital output (the optical jack on the back)
<clever>
add in headphones, and you have an instant heart-attack and deafness :P
<clever>
on the other hand, i have other laptops, where the console beep is ear-splittingly loud, at the lowest setting
<clever>
so console beeps would leak whatever you where trying to listen to privately, to the whole room
<clever>
so you would get a mix of beep + music, on the case speaker
<clever>
but it only had 1 dac
<clever>
i had one card, that would switch back to the laptop speaker for pc-beeps
<clever>
with some cards, you can manualy switch between the speaker and headphone in alsamixer
<clever>
sounds similiar to what ive noticed, the state in software was out of sync with the state in hardware
<clever>
ah
<clever>
sphalerite: try restarting pulseaudio after resuming, and see if that fixes it?
<clever>
and then youll be the one finding all of those bugs
<clever>
you would have to manualy clone nixpkgs master and set nixos-rebuild to use that
<clever>
to prevent broken stuff from reaching users
<clever>
it builds pretty often, but all tests must pass before nixos-unstable will update
<clever>
users.extraUsers is an alias of users.users
<clever>
and was nixos-install re-ran after the change?
<clever>
was it inside the users.users.foo block for your user?
<clever>
and nixos will set that when creating it on bootup
<clever>
yeah, you can add .initialPassword = "hunter2";
<clever>
it has to boot at least once, then its simpler to just login as root and passwd
<clever>
that doesnt run the activation scripts, so the /etc/passwd isnt updated yet
<clever>
*looks*
<clever>
normal chroot or nixos chroot?
<clever>
so if you add that setting and reboot, it wont change the pw
<clever>
and the initial options only apply when nixos initialy makes the user
<clever>
Nobabs27: nixos-install will only ask for the root password, you have to either run passwd to set all others, or set something like .initialPassword or.initialHashedPassword
<clever>
causing the opensource driver to re-crash every time i login
<clever>
xfce also tries to help too much, and restores the dual-monitor config on login
<clever>
the unfree amd driver crashes xorg if i unplug the 2nd monitor while its active
<clever>
the opensource amd drivers crash xorg if i turn on 2 monitors
<clever>
i rely on too much unfree garbage
<clever>
ive heard of it but havent really looked into it
<clever>
you could then do "exec /nix/var/nix/profiles/system/init" when done, to resume the boot
<clever>
so the shell entirely replaces your init system
<clever>
hydraz: if you import <nixpkgs> and set crossSystem correctly, it will enable the use of cross-compilers
<clever>
but replugging it resends the state change and fixes it
<clever>
and in some of my systems, pulseaudio must actively initiate the switch, and it doesnt work if the headphones are plugged in while pulse is off
<clever>
dash: headphone jacks in modern hardware have a switch to detect the presence and switch over actively
<clever>
sphalerite: double-check pavucontrol while plugging it in
<clever>
not sure then
<clever>
pbogdan`: are those things in the buildInputs already?
<clever>
ircuser5678: you can also 'man configuration.nix'
<clever>
it will always come back at boot or switch
<clever>
oh, and i often delete the /etc/nix/machines symlink to temporarily turn remote builds off
<clever>
it might be that some env variables like NIX_BUILD_HOOK had been cleared accidentaly
<clever>
strange
<clever>
freusque2: --option binary-caches ""
<clever>
what error does it fail with?
<clever>
and you dont have any import <nixpkgs>{}'s anywhere in your expresions?
<clever>
LnL: are you using your own default.nix or the nixpkgs/default.nix?
<clever>
its the only service that does that
<clever>
the ssh service automaticaly opens the port you set it to
<clever>
ive run into similiar problems when trying to package gradle stuff in nix
<clever>
yeah, i would keep a git repo with nix+cargo.lock pairs, you could just overwrite them, and let git history keep the history
<clever>
about all i can think of is to run "cargo generate-lockfile" inside a nix-shell against a copy of $src
<clever>
but once upstream changs things, generate-lockfile will make something differnt, and fetch just fails
<clever>
i was thinking a fixed-output derivation can generate the cargo.lock
<clever>
ah wait, what i was thinking wont work right
<clever>
boomshroom: what is the command you run to generate a cargo.lock?
<clever>
and nix uses a slightly different algo for hashing $out, so you cant reuse hashes upstream gives
<clever>
boomshroom: so your free to do pretty much whatever you want in there, as long as its reproducable, and you declare the final hash (nix-build will tell you the right one)
<clever>
boomshroom: any derivation that defines these 3 attributes is fixed-output, it will get network access, and the hash of $out must match what it declared
<clever>
boomshroom: though if you flag it as fixed-output, you can get network, but youll need to run that generate step twice
<clever>
boomshroom: nix does a good deal to ensure all builds are pure, so a normal nix build cant get network access to query things and make the cargo.lock