The patch will be added in a later commit.
zfs 2.0.x requires linux 3.10 or greater. Backporting looks difficult and probably not worth the effort.
If tomato is ever ported to aarch64 architecture with newer kernel then upgrading zfs will be simple.
libuuid and libblkid from e2fsprogs are not zfs aware.
e2fsprogs only focuses on ext* filesystems, so compile those libraries from util-linux.
Then we'll static link them to zfs binaries.
The patch will be added in a later commit.
zfs 2.0.x requires linux 3.10 or greater. Backporting looks difficult and probably not worth the effort.
If tomato is ever ported to aarch64 architecture with newer kernel then upgrading zfs will be simple.
If a dead AvahiEntry cleanup is scheduled, and we try to schedule
another one, defer the existing callback by 1s. Also remove other calls
to avahi_cleanup_dead_entries.
This is done to ensure that an entry stays in the dead state for at
least 1 second, so that if we receive a copy of our own probe we don't
think it's a conflict.
This should resolve issues where on startup the server spuriously
conflicts with itself and renames to hostname-2, hostname-3, etc. This
typically happens as addresses are rapidly added and removed, e.g. when
IPv6 global addresses cause the link local address to be revoked.
Ideally to prevent excess memory usage we would track the age of the
entries and expire them sooner to prevent the schedule being deferred
forever on a busy server.
Fix from upstream: 0a536f6082
- sync IPv4/IPv6 infos in two steps (wl first, then wired devices)
- do not touch wds
- fix some visual problems showing wireless clients as a lan client
tested with DHCPv6 and IPv6 Tunnel, working correct now :)
Note: update for the following commit
455984a762
M_ars
pedro
Jeremy Tan
lancethepants