Difference between revisions of "Avahi Configuration for Pidora"
(→Project News) |
(→Goals by Release) |
||
| Line 52: | Line 52: | ||
<!-- 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 | + | • Avahi 0.6.31 working |
• Automatic configuration working or near completed | • Automatic configuration working or near completed | ||
| Line 58: | Line 58: | ||
• Automatic configuration completed | • Automatic configuration completed | ||
| − | • Avahi packaged | + | • Avahi 0.6.31 packaged |
• Successful build on ARMv6 | • Successful build on ARMv6 | ||
Revision as of 12:14, 20 October 2013
Contents
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
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.
I intend to use as pristine sources as I can get, although the first few hours of my project will be devoted to familiarizing myself with the Pi.
I will also probably have to install some form of Avahi on a PC at home to test operation.
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 0.6.31 working
• Automatic configuration working or near completed
- 0.2
• Automatic configuration completed
• Avahi 0.6.31 packaged
• Successful build on ARMv6
- 0.3
• RPM package in Pidora repo/distribution
Communication
Mailing Lists
Unsubcribed because Seneca outlook would not sort these email into a separate folder.
Upstream Wiki and Web
Links/Bugs/Tracking
Source Code Control
To be added soon.
Blogs
Non-Seneca Participants
Planets
Project News
Oct 20th, 2013
• I have purchased and setup my Pi. It is running Pidora from NOOBS. [Here is the blog post] on my setup experience.
• Testing of Avahi and nss-mdns has begun.
• I will install, test, and package with the newest version of avahi (0.6.31) as part of this project.
Skullhat 13:11, 20 October 2013 (EDT)
Oct 9th, 2013
• I have purchased some equipment for my Raspberry Pi and intend to buy the unit this week.
Skullhat 13:11, 20 October 2013 (EDT)
Oct 2nd, 2013
• I will be purchasing a Raspberry Pi and the equipment required to begin my project within the coming week or two.
Skullhat 13:11, 20 October 2013 (EDT)
