There are two issues with the following line.
# echo -e "deb http://deb.i2p2.no/ jessie main\ndeb-src http://deb.i2p2.no/ jessie main" >> /etc/apt/sources.list.d/i2p-release.list
We’ve been consistently using sudo instead of #.
>> appends. > overwrites. I think in this case, to make instructions idempotent, > is better.
For 1 there is no way around it. I tried using sudo and I got permission denied everytime
I can experiment with 2 and see if it can create the file.
The command you’re looking for is probably tee. To echo and to write as use, see the following example.
echo "some thing" | sudo tee ./a >/dev/null
(The >/dev/null is negligible, but it would echo then. I guess that’s more confusing.)
The wording
comes from:
through is ambiguous. That wording has been developed with English native speaker @JasonJAyalaP.
Please undo Connecting to I2P through Tor to the previous Connecting to Tor before I2P for consistency.
Updated the Wiki, please review the changes I made
https://www.whonix.org/w/index.php?title=I2P&oldid=23956&diff=cur
What about adding the config file explanations right into the config file?
Example:
## change router identity and UDP port when IP changes
i2np.laptopMode=true
etc.
I wanted to do that at first, but then I thought it would be overloaded with all this. If you think it would be better to add it then I’ll add it.
I see. I don’t have any strong opinion. Welcome other thoughts.
Since the user has to copy and paste all of that anyhow, I did not think it would matter.
(If we one day create a configuration package for Connecting to Tor before I2P, I2P inside the Whonix-Workstation, user -> Tor -> I2P -> Internet, then the config file explainations should certainly be included inside the config file.)
+1 detailed configuration options belong into the .config
Putting explanations in references is good too. We’ve squashed entire paragraphs in there for other topics on the wiki.
On the workstation at least, we don’t ship openjdk-7-jre-headless by default and so it needs to be installed.
Readded it and accepted changes.
HulaHoop:
On the workstation at least, we don’t ship openjdk-7-jre-headless by default and so it needs to be installed.
Doesn’t the i2p package depend on that package and thereby install it?
If not, would that not be a i2p packaging bug?