<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.linux.gentoo.documentation">
    <title>gmane.linux.gentoo.documentation</title>
    <link>http://blog.gmane.org/gmane.linux.gentoo.documentation</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3255"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3251"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3250"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3244"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3229"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3224"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3221"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3210"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3206"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3204"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3193"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3191"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3179"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3175"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3166"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3163"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3158"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3149"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3147"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.gentoo.documentation/3136"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3255">
    <title>Clean-up of &lt; at &gt;link attribute</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3255</link>
    <description>&lt;pre&gt;Guys,

Unless you're all screaming loud "No" or something else that's clear to
understand, I'll be removing the &amp;lt; at &amp;gt;link attribute from all documents in
gentoo/xml/htdocs. After that, I'll update guide.dtd to remove the attribute
so that newly committed documents won't have it anymore either.

I was first contemplating of editing the XML-QA-Checker that gets triggered
on CVS commits so that new commits are "screened" for a while, but I thought
to myself - hey, we're a fast-moving distro, it's easier to just mass-commit
everything (and a nice sed command can auto-change the files for me as
well). 

Let's say, give feedback before tuesday april 10th?

Wkr,
Sven Vermeulen

PS I'll mail it to gentoo-dev as well, since it'll also affect guides in
project pages.


&lt;/pre&gt;</description>
    <dc:creator>Sven Vermeulen</dc:creator>
    <dc:date>2012-04-05T20:17:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3251">
    <title>Moving stuff to Gentoo Wiki?</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3251</link>
    <description>&lt;pre&gt;Hi guys,

As the GDP isn't as large as it used to be (I think we have 2 to 4 active
participants/developers currently, coming from a 20+ situation) we might
want to consider moving documents we can't handle currently onto the Gentoo
Wiki. Most of us either don't know the technologies described in it too
well, or we need some help from the community...

License-wise, this should be okay, as there is a version-up clause in the
CC-BY-SA license most documents use. It would also allow us to focus on the
installation instructions and, who knows, have some input for the Gentoo
Wiki Knowledge base at http://wiki.gentoo.org/wiki/Knowledge_Base:Main_Page
;-)

Thoughts on this?

Wkr,
Sven Vermeulen


&lt;/pre&gt;</description>
    <dc:creator>Sven Vermeulen</dc:creator>
    <dc:date>2012-03-27T19:05:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3250">
    <title>Update dcumentation for separate /usr</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3250</link>
    <description>&lt;pre&gt;Hi guys,

The udev package (version 181 and higher) will not support separate /usr
partitions without using an initramfs. Because of this, we will need to
update our documents to inform the users about this:
- inform them that using a separate /usr requires an initramfs
- tell them how to build their own initramfs

I've opened a tracker bug [1] so that we can track issues related with it,
as well as major changes that still need to be done (if any). It also allows
the udev maintainers to block on this bug before stabilizing.

Wkr,
Sven Vermeulen

[1] https://bugs.gentoo.org/show_bug.cgi?id=407959


&lt;/pre&gt;</description>
    <dc:creator>Sven Vermeulen</dc:creator>
    <dc:date>2012-03-12T18:32:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3244">
    <title>RAID install document</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3244</link>
    <description>&lt;pre&gt;Hello,

I'm trying to build a simple (all) raid 1
workstation. Just boot/root/swap like
what is found in the handbook.
  Is this the best document to follow:

http://en.gentoo-wiki.com/wiki/RAID/Software

Since grub2 is now defacto and drive sizes
are routinely over 2T, I guess that Disk-labels
(UUIDs), fstab, gpt and grub2 should all be used
to 'future proof' installations?

There is only a snippet in the handbook
and it couches these and other related issues
around multilib.

Any better, more complete documents are keenly
appreciated.


James





&lt;/pre&gt;</description>
    <dc:creator>wireless</dc:creator>
    <dc:date>2012-02-14T17:48:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3229">
    <title>Updated date in handbook</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3229</link>
    <description>&lt;pre&gt;Hi guys,

Something else I noticed is that we sometimes get questions in #gentoo or
even #gentoo-doc about the "Updated" date of the Gentoo Handbook(s). Because
of how things work, the displayed date on the handbook pages is always the
one that is for the given file.

In case of the index page, this is a somewhat old(er) version as the index
page hardly changes. Yet that is the "Updated" version most people look at.

Would it be okay if I updated doc-struct.xsl so that for handbooks, the
updated version always matches the latest update?

Other possibilities are:
- On the index page, display the latest update, but on individual chapters,
  keep the current used date
- Don't touch anything and stop harassing me with your suggestions


