This is a RFC about marking miredo stable on amd64 (at least). I've been using it for a while in production and it works fine, that's why I'm asking. If you feel like that's possible, please CC arches. Thanks, Diego
sure - please go ahead
works for me on amd64.
Anyway, checking better, the init scritp fails to modprobe tun(if it is not builtin). Small example from my shell: amd64box ~ # /etc/init.d/miredo start * Starting Miredo ... [ !! ] * ERROR: miredo failed to start amd64box ~ # /etc/init.d/miredo start * Starting Miredo ... [ !! ] * ERROR: miredo failed to start amd64box ~ # modprobe tun amd64box ~ # /etc/init.d/miredo start * Starting Miredo ... [ ok ] amd64box ~ #
amd64; All is good. In host && chroot; gentoo64 / # lsmod |grep tun tun 12712 2 gentoo64 / # /etc/init.d/miredo start * Starting Miredo ...
Testing report for x86; USE='-caps' succeeded for =net-misc/miredo-1.2.3-r1 USE='caps' succeeded for =net-misc/miredo-1.2.3-r1 FEATURES= test succeeded for =net-misc/miredo-1.2.3-r1 No further testing done.
amd64/x86 stable, thanks Agostino, Ian and David