Hi, [email protected] wrote (18 Feb 2014 13:38:01 GMT) : > From what I understand in the code, tails-upgrade-frontend-wrapper uses > its own logic to determine that Tor is ready.
IIRC, it uses the same logic as our (old) security check wrapper uses. > Why doesn't it reuse /usr/local/sbin/tor-has-bootstrapped, as the "Tor > is ready" notification and Iceweasel launcher? That's exactly my plan (sorry, I should have created a ticket about it already, but it's on my personal TODO list). I was initially wary to do so, as I generally dislike anything that's based on parsing log files, but well, I probably will work better. Likely tails-security-check-wrapper will need to be converted to tor-has-bootstrapped as well. > I've seen the upgrader tell me that it couldn't check for upgrades even > if I had some connectivity (in VMs mostly). And the thread "Error > message while booting Tails 0.22.1" on tails-support is pretending the same. Same here. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc _______________________________________________ tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