Sven Vermeulen


&lt;/pre&gt;</description>
    <dc:creator>Sven Vermeulen</dc:creator>
    <dc:date>2011-12-29T14:27:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3224">
    <title>Portage per-package environment/behavior</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3224</link>
    <description>&lt;pre&gt;Hi guys,

I noticed we don't describe in the handbook that Portage can have
per-package environment variables (like CFLAGS) through /etc/portage/env.
This can be even (ab?)used to execute steps before or after specific phases
(based on the EBUILD_PHASE information), something I use for updating IDS
systems (postinst/prerm phase).

But I'm not sure if and where in the handbook this can be positioned best.
The environment variable stuff could be placed in the section on
"Environment Variables", but is quite off from the rest of the content
(since the rest of that chapter has nothing really to do with Portage or
build environments).

"Configuring through Variables" is probably the best location (somewhere in
the beginning as we talk there about Build-specific Options), but I do feel
that this particular feature is already more targeting advanced users, where
the location in the handbook somewhat suggests this for more beginner-like
types.

Perhaps another section in "Working with Portage", called "Advanced Port&lt;/pre&gt;</description>
    <dc:creator>Sven Vermeulen</dc:creator>
    <dc:date>2011-12-28T10:14:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3221">
    <title>Job Position: someone with a printer ;-)</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3221</link>
    <description>&lt;pre&gt;Hi guys,

No, it's not a real vacancy. But we have a couple of bugreports about CUPS
or printing that could need a hand from someone who has at least some
knowledge in printing on Linux. I haven't had a printer in ages (more than a
decade ago) and don't really feel like learning about it without being able
to test things.

Bugs are:
  - #392743 "Implicit assumptions -&amp;gt; confusion when trying to use printer on
             a Win7 machine"
  - #327093 "Addition of 64-bit info to "Gentoo Samba3/CUPS HOWTO"

Wkr,
Sven Vermeulen


&lt;/pre&gt;</description>
    <dc:creator>Sven Vermeulen</dc:creator>
    <dc:date>2011-12-10T15:39:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3210">
    <title>Supporting CC-BY-SA 3.0 and later versions</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3210</link>
    <description>&lt;pre&gt;Hi guys,                                                                                                                           
                                                                                                                                   
With http://wiki.gentoo.org having their documents as CC-BY-SA 3.0, I                                                              
thought it might be a good idea to work this out for our documents as well.                                                        
That would allow us to "tech-write" stuff that is on the wiki properly, but                                                        
also use the newer (and recommended) version.                                                                                      
                                                                                                                                   
Of course, that won't be done by just making &amp;lt;license /&amp;gt; refer to the 3.0 as                       &lt;/pre&gt;</description>
    <dc:creator>Sven Vermeulen</dc:creator>
    <dc:date>2011-11-27T17:41:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3206">
    <title>Corrections</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3206</link>
    <description>&lt;pre&gt;Hello gentoo-doc,

I found a typo in the Documentation. This is for amd64 and x86.

The error is in the code, "mount --rbind /dev /mnt/gentoo/dev"

The above command, if assumed that the user enters them exactly that way,
would give them an error. It was correctly written as "mount -o bind /dev
/mnt/gentoo/dev" previously.

If I find any other errors, I will let you know.

IRC: DistantStar

Tom
&lt;/pre&gt;</description>
    <dc:creator>Thomas</dc:creator>
    <dc:date>2011-11-26T14:30:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3204">
    <title>documenting emerge-webrsync GPG verification</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3204</link>
    <description>&lt;pre&gt;I've noticed excellent blog post
&amp;lt;http://blog.siphos.be/2011/07/emerge-webrsync-and-gpg-verification/&amp;gt;
but it seems it's still not part of official documentation (e.g.
&amp;lt;http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&amp;amp;chap=1&amp;gt;).

Please consider mentioning the steps from the blog post in the official
docs.

&lt;/pre&gt;</description>
    <dc:creator>Paweł Hajdan, Jr.</dc:creator>
    <dc:date>2011-10-20T08:56:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3193">
    <title>Arm Gentoo Handbook</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3193</link>
    <description>&lt;pre&gt;Hello Team_doc

What currently links to the Gentoo handbook for ARM
is deprecated!

http://www.gentoo.org/doc/en/handbook/handbook-arm.xml?part=1&amp;amp;chap=5

Why not link to this doc?
http://dev.gentoo.org/~armin76/arm/trimslice/install.xml

Lots of new arm netbooks are here and no doubt many different
offerings are on the way!

(Asus E transformer) Genesi Efika MX Smarttop
(Compulab TrimSlice)


