Currently, btrfsprogs is misdetected by nix such that it requires
specifying btrfs-progs-v3.12 for install instead of just btrfs-progs.
This patch removes the v so that it now reads btrfs-progs-3.12 and is
properly detected by nix.
Currently, the command btrfs scrub start <filesystem> attempts to invoke the pthread_cancel
routine and ends with an error melibgcc_sssage about it being missing. This prevents btrfs
scrub status from maintaining proper statistics about the running scrub.
Close#1127.
There are many more packages to fix, this is just a start.
Rules:
* Don't repeat the package name (not always that easy...)
* Start with capital letter
* Don't end with full stop
* Don't start with "The ..." or "A ..."
I've also added descriptions to some packages and rewritten others.
Contains the following fix:
- Fix mounting btrfs when mount_only (-m) is used.
I would like to update blivet as well, but at the moment it breaks for
nixpart, so let's retry later when we're at 0.5.x or even 1.x :-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Changes are:
- Properly detect GPT disklabels and create proper BIOS boot partitions
if necessary.
- Return exit code 100 if reboot is required due to the kernel not
picking up the new partition table.
- Don't include BIOS boot partition in GRUB devices.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This fixes two issues:
- Don't _always_ print out NixOS configuration, only when explicitly
requested with -p.
- Add GRUB boot devices to NixOS configuration output.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This makes it possible to mount unionfs directly with mount or fstab.
Example fstab entry:
none /mnt/union unionf-fuse allow-other,dirs=/source1=RW,/source2=RW
Note, the dirs= option need to be the last option, due to limitations
in the mount helper provided by unionfs-fuse. Maybe we should write a
better helper ourselves.
Also, you need to specify your branches as dirs= option, NOT as
the device, since the latest version of libmount always interprets
"=" characters in the device name as a tag (like LABEL, UUID etc)
and will try to resolve the tag before calling the mount helper.
This will of course not succeed and the mount will fail.
Conflicts:
pkgs/applications/networking/browsers/chromium/default.nix
pkgs/top-level/all-packages.nix
Merge conflicts seemed trivial, but a look from viric and aszlig would be nice.
