https://www.funtoo.org/api.php?action=feedcontributions&user=Golodhrim&feedformat=atomFuntoo - User contributions [en]2024-03-19T05:09:32ZUser contributionsMediaWiki 1.36.2https://www.funtoo.org/index.php?title=User:Golodhrim&diff=4005User:Golodhrim2014-05-30T19:46:56Z<p>Golodhrim: </p>
<hr />
<div>{{Person<br />
|Full name=Martin 'golodhrim' Scholz<br />
|Email=golodhrim@funtoo.org<br />
|Nick=golodhrim<br />
|Geoloc=51.13379, 8.86179<br />
|Location name=Ederbringhauen, Hessen, Germany<br />
|Roles={{Role<br />
|Role type=Staff<br />
|Role desc=Core Community Manager<br />
|Start date=2009/09/01<br />
|End date=<br />
}}{{Role<br />
|Role type=User<br />
|Role desc=Just a User<br />
|Start date=2009/01/01<br />
|End date=2009/09/30<br />
}}<br />
|Blogs=<br />
|Maintains={{Ebuild<br />
|Ebuild=www-servers/nginx<br />
|Overlay=Funtoo<br />
}}{{Ebuild<br />
|Ebuild=sys-process/whenjobs<br />
|Overlay=Funtoo<br />
}}{{Ebuild<br />
|Ebuild=dev-lua/linotify<br />
|Overlay=Funtoo<br />
}}{{Ebuild<br />
|Ebuild=net-im/prosody-modules<br />
|Overlay=Funtoo<br />
}}<br />
}}<br />
{{User page<br />
|fileextention=png<br />
|welcome= == Mae Govannen randir == <br />
pedo mellon a minno <br />
(be greeted hiker)<br />
|biography=studied Math and Chemstry for educational science, quite it without end in 2012. Normally I'm found online in jabber/xmpp network all the time. Next to it I hang around in [irc://irc.freenode.net/funtoo #funtoo], [irc://irc.freenode.net/funtoo-quebec #funtoo-quebec] and some others not related to funtoo... After I quit my studies, I now started to work as a Trainee IT specialist system integration for the german internet name center. Now I started a trainee position as IT Specialist for System Integration at Denic eG on Aug 2013 and will finish it possibly in February 2015<br />
|history_linux=I started my way to Linux by an advice of an teacher of mine with SuSE Linux 6.* stayed there until 9.0 and it was fun as long as you didn't update your system, this period hold for about 2 years, then I switched to debian and stayed there until Spring 2009, that was the time I gave Gentoo a try and it was fun at first to install it, but the war of releasing upgrades without a careful testing made it a hell and so I switched from gentoo to funtoo only after about a quarter year. Since then I stayed with funtoo.<br />
|oss_information=working on some ConTeXt projects too, right now try to write an source ebuild for it...<br />
|history_funtoo=using it since 2009 and beeing very happy with it, maintaining my private overlay with smaller ebuilds...<br />
|real_life=<pre>$ man rl<br />
<br />
rl(1) The Real Life rl(1)<br />
<br />
<br />
<br />
NAME<br />
rl - reallife<br />
<br />
SYNOPSIS<br />
rl [ Options ]<br />
<br />
DESCRIPTION<br />
rl, short for reallife, refers to life in the real world.<br />
<br />
rl would mean that you have a life next to Funtoo, Linux or hacking,<br />
what wouldn't affect all the devs, except for a little offtime they take<br />
for regenerating their internal batteries. Therefore "rl" has several<br />
options that can be used to explain what to do in rl mode.<br />
<br />
The rl-mode can only be set in combination with a Geek or Hacker that you<br />
have in front of the computer screen.<br />
<br />
OPTIONS<br />
--eat, -e <MEAL> <TIME><br />
Used to move the Geek or Hacker into the kitchen and let him prepare<br />
a meal specified by <MEAL> for the given daytime <TIME>, where <TIME><br />
is in the form of mm/dd/yyyy-hh:mm. If <MEAL> and <TIME> isn't<br />
specified it means that the Geek/Hacker will grab the next phone,<br />
call the local Pizza or Doener delivery service and order a Pizza or<br />
Doener there, that he will consume as soon as it arrives.<br />
<br />
--weekend, -we<br />
moves the Geek or Hacker into a two day lasting weekend where he is<br />
normaly not available on the PC, but it might happen that he has a<br />
connection to the internet from his cell-phone, so better take it<br />
away.<br />
<br />
--suspend, --sleep, -s <TIME><br />
moves the Geek or Hacker for <TIME> in seconds to sleep, if <TIME><br />
isn't specified it defaults here to 10800 seconds what would be 3hrs.<br />
<br />
--drink, -d <DRINK> <AMOUNT> <TIME><br />
so that the Geek or Hacker doesn't die, he also sometimes need to drink.<br />
this moves him to get <AMOUNT> of <DRINK> at <TIME>. If you specified<br />
<DRINK> it is necessary that you also specify the <AMOUNT> else the<br />
command is abborted. When the drinking should happen at a special time<br />
add <TIME> in format mm/dd/yyyy-hh:mm to the command. If you just use<br />
the drink-option it will default to <DRINK>=coffee or Jolt-coke<br />
depending on what the Geek or Hacker sees first and <AMOUNT>=2-3 cups<br />
or cans and <TIME>=now.<br />
<br />
--holiday, -away, -a <TIME><br />
will move the Geek or Hacker away from the net for <TIME> and give him<br />
a recreational pause. He will come back after <TIME> to work with more<br />
power and even better ideas. <TIME> here is explicit needed and has to<br />
be given in format of days or weeks, so 14d will be equal to 2w.<br />
<br />
--social_contact, -sc <PERSON> or <GROUP><br />
that moves the Geek or Hacker away from the PC for a short period where<br />
a <PERSON> or <GROUP> comes over to visit him or he needs to move to<br />
them. The period of time he is away can vary from several hours to some<br />
days, so be patient if this option is set.<br />
</pre><br />
|lang_skills=I speak German as my native lang and learned English for 8 and French for 5 years at School. ATM I'm not really used to talk French any more as I hadn't had a opportunity to do so for the last years... So will give my best to also help our french users, feel free to ask. For places to meet me see at Biography...<br />
|working_on= * working on [[flora]], the Funtoo Linux Overlay for User Contribution<br />
* writing howto for [[nginx]]<br />
* writing howto for [[wpa_supplicant]] <br />
* writing an ebuild for ConTeXt-minimals source based, atm a low priority project...<br />
|worked_on=* updated ebuild for dhcpcd-5.2.11<br />
* tested sandbox 2.5 with metro<br />
* starting to rewrite the quick install howto from Guy Fontaine to [[Funtoo_Quick_Install]]<br />
* update Funtoo install guide with quick install guide<br />
* writing guide for [[flora]], the Funtoo Linux Overlay for User Contribution<br />
}}<br />
== Boxes ==<br />
* mordor -- Homeserver (x86_64 architecture) ~funtoo<br />
* hobbigen -- Main PC (x86_64 architecture) ~funtoo<br />
* lorien -- Laptop (x86_64 architecture) ~funtoo HP Compaq 6820s (died 2011)<br />
* lorien -- Laptop (x86_64 architecture) ~funtoo Dell Vostro 6830<br />
* doriath -- rootserver (x86_64 architecture) ~funtoo Hetzner EX6S rootserver</div>Golodhrimhttps://www.funtoo.org/index.php?title=FLOP:Enterprise_Guides&diff=3475FLOP:Enterprise Guides2014-02-24T21:20:53Z<p>Golodhrim: </p>
<hr />
<div>{{FLOP<br />
|Created on=2014/01/12<br />
|Summary=Guides for a Funtoo Linux Enterprise Setup<br />
|Author=Golodhrim, Psychopatch, <br />
|Maintainer=Golodhrim, Psychopatch, <br />
|Organization=Funtoo Linux<br />
}}<br />
This is the FLOP for the Funtoo Linux Enterprise Guide, it is split up into several Userstories in the backlog of jira and will be handled as a first real Scrum Project in Funtoo Linux.<br />
{{FLOPFooter}}</div>Golodhrimhttps://www.funtoo.org/index.php?title=FLOP:Enterprise_Guides&diff=3474FLOP:Enterprise Guides2014-02-24T21:17:34Z<p>Golodhrim: Created page with "{{FLOP |Created on=2014/01/12 |Summary=Guides for a Funtoo Linux Enterprise Setup |Author=golodhr }} {{FLOPFooter}}"</p>
<hr />
<div>{{FLOP<br />
|Created on=2014/01/12<br />
|Summary=Guides for a Funtoo Linux Enterprise Setup<br />
|Author=golodhr<br />
}}<br />
<br />
{{FLOPFooter}}</div>Golodhrimhttps://www.funtoo.org/index.php?title=User:Golodhrim&diff=1020User:Golodhrim2014-01-07T01:10:58Z<p>Golodhrim: </p>
<hr />
<div>{{Person<br />
|Full name=Martin 'golodhrim' Scholz<br />
|Email=golodhrim@funtoo.org<br />
|Nick=golodhrim<br />
|Geoloc=51.13379, 8.86179<br />
|Location name=Ederbringhauen, Hessen, Germany<br />
|Roles={{Role<br />
|Role type=Staff<br />
|Role desc=Core Community Manager<br />
|Start date=2009/09/01<br />
}}{{Role<br />
|Role type=User<br />
|Role desc=Just a User<br />
|Start date=2009/01/01<br />
|End date=2009/09/30<br />
}}<br />
|Maintains={{Ebuild<br />
|Ebuild=www-servers/nginx<br />
|Overlay=Funtoo<br />
}}{{Ebuild<br />
|Ebuild=sys-process/whenjobs<br />
|Overlay=Funtoo<br />
}}{{Ebuild<br />
|Ebuild=dev-lua/linotify<br />
|Overlay=Funtoo<br />
}}{{Ebuild<br />
|Ebuild=net-im/prosody-modules<br />
|Overlay=Funtoo<br />
}}<br />
|Blogs=<br />
}}<br />
{{User page<br />
|fileextention=png<br />
|welcome= == Mae Govannen randir == <br />
pedo mellon a minno <br />
(be greeted hiker)<br />
|biography=studied Math and Chemstry for educational science. Normally I'm found online in jabber/xmpp network all the time. Next to it I hang around in [irc://irc.freenode.net/funtoo #funtoo], [irc://irc.freenode.net/funtoo-quebec #funtoo-quebec] and some others not related to funtoo... After I quit my studies, I now started to work as a Trainee IT specialist system integration for the german internet name center.<br />
|history_linux=I started my way to Linux by an advice of an teacher of mine with SuSE Linux 6.* stayed there until 9.0 and it was fun as long as you didn't update your system, this period hold for about 2 years, then I switched to debian and stayed there until Spring 2009, that was the time I gave Gentoo a try and it was fun at first to install it, but the war of releasing upgrades without a careful testing made it a hell and so I switched from gentoo to funtoo only after about a quarter year. Since then I stayed with funtoo.<br />
|oss_information=working on some ConTeXt projects too, right now try to write an source ebuild for it...<br />
|history_funtoo=using it since 2009 and beeing very happy with it, maintaining my private overlay with smaller ebuilds...<br />
|real_life=<pre>$ man rl<br />
<br />
rl(1) The Real Life rl(1)<br />
<br />
<br />
<br />
NAME<br />
rl - reallife<br />
<br />
SYNOPSIS<br />
rl [ Options ]<br />
<br />
DESCRIPTION<br />
rl, short for reallife, refers to life in the real world.<br />
<br />
rl would mean that you have a life next to Funtoo, Linux or hacking,<br />
what wouldn't affect all the devs, except for a little offtime they take<br />
for regenerating their internal batteries. Therefore "rl" has several<br />
options that can be used to explain what to do in rl mode.<br />
<br />
The rl-mode can only be set in combination with a Geek or Hacker that you<br />
have in front of the computer screen.<br />
<br />
OPTIONS<br />
--eat, -e <MEAL> <TIME><br />
Used to move the Geek or Hacker into the kitchen and let him prepare<br />
a meal specified by <MEAL> for the given daytime <TIME>, where <TIME><br />
is in the form of mm/dd/yyyy-hh:mm. If <MEAL> and <TIME> isn't<br />
specified it means that the Geek/Hacker will grab the next phone,<br />
call the local Pizza or Doener delivery service and order a Pizza or<br />
Doener there, that he will consume as soon as it arrives.<br />
<br />
--weekend, -we<br />
moves the Geek or Hacker into a two day lasting weekend where he is<br />
normaly not available on the PC, but it might happen that he has a<br />
connection to the internet from his cell-phone, so better take it<br />
away.<br />
<br />
--suspend, --sleep, -s <TIME><br />
moves the Geek or Hacker for <TIME> in seconds to sleep, if <TIME><br />
isn't specified it defaults here to 10800 seconds what would be 3hrs.<br />
<br />
--drink, -d <DRINK> <AMOUNT> <TIME><br />
so that the Geek or Hacker doesn't die, he also sometimes need to drink.<br />
this moves him to get <AMOUNT> of <DRINK> at <TIME>. If you specified<br />
<DRINK> it is necessary that you also specify the <AMOUNT> else the<br />
command is abborted. When the drinking should happen at a special time<br />
add <TIME> in format mm/dd/yyyy-hh:mm to the command. If you just use<br />
the drink-option it will default to <DRINK>=coffee or Jolt-coke<br />
depending on what the Geek or Hacker sees first and <AMOUNT>=2-3 cups<br />
or cans and <TIME>=now.<br />
<br />
--holiday, -away, -a <TIME><br />
will move the Geek or Hacker away from the net for <TIME> and give him<br />
a recreational pause. He will come back after <TIME> to work with more<br />
power and even better ideas. <TIME> here is explicit needed and has to<br />
be given in format of days or weeks, so 14d will be equal to 2w.<br />
<br />
--social_contact, -sc <PERSON> or <GROUP><br />
that moves the Geek or Hacker away from the PC for a short period where<br />
a <PERSON> or <GROUP> comes over to visit him or he needs to move to<br />
them. The period of time he is away can vary from several hours to some<br />
days, so be patient if this option is set.<br />
</pre><br />
|lang_skills=I speak German as my native lang and learned English for 8 and French for 5 years at School. ATM I'm not really used to talk French any more as I hadn't had a opportunity to do so for the last years... So will give my best to also help our french users, feel free to ask. For places to meet me see at Biography...<br />
|working_on= * working on [[flora]], the Funtoo Linux Overlay for User Contribution<br />
* writing howto for [[nginx]]<br />
* writing howto for [[wpa_supplicant]] <br />
* writing an ebuild for ConTeXt-minimals source based, atm a low priority project...<br />
|worked_on=* updated ebuild for dhcpcd-5.2.11<br />
* tested sandbox 2.5 with metro<br />
* starting to rewrite the quick install howto from Guy Fontaine to [[Funtoo_Quick_Install]]<br />
* update Funtoo install guide with quick install guide<br />
* writing guide for [[flora]], the Funtoo Linux Overlay for User Contribution<br />
}}<br />
== Boxes ==<br />
* mordor -- Homeserver (x86_64 architecture) ~funtoo<br />
* hobbigen -- Main PC (x86_64 architecture) ~funtoo<br />
* lorien -- Laptop (x86_64 architecture) ~funtoo HP Compaq 6820s (died 2011)<br />
* lorien -- Laptop (x86_64 architecture) ~funtoo Dell Vostro 6830<br />
* doriath -- rootserver (x86_64 architecture) ~funtoo Hetzner EX6S rootserver</div>Golodhrimhttps://www.funtoo.org/index.php?title=User:Golodhrim&diff=1019User:Golodhrim2014-01-07T01:08:45Z<p>Golodhrim: </p>
<hr />
<div>{{Person<br />
|Full name=Martin 'golodhrim' Scholz<br />
|Email=golodhrim@funtoo.org<br />
|Nick=golodhrim<br />
|Geoloc=51.13379, 8.86179<br />
|Location name=Ederbringhauen, Hessen, Germany<br />
|Roles={{Role<br />
|Role type=Staff<br />
|Role desc=Core Community Manager<br />
|Start date=2009/09/01<br />
}}{{Role<br />
|Role type=User<br />
|Role desc=Just a User<br />
|Start date=2009/01/01<br />
|End date=2009/09/30<br />
}}<br />
|Maintains={{Ebuild<br />
|Ebuild=www-servers/nginx<br />
|Overlay=Funtoo<br />
}}{{Ebuild<br />
|Ebuild=sys-process/whenjobs<br />
|Overlay=Funtoo<br />
}}{{Ebuild<br />
|Ebuild=dev-lua/linotify<br />
|Overlay=Funtoo<br />
}}{{Ebuild<br />
|Ebuild=net-im/prosody-modules<br />
|Overlay=Funtoo<br />
}}<br />
|Blogs=<br />
}}<br />
{{User page<br />
|fileextention=png<br />
|welcome= == Mae Govannen randir == <br />
pedo mellon a minno <br />
(be greeted hiker)<br />
|biography=studied Math and Chemstry for educational science. Normally I'm found online in jabber/xmpp network all the time. Next to it I hang around in [irc://irc.freenode.net/funtoo #funtoo], [irc://irc.freenode.net/funtoo-quebec #funtoo-quebec] and some others not related to funtoo... After I quit my studies, I now started to work as a Trainee IT specialist system integration for the german internet name center.<br />
|history_linux=I started my way to Linux by an advice of an teacher of mine with SuSE Linux 6.* stayed there until 9.0 and it was fun as long as you didn't update your system, this period hold for about 2 years, then I switched to debian and stayed there until Spring 2009, that was the time I gave Gentoo a try and it was fun at first to install it, but the war of releasing upgrades without a careful testing made it a hell and so I switched from gentoo to funtoo only after about a quarter year. Since then I stayed with funtoo.<br />
|oss_information=working on some ConTeXt projects too, right now try to write an source ebuild for it...<br />
|history_funtoo=using it since 2009 and beeing very happy with it, maintaining my private overlay with smaller ebuilds...<br />
|real_life=<pre>$ man rl<br />
<br />
rl(1) The Real Life rl(1)<br />
<br />
<br />
<br />
NAME<br />
rl - reallife<br />
<br />
SYNOPSIS<br />
rl [ Options ]<br />
<br />
DESCRIPTION<br />
rl, short for reallife, refers to life in the real world.<br />
<br />
rl would mean that you have a life next to Funtoo, Linux or hacking,<br />
what wouldn't affect all the devs, except for a little offtime they take<br />
for regenerating their internal batteries. Therefore "rl" has several<br />
options that can be used to explain what to do in rl mode.<br />
<br />
The rl-mode can only be set in combination with a Geek or Hacker that you<br />
have in front of the computer screen.<br />
<br />
OPTIONS<br />
--eat, -e <MEAL> <TIME><br />
Used to move the Geek or Hacker into the kitchen and let him prepare<br />
a meal specified by <MEAL> for the given daytime <TIME>, where <TIME><br />
is in the form of mm/dd/yyyy-hh:mm. If <MEAL> and <TIME> isn't<br />
specified it means that the Geek/Hacker will grab the next phone,<br />
call the local Pizza or Doener delivery service and order a Pizza or<br />
Doener there, that he will consume as soon as it arrives.<br />
<br />
--weekend, -we<br />
moves the Geek or Hacker into a two day lasting weekend where he is<br />
normaly not available on the PC, but it might happen that he has a<br />
connection to the internet from his cell-phone, so better take it<br />
away.<br />
<br />
--suspend, --sleep, -s <TIME><br />
moves the Geek or Hacker for <TIME> in seconds to sleep, if <TIME><br />
isn't specified it defaults here to 10800 seconds what would be 3hrs.<br />
<br />
--drink, -d <DRINK> <AMOUNT> <TIME><br />
so that the Geek or Hacker doesn't die, he also sometimes need to drink.<br />
this moves him to get <AMOUNT> of <DRINK> at <TIME>. If you specified<br />
<DRINK> it is necessary that you also specify the <AMOUNT> else the<br />
command is abborted. When the drinking should happen at a special time<br />
add <TIME> in format mm/dd/yyyy-hh:mm to the command. If you just use<br />
the drink-option it will default to <DRINK>=coffee or Jolt-coke<br />
depending on what the Geek or Hacker sees first and <AMOUNT>=2-3 cups<br />
or cans and <TIME>=now.<br />
<br />
--holiday, -away, -a <TIME><br />
will move the Geek or Hacker away from the net for <TIME> and give him<br />
a recreational pause. He will come back after <TIME> to work with more<br />
power and even better ideas. <TIME> here is explicit needed and has to<br />
be given in format of days or weeks, so 14d will be equal to 2w.<br />
<br />
--social_contact, -sc <PERSON> or <GROUP><br />
that moves the Geek or Hacker away from the PC for a short period where<br />
a <PERSON> or <GROUP> comes over to visit him or he needs to move to<br />
them. The period of time he is away can vary from several hours to some<br />
days, so be patient if this option is set.<br />
</pre><br />
|lang_skills=I speak German as my native lang and learned English for 8 and French for 5 years at School. ATM I'm not really used to talk French any more as I hadn't had a opportunity to do so for the last years... So will give my best to also help our french users, feel free to ask. For places to meet me see at Biography...<br />
|working_on= * working on [[flora]], the Funtoo Linux Overlay for User Contribution<br />
* writing howto for [[nginx]]<br />
* writing howto for [[wpa_supplicant]] <br />
* writing an ebuild for ConTeXt-minimals source based, atm a low priority project...<br />
|worked_on=* updated ebuild for dhcpcd-5.2.11<br />
* tested sandbox 2.5 with metro<br />
* starting to rewrite the quick install howto from Guy Fontaine to [[Funtoo_Quick_Install]]<br />
* update Funtoo install guide with quick install guide<br />
* writing guide for [[flora]], the Funtoo Linux Overlay for User Contribution<br />
}}<br />
== Boxes ==<br />
* mordor -- Homeserver (x86_64 architecture) ~funtoo<br />
* hobbigen -- Main PC (x86_64 architecture) ~funtoo will be there for a gentoo bug resolver<br />
* lorien -- Laptop (x86_64 architecture) ~funtoo HP Compaq 6820s (died 2011)<br />
* lorien -- Laptop (x86_64 architecture) ~funtoo experimental Dell Vostro 6830</div>Golodhrimhttps://www.funtoo.org/index.php?title=Funtoo_Events&diff=2618Funtoo Events2013-01-31T21:34:49Z<p>Golodhrim: </p>
<hr />
<div>{{Event Calendar Item<br />
|event=Start of Funtoo Events Calendar<br />
|start=2013/01/29<br />
|type=Meeting<br />
}}<br />
<br />
This site is a WIP for events the Funtoo Community is invited to join and get a meet and greet with devs and other entusiast of Funtoo Linux. :)<br />
<br />
{{#ask:[[Has event::+]][[Has event start::+]]<br />
|?Has event=title<br />
|?Has event start<br />
|?Has event end<br />
|?Has event description=Description<br />
|?Has event icon=icon<br />
|?Has event color=color<br />
|?Has event location <br />
|format=eventcalendar<br />
|start=earliest<br />
|defaultview=month<br />
|limit= <br />
|link=subject<br />
|legend=pane<br />
|firstday=Sunday<br />
|dayview=yes<br />
|headers=show<br />
|theme=vector}}<br />
<br />
{{#formlink:popup|form=Event Calendar Item|link text=Create event|link type=button}}</div>Golodhrimhttps://www.funtoo.org/index.php?title=Template:Event_Calendar_Item&diff=2614Template:Event Calendar Item2013-01-29T21:56:20Z<p>Golodhrim: </p>
<hr />
<div><noinclude><br />
This is the "Event Calendar Item" template.<br />
</noinclude><includeonly><br />
{| style="width:100%;"! style="width: 110px; text-align: left; vertical-align: middle;" |Event:<br />
| style="text-align: left;" colspan="3"|{{{event}}}<br />
|-<br />
! style="width: 110px; text-align: left; vertical-align: middle;" | Start:<br />
| {{{start|}}}<br />
! style="width: 110px; text-align: left; vertical-align: middle;" | End:<br />
| {{{end|}}}<br />
|-<br />
! style="text-align: left;"| Type:<br />
| style="text-align: left;"| {{{type|}}}<br />
! style="width: 80px; text-align: left; vertical-align: middle;" | Location:<br />
| {{{location|}}}<br />
|-<br />
! style="width: 110px; text-align: left; vertical-align: top;" | Description:<br />
| style="text-align: left;" colspan="3" | {{{description|}}}<br />
|-<br />
! style="width: 110px; text-align: left; vertical-align: middle;" |<br />
| style="text-align: right;" colspan="3" | [[Funtoo Events|Other events]]<br />
|} __NOFACTBOX__ <br />
[[Page has default form::Event Calendar Item| ]] <br />
{{#subobject:<br />
|Has event={{{event|}}}<br />
|Has event start={{{start|}}}<br />
|Has event end={{{end|}}}<br />
|Has event type={{{type|}}}<br />
|Has event location={{{location|}}}<br />
|Has event icon={{#switch: {{{type|}}}|Meeting =File:Event-meeting-icon.png|Presentation=File:Event-presentation-icon.png|Talk=File:Event-talk-icon.png }}<br />
|Has event color={{#switch: {{{type|}}}|Meeting=#E9AF32|Presentation=#A0D8F1|Talk=#BF381A|Party=#E07628 }}<br />
|Has event description={{{description|}}} <br />
}}</includeonly></div>Golodhrimhttps://www.funtoo.org/index.php?title=User:Golodhrim&diff=1018User:Golodhrim2013-01-19T17:07:30Z<p>Golodhrim: </p>
<hr />
<div>{{Person<br />
|Full name=Martin 'golodhrim' Scholz<br />
|Email=golodhrim@funtoo.org<br />
|Nick=golodhrim<br />
|Geoloc=51.13379, 8.86179<br />
|Location name=Ederbringhauen, Hessen, Germany<br />
|Roles={{Role<br />
|Role type=Staff<br />
|Role desc=Core Community Manager<br />
|Start date=2009/09/01<br />
}}{{Role<br />
|Role type=User<br />
|Role desc=Just a User<br />
|Start date=2009/01/01<br />
|End date=2009/09/30<br />
}}<br />
|Maintains={{Ebuild<br />
|Ebuild=www-servers/nginx<br />
|Overlay=Funtoo-overlay<br />
}}{{Ebuild<br />
|Ebuild=sys-process/whenjobs<br />
|Overlay=Funtoo-overlay<br />
}}{{Ebuild<br />
|Ebuild=dev-lua/linotify<br />
|Overlay=Flora<br />
}}{{Ebuild<br />
|Ebuild=net-im/prosody-modules<br />
|Overlay=Flora<br />
}}<br />
|Blogs=<br />
}}<br />
{{User page<br />
|fileextention=png<br />
|welcome= == Mae Govannen randir == <br />
pedo mellon a minno <br />
(be greeted hiker)<br />
|biography=studying Math and Chemstry for educational science right know, hopefully finish it that year and see where I move then... Normally I'm found online in jabber/xmpp network all the time. Next to it I hang around in [irc://irc.freenode.net/funtoo #funtoo], [irc://irc.freenode.net/funtoo-quebec #funtoo-quebec] and some others not related to funtoo...<br />
|history_linux=I started my way to Linux by an advice of an teacher of mine with SuSE Linux 6.* stayed there until 9.0 and it was fun as long as you didn't update your system, this period hold for about 2 years, then I switched to debian and stayed there until Spring 2009, that was the time I gave Gentoo a try and it was fun at first to install it, but the war of releasing upgrades without a careful testing made it a hell and so I switched from gentoo to funtoo only after about a quarter year. Since then I stayed with funtoo.<br />
|oss_information=working on some ConTeXt projects too, right now try to write an source ebuild for it...<br />
|history_funtoo=using it since 2009 and beeing very happy with it, maintaining my private overlay with smaller ebuilds...<br />
|real_life=<pre>$ man rl<br />
<br />
rl(1) The Real Life rl(1)<br />
<br />
<br />
<br />
NAME<br />
rl - reallife<br />
<br />
SYNOPSIS<br />
rl [ Options ]<br />
<br />
DESCRIPTION<br />
rl, short for reallife, refers to life in the real world.<br />
<br />
rl would mean that you have a life next to Funtoo, Linux or hacking,<br />
what wouldn't affect all the devs, except for a little offtime they take<br />
for regenerating their internal batteries. Therefore "rl" has several<br />
options that can be used to explain what to do in rl mode.<br />
<br />
The rl-mode can only be set in combination with a Geek or Hacker that you<br />
have in front of the computer screen.<br />
<br />
OPTIONS<br />
--eat, -e <MEAL> <TIME><br />
Used to move the Geek or Hacker into the kitchen and let him prepare<br />
a meal specified by <MEAL> for the given daytime <TIME>, where <TIME><br />
is in the form of mm/dd/yyyy-hh:mm. If <MEAL> and <TIME> isn't<br />
specified it means that the Geek/Hacker will grab the next phone,<br />
call the local Pizza or Doener delivery service and order a Pizza or<br />
Doener there, that he will consume as soon as it arrives.<br />
<br />
--weekend, -we<br />
moves the Geek or Hacker into a two day lasting weekend where he is<br />
normaly not available on the PC, but it might happen that he has a<br />
connection to the internet from his cell-phone, so better take it<br />
away.<br />
<br />
--suspend, --sleep, -s <TIME><br />
moves the Geek or Hacker for <TIME> in seconds to sleep, if <TIME><br />
isn't specified it defaults here to 10800 seconds what would be 3hrs.<br />
<br />
--drink, -d <DRINK> <AMOUNT> <TIME><br />
so that the Geek or Hacker doesn't die, he also sometimes need to drink.<br />
this moves him to get <AMOUNT> of <DRINK> at <TIME>. If you specified<br />
<DRINK> it is necessary that you also specify the <AMOUNT> else the<br />
command is abborted. When the drinking should happen at a special time<br />
add <TIME> in format mm/dd/yyyy-hh:mm to the command. If you just use<br />
the drink-option it will default to <DRINK>=coffee or Jolt-coke<br />
depending on what the Geek or Hacker sees first and <AMOUNT>=2-3 cups<br />
or cans and <TIME>=now.<br />
<br />
--holiday, -away, -a <TIME><br />
will move the Geek or Hacker away from the net for <TIME> and give him<br />
a recreational pause. He will come back after <TIME> to work with more<br />
power and even better ideas. <TIME> here is explicit needed and has to<br />
be given in format of days or weeks, so 14d will be equal to 2w.<br />
<br />
--social_contact, -sc <PERSON> or <GROUP><br />
that moves the Geek or Hacker away from the PC for a short period where<br />
a <PERSON> or <GROUP> comes over to visit him or he needs to move to<br />
them. The period of time he is away can vary from several hours to some<br />
days, so be patient if this option is set.<br />
</pre><br />
|lang_skills=I speak German as my native lang and learned English for 8 and French for 5 years at School. ATM I'm not really used to talk French any more as I hadn't had a opportunity to do so for the last years... So will give my best to also help our french users, feel free to ask. For places to meet me see at Biography...<br />
|working_on= * working on [[flora]], the Funtoo Linux Overlay for User Contribution<br />
* writing howto for [[nginx]]<br />
* writing howto for [[wpa_supplicant]] <br />
* writing an ebuild for ConTeXt-minimals source based, atm a low priority project...<br />
|worked_on=* updated ebuild for dhcpcd-5.2.11<br />
* tested sandbox 2.5 with metro<br />
* starting to rewrite the quick install howto from Guy Fontaine to [[Funtoo_Quick_Install]]<br />
* update Funtoo install guide with quick install guide<br />
* writing guide for [[flora]], the Funtoo Linux Overlay for User Contribution<br />
}}<br />
== Boxes ==<br />
* mordor -- Homeserver (x86_64 architecture) ~funtoo<br />
* hobbigen -- Main PC (x86_64 architecture) ~funtoo will be there for a gentoo bug resolver<br />
* lorien -- Laptop (x86_64 architecture) ~funtoo HP Compaq 6820s (died 2011)<br />
* lorien -- Laptop (x86_64 architecture) ~funtoo experimental Dell Vostro 6830</div>Golodhrimhttps://www.funtoo.org/index.php?title=Package:Emacs&diff=2052Package:Emacs2013-01-11T23:48:58Z<p>Golodhrim: Undo revision 8585 by Golodhrim (talk)</p>
<hr />
<div>[[File:emacs-logo.png]]<br />
<br />
Emacs is a famous text editor, famous by its flexibility and extensibility. One manual describes it as "the extensible, customizable, self-documenting, real-time display editor".<br />
<br />
This page is designed to give users a good place to share their config and settings for a nice emacs setup.<br />
<br />
== installing emacs ==<br />
<br />
<pre><br />
emerge -avt emacs<br />
</pre><br />
<br />
for the standard gnu emacs and<br />
<br />
<pre><br />
emerge -avt xemacs<br />
</pre><br />
<br />
for the 1980 created fork of emacs, both should handle the same, while emacs on its own stands here for both. If you install additional extensions for both you might need to add <tt>app-emacs</tt> or <tt>app-xemacs</tt> to the package as there are two different versions for both.<br />
<br />
== What emacs is and what it is not ==<br />
<br />
(X)Emacs is primarily a text editor and not a word processor, it concentrates on manipulating any kind of text, rather than manipulating the font and look. It is client and GUI based, so can be used on local box in graphical environments with a GUI and remote on a server in a client mode. (X)Emacs provides commands for manipulate every kind of text and syntax highlighting.<br />
<br />
=== Customizability ===<br />
<br />
(X)Emacs is highly customizable in many ways through:<br />
<br />
* the <tt>customize</tt> extension, which allows settings of customized variables, such as color themes, graphical interface, etc. This part is intended for emacs beginners, who do not want to work with Emacs lisp code.<br />
* combine keystrokes to execute complex makros.<br />
* using Emacs Lisp. Designed for the emacs professional.<br />
<br />
=== Extensibility ===<br />
<br />
As a result of the above points, (X)Emacs behaviour can be easily definied to all text behavings without limit. Like some of the examples below show you:<br />
<br />
* AUCTeX, A suite for LaTeX and other TeX versions,<br />
* ERC, A Emacs IRC client,<br />
* ORG-mode, A Emacs PIM and Orga tool<br />
* Wanderlust, A highly flexible Mail tool for Emacs<br />
<br />
== User Configs ==<br />
=== golodhrim's config ===<br />
==== .emacs ====<br />
<br />
<pre><br />
;;;;;;;;;;;;;;;;;;;;;;<br />
;; General Settings ;;<br />
;;;;;;;;;;;;;;;;;;;;;;<br />
<br />
(setq emacs-root-dir (concat (getenv "HOME") "/em/"))<br />
<br />
(setq inhibit-startup-message t) ;; Suppress the startup message<br />
(setq standard-indent 4) ;; Default indent level is 3 chars<br />
(setq-default indent-tabs-mode nil) ;; Indent with spaces, not tabs<br />
<br />
(setq make-backup-files nil) ;; Enable backup files.<br />
(setq version-control nil) ;; Enable versioning with default values<br />
(setq backup-directory-alist (quote ((".*" . "~/.emacs_backups/")))) ;; Save all backup file in this directory.<br />
<br />
(line-number-mode 1) ;; Show line-number in the mode line<br />
(column-number-mode 1) ;; Show column-number in the mode line<br />
<br />
(setq auto-fill-mode 1) ;; Line wrap<br />
<br />
(set-default-font "Inconsolata-12")<br />
<br />
(setq browse-url-browser-function 'browse-url-generic<br />
browse-url-generic-program "google-chrome")<br />
<br />
(global-set-key (kbd "C-<prior>") 'previous-buffer)<br />
(global-set-key (kbd "C-<next>" ) 'next-buffer )<br />
<br />
<br />
(setq load-path (cons "~/.emacs.d/plugins" load-path))<br />
<br />
(setq global-font-lock-mode 1)<br />
<br />
(show-paren-mode 1)<br />
<br />
;;;;;;;;;;;;;;;;;;<br />
;; el-get setup ;;<br />
;;;;;;;;;;;;;;;;;;<br />
(add-to-list 'load-path "~/.emacs.d/el-get/el-get") <br />
(unless (require 'el-get nil t) <br />
(with-current-buffer <br />
(url-retrieve-synchronously "https://raw.github.com/golodhrim/el-get/master/el-get-install.el") <br />
(end-of-buffer) <br />
(eval-print-last-sexp)))<br />
<br />
(el-get 'sync)<br />
<br />
;;;;;;;;;;;;;;;<br />
;; mediawiki ;;<br />
;;;;;;;;;;;;;;;<br />
(require 'mediawiki)<br />
<br />
;;;;;;;;;;;;;;;;;;;;<br />
;; Org-mode stuff ;;<br />
;;;;;;;;;;;;;;;;;;;;<br />
<br />
;; Tell emacs where org-mode is<br />
;;(setq load-path (cons "/usr/share/emacs/site-lisp/org-mode/" load-path))<br />
;;(setq load-path (cons "/usr/share/emacs/site-lisp/org-mode/contrib/" load-path))<br />
(require 'org-install) ;; Tell emacs to use org-mode<br />
(add-to-list 'auto-mode-alist '("\\.org$" . org-mode)) ;; Turn on org-mode for all *.org files<br />
<br />
;; Some key sequences<br />
(define-key global-map "\C-cl" 'org-store-link) <br />
(define-key global-map "\C-ca" 'org-agenda)<br />
(global-set-key [f9] 'org-archive-subtree-default)<br />
<br />
(setq org-log-done t) ;; I have no idea what this does, it was in the manual -- think it controls whether or not to log time completed for tasks<br />
<br />
(setq org-directory "~/notes")<br />
<br />
;; Files that should be included in agenda views:<br />
(setq org-agenda-files (list "~/notes/business.org"<br />
"~/notes/personal.org" <br />
"~/notes/projects/"<br />
"~/notes/projects/writing/"))<br />
<br />
(setq org-todo-keywords '((type "TODO" "Postponed" "Upcoming" "Doing" "|" "DONE(#)"))) ;; TODO workflows<br />
<br />
(setq org-tag-alist '(("work" . ?k) ("personal" . ?p) ("organization" . ?o) ("writing" . ?w) ("code" . ?c) ("blog" . ?b) ("funtoo" . ?f) ("social" . ?s))) ;; Most-used tags, with shortcuts<br />
<br />
;; Capture stuff<br />
(setq org-default-notes-file "~/.org/capture.org")<br />
(define-key global-map "\C-cc" 'org-capture)<br />
(setq org-refile-targets '((org-agenda-files :level . 1)(org-agenda-files :level . 2)))<br />
(setq org-refile-use-outline-path 'file)<br />
<br />
(setq org-capture-templates<br />
'(("t" "Todo" entry (file+headline "~/.org/capture.org" "Tasks")<br />
"- TODO %?\n %i\n %a")<br />
("j" "Journal" entry (file+datetree "~/.org/journal.org")<br />
"- %?\nEntered on %U\n %i\n %a")))<br />
<br />
(setq org-mobile-directory "~/Dropbox/MobileOrg")<br />
(setq org-mobile-use-encryption)<br />
(setq org-mobile-use-encryption-password "PASSWORD")<br />
(setq org-mobile-inbox-for-pull "~/notes/mobileorg/inbox.org")<br />
<br />
;;;;;;;;;;;;;;;;;;;<br />
;; Markdown Mode ;;<br />
;;;;;;;;;;;;;;;;;;;<br />
<br />
(require 'markdown-mode)<br />
(add-to-list 'auto-mode-alist '("\\.markdown$" . markdown-mode))<br />
(add-to-list 'auto-mode-alist '("\\.md$" . markdown-mode))<br />
<br />
;;;;;;;;;;;;;;;;<br />
;; Python IDE ;;<br />
;;;;;;;;;;;;;;;;<br />
(c-add-style<br />
"python-new"<br />
'((indent-tabs-mode . nil)<br />
(fill-column . 78)<br />
(c-basic-offset . 4)<br />
(c-offsets-alist . ((substatement-open . 0)<br />
(inextern-lang . 0)<br />
(arglist-intro . +)<br />
(knr-argdecl-intro . +)))<br />
(c-hanging-braces-alist . ((brace-list-open)<br />
(brace-list-intro)<br />
(brace-list-close)<br />
(brace-entry-open)<br />
(substatement-open after)<br />
(block-close . c-snug-do-while)))<br />
(c-block-comment-prefix . "* "))<br />
)<br />
<br />
;; This is a very crude hook that auto-selects the C style depending on<br />
;; whether it finds a line starting with tab in the first 3000 characters<br />
;; in the file<br />
(defun c-select-style ()<br />
(save-excursion<br />
(if (re-search-forward "^\t" 3000 t)<br />
(c-set-style "python")<br />
(c-set-style "python-new"))))<br />
(add-hook 'c-mode-hook 'c-select-style)<br />
<br />
;;;;;;;;;;;;<br />
;; Django ;;<br />
;;;;;;;;;;;;<br />
(yas/initialize)<br />
(add-to-list 'load-path "~/.emacs.d/el-get/django-mode/")<br />
(require 'django-html-mode)<br />
(require 'django-mode)<br />
(yas/load-directory "~/.emacs.d/el-get/django-mode/snippets")<br />
(add-to-list 'auto-mode-alist '("\\.djhtml$" . django-html-mode))<br />
<br />
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;<br />
;; Document Engineering (AUCTeX + ConTeXt) ;;<br />
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;<br />
(load "auctex.el" nil t t)<br />
(load "preview-latex.el" nil t t)<br />
<br />
(setq TeX-auto-save 1)<br />
(setq TeX-parse-self 1)<br />
(setq TeX-auto-untabify 1)<br />
(setq TeX-display-help 1)<br />
(setq TeX-save-query nil)<br />
(setq TeX-clean-confirm nil)<br />
(setq-default TeX-master nil)<br />
<br />
(add-hook 'TeX-mode-hook (lambda () (TeX-fold-mode 1)))<br />
(add-hook 'TeX-mode-hook (lambda () (TeX-source-specials-mode 1)))<br />
(add-hook 'TeX-mode-hook (lambda () (TeX-toggle-debug-bad-boxes)))<br />
(add-hook 'TeX-mode-hook (lambda () (TeX-toggle-debug-warnings)))<br />
(add-hook 'TeX-mode-hook (lambda () (outline-minor-mode)))<br />
(add-hook 'TeX-mode-hook (lambda () (abbrev-mode t)))<br />
(add-hook 'TeX-mode-hook (lambda () (auto-fill-mode 1)))<br />
<br />
(add-hook 'TeX-mode-hook 'LaTeX-math-mode)<br />
<br />
(autoload 'etexshow "etexshow" "Browser for ConTeXt commands." t)<br />
<br />
(setq etexshow-xml-files-alist<br />
`((,(concat emacs-root-dir "libs/etexshow/cont-en.xml") .<br />
,(concat "/tmp/cont-en.cache"))))<br />
<br />
(setq etexshow-comment-file<br />
(concat emacs-root-dir "libs/etexshow/cont-en-comments.xml"))<br />
<br />
(setq TeX-PDF-mode 1)<br />
(setq revert-without-query '(".+pdf$"))<br />
(add-hook 'doc-view-mode-hook 'auto-revert-mode)<br />
<br />
;;;;;;;;;;<br />
;; bbdb ;;<br />
;;;;;;;;;;<br />
(setq bbdb-file "~/.emacs.d/.bbdb")<br />
(require 'bbdb)<br />
(bbdb-initialize)<br />
(setq<br />
bbdb-offer-save 1 ;; 1 means save-without-asking<br />
bbdb-use-pop-up t ;; allow popups for addresses<br />
bbdb-electric-p t ;; be disposable with SPC<br />
bbdb-popup-target-lines 1 ;; very small<br />
bbdb-dwim-net-address-allow-redundancy t ;; always use full name<br />
bbdb-quiet-about-name-mismatches 2 ;; show name-mismatches 2 secs<br />
bbdb-always-add-address t ;; add new addresses to existing...<br />
;; ...contacts automatically<br />
bbdb-canonicalize-redundant-nets-p t ;; x@foo.bar.cx => x@bar.cx<br />
bbdb-completion-type nil ;; complete on anything<br />
bbdb-complete-name-allow-cycling t ;; cycle through matches<br />
;; this only works partially<br />
bbdb-message-caching-enabled t ;; be fast<br />
bbdb-use-alternate-names t ;; use AKA<br />
bbdb-elided-display t ;; single-line addresses<br />
;; auto-create addresses from mail<br />
bbdb/mail-auto-create-p 'bbdb-ignore-some-messages-hook<br />
bbdb-ignore-some-messages-alist ;; don't ask about fake addresses<br />
;; NOTE: there can be only one entry per header (such as To, From)<br />
;; http://flex.ee.uec.ac.jp/texi/bbdb/bbdb_11.html<br />
'(( "From" . "no.?reply\\|DAEMON\\|daemon\\|facebookmail\\|twitter")))<br />
<br />
;;;;;;;;;;;;;;;;;<br />
;; Jabber Mode ;;<br />
;;;;;;;;;;;;;;;;;<br />
<br />
(require 'jabber-autoloads)<br />
(setq jabber-account-list '(<br />
("USER@jabber-server.tld"<br />
(:password . "PASSWORD")<br />
)<br />
)<br />
)<br />
(setq<br />
jabber-history-enabled t<br />
jabber-use-global-history nil<br />
jabber-backlog-number 40<br />
jabber-backlog-days 30<br />
)<br />
<br />
(add-hook 'jabber-chat-mode-hook 'goto-address)<br />
<br />
(load "~/.emacs.d/plugins/autosmiley.el")<br />
(require 'autosmiley)<br />
(add-hook 'jabber-chat-mode-hook 'autosmiley-mode)<br />
<br />
(defvar libnotify-program "/usr/bin/notify-send")<br />
<br />
(defun notify-send (title message)<br />
(start-process "notify" " notify"<br />
libnotify-program "--expire-time=4000" title message))<br />
<br />
(defun libnotify-jabber-notify (from buf text proposed-alert)<br />
"(jabber.el hook) Notify of new Jabber chat messages via libnotify"<br />
(when (or jabber-message-alert-same-buffer<br />
(not (memq (selected-window) (get-buffer-window-list buf))))<br />
(if (jabber-muc-sender-p from)<br />
(notify-send (format "(PM) %s"<br />
(jabber-jid-displayname (jabber-jid-user from)))<br />
(format "%s: %s" (jabber-jid-resource from) text)))<br />
(notify-send (format "%s" (jabber-jid-displayname from))<br />
text)))<br />
<br />
(add-hook 'jabber-alert-message-hooks 'libnotify-jabber-notify)<br />
<br />
(defun jabber-visit-history (jid)<br />
"Visit jabber history with JID in a new buffer.<br />
<br />
Performs well only for small files. Expect to wait a few seconds<br />
for large histories. Adapted from `jabber-chat-create-buffer'."<br />
(interactive (list (jabber-read-jid-completing "JID: ")))<br />
(let ((buffer (generate-new-buffer (format "*-jabber-history-%s-*"<br />
(jabber-jid-displayname jid)))))<br />
(switch-to-buffer buffer)<br />
(make-local-variable 'jabber-chat-ewoc)<br />
(setq jabber-chat-ewoc (ewoc-create #'jabber-chat-pp))<br />
(mapc 'jabber-chat-insert-backlog-entry<br />
(nreverse (jabber-history-query nil nil t t "."<br />
(jabber-history-filename jid))))<br />
(view-mode)))<br />
<br />
;;;;;;;;;;<br />
;; EMMS ;;<br />
;;;;;;;;;;<br />
(require 'emms-setup)<br />
(emms-devel)<br />
(emms-default-players)<br />
<br />
;;;;;;;;;<br />
;; ERC ;;<br />
;;;;;;;;;<br />
(require 'erc)<br />
(require 'erc-extension)<br />
(require 'erc-services)<br />
(require 'erc-tex)<br />
(require 'tls)<br />
(require 'erc-nicklist)<br />
<br />
(and<br />
(require 'erc-highlight-nicknames)<br />
(add-to-list 'erc-modules 'highlight-nicknames)<br />
(erc-update-modules))<br />
<br />
(erc-services-mode 1)<br />
<br />
(setq tls-program '("openssl s_client -connect %h:%p -no_ssl2 -ign_eof<br />
-CAfile /home/USER/.ssl/USER.pem <br />
-cert /home/USER/.ssl/USER.pem"<br />
"gnutls-cli --priority secure256<br />
--x509cafile /home/USER/.ssl/USER.pem <br />
--x509certfile /home/USER/.ssl/USER.pem -p %p %h"<br />
"gnutls-cli --priority secure256 -p %p %h"))<br />
<br />
(autoload 'erc-nick-notify-mode "erc-nick-notify" "Minor mode that calls `erc-nick-notify-cmd' when his nick gets mentioned in an erc channel" t)<br />
(eval-after-load 'erc '(erc-nick-notify-mode t))<br />
(defun irc-erc ()<br />
"Fire up IRC."<br />
(interactive)<br />
(erc-tls :server "chat.freenode.net" :port 7000 :nick "USER" :full-name "FULL NAME" :password "PASSWORD"))<br />
<br />
(setq erc-autojoin-channels-alist '(("freenode.net" "#frogandowl" "#funtoo" "#funtoo-quebec" "#syntazia" "#context" "#nginx" "#emacs" "#openvswitch")))<br />
(setq erc-log-channels-directory "~/.erc/logs/")<br />
(setq erc-log-insert-log-on-open nil)<br />
(setq erc-save-buffer-on-part nil<br />
erc-save-buffer-queries-on-quit nil<br />
erc-log-write-after-send t<br />
erc-log-write-after-insert t)<br />
<br />
(require 'smiley)<br />
(add-to-list 'smiley-regexp-alist '("\\(:-?]\\)\\W" 1 "forced"))<br />
(add-to-list 'smiley-regexp-alist '("\\s-\\(:-?/\\)\\W" 1 "wry"))<br />
(add-to-list 'smiley-regexp-alist '("\\(:-?(\\)\\W" 1 "sad"))<br />
(add-to-list 'smiley-regexp-alist '("\\((-?:\\)\\W" 1 "reverse-smile"))<br />
(add-to-list 'smiley-regexp-alist '("\\(:-?D\\)\\W" 1 "grin"))<br />
(add-to-list 'smiley-regexp-alist '("\\(:-?P\\)\\W" 1 "poke"))<br />
<br />
;; (setq smiley-cached-regexp-alist nil)<br />
;; (smiley-update-cache)<br />
<br />
;;;;;;;;;;;;;;;;<br />
;; Wanderlust ;;<br />
;;;;;;;;;;;;;;;;<br />
(autoload 'wl "wl" "Wanderlust" t)<br />
<br />
;;;;;;;;;;;;;;;<br />
;; mailcrypt ;;<br />
;;;;;;;;;;;;;;;<br />
(require 'mailcrypt)<br />
(add-hook 'wl-summary-mode-hook 'mc-install-read-mode)<br />
(add-hook 'wl-mail-setup-hook 'mc-install-write-mode)<br />
<br />
(defun mc-wl-verify-signature ()<br />
(interactive)<br />
(save-window-excursion<br />
(wl-summary-jump-to-current-message)<br />
(mc-verify)))<br />
<br />
(defun mc-wl-decrypt-message ()<br />
(interactive)<br />
(save-window-excursion<br />
(wl-summary-jump-to-current-message)<br />
(let ((inhibit-read-only t))<br />
(mc-decrypt))))<br />
<br />
(eval-after-load "mailcrypt"<br />
'(setq mc-modes-alist<br />
(append<br />
(quote<br />
((wl-draft-mode (encrypt . mc-encrypt-message)<br />
(sign . mc-sign-message))<br />
(wl-summary-mode (decrypt . mc-wl-decrypt-message)<br />
(verify . mc-wl-verify-signature))))<br />
mc-modes-alist)))<br />
<br />
;;;;;;;;;;;;;;;;;;;;;<br />
;; notify function ;;<br />
;;;;;;;;;;;;;;;;;;;;;<br />
(defun djcb-popup (title msg &optional icon sound)<br />
"Show a popup if we're on X, or echo it otherwise; TITLE is the title of the message, MSG is the context. Optionally, you can provide an ICON and a sound to be played"<br />
(interactive)<br />
(when sound (shell-command<br />
(concat "mplayer2 -really-quiet " sound " 2> /dev/null")))<br />
(if (eq window-system 'x)<br />
(shell-command (concat "notify-send "<br />
<br />
(if icon (concat "-i " icon) "")<br />
" '" title "' '" msg "'"))<br />
;; text only version<br />
(message (concat title ": " msg))))<br />
<br />
;; the appointment notification facility<br />
(setq<br />
appt-message-warning-time 15 ;; warn 15 min in advance<br />
appt-display-mode-line t ;; show in the modeline<br />
appt-display-format 'window) ;; usr our func<br />
(appt-activate t) ;; active appt (appointment notification)<br />
(display-time)<br />
<br />
;; update appt each time agenda opened<br />
(add-hook 'org-finalize-agenda-hook 'org-agenda-to-appt)<br />
<br />
;; our little facade-function for djcb-popup<br />
(defun djcb-appt-display (min-to-app new-time msg)<br />
(djcb-popup (format "Appointment in %s minute(s)" min-to-app) msg<br />
"/usr/share/icons/gnome/32x32/status/appointment-soon.png"<br />
"/usr/share/sounds/purple/alert.wav"))<br />
(setq appt-disp-window-function (function djcb-appt-display))<br />
<br />
;;;;;;;;;;;;;;;;;;;;;;;;;;<br />
;; Custom Variable sets ;;<br />
;;;;;;;;;;;;;;;;;;;;;;;;;;<br />
(custom-set-variables<br />
;; custom-set-variables was added by Custom.<br />
;; If you edit it by hand, you could mess it up, so be careful.<br />
;; Your init file should contain only one such instance.<br />
;; If there is more than one, they won't work right.<br />
'(TeX-command-list (quote (("TeX" "%(PDF)%(tex) %`%S%(PDFout)%(mode)%' %t" TeX-run-TeX nil (plain-tex-mode texinfo-mode ams-tex-mode) :help "Run plain TeX") ("LaTeX" "%`%l%(mode)%' %t" TeX-run-TeX nil (latex-mode doctex-mode) :help "Run LaTeX") ("Makeinfo" "makeinfo %t" TeX-run-compile nil (texinfo-mode) :help "Run Makeinfo with Info output") ("Makeinfo HTML" "makeinfo --html %t" TeX-run-compile nil (texinfo-mode) :help "Run Makeinfo with HTML output") ("AmSTeX" "%(PDF)amstex %`%S%(PDFout)%(mode)%' %t" TeX-run-TeX nil (ams-tex-mode) :help "Run AMSTeX") ("ConTeXt MKIV" "context %t" TeX-run-TeX nil (context-mode) :help "Run ConTeXt MKIV") ("ConTeXt" "texexec --once --texutil %(execopts)%t" TeX-run-TeX nil (context-mode) :help "Run ConTeXt once") ("ConTeXt Full" "texexec %(execopts)%t" TeX-run-TeX nil (context-mode) :help "Run ConTeXt until completion") ("BibTeX" "bibtex %s" TeX-run-BibTeX nil t :help "Run BibTeX") ("View" "%V" TeX-run-discard-or-function t t :help "Run Viewer") ("Print" "%p" TeX-run-command t t :help "Print the file") ("Queue" "%q" TeX-run-background nil t :help "View the printer queue" :visible TeX-queue-command) ("File" "%(o?)dvips %d -o %f " TeX-run-command t t :help "Generate PostScript file") ("Index" "makeindex %s" TeX-run-command nil t :help "Create index file") ("Check" "lacheck %s" TeX-run-compile nil (latex-mode) :help "Check LaTeX file for correctness") ("Spell" "(TeX-ispell-document \"\")" TeX-run-function nil t :help "Spell-check the document") ("Clean" "TeX-clean" TeX-run-function nil t :help "Delete generated intermediate files") ("Clean All" "(TeX-clean t)" TeX-run-function nil t :help "Delete generated intermediate and output files") ("Other" "" TeX-run-command t t :help "Run an arbitrary command"))))<br />
'(column-number-mode t)<br />
'(erc-modules (quote (autojoin bbdb button completion fill irccontrols list log match menu move-to-prompt netsplit networks noncommands readonly ring services smiley stamp spelling track)))<br />
'(mediawiki-site-alist (quote (("Funtoo" "http://www.funtoo.org/" "USER" "PASSWORD" "")))))<br />
(custom-set-faces<br />
;; custom-set-faces was added by Custom.<br />
;; If you edit it by hand, you could mess it up, so be careful.<br />
;; Your init file should contain only one such instance.<br />
;; If there is more than one, they won't work right.<br />
)<br />
<br />
;;;;;;;;;;;;;;;;;;<br />
;; Color-Themes ;;<br />
;;;;;;;;;;;;;;;;;;<br />
;;(add-to-list 'load-path "/usr/share/emacs/site-lisp/color-theme/color-theme.el")<br />
;;(add-to-list 'load-path "~/.emacs.d/themes/")<br />
(require 'color-theme)<br />
(color-theme-initialize)<br />
;;(color-theme-subtle-hacker)<br />
(color-theme-twilight)<br />
;;(eval-after-load "color-theme"<br />
;; '(progn<br />
;; (color-theme-initialize)<br />
;; (require 'color-theme-citrus)<br />
;; (require 'color-theme-candy)<br />
;; (require 'color-theme-autumn-leaves)<br />
;; (require 'color-theme-inthedark)<br />
;; (require 'color-theme-marine)<br />
;; (require 'color-theme-october)<br />
;; (require 'color-theme-eatyourgreens)<br />
;; (require 'color-theme-august)<br />
;; (require 'color-theme-saddle-2)<br />
;; (color-theme-saddle-2)))<br />
;; (color-theme-subtle-hacker)))<br />
<br />
(setq css-indent-offset 2)<br />
</pre><br />
<br />
==== .wl ====<br />
<br />
<pre><br />
;; load bbdb support<br />
(require 'bbdb-wl)<br />
(bbdb-wl-setup)<br />
<br />
;; setup from where to get addresses<br />
(setq bbdb-wl-folder-regexp "^\.INBOX|^\.inbox|^\.Sent|^\.sent|^\.\[IMAPS\]\\Sent")<br />
<br />
;; define keybinding<br />
(define-key wl-draft-mode-map (kbd "<C-tab>") 'bbdb-complete-name)<br />
<br />
;; set multiple e-mail addresses<br />
(setq wl-user-mail-address-list (quote ("User@googlemail.com" "USER@own-server.tld")))<br />
<br />
;; handle ("d") mark<br />
;; remove = instant removal (same as "D"), thrash = move to wl-trash-folder<br />
;; string = move to string<br />
(setq wl-dispose-folder-alist<br />
'(<br />
("\.\*googlemail\\.com" "%[Imap]/Trash:"User@googlemail.com"/clear@imap.gmail.com:993!")<br />
("\.\*@own\-\server\\.tld" "%INBOX.Trash:"USER"/clear@imap.own-server.tld")<br />
))<br />
<br />
;; notify hook<br />
(add-hook 'wl-biff-notify-hook<br />
(lambda()<br />
(djcb-popup "Wanderlust" "You have new mail!"<br />
"/usr/share/icons/gnome/32x32/status/mail-unread.png"<br />
"/usr/share/sounds/purple/alert.wav")))<br />
<br />
;; timer settings<br />
(setq<br />
wl-biff-check-interval 30 ;; check every 30 seconds<br />
wl-biff-use-idle-timer t) ;; in the background<br />
<br />
;; Name of top-folder, default "Desktop"<br />
(setq wl-folder-desktop-name "e-Mail")<br />
<br />
;; select correct email address when we _start_ writing a draft.<br />
(add-hook 'wl-mail-setup-hook 'wl-draft-config-exec)<br />
<br />
(setq wl-draft-config-alist<br />
'(<br />
((string-match "googlemail.com" wl-draft-parent-folder)<br />
(template . "User"))<br />
((string-match "own-server.tld" wl-draft-parent-folder)<br />
(template . "USER"))<br />
))<br />
<br />
;; choose template with C-c C-j<br />
(setq wl-template-alist<br />
'(("User"<br />
(wl-from . "Full Name <User@googlemail.com>")<br />
("From" . wl-from)<br />
(wl-smtp-posting-user . "User")<br />
(wl-smtp-posting-server . "smtp.gmail.com")<br />
(wl-smtp-authenticate-type . "plain")<br />
(wl-smtp-connection-type . 'starttls)<br />
(wl-smtp-posting-port . 587)<br />
(wl-local-domain . "googlemail.com")<br />
(wl-message-id-domain . "smtp.gmail.com")<br />
<br />
(wl-fcc . "%[IMAPS]/Sent:\"User@googlemail.com\"/clear@imap.gmail.com:993!")<br />
(wl-draft-folder . "%[IMAPS]/Draft:\"User@googlemail.com\"/clear@imap.gmail.com:993!")<br />
)<br />
("USER"<br />
(wl-from . "Full Name <USER@own-server.tld>")<br />
("From" . wl-from)<br />
(wl-smtp-posting-user . "USER")<br />
(wl-smtp-posting-server . "smtp.own-server.tld")<br />
(wl-local-domain . "own-server.tld")<br />
<br />
(wl-fcc "%INBOX.Sent:USER/digest-md5@imap.own-server.tld:143")<br />
(wl-draft-folder "%INBOX.Drafts:USER/digest-md5@imap.own-server.tld:143")<br />
)<br />
)<br />
)<br />
<br />
(define-key wl-template-mode-map (kbd "<right>") 'wl-template-next)<br />
(define-key wl-template-mode-map (kbd "<left>") 'wl-template-prev)<br />
<br />
(setq wl-default-spec "%")<br />
<br />
(setq wl-fcc-force-as-read t)<br />
(setq wl-auto-save-drafts-interval nil)<br />
</pre><br />
<br />
==== .folders ====<br />
<br />
<pre><br />
User@googlemail{<br />
%INBOX:"User@googlemail.com"/clear@imap.gmail.com:993! "Inbox"<br />
[IMAPS-gmail]{<br />
%[IMAPS]/Sent:"User@googlemail.com"/clear@imap.gmail.com:993! "Sent"<br />
%[IMAPS]/Draft:"User@googlemail.com"/clear@imap.gmail.com:993! "Draft"<br />
%[IMAPS]/Spam:"User@googlemail.com"/clear@imap.gmail.com:993! "Spam"<br />
%[IMAPS]/Trash:"User@googlemail.com"/clear@imap.gmail.com:993! "Trash"<br />
}<br />
}<br />
USER@own-server.tld{<br />
%INBOX:USER/digest-md5@imap.own-server.tld "Inbox"<br />
%INBOX.Sent:USER/digest-md5@imap.own-server.tld "Sent"<br />
%INBOX.Drafts:USER/digest-md5@imap.own-server.tld "Drafts"<br />
}<br />
</pre><br />
<br />
[[Category:HOWTO]]<br />
[[Category:Featured]]</div>Golodhrimhttps://www.funtoo.org/index.php?title=Talk:Welcome&diff=2259Talk:Welcome2013-01-10T23:44:04Z<p>Golodhrim: /* Takeing out twitter as linking to car insurance sites with only red dots */ new section</p>
<hr />
<div>Hello. And Bye.<br />
<br />
== Takeing out twitter as linking to car insurance sites with only red dots ==<br />
<br />
This is the outtaken part of the site as it shows only red dots and links by them to an car insurance page<br />
<br />
<pre><br />
<br />
<br />
=== Latest Funtoo News from Twitter ===<br />
<br />
<div class="tweets"><br />
<ul><br />
<feed entries=8 url="http://search.twitter.com/search.atom?q=from%3Afuntoo"><br />
<li>[{PERMALINK} <nowiki>{TITLE}</nowiki>]<br />
</feed><br />
</ul><br />
</div><br />
</pre></div>Golodhrimhttps://www.funtoo.org/index.php?title=Open_vSwitch&diff=2093Open vSwitch2012-04-26T00:41:13Z<p>Golodhrim: update</p>
<hr />
<div>== Open vSwitch ==<br />
<br />
Open vSwitch is a production quality, multilayer virtual switch licensed under the open source Apache 2.0 license. It is designed to enable massive network automation through programmatic extension, while still supporting standard management interfaces and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed to support distribution across multiple physical servers similar to VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V.<br />
<br />
=== Features ===<br />
<br />
The current stablerelease of Open vSwitch (version 1.4.0) supports the following features:<br />
<br />
* Visibility into inter-VM communication via NetFlow, sFlow(R), SPAN, RSPAN, and GRE-tunneled mirrors<br />
* LACP (IEEE 802.1AX-2008)<br />
* Standard 802.1Q VLAN model with trunking<br />
* A subset of 802.1ag CCM link monitoring<br />
* STP (IEEE 802.1D-1998)<br />
* Fine-grained min/max rate QoS<br />
* Support for HFSC qdisc<br />
* Per VM interface traffic policing<br />
* NIC bonding with source-MAC load balancing, active backup, and L4 hashing<br />
* OpenFlow protocol support (including many extensions for virtualization)<br />
* IPv6 support<br />
* Multiple tunneling protocols (Ethernet over GRE, CAPWAP, IPsec, GRE over IPsec)<br />
* Remote configuration protocol with local python bindings<br />
* Compatibility layer for the Linux bridging code<br />
* Kernel and user-space forwarding engine options<br />
* Multi-table forwarding pipeline with flow-caching engine<br />
* Forwarding layer abstraction to ease porting to new software and hardware platforms<br />
<br />
== Configuring Open vSwitch ==<br />
<br />
Open vSwitch needs to be compiled with the kernel modules (modules USE flag) for kernel versions <3.3, since 3.3.0 it is included in the kernel as a module named "Open vSwitch" and can be found in kernel at '''Networking Support -> Networking Options -> Open vSwitch'''. Then just emerge openvswitch with<br />
<br />
<pre><br />
# emerge -avt openvswitch<br />
</pre><br />
<br />
== Using Open vSwitch ==<br />
<br />
These Configs are taken from the Open vSwitch website at http://openvswitch.org and adjusted to funtoo's needs<br />
<br />
=== VLANs ===<br />
<br />
==== Setup ====<br />
<br />
* Two Physical Networks<br />
** Data Network: Eternet network for VM data traffic, which will carry VLAN tagged traffic between VMs. Your physical switch(es) must be capable of forwarding VLAN tagged traffic and the physical switch ports should be VLAN trunks (Usually this is default behavior. Configuring your physical switching hardware is beyond the scope of this document).<br />
** Management Network: This network is not strictly required, but it is a simple way to give the physical host an IP address for remote access, since an IP address cannot be assigned directly to eth0.<br />
* Two Physical Hosts<br />
Host1, Host2. Both hosts are running Open vSwitch. Each host has two NICs:<br />
** eth0 is connected to the Data Network. No IP address can be assigned on eth0<br />
** eth1 is connected to the Management Network (if necessary). eth1 has an IP address that is used to reach the physical host for management.<br />
* Four VMs<br />
VM1, VM2 run on Host1. VM3, VM4 run on Host2.<br />
Each VM has a single interface that appears as a Linux device (e.g., "tap0") on the physical host. (Note: for Xen/XenServer, VM interfaces appear as Linux devices with names like "vif1.0").<br />
[[image:2host-4vm.png]]<br />
<br />
==== Goal ====<br />
<br />
Isolate VMs using VLANs on the Data Network.<br />
VLAN1: VM1, VM3<br />
VLAN2: VM2, VM4<br />
<br />
==== Configuration ====<br />
Perform the following configuration on Host1:<br />
# Create an OVS bridge <pre>ovs-vsctl add-br br0</pre><br />
# Add eth0 to the bridge (by default, all OVS ports are VLAN trunks, so eth0 will pass all VLANs) <pre>ovs-vsctl add-port br0 eth0</pre><br />
# Add VM1 as an "access port" on VLAN1 <pre>ovs-vsctl add-port br0 tap0 tag=1</pre><br />
# Add VM2 on VLAN2 <pre>ovs-vsctl add-port br0 tap0 tag=2</pre><br />
On Host2, repeat the same configuration to setup a bridge with eth0 as a trunk <pre>ovs-vsctl add-br br0<br />
ovs-vsctl add-port br0 eth0</pre><br />
# Add VM3 to VLAN1 <pre>ovs-vsctl add-port br0 tap0 tag=1</pre><br />
# Add VM4 to VLAN2 <pre>ovs-vsctl add-port br0 tap0 tag=2</pre><br />
<br />
=== sFlow ===<br />
This will setup a VM traffic Monitor using sFlow.<br />
==== Setup ====<br />
* Two Physical Networks<br />
** Data Network: Eternet network for VM data traffic.<br />
** Management Network: This network must exist, as it is used to send sFlow data from the agent to the remote collector.<br />
* Two Physical Hosts<br />
** Host1 runs Open vSwitch and has two NICs:<br />
*** eth0 is connected to the Data Network. No IP address can be assigned on eth0.<br />
*** eth1 is connected to the Management Network. eth1 has an IP address for management traffic (including sFlow).<br />
** Monitoring Host can be any computer that run the sFlow collector. Here we use [http://www.inmon.com/products/sFlowTrend.php sFlowTrend], a free sFlow collector, a simple cross-platform Java tool. Other sFlow collectors should work equally well.<br />
*** eth0 is connected to the Management Netowrk: eth0 has an IP address that can reach Host1.<br />
* Two VMs<br />
VM1, VM2 run on Host1. Each VM has a single interface that appears as a Linux device (e.g., "tap0") on the physical host. (Note: same for Xen/XenServer as in the VLANs section.)<br />
[[image:sflow-setup.png]]<br />
<br />
==== Goal ====<br />
Monitor traffic sent to/from VM1 and VM2 on the Data network using an sFlow collector.<br />
<br />
==== Configuration ====<br />
Define the following configuration values in your shell environment. The default port for sFlowTrend is 6343. You will want to set your own IP address for the collector in the place of 10.0.0.1. Setting the AGENT_IP value to eth1 indicates that the sFlow agent should send traffic from eth1's IP address. The other values indicate settings regarding the frequency and type of packet sampling that sFlow should perform.<br />
<pre><br />
# export COLLECTOR_IP=10.0.0.1<br />
# export COLLECTOR_PORT=6343<br />
# export AGENT_IP=eth1<br />
# export HEADER_BYTES=128<br />
# export SAMPLING_N=64<br />
# export POLLING_SECS=10<br />
</pre><br />
Run the following command to create an sFlow configuration and attach it to bridge br0:<br />
<pre><br />
ovs-vsctl -- -id=@sflow create sflow agent=${AGENT_IP} target=\”${COLLECTOR_IP}:${COLLECTOR_PORT}\” header=${HEADER_BYTES} sampling=${SAMPLING_N} polling=${POLLING_SECS} — set bridge br0 sflow=@sflow<br />
</pre><br />
That is all. To configure sFlow on additional bridges, just replace "br0" in the above command with a different bridge name.<br />
To remove sFlow configuration from a bridge (in this case, 'br0'), run:<br />
<pre><br />
ovs-vsctl remove bridge br0 sflow $SFLOWUUID<br />
</pre><br />
To see all current sets of sFlow configuration parameters, run:<br />
<pre><br />
ovs-vsctl list sflow<br />
</pre><br />
<br />
=== QoS Rate-limiting ===</div>Golodhrimhttps://www.funtoo.org/index.php?title=Template:Shell&diff=1583Template:Shell2011-08-19T00:01:17Z<p>Golodhrim: </p>
<hr />
<div>{|width="100%" cellpadding=0 cellspacing=0 style="margin: .5em 0; background-color: #D8CCFF; border: solid 1px #000066;" <br />
{{#if: {{{Desc|}}} | {{!}} valign="top" style="background-color: #0080FF; border-bottom: 1px solid #000066; font-size: 0.9em" {{!}} '''Description:''' {{{Desc}}}<br />
{{!}}- <br />
{{!}} style="padding: 0 0.5em; color: #000000" colspan="2" {{!}} {{{Input}}} | {{!}} style="padding: 0 0.5em; color: #000000" {{!}} {{{Input}}} }}<br />
|}<noinclude>{{documentation}}</noinclude></div>Golodhrimhttps://www.funtoo.org/index.php?title=Template:Shell/Doc&diff=1584Template:Shell/Doc2011-08-18T23:59:14Z<p>Golodhrim: </p>
<hr />
<div>Example 1:<br />
<pre><br />
{{shell<br />
| Desc = Descriptiontext<br />
| Input = # command to run<br />
Output of command<br><br />
<font color=#ff0000;>Alert!</font><br />
}}<br />
</pre><br />
<br />
Will produce:<br />
{{shell<br />
| Desc = Descriptiontext<br />
| Input = # command to run<br />
Output of command<br><br />
<font color=#ff0000;>Alert!</font><br />
}}<br />
<br />
and Example 2:<br />
<pre><br />
{{shell<br />
| Input = # command to run<br />
Output of command<br><br />
<font color=#ff0000;>Alert!</font><br />
}}<br />
</pre><br />
<br />
Will produce:<br />
{{shell<br />
| Input = # command to run<br />
Output of command<br><br />
<font color=#ff0000;>Alert!</font><br />
}}<br />
<br />
and Example 3:<br />
<pre><br />
{{shell<br />
| Desc =<br />
| Input = # command to run<br />
Output of command<br><br />
<font color=#ff0000;>Alert!</font><br />
}}<br />
</pre><br />
<br />
Will produce:<br />
{{shell<br />
| Desc =<br />
| Input = # command to run<br />
Output of command<br><br />
<font color=#ff0000;>Alert!</font><br />
}}<br />
<br />
Please be aware if you are using | inside the Input String it wouldn't work and break you need to replace | with {{!}} and inside the input it is saver to use clean HTML code. :)<br />
<br />
<noinclude>[[Category:Template Documentation]]</noinclude></div>Golodhrimhttps://www.funtoo.org/index.php?title=Sed_by_Example,_Part_1&diff=1110Sed by Example, Part 12011-06-29T17:36:56Z<p>Golodhrim: *** SPAM *** Undo revision 18773 by SarahBenson (talk) USER will be baned... :)</p>
<hr />
<div>== Get to know the powerful UNIX editor ==<br />
<br />
=== Pick an editor ===<br />
In the UNIX world, we have a lot of options when it comes to editing files. Think of it -- vi, emacs, and jed come to mind, as well as many others. We all have our favorite editor (along with our favorite keybindings) that we have come to know and love. With our trusty editor, we are ready to tackle any number of UNIX-related administration or programming tasks with ease.<br />
<br />
While interactive editors are great, they do have limitations. Though their interactive nature can be a strength, it can also be a weakness. Consider a situation where you need to perform similar types of changes on a group of files. You could instinctively fire up your favorite editor and perform a bunch of mundane, repetitive, and time-consuming edits by hand. But there's a better way.<br />
<br />
=== Enter sed ===<br />
It would be nice if we could automate the process of making edits to files, so that we could "batch" edit files, or even write scripts with the ability to perform sophisticated changes to existing files. Fortunately for us, for these types of situations, there is a better way -- and the better way is called sed.<br />
<br />
sed is a lightweight stream editor that's included with nearly all UNIX flavors, including Linux. sed has a lot of nice features. First of all, it's very lightweight, typically many times smaller than your favorite scripting language. Secondly, because sed is a stream editor, it can perform edits to data it receives from stdin, such as from a pipeline. So, you don't need to have the data to be edited stored in a file on disk. Because data can just as easily be piped to sed, it's very easy to use sed as part of a long, complex pipeline in a powerful shell script. Try doing that with your favorite editor.<br />
<br />
=== GNU sed ===<br />
Fortunately for us Linux users, one of the nicest versions of sed out there happens to be GNU sed. Every Linux distribution has GNU sed, or at least should. GNU sed is popular not only because its sources are freely distributable, but because it happens to have a lot of handy, time-saving extensions to the POSIX sed standard. GNU sed also doesn't suffer from many of the limitations that earlier and proprietary versions of sed had, such as a limited line length -- GNU sed handles lines of any length with ease.<br />
<br />
=== The right sed ===<br />
In this series, we will be using GNU sed. Some (but very few) of the most advanced examples you'll find in my upcoming, follow-on articles in this series will not work with GNU sed 3.02 or 3.02a and will require a modern version. If you're using a non-GNU sed, your results may vary. Why not take some time to install GNU sed now (see [[#Resources|Resources]] for source code)? Then, not only will you be ready for the rest of the series, but you'll also be able to use arguably the best sed in existence!<br />
<br />
=== Sed examples ===<br />
Sed works by performing any number of user-specified editing operations ("commands") on the input data. Sed is line-based, so the commands are performed on each line in order. And, sed writes its results to standard output (stdout); it doesn't modify any input files.<br />
<br />
Let's look at some examples. The first several are going to be a bit weird because I'm using them to illustrate how sed works rather than to perform any useful task. However, if you're new to sed, it's very important that you understand them. Here's our first example:<br />
<pre><br />
$ sed -e 'd' /etc/services<br />
</pre><br />
If you type this command, you'll get absolutely no output. Now, what happened? In this example, we called sed with one editing command, <span style="color:green">d</span>. Sed opened the '''/etc/services''' file, read a line into its pattern buffer, performed our editing command ("delete line"), and then printed the pattern buffer (which was empty). It then repeated these steps for each successive line. This produced no output, because the <span style="color:green">d</span> command zapped every single line in the pattern buffer!<br />
<br />
There are a couple of things to notice in this example. First, '''/etc/services''' was not modified at all. This is because, again, sed only reads from the file you specify on the command line, using it as input -- it doesn't try to modify the file. The second thing to notice is that sed is line-oriented. The <span style="color:green">d</span> command didn't simply tell sed to delete all incoming data in one fell swoop. Instead, sed read each line of /etc/services one by one into its internal buffer, called the pattern buffer. Once a line was read into the pattern buffer, it performed the <span style="color:green">d</span> command and printed the contents of the pattern buffer (nothing in this example). Later, I'll show you how to use address ranges to control which lines a command is applied to -- but in the absence of addresses, a command is applied to all lines.<br />
<br />
The third thing to notice is the use of single quotes to surround the d command. It's a good idea to get into the habit of using single quotes to surround your sed commands, so that shell expansion is disabled.<br />
<br />
=== Another sed example ===<br />
Here's an example of how to use sed to remove the first line of the '''/etc/services''' file from our output stream:<br />
<pre><br />
$ sed -e '1d' /etc/services | more<br />
</pre><br />
As you can see, this command is very similar to our first <span style="color:green">d</span> command, except that it is preceded by a 1. If you guessed that the 1 refers to line number one, you're right. While in our first example, we used d by itself, this time we use the <span style="color:green">d</span> command preceded by an optional numerical address. By using addresses, you can tell sed to perform edits only on a particular line or lines.<br />
<br />
=== Address ranges ===<br />
Now, let's look at how to specify an address range. In this example, sed will delete lines 1-10 of the output:<br />
<pre><br />
$ sed -e '1,10d' /etc/services | more<br />
</pre><br />
When we separate two addresses by a comma, sed will apply the following command to the range that starts with the first address, and ends with the second address. In this example, the <span style="color:green">d</span> command was applied to lines 1-10, inclusive. All other lines were ignored.<br />
<br />
=== Addresses with regular expressions ===<br />
Now, it's time for a more useful example. Let's say you wanted to view the contents of your '''/etc/services''' file, but you aren't interested in viewing any of the included comments. As you know, you can place comments in your '''/etc/services''' file by starting the line with the '#' character. To avoid comments, we'd like sed to delete lines that start with a '#'. Here's how to do it:<br />
<pre><br />
$ sed -e '/^#/d' /etc/services | more<br />
</pre><br />
Try this example and see what happens. You'll notice that sed performs its desired task with flying colors. Now, let's figure out what happened.<br />
<br />
To understand the '/^#/d' command, we first need to dissect it. First, let's remove the 'd' -- we're using the same delete line command that we've used previously. The new addition is the '/^#/' part, which is a new kind of regular expression address. Regular expression addresses are always surrounded by slashes. They specify a pattern, and the command that immediately follows a regular expression address will only be applied to a line if it happens to match this particular pattern.<br />
<br />
So, '/^#/' is a regular expression. But what does it do? Obviously, this would be a good time for a regular expression refresher.<br />
<br />
=== Regular expression refresher ===<br />
We can use regular expressions to express patterns that we may find in the text. If you've ever used the '*' character on the shell command line, you've used something that's similar, but not identical to, regular expressions. Here are the special characters that you can use in regular expressions:<br />
{| border=1<br />
|-<br />
|'''Character'''<br />
|'''Description'''<br />
|-<br />
|^<br />
|Matches the beginning of the line<br />
|-<br />
|$<br />
|Matches the end of the line<br />
|-<br />
|.<br />
|Matches any single character<br />
|-<br />
|*<br />
|Will match zero or more occurrences of the previous character<br />
|-<br />
|[ ]<br />
|Matches all the characters inside the [ ]<br />
|}<br />
<br />
Probably the best way to get your feet wet with regular expressions is to see a few examples. All of these examples will be accepted by sed as valid addresses to appear on the left side of a command. Here are a few:<br />
{| border=1<br />
|-<br />
|'''Regular expression'''<br />
|'''Description'''<br />
|-<br />
|/./<br />
|Will match any line that contains at least one character<br />
|-<br />
|/../<br />
|Will match any line that contains at least two characters<br />
|-<br />
|/^#/<br />
|Will match any line that begins with a '#'<br />
|-<br />
|/^$/<br />
|Will match all blank lines<br />
|-<br />
|/}$/<br />
|Will match any lines that ends with '}' (no spaces)<br />
|-<br />
|/} *$/<br />
|Will match any line ending with '}' followed by zero or more spaces<br />
|-<br />
|/[abc]/<br />
|Will match any line that contains a lowercase 'a', 'b', or 'c'<br />
|-<br />
|/^[abc]/<br />
|Will match any line that begins with an 'a', 'b', or 'c'<br />
|}<br />
I encourage you to try several of these examples. Take some time to get familiar with regular expressions, and try a few regular expressions of your own creation. You can use a regexp this way:<br />
<pre><br />
$ sed -e '/regexp/d' /path/to/my/test/file | more<br />
</pre><br />
This will cause sed to delete any matching lines. However, it may be easier to get familiar with regular expressions by telling sed to print regexp matches, and delete non-matches, rather than the other way around. This can be done with the following command:<br />
<pre><br />
$ sed -n -e '/regexp/p' /path/to/my/test/file | more<br />
</pre><br />
Note the new '-n' option, which tells sed to not print the pattern space unless explicitly commanded to do so. You'll also notice that we've replaced the <span style="color:green">d</span> command with the <span style="color:green">p</span> command, which as you might guess, explicitly commands sed to print the pattern space. Voila, now only matches will be printed.<br />
<br />
=== More on addresses ===<br />
Up till now, we've taken a look at line addresses, line range addresses, and regexp addresses. But there are even more possibilities. We can specify two regular expressions separated by a comma, and sed will match all lines starting from the first line that matches the first regular expression, up to and including the line that matches the second regular expression. For example, the following command will print out a block of text that begins with a line containing "BEGIN", and ending with a line that contains "END":<br />
<pre><br />
$ sed -n -e '/BEGIN/,/END/p' /my/test/file | more<br />
</pre><br />
If "BEGIN" isn't found, no data will be printed. And, if "BEGIN" is found, but no "END" is found on any line below it, all subsequent lines will be printed. This happens because of sed's stream-oriented nature -- it doesn't know whether or not an "END" will appear.<br />
<br />
=== C source example ===<br />
If you want to print out only the main() function in a C source file, you could type:<br />
<pre><br />
$ sed -n -e '/main[[:space:]]*(/,/^}/p' sourcefile.c | more<br />
</pre><br />
This command has two regular expressions, <nowiki>'/main[[:space:]]*(/' and '/^}/'</nowiki>, and one command, <span style="color:green">p</span>. The first regular expression will match the string "main" followed by any number of spaces or tabs, followed by an open parenthesis. This should match the start of your average ANSI C main() declaration.<br />
<br />
<nowiki>In this particular regular expression, we encounter the '[[:space:]]' character class. This is simply a special keyword that tells sed to match either a TAB or a space. If you wanted, instead of typing '[[:space:]]', you could have typed '[', then a literal space, then Control-V, then a literal tab and a ']' -- The Control-V tells bash that you want to insert a "real" tab rather than perform command expansion. It's clearer, especially in scripts, to use the '[[:space:]]' command class.</nowiki><br />
<br />
OK, now on to the second regexp. '/^}/' will match a '}' character that appears at the beginning of a new line. If your code is formatted nicely, this will match the closing brace of your main() function. If it's not, it won't -- one of the tricky things about performing pattern matching.<br />
<br />
The <span style="color:green">p</span> command does what it always does, explicitly telling sed to print out the line, since we are in '-n' quiet mode. Try running the command on a C source file -- it should output the entire main() { } block, including the initial "main()" and the closing '}'.<br />
<br />
=== Next time ===<br />
Now that we've touched on the basics, we'll be picking up the pace for the next two articles. If you're in the mood for some meatier sed material, be patient -- it's coming! In the meantime, you might want to check out the following sed and regular expression resources.<br />
<br />
== Resources ==<br />
* Read Daniel's other sed articles: Sed by example, [[Sed by Example, Part 2|Part 2]] and [[Sed by Example, Part 3|Part 3]].<br />
* Check out Eric Pement's excellent [http://sed.sourceforge.net/sedfaq.html sed FAQ].<br />
* You can find the sources to sed at ftp://ftp.gnu.org/pub/gnu/sed.<br />
* Eric Pement also has a handy list of [http://sed.sourceforge.net/sed1line.txt sed one-liners] that any aspiring sed guru should definitely look at.<br />
* If you'd like a good old-fashioned book, [http://www.oreilly.com/catalog/sed2/ O'Reilly's sed & awk, 2nd Edition] would be wonderful choice.<br />
* See the regular expressions [http://docs.python.org/dev/howto/regex.html how-to document] from [http://python.org/ python.org].<br />
* Refer to an [http://www.uky.edu/ArtsSciences/Classics/regex.html overview of regular expressions] from the University of Kentucky.<br />
<br />
__NOTOC__<br />
[[Category:Linux Core Concepts]]<br />
[[Category:Articles]]<br />
[[Category:Featured]]</div>Golodhrimhttps://www.funtoo.org/index.php?title=Template:Kernelop&diff=1245Template:Kernelop2011-05-18T20:40:35Z<p>Golodhrim: </p>
<hr />
<div>{| width="100%" cellpadding=0 cellspacing=0 style="margin: .5em 0; background-color: #d3d7cf; border: solid 1px #34dae0;" <br />
| width="150px" valign="top" style="background-color: #3465a4; border-left: solid 1px #34dae0; border-top: solid 1px #34dae0; border-bottom: 1px solid #888; font-size: 0.9em" | '''Kernel option path:''' <br />
| style="background-color: #3465a4; border-top: solid 1px #34dae0; border-right: solid 1px #34dae0; border-bottom: 1px solid #888; font-size: 0.9em" | {{{1}}} <br />
|- <br />
| style="padding: 0 0.5em; font-family=monospace, fixed;" colspan="2" | {{{2}}}<br />
|}<noinclude>{{documentation}}</noinclude></div>Golodhrimhttps://www.funtoo.org/index.php?title=Core_Developer_Reference&diff=1186Core Developer Reference2011-04-29T18:48:52Z<p>Golodhrim: /* Funtoo portage tree */ adding link to Git Guide</p>
<hr />
<div>This page is a reference for Funtoo core developers.<br />
<br />
= Core developers =<br />
<br />
A Funtoo core developer is a member of the [[Core Team]] who help in the maintenance/evolution of Funtoo Linux.<br />
<br />
= Funtoo portage tree =<br />
<br />
A frequently asked question is: "What your portage tree is made of?". The answer lies in a Python script named merge.py present in the directory funtoo/scripts of the Funtoo overlay. Basically, this script:<br />
<br />
* Takes a snapshot of the Gentoo portage tree (imported every 12 hours)<br />
* Merges with the Funtoo overlay: the Funtoo historical development overlay (still maintained, the Funtoo overlay contains for example the scripts used to regenerate the Funtoo portage tree)<br />
* Merges with the Multimedia overlay (only one package here -> media-video/mplayer-uau)<br />
* Merges with the overlays maintained by several Funtoo developpers:<br />
** Tarsius overlay (tarsius/Funtoo Core Team)<br />
** Foo overlay (slashbeast)<br />
** Bar overlay (404 error)<br />
** Golodhrim overlay (golodhrim)<br />
<br />
A short guide on how to go working with github is available at [[Git Guide]], so everyone new to git, github and CoreTeam should have a look there to get the basics.<br />
<br />
When a new core developer or contributor want to share his ebuild repository, he must:<br />
<br />
# Ask for having a read-write access on the Funtoo overlay (''With great privileges come great responsibilities'', do not change something you are sure about, you will be very likely to break things so please ask before act).<br />
# Clone the Funtoo overlay (use git@github.com:funtoo/funtoo-overlay.git, not git://github.com/funtoo/funtoo-overlay.git that later is a public read-only reference)<br />
# Edit funtoo/scripts/merge.py:<br />
<pre><br />
bar_overlay = Tree("bar-overlay","/root/git/bar-funtoo-overlay", pull=True)<br />
multimedia_overlay = Tree("multimedia-overlay", "/root/git/multimedia-overlay",pull=True)<br />
your_overlay = Tree("name-of-your-overlay", "/root/git/name-of-your-overlay",pull=True)<br />
<br />
steps = [<br />
SyncTree(gentoo_src,exclude=["/metadata/cache/**","sys-kernel/openvz-sources"]),<br />
ApplyPatchSeries("%s/funtoo/patches" % funtoo_overlay.root ),<br />
SyncDir(funtoo_overlay.root,"profiles","profiles", exclude=["repo_name","categories"]),<br />
(.... some lines removed ....)<br />
InsertEbuilds(bar_overlay, select="all", skip=None, replace=False),<br />
InsertEbuilds(multimedia_overlay, select=["media-video/mplayer-uau"], skip=None, replace=False),<br />
InsertEbuilds(your_overlay, select="all", skip=None, replace=False),<br />
GenCache()<br />
]<br />
<br />
</pre><br />
<br />
Once the modifications are in place, just push merge.py back to github (and please, again, do that with a core team member on IRC)<br />
<br />
<pre><br />
# git push origin<br />
</pre><br />
<br />
Basically you define an ebuild tree object which points to your repository and tell the script:"Select all the content of my package tree, skip no packages and do not replace duplicates if any".<br />
<br />
= Masking or unmasking your packages =<br />
<br />
The rule is: '''"If you update a package which is either a part of the system core or can have a severe impact on the system, please mask it".''' <br />
<br />
This is the case for example of GCC, Glibc, Binutils, autoconf, automake, Python, Perl, DHCPD, NTP, OpenRC. By definition, every package that could make your system unusable after an update '''must''' be masked. If you add an optional package that have minor or no impact at all (e.g. an IDE, a Pascal compiler, a multimedia file player...) there is no need to mask the package first. <br />
<br />
There are 3 files used in the Funtoo overlay to achive that (see funtoo-overlay/profile/package.mask). By convention:<br />
<br />
* funtoo-staging : '''when a core package is added, its masking ''must'' go there'''. Once the package has been tested enough by the community, its masking statement is removed from that file.<br />
* funtoo-cautionary : permanent maskings should go there. This file is also updated if a package is masked prior to its removal from the Funtoo tree<br />
* sunrise : updated on very rare occasions this file is related to the Gentoo sunrise overlay.<br />
<br />
= How to edit and commit your changes in funtoo-overlay/profile/package.mask =<br />
<br />
== The way to go ==<br />
<br />
A good practice is to do a ''git pull'' '''before''' changing anything in the funtoo-overlay/profile/package.mask directory (please do not add any other files there, use only existing ones). This helps to get a clearer commit history and make your and our life a bit more happy. Once this refresh is done you can bring your changes in the adequate files in accordance to the following rules:<br />
# Always put your changes at the top of the list<br />
# Always mention in the first line who you are, your e-mail and the date of the day<br />
# Unless you have a good reason to not do it, please always mask like: '''>=category/package-revision'''. E.g. '''>=dev-lang/perl-5.12.3'''<br />
# '''Do not mask the same package several times''' (i.e. never put more that one line mentioning the same category/package).<br />
<br />
<pre><br />
<br />
# John Doe <john.doe@funtoo.org> (31 Dec 2010)<br />
# Masked for testing<br />
>=dev-lang/python-4.0<br />
<br />
# John Doe <john.doe@funtoo.org> (30 Dec 2010)<br />
# Masked for testing<br />
>=net-dialup/ppp-7.0.1_beta<br />
<br />
...<br />
<br />
</pre><br />
<br />
== Stashing and merging your local changes ==<br />
<br />
If you have changed some files before doing a ''git pull'', you will be likely to encounter a conflict when pulling from the GitHub repository:<br />
<br />
<pre><br />
# git pull<br />
Enter passphrase for key '/root/.ssh/id_rsa':<br />
remote: Counting objects: 145, done.<br />
remote: Compressing objects: 100% (115/115), done.<br />
remote: Total 117 (delta 66), reused 0 (delta 0)<br />
Receiving objects: 100% (117/117), 37.20 KiB, done.<br />
(...)<br />
error: Your local changes to the following files would be overwritten by merge:<br />
profiles/package.mask/funtoo-staging<br />
Please, commit your changes or stash them before you can merge.<br />
</pre><br />
<br />
To sort this situation out:<br />
# Stash your changes by issuing '''git stash'''<br />
# Issue '''git pull'''<br />
# Merge back your stashed changes with the current HEAD by issuing: '''git stash pop'''<br />
<br />
Example:<br />
<pre><br />
# git stash<br />
Saved working directory and index state WIP on master: 7990315 gptfdisk unmask<br />
HEAD is now at 7990315 gptfdisk unmask<br />
(...)<br />
# git pull<br />
Enter passphrase for key '/root/.ssh/id_rsa':<br />
Updating 7990315..efecb0d<br />
Fast-forward<br />
app-arch/tar/Manifest | 2 +-<br />
app-arch/tar/tar-1.25-r1.ebuild | 2 +-<br />
profiles/funtoo/1.0/linux-gnu/flavor/core/virtuals | 2 -<br />
(...)<br />
# git stash pop<br />
Auto-merging profiles/package.mask/funtoo-staging<br />
(...)<br />
</pre><br />
<br />
At this point, it is highly probable that Git will report a conflict if another Funtoo developer had also brought and pushed on GitHub some changes:<br />
<br />
<pre><br />
CONFLICT (content): Merge conflict in profiles/package.mask/funtoo-staging<br />
</pre><br />
<br />
Just correct the conflict in the file (see the marks put by Git in the file). Once everything is in order, just commit and push your changes (remember to add a short explicative note in the commit to track down the reason of the change).<br />
<br />
== Committing your changes on funtoo-overlay/profile/package.mask ==<br />
<br />
A '''highly recommended''' way to commit your changes is to proceed in the following order:<br />
<br />
# Commit and push the changes brought in profiles/packages.mask<br />
# Commit and push the changes brought in the package tree (in your overlay and/or the funtoo-overlay in itself).<br />
<br />
Why? Simple: remember that the Funtoo portage tree is automatically refreshed every 12 hours and this refresh of merging several Funtoo developers repositories on GitHub, the Funtoo overlay master copy (also located on GitHub) and a snapshot of the Gentoo portage tree. At the time you commit, it is not impossible that the refreshment process and you are acting in a concurrent way and the following scenario could occur:<br />
<br />
# You have updated some Funtoo core packages (or, worse, a Funtoo critical package) and you commit and push the changes brought either in the Funtoo overlay either in your local repository on GitHub<br />
# The Funtoo tree refreshment process starts and grab the place where your updated package resides and the profiles/packages.mask directory in the Funtoo overlay <br />
# You commit and push your changes in profiles/packages.mask to mask<br />
<br />
'''Not respecting this order could lead to ''catastrophic'' consequences for Funtoo users the next time they will resync their portage tree''' if your package breaks for various reasons or if the deployed software has severe issues that you had not been able to detect on your side.<br />
<br />
= Things to do after pushing a package (update or new) - IMPORTANT =<br />
<br />
== Advise the Funtoo community ==<br />
'''The following is not optional so pay attention''': once your bits have been pushed on GitHub, you have to post a notice about what you have updated/added to the Funtoo tree on all of the following Funtoo communication channels:<br />
<br />
* the funtoo-dev mailing list on Google Groups<br />
* the funtoo.org Forums<br />
<br />
The reason is simple: some of the Funtoo users use the mailing list and some others prefer to use the Funtoo forums and both categories must be reached.<br />
<br />
== Update the additions/forks pages in the wiki ==<br />
Depending on what you did, please update the following pages:<br />
* [[Forked_Ebuilds]] if you have forked an '''existing''' Gentoo package (giving a new revision)<br />
* [[Specific_Funtoo_Ebuilds]] if you have introduced '''a totally new package''' in Funtoo (not a revision of an existing Gentoo/Funtoo package)<br />
<br />
[[Category:Internals]]</div>Golodhrimhttps://www.funtoo.org/index.php?title=Template:Infobox_software/Doc&diff=1083Template:Infobox software/Doc2011-02-22T23:02:15Z<p>Golodhrim: </p>
<hr />
<div><br />
== Usage ==<br />
<pre style="overflow:auto;"><br />
{{Infobox software<br />
| name = <br />
| title = <br />
| logo = <!-- [[File: ]] --><br />
| screenshot = <!-- [[File: ]] --><br />
| caption = <br />
| collapsible = <br />
| author = <br />
| developer = <br />
| released = <!-- {{Start date|YYYY|MM|DD|df=yes/no}} --><br />
| discontinued = <br />
| latest release version = <br />
| latest release date = <!-- YYYY-MM-DD --><br />
| latest preview version = <br />
| latest preview date = <!-- YYYY-MM-DD --><br />
| frequently updated = <!-- DO NOT include this parameter unless you know what it does --><br />
| programming language = <br />
| operating system = <br />
| platform = <br />
| size = <br />
| language = <br />
| status = <br />
| genre = <br />
| license = <br />
| website = example.org<br />
}}<br />
</pre><br />
<br />
<br />
== Example ==<br />
<div class="dablink">The following example is captured on 1 September 2010 from [[GIMP]] article and is include '''only with the purpose serving as an example.''' Information included in this example infobox are therefore bound to become obsolete as the time passes. Images in this example are published under free licenses.</div><br />
{{Infobox software<br />
| name = GIMP<br />
| logo = [[File:The GIMP icon - gnome.svg|64px|Wilber, The GIMP mascot]]<br />
| screenshot = [[File:Gimpscreen.png|250px]]<br />
| caption = Screenshot of GIMP 2.6<br />
| developer = The GIMP Development Team<br />
| released = 1996<br />
| latest preview version = 2.7.1<br />
| latest preview date = 2010-06-29<br />
| latest release version = 2.6.10<br />
| latest release date = 2010-07-08<br />
| programming language = [[C (programming language)|C]] and [[GTK+]]<br />
| operating system = [[Linux]], [[Mac OS X]], [[Microsoft Windows]], [[FreeBSD]], [[Solaris (operating system)|Solaris]]<br />
| language = 52 languages in GIMP 2.6, 37 fully translated, others partly translated.{{cite web|title=GIMP - Documentation|url=http://www.gimp.org/docs/|date=2001-2009|work=GIMP documentation|publisher=GIMP Documentation team|accessdate=2 July 2009}}{{cite web|url=http://l10n.gnome.org/module/gimp/ |title=GNOME GIMP translation statistics, see GIMP 2.6}}<br />
| status = Active<br />
| genre = [[Raster graphics editor]]<br />
| license = [[GNU General Public License]]<br />
| website = www.gimp.org<br />
}}<br />
<br />
<pre style="overflow:auto;"><br />
{{Infobox software<br />
| name = GIMP<br />
| logo = [[File:The GIMP icon - gnome.svg|64px|Wilber, The GIMP mascot]]<br />
| screenshot = [[File:Gimpscreen.png|250px]]<br />
| caption = Screenshot of GIMP 2.6<br />
| developer = The GIMP Development Team<br />
| released = 1996<br />
| latest preview version = 2.7.1<br />
| latest preview date = 2010-06-29<br />
| latest release version = 2.6.10<br />
| latest release date = 2010-07-08<br />
| programming language = [[C (programming language)|C]] and [[GTK+]]<br />
| operating system = [[Linux]], [[Mac OS X]], [[Microsoft Windows]], [[FreeBSD]], [[Solaris (operating system)|Solaris]]<br />
| language = 52 languages in GIMP 2.6, 37 fully translated, others partly translated.{{cite web|title=GIMP - Documentation|url=http://www.gimp.org/docs/|date=2001-2009|work=GIMP documentation|publisher=GIMP Documentation team|accessdate=2 July 2009}}{{cite web|url=http://l10n.gnome.org/module/gimp/ |title=GNOME GIMP translation statistics, see GIMP 2.6}}<br />
| status = Active<br />
| genre = [[Raster graphics editor]]<br />
| license = [[GNU General Public License]]<br />
| website = www.gimp.org<br />
}}<br />
</pre><br />
----<br />
<br />
== Parameters ==<br />
All parameters are optional.<br />
<br />
; name: Name of the infobox. Usually, it is used to display the name software product but may be anything, as it used as an internal parameter for use with <code>frequently updated</code> parameter, and "Stable release" / "Preview release" fields. When modifying an article which already has an infobox, be careful not to edit this parameter when <code>frequently updated</code> parameter is set to ''yes''. In such cases, if you want to edit the title at the top of the infobox, use the <code>title</code> parameter instead.<br />
:'''ATTENTION:''' Please do not include a [[Help:Link#Wikilinks|wikilink]], [[hyperlink]] or image in this parameter. This parameter should be composed of pure text.<br />
<br />
; title: Name of the software product as displayed above the infobox. When not specified, contents of ''name'' parameter will be displayed instead.<br />
:'''Important note:''' Please do not include an image in this field. Wikipedia [[accessibility]] requirements mandates that this field should contain text that can be read by [[screen reader]]s.<br />
<br />
; logo: Code for a small image to be displayed as software product's [[logo]] or [[computer icon]]. The contents of this field should look like:<br />
::<tt>&#91;&#91;File:''File name.ext''{{!}}''Size''px&#93;&#93;</tt><br />
:Replace ''Filename.ext'' with the name of your image and ''Size'' with width of your image in pixels. For more information regarding use of images and their syntax, please consult: [[Help:Contents/Images and media]].<br />
<br />
; screenshot: Code for an image to be displayed as software product's [[screenshot]]. The contents of this field should look like:<br />
::<tt>&#91;&#91;File:''File name.ext''{{!}}''Size''px&#93;&#93;</tt><br />
:Replace ''Filename.ext'' with the name of your image and ''Size'' with width of your image in pixels. For more information regarding use of images and their syntax, please consult: [[Help:Contents/Images and media]].<br />
<br />
; caption: A caption for screenshot that appears below it. Please include this parameter only when there is an image to display.<br />
<br />
; collapsible: Whether this screenshot is by default hidden and is only shown when user clicks on a minuscule "Expand" button. Can be set to "yes". Especially useful in case of long vertical screenshot (see [[QQ]] for example)<br />
<br />
; developer: Name of the current developer of the software product. It can be either an individual or an organization/business.<br />
<br />
; author: Name of the original author or publisher of the software product. It can be either an individual or an organization/business. Most of the times, it only needs to be specified when <code>developer</code> field is populated.<br />
<br />
; released: The date in which version 1.0 (or closely-matching release) of the software product in question reaches its [[Release to manufacturing]] (RTM) stage. In case the article is about a specific major release of a software product (for instance [[Internet Explorer 8]] or [[Microsoft Office 2007]]), this field should contain the date in which that specific major release reached RTM stage. In case the software product is still in development and has not reached its RTM stage, please ignore this field; do not use this field to specify the release date of the first preview/test release of the software product; there is already another parameter for that use.<br />
:The content of this field should look like the following:<br />
::''year''-''month''-''day''<br />
:In case the article uses DMY as date format, use this code instead:<br />
::''year''-''month''-''day''<br />
:If you are unsure which date format to use, please consult [[WP:MOSDATES]].<br />
<br />
; latest release version: The version number of the latest release of the software product. Please observe the following examples:<br />
: Example #1: If the article is about a product called ''Example Software'' whose latest version is 1.5, specify:<br />
::v1.5<br />
: Example #2: If the article is about a product called ''Example Software'' whose latest release is called ''Example Software 2008'' and whose latest version number is 12.2, specify:<br />
::2008 (v12.2)<br />
: Example #3: If the article is about ''Famous Example Software 2010'', which is a significant release of a product called ''Famous Example Software'' and whose latest version number is 14.0.0.25, just specify:<br />
::v14.0.0.25<br />
: Example #4: If the article is about ''Famous Example Software 2010'' for which no update is released since its initial release-to-manufacturing (RTM), please omit this parameter unless there is an evidence that it is necessary for the reader to know this number. One reason would be the presence of preview releases of the software product which can only be distinguished from the RTM by their version number.<br />
:This parameter and <code>latest release date</code> complement each other but none strictly requires the other.<br />
<br />
; latest release date: The release date of the latest released version. If no update is released for the software since its initial release, please omit this field; filling in the <code>released</code> field would be enough. The content of this field should look like the following:<br />
::''year''-''month''-''day''<br />
:In case the article uses DMY as date format, use this code instead:<br />
::''year''-''month''-''day''<br />
:If you are unsure which date format to use, please consult [[WP:MOSDATES]].<br />
:This parameter and <code>latest release version</code> complement each other but none strictly requires the presence of the other.<br />
<br />
; discontinued: Whether this product is no longer being developed, thus changing the phrase "Latest release" in the infobox to "Discontinued". For technical reasons, anything for this parameter has the same effect, be it "yes", "no" or anything else. To nullify the effect of this parameter, you need to omit it.<br />
<br />
; latest preview version: The version number of the latest preview version or development branch. Should only be specified when development of a new version of the software product in question (newer than one specified in <code>latest release version</code>) is in progress. Please consult descriptions for <code>latest release version</code> provided above for best practices of specifying this parameter.<br />
<br />
; latest preview date: Specifies the release date of the latest preview version or development branch. Should only be specified when development of a new version of the software product in question (newer than one specified in <code>latest release version</code>) is in progress. Please consult descriptions for <code>latest release date</code> provided above for best practices of specifying this parameter.<br />
<br />
; frequently updated: Specifies whether the infobox retrieves the software product's latest release version, latest release date, latest preview version and latest preview date from outside the article. Users visiting the article may click the numbers directly in the infobox to edit that external source. This mode is very useful for articles about software products whose vendors keep releasing updates or newer versions. With this mode is enabled, users can quickly and effectively edit the release data without affecting the articles.<br />
:For technical reasons, anything for this parameter has the same effect, be it "yes", "no", "true", "false" or anything else. To nullify the effect of this parameter, you need to omit this parameter or specify nothing for it. Note however, that if any of <code>latest release version</code>, <code>latest release date</code>, <code>latest preview version</code> or <code>latest preview date</code> parameters are specified, external source will be ignored.<br />
:To make the infobox retrieve release data from outside the article:<br />
#Delete <code>latest release version</code>, <code>latest release date</code>, <code>latest preview version</code> or <code>latest preview date</code> parameters from the infobox.<br />
#Save the article.<br />
#Create external source that supplies data for latest stable release. To do so:<br />
##Copy and paste the following URL into your browser's address bar, replacing ''INFOBOX_NAME'' with the value supplied in <code>name</code> parameter of the infobox: <br/><span class="plainlinks"><code>{{fullurl:Template:Latest stable software release/INFOBOX_NAME|action=edit&preload=Template:LSR/syntax}}</code></span><br />
##In the page that opens, fill in the required information.<br />
##Save the page.<br />
#Create external source that supplies data for latest preview release. To do so:<br />
##Copy and paste the following URL into your browser's address bar, replacing ''INFOBOX_NAME'' with the value suppplied in <code>name</code> parameter of the infobox: <br/><span class="plainlinks"><code>{{fullurl:Template:Latest preview software release/INFOBOX_NAME|action=edit&preload=Template:LPR/syntax}}</code></span><br />
##In the page that opens, fill in the required information.<br />
##Save the page.<br />
#Refresh the article.<br />
<br />
; programming language: The [[programming language]] of that subject of the article. If the program language of the software product has a corresponding article in Wikipedia, please link to it. Here is an example:<br />
::Code: <code><nowiki>[[C++]] and [[C Sharp (programming language)|C#]]</nowiki></code><br />
::Result: [[C++]] and [[C Sharp (programming language)|C#]]<br />
:When specifying the name of the programming language please make sure that you [[WP:V|cite your source]]. Unreferenced assertions in Wikipedia may be challenged or removed. If you have a source, do not include this parameter.<br />
<br />
; operating system: The [[operating system]] on which the given software product works. Please be as accurate as possible in specifying this parameter (but also be mindful of the length) and avoid specifying vague phrases such as [[Cross-platform]] (or its redirect, [[Multi-platform]]). Please consider these examples:<br />
:*If the software product works on all incarnations of [[Unix]], [[Linux]] and derived operating systems, please specify:<br />
:**<code><nowiki>[[Unix-like]]</nowiki></code><br />
:*If the software works unconditionally on ALL incarnations of [[Microsoft Windows]], please specify:<br />
:**<code><nowiki>[[Microsoft Windows]]</nowiki></code><br/>(Do not specify <code><nowiki>[[Microsoft Windows|Windows]]</nowiki></code>; always write the full name of a registered trademark when no length restriction is imposed upon you.)<br />
:*If the software product works only on [[Windows XP]] and all subsequent releases of Microsoft Windows, please specify:<br />
:**<code><nowiki>[[Windows XP]] and later</nowiki></code><br />
:*If the software product works only on [[Windows XP]] and all subsequent releases of consumers versions of Microsoft Windows, please specify:<br />
:**<code><nowiki>[[Windows XP]], [[Windows Vista]] and [[Windows 7]]</nowiki></code><br/>(At the time of this writing, August 2010, Windows 7 was the latest consumers release of Microsoft Windows.)<br />
:*If the software product is released for various families of different operating systems, (such as specific versions of BSD, Linux, Mac OS and Windows) so that listing them in the infobox gives it undue length, please leave the details to article body and specify:<br />
:**<code><nowiki>[[BSD]], [[Linux]], [[Mac OS]] and [[Microsoft Windows|Windows]]</nowiki></code><br />
:*If the software is an operating system–independent [[web application]], ignore this parameter.<br />
<br />
; platform: The [[computing platform]] under which the product runs. You might like to include the following information:<br />
:*'''Processor architecture:''' Some software products only run under a certain processor architecture. The most common architectures are [[IA-32]] (also known as ''x86'', ''i386'' and ''32-bit processor''), [[x86-64]] (also known as ''x64'', ''AMD64'', ''EM64T'' and ''64-bit'') and [[Itanium]]. Unfortunately, these information are very technical. Specially, a lot of people do not know that [[x86]] is not the same as [[IA-32]]. For that reason, please consider specifying the following phrases:<br />
:**For software products that run on IA-32 processors, please specify: '''<code><nowiki>[[IA-32|Intel x86 - 32-bit]]</nowiki></code>''' or '''<code><nowiki>[[IA-32]]</nowiki></code>'''. Do ''not'' specify: <code><nowiki>[[x86]]</nowiki></code> or <code><nowiki>[[32-bit]]</nowiki></code><br />
:**For software products that run on x86-64 processors, please specify: '''<code><nowiki>[[x86-64|x64]]</nowiki></code>'''. Do ''not'' specify: <code><nowiki>[[64-bit]]</nowiki></code>, <code><nowiki>[[AMD64]]</nowiki></code> or <code><nowiki>[[EM64T]]</nowiki></code><br />
:*'''Software frameworks:''' Some software products run on [[Java platform]], [[.NET Framework]], [[Adobe Flash]], [[Adobe AIR]], [[Microsoft Silverlight]] or [[XUL]] without regard to the processor architecture. If so, you may ignore processor architecture and instead specify the framework.<br />
:Please avoid specifying vague phrases such as [[Cross-platform]] unless the following conditions meet:<br />
:#The software product has been released for numerous different platforms, so much so that including all of them causes the infobox size to grow unduly large.<br />
:#The article body lists the platforms under which the product runs.<br />
:If the above do not meet, then specifying such a vague phrase is the same as not specifying it.<br />
<br />
; size: Size of the installer package. Only applies to software products that are available via download. For products distributed physically in boxes of packages, ignore this parameter. Do not forget to include your unit of measurements (i.e. Kilobytes, megabytes or gigabytes). Observe the following examples:<br />
:*<code><nowiki>760&#x26;nbsp&#x3B;[[Kilobyte|KB]]</nowiki></code> → 760&nbsp;[[Kilobyte|KB]]<br />
:*<code><nowiki>32&#x26;nbsp&#x3B;[[Megabyte|MB]]</nowiki></code> → 32&nbsp;[[Megabyte|MB]]<br />
:*<code><nowiki>1.5&#x26;nbsp&#x3B;[[Gigabyte|GB]]</nowiki></code> → 1.5&nbsp;[[Gigabyte|GB]]<br />
:'''Note:''' "&#x26;nbsp&#x3B;" generates a non-breaking space. Words connected by this mark won't separate when "word wrapping" occurs.<br />
:For more information, visit [[WP:UNITS]]<br />
<br />
; language: Lists the Natural languages in which the software product user interface can interact with user. Please do not supply "Multilingual" or such vague phrases which do not add to the knowledge of the reader. When the list of languages is huge AND when those languages are listed in the article body, please specify number of the supported languages instead. Also please do not wikilink the name of languages: Readers are most likely unwilling to read about those languages.<br />
<br />
; status: The development status of the computer program, such as: Planned, Active, Unmaintained, Discontinued, Stalled or [[Abandonware]]<br />
<br />
; genre: Type of program. Should be wikilinked to an article such as [[Geographic information system]]. For more information, consult [[List of software categories]]. Please do not use this field to briefly describe the role and function of the subject of the article. For example, instead of "SVG creator, editor and converter", consider using "[[Vector graphics editor]]". Instead of "PDF creator, editor, converter and viewer", consider using "[[Desktop publishing software]]". Instead of "DWG creator/editor", consider using "[[Computer-aided design]]".<br />
<br />
; license: Type of the software license under which the consumer is allowed to use the product. You may specify it in two forms:<br />
:*You may specify a type of well-known license. For example:<br />
:**[[Proprietary software|Proprietary]] [[commercial software]] (<code><nowiki>[[Proprietary software|Proprietary]] [[commercial software]]</nowiki></code>): Software products which are licensed for use for a price. Most software today are published under this license type.<br />
:**[[Freeware]]: Software products which are licensed for use (and sometimes redistribution) but free of charge.<br />
:**[[Free software]]: Software products that can be used, studied, and modified without restriction, and which can be copied and redistributed in modified or unmodified form.<br />
:*You may specify a well-known licensing scheme, such as:<br />
:**[[GNU General Public License]]<br />
:**[[GNU Lesser General Public License]]<br />
:**[[BSD License]]<br />
:Please avoid specifying phrases that makes no sense to the reader such as "Microsoft EULA", "Adobe End-User License Agreement" or "Symantec Terms of License", etc. (Always bear in mind that you are writing the article for those who do not know about the subject and come to the article to gain knowledge. You are not writing Wikipedia articles for your fellow co-editors who already know!)<br />
<br />
;licence: Same as <code>license</code>. Pick either ''license'' (American English) or ''licence'' (Commonwealth English), not both - select the one which matches the content of the article the template is used in.<br />
<br />
; website: Web site of software package. Please make sure that, whenever possible, the significant portion of the website address remains visible. For example, instead of "<code><nowiki>[http://www.example.com Example website]</nowiki></code>", specify "<code><nowiki>[http://www.example.com www.example.com]</nowiki></code>". You can also specify "<code><nowiki>http://www.example.com</nowiki></code>". The URL template will automatically generate compatible code.</div>Golodhrimhttps://www.funtoo.org/index.php?title=Template:Infobox_software&diff=1082Template:Infobox software2011-02-22T22:58:58Z<p>Golodhrim: </p>
<hr />
<div>{{Infobox <br />
| bodyclass = vevent<br />
| title = {{{title|{{{name|<includeonly>{{PAGENAME}}</includeonly>}}}}}}<br />
| titleclass = summary<br />
| labelstyle = white-space: nowrap<br />
| above = {{{logo|}}}<br />
| image = {{#if:{{{collapsible|}}}|{{hidden begin|title=Screenshot|titlestyle=text-align:center}}}}{{{screenshot|}}}<br />
| caption = {{{caption|}}}{{#if:{{{collapsible|}}}|{{hidden end}}}}<br />
<br />
| label1 = [[Software design|Original author(s)]]<br />
| data1 = {{{author<includeonly>|</includeonly>}}}<br />
| label2 = [[Software developer|Developer(s)]]<br />
| data2 = {{{developer<includeonly>|</includeonly>}}}<br />
| label3 = Initial release<br />
| data3 = {{{released<includeonly>|</includeonly>}}}<br />
| label4 = [[Software release life cycle|{{#if:{{{discontinued|}}}|Discontinued|Stable release}}]]<br />
| data4 = {{#if:{{{latest release version|{{{latest_release_version<includeonly>|</includeonly>}}}}}}<br />
|{{{latest release version|{{{latest_release_version}}}}}} {{#if:{{{latest release date|{{{latest_release_date<includeonly>|</includeonly>}}}}}}<br />
| / {{{latest release date|{{{latest_release_date}}}}}}<br />
}}<br />
|{{#if:{{{frequently updated|{{{frequently_updated|}}}}}}<br />
|{{#ifexist:Template:Latest stable software release/{{{name|{{PAGENAME}}}}} <br />
}}<br />
}}<br />
}}<br />
| label5 = [[Software release life cycle|Preview release]]<br />
| data5 = {{#if:{{{latest preview version|{{{latest_preview_version<includeonly>|</includeonly>}}}}}}<br />
|{{{latest preview version|{{{latest_preview_version}}}}}} {{#if:{{{latest preview date|{{{latest_preview_date<includeonly>|</includeonly>}}}}}}<br />
| / {{{latest preview date|{{{latest_preview_date}}}}}}<br />
}}<br />
|{{#if:{{{frequently updated|{{{frequently_updated|}}}}}}<br />
|{{#ifexist:Template:Latest preview software release/{{{name|{{PAGENAME}}}}}<br />
}}<br />
}}<br />
}}<br />
| label6 = Development status<br />
| data6 = {{{status<includeonly>|</includeonly>}}}<br />
| label7 = [[Programming language|Written in]]<br />
| data7 = {{{programming language|{{{programming_language<includeonly>|</includeonly>}}}}}}<br />
| label8 = [[Operating system]]<br />
| data8 = {{{operating system|{{{operating_system<includeonly>|</includeonly>}}}}}}<br />
| label9 = [[Computing platform|Platform]]<br />
| data9 = {{{platform<includeonly>|</includeonly>}}}<br />
| label10 = [[File size|Size]]<br />
| data10 = {{{size<includeonly>|</includeonly>}}}<br />
| label11 = [[Language|Available in]]<br />
| data11 = {{{language<includeonly>|</includeonly>}}}<br />
| label12 = [[List of software categories|Type]]<br />
| data12 = {{{genre<includeonly>|</includeonly>}}}<br />
| label13 = [[Software license|License]]<br />
| data13 = {{{license<includeonly>|</includeonly>}}}<br />
| label14 = [[Software license|Licence]]<br />
| data14 = {{{licence<includeonly>|</includeonly>}}}<br />
| label15 = [[Website]]<br />
| data15 = {{{website<includeonly>|</includeonly>}}}<br />
| label16 = [[Technical standard|Standard]](s)<br />
| data16 = {{{standard<includeonly>|</includeonly>}}}<br />
| label17 = As of<br />
| data17 = {{{AsOf<includeonly>|</includeonly>}}}<br />
}}<noinclude><br />
{{documentation}}<br />
</noinclude></div>Golodhrimhttps://www.funtoo.org/index.php?title=Template:Infobox/row&diff=1084Template:Infobox/row2011-02-22T22:25:01Z<p>Golodhrim: Created page with "{{#if:{{{header|}}} |<tr><th colspan="2" class="{{{class|}}}" style="text-align:center; {{{headerstyle|}}}">{{{header}}}</th></tr> |{{#if:{{{data|}}} |<tr class="{{{rowclass|..."</p>
<hr />
<div>{{#if:{{{header|}}}<br />
|<tr><th colspan="2" class="{{{class|}}}" style="text-align:center; {{{headerstyle|}}}">{{{header}}}</th></tr><br />
|{{#if:{{{data|}}}<br />
|<tr class="{{{rowclass|}}}">{{#if:{{{label|}}}<br />
|<th scope="row" style="text-align:left; {{{labelstyle|}}}">{{{label}}}</th><br />
<td class="{{{class|}}}" style="{{{datastyle|}}}"><br />
|<td colspan="2" class="{{{class|}}}" style="text-align:center; {{{datastyle|}}}"><br />
}}<br />
{{{data}}}</td></tr><br />
}}<br />
}}</div>Golodhrim