Fixme.ch - User contributions [en]

AG 2017

2017-06-06T22:17:20Z

CrazyGolem: /* Proposition de modification processus Achats */

[[Category:Meetings]]
[[Category:AG]]

== Information ==
* https://pad.fixme.ch/p/ag2017
* https://framadate.org/AqK3qIfvZzh1Qh9o
* Date: 2017-06-23 à 20h

== Ordre du jour ==
* Bilan de l'année 2016
* Approbation des comptes 2016
* Electrion du comité
* Election des contrôleurs des comptes
* Proposition de modifications du processus d'achats
* ...
* Apero

=== Election du comité ===
Sont candidat(e)s:
* Président: ???
* Secrétaire: ???
* Caissier: ???
* Communication: ???
* Événements: ???
* Logistique: ???

'''Ajoutez-vous pour être candidat ;)'''

=== Proposition de modification processus Achats ===

* la demande d'achats est faite sur le chat dans le channel <code>10_achats</code>, au lieu de la mailing list
* Proposition: pour les achats de moins de X CHF?
* Définir un timeout a partir duquel l'achat est validé s'il n'y a pas d'opposition.
* Définir un format spécifique (e.g. mot-clef) qui permet la configuration d'un highlight/trigger
* Actuellement: Achat doit être proposé sur la MailingList, si pas d'opposition après 3 jours -> validé (le comptable a le droit de veto)

== Photos ==
* FIXME
<gallery>
</gallery>

Press kit

2016-09-21T21:58:09Z

CrazyGolem:

== Why ?==
* It's hard to say the right things about FIXME when asked (by people/journalists/...)
* We need documents to explain what we do

== What to say ?==
* Here's what the status says about our goals:
**Promouvoir une utilisation originale, intelligente, éthique et innovante de la technologie
**Promouvoir la liberté d'utiliser, de créer, de modifier les outils techniques
**Mise à disposition et entretien d'un lieu de rencontre, de travail
* So an important thing is we want to be local, accessible and as open as possible

== Dossier de presse ==
=== Le mot du président ===
* FIXME

=== Le concept de Hackerspace ===
* Mise à disposition d'un local équipé
* Encourager et faciliter le partage de connaissances, l'accessibilité au savoir et à l'entre-aide
* Promotion des technologies et de leur libre utilisation
* Réalisation de projets en communs

=== Le Hackerspace de Lausanne===
* Créé en septembre 2010
* Arrivée au 1er local en avril 2011
** Rue de Genève 79, 1004 Lausanne
** 60m² en sous-location
** Local commercial dans un immeuble locatif
* Arrivée au 2ème local en octobre 2014
** Chemin du Closel 5, 1020 Renens
** 37m² en location
** Local commercial dans un immeuble industriel
* Arrivée au 3ème local en septembre 2016 (TBC)
** 117m² en location avec le Fablab Chêne 20

=== Les membres ===
* 29 membres (dont environ 15% d'étudiants) (11.01.2013)

=== Les équipements ===
* Informatique:
** Ordinateurs en libre service,
** Vidéo-projecteur,
** Imprimantes
* Electronique:
** Table d'électronique,
** Matériel de soudure,
** Oscilloscope, générateur de signal,
** Stock de composants
* Divertissement:
** Borne d'arcade,
** Chaine Hifi
** Bibliotèque (magazine, ouvrages de référence, ...)
* Outils:
** Outils légers de découpe, perçage,
* Services
** Outil collaboratifs (Dépôts GIT, Etherpad, Mumble)
** Accès à l'infrastructure à distance (SSH, OpenVPN, FTP)
** Applications web diverses (Gestion des lumières, commande de nourriture, publication du status du hackerspace, controle de la musique)
** Autres: PXE, NTP, NFS, Bouncer IRC, BOT IRC

=== Les activités ===
* Electronique:
** Découverte de l'électronique avec platines d'essais,
** Réalisation de projets en groupe (RFID Door lock, ...),
* Programmation:
** Découverte de la programmation,
** Présentations sur les langages de programmation (Android, Django, Haskell),
** Ateliers de programmation en groupe (Coding Nights),
* Hacking ethique:
** Séances d'entrainement et de formation aux techniques de hacking éthique,
** Participation en équipe à différents challenges de hacking éthique (en ligne et en réel),
* Rencontres:
** Réunion hedbomadaire le mercredi à 19h
** Rendez-vous électronique le lundi à 19h
** Tables rondes (culture, etc)

=== Les interactions externes ===
* Stand aux RMLL 2012 à Genève ainsi que participation active à l'organisation de l'évènement
* Stand aux Journées des Alternatives Urbaines 2013 à Lausanne
* Participations au concours de hacking éthique Insomni'Hack en 2011, 2012 et 2013
* Déplacement au Chaos Communication Congress en Allemagne

=== Les contacts ===
* Comité: comite AT fixme.ch
* Président: Jean-Baptiste Aubort president_AT_fixme.ch
* Secrétaire: Sarah Bourquenoud secretaire_AT_fixme.ch
* Téléphone du local: +4121 622 07 34

== See also ==
* [[Logo]]
* [[Flyers]]
* [[Sticker]]
* [[T-shirt_FIXME]]
* [[Press_reviews]]
* [[Utilité_publique]]

InsomniHack-2016

2016-02-14T12:27:57Z

CrazyGolem: /* FIXME */

[[Category:CTF]]
[[Category:Conferences]]
== Information ==
* http://insomnihack.ch/
* '''Lieu:''' Palexpo Genève
* '''Dates:''' 17-19 mars 2015
** '''CTF:''' Vendredi 18 mars de 18h à 4h
** '''Conferences:''' Vendredi 18 mars
** '''Workshops:''' Jeudi 17 mars

== CTF teams ==
* Team size limit : 8 persons
* Registration [https://www.eventbrite.fr/e/insomnihack-2016-workshop-conferences-contest-registration-19112613341 here]

=== FIXME ===
Participants: Rorist, crazygolem, you here

== See Also ==
* [[InsomniHack-2012]]
* [[InsomniHack-2013]]
* [[InsomniHack-2014]]
* [[InsomniHack-2015]]

T-shirt FIXME

2015-08-28T22:56:28Z

CrazyGolem: /* Crazygolem */

[[Category:Ongoing_Projects]]

== Information ==
* Order custom T-shirts for FIXME
* Sizes: http://www.doodle.com/vwqkhkhf2yck9vk4
* TODO: A tshirt with the Mateist logo on the back http://hsbp.org/polo&highlight=mateist

== Printing companies ==
* Artist making shirts: http://ybdesign.ch/
* http://creacom.ch/
* http://shirtcity.com/ (t-shirt à l'unité possible)
* http://www.affirmatif90.com/ (the one we used for the 1st batch in 2012)

== 2015 batch ==

=== Your proposition ===
* Design and description here

=== Crazygolem ===
'''Back'''<br>
[[File:Proposition tshirt crazygolem.jpg|150px]]
* This is not the final design!
** It should have 59 labeled "holes" (if I counted correctly)
** Also it will probably have holes around the "FIXME" text too, instead of the frame
** The circuits might be drawn as in real life (e.g. optimized for length or other factors unknown to me)
* The design should be big enough to fill the t-shirt on the back, at least in width

'''Front'''<br>
The FIXME logo and text on the chest.

=== Rorist ===
==== Version 1 - The Greedy ====
* The hackerspace rocket, with the moto on the front
* The FIXME text logo on the back
* The head logo on the shoulders
[[File:Proposition_tshirt_rorist.svg|150px]]

==== Version 2 - The Simple ====
* The FIXME text logo on the front, on the heart
* Hackerspace Lausanne text on the back
[[File:Proposition_tshirt_rorist2.svg|150px]]

==== Version 3 - The Mateist ====
* The FIXME text logo on the front, with the Mateist in the center
* Hackerspace Lausanne text on the back
[[File:Proposition_tshirt_rorist3.svg|150px]]

== 2012 batch ==
=== First proposition ===
[[File:Proposition_tshirt.svg|100px]]

* It can be cool to have custom t-shirt for everyone with (IRC) nickname (or other string like HACKER, MAKER, ROOT, STAFF, TEAM, TROLL :) ) on the back, but it can be optionnal.
* All remarks are welcome :)

=== Second proposition ===
We can realise a broderie polo for 21 Fr at http://www.art-image.ch/cgi-bin/marquages_textiles.php. I would propose to only have the fixme logo with fixme under it. They only make batch of 100 pieces.

=== Third proposition ===
* This has been ordered on the on december 2012
[[File:Proposition_tshirt2.svg|100px]]
[[File:Proposition_tshirt3.svg|100px]]
[[File:Proposition_tshirt4.svg|100px]]
[[File:Proposition_tshirt5.svg|100px]]
[[File:Proposition_tshirt6.svg|100px]]

==== Order at Quotation Affirmatif90 ====
http://www.affirmatif90.com/

* They provides 2 types of T-shirts:
** 150 g/m2 [[File:T-SHIRT-150G-B&C.pdf‎]]
** 190 g/m2 [[File:T-SHIRT-190G-B&C.pdf‎]]
* Submitted quantities: 12 M, 14 L, 8 XL and 2 XXL
* First batch (with do-ocraty spelled like in [https://en.wiktionary.org/wiki/democraty 1913])
[[File:Proposition_tshirt6.svg|200px]]
[[File:tshirt-final1.png|200px]]
* They did cost 13.70 CHF (Total TTC 404.73 Euro for 36 shirts)

{| class="wikitable centre" width="80%"
|-
! scope=col | Quantities !! scope=col | Description !! scope=col | P.U. !! scope=col | Total
|-
| width="10%" | 36 || width="50%" | B&C 150 G || width="20%" | 8.43 € || width="20%" | 303.48 €
|-
| width="10%" | 36 || width="50%" | B&C 190 G || width="20%" | 9.40 € || width="20%" | 338.40 €
|}

== Participant ==
* [[User:Nemen]]
* [[User:Rorist]]

== See also ==
* [[Logo]]

T-shirt FIXME

2015-08-28T22:54:21Z

CrazyGolem: /* 2015 batch */

[[Category:Ongoing_Projects]]

== Information ==
* Order custom T-shirts for FIXME
* Sizes: http://www.doodle.com/vwqkhkhf2yck9vk4
* TODO: A tshirt with the Mateist logo on the back http://hsbp.org/polo&highlight=mateist

== Printing companies ==
* Artist making shirts: http://ybdesign.ch/
* http://creacom.ch/
* http://shirtcity.com/ (t-shirt à l'unité possible)
* http://www.affirmatif90.com/ (the one we used for the 1st batch in 2012)

== 2015 batch ==

=== Your proposition ===
* Design and description here

=== Crazygolem ===
'''Back'''

[[File:Proposition tshirt crazygolem.jpg|150px]]
* This is not the final design!
** It should have 59 labeled "holes" (if I counted correctly)
** Also it will probably have holes around the "FIXME" text too, instead of the frame
** The circuits might be drawn as in real life (e.g. optimized for length or other factors unknown to me)
* The design should be big enough to fill the t-shirt on the back, at least in width

'''Front'''
The FIXME logo and text on the chest

=== Rorist ===
==== Version 1 - The Greedy ====
* The hackerspace rocket, with the moto on the front
* The FIXME text logo on the back
* The head logo on the shoulders
[[File:Proposition_tshirt_rorist.svg|150px]]

==== Version 2 - The Simple ====
* The FIXME text logo on the front, on the heart
* Hackerspace Lausanne text on the back
[[File:Proposition_tshirt_rorist2.svg|150px]]

==== Version 3 - The Mateist ====
* The FIXME text logo on the front, with the Mateist in the center
* Hackerspace Lausanne text on the back
[[File:Proposition_tshirt_rorist3.svg|150px]]

== 2012 batch ==
=== First proposition ===
[[File:Proposition_tshirt.svg|100px]]

* It can be cool to have custom t-shirt for everyone with (IRC) nickname (or other string like HACKER, MAKER, ROOT, STAFF, TEAM, TROLL :) ) on the back, but it can be optionnal.
* All remarks are welcome :)

=== Second proposition ===
We can realise a broderie polo for 21 Fr at http://www.art-image.ch/cgi-bin/marquages_textiles.php. I would propose to only have the fixme logo with fixme under it. They only make batch of 100 pieces.

=== Third proposition ===
* This has been ordered on the on december 2012
[[File:Proposition_tshirt2.svg|100px]]
[[File:Proposition_tshirt3.svg|100px]]
[[File:Proposition_tshirt4.svg|100px]]
[[File:Proposition_tshirt5.svg|100px]]
[[File:Proposition_tshirt6.svg|100px]]

==== Order at Quotation Affirmatif90 ====
http://www.affirmatif90.com/

