Jump to content
funtoo forums


Popular Content

Showing most liked content since 05/23/2018 in all areas

  1. 1 point
    is in the /var/db/pkg/app-crypt/qca-2.1.3-r2/qca-2.1.3-r2.ebuild before has qt4 and qt5 IUSE , now have no! PS: if u remove kdelibs your kde goes broke!!!!
  2. 1 point
    working on this problem
  3. 1 point
    yes, I know that one exactly. ... Once it will be fixed :)
  4. 1 point

    ZFS Mountpoints

    Supported boot parameters rollback=<on|yes|1> Do a rollback of specified snapshot. zfs_debug=<on|yes|1> Debug the initrd script zfs_force=<on|yes|1> Force importing the pool. Should not be necessary. zfs=<off|no|0> Don't try to import ANY pool, mount ANY filesystem or even load the module. rpool=<pool> Use this pool for root pool. bootfs=<pool>/<dataset> Use this dataset for root filesystem. root=<pool>/<dataset> Use this dataset for root filesystem. root=ZFS=<pool>/<dataset> Use this dataset for root filesystem. root=zfs:<pool>/<dataset> Use this dataset for root filesystem. root=zfs:AUTO Try to detect both pool and rootfs In all these cases, <dataset> could also be <dataset>@<snapshot>. Booting from snapshot: Enter the snapshot for the root= parameter like in this example: linux /ROOT/funtoo-1@/boot/vmlinuz root=ZFS=rpool/ROOT/funtoo-1@some_snapshot ro boot=zfs $bootfs quiet This will clone the snapshot rpool/ROOT/funtoo-1@some_snapshot into the filesystem rpool/ROOT/funtoo-1_some_snapshot and use that as root filesystem. The original filesystem and snapshot is left alone in this case.
  5. 0 points

    emerge @preserved-rebuild trouble

    If you look closely, you see that this bug report is closed and marked as fixed. So you would need to open a new bug.