I've figured out more about why my first install of 0.4 went so badly.
For some reason, the network interfaces weren't configured properly
on first boot (even though the files were in the right places).
In conjuction with having the cable to my wired net plugged into the
LAN port, nothing was
Wad,
If you are pointing to localhost in resolv.conf, will there be at least a
caching DNS named server to catch it?
--HH
On Tue, Aug 26, 2008 at 10:08 AM, John Watlington [EMAIL PROTECTED] wrote:
I've figured out more about why my first install of 0.4 went so badly.
For some reason, the
On Aug 26, 2008, at 4:47 PM, Martin Langhoff wrote:
That sounds like network_config crashed on you. network_config is
responsible for creating /etc/resolv.conf.in and then domain_config
will do the rest. On xs-0.4, we call domain_config at install time
(and it defaults to random.xs.l.o).
On Wed, Aug 27, 2008 at 7:50 AM, John Watlington [EMAIL PROTECTED] wrote:
The proposed change to the operation of the xs-config
package seem sane, with a few comments:
Thanks!
The make-a-replacement strategy is the crucial one.
I have hesitations about the xs-config.make file
used:
My
On Tue, Aug 26, 2008 at 4:43 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
HTTPS has many problems. None of the basic XO protocols use HTTPS.
Will we never care for end-user privacy?
We do. We just don't use HTTPS. You should know better.
- At the protocol layer you mask a whole
On Wed, Aug 27, 2008 at 10:48 AM, C. Scott Ananian [EMAIL PROTECTED] wrote:
On Tue, Aug 26, 2008 at 4:43 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
HTTPS has many problems. None of the basic XO protocols use HTTPS.
Will we never care for end-user privacy?
We do. We just don't use HTTPS.
On Tue, Aug 26, 2008 at 7:17 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
Network principles is a nice statement of desired ideal network
topology. Which we may implement one day - but I am delivering a
network topology and the _main source of XO services_ on a very tight
timeframe and with
On Tue, Aug 26, 2008 at 7:40 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
http://wiki.laptop.org/go/Network_principles#Disconnected_operation is
a principled means to substitute unavailable resources in the offline
case.
The solution you suggest has problems, and I mentioned them in my
On Tue, Aug 26, 2008 at 07:53:19PM -0400, C. Scott Ananian wrote:
On Tue, Aug 26, 2008 at 7:40 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
http://wiki.laptop.org/go/Network_principles#Disconnected_operation is
a principled means to substitute unavailable resources in the offline
case.
