BUG Community

Hi All,

I’m trying to get the device name changed on the Bug base so that it can report itself to a server.

I can get the name changed temporarily by doing this:

1. vi /etc/hosts and change the name

2. do a hostname ‘name’ from the command line

3. vi /etc/hostname and change the name

4. check this with cat /proc/sys/kernel/hostname 

However when I reboot the device name changes to ‘localhost’. I suspect there is probably another file somewhere that I need to change.

Any advice?

Thanks!

-Jer 

Hi Jer,

Your steps seem right to me. Here’s what I did just now and verified it renames my BUG:

1. vi /etc/hostname

and change BUG to something else. Let’s say we rename to “myBUG.”

2. vi /etc/hosts

and change “localhost bug” to “localhost mybug”. This basically allows you ping your BUG’s web server with a friendly name.

After you restart your BUG and ssh in, you should see root@myBUG at the prompt.

Let me now if you have any issues.

Thanks,
Amie

I’ll try it again.

It might be I’m retrieving the device name wrong in my app:

try{

      InetAddress ownIP=InetAddress.getLocalHost();

      mName = ownIP.getHostName();

    }catch (Exception e){

      System.out.println(“Couldn’t set device name =”+e.getMessage());

    }

This code sends the correct device name after I change the device name with the steps above, but it doesn’t ‘stick’ after restart.

I’ll poke around and see if I can figure it out.

Thanks.

-Jer

Hi Jer,

If I remember correctly you’re using a Angstrom build from jconnolly? If this is the case this might be a defect. I will email this thread to JC and see if he has any ideas.

Thanks,

Brian

Works for me:

root@mybug123:~# tail -n 5 /var/log/concierge.log [Wed Feb 03 13:15:57 GMT 2010] [DEBUG] UAM INSTALL /usr/share/java/apps/HostnameTest.jar [Wed Feb 03 13:15:57 GMT 2010] [DEBUG] UAM START file:/usr/share/java/apps/HostnameTest.jar ------------------------- Name:mybug123 ------------------------- root@mybug123:~# cat /etc/hosts 127.0.0.1 localhost.localdomain localhost mybug123 10.10.10.1 bughost root@mybug123:~# cat /etc/hostname mybug123 root@mybug123:~# reboot Broadcast message from root (ttymxc/4) (Wed Feb 3 13:16:21 2010): .... .-------. | | .-. | | |-----.-----.-----.| | .----..-----.-----. | | | __ | ---'| '--.| .-'| | | | | | | | |--- || --'| | | ' | | | | '---'---'--'--'--. |-----''----''--' '-----'-'-'-' -' | '---' The Angstrom Distribution mybug123 ttymxc4 Angstrom 2009.X-stable mybug123 ttymxc4 mybug123 login: root root@mybug123:~# cat /etc/hosts 127.0.0.1 localhost.localdomain localhost mybug123 10.10.10.1 bughost root@mybug123:~# cat /etc/hostname mybug123 root@mybug123:~# cat /var/log/concierge.log --------------------------------------------------------- Concierge OSGi 1.0.0.RC3 on Linux 2.6.27.2 starting ... --------------------------------------------------------- [Wed Feb 03 13:18:04 GMT 2010] [DEBUG] UAM START file:/usr/share/java/apps/HostnameTest.jar ... ------------------------- Name:mybug123 ------------------------- ...

Thanks, John…

This all seems to be working, now. One of the devices early on switched to ‘localhost’ for a device name but I may have just done something wrong.

We’re one day away from the opening here and things are almost under control.

The big issue is with WiFi – getting the bugs to ‘smartly’ connect to the right network is still a manual process, which is somewhat irritating. But, all in all, we are in good shape.

Cheers,

-Jer

I’ll try to get into that today.  I’ll keep it within this thread and let you know

Thanks again.

In the case where a device loses signal, and then moves into another zone, it does appear to pick up a signal eventually, but after a long delay.

I wonder if the frequency of checking networks can be increased? Just a thought.

-Jer

I think I’ve found where to change the scan interval:

In the /var/lib/connman/ directory, there is a set of config files.

It looks like there’s one master config file (in my case it’s called dev_001988202648.conf) which has some global settings:

[Configuration]

Policy=auto

Priority=100

ScanInterval=300

Yeah that makes sense:

<a href="http://docs.enlightenment.org/api/e_dbus/html/e__connman__device_8c.html">http://docs.enlightenment.org/api/e_dbus/html/e...</a>

I don’t have access to “many” AP’s in the office so it would be difficult to test your scenario.  Let me know how it goes.

Changing the interval doesn’t seem to help.

Even selecting networks manually has always been problematic. Half the time, there are no networks listed in the drop down. 

I will continue forward and see what I can do. 

You may want to try some of the artifacts built with connman… there are test utilities that may be of some value even for use by your application:

http://bugcommunity.com/downloads/files/connman…

One thing to try is using the GUI to list networks, then at the same time try the command line utility in that tarball.  This should tell you if it’s just a crappy GUI problem.  connman-gnome support has been pretty much dropped by their community so I wouldn’t doubt that there are quirks and unfixed bugs.

Connman…

Personally I am using wpa-supplicant directly and store common used networks in it’s config: /etc/wpa-supplicant.conf. But it works just because I do not use connman and my bug devices are always connected by Ethernet.

Is there a way to scan and auto-connect to nearest networks though?  I think that’s the clincher

jc: no idea how connman solves that but wpa-supplicant can be told to which networks it has to connect, which ones are more preferred then others etc.

http://blog.jasondonenfeld.com/248 is nice read

This sounds like exactly what you need Jer.  I would definitely try using wpa_supplicant and disabling or removing connman entirely.

OK. I will maybe get the chance to dig into this. Our show is up and running in 2 hours so there’s not much I can do for now!

We’ll take and post a bunch of photos.