thoughts?

hth,
James



&lt;/pre&gt;</description>
    <dc:creator>wireless</dc:creator>
    <dc:date>2011-10-05T18:46:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3191">
    <title>idea for more docs: document new portage features</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3191</link>
    <description>&lt;pre&gt;I just noticed
&amp;lt;http://forums.gentoo.org/viewtopic-t-896728-highlight-.html&amp;gt; and
thought it would be cool to document some of the new portage features.
Now that we have Sven on board, it should be possible!

I think you could ask Zac Medico about some summary of the features
maybe, and then just put some overview in the handbook.

&lt;/pre&gt;</description>
    <dc:creator>Paweł Hajdan, Jr.</dc:creator>
    <dc:date>2011-10-03T03:52:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3179">
    <title>OpenRC tracker "empty"</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3179</link>
    <description>&lt;pre&gt;Guys,

The OpenRC tracker bug (#213988) is currently without open depending bugs.
I'm sure there are still OpenRC "delta's" afloat here and there, so don't
hesitate to bug them on bugzilla (or, even better, just fix them).

Wkr,
Sven Vermeulen


&lt;/pre&gt;</description>
    <dc:creator>Sven Vermeulen</dc:creator>
    <dc:date>2011-09-17T12:48:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3175">
    <title>/etc/conf.d/hwclock and /etc/conf.d/adjkerntz</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3175</link>
    <description>&lt;pre&gt;Well what I want to ask here is how should we aproach this. As things
stand now:
The open rc upgrade guide mentions both (which is ok)
The gentoo bsd guide just refers to adjkerntz (which is ok)
The hand book refers only to hwclock (which is "ok" as long as there
doesn't appears a gentoo-bsd handbook).
Tthe localization guide still refers to the older clock one, here I'd
like to say:

    If,
    for some reason, you need your hardware clock not to be in UTC,
    you will need to edit &amp;lt;path&amp;gt;/etc/conf.d/hwclock&amp;lt;/path&amp;gt; (or if you
    use Gentoo BSD &amp;lt;path&amp;gt;/etc/conf.d/hwclock&amp;lt;/path&amp;gt; and change
    the value of &amp;lt;c&amp;gt;clock&amp;lt;/c&amp;gt; from &amp;lt;c&amp;gt;UTC&amp;lt;/c&amp;gt; to &amp;lt;c&amp;gt;local&amp;lt;/c&amp;gt;.

Other than that I'm working now on updating the localization guide.
&lt;/pre&gt;</description>
    <dc:creator>Francisco Blas Izquierdo Riera (klondike</dc:creator>
    <dc:date>2011-09-11T22:26:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3166">
    <title>Use of link attribute in &lt;guide&gt; tag</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3166</link>
    <description>&lt;pre&gt;Hi guys,

If I look at the XSL files, we do not seem to have a dependency on the
&amp;lt;guide link="..." /&amp;gt; usage anymore (I'm talking about the &amp;lt; at &amp;gt;link attribute).
Running guides without the link tag doesn't seem to break stuff (there are
already quite a few guides without &amp;lt; at &amp;gt;link). However, that doesn't mean there
isn't any breakage outside.

nightmorph suggested me that it might be possible that some translation
teams are using this information within their own infrastructure for
particular reasons.

Can anyone check if they require this tag to be filled in (in the English
guides)? If not, I'll be removing those attributes from the guides in
/doc/en as well as remove references to it from guides such as
xml-guide.xml.

See also bug #379883 as some kind of "tracker" (for those not subscribed to
the list or using a different escalation path ;-)

Wkr,
Sven Vermeulen



&lt;/pre&gt;</description>
    <dc:creator>Sven Vermeulen</dc:creator>
    <dc:date>2011-08-19T17:33:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3163">
    <title>Review of Documentation Policy</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3163</link>
    <description>&lt;pre&gt;Hi guys,

Sorry to barge in like this here, but why not start a nice discussion on
things... Keeps the minds fresh and the activity high (heh, almost sounds
like a bad exercise DVD).

The GDP currently uses the Documentation Policy [1] as its main policy on
documentation development, recruitment, team organization and what not. It
was written a few years ago and has seen some small changes since. However,
like any policy, it should best be reviewed from time to time.

So, what is your take on the policy? Which things need to be changed? What
would you like to see added?

Wkr,
Sven Vermeulen

[1] http://www.gentoo.org/proj/en/gdp/doc/doc-policy.xml



&lt;/pre&gt;</description>
    <dc:creator>Sven Vermeulen</dc:creator>
    <dc:date>2011-08-15T21:23:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3158">
    <title>Dropping in to say hi!</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3158</link>
    <description>&lt;pre&gt;Hi guys

I'm dropping in to say "hi". As you probably know by now, I've rejoined
Gentoo to help out with documentation (yes, you guys) and hardened (those
tin-foil hat folks).

Of course, that means you'll notice a couple of updates on the documentation
as well as me taking on a couple of bugs. I also added myself to the
docs-team alias again.

Wkr,
  Sven Vermeulen


&lt;/pre&gt;</description>
    <dc:creator>Sven Vermeulen</dc:creator>
    <dc:date>2011-08-12T18:10:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3149">
    <title>RFC: PostgreSQL Documentation</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3149</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I think the documentation I've written[1] for PostgreSQL is pretty well
set to be published. I'm submitting it here for a final review.

It's intended to replace the existing postgres-howto.xml.

Some items that have been removed from this version of the documentation
from the old one:
  - No comparison to MySQL
  - Does not instruct users to give the 'postgres' system user a
    password (A potential security risk)
  - Does not instruct users in creating a database and/or role (This is
    better left to the official tutorial, which this doc points to)

[1] http://dev.gentoo.org/~titanofold/postgresql.xml

- - Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iF4EAREIAAYFAk4pc60ACgkQCOhwUhu5AEkqcwD8CIBymIwoEyq2fE0XzW8Mzig2
HkNeAzFFnm7kBMHKmTwA/13grpyqafc4Nb5ouoG9Aszd4RavMoA/YOkrf49gmSEM
=UR79
-----END PGP SIGNATURE-----


&lt;/pre&gt;</description>
    <dc:creator>Aaron W. Swenson</dc:creator>
    <dc:date>2011-07-22T12:57:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3147">
    <title>Few pending handbook updates</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3147</link>
    <description>&lt;pre&gt;Hi guys,

In bug #369841 [1] I have a set of updates to the handbook ready in a single
patch. The patch does include quite a few changes based on end-user feedback
received earlier. If you'd rather see it as separate patches, just yell.

[1] https://bugs.gentoo.org/show_bug.cgi?id=369841

If okay, i'll focus on the bugs associated with the openrc/baselayout-2
tracker [2] so that we can get this openrc/baselayout-2 over with ;-)

[2] https://bugs.gentoo.org/show_bug.cgi?id=213988

Wkr,
Sven Vermeulen


&lt;/pre&gt;</description>
    <dc:creator>Sven Vermeulen</dc:creator>
    <dc:date>2011-06-21T20:45:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3136">
    <title>okupy, a Django rewrite of www.g.o</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3136</link>
    <description>&lt;pre&gt;Hi,
yesterday I read Theo's blog post [1] about his upcoming GSoC project,
which apparently is about using Django for www.g.o, and has some
implications for the way how the GDP works.

I have a few comments/notes that I want to say here. They reflect my
personal opinion, which is based on six years of working with docs. I
have no idea whether they match the opinion of the rest of the GDP.

First of all, a suggestion -- maybe, when you want to do something to
the docs (like change the presentation layer, integrate a WYSIWYG
editor, convert to git from CVS, or stuff like that -- which are all the
objectives of the project [2]), maybe it would be a great idea to
contact the GDP first. There are fine contacts for chatting with us,
either the nice gentoo-doc ML, or the #gentoo-doc IRC channel, or the
docs-team&amp;lt; at &amp;gt;g.o alias. I have no idea whether Theo contacted anyone
directly, but I'm sure I haven't received anything through any of these
channels. That's bad, and it means that there's a communication problem
somewh&lt;/pre&gt;</description>
    <dc:creator>Jan Kundrát</dc:creator>
    <dc:date>2011-06-02T10:13:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.gentoo.documentation/3133">
    <title>handbook needs updates for openrc and baselayout-2</title>
    <link>http://comments.gmane.org/gmane.linux.gentoo.documentation/3133</link>
    <description>&lt;pre&gt;There is a thread on Gentoo Forums about Gentoo Handbook being outdated:
&amp;lt;http://forums.gentoo.org/viewtopic-t-879875-highlight-.html&amp;gt;

I'm not sure if the user is going to file a bug or not, so I just
decided to post here. Please note that more updates would be needed, for
example the syntax for /etc/conf.d/net has changed.

&lt;/pre&gt;</description>
    <dc:creator>Paweł Hajdan, Jr.</dc:creator>
    <dc:date>2011-05-26T14:23:02</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.gentoo.documentation">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.gentoo.documentation</link>
  </textinput>
</rdf:RDF>

