openwrt post-flash
# set root password telnet 192.168.1.1 passwd # install web UI ssh root@192.168.1.1 opkg update # if you'll get 404 errors, edit /etc/opkg.conf and change the package paths: # https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/packages/packages opkg install luci-ssl # if you have default_postinst: not found, script returned status 127 errors, check if the package version is ok: http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages maybe? # remove & try again: opkg remove --force-remove luci-ssl px5g libustream-polarssl libpolarssl luci luci-proto-ppp luci-mod-admin-full luci-base luci-lib-nixio uhttpd-mod-ubus uhttpd lua luci-app-firewall luci-theme-bootstrap libiwinfo-lua liblua libuci-lua rpcd luci-lib-ip libubus-lua # start web server /etc/init.d/uhttpd start /etc/init.d/uhttpd enable # enable wifi uci set wireless.@wifi-device[0].disabled=0; uci commit wireless; wifi uci show wireless | grep disabled
login to https://192.168.1.1 and do the rest...
zfs and portage’s var directories
While /var
is usually for non-crucial content, caches[3], pid files, etc, portage has a different idea [1]:
/var/db/pkg Portage stores the state of your system
/var/lib/portage The versions for the applications you have explicitly installed
These directories store the current tree state, there is no way recreating them if they are deleted.[2]
So if you plan to use ZFS with separate /
and /var
to take a snapshot of /
, install some packages and then rollback the snapshot as you changed your mind, your /
and /var
will be out of sync!
/var/db/pkg
and /var/lib/portage
has to be on /
.
mkdir /usr/var_db_pkg /usr/var_lib_portage cp -r /var/lib/portage /usr/var_lib_portage cp -r /var/db/pkg /usr/var_db_pkg rm -rf /var/lib/portage /var/db/pkg ln -s /usr/var_lib_portage /var/lib/portage ln -s /usr/var_db_pkg /var/db/pkg
[1] https://wiki.gentoo.org/wiki/Directories
[2] Or at least it is painfull. To avoid the initial circular-dependency hell, issue:
emerge --nodeps dev-lang/perl dev-lang/python dev-libs/libxml2 dev-util/cmake dev-util/pkgconfig sys-apps/acl ys-apps/systemd sys-devel/automake sys-libs/glibc sys-libs/ncurses sys-libs/zlib virtual/libudev
[3] what you'd have to recreate: powertop's calibration measurements, gentoolkit's busybox and initramfs
zfs set ditto blocks after file system creation
"The copies property works for all new writes, so I recommend that you set that policy when you create the file system or immediately after you create a zpool." [1]
So how can you force a complete reread-rewrite?
With (non-incremental) backup and restore:
# settings properties won't work: zfs set copies=2 POOL/FS zfs snapshot SNAPSHOT zfs send SNAPSHOT | xz --threads=12 --verbose > FILE.img.xz zfs destoy POOL/FS xz --threads=12 --decompress --verbose FILE.img.xz -c | zfs receive POOL/FS # so you have to create & override a new FS with copies=2 zfs snapshot SNAPSHOT zfs send SNAPSHOT | xz --threads=12 --verbose > FILE.img.xz zfs destoy POOL/FS zfs create ... -o copies=2 POOL/FS xz --threads=12 --decompress --verbose FILE.img.xz -c | zfs receive POOL/FS -F
[1] https://blogs.oracle.com/relling/entry/zfs_copies_and_data_protection