On Tue, May 1, 2012 at 11:29 AM, Daniel Drake d...@laptop.org wrote:
In Nicaragua we are seeing cases where XOs have no hostname set, both
on XO-1 and XO-1.5. On XO-1 this is presumably because libertas
usb8388 init was never 100% reliable, and on XO-1.5 its presumably
because the wireless
On May 1, 2012, at 6:49 PM, John Gilmore wrote:
Currently, XO hostnames are set on first boot in the following format:
xo-A-B-C
Where A, B and C are the last 3 bytes of the MAC address expressed in hex.
In Nicaragua we are seeing cases where XOs have no hostname set, both
on XO-1 and
Using the wireless device MAC address as the basis of the hostname seems
wrong to me. It is an overload of meaning. It also has an impact if
the wireless device is changed.
I'm also amused that the hostname needs to be unique, but that is
probably a different issue.
If the need for it to be
On Wed, May 2, 2012 at 3:28 AM, John Watlington w...@laptop.org wrote:
I second this recommendation. While the MAC address in the manufacturing
data may not be correct (if the WLAN card has been changed), it is guaranteed
to be as unique as the laptop serial number.
Talking with Wad about
On Tue, May 1, 2012 at 4:49 PM, John Gilmore g...@toad.com wrote:
Currently, XO hostnames are set on first boot in the following format:
xo-A-B-C
Where A, B and C are the last 3 bytes of the MAC address expressed in hex.
In Nicaragua we are seeing cases where XOs have no hostname set, both
On Wed, May 2, 2012 at 10:52 AM, Daniel Drake d...@laptop.org wrote:
On Tue, May 1, 2012 at 4:49 PM, John Gilmore g...@toad.com wrote:
Currently, XO hostnames are set on first boot in the following format:
xo-A-B-C
Where A, B and C are the last 3 bytes of the MAC address expressed in
hex.
kevin wrote:
On Wed, May 2, 2012 at 10:52 AM, Daniel Drake d...@laptop.org wrote:
On Tue, May 1, 2012 at 4:49 PM, John Gilmore g...@toad.com wrote:
Currently, XO hostnames are set on first boot in the following format:
xo-A-B-C
Where A, B and C are the last 3 bytes of the MAC
On Wed, May 2, 2012 at 1:18 AM, Martin Langhoff
martin.langh...@gmail.com wrote:
On Tue, May 1, 2012 at 11:29 AM, Daniel Drake d...@laptop.org wrote:
In Nicaragua we are seeing cases where XOs have no hostname set, both
on XO-1 and XO-1.5. On XO-1 this is presumably because libertas
usb8388
On Wed, May 2, 2012 at 11:05 AM, Daniel Drake d...@laptop.org wrote:
1 - the code to setup /etc/sysconfig/network is in the wrong place --
it should trigger boot that /etc/sysconfig/network is missing
Yes, we can improve the code that handles this case.
That'll be great :-)
2 - yes,
On Wed, May 2, 2012 at 10:05 AM, Martin Langhoff
martin.langh...@gmail.com wrote:
Yep. In genral, a modprobe/udevtrigger/waitforpath approach seems to work.
I am a bit annoyed that systemd/udev doesn't provide some useful
facilities for this. We are early users, and as such we hit all the
On Wed, May 2, 2012 at 12:14 PM, Daniel Drake d...@laptop.org wrote:
I think they would just point out that the solution we're working
towards is the wrong approach. That is, we're requiring the hardware
to be connected at boot for it to be used. If you connect it after
boot, nothing happens.
Hi,
Currently, XO hostnames are set on first boot in the following format:
xo-A-B-C
Where A, B and C are the last 3 bytes of the MAC address expressed in hex.
In Nicaragua we are seeing cases where XOs have no hostname set, both
on XO-1 and XO-1.5. On XO-1 this is presumably because libertas
On Tue, May 1, 2012 at 11:29 AM, Daniel Drake d...@laptop.org wrote:
Hi,
Currently, XO hostnames are set on first boot in the following format:
xo-A-B-C
Where A, B and C are the last 3 bytes of the MAC address expressed in hex.
In Nicaragua we are seeing cases where XOs have no hostname
daniel wrote:
Hi,
Currently, XO hostnames are set on first boot in the following format:
xo-A-B-C
Where A, B and C are the last 3 bytes of the MAC address expressed in hex.
In Nicaragua we are seeing cases where XOs have no hostname set, both
on XO-1 and XO-1.5. On XO-1 this is
On 05/01/2012 10:29 AM, Daniel Drake wrote:
As far as I can see, the hostname is not really of relevance to
anything except avahi.
But from avahi is how the other XO users identify who is online. I can
never remember which system has which XO-icon color -- but the name (as
shown on hover in
Currently, XO hostnames are set on first boot in the following format:
xo-A-B-C
Where A, B and C are the last 3 bytes of the MAC address expressed in hex.
In Nicaragua we are seeing cases where XOs have no hostname set, both
on XO-1 and XO-1.5. On XO-1 this is presumably because libertas
16 matches
Mail list logo
