Difference between revisions of "Headless IP Address Communication"

From CDOT Wiki
Jump to: navigation, search
(Created page with '= Headless IP Address Communication = <!-- Replace "Project Name" with the actual name of the project in the line above. --> == Project Description == The Raspberry Pi (and som…')
 
(→‎Source Code Control)
 
(2 intermediate revisions by the same user not shown)
Line 58: Line 58:
  
 
=== Upsteam Wiki and Web ===
 
=== Upsteam Wiki and Web ===
−
*
+
* http://scotland.proximity.on.ca/chris/source/ip-info/
 
<!-- Links to upstream wiki/web pages -->
 
<!-- Links to upstream wiki/web pages -->
  
Line 65: Line 65:
  
 
=== Source Code Control ===
 
=== Source Code Control ===
 +
 +
* ''Not in git yet, will put in GitHub by 0.2''
 
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->
 
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->
  
Line 78: Line 80:
  
 
==== Planets ====
 
==== Planets ====
 +
* [http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet CDOT]
 +
* [http://planet.fedoraproject.org/ Planet Fedora]
 
<!-- Links to any planets related to this project -->
 
<!-- Links to any planets related to this project -->
  

Latest revision as of 12:25, 5 November 2012

Headless IP Address Communication

Project Description

The Raspberry Pi (and some other development boards) may be run "headless" in certain applications - without a monitor connected. However, to connect over ethernet for remote diagnostics, it is necessary to know the IP address of the system. This project involves communicating the address through other available means, such as the LED or audio system.

Project Leader(s)

Chris Tyler

Project Contributor(s)

None so far!

Project Details

The two most obvious ways to provide IP address information are: (1) to flash the programmable LED on the Pi (or other development board) and (2) to "read" the IP address over the audio system

This project involves:

  • creating scripts to do both of these
  • creating the appropriate systemd service files so that the scripts can be run at boot time
  • packaging all of this up for inclusion in Fedora

Project Plan

Tracking mechanism (bugzilla, trac, github, ...):

Key contacts:

  • Fedora-ARM community

Goals for each release and plans for reaching those goals:

  • 0.1
    • Scripts written and tested
    • First draft of the systemd service files
    • First draft of the RPM package
  • 0.2
    • Service files tested
    • Package finalized
    • Package in review
  • 0.3
    • Package review successfully completed

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

  • Not in git yet, will put in GitHub by 0.2

Blogs

Seneca Particpants

Non-Seneca Participants

  • None yet

Planets

Project News

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=Headless_IP_Address_Communication&oldid=90535"