* They provides 2 types of T-shirts:
** 150 g/m2 [[File:T-SHIRT-150G-B&C.pdf‎]]
** 190 g/m2 [[File:T-SHIRT-190G-B&C.pdf‎]]
* Submitted quantities: 12 M, 14 L, 8 XL and 2 XXL
* First batch (with do-ocraty spelled like in [https://en.wiktionary.org/wiki/democraty 1913])
[[File:Proposition_tshirt6.svg|200px]]
[[File:tshirt-final1.png|200px]]
* They did cost 13.70 CHF (Total TTC 404.73 Euro for 36 shirts)

{| class="wikitable centre" width="80%"
|-
! scope=col | Quantities !! scope=col | Description !! scope=col | P.U. !! scope=col | Total
|-
| width="10%" | 36 || width="50%" | B&C 150 G || width="20%" | 8.43 € || width="20%" | 303.48 €
|-
| width="10%" | 36 || width="50%" | B&C 190 G || width="20%" | 9.40 € || width="20%" | 338.40 €
|}

== Participant ==
* [[User:Nemen]]
* [[User:Rorist]]

== See also ==
* [[Logo]]

File:Proposition tshirt crazygolem.jpg

2015-08-28T22:48:10Z

CrazyGolem:

Git

2015-07-29T22:55:06Z

CrazyGolem: /* Info */

{{warning|Documentation in progress. Send your angry messages to [[User:dgellow]] if you think it can make you feel better.}}

= Migration from gitolite to Gogs =

Authors: [[User:dgellow]], [[User:nemen]]

Date: July 2015

== Reasons ==
< list of irrefutable arguments >

== Info ==

* Trello card: https://trello.com/c/NSQnA7gV
* New base git URL: <code>ssh://gogs@git.fixme.ch:1337/<user>/<repo></code> where <code><user></code> can be a username or an organization

= Git 101 =

< some discussions around basic commands >

= Mirror a repo from foo.fixme.ch to somewhere else (github in this example) =

* Create the target repository (for github, create a new repo)

* Set a new push remote
<pre>
# ssh to foo
ssh YOUR_USER@foo.fixme.ch -p 1337
# Navigate to the repository
cd /home/gogs/gogs-repositories/YOUR_USER/YOU_REPO.git
# Switch to the gogs user
su gogs
# Add a push remote (Don't forget the `--mirror=push` !)
git remote add --mirror=push origin git@github.com:GITHUB_USER/YOUR_REPO.git
# Test it
git push --mirror
</pre>

You will certainly need to register a Deploy Key in your github project. See https://developer.github.com/guides/managing-deploy-keys/#deploy-keys

* Check that a `post-receive` git hook is defined for you repository on git.fixme.ch
You can access it here :
https://git.fixme.ch/YOUR_USER/YOUR_REPO/settings/hooks/git/post-receive
The content should be something like that:
<pre>
git push --mirror
</pre>

* That's it. You can try with a simple commit and push.
<pre>
# In your local clone
touch test_mirror
git add test_mirror
git commit -m "test push to mirror"
git push
</pre>

= Gogs =

< description and a small guide >

== Organizations ==

== Hooks ==

=== Web hooks ===

=== Git hooks ===

Burgers

2015-07-29T22:47:46Z

CrazyGolem: /* Updating the site */ Should be executed as a standard user (hence the `sudo`)

[[Category:Ongoing_Projects]]
[[Category:Services]]
= Description =
* https://burgers.fixme.ch/
* This is part of the [[Internal_Server]], using [[Apache]] and [[MySQL]]
* Order burgers from HolyCow in a nice way
* Replaces the pad https://pad.fixme.ch/burgers
* Repo: <code>git clone ssh://gogs@git.fixme.ch:1337/fixme/burger.git</code>
* New holycow menu: [http://holycow.ch.ismmedia.com/ISM3/std-content/repos/Top/Menu/Holy%20Cow%20Menu.pdf Menu]
* Old holycow menu: [[Media:Holy cow menu web.pdf]]

= Utilisation =
When creating a batch, we set a deadline, which allows to order burgers until it is reached. It is possible to modify the deadline if a batch is not locked.

When the deadline is reached, it is not possible to place orders, and the option to lock a batch becomes available. When a batch is locked, the deadline cannot be modified anymore, and the option to print the batch becomes available, as well as the possibility to mark orders as paid. Printing batches by clicking on the "Print" button allows to get a nicely formatted print, which looks different from on the screen (using CSS @media). ''Currently, only Opera seems to get it properly on Linux, tested with Firefox 12 and Chromium.''

When all orders are marked as ''Paid'' (by clicking on the corresponding red button), the option to close a batch becomes available. When closed, a batch does not appear on the dashboard anymore.

= Summary =
* New Batch -> Place orders, edit deadline
* Deadline met -> Edit deadline, lock batch
* Batch locked -> Print batch, mark orders as paid
* All orders paid -> Close batch

= Website Information =
* Uses the [http://cakephp.org CakePHP Framework] (PHP + MySQL)
* Root Web directory: foo:/home/burgers/www
* Useful scripts and information in foo:/home/burgers

= Updating the site =
# git clone ssh://gitolite@git.fixme.ch:1337/burgers
# Make your modifications
# Push to the repo
# Log into foo and execute these scripts:
sudo /home/burgers/git-update.sh
sudo /home/burgers/set-permissions.sh

= To do =
* Complete the database with prices and drinks
* Refine the batch-print page to improve efficiency
* Fix print output in browsers other than Opera (which does pretty well so far)

== Project Leader ==
* [[user:CrazyGolem|CrazyGolem]]

= Participants =
* [[User:Rorist]], made some bugfixes

Burgers

2015-07-29T22:46:46Z

CrazyGolem: /* Description */ Modified the git url to the new gogs repo

[[Category:Ongoing_Projects]]
[[Category:Services]]
= Description =
* https://burgers.fixme.ch/
* This is part of the [[Internal_Server]], using [[Apache]] and [[MySQL]]
* Order burgers from HolyCow in a nice way
* Replaces the pad https://pad.fixme.ch/burgers
* Repo: <code>git clone ssh://gogs@git.fixme.ch:1337/fixme/burger.git</code>
* New holycow menu: [http://holycow.ch.ismmedia.com/ISM3/std-content/repos/Top/Menu/Holy%20Cow%20Menu.pdf Menu]
* Old holycow menu: [[Media:Holy cow menu web.pdf]]

= Utilisation =
When creating a batch, we set a deadline, which allows to order burgers until it is reached. It is possible to modify the deadline if a batch is not locked.

When the deadline is reached, it is not possible to place orders, and the option to lock a batch becomes available. When a batch is locked, the deadline cannot be modified anymore, and the option to print the batch becomes available, as well as the possibility to mark orders as paid. Printing batches by clicking on the "Print" button allows to get a nicely formatted print, which looks different from on the screen (using CSS @media). ''Currently, only Opera seems to get it properly on Linux, tested with Firefox 12 and Chromium.''

When all orders are marked as ''Paid'' (by clicking on the corresponding red button), the option to close a batch becomes available. When closed, a batch does not appear on the dashboard anymore.

= Summary =
* New Batch -> Place orders, edit deadline
* Deadline met -> Edit deadline, lock batch
* Batch locked -> Print batch, mark orders as paid
* All orders paid -> Close batch

= Website Information =
* Uses the [http://cakephp.org CakePHP Framework] (PHP + MySQL)
* Root Web directory: foo:/home/burgers/www
* Useful scripts and information in foo:/home/burgers

= Updating the site =
# git clone ssh://gitolite@git.fixme.ch:1337/burgers
# Make your modifications
# Push to the repo
# Log into foo and execute these scripts as root:
sudo /home/burgers/git-update.sh
sudo /home/burgers/set-permissions.sh

= To do =
* Complete the database with prices and drinks
* Refine the batch-print page to improve efficiency
* Fix print output in browsers other than Opera (which does pretty well so far)

== Project Leader ==
* [[user:CrazyGolem|CrazyGolem]]

= Participants =
* [[User:Rorist]], made some bugfixes

Stickers

2015-07-01T19:11:14Z

CrazyGolem: /* Aliexpress (bis) */

[[Category:Ongoing_Projects]]
== Description ==
Create stickers with FIXME [[Logo]] to stick them everywhere.

== Goal ==
* Create them in many sizes, to fit different usages
* Create a vinyl version, which we can stick on vehicles

== Obstacle ==
A list of potential obstacles
* Need to find a good and not too expansive printing company
* <s>We need a high-resolution logo, possibly a vector version</s>

== Components ==
* High-res [[Logo]] <s>(currently resolution is too low)</s>
* Printing companies
** http://stickerobot.com
** http://www.stickair.com
** http://www.seridanzil.ch/
** http://aliexpress.com/ aliexpress provides the lowest prices in bulk, and they do provide custom stickers, FIY
** http://www.lenzlinger.com/fr/
** http://www.sergentpapers.com/imprimerie/stickers_classiques_c.html

== Batches ==
=== July 2012 ===
* 1000x 70x20mm CHF87.- at [http://lenzlinger.com/fr/impression/standard/noir/ lenzlinger.com]
[[File:Stickers_70x20.jpg|x250px]]

== Propositions ==

=== Aliexpress ===
* [http://www.aliexpress.com/item/Self-Adhesive-Label-Sticker-Printing/506822112.html Die Cut Custom Vinyl Sticker]
* Type d'impression : Pantone colors on paper/PP/PET/Vinyl/other (lives longer)
* Support : paper/PP/PET/Vinyl/other
* Gloss/matte lamination, vanish, aqueous coating, UV coating, gold / silver stamping
* Délai de fabrication : 6 jours
* Quantité : 1000 ''(2 fois plus pour la moitié du prix)''
* Prix: 75 USD (avec livraison DHL) = ~0.07 chf/sticker

=== Aliexpress (bis) ===
* [http://www.aliexpress.com/item/Professional-customized-stickers-personalized-full-color-label-and-die-cut-decal/32300150087.html Customized full-color die cut decal]
* Type d'impression : CMYK/PANTONE on paper/PE/PVC/PET/PP/Vinyl
* Délai de fabrication : 5 jours
* Quantité : 500
* Prix : 20 USD (avec livraison par poste) = ~0.04 CHF/sticker

=== Stickair ===
* http://www.stickair.com
* Type d'impression : Encre solvant lourd (lives longer)
* Support : Vinyle blanc mat
* Papier transfert & Massicotage
* Délai de fabrication : 8 jours
* Quantité : 500
* Prix: MIN 260 CHF + Livraison = ~0.55 chf/sticker

==== Design 1 ====
* H x W: 10 cm x 8.7 cm
* Coût : 240€ (~ 290 CHF)
[[File:FIXME Logo dark sticker.jpg|x250px|thumb|none]]
(Stickers will be cut on the red line)

==== Design 2 ====
* H x W: 5 cm x 17.8 cm
* Coût : 245€ (~ 295 CHF)
[[File:FIXME Sticker long darkbg.png|500px|thumb|none]]
[[File:FIXME Sticker long lightbg.png|500px|thumb|none]]

==== Design 3 ====
* H x W: 5 cm x 14 cm
* Coût : 220€ (~ 265 CHF)
[[File:FIXME Sticker long darkbg2.png|500px|thumb|none]]
[[File:FIXME Sticker long lightbg2.png|500px|thumb|none]]

== See also ==
[[Permission Stickers]]

== Participant ==
* [[User:CrazyGolem]]

Stickers

2015-07-01T19:07:06Z

CrazyGolem: /* Aliexpress */

[[Category:Ongoing_Projects]]
== Description ==
Create stickers with FIXME [[Logo]] to stick them everywhere.

== Goal ==
* Create them in many sizes, to fit different usages
* Create a vinyl version, which we can stick on vehicles

== Obstacle ==
A list of potential obstacles
* Need to find a good and not too expansive printing company
* <s>We need a high-resolution logo, possibly a vector version</s>

== Components ==
* High-res [[Logo]] <s>(currently resolution is too low)</s>
* Printing companies
** http://stickerobot.com
** http://www.stickair.com
** http://www.seridanzil.ch/
** http://aliexpress.com/ aliexpress provides the lowest prices in bulk, and they do provide custom stickers, FIY
** http://www.lenzlinger.com/fr/
** http://www.sergentpapers.com/imprimerie/stickers_classiques_c.html

== Batches ==
=== July 2012 ===
* 1000x 70x20mm CHF87.- at [http://lenzlinger.com/fr/impression/standard/noir/ lenzlinger.com]
[[File:Stickers_70x20.jpg|x250px]]

== Propositions ==

=== Aliexpress ===
* [http://www.aliexpress.com/item/Self-Adhesive-Label-Sticker-Printing/506822112.html Die Cut Custom Vinyl Sticker]
* Type d'impression : Pantone colors on paper/PP/PET/Vinyl/other (lives longer)
* Support : paper/PP/PET/Vinyl/other
* Gloss/matte lamination, vanish, aqueous coating, UV coating, gold / silver stamping
* Délai de fabrication : 6 jours
* Quantité : 1000 ''(2 fois plus pour la moitié du prix)''
* Prix: 75 USD (avec livraison DHL) = ~0.07 chf/sticker

=== Aliexpress (bis) ===
* [http://www.aliexpress.com/item/Professional-customized-stickers-personalized-full-color-label-and-die-cut-decal/32300150087.html Customized full-color die cut decal]
* Type d'impression : CMYK/PANTONE on paper/PE/PVC/PET/PP/Vinyl
* Délai de fabrication : 5 jours
* Quantité : 500
* Prix : 20 USD (avec livraison) = ~0.04 CHF/sticker

=== Stickair ===
* http://www.stickair.com
* Type d'impression : Encre solvant lourd (lives longer)
* Support : Vinyle blanc mat
* Papier transfert & Massicotage
* Délai de fabrication : 8 jours
* Quantité : 500
* Prix: MIN 260 CHF + Livraison = ~0.55 chf/sticker

==== Design 1 ====
* H x W: 10 cm x 8.7 cm
* Coût : 240€ (~ 290 CHF)
[[File:FIXME Logo dark sticker.jpg|x250px|thumb|none]]
(Stickers will be cut on the red line)

==== Design 2 ====
* H x W: 5 cm x 17.8 cm
* Coût : 245€ (~ 295 CHF)
[[File:FIXME Sticker long darkbg.png|500px|thumb|none]]
[[File:FIXME Sticker long lightbg.png|500px|thumb|none]]

==== Design 3 ====
* H x W: 5 cm x 14 cm
* Coût : 220€ (~ 265 CHF)
[[File:FIXME Sticker long darkbg2.png|500px|thumb|none]]
[[File:FIXME Sticker long lightbg2.png|500px|thumb|none]]

== See also ==
[[Permission Stickers]]

== Participant ==
* [[User:CrazyGolem]]

Logo

2015-06-29T21:26:29Z

CrazyGolem: /* Final version */

[[Category:Ongoing_Projects]]

== Description ==
Créer un logo pour l'association
* [[T-shirt_FIXME]]
* [[Flyer_FIXME]]
* [[Sticker]]
* [[FixMyFlag]]

== Final version ==
* Wallpapers/background
** [[Media:FIXME_Background.png]]
** [[Media:FIXME_Background-800x480.png]]
* Laser-cutter friendly
** [[Media:FIXME logo cutter-friendly.svg]]
** [[File:FIXME arrows cutter-friendly.tgz|Arrow signs to point the way to FIXME]]

=== Vectorial standard versions ===
[[File:FIXME_Logo.svg|x200px|Original]]
[[File:FIXME_Logo_dark.svg|x200px|Dark]]
[[File:FIXME_Logo_light.svg|x200px|Light]]
[[File:FIXME Logo dark horizontal.svg|x100px|Dark Horizontal]]

=== Custom png versions ===
[[File:Logo_fb.png|x150px]]
[[File:Logo_fixme_big.png|x150px]]
[[File:Logo_fixme_big_transparent.png|x150px]]

[[File:Logo_fixme_small_transparent.png|x100px]]
[[File:Logo_fixme_small_transparent_x64.png|x100px]]
[[File:Logo_fixme_small_twitter.png|x100px]]
[[File:Logo_fixme_small_notext.png|x100px]]
[[File:Logo_fixme_small_notext_transparent.png|x100px]]

== Travail sur le logo N°5 ==
[[File:logo5_v3.png|350px]]
[[File:FIXME_Logo_dark_Renens.svg|220px]]

[[File:logo5_v1.png|150px]]
[[File:logo5_v2.png|150px]]

[[File:logo5_v2_facture.png|150px]]
[[File:logo5_v2_bw.jpg|150px]]

License par défaut: [http://creativecommons.org/licenses/by-sa/2.0/ CC-BY-SA] Audrey Piguet (www.audreypiguet.com)

=== Comments ===
* Too much lines on the back of the head
* Looks like a girl now
* Neck not satisfying
* "FIXME" font is Neo Sans, "Hackerspace Lausanne" is Van Condensed

== Goal ==
* Créer une identité pour FIXME
* Le logo doit pouvoir être imprimé sur papier (facture, courrier officiel, ..) et sur t-shirt
* Nous avons besoin de logo pour:
** Le site
** Le wiki
** Twitter
** T-shirt
** Affiche/Flyer
** Courrier officiel
** "Carte de visite"/Mini flyer

== Components ==
Le logo doit correspondre au pre-requis suivant:
* Contenir l'URL de FIXME: fixme.ch
* Contenir "Hackerspace Lausanne" sous cette forme exacte
et éventuellement: "Switzerland" ou juste "CH"
* Etre imprimé sur un fond noir (couleurs inversées)
* Avoir un minimum de couleurs, voir être en noir et blancs.
* Pouvoir être utilisé aussi bien en petite taille (carte de visite) qu'en grand format (bâches)

== Idées ==
* Hacker glyph (Glider du jeu de la vie) ?
[[File:Glider.png]]
* La fusée hackerspaces.org ?
* Un mélange de: coding, electronics, communities, ...
* un vieux fer à souder styliser en blanc dans un disque ou carré en diagonale, bleu, comme les symboles routier "c'est autorisé".

== Propositions ==
=== logo 1 ===
#[[File:Logo-digital-corrige-1.png|250px]][[File:Logo-digital-corrige-1_reverse.png|250px]]

=== logo 2===
#[[File:logo_over_white.png|250px]][[File:logo_over_black.png|250px]][[File:logo_side_white.png|300px]]

=== logo 3===
#[[File:Fixme1.jpg|300px]][[File:Fixme2.jpg|200px]][[File:Fixme3.jpg|200px]]

=== logo 4===
[[File:Fixme4.jpg|250px]]

=== logo 5===
#[[File:Fixme_logo_head1.png|300px]] [[File:Fixme_logo_head2.png|300px]]
License par défaut: [http://creativecommons.org/licenses/by-sa/2.0/ CC-BY-SA] Audrey Piguet (www.audreypiguet.com)

== Old logo ==
* The first logo we used
https://fixme.ch/sites/default/files/logo.png

== Liens ==
* http://www.catb.org/hacker-emblem/
* http://hackerspaces.org

File:FIXME arrows cutter-friendly.tgz

2015-06-29T21:25:14Z

CrazyGolem: Arrows to point the way to FIXME, laser-cutter friendly. The archive contains a dxf file that can be imported into LaserWork as-is, as well as the original svg. Tested with the following settings on poplar wood: * 500 mm/s * 0.3 mm * X_Uni * 50% (dark z

Arrows to point the way to FIXME, laser-cutter friendly.

The archive contains a dxf file that can be imported into LaserWork as-is, as well as the original svg. Tested with the following settings on poplar wood:

* 500 mm/s
* 0.3 mm
* X_Uni
* 50% (dark zones) / 15% (light zones)

File:FIXME logo cutter-friendly.svg

2015-06-29T16:51:01Z

CrazyGolem:

Layered version of the FIXME logo that can easily be exported to the .dxf using inkscape, and which shapes are non-overlapping.

The dark and light parts of the logo are in separate layers. An additional layer contains a contour of the shapes (can be used to cut as-is or as a basis for transformations of the contour, such as a dilatation to have a gap between the logo and the cut). A fourth layer contains a rectangular frame, which can also be used to cut.

Logo

2015-06-29T16:48:05Z

CrazyGolem: Added link to laser-cutter friendly version of the logo

[[Category:Ongoing_Projects]]

== Description ==
Créer un logo pour l'association
* [[T-shirt_FIXME]]
* [[Flyer_FIXME]]
* [[Sticker]]
* [[FixMyFlag]]

== Final version ==
* Wallpapers/background
** [[Media:FIXME_Background.png]]
** [[Media:FIXME_Background-800x480.png]]
* Laser-cutter friendly
** [[Media:FIXME logo cutter-friendly.svg]]

=== Vectorial standard versions ===
[[File:FIXME_Logo.svg|x200px|Original]]
[[File:FIXME_Logo_dark.svg|x200px|Dark]]
[[File:FIXME_Logo_light.svg|x200px|Light]]
[[File:FIXME Logo dark horizontal.svg|x100px|Dark Horizontal]]

=== Custom png versions ===
[[File:Logo_fb.png|x150px]]
[[File:Logo_fixme_big.png|x150px]]
[[File:Logo_fixme_big_transparent.png|x150px]]

[[File:Logo_fixme_small_transparent.png|x100px]]
[[File:Logo_fixme_small_transparent_x64.png|x100px]]
[[File:Logo_fixme_small_twitter.png|x100px]]
[[File:Logo_fixme_small_notext.png|x100px]]
[[File:Logo_fixme_small_notext_transparent.png|x100px]]

== Travail sur le logo N°5 ==
[[File:logo5_v3.png|350px]]
[[File:FIXME_Logo_dark_Renens.svg|220px]]

[[File:logo5_v1.png|150px]]
[[File:logo5_v2.png|150px]]

[[File:logo5_v2_facture.png|150px]]
[[File:logo5_v2_bw.jpg|150px]]

License par défaut: [http://creativecommons.org/licenses/by-sa/2.0/ CC-BY-SA] Audrey Piguet (www.audreypiguet.com)

=== Comments ===
* Too much lines on the back of the head
* Looks like a girl now
* Neck not satisfying
* "FIXME" font is Neo Sans, "Hackerspace Lausanne" is Van Condensed

== Goal ==
* Créer une identité pour FIXME
* Le logo doit pouvoir être imprimé sur papier (facture, courrier officiel, ..) et sur t-shirt
* Nous avons besoin de logo pour:
** Le site
** Le wiki
** Twitter
** T-shirt
** Affiche/Flyer
** Courrier officiel
** "Carte de visite"/Mini flyer

== Components ==
Le logo doit correspondre au pre-requis suivant:
* Contenir l'URL de FIXME: fixme.ch
* Contenir "Hackerspace Lausanne" sous cette forme exacte
et éventuellement: "Switzerland" ou juste "CH"
* Etre imprimé sur un fond noir (couleurs inversées)
* Avoir un minimum de couleurs, voir être en noir et blancs.
* Pouvoir être utilisé aussi bien en petite taille (carte de visite) qu'en grand format (bâches)

== Idées ==
* Hacker glyph (Glider du jeu de la vie) ?
[[File:Glider.png]]
* La fusée hackerspaces.org ?
* Un mélange de: coding, electronics, communities, ...
* un vieux fer à souder styliser en blanc dans un disque ou carré en diagonale, bleu, comme les symboles routier "c'est autorisé".

== Propositions ==
=== logo 1 ===
#[[File:Logo-digital-corrige-1.png|250px]][[File:Logo-digital-corrige-1_reverse.png|250px]]

=== logo 2===
#[[File:logo_over_white.png|250px]][[File:logo_over_black.png|250px]][[File:logo_side_white.png|300px]]

=== logo 3===
#[[File:Fixme1.jpg|300px]][[File:Fixme2.jpg|200px]][[File:Fixme3.jpg|200px]]

=== logo 4===
[[File:Fixme4.jpg|250px]]

=== logo 5===
#[[File:Fixme_logo_head1.png|300px]] [[File:Fixme_logo_head2.png|300px]]
License par défaut: [http://creativecommons.org/licenses/by-sa/2.0/ CC-BY-SA] Audrey Piguet (www.audreypiguet.com)

== Old logo ==
* The first logo we used
https://fixme.ch/sites/default/files/logo.png

== Liens ==
* http://www.catb.org/hacker-emblem/
* http://hackerspaces.org

File:FIXME logo cutter-friendly.svg

2015-06-29T16:45:55Z

CrazyGolem: Layered version of the FIXME logo that can easily be exported to the .dxf using inkscape. The dark and light parts of the logo are in separate layers. An additional layer contains a contour of the shapes (can be used to cut as-is or as a basis for transfo

Layered version of the FIXME logo that can easily be exported to the .dxf using inkscape.
The dark and light parts of the logo are in separate layers. An additional layer contains a contour of the shapes (can be used to cut as-is or as a basis for transformations of the contour, such as a dilatation to have a gap between the logo and the cut). A fourth layer contains a rectangular frame, which can also be used to cut.

Raspberry Pi: Headless installation

2015-05-20T23:10:56Z

CrazyGolem:

While it is not uncommon to have a headless Raspberry Pi (RPi) server, the installation process is usually done by connecting a monitor and a keyboard to the RPi to do the initial installation and configuration, e.g. using NOOBS or by directly transferring the official Raspbian image on the SD card.

If you don't have an additional monitor and keyboard for your RPi, e.g. you only have a laptop at hands, by installing directly Raspbian and after you have hooked up your RPi to the network you can SSH into it to finalize the installation. But this assumes that you know the IP address of your RPi in order to SSH into it. If you don't, e.g. the IP address is assigned by a DHCP server that you do not control, you can still have some ways to get it, but this can be challenging to novice users.

This article proposes a simple solution to allow the user to SSH into its RPi without having to go above and beyond to get its IP address once hooked to the network. It is assumed that you can modify the content of the SD card once the Raspbian image has been transfered to it, so it won't work natively on Windows.

Among others, the following solutions seem interesting to easily SSH into the RPi:

* Configure the RPi to advertise its hostname with Zeroconf. The hostname can be modified from its default to prevent ambiguities.
* Configure the RPi to advertise itself on a DynDNS service.
* Configure the RPi to send an email to a predetermined address once its network interface is up.

However, none of them are actionable out of the box, and they require some packages to be installed on the RPi in order to work.

== Existing solutions ==

[https://github.com/raspberrypi/noobs NOOBS] has some facilities to make unattended installations and [https://pihw.wordpress.com/guides/pi-kitchen/ Pi-Kitchen] can be used to customize it further (e.g. by installing package, configuring and launching services after the first boot).

[https://github.com/debian-pi/raspbian-ua-netinst Raspbian-ua-netinstall] can be used to create self-downloading unattended installations, and seems very flexible.

All those solutions are however too complex for a simple installation, and do not allow to easily understand what is happening under the hood. The aim of this article is to only install a standard Raspbian distribution and configure it such that it can be SSH'd into without hassle to complete the installation.

The <code>raspi-config</code> tool (available out of the box) is usually used to do part of this initial configuration, but it must be used interactively so it is not fit for our purpose. Another similar tool, <code>[https://github.com/shamiao/TRUNCATED-raspi-autoconfig raspi-autoconfig]</code> is a non-interactive pendant of the former, and might be useful for our purpose.

== Prerequisites ==

* An SD card that meets the capacity requirements for Raspbian
* A running computer with an SD card reader (for this guide, it is assumed that it runs a linux distribution)

And as the target for the installed OS, although not absolutely required to follow this guide:
* A powered RPi
* Network access with a DHCP-provided IP address

== Installation ==

''All the following steps are done from your running computer, not from your RPi.''

Download the latest [https://www.raspberrypi.org/downloads/ Raspbian] image and follow the [https://www.raspberrypi.org/documentation/installation/installing-images/linux.md official installation procedure].

TL;DR: <code>dd bs=4M if=/path/to/raspbian-image of=/dev/sdX; sync</code>

That's it! Also, an SSH server should be up and running on your RPi once powered-up with the default Raspbian installation.

Although optional, it could be nice to already prevent anyone except you to access the RPi through SSH. In order to do this, even before putting the SD card into the RPi, you can already configure sshd to authorize only access using SSH keys.

Assuming you already have an SSH key pair on your running computer, you just have to authorize your key (<code>$SD</code> is the root directory of your SD card):

<pre>
mkdir $SD/home/pi/.ssh
cat ~/.ssh/id_rsa.pub >> $SD/home/pi/.ssh/authorized_keys
</pre>

(note that the default raspbian user is <code>pi</code>)

Then configure sshd to prevent password login by editing <code>$SD/etc/ssh/sshd_config</code> with the following options:

<pre>
ChallengeResponseAuthentication no
PasswordAuthentication no
UsePAM no
</pre>

Now, something must be done to address the IP address discovery problem.

== Bootstrapping packages ==

Installing additional packages beyond the basic Raspbian installation is not straightforward when you want to do it on your running computer: you cannot just <code>chroot</code> into the SD card and execute <code>apt-get</code> to pull additional packages, because your running computer probably runs on an x86/x86-64 architecture and your RPi uses ARM (and <code>chroot</code> works only when the architectures [http://unix.stackexchange.com/a/41890 are the same]).

To solve this problem, we will let Raspbian bootstrap the additional packages directly from the RPi once the network is available. It should also be possible to download the packages' and their dependencies' archives and install them manually from your running computer or let <code>apt</code> install them from the file system instead of downloading them, but this won't be covered here.

By placing a script in <code>$SD/etc/networks/if-up.d/</code>, it will be executed every time a network interface becomes available, and this will be used to wait for Internet access before downloading additional packages. The following script contains boilerplate code to ensure that Internet access is actually available (e.g. this is not the case with the loopback interface) and prevent the script from being executed several times (e.g. if there are several interfaces with Internet connectivity, such as Ethernet and WiFi) and finally ensure that the script is executed only once, typically the first time the RPi is booted.

<pre>
#!/bin/sh

# Ensures that the script is run only when "useful" network interfaces become
# available, e.g. the loopback interface provides no Internet connectivity.
case "$IFACE" in
lo)
exit 0
;;
*)
;;
esac

# Ensures that the script is run only once, e.g. when several network
# interfaces are available
FLAGFILE=/var/run/raspi-bootstrap.flag
if [ -e $FLAGFILE ]; then
exit 0
else
touch $FLAGFILE
fi

###############################################################################
### Your code goes here, everything before and after is boilerplate ###########
###############################################################################

# The file containing this script is removed from the file system, so it won't
# be executed again
rm "$0"
</pre>

=== Using Zeroconf ===

Assuming that you have a Zeroconf client (e.g. Avahi, Bonjour) on the machine you will use to SSH into your RPi, it would be nice to be able to use it to automatically resolve the IP address of your RPi. If both your computer and the RPi are on the same LAN (Zeroconf does not work across LANs), it would allow to use the hostname of your RPi instead of its IP address.

The problem is that there is no Zeroconf client in the default Raspbian installation, so it will have to be bootstrapped using the script above. Simply replace the "your code goes here" line by the following:

<pre>
apt-get -q update
apt-get -qy install avahi-daemon
insserv avahi-daemon
</pre>

You should be able to replace <code>insserv avahi-daemon</code> by <code>update-rc.d avahi-daemon defaults</code>, which is actually the recommended way to manage boot scripts.

You can optionally change the hostname of your RPi in order to prevent ambiguities, as it defaults to <code>raspberrypi</code> on all fresh Raspbian installations. To achieve this, change the hostname in <code>$SD/etc/hostname</code> and in <code>$SD/etc/hosts</code> at the <code>127.0.1.1</code> line (which is exactly what <code>raspi-config</code> does when you ask it to change the hostname).

Once done, you can finally place the SD card into your RPi, connect it to your LAN and power it up. After a few minutes (it can take some time, go get a coffee) you should be able to ssh into your RPi using <code>ssh pi@<hostname></code> (or <code>pi@<hostname>.local</code> depending on the configuration of your machine, if none works check the installation and configuration procedure of the Avahi client for your distribution).

Finally you can execute <code>sudo raspi-config</code> in your SSH shell to configure your RPi as usual.

=== Using DynDNS ===

When you are not on the same LAN as your RPi, you can use a DynDNS service to resolve the IP address of your RPi.

Basically, you have to install a DynDNS client on your RPi using the same technique as above and configure it according to the requirement of the DynDNS service you use.

As an example, using OVH's DynDNS service you can install <code>ddclient</code> on your RPi by replacing the "your code here" line of the script above with:

<pre>
apt-get -q update
apt-get -qy install ddclient
</pre>

and configuring the client by editing <code>$SD/etc/ddclient.conf</code> with:

<pre>
protocol=dyndns2
use=if, if=eth0
server=www.ovh.com
login=raspberrypi
password='p455w0rd'

# Updates interval (in seconds)
daemon=300

# Logging & temp files
syslog=yes
pid=/var/run/ddclient.pid
cache=/tmp/ddclient.cache

# Domain name
raspberrypi.fixme.ch
</pre>

''Note: if you have not guessed it already, you have to adapt the values for <code>login</code>, <code>password</code> and the domain name to match your case, and the values above are fictional.''

=== Sending a mail ===

The poor man's version of IP address discovery: make the RPi send an email that containing its IP address to a predefined email address. Yours.

Raspbian does not have an SMTP server installed by default, so again you can use the script above to install <code>sendmail</code>. You might have to configure the SMTP server before <code>sendmail</code> can be used in your script (which you can do by directly editing configuration files on the SD card before placing it in the RPi; I won't explain how to do it here because I'm too lazy).

For this solution to be a bit more comfortable, you might want to adapt the script such that it sends the email at regular intervals, and disable it manually once you have SSH'ed into your RPi.

Raspberry Pi: Headless installation

2015-05-20T22:50:28Z

CrazyGolem:

While it is not uncommon to have a headless Raspberry Pi (RPi) server, the installation process is usually done by connecting a monitor and a keyboard to the RPi to do the initial installation and configuration, e.g. using NOOBS or by directly transferring the official Raspbian image on the SD card.

If you don't have an additional monitor and keyboard for your RPi, e.g. you only have a laptop at hands, by installing directly Raspbian and after you have hooked up your RPi to the network you can SSH into it to finalize the installation. But this assumes that you know the IP address of your RPi in order to SSH into it. If you don't, e.g. the IP address is assigned by a DHCP server that you do not control, you can still have some ways to get it, but this can be challenging to novice users.

This article proposes a simple solution to allow the user to SSH into its RPi without having to go above and beyond to get its IP address once hooked to the network. It is assumed that you can modify the content of the SD card once the Raspbian image has been transfered to it, so it won't work natively on Windows.

Among others, the following solutions seem interesting to easily SSH into the RPi:

* Configure the RPi to advertise its hostname with Zeroconf. The hostname can be modified from its default to prevent ambiguities.
* Configure the RPi to advertise itself on a DynDNS service.
* Configure the RPi to send an email to a predetermined address once its network interface is up.

However, none of them are actionable out of the box, and they require some packages to be installed on the RPi in order to work.

== Existing solutions ==

[https://github.com/raspberrypi/noobs NOOBS] has some facilities to make unattended installations and [https://pihw.wordpress.com/guides/pi-kitchen/ Pi-Kitchen] can be used to customize it further (e.g. by installing package, configuring and launching services after the first boot).

[https://github.com/debian-pi/raspbian-ua-netinst Raspbian-ua-netinstall] can be used to create self-downloading unattended installations, and seems very flexible.

All those solutions are however too complex for a simple installation, and do not allow to easily understand what is happening under the hood. The aim of this article is to only install a standard Raspbian distribution and configure it such that it can be SSH'd into without hassle to complete the installation.

The <code>raspi-config</code> tool (available out of the box) is usually used to do part of this initial configuration, but it must be used interactively so it is not fit for our purpose. Another similar tool, <code>[https://github.com/shamiao/TRUNCATED-raspi-autoconfig raspi-autoconfig]</code> is a non-interactive pendant of the former, and might be useful for our purpose.

== Prerequisites ==

* An SD card that meets the capacity requirements for Raspbian
* A running computer with an SD card reader (for this guide, it is assumed that it runs a linux distribution)

And as the target for the installed OS, although not absolutely required to follow this guide:
* A powered RPi
* Network access with a DHCP-provided IP address

== Installation ==

''All the following steps are done from your running computer, not from your RPi.''

Download the latest [https://www.raspberrypi.org/downloads/ Raspbian] image and follow the [https://www.raspberrypi.org/documentation/installation/installing-images/linux.md official installation procedure].

TL;DR: <code>dd bs=4M if=/path/to/raspbian-image of=/dev/sdX; sync</code>

That's it! Also, an SSH server should be up and running on your RPi once powered-up with the default Raspbian installation.

Although optional, it could be nice to already prevent anyone except you to access the RPi through SSH. In order to do this, even before putting the SD card into the RPi, you can already configure sshd to authorize only access using SSH keys.

Assuming you already have an SSH key pair on your running computer, you just have to authorize your key (<code>$SD</code> is the root directory of your SD card):

<pre>
mkdir $SD/home/pi/.ssh
cat ~/.ssh/id_rsa.pub >> $SD/home/pi/.ssh/authorized_keys
</pre>

(note that the default raspbian user is <code>pi</code>)

Then configure sshd to prevent password login by editing <code>$SD/etc/ssh/sshd_config</code> with the following options:

<pre>
ChallengeResponseAuthentication no
PasswordAuthentication no
UsePAM no
</pre>

Now, something must be done to address the IP address discovery problem.

== Bootstrapping packages ==

Installing additional packages beyond the basic Raspbian installation is not straightforward when you want to do it on your running computer: you cannot just <code>chroot</code> into the SD card and execute <code>apt-get</code> to pull additional packages, because your running computer probably runs on an x86/x86-64 architecture and your RPi uses ARM (and <code>chroot</code> works only when the architectures [http://unix.stackexchange.com/a/41890 are the same]).

To solve this problem, we will let Raspbian bootstrap the additional packages directly from the RPi once the network is available. It should also be possible to download the packages' and their dependencies' archives and install them manually from your running computer or let <code>apt</code> install them from the file system instead of downloading them, but this won't be covered here.

By placing a script in <code>$SD/etc/networks/if-up.d/</code>, it will be executed every time a network interface becomes available, and this will be used to wait for Internet access before downloading additional packages. The following script contains boilerplate code to ensure that Internet access is actually available (e.g. this is not the case with the loopback interface) and prevent the script from being executed several times (e.g. if there are several interfaces with Internet connectivity, such as Ethernet and WiFi) and finally ensure that the script is executed only once, typically the first time the RPi is booted.

<pre>
#!/bin/sh

# Ensures that the script is run only when "useful" network interfaces become
# available, e.g. the loopback interface provides no Internet connectivity.
case "$IFACE" in
lo)
exit 0
;;
*)
;;
esac

# Ensures that the script is run only once, e.g. when several network
# interfaces are available
FLAGFILE=/var/run/raspi-bootstrap.flag
if [ -e $FLAGFILE ]; then
exit 0
else
touch $FLAGFILE
fi

###############################################################################
### Your code goes here, everything before and after is boilerplate ###########
###############################################################################

# The file containing this script is removed from the file system, so it won't
# be executed again
rm "$0"
</pre>

=== Using Zeroconf ===

Assuming that you have a Zeroconf client (e.g. Avahi, Bonjour) on the machine you will use to SSH into your RPi, it would be nice to be able to use it to automatically resolve the IP address of your RPi. If both your computer and the RPi are on the same LAN (Zeroconf does not work across LANs), it would allow to use the hostname of your RPi instead of its IP address.

The problem is that there is no Zeroconf client in the default Raspbian installation, so it will have to be bootstrapped using the script above. Simply replace the "your code goes here" line by the following:

<pre>
apt-get -q update
apt-get -qy install avahi-daemon
insserv avahi-daemon
</pre>

You should be able to replace <code>insserv avahi-daemon</code> by <code>update-rc.d avahi-daemon defaults</code>, which is actually the recommended way to manage boot scripts.

You can optionally change the hostname of your RPi in order to prevent ambiguities, as it defaults to <code>raspberrypi</code> on all fresh Raspbian installations. To achieve this, change the hostname in <code>$SD/etc/hostname</code> and in <code>$SD/etc/hosts</code> at the <code>127.0.1.1</code> line (which is exactly what <code>raspi-config</code> does when you ask it to change the hostname).

Once done, you can finally place the SD card into your RPi, connect it to your LAN and power it up. After a few minutes (it can take some time, go get a coffee) you should be able to ssh into your RPi using <code>ssh pi@<hostname></code> (or <code>pi@<hostname>.local</code> depending on the configuration of your machine, if none works check the installation and configuration procedure of the Avahi client for your distribution).

Finally you can execute <code>sudo raspi-config</code> in your SSH shell to configure your RPi as usual.

=== Using DynDNS ===

When you are not on the same LAN as your RPi, you can use a DynDNS service to resolve the IP address of your RPi.

Basically, you have to install a DynDNS client on your RPi using the same technique as above and configure it according to the requirement of the DynDNS service you use.

As an example, using OVH's DynDNS service you can install <code>ddclient</code> on your RPi by replacing the "your code here" line of the script above with:

<pre>
apt-get -q update
apt-get -qy install ddclient
</pre>

and configuring the client by editing <code>$SD/etc/ddclient.conf</code> with:

<pre>
protocol=dyndns2
use=if, if=eth0
server=www.ovh.com
login=raspberrypi
password='p455w0rd'

# Updates interval (in seconds)
daemon=300

# Logging & temp files
syslog=yes
pid=/var/run/ddclient.pid
cache=/tmp/ddclient.cache

# Domain name
raspberrypi.fixme.ch
</pre>

''Note: if you have not guessed it already, you have to adapt the values for ''login'', ''password'' and the domain name to match your case, and the values above are fictional.''

=== Sending a mail ===

The poor man's version of IP address discovery: make the RPi send an email that containing its IP address to a predefined email address. Yours.

Raspbian does not have an SMTP server installed by default, so again you can use the script above to install <code>sendmail</code>. You might have to configure the SMTP server before <code>sendmail</code> can be used in your script (which you can do by directly editing configuration files on the SD card before placing it in the RPi; I won't explain how to do it here because I'm too lazy).

For this solution to be a bit more comfortable, you might want to adapt the script such that it sends the email at regular intervals, and disable it manually once you have SSH'ed into your RPi.

Raspberry Pi: Headless installation

2015-05-20T22:47:14Z

CrazyGolem: /* Installation */

While it is not uncommon to have a headless Raspberry Pi (RPi) server, the installation process is usually done by connecting a monitor and a keyboard to the RPi to do the initial installation and configuration, e.g. using NOOBS or by directly transferring the official Raspbian image on the SD card.

If you don't have an additional monitor and keyboard for your RPi, e.g. you only have a laptop at hands, by installing directly Raspbian and after you have hooked up your RPi to the network you can SSH into it to finalize the installation. But this assumes that you know the IP address of your RPi in order to SSH into it. If you don't, e.g. the IP address is assigned by a DHCP server that you do not control, you can still have some ways to get it, but this can be challenging to novice users.

This article proposes a simple solution to allow the user to SSH into its RPi without having to go above and beyond to get its IP address once hooked to the network. It is assumed that you can modify the content of the SD card once the Raspbian image has been transfered to it, so it won't work natively on Windows.

Among others, the following solutions seem interesting to easily SSH into the RPi:

* Configure the RPi to advertise its hostname with Zeroconf. The hostname can be modified from its default to prevent ambiguities.
* Configure the RPi to advertise itself on a DynDNS service.
* Configure the RPi to send an email to a predetermined address once its network interface is up.

However, none of them are actionable out of the box, and they require some packages to be installed on the RPi in order to work.

== Existing solutions ==

[https://github.com/raspberrypi/noobs NOOBS] has some facilities to make unattended installations and [https://pihw.wordpress.com/guides/pi-kitchen/ Pi-Kitchen] can be used to customize it further (e.g. by installing package, configuring and launching services after the first boot).

[https://github.com/debian-pi/raspbian-ua-netinst Raspbian-ua-netinstall] can be used to create self-downloading unattended installations, and seems very flexible.

All those solutions are however too complex for a simple installation, and do not allow to easily understand what is happening under the hood. The aim of this article is to only install a standard Raspbian distribution and configure it such that it can be SSH'd into without hassle to complete the installation.

The <code>raspi-config</code> tool (available out of the box) is usually used to do part of this initial configuration, but it must be used interactively so it is not fit for our purpose. Another similar tool, <code>[https://github.com/shamiao/TRUNCATED-raspi-autoconfig raspi-autoconfig]</code> is a non-interactive pendant of the former, and might be useful for our purpose.

== Prerequisites ==

* An SD card that meets the capacity requirements for Raspbian
* A running computer with an SD card reader (for this guide, it is assumed that it runs a linux distribution)

And as the target for the installed OS, although not absolutely required to follow this guide:
* A powered RPi
* Network access with a DHCP-provided IP address

== Installation ==

''All the following steps are done from your running computer, not from your RPi.''

Download the latest [https://www.raspberrypi.org/downloads/ Raspbian] image and follow the [https://www.raspberrypi.org/documentation/installation/installing-images/linux.md official installation procedure].

TL;DR: <code>dd bs=4M if=/path/to/raspbian-image of=/dev/sdX; sync</code>

That's it! Also, an SSH server should be up and running on your RPi once powered-up with the default Raspbian installation.

Although optional, it could be nice to already prevent anyone except you to access the RPi through SSH. In order to do this, even before putting the SD card into the RPi, you can already configure sshd to authorize only access using SSH keys.

Assuming you already have an SSH key pair on your running computer, you just have to authorize your key (<code>$SD</code> is the root directory of your SD card):

<pre>
mkdir $SD/home/pi/.ssh
cat ~/.ssh/id_rsa.pub >> $SD/home/pi/.ssh/authorized_keys
</pre>

(note that the default raspbian user is <code>pi</code>)

Then configure sshd to prevent password login by editing <code>$SD/etc/ssh/sshd_config</code> with the following options:

<pre>
ChallengeResponseAuthentication no
PasswordAuthentication no
UsePAM no
</pre>

Now, something must be done to address the IP address discovery problem.

== Bootstrapping packages ==

Installing additional packages beyond the basic Raspbian installation is not straightforward when you want to do it on your running computer: you cannot just <code>chroot</code> into the SD card and execute <code>apt-get</code> to pull additional packages, because your running computer probably runs on an x86/x86-64 architecture and your RPi uses ARM (and <code>chroot</code> works only when the architectures [http://unix.stackexchange.com/a/41890 are the same]).

To solve this problem, we will let Raspbian bootstrap the additional packages directly from the RPi once the network is available. It should also be possible to download the packages' and their dependencies' archives and install them manually from your running computer or let <code>apt</code> install them from the file system instead of downloading them, but this won't be covered here.

By placing a script in <code>$SD/etc/networks/if-up.d/</code>, it will be executed every time a network interface becomes available, and this will be used to wait for Internet access before downloading additional packages. The following script contains boilerplate code to ensure that Internet access is actually available (e.g. this is not the case with the loopback interface) and prevent the script from being executed several times (e.g. if there are several interfaces with Internet connectivity, such as Ethernet and WiFi) and finally ensure that the script is executed only once, typically the first time the RPi is booted.

<pre>
#!/bin/sh

# Ensures that the script is run only when "useful" network interfaces become
# available, e.g. the loopback interface provides no Internet connectivity.
case "$IFACE" in
lo)
exit 0
;;
*)
;;
esac

# Ensures that the script is run only once, e.g. when several network
# interfaces are available
FLAGFILE=/var/run/raspi-bootstrap.flag
if [ -e $FLAGFILE ]; then
exit 0
else
touch $FLAGFILE
fi

###############################################################################
### Your code goes here, everything before and after is boilerplate ###########
###############################################################################

# The file containing this script is removed from the file system, so it won't
# be executed again
rm "$0"
</pre>

=== Using Zeroconf ===

Assuming that you have a Zeroconf client (e.g. Avahi, Bonjour) on the machine you will use to SSH into your RPi, it would be nice to be able to use it to automatically resolve the IP address of your RPi. If both your computer and the RPi are on the same LAN (Zeroconf does not work across LANs), it would allow to use the hostname of your RPi instead of its IP address.

The problem is that there is no Zeroconf client in the default Raspbian installation, so it will have to be bootstrapped using the script above. Simply replace the "your code goes here" section by the following:

<pre>
apt-get -q update
apt-get -qy install avahi-daemon
insserv avahi-daemon
</pre>

You should be able to replace <code>insserv avahi-daemon</code> by <code>update-rc.d avahi-daemon defaults</code>, which is actually the recommended way to manage boot scripts.

You can optionally change the hostname of your RPi in order to prevent ambiguities, as it defaults to <code>raspberrypi</code> on all fresh Raspbian installations. To achieve this, change the hostname in <code>$SD/etc/hostname</code> and in <code>$SD/etc/hosts</code> at the <code>127.0.1.1</code> line (which is exactly what <code>raspi-config</code> does when you ask it to change the hostname).

Once done, you can finally place the SD card into your RPi, connect it to your LAN and power it up. After a few minutes (it can take some time, go get a coffee) you should be able to ssh into your RPi using <code>ssh pi@<hostname></code> (or <code>pi@<hostname>.local</code> depending on the configuration of your machine, if none works check the installation and configuration procedure of the Avahi client for your distribution).

Finally you can execute <code>sudo raspi-config</code> in your SSH shell to configure your RPi as usual.

=== Using DynDNS ===

When you are not on the same LAN as your RPi, you can use a DynDNS service to resolve the IP address of your RPi.

Basically, you have to install a DynDNS client on your RPi using the same technique as above and configure it according to the requirement of the DynDNS service you use.

As an example, using OVH's DynDNS service you can install <code>ddclient</code> on your RPi by replacing the "your code here" section of the script above with:

<pre>
apt-get -q update
apt-get -qy install ddclient
</pre>

and configuring the client by editing <code>$SD/etc/ddclient.conf</code> with:

<pre>
protocol=dyndns2
use=if, if=eth0
server=www.ovh.com
login=raspberrypi
password='p455w0rd'

# Updates interval (in seconds)
daemon=300

# Logging & temp files
syslog=yes
pid=/var/run/ddclient.pid
cache=/tmp/ddclient.cache

# Domain name
raspberrypi.fixme.ch
</pre>

''Note: if you have not guessed it already, you have to adapt the values for ''login'', ''password'' and the domain name to match your case, and the values above are fictional.''

=== Sending a mail ===

The poor man's version of IP address discovery: make the RPi send an email that containing its IP address to a predefined email address. Yours.

Raspbian does not have an SMTP server installed by default, so again you can use the script above to install <code>sendmail</code>. You might have to configure the SMTP server before <code>sendmail</code> can be used in your script (which you can do by directly editing configuration files on the SD card before placing it in the RPi; I won't explain how to do it here because I'm too lazy).

For this solution to be a bit more comfortable, you might want to adapt the script such that it sends the email at regular intervals, and disable it manually once you have SSH'ed into your RPi.

Raspberry Pi: Headless installation

2015-05-20T22:45:44Z

CrazyGolem: /* Existing solutions */

While it is not uncommon to have a headless Raspberry Pi (RPi) server, the installation process is usually done by connecting a monitor and a keyboard to the RPi to do the initial installation and configuration, e.g. using NOOBS or by directly transferring the official Raspbian image on the SD card.

If you don't have an additional monitor and keyboard for your RPi, e.g. you only have a laptop at hands, by installing directly Raspbian and after you have hooked up your RPi to the network you can SSH into it to finalize the installation. But this assumes that you know the IP address of your RPi in order to SSH into it. If you don't, e.g. the IP address is assigned by a DHCP server that you do not control, you can still have some ways to get it, but this can be challenging to novice users.

This article proposes a simple solution to allow the user to SSH into its RPi without having to go above and beyond to get its IP address once hooked to the network. It is assumed that you can modify the content of the SD card once the Raspbian image has been transfered to it, so it won't work natively on Windows.

Among others, the following solutions seem interesting to easily SSH into the RPi:

* Configure the RPi to advertise its hostname with Zeroconf. The hostname can be modified from its default to prevent ambiguities.
* Configure the RPi to advertise itself on a DynDNS service.
* Configure the RPi to send an email to a predetermined address once its network interface is up.

However, none of them are actionable out of the box, and they require some packages to be installed on the RPi in order to work.

== Existing solutions ==

[https://github.com/raspberrypi/noobs NOOBS] has some facilities to make unattended installations and [https://pihw.wordpress.com/guides/pi-kitchen/ Pi-Kitchen] can be used to customize it further (e.g. by installing package, configuring and launching services after the first boot).

[https://github.com/debian-pi/raspbian-ua-netinst Raspbian-ua-netinstall] can be used to create self-downloading unattended installations, and seems very flexible.

All those solutions are however too complex for a simple installation, and do not allow to easily understand what is happening under the hood. The aim of this article is to only install a standard Raspbian distribution and configure it such that it can be SSH'd into without hassle to complete the installation.

The <code>raspi-config</code> tool (available out of the box) is usually used to do part of this initial configuration, but it must be used interactively so it is not fit for our purpose. Another similar tool, <code>[https://github.com/shamiao/TRUNCATED-raspi-autoconfig raspi-autoconfig]</code> is a non-interactive pendant of the former, and might be useful for our purpose.

== Prerequisites ==

* An SD card that meets the capacity requirements for Raspbian
* A running computer with an SD card reader (for this guide, it is assumed that it runs a linux distribution)

And as the target for the installed OS, although not absolutely required to follow this guide:
* A powered RPi
* Network access with a DHCP-provided IP address

== Installation ==

''All the following steps are done from your running computer, not from your RPi.''

Download the latest [https://www.raspberrypi.org/downloads/ Raspbian] image and follow the [https://www.raspberrypi.org/documentation/installation/installing-images/linux.md official installation procedure].

TL;DR: <code>dd bs=4M if=/path/to/raspbian-image of=/dev/sdX; sync</code>

That's it! Also, an SSH server should be up and running on your RPi once powered-up with the default Raspbian installation.

Although optional, it could be nice to already prevent anyone except you to access the RPi through SSH. In order to do this, even before putting the SD card into the RPi, you can already configure sshd to authorize only access using SSH keys.

Assuming you already have an SSH key pair on your running computer, you just have to authorize your key (paths are relative to the SD card root <code>$SD</code>, NOT your file system root <code>/</code>):

<pre>
mkdir $SD/home/pi/.ssh
cat ~/.ssh/id_rsa.pub >> $SD/home/pi/.ssh/authorized_keys
</pre>

(note that the default raspbian user is <code>pi</code>)

Then configure sshd to prevent password login by editing <code>$SD/etc/ssh/sshd_config</code> with the following options:

<pre>
ChallengeResponseAuthentication no
PasswordAuthentication no
UsePAM no
</pre>

Now, something must be done to address the IP address discovery problem.

== Bootstrapping packages ==

Installing additional packages beyond the basic Raspbian installation is not straightforward when you want to do it on your running computer: you cannot just <code>chroot</code> into the SD card and execute <code>apt-get</code> to pull additional packages, because your running computer probably runs on an x86/x86-64 architecture and your RPi uses ARM (and <code>chroot</code> works only when the architectures [http://unix.stackexchange.com/a/41890 are the same]).

To solve this problem, we will let Raspbian bootstrap the additional packages directly from the RPi once the network is available. It should also be possible to download the packages' and their dependencies' archives and install them manually from your running computer or let <code>apt</code> install them from the file system instead of downloading them, but this won't be covered here.

By placing a script in <code>$SD/etc/networks/if-up.d/</code>, it will be executed every time a network interface becomes available, and this will be used to wait for Internet access before downloading additional packages. The following script contains boilerplate code to ensure that Internet access is actually available (e.g. this is not the case with the loopback interface) and prevent the script from being executed several times (e.g. if there are several interfaces with Internet connectivity, such as Ethernet and WiFi) and finally ensure that the script is executed only once, typically the first time the RPi is booted.

<pre>
#!/bin/sh

# Ensures that the script is run only when "useful" network interfaces become
# available, e.g. the loopback interface provides no Internet connectivity.
case "$IFACE" in
lo)
exit 0
;;
*)
;;
esac

# Ensures that the script is run only once, e.g. when several network
# interfaces are available
FLAGFILE=/var/run/raspi-bootstrap.flag
if [ -e $FLAGFILE ]; then
exit 0
else
touch $FLAGFILE
fi

###############################################################################
### Your code goes here, everything before and after is boilerplate ###########
###############################################################################

# The file containing this script is removed from the file system, so it won't
# be executed again
rm "$0"
</pre>

=== Using Zeroconf ===

Assuming that you have a Zeroconf client (e.g. Avahi, Bonjour) on the machine you will use to SSH into your RPi, it would be nice to be able to use it to automatically resolve the IP address of your RPi. If both your computer and the RPi are on the same LAN (Zeroconf does not work across LANs), it would allow to use the hostname of your RPi instead of its IP address.

The problem is that there is no Zeroconf client in the default Raspbian installation, so it will have to be bootstrapped using the script above. Simply replace the "your code goes here" section by the following:

<pre>
apt-get -q update
apt-get -qy install avahi-daemon
insserv avahi-daemon
</pre>

You should be able to replace <code>insserv avahi-daemon</code> by <code>update-rc.d avahi-daemon defaults</code>, which is actually the recommended way to manage boot scripts.

You can optionally change the hostname of your RPi in order to prevent ambiguities, as it defaults to <code>raspberrypi</code> on all fresh Raspbian installations. To achieve this, change the hostname in <code>$SD/etc/hostname</code> and in <code>$SD/etc/hosts</code> at the <code>127.0.1.1</code> line (which is exactly what <code>raspi-config</code> does when you ask it to change the hostname).

Once done, you can finally place the SD card into your RPi, connect it to your LAN and power it up. After a few minutes (it can take some time, go get a coffee) you should be able to ssh into your RPi using <code>ssh pi@<hostname></code> (or <code>pi@<hostname>.local</code> depending on the configuration of your machine, if none works check the installation and configuration procedure of the Avahi client for your distribution).

Finally you can execute <code>sudo raspi-config</code> in your SSH shell to configure your RPi as usual.

=== Using DynDNS ===

When you are not on the same LAN as your RPi, you can use a DynDNS service to resolve the IP address of your RPi.

Basically, you have to install a DynDNS client on your RPi using the same technique as above and configure it according to the requirement of the DynDNS service you use.

As an example, using OVH's DynDNS service you can install <code>ddclient</code> on your RPi by replacing the "your code here" section of the script above with:

<pre>
apt-get -q update
apt-get -qy install ddclient
</pre>

and configuring the client by editing <code>$SD/etc/ddclient.conf</code> with:

<pre>
protocol=dyndns2
use=if, if=eth0
server=www.ovh.com
login=raspberrypi
password='p455w0rd'

# Updates interval (in seconds)
daemon=300

# Logging & temp files
syslog=yes
pid=/var/run/ddclient.pid
cache=/tmp/ddclient.cache

# Domain name
raspberrypi.fixme.ch
</pre>

''Note: if you have not guessed it already, you have to adapt the values for ''login'', ''password'' and the domain name to match your case, and the values above are fictional.''

=== Sending a mail ===

The poor man's version of IP address discovery: make the RPi send an email that containing its IP address to a predefined email address. Yours.

Raspbian does not have an SMTP server installed by default, so again you can use the script above to install <code>sendmail</code>. You might have to configure the SMTP server before <code>sendmail</code> can be used in your script (which you can do by directly editing configuration files on the SD card before placing it in the RPi; I won't explain how to do it here because I'm too lazy).

For this solution to be a bit more comfortable, you might want to adapt the script such that it sends the email at regular intervals, and disable it manually once you have SSH'ed into your RPi.

Raspberry Pi: Headless installation

2015-05-20T22:43:30Z

CrazyGolem:

While it is not uncommon to have a headless Raspberry Pi (RPi) server, the installation process is usually done by connecting a monitor and a keyboard to the RPi to do the initial installation and configuration, e.g. using NOOBS or by directly transferring the official Raspbian image on the SD card.

If you don't have an additional monitor and keyboard for your RPi, e.g. you only have a laptop at hands, by installing directly Raspbian and after you have hooked up your RPi to the network you can SSH into it to finalize the installation. But this assumes that you know the IP address of your RPi in order to SSH into it. If you don't, e.g. the IP address is assigned by a DHCP server that you do not control, you can still have some ways to get it, but this can be challenging to novice users.

This article proposes a simple solution to allow the user to SSH into its RPi without having to go above and beyond to get its IP address once hooked to the network. It is assumed that you can modify the content of the SD card once the Raspbian image has been transfered to it, so it won't work natively on Windows.

Among others, the following solutions seem interesting to easily SSH into the RPi:

* Configure the RPi to advertise its hostname with Zeroconf. The hostname can be modified from its default to prevent ambiguities.
* Configure the RPi to advertise itself on a DynDNS service.
* Configure the RPi to send an email to a predetermined address once its network interface is up.

However, none of them are actionable out of the box, and they require some packages to be installed on the RPi in order to work.

== Existing solutions ==

[https://github.com/raspberrypi/noobs NOOBS] has some facilities to make unattended installations and [https://pihw.wordpress.com/guides/pi-kitchen/ Pi-Kitchen] can be used to customize it further (e.g. by installing package, configuring and launching services after the first boot).

[https://github.com/debian-pi/raspbian-ua-netinst Raspbian-ua-netinstall] can be used to create self-downloading unattended installations, and seems very flexible.

All those solutions are however too complex for a simple installation, and do not allow to easily understand what is happening under the hood. The aim of this article is to only install a standard Raspbian distribution and configure it such that it can be SSH'd into without hassle to complete the installation.

The <code>raspi-config</code> tool (available out of the box) is usually used to do part of this initial configuration, but it must be used interactively so it is not fit for our purpose. Another similar tool, <code>raspi-autoconfig</code> is a non-interactive pendant of the former, and might be useful for our purpose.

== Prerequisites ==

* An SD card that meets the capacity requirements for Raspbian
* A running computer with an SD card reader (for this guide, it is assumed that it runs a linux distribution)

And as the target for the installed OS, although not absolutely required to follow this guide:
* A powered RPi
* Network access with a DHCP-provided IP address

== Installation ==

''All the following steps are done from your running computer, not from your RPi.''

Download the latest [https://www.raspberrypi.org/downloads/ Raspbian] image and follow the [https://www.raspberrypi.org/documentation/installation/installing-images/linux.md official installation procedure].

TL;DR: <code>dd bs=4M if=/path/to/raspbian-image of=/dev/sdX; sync</code>

That's it! Also, an SSH server should be up and running on your RPi once powered-up with the default Raspbian installation.

Although optional, it could be nice to already prevent anyone except you to access the RPi through SSH. In order to do this, even before putting the SD card into the RPi, you can already configure sshd to authorize only access using SSH keys.

Assuming you already have an SSH key pair on your running computer, you just have to authorize your key (paths are relative to the SD card root <code>$SD</code>, NOT your file system root <code>/</code>):

<pre>
mkdir $SD/home/pi/.ssh
cat ~/.ssh/id_rsa.pub >> $SD/home/pi/.ssh/authorized_keys
</pre>

(note that the default raspbian user is <code>pi</code>)

Then configure sshd to prevent password login by editing <code>$SD/etc/ssh/sshd_config</code> with the following options:

<pre>
ChallengeResponseAuthentication no
PasswordAuthentication no
UsePAM no
</pre>

Now, something must be done to address the IP address discovery problem.

== Bootstrapping packages ==

Installing additional packages beyond the basic Raspbian installation is not straightforward when you want to do it on your running computer: you cannot just <code>chroot</code> into the SD card and execute <code>apt-get</code> to pull additional packages, because your running computer probably runs on an x86/x86-64 architecture and your RPi uses ARM (and <code>chroot</code> works only when the architectures [http://unix.stackexchange.com/a/41890 are the same]).

To solve this problem, we will let Raspbian bootstrap the additional packages directly from the RPi once the network is available. It should also be possible to download the packages' and their dependencies' archives and install them manually from your running computer or let <code>apt</code> install them from the file system instead of downloading them, but this won't be covered here.

By placing a script in <code>$SD/etc/networks/if-up.d/</code>, it will be executed every time a network interface becomes available, and this will be used to wait for Internet access before downloading additional packages. The following script contains boilerplate code to ensure that Internet access is actually available (e.g. this is not the case with the loopback interface) and prevent the script from being executed several times (e.g. if there are several interfaces with Internet connectivity, such as Ethernet and WiFi) and finally ensure that the script is executed only once, typically the first time the RPi is booted.

<pre>
#!/bin/sh

# Ensures that the script is run only when "useful" network interfaces become
# available, e.g. the loopback interface provides no Internet connectivity.
case "$IFACE" in
lo)
exit 0
;;
*)
;;
esac

# Ensures that the script is run only once, e.g. when several network
# interfaces are available
FLAGFILE=/var/run/raspi-bootstrap.flag
if [ -e $FLAGFILE ]; then
exit 0
else
touch $FLAGFILE
fi

###############################################################################
### Your code goes here, everything before and after is boilerplate ###########
###############################################################################

# The file containing this script is removed from the file system, so it won't
# be executed again
rm "$0"
</pre>

=== Using Zeroconf ===

Assuming that you have a Zeroconf client (e.g. Avahi, Bonjour) on the machine you will use to SSH into your RPi, it would be nice to be able to use it to automatically resolve the IP address of your RPi. If both your computer and the RPi are on the same LAN (Zeroconf does not work across LANs), it would allow to use the hostname of your RPi instead of its IP address.

The problem is that there is no Zeroconf client in the default Raspbian installation, so it will have to be bootstrapped using the script above. Simply replace the "your code goes here" section by the following:

<pre>
apt-get -q update
apt-get -qy install avahi-daemon
insserv avahi-daemon
</pre>

You should be able to replace <code>insserv avahi-daemon</code> by <code>update-rc.d avahi-daemon defaults</code>, which is actually the recommended way to manage boot scripts.

You can optionally change the hostname of your RPi in order to prevent ambiguities, as it defaults to <code>raspberrypi</code> on all fresh Raspbian installations. To achieve this, change the hostname in <code>$SD/etc/hostname</code> and in <code>$SD/etc/hosts</code> at the <code>127.0.1.1</code> line (which is exactly what <code>raspi-config</code> does when you ask it to change the hostname).

Once done, you can finally place the SD card into your RPi, connect it to your LAN and power it up. After a few minutes (it can take some time, go get a coffee) you should be able to ssh into your RPi using <code>ssh pi@<hostname></code> (or <code>pi@<hostname>.local</code> depending on the configuration of your machine, if none works check the installation and configuration procedure of the Avahi client for your distribution).

Finally you can execute <code>sudo raspi-config</code> in your SSH shell to configure your RPi as usual.

=== Using DynDNS ===

When you are not on the same LAN as your RPi, you can use a DynDNS service to resolve the IP address of your RPi.

Basically, you have to install a DynDNS client on your RPi using the same technique as above and configure it according to the requirement of the DynDNS service you use.

As an example, using OVH's DynDNS service you can install <code>ddclient</code> on your RPi by replacing the "your code here" section of the script above with:

<pre>
apt-get -q update
apt-get -qy install ddclient
</pre>

and configuring the client by editing <code>$SD/etc/ddclient.conf</code> with:

<pre>
protocol=dyndns2
use=if, if=eth0
server=www.ovh.com
login=raspberrypi
password='p455w0rd'

# Updates interval (in seconds)
daemon=300

# Logging & temp files
syslog=yes
pid=/var/run/ddclient.pid
cache=/tmp/ddclient.cache

# Domain name
raspberrypi.fixme.ch
</pre>

''Note: if you have not guessed it already, you have to adapt the values for ''login'', ''password'' and the domain name to match your case, and the values above are fictional.''

=== Sending a mail ===

The poor man's version of IP address discovery: make the RPi send an email that containing its IP address to a predefined email address. Yours.

Raspbian does not have an SMTP server installed by default, so again you can use the script above to install <code>sendmail</code>. You might have to configure the SMTP server before <code>sendmail</code> can be used in your script (which you can do by directly editing configuration files on the SD card before placing it in the RPi; I won't explain how to do it here because I'm too lazy).

For this solution to be a bit more comfortable, you might want to adapt the script such that it sends the email at regular intervals, and disable it manually once you have SSH'ed into your RPi.

Raspberry Pi

2015-05-20T22:40:30Z

CrazyGolem:

Page showing some useful RPi information. Don't hesitate to contribute! Keep in mind that this is aimed at people who aren't necessarily competent with linux or electronics in general.
== Setup ==
# Download [http://downloads.raspberrypi.org/NOOBS_lite_latest NOOBS], a simple to use installer that requires no command line knowledge
# Find an empty SD or microSD card (minimum 2gb/class 6, 4gb/class 10 recommended - try to find cards with UHS-1), make sure it's FAT32, and then extract all the files from the NOOBS zip onto it
# Plug in the SD card, an HDMI or composite display, a ethernet cable, usb keyboard + mouse, and a ''good'' 5v power supply (seriously - a lot of issues come from low power/fake power supplies) [[File:RasperrySetup.jpg|500px]]
# Power on the Pi, and wait a few seconds until you reach the screen below. Select Raspbian, click install, and wait a few minutes - the Pi should take 20-60 minutes to install depending on your internet connection and SD card. [[File:NOOBS.png|500px]]
# After installation is complete, the 'Raspberry Pi Software Configuration Tool' pop up. You can skip this step ''but'' it's recommended that you change the following: [[File:Raspi-config.png|500px]]
## '''Change User Password''' to something that you can remember - default one is raspbian
## '''Enable boot to Desktop''' select whether you want to boot to console (ideal for servers and remote access), or desktop (for projects that display something, or if you want to set up the pi directly on itself)
## '''Internationalisation Options'''
### '''Change locale''' to en_US.UTF-8 for everything, other options will break things later
### '''Change keyboard layout''' to German Switzerland -> Swiss French, this part is a must if you're used to fr_ch keyboards
## '''Advanced Options''' -> '''Hostname''' to something easy to find, such as 'raspberrypi-yourname'
# Click on finish, reboot your Pi, and you're good to go!

<pre>

Hackers guide, only do this if you know what you're doing - you could wipe the wrong device!

wget http://downloads.raspberrypi.org/raspbian_latest && unzip raspbian_latest
umount /dev/sdd1
dd bs=4M if=2015-02-16-raspbian-wheezy.img of=/dev/sdd
##progress won't be evident, run 'pkill -USR1 -n -x dd' in another window to see it
sync
##remove SD card and copy steps 3 and 5 above

## Configuration tool with menus / Outil de configuration par menu :
raspi-config

## Ddefault user / Utilisateur par défaut : pi

</pre>

=== WiFi ===
If you have a WiFi stick that is directly compatible with Raspbian, follow the instructions bellow. If it's not, then you'll need to troubleshoot with Google.

[http://www.debuntu.org/how-to-wifi-roaming-with-wpa-supplicant/ WPA supplicant setup] with different settings for different networks

=== Headless setup ===

If you don't want to connect a keyboard and monitor to your RPi, you can perform a [[Raspberry Pi: Headless installation|headless installation of Raspbian]] instead of using NOOBS.

== Screen blanking ==
add the following lines to /etc/xdg/lxsession/LXDE/autostart, remove the line with the screensaver option

@xset s off
@xset -dpms
@xset s noblank

== Software ==
=== Web server (Apache) ===
sudo apt-get install apache2

Then you can edit files in /var/www/
=== Un wiki ===
==== Intro ====
Utiliser un Raspberry Pi pour remplacer un serveur AMD 64 bit est ce réaliste pour héberger un wiki?

Lors de la sortie du modèle B+ en novembre je me suis lancé dans l'aventure d'installer un wikimedia sur le Raspberry Pi en ma possession .

==== mediawiki ====

Afin de minimiser l'utilisation des ressources et compte-tenu de mon besoin j'ai opté pour une installation avec sqllite3 .

Et si le wiki est visible il est d'une lenteur affligeante :-( voyez par vous même belorne .

La faute me semble-t-il à PHP et à la programation de mediadwiki qui est bien trop lourde pour une si petite machine.

Il faut oublier une telle idée, si ce n'est pour jouer .

==== Une autre solution ====

Oui biensur il y en a bcp mais pour une tel machine , la solution la plus ligth mais aussi la plus simple c'est MDwiki.

Un wiki en langage de description de page Markdown.

Je ne vais pas décrire les étapes de cette installation , juste vous donner des liens permettant de comprendre comment cela est faisable.

Les composants :

* Un rapsberry Pi B+
* Os Raspbian 3.12.35+
* Mdwiki [[http://dynalon.github.io/mdwiki/#!index.md Site]]
* 2 comptes Google Drive
* [[https://www.insynchq.com/ insync]] version RaspberryPi

Voici le [[http://boizot.ch/ résultats]]

Comment cela marche ?

Trés trés simplement. de mon portable je peux éditer n'importe quel fichier du site , en changer les liens....
Le tout est quasi immédiatement mise à jour sur le dossier de mon Raspberry Pi qui est synchroniser en temps .

==== Conclusion ====
Biensur on est bien loin de Mediawiki ou de MoinsMoins.

Then you can edit files on your laptop.

== Hardware ==
=== GPIO ===
git clone git://git.drogon.net/wiringPi
cd wiringPi/
./build

Then set a pin to output
gpio [-g] mode <pin> in/out/pwm/up/down/tri
gpio -g mode 13 out #for example

Use the pin
gpio -g write 13 1

[https://projects.drogon.net/raspberry-pi/wiringpi/the-gpio-utility/ Documentation]

[https://github.com/sarfata/pi-blaster PWM library]

Raspberry Pi: Headless installation

2015-05-20T22:36:45Z

CrazyGolem: Created page with "While it is not uncommon to have a headless Raspberry Pi (RPi) server, the installation process is usually done by connecting a monitor and a keyboard to the RPi to do the initia..."

While it is not uncommon to have a headless Raspberry Pi (RPi) server, the installation process is usually done by connecting a monitor and a keyboard to the RPi to do the initial installation and configuration, e.g. using NOOBS or by directly transferring the official Raspbian image on the SD card.

If you don't have an additional monitor and keyboard for your RPi, e.g. you only have a laptop at hands, by installing directly Raspbian and after you have hooked up your RPi to the network you can SSH into it to finalize the installation. But this assumes that you know the IP address of your RPi in order to SSH into it. If you don't, e.g. the IP address is assigned by a DHCP server that you do not control, you can still have some ways to get it, but this can be challenging to novice users.

This article proposes a simple solution to allow the user to SSH into its RPi without having to go above and beyond to get its IP address once hooked to the network. It is assumed that you can modify the content of the SD card once the Raspbian image has been transfered to it, so it won't work natively on Windows.

Among others, the following solutions seem interesting to easily SSH into the RPi:

* Configure the RPi to advertise its hostname with Zeroconf (e.g. using avahi-daemon). The hostname can be modified from its default to prevent ambiguities.
* Configure the RPi to advertise itself on a DynDNS service.
* Configure the RPi to send an email to a predetermined address once its network interface is up.

However, none of them are actionable out of the box, and they require some packages to be installed on the RPi in order to work.

== Existing solutions ==

[https://github.com/raspberrypi/noobs NOOBS] has some facilities to make unattended installations and [https://pihw.wordpress.com/guides/pi-kitchen/ Pi-Kitchen] can be used to customize it further (e.g. by installing package, configuring and launching services after the first boot).

[https://github.com/debian-pi/raspbian-ua-netinst Raspbian-ua-netinstall] can be used to create self-downloading unattended installations, and seems very flexible.

All those solutions are however too complex for a simple installation, and do not allow to easily understand what is happening under the hood. The aim of this article is to only install a standard Raspbian distribution and configure it such that it can be SSH'd into without hassle to complete the installation.

The <code>raspi-config</code> tool (available out of the box) is usually used to do part of this initial configuration, but it must be used interactively so it is not fit for our purpose. Another similar tool, <code>raspi-autoconfig</code> is a non-interactive pendant of the former, and might be useful for our purpose.

== Prerequisites ==

* An SD card that meets the capacity requirements for Raspbian
* A running computer with an SD card reader (for this guide, it is assumed that it runs a linux distribution)

And as the target for the installed OS, although not absolutely required to follow this guide:
* A powered RPi
* Network access with a DHCP-provided IP address

== Installation ==

''All the following steps are done from your running computer, not from your RPi.''

Download the latest [https://www.raspberrypi.org/downloads/ Raspbian] image and follow the [https://www.raspberrypi.org/documentation/installation/installing-images/linux.md official installation procedure].

TL;DR: <code>dd bs=4M if=/path/to/raspbian-image of=/dev/sdX; sync</code>

That's it! Also, an SSH server should be up and running on your RPi once powered-up with the default Raspbian installation.

Although optional, it could be nice to already prevent anyone except you to access the RPi through SSH. In order to do this, even before putting the SD card into the RPi, you can already configure sshd to authorize only access using SSH keys.

Assuming you already have an SSH key pair on your running computer, you just have to authorize your key (paths are relative to the SD card root <code>$SD</code>, NOT your file system root <code>/</code>):

<pre>
mkdir $SD/home/pi/.ssh
cat ~/.ssh/id_rsa.pub >> $SD/home/pi/.ssh/authorized_keys
</pre>

(note that the default raspbian user is <code>pi</code>)

Then configure sshd to prevent password login by editing <code>$SD/etc/ssh/sshd_config</code> with the following options:

<pre>
ChallengeResponseAuthentication no
PasswordAuthentication no
UsePAM no
</pre>

Now, something must be done to address the IP address discovery problem.

== Bootstrapping packages ==

Installing additional packages beyond the basic Raspbian installation is not straightforward when you want to do it on your running computer: you cannot just <code>chroot</code> into the SD card and execute <code>apt-get</code> to pull additional packages, because your running computer probably runs on an x86/x86-64 architecture and your RPi uses ARM (and <code>chroot</code> works only when the architectures [http://unix.stackexchange.com/a/41890 are the same]).

To solve this problem, we will let Raspbian bootstrap the additional packages directly from the RPi once the network is available. It should also be possible to download the packages' and their dependencies' archives and install them manually from your running computer or let <code>apt</code> install them from the file system instead of downloading them, but this won't be covered here.

By placing a script in <code>$SD/etc/networks/if-up.d/</code>, it will be executed every time a network interface becomes available, and this will be used to wait for Internet access before downloading additional packages. The following script contains boilerplate code to ensure that Internet access is actually available (e.g. this is not the case with the loopback interface) and prevent the script from being executed several times (e.g. if there are several interfaces with Internet connectivity, such as Ethernet and WiFi) and finally ensure that the script is executed only once, typically the first time the RPi is booted.

<pre>
#!/bin/sh

# Ensures that the script is run only when "useful" network interfaces become
# available, e.g. the loopback interface provides no Internet connectivity.
case "$IFACE" in
lo)
exit 0
;;
*)
;;
esac

# Ensures that the script is run only once, e.g. when several network
# interfaces are available
FLAGFILE=/var/run/raspi-bootstrap.flag
if [ -e $FLAGFILE ]; then
exit 0
else
touch $FLAGFILE
fi

###############################################################################
### Your code goes here, everything before and after is boilerplate ###########
###############################################################################

# The file containing this script is removed from the file system, so it won't
# be executed again
rm "$0"
</pre>

=== Using Zeroconf ===

Assuming that you have a Zeroconf client (e.g. Avahi, Bonjour) on the machine you will use to SSH into your RPi, it would be nice to be able to use it to automatically resolve the IP address of your RPi. If both your computer and the RPi are on the same LAN (Zeroconf does not work across LANs), it would allow to use the hostname of your RPi instead of its IP address.

The problem is that there is no Zeroconf client in the default Raspbian installation, so it will have to be bootstrapped using the script above. Simply replace the "your code goes here" section by the following:

<pre>
apt-get -q update
apt-get -qy install avahi-daemon
insserv avahi-daemon
</pre>

You should be able to replace <code>insserv avahi-daemon</code> by <code>update-rc.d avahi-daemon defaults</code>, which is actually the recommended way to manage boot scripts.

You can optionally change the hostname of your RPi in order to prevent ambiguities, as it defaults to <code>raspberrypi</code> on all fresh Raspbian installations. To achieve this, change the hostname in <code>$SD/etc/hostname</code> and in <code>$SD/etc/hosts</code> at the <code>127.0.1.1</code> line (which is exactly what <code>raspi-config</code> does when you ask it to change the hostname).

Once done, you can finally place the SD card into your RPi, connect it to your LAN and power it up. After a few minutes (it can take some time, go get a coffee) you should be able to ssh into your RPi using <code>ssh pi@<hostname></code> (or <code>pi@<hostname>.local</code> depending on the configuration of your machine, if none works check the installation and configuration procedure of the Avahi client for your distribution).

Finally you can execute <code>sudo raspi-config</code> in your SSH shell to configure your RPi as usual.

=== Using DynDNS ===

When you are not on the same LAN as your RPi, you can use a DynDNS service to resolve the IP address of your RPi.

Basically, you have to install a DynDNS client on your RPi using the same technique as above and configure it according to the requirement of the DynDNS service you use.

As an example, using OVH's DynDNS service you can install <code>ddclient</code> on your RPi by replacing the "your code here" section of the script above with:

<pre>
apt-get -q update
apt-get -qy install ddclient
</pre>

and configuring the client by editing <code>$SD/etc/ddclient.conf</code> with:

<pre>
protocol=dyndns2
use=if, if=eth0
server=www.ovh.com
login=raspberrypi
password='p455w0rd'

# Updates interval (in seconds)
daemon=300

# Logging & temp files
syslog=yes
pid=/var/run/ddclient.pid
cache=/tmp/ddclient.cache

# Domain name
raspberrypi.fixme.ch
</pre>

''Note: if you have not guessed it already, you have to adapt the values for ''login'', ''password'' and the domain name to match your case, and the values above are fictional.''

=== Sending a mail ===

The poor man's version of IP address discovery: make the RPi send an email that containing its IP address to a predefined email address. Yours.

Raspbian does not have an SMTP server installed by default, so again you can use the script above to install <code>sendmail</code>. You might have to configure the SMTP server before <code>sendmail</code> can be used in your script (which you can do by directly editing configuration files on the SD card before placing it in the RPi; I won't explain how to do it here because I'm too lazy).

For this solution to be a bit more comfortable, you might want to adapt the script such that it sends the email at regular intervals, and disable it manually once you have SSH'ed into your RPi.

Sheets

2014-03-27T19:29:08Z

CrazyGolem: /* Fridge / FFH */

Various facts and explications sheets hanging around the Hackerspace or available for printing.

= Fridge / FFH =
* [[File:Fill fridge wishlist.pdf]] Boromir telling to fill the fridge and wishlist
* [[File:Fill the fridge.xcf.gz]] poster for the fridge
* [[File:Prices.odt]] Prices list for the fridge
* [[File:Holycow.odt]], holycow stuff

= Network =
* [[File:Network.odt]]

= Administrative =
* [[File:Invitation_apero.odt]]

File:Fill the fridge.xcf.gz

2014-03-27T19:28:01Z

CrazyGolem: Affiche pour le frigo

Affiche pour le frigo

InsomniHack-2014

2014-03-26T23:19:48Z

CrazyGolem: /* Result */

[[Category:CTF]]
[[Category:Conferences]]
== Information ==
* http://insomnihack.ch/
* '''Lieu:''' Palexpo Genève
* '''Dates:''' 20-21 mars 2014
** '''CTF:''' Vendredi 21 mars de 18h à 4h
** '''Conferences:''' Vendredi 21 mars toute la journée
** '''Workshops:''' Jeudi 20 mars
* '''Nom de la team:''' FIXME, EMXIF
* 8 players per team

== Fixme Team ==
* Team FIXME: TBD

== Result ==

=== Team FIXME ===
* Ranking: 7th
* 2195 points
* Score evolution: TBA
[[Image:ins14-result.jpg|200px]]

=== Team EMXIF ===
[[Image:Ins14 EMXIF.jpg|thumb=Ins14 EMXIF thumb.jpg|alt=EMXIF Scoreboard|EMXIF Scoreboard]]
* Ranking: ???
* 1070 points
* 11 challenges solved
** 9 easy, 2 medium
** 1 reverse, 5 web, 2 misc, 2 network, 1 stegano

== Writeups ==
* Protocrypt: http://blafh.blogspot.ch/2014/03/ctf-writeup-insomnihack-2014-protocrypt.html
* Encoding: http://blafh.blogspot.ch/2014/03/ctf-writeup-insomnihack-2014-encoding.html
* Leeeetcrypto: http://blafh.blogspot.ch/2014/03/ctf-writeup-insomnihack-2014.html
* Gigpang echo: http://cybermashup.com/2014/03/24/insomnihack-writeup-gigpang-echo/

== Photos ==
* TODO

== See Also ==
* [[InsomniHack-2012]]
* [[InsomniHack-2013]]

File:Ins14 EMXIF thumb.jpg

2014-03-26T23:18:28Z

CrazyGolem: uploaded a new version of "File:Ins14 EMXIF thumb.jpg": Smaller version. The complete scoreboard is located at File:Ins14 EMXIF.jpg

File:Ins14 EMXIF thumb.jpg

2014-03-26T23:02:51Z

CrazyGolem:

File:Ins14 EMXIF.jpg

2014-03-26T22:50:35Z

CrazyGolem: Insomni'hack 2014 - Scores team EMXIF

Insomni'hack 2014 - Scores team EMXIF

File:Prices.odt

2014-02-19T17:52:44Z

CrazyGolem: uploaded a new version of "File:Prices.odt": Instant-noodly noodles noodled

Price list for the fridge

AG 2013 December

2013-11-05T18:18:38Z

CrazyGolem: /* To discuss */

[[Category:Meetings]]
[[Category:AG]]
== Information ==
* Date: FIXME
* PV: FIXME

== To discuss ==
* Finance
* Membership
** Different rules for the intermediate membership
** Different ways to get a key -> Moar keys!!!
* New local
* !!!Events!!!
* Comitee, re-election
** President: Crazygolem / You here
** Secretary: [[User:Nemen]] / You here
** Cashier (most important position): You here
** Logistic: [[User:Rorist]]

==References/notes==
<references/>

Printer

2013-10-16T17:08:27Z

CrazyGolem: /* Configuration */

* A printer with a cups server is available on cups://printer.fixme.ch. It's an old black and white brother laser printer.

== Configuration ==
Using CUPS:
* Protocol: AppSocket/HP JetDirect
* Url: socket://printer.fixme.ch (or socket://hl-2150.fixme.ch)
* Driver
** Generic > Generic PCL Laser Printer
** Brother > Brother HL 2150N http://www.brother.com/pub/bsc/linux/dlf/brhl2150nlpr-2.0.2-1.i386.deb
** Brother > Brother HL 2170W (provided by foomatic) seems OK

Logo

2013-06-21T17:05:40Z

CrazyGolem: /* Version vectorielle */

[[Category:Ongoing_Projects]]

= Description =
Créer un logo pour l'association
* [[T-shirt_FIXME]]
* [[Flyer_FIXME]]
* [[Sticker]]
* Wallpapers/background
** [[Media:FIXME_Background.png]]
** [[Media:FIXME_Background-800x480.png]]

= Travail sur le logo N°5 =
[[File:logo5_v3.png|350px]]
[[File:logo5_v1.png|150px]]
[[File:logo5_v2.png|150px]]
[[File:logo5_v2_facture.png|150px]]
[[File:logo5_v2_bw.jpg|150px]]
[http://creativecommons.org/licenses/by-sa/2.0/ CC-BY-SA] Audrey Piguet (www.audreypiguet.com)

== Versions vectorielles ==
[[File:FIXME_Logo.svg|x200px|Original]]
[[File:FIXME_Logo_dark.svg|x200px|Dark]]
[[File:FIXME_Logo_light.svg|x200px|Light]]

[[File:FIXME Logo dark horizontal.svg|x100px|Dark Horizontal]]

License par défaut: [http://creativecommons.org/licenses/by-sa/2.0/ CC-BY-SA] Audrey Piguet (www.audreypiguet.com)

= T-Shirt =
* http://www.art-image.ch/ (in Lausanne)
* http://www.mcshirt.ch/ (in Geneva)
* http://www.seridanzil.ch/

== Comments ==
* Too much lines on the back of the head
* Looks like a girl now
* Neck not satisfying

= Goal =
* Créer une identité pour FIXME
* Le logo doit pouvoir être imprimé sur papier (facture, courrier officiel, ..) et sur t-shirt
* Nous avons besoin de logo pour:
** Le site
** Le wiki
** Twitter
** T-shirt
** Affiche/Flyer
** Courrier officiel
** "Carte de visite"/Mini flyer

= Components =
Le logo doit correspondre au pre-requis suivant:
* Contenir l'URL de FIXME: fixme.ch
* Contenir "Hackerspace Lausanne" sous cette forme exacte
et éventuellement: "Switzerland" ou juste "CH"
* Etre imprimé sur un fond noir (couleurs inversées)
* Avoir un minimum de couleurs, voir être en noir et blancs.
* Pouvoir être utilisé aussi bien en petite taille (carte de visite) qu'en grand format (bâches)

= Idées =
* Hacker glyph (Glider du jeu de la vie) ?
[[File:Glider.png]]
* La fusée hackerspaces.org ?
* Un mélange de: coding, electronics, communities, ...
* un vieux fer à souder styliser en blanc dans un disque ou carré en diagonale, bleu, comme les symboles routier "c'est autorisé".

= Propositions =
= logo 1 =
#[[File:Logo-digital-corrige-1.png|250px]][[File:Logo-digital-corrige-1_reverse.png|250px]]
= logo 2=
#[[File:logo_over_white.png|250px]][[File:logo_over_black.png|250px]][[File:logo_side_white.png|300px]]
= logo 3=
#[[File:Fixme1.jpg|300px]][[File:Fixme2.jpg|200px]][[File:Fixme3.jpg|200px]]
= logo 4=
[[File:Fixme4.jpg|250px]]
= logo 5=
#[[File:Fixme_logo_head1.png|300px]] [[File:Fixme_logo_head2.png|300px]]
License par défaut: [http://creativecommons.org/licenses/by-sa/2.0/ CC-BY-SA] Audrey Piguet (www.audreypiguet.com)

= Old logo =
* The first logo we used
https://fixme.ch/sites/default/files/logo.png

= Liens =
* http://www.catb.org/hacker-emblem/
* http://hackerspaces.org

File:FIXME Logo dark horizontal.svg

2013-06-21T17:03:30Z

CrazyGolem: uploaded a new version of "File:FIXME Logo dark horizontal.svg": Removed border

Horizontal version of the dark logo.

The top of the text is aligned under the large bar of the head.

File:FIXME Logo dark horizontal.svg

2013-06-21T17:02:24Z

CrazyGolem: Horizontal version of the dark logo. The top of the text is aligned under the large bar of the head.

Horizontal version of the dark logo.

The top of the text is aligned under the large bar of the head.

File:Prices.odt

2013-06-18T18:15:28Z

CrazyGolem: uploaded a new version of "File:Prices.odt"

Price list for the fridge

File:Prices.odt

2013-03-27T18:11:02Z

CrazyGolem: uploaded a new version of "File:Prices.odt"

Price list for the fridge

Meeting-20130305

2013-03-05T20:07:29Z

CrazyGolem: /* PV */

[[Category:Meetings]]
== Information ==
* http://doodle.com/gtzhkzxtuainywhc#table
* 05.03.2013 @19h

== Summary ==
=== Admin ===
* Cotisations pour 2013
* ETA : Dossier sponsoring
* Point sur adresse/compte postal
* Point sur le fonctionnement du comité (comptes, rappel, nouveaux membres, ...)

=== Other ===
* Pub, etc
* Communication events (personne à la coding night, ...)
* Envoyer un mail pour dire que le matériel labelisé avec un nom peut etre utilisé, en demandant à son proprio
* ETA : [[AlternativesUrbaines2013]]
* Evenements pour avril-mai-juin
* MySpace ?
* Collaboration avec l'association ADER pour leur atelier gros oeuvre (métal, bois) (mail de Philou sur la ML)
** On avait deja eu une mise à dispo de l'atelier de Nico, en 1 année personne n'a manifesté un besoin
** Cette association a un certain caractère politique non ?

== PV ==

* Cotisations: 25 Lettres et emails de relance à envoyer.
* Finances:
** Voir pour mettre une alerte sur le compte quand le solde passe sous la barre des 2500,-.
** 47,- de dons depuis le 1er janvier.
* Adresse virtuelle, opérationnelle et redirigée au domicile du président: FIXME Hackerspace 1004 Lausanne
* A déterminer si le compte postal doit être au siège de l'association, donc au domicile du président (cf. Statuts).
* Le dossier de sponsoring n'a pas avancé.
* Point sur le fonctionnement du comité:
** Comptes: ca roule.
** Rappels: à la bourre.
** Nouveaux membres: 5 nouveaux membres depuis le 1er janvier.

* Pas de pub pour le moment.
* Petit concours avec un flyer reporté.
* Communication pour les events:
** Com récurrente sur les semaines/jours précédents l'event
** Faire un doodle pour l'event pour essayer de fixer une date qui plait/convient et avoir une estimation des personnes potentiellement présentes.
* Matériel:
** Voir pour mettre en place les stickers pour réguler l'utilisation du matériel.
** Fred peut envoyer un mail pour expliquer comment utiliser son matériel (sur lequel il y a son nom)
* Alternatives Urbaines:
** rorist va mettre un coup de collier
** Ultimaker a réparer pour l'événement
** Voir avec Fred pour la matrice de LED
** Prévoir des flyers et apporter des stickers
** Nemen va essayer d'apporter son robot.
* Events pour avril/mai/juin:
** Workshop samedi après-midi avec des jeunes.
** Workshop PCB Etching: Marc propose de venir un samedi après-midi avec son matériel.
* Myspace: il faut faire le nécessaire, la personne doit trouver le bon email.
* Collaboration avec l'association ADER:
** Demander à Philou les contacts.
** Inviter/Rendre visite aux gens de l'ADER pour un premier contact.

AlternativesUrbaines2013

2013-03-05T19:40:24Z

CrazyGolem: /* Stand */

[[Category:Ongoing_Projects]]
[[Category:Conferences]]
== Information ==
* 3-4 may 2013
* Site: http://alternativesurbaines.ch/

== Stand ==
* Stand on saturday 4th may from 9h

== Participants ==
* [[User:rorist]] project leader
* [[User:gcmalloc]] throwies

Meeting-20130305

2013-03-04T18:33:57Z

CrazyGolem:

[[Category:Meetings]]
== Information ==
* http://doodle.com/gtzhkzxtuainywhc#table
* 05.03.2013 @19h

== Summary ==
* Cotisations pour 2013
* Envoyer un mail pour dire que le matériel labelisé avec un nom peut etre utilisé, en demandant à son proprio
* ETA : [[AlternativesUrbaines2013]]
* ETA : Dossier sponsoring
* Evenements pour avril-mai-juin
* Point sur adresse/compte postal
* Point sur le fonctionnement du comité (comptes, rappel, nouveaux membres, ...)
* Pub, etc
* Communication events (personne à la coding night, ...)
* MySpace ?
* Collaboration avec l'association ADER pour leur atelier gros oeuvre (métal, bois) (mail de Philou sur la ML)

Meeting-20130305

2013-02-22T08:39:16Z

CrazyGolem: /* Summary */

[[Category:Meetings]]
== Information ==
* http://doodle.com/gtzhkzxtuainywhc#table
* Mardi 5 mars at 19h

== Summary ==
* ETA : Alternatives urbaines
* ETA : Dossier sponsoring

File:Prices.odt

2013-01-09T19:21:10Z

CrazyGolem: uploaded a new version of "File:Prices.odt"

Price list for the fridge

Main Page

2012-12-03T18:10:41Z

CrazyGolem:

__NOTOC__
{{Boite
| titre=Welcome to FIXME
| bordure=black
| fond=lightgray
| couleurTitre=black
| couleurTexteTitre=white
| largeur=75%
| flotte=left
}}
This is the working wiki of the FIXME Hackerspace, main website is at https://fixme.ch
{{BoiteFin}}

{{Boite
| couleurTexteTitre=white
| largeur=20%
| flotte=right
}}
https://fixme.ch/sites/default/files/hackerspace_status.png
[http://foo.fixme.ch/trigger.html Open/close the space]
{{BoiteFin}}

{{Boite
| titre=Assemblée Générale 2012 / General Assembly 2012
| couleurTexteTitre=black
| couleurTitre=red
| bordure=red
| fond=lightgray
| flotte=left
| largeur=100%
}}
L'assemblée générale 2012 de FIXME aura lieu le '''mardi 11 décembre 2012, 20h'''.

Toutes les informations : [[AG 2012 December]]

----

FIXME General Assembly will take place on '''Tuesday, December 11, 2012'''.

All information on [[AG 2012 December]]
{{BoiteFin}}

{{Boite
| titre=[[:Category:Projects|Projects]]
| flotte=left
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Projects.png}}
* [[:Category:Ongoing_Projects|Ongoing]] | [[:Category:Proposed_Projects|Proposed]] | [[:Category:Closed_Projects|Closed]]
* [[Project template]] | [[Projects Ideas]]

===Top projects===
* [[GIMP + Photoshop Workshop]]
* [[LED Retrofit]]
* [[29C3]]
* [[HackerspacesDinner]]
* [[Tron_Restore]]
* [[T-shirt FIXME]]
* [[Screen sound]]
* [[PCB_Etching]]
* [[Ultimaker|Ultimaker 3D printer]]
* [[AG_2012_December]]
{{BoiteFin}}

{{Boite
| titre=Events
| flotte=right
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Events.png}}

===Recuring events===
* Every mondays [[Electronics evening]]
* Every wednesdays [[Weekly Meetings]]
* Every friday evening [[Hacking challenges|CTF]]
* Every other friday [[dooky dooky meeting]]

===Ponctual events===
* [[:Category:CodingNight|Coding Night]]
* [[:Category:Workshops|Workshops]]
* [[:Category:ShortTalks|Short Talks]]
* [[:Category:Debates|Debates]]
* [[Suggestion box]]
{{BoiteFin}}

{{Boite
| titre=Other
| flotte=left
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Other.png}}
* Equipment
** [[What do we provide ?]]
** [[What are we looking for ?]]
* [[Resources]] (local associations, events and shops)
* [[Movies|Geek movies]]
* [[Modele XP]]
* [[Sandbox]] for syntax tests
* [[Burgers]]
* [[Minecraft]]
* [[Podcasts]]
{{BoiteFin}}

{{Boite
| titre=Administration
| flotte=right
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Administration.png}}
* [[Openings]]
* [[Internal Regulation]] [French]
* [[Roles]]
* [[Membership_admin]]
* [[:Category:Meetings|Meetings]]
* [[Press_reviews]]
* [[Communication]]
* [[Utilité_publique]]: [https://pad.fixme.ch/p/letter_to_lausanne subventions], ...
* [[History]]
* [[Network]]
* [[Logo]]
{{BoiteFin}}

{{Boite
| titre=Electronic
| flotte=left
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Other.png}}
* [[Parts Order]]
* [[:Category:ElectroKit|Electronic kits]]
* [[Electronic FAQ]]
* [[CPU_Boards]]
{{BoiteFin}}

{{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}}

File:Prices.odt

2012-11-21T20:37:11Z

CrazyGolem: uploaded a new version of "File:Prices.odt"

Price list for the fridge

AG 2012 December

2012-11-14T12:51:38Z

CrazyGolem: /* Proposition 3 (Crazygolem) */

[[Category:Meetings]]
[[Category:AG]]
== Information ==
* Mardi 11 décembre 2012 à 20h
* Date picking http://framadate.org/c6eld5ydzmws7l74

== To discuss ==
* Comitee election, proposition
** Président: Freestorm, Crazygolem
** Secrétaire: Nemen
** Caissier: Prosouth
** Logistique: Rorist

=== Finance ===
* Accounts balance and presentation
* Transparency on the account (regular point?)
* Budget for buying stuff, budget in general.
* Taskforce groups
** Create a group for getting public subventions, being of [[Utilité_publique|public utility]]
** New local (search, subventions, ...)
* Open a Paypal account to receive payments (membership, donations, etc.)

=== Membership ===
* Align membership on January, so everyone has the same period (easier to manage)
* Remove subscription fees (30chf)
* More members with the keys ?
* Add a new membership, see [[Meeting_20120914]]
* Should we put a new way to elect exceptions ? (like gcmalloc/nemen)
* Should we continue with such exceptions ?
* Should we add a subscription/donation form with Paypal on Fixme website?

==== Proposition 1 (Rorist) ====
* 25.-/month (300.-/year)
* Key validation by 3 keys members

==== Proposition 2 (Nemen) ====
* 30.-/monthly or 330.-/yearly (1 free month)
* -50% for students
* Key validation by 2 keys members
==== Proposition 3 (Crazygolem) ====
'''Fee 1''': CHF 100 / month
* One free Key
* One free locker upon request
* Priority over ''Fee 2'' members for lockers

'''Fee 2''': CHF 30 / month
* Key
** Only if validated by 5 members that have a key (validation is revocable: ''chain of trust'' model)
* Locker
** If available
** Locker attribution can be revoked (with prior notice) for ''Fee 1'' members

'''Fee 3''': CHF 10 / month
* No key
* No locker

'''Packs & Bonuses'''
* Key: CHF 10 / month
* Locker: CHF 10 / month
* 50% on fees (not on packs) for students

=== Other stuff ===
* Results of the [[roles]], what to do with all this stuff that has to be done ?
* Being member of the CCC-CH https://www.ccczh.ch/CCC-CH/Statuten
* License for the wiki:
** Public Domaine like ? http://creativecommons.org/publicdomain/zero/1.0/
** OpenSource license ?
* Licenses for work done for FIXME (Logo, flyers, etc)
** CC licenses too restrictive ? (BY clause)
** Require at least separate and more flexible license for FIXME (along with default CC / other license)
* What is the commitee for ?
* status of the actual role [Roles], speak about delegation and responsability of the members.
* Can we transfer the bail to fixme as an association and not to a single person ? Would thermibel be ok with it ?

== Bonus (to be discussed outsite an AG (ML, ...) ==
* fixme.ch certificate and general security concern.
* General discussion about the internal infrastructure and migration on the internal server.

AG 2012 December

2012-11-14T12:40:55Z

CrazyGolem: /* Proposition 3 (Crazygolem) */

[[Category:Meetings]]
[[Category:AG]]
== Information ==
* Mardi 11 décembre 2012 à 20h
* Date picking http://framadate.org/c6eld5ydzmws7l74

== To discuss ==
* Comitee election, proposition
** Président: Freestorm, Crazygolem
** Secrétaire: Nemen
** Caissier: Prosouth
** Logistique: Rorist

=== Finance ===
* Accounts balance and presentation
* Transparency on the account (regular point?)
* Budget for buying stuff, budget in general.
* Taskforce groups
** Create a group for getting public subventions, being of [[Utilité_publique|public utility]]
** New local (search, subventions, ...)
* Open a Paypal account to receive payments (membership, donations, etc.)

=== Membership ===
* Align membership on January, so everyone has the same period (easier to manage)
* Remove subscription fees (30chf)
* More members with the keys ?
* Add a new membership, see [[Meeting_20120914]]
* Should we put a new way to elect exceptions ? (like gcmalloc/nemen)
* Should we continue with such exceptions ?
* Should we add a subscription/donation form with Paypal on Fixme website?

==== Proposition 1 (Rorist) ====
* 25.-/month (300.-/year)
* Key validation by 3 keys members

==== Proposition 2 (Nemen) ====
* 30.-/monthly or 330.-/yearly (1 free month)
* -50% for students
* Key validation by 2 keys members
==== Proposition 3 (Crazygolem) ====
'''Fee 1''': CHF 100 / month
* One free Key
* One free locker upon request (priority over ''Fee 2'' members)

'''Fee 2''': CHF 30 / month
* Key
** Only if validated by 5 members that have a key (validation is revocable: ''chain of trust'' model)
* Locker
** If available
** Locker attribution can be revoked (with prior notice) for ''Fee 1'' members

'''Fee 3''': CHF 10 / month
* No key
* No locker

'''Packs & Bonuses'''
* Key: CHF 10 / month
* Locker: CHF 10 / month
* 50% on fees (not on packs) for students

=== Other stuff ===
* Results of the [[roles]], what to do with all this stuff that has to be done ?
* Being member of the CCC-CH https://www.ccczh.ch/CCC-CH/Statuten
* License for the wiki:
** Public Domaine like ? http://creativecommons.org/publicdomain/zero/1.0/
** OpenSource license ?
* Licenses for work done for FIXME (Logo, flyers, etc)
** CC licenses too restrictive ? (BY clause)
** Require at least separate and more flexible license for FIXME (along with default CC / other license)
* What is the commitee for ?
* status of the actual role [Roles], speak about delegation and responsability of the members.
* Can we transfer the bail to fixme as an association and not to a single person ? Would thermibel be ok with it ?

== Bonus (to be discussed outsite an AG (ML, ...) ==
* fixme.ch certificate and general security concern.
* General discussion about the internal infrastructure and migration on the internal server.

AG 2012 December

2012-11-14T12:38:58Z

CrazyGolem: /* Proposition 2 (Nemen) */

[[Category:Meetings]]
[[Category:AG]]
== Information ==
* Mardi 11 décembre 2012 à 20h
* Date picking http://framadate.org/c6eld5ydzmws7l74

== To discuss ==
* Comitee election, proposition
** Président: Freestorm, Crazygolem
** Secrétaire: Nemen
** Caissier: Prosouth
** Logistique: Rorist

=== Finance ===
* Accounts balance and presentation
* Transparency on the account (regular point?)
* Budget for buying stuff, budget in general.
* Taskforce groups
** Create a group for getting public subventions, being of [[Utilité_publique|public utility]]
** New local (search, subventions, ...)
* Open a Paypal account to receive payments (membership, donations, etc.)

=== Membership ===
* Align membership on January, so everyone has the same period (easier to manage)
* Remove subscription fees (30chf)
* More members with the keys ?
* Add a new membership, see [[Meeting_20120914]]
* Should we put a new way to elect exceptions ? (like gcmalloc/nemen)
* Should we continue with such exceptions ?
* Should we add a subscription/donation form with Paypal on Fixme website?

==== Proposition 1 (Rorist) ====
* 25.-/month (300.-/year)
* Key validation by 3 keys members

==== Proposition 2 (Nemen) ====
* 30.-/monthly or 330.-/yearly (1 free month)
* -50% for students
* Key validation by 2 keys members
==== Proposition 3 (Crazygolem) ====
'''Fee 1''': CHF 100 / month
* One free Key
* One free locker upon request (priority over ''Fee 2'' members)

'''Fee 2''': CHF 30 / month
* Key
** Only if validated by 5 members that have a key (revocable)
* Locker
** If available
** Locker attribution can be revoked (with prior notice) for ''Fee 1'' members

'''Fee 3''': CHF 10 / month
* No key
* No locker

'''Packs & Bonuses'''
* Key: CHF 10 / month
* Locker: CHF 10 / month
* 50% on fees (not on packs) for students

=== Other stuff ===
* Results of the [[roles]], what to do with all this stuff that has to be done ?
* Being member of the CCC-CH https://www.ccczh.ch/CCC-CH/Statuten
* License for the wiki:
** Public Domaine like ? http://creativecommons.org/publicdomain/zero/1.0/
** OpenSource license ?
* Licenses for work done for FIXME (Logo, flyers, etc)
** CC licenses too restrictive ? (BY clause)
** Require at least separate and more flexible license for FIXME (along with default CC / other license)
* What is the commitee for ?
* status of the actual role [Roles], speak about delegation and responsability of the members.
* Can we transfer the bail to fixme as an association and not to a single person ? Would thermibel be ok with it ?

== Bonus (to be discussed outsite an AG (ML, ...) ==
* fixme.ch certificate and general security concern.
* General discussion about the internal infrastructure and migration on the internal server.

AG 2012 December

2012-11-14T09:32:23Z

CrazyGolem: /* To discuss */

[[Category:Meetings]]
[[Category:AG]]
== Information ==
* Mardi 11 décembre 2012 à 20h
* Date picking http://framadate.org/c6eld5ydzmws7l74

== To discuss ==
* Comitee election, proposition
** Président: Freestorm, Crazygolem
** Secrétaire: Nemen
** Caissier: Prosouth
** Logistique: Rorist

=== Finance ===
* Accounts balance and presentation
* Transparency on the account (regular point?)
* Budget for buying stuff, budget in general.
* Taskforce groups
** Create a group for getting public subventions, being of [[Utilité_publique|public utility]]
** New local (search, subventions, ...)
* Open a Paypal account to receive payments (membership, donations, etc.)

=== Membership ===
* Align membership on January, so everyone has the same period (easier to manage)
* Remove subscription fees (30chf)
* More members with the keys ?
* Add a new membership, see [[Meeting_20120914]]
* Should we put a new way to elect exceptions ? (like gcmalloc/nemen)
* Should we continue with such exceptions ?
* Should we add a subscription/donation form with Paypal on Fixme website?

==== Proposition 1 (Rorist) ====
* 25.-/month (300.-/year)
* Key validation by 3 keys members

==== Proposition 2 (Nemen) ====
* 30.-/monthly or 330.-/yearly (1 free month)
* -50% for students
* Key validation by 2 keys members

=== Other stuff ===
* Results of the [[roles]], what to do with all this stuff that has to be done ?
* Being member of the CCC-CH https://www.ccczh.ch/CCC-CH/Statuten
* License for the wiki:
** Public Domaine like ? http://creativecommons.org/publicdomain/zero/1.0/
** OpenSource license ?
* Licenses for work done for FIXME (Logo, flyers, etc)
** CC licenses too restrictive ? (BY clause)
** Require at least separate and more flexible license for FIXME (along with default CC / other license)
* What is the commitee for ?
* status of the actual role [Roles], speak about delegation and responsability of the members.
* Can we transfer the bail to fixme as an association and not to a single person ? Would thermibel be ok with it ?

== Bonus (to be discussed outsite an AG (ML, ...) ==
* fixme.ch certificate and general security concern.
* General discussion about the internal infrastructure and migration on the internal server.

File:Prices.odt

2012-09-07T17:17:50Z

CrazyGolem: uploaded a new version of "File:Prices.odt"

Price list for the fridge

File:Prices.odt

2012-09-07T17:16:30Z

CrazyGolem: uploaded a new version of "File:Prices.odt"

Price list for the fridge