Difference between revisions of "Avahi Configuration for Pidora"

From CDOT Wiki
Jump to: navigation, search
(Goals by Release)
Line 47: Line 47:
 
<!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
 
<!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
 
* 0.1
 
* 0.1
 +
• Avahi working
 +
• Automatic configuration working or near completed
 
* 0.2
 
* 0.2
 +
• Automatic configuration completed
 +
• Avahi packaged
 +
• Successful build on ARMv7
 
* 0.3
 
* 0.3
 +
• RPM package in Pidora repo/distribution
  
 
== Communication ==
 
== Communication ==

Revision as of 21:16, 2 October 2013

Avahi Configuration for Pidora

Project Description

Avahi (zeroconf) enables discovery of computers without DNS or IP numbers. This project involves configuring Avahi for use on the Raspberry Pi, so that other computers can connect to it by name without DNS support. This configuration must then be packaged in such a way that it can be included in the Pidora composes without causing conflicts.

Project Leader

Taylor Barras (tsbarras)

Project Contributor(s)

None

Project Details

Since the Raspberry Pi utlizies the same NIC throughout its two models, I predict that getting avahi to work should only be a matter of customizing the configuration files to fit the hardware on install (unless this is done automatically, like while running a configuration).

My main resource will be the Avahi website and the references that are linked to from that page.

DNS Service Discovery

Multicast DNS

D-Bus


Project Plan

Tracking

For tracking I plan to use github. My github is located here.

Key contacts

None yet

Goals by Release

Goals for each release and plans for reaching those goals:

  • 0.1

• Avahi working • Automatic configuration working or near completed

  • 0.2

• Automatic configuration completed • Avahi packaged • Successful build on ARMv7

  • 0.3

• RPM package in Pidora repo/distribution

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

Non-Seneca Participants

Planets

Project News