/[gentoo]/xml/htdocs/doc/en/vdr-guide.xml
Gentoo

Diff of /xml/htdocs/doc/en/vdr-guide.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.4 Revision 1.5
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vdr-guide.xml,v 1.4 2006/11/16 04:53:37 nightmorph Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vdr-guide.xml,v 1.5 2007/01/03 00:58:38 nightmorph Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/doc/en/vdr-guide.xml"> 5<guide link="/doc/en/vdr-guide.xml">
6<title>Gentoo Linux VDR Guide</title> 6<title>Gentoo Linux VDR Guide</title>
7 7
9 <mail link="mail@ng-plasmon.de">Norman Golisz</mail> 9 <mail link="mail@ng-plasmon.de">Norman Golisz</mail>
10</author> 10</author>
11<author title="Author"> 11<author title="Author">
12 <mail link="diox@gentoo.org">Dimitry Bradt</mail> 12 <mail link="diox@gentoo.org">Dimitry Bradt</mail>
13</author> 13</author>
14<author title="Author">
15 <mail link="zzam@gentoo.org">Matthias Schwarzott</mail>
16</author>
14<author title="Editor"> 17<author title="Editor">
15 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail> 18 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
16</author> 19</author>
17 20
18<abstract> 21<abstract>
21 24
22<!-- The content of this document is licensed under the CC-BY-SA license --> 25<!-- The content of this document is licensed under the CC-BY-SA license -->
23<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 26<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
24<license/> 27<license/>
25 28
26<version>1.3</version> 29<version>1.4</version>
27<date>2006-11-15</date> 30<date>2007-01-02</date>
28 31
29<chapter> 32<chapter>
30<title>General information to DVB</title> 33<title>General information to DVB</title>
31<section> 34<section>
32<title>What is DVB?</title> 35<title>What is DVB?</title>
86<section> 89<section>
87<title>Configuring the kernel</title> 90<title>Configuring the kernel</title>
88<body> 91<body>
89 92
90<p> 93<p>
91First, we must ensure that your kernel supports DVB and your DVB device. Since 94First, we must ensure that your kernel supports DVB and your DVB device. Since
92kernel version 2.6 the necessary drivers are included. Check your kernel 95kernel version 2.6 the necessary drivers are included. Check your kernel
93configuration and make sure the following options are selected as a static 96configuration and make sure the following options are selected as a static
94driver or as modules. 97driver or as modules.
95</p> 98</p>
96 99
148<section id="kernel_output"> 151<section id="kernel_output">
149<title>Checking the kernel output</title> 152<title>Checking the kernel output</title>
150<body> 153<body>
151 154
152<p> 155<p>
153It's recommended to mark every driver as module, so you are able to add the 156It's recommended to mark every driver as module, so that you can to add the
154required module dynamically, especially if you don't know the module name. If 157required module dynamically, especially if you don't know the module name. If
155you know the module name already, select the driver as built-in driver. Compile 158you know the module name already, select the driver as a built-in driver.
156the kernel, install the modules and boot it. Check to see if your kernel has 159Compile the kernel, install the modules and boot it. Check to see if your kernel
157successfully detected your card by using <c>dmesg</c>. 160has successfully detected your card by using <c>dmesg</c>.
158</p> 161</p>
159 162
160<pre caption="Checking kernel output"> 163<pre caption="Checking kernel output">
161# <i>dmesg | grep DVB</i> 164# <i>dmesg | grep DVB</i>
162<comment>(If you own a TerraTec Cinergy T2, your output might look like this:)</comment> 165<comment>(If you own a TerraTec Cinergy T2, your output might look like this:)</comment>
163DVB: registering new adaptor (TerraTec/qanu USB2.0 Highspeed DVB-T Receiver). 166DVB: registering new adaptor (TerraTec/qanu USB2.0 Highspeed DVB-T Receiver).
164input: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control as /class/input/input2 167input: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control as /class/input/input2
165</pre> 168</pre>
166 169
167<p>
168Now continue with <uri link="#inst_lirc">installing LIRC</uri> if you want to
169use a remote control.
170</p>
171
172</body> 170</body>
173</section> 171</section>
174</chapter> 172</chapter>
175 173
176<chapter id="inst_lirc"> 174<chapter id="inst_vdr">
177<title>Configuring the remote control - LIRC</title> 175<title>Installing VDR</title>
176<section>
177<body>
178
179<p>
180To install VDR, we just emerge it.
181</p>
182
183<pre caption="Installing VDR">
184# <i>emerge vdr</i>
185</pre>
186
187<p>
188Now continue with <uri link="#inst_ir_remote">Installing the Remote Control</uri>.
189</p>
190
191</body>
178<section> 192</section>
193</chapter>
194
195<chapter id="inst_ir_remote">
179<title>Installing LIRC</title> 196<title>Installing the Remote Control</title>
197<section>
198<body>
199
200<p>
201There are at least two ways to control VDR via an infrared remote control. If
202your TV card has an onboard IR receiver you can use <c>vdr-remote</c>.
203Otherwise, you most likely need to use LIRC.
204</p>
205
180<body> 206</body>
207</section>
208<section>
209<title>Installing vdr-remote</title>
210<body>
181 211
212<p>
213We first install the plugin via emerge:
182<p> 214</p>
183If your card can be remotely controlled, you may wish to configure LIRC. LIRC 215
184interprets the pressed keys and returns a name for each one. A program that 216<pre caption="Installing vdr-remote">
185supports LIRC waits for key events and runs the action configured in the config 217# <i>emerge vdr-remote</i>
186file, mostly stored in the config directory of the executing program (e.g. 218# <i>emerge --config vdr-remote</i>
187<c>mplayer</c> loads the file <path>~/.mplayer/lircrc</path>). Before we 219</pre>
188install LIRC, you have to add <c>lirc</c> to your USE flags and add an 220
221<p>
222When using the remote plugin for the IR port on your DVB card everything should
223be fine with the default config. It automatically uses the input device which
224has "dvb" in its name. For more advanced uses take a look at
225<path>/etc/conf.d/vdr.remote</path>.
226</p>
227
228<p>
229Now, continue with <uri link="#video-out">Video Output Methods</uri>.
230</p>
231
232</body>
233</section>
234<section>
235<title>Alternative: installing LIRC</title>
236<body>
237
238<p>
239If your card can be remotely controlled (but you cannot or do not want to use
240<c>vdr-remote</c>), you may wish to configure LIRC. LIRC interprets the pressed
241keys and returns a name for each one. A program that supports LIRC waits for key
242events and runs the action configured in the config file, mostly stored in the
243config directory of the executing program (e.g. <c>mplayer</c> loads the file
244<path>~/.mplayer/lircrc</path>). Before we install LIRC, you have to add
245<c>lirc</c> to your USE flags and add an additional entry to
189additional entry to <path>/etc/make.conf</path>: <c>LIRC_DEVICES</c>. Use <uri 246<path>/etc/make.conf</path>: <c>LIRC_DEVICES</c>. Use <uri
190link="http://www.lirc.org/html/table.html">this list</uri> to find the proper 247link="http://www.lirc.org/html/table.html">this list</uri> to find the proper
191arguments for the option. 248arguments for the option.
192</p> 249</p>
193 250
194<pre caption="Installing LIRC"> 251<pre caption="Installing LIRC">
242<pre caption="Starting lircd"> 299<pre caption="Starting lircd">
243# <i>/etc/init.d/lircd start</i> 300# <i>/etc/init.d/lircd start</i>
244</pre> 301</pre>
245 302
246<p> 303<p>
304Now it should be possible to watch <c>lircd</c> running and decoding key-presses.
305Just run the command <c>irw</c>. Stop it with pressing Ctrl+C when you have
306enough.
307</p>
308
309<pre caption="Testing LIRC">
310# <i>irw</i>
3110000000000001aa2 00 Exit Technisat_TTS35AI.conf
3120000000000001a8d 00 Mute Technisat_TTS35AI.conf
3130000000000000a97 00 OK Technisat_TTS35AI.conf
3140000000000000a97 01 OK Technisat_TTS35AI.conf
3150000000000000a92 00 Menu Technisat_TTS35AI.conf
316</pre>
317
318<p>
247Next, add it to the default runlevel so that it starts automatically at boot. 319Next, add it to the default runlevel so that it starts automatically at boot.
248</p> 320</p>
249 321
250<pre caption="Adding lircd to the default runlevel"> 322<pre caption="Adding lircd to the default runlevel">
251# <i>rc-update add lircd default</i> 323# <i>rc-update add lircd default</i>
252</pre> 324</pre>
253 325
254</body>
255</section>
256</chapter>
257
258<chapter>
259<title>Setting up VDR</title>
260<section>
261<title>Installing VDR</title>
262<body>
263
264<p>
265To install VDR, we just emerge it.
266</p> 326<p>
267 327To be able to use your remote control, you must enable LIRC support in VDR. Add
268<pre caption="Installing VDR">
269# <i>emerge vdr</i>
270</pre>
271
272<p>
273If you want to be able to use your remote control, we have to enable LIRC
274support in VDR. Add the following line to the <path>/etc/conf.d/vdr</path>: 328the following line to <path>/etc/conf.d/vdr</path>:
275</p> 329</p>
276 330
277<pre caption="Enabling support for LIRC"> 331<pre caption="Enabling support for LIRC">
278# <i>nano -w /etc/conf.d/vdr</i> 332# <i>nano -w /etc/conf.d/vdr</i>
279IR_CTRL="lirc" 333IR_CTRL="lirc"
280</pre> 334</pre>
281 335
282<note>
283There's a remote configuration file available at Matthias Schwarzott's <uri
284link="http://dev.gentoo.org/~zzam/remote.conf">devspace</uri>. You will need to
285run <c>chown vdr:vdr</c> on the file to get it working.
286</note>
287
288<p>
289You'll probably want to configure your channels at this point. The VDR project
290provides you with some examples which can be found at
291<path>/usr/share/doc/vdr-analogtv-$version/examples/</path>, as long as you've
292installed &gt;=<c>media-plugins/vdr-analogtv-1.0.00-r1</c>.
293</p>
294
295<p>
296Next, start VDR and add it to the default runlevel:
297</p>
298
299<pre caption="Adding vdr to the default runlevel">
300# <i>/etc/init.d/vdr start</i>
301# <i>rc-update add vdr default</i>
302</pre>
303
304<p>
305Now that the basic installation is over, you need to configure VDR. Switch to
306your output screen and follow the on-screen instructions. VDR asks you to press
307various keys on your remote control to learn the correct key codes. In case you
308don't own a remote control unit, you can use your keyboard. If you only have a
309budget card, you need to install a software output plugin, or <e>softdevice
310plugin</e>. This decodes the stream and offers a device to access.
311</p>
312
313</body> 336</body>
337</section>
338</chapter>
339
340<chapter id="video-out">
341<title>Video Output Methods</title>
314</section> 342<section>
315<section id="softdevice"> 343<body>
316<title>Optional: Installing a softdevice plugin</title> 344
345<p>
346You now need to decide on one (and only one!) of the following video output
347devices which show the picture and the overlayed On Screen Display (OSD).
348</p>
349
317<body> 350</body>
351</section>
352<section id="vdr-dxr3">
353<title>Hardware decoding: full-featured DVB cards</title>
354<body>
318 355
356<p>
357Users of these expensive cards need not install anything else, so you may
358continue with <uri link="#channel_list">configuring your channel list</uri>.
319<p> 359</p>
360
361</body>
362</section>
363<section id="vdr-dxr3">
364<title>Hardware decoding: DXR3/Hollywood+ cards</title>
365<body>
366
367<p>
368To use a DXR3 card for VDR output we need the <c>vdr-dxr3</c> plugin.
369</p>
370
371<pre caption="Installing the plugin">
372# <i>emerge vdr-dxr3</i>
373# <i>echo em8300 &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>
374</pre>
375
376<p>
377em8300-modules needs some configuration that depends on the exact used
378revision of the card.
379</p>
380
381<!--
382<p>
383Because we (the authors) don't own a card that uses the dxr3config, we decided
384to skip this part till we have one at our disposal.
385</p>
386-->
387
388<p>
389Continue with <uri link="#channel_list">configuring your channel list</uri>.
390</p>
391
392</body>
393</section>
394<section id="vdr-pvr350">
395<title>Hardware decoding: PVR350 cards</title>
396<body>
397
398<p>
399As PVR350 cards have an onboard MPEG-Decoder chip we want to make use of that.
400We need to install the <c>vdr-pvr350</c> plugin. If <c>ivtv-driver</c> is not
401yet installed emerge will automatically install it for you. To have the ivtv
402module loaded at boot we add it to
403<path>/etc/modules.autoload.d/kernel-2.6</path>:
404</p>
405
406<pre caption="Installing PVR350-Plugin">
407# <i>emerge vdr-pvr350</i>
408# <i>echo ivtv &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>
409</pre>
410
411<p>
412Continue with <uri link="#channel_list">configuring your channel list</uri>.
413</p>
414
415</body>
416</section>
417<section id="vdr-xineliboutput">
418<title>Software decoding: vdr-softdevice</title>
419<body>
420
421<p>
320To install a softdevice, we have to emerge <c>vdr-softdevice</c>. Don't forget 422To install it, we have to emerge <c>vdr-softdevice</c>. Don't forget
321to configure the plugin. 423to enable the plugin.
322</p> 424</p>
323 425
324<pre caption="Installing the softdevice plugin"> 426<pre caption="Installing the softdevice plugin">
325# <i>emerge vdr-softdevice</i> 427# <i>emerge vdr-softdevice</i>
326# <i>emerge --config vdr-softdevice</i> 428# <i>emerge --config vdr-softdevice</i>
329<p> 431<p>
330To select the proper video and audio output, edit 432To select the proper video and audio output, edit
331<path>/etc/conf.d/vdr.softdevice</path>. 433<path>/etc/conf.d/vdr.softdevice</path>.
332</p> 434</p>
333 435
436<p>
437For now, we will only describe the shm ("shared memory") method. This is already
438enabled in the installed config file (Setting SOFTDEVICE_VIDEO_OUT). Later you
439need to start <c>ShmClient</c> to get a window showing the picture.
440</p>
441
442<note>
443If you do not want to think about a separate keyboard layout for controlling VDR
444with softdevice/shm there is a remote configuration file available at Matthias
445Schwarzott's <uri
446link="http://dev.gentoo.org/~zzam/remote.softdevice-shm.conf">devspace</uri>.
447You will need to copy it to <path>/etc/vdr/remote.conf</path> and run <c>chown
448vdr:vdr</c> on the file to get it working.
449</note>
450
451<p>
452Continue with <uri link="#channel_list">configuring your channel list</uri>.
453</p>
454
334</body> 455</body>
335</section> 456</section>
336<section id="vdr-xineliboutput"> 457<section id="vdr-xineliboutput">
337<title>Optional: Alternate installation of a softdevice plugin</title> 458<title>Software decoding: vdr-xineliboutput</title>
338<body> 459<body>
339 460
340<p> 461<p>
341Some people prefer to use <c>vdr-xineliboutput</c>, because it can also work 462Some people prefer to use <c>vdr-xineliboutput</c>, because it can also work
342remotely. We'll now teach you how to configure <c>vdr-xineliboutput</c> on your 463remotely. We'll now teach you how to configure <c>vdr-xineliboutput</c> on your
347# <i>emerge vdr-xineliboutput</i> 468# <i>emerge vdr-xineliboutput</i>
348# <i>emerge --config vdr-xineliboutput</i> 469# <i>emerge --config vdr-xineliboutput</i>
349</pre> 470</pre>
350 471
351<p> 472<p>
352Adding command line options at this point is crucial for your softdevice to 473Adding command line options at this point is crucial for xineliboutput to work.
353work. For more options, see <c>vdr --help</c>. 474For more options, see <c>vdr --help</c>.
354</p> 475</p>
355 476
356<pre caption="Adding command line options to /etc/conf.d/vdr.xineliboutput"> 477<pre caption="Adding command line options to /etc/conf.d/vdr.xineliboutput">
357_EXTRAOPTS="--local=none --remote=37890" 478_EXTRAOPTS="--local=none --remote=37890"
358</pre> 479</pre>
366<pre caption="Editing /etc/vdr/svdrphosts.conf"> 487<pre caption="Editing /etc/vdr/svdrphosts.conf">
367<comment>(The proper syntax is: IP-Address[/Netmask])</comment> 488<comment>(The proper syntax is: IP-Address[/Netmask])</comment>
368127.0.0.1 <comment>(always accept localhost)</comment> 489127.0.0.1 <comment>(always accept localhost)</comment>
369192.168.1.0/24 <comment>(any host on the local net)</comment> 490192.168.1.0/24 <comment>(any host on the local net)</comment>
370#204.152.189.113 <comment>(a specific host)</comment> 491#204.152.189.113 <comment>(a specific host)</comment>
371#0.0.0.0/0 <comment>(any host on any net (USE THIS WITH CARE!))</comment> 492#0.0.0.0/0 <comment>(any host on any net - USE THIS WITH CARE!)</comment>
372</pre> 493</pre>
373 494
374<p>
375You must restart VDR for the changes to take effect:
376</p> 495<p>
496If you only want to use <c>vdr-xineliboutput</c> to view the picture
497on the same PC running VDR you can now
498<uri link="#channel_list">continue with configuring your channel-list</uri>.
499</p>
377 500
501<p>
502Otherwise, you now simply <c>emerge media-plugins/vdr-xineliboutput</c> on your
503client:
504</p>
505
506<pre caption="Client setup">
507# <i>emerge vdr-xineliboutput</i>
508</pre>
509
510<p>
511Later (after having started VDR) you will use the command <c>vdr-sxfe
512xvdr://hostname</c> to connect to VDR and view its picture and OSD.
513</p>
514
515<p>
516Continue with <uri link="#channel_list">configuring your channel list</uri>.
517</p>
518
519<note>
520There is also a plugin which just simulates the existance of a real
521output device (<c>vdr-dummydevice</c>) for some fancy uses like record-only
522servers, but that is more advanced than a normal VDR setup.
523</note>
524
525</body>
526</section>
527</chapter>
528
529<chapter id="channel_list">
530<title>Creating a Channel List</title>
531<section>
532<body>
533
534<p>
535To make VDR really useful you need to create an appropriate channel list.
536</p>
537
538<p>
539There is more than one way to get a working list of channels (besides
540downloading one). The channel list installed by default is for DVB-S reception
541on Astra on 19.2°E.
542</p>
543
544</body>
545</section>
546<section>
547<title>Using dvbscan from linuxtv-dvb-apps</title>
548<body>
549
550<pre caption="Installing linuxtv-dvb-apps">
551# <i>emerge linuxtv-dvb-apps</i>
552</pre>
553
554<p>
555Find the correct frequency list for your region and type of reception. These
556files are stored under <path>/usr/share/dvb/scan</path>. For reception with
557DVB-T in Germany, Region Nuernberg you need to use
558<path>/usr/share/dvb/scan/dvb-t/de-Nuernberg</path>.
559</p>
560
561<pre caption="Scanning with dvbscan">
562$ <i>dvbscan -o vdr /usr/share/dvb/scan/dvb-t/de-Nuernberg &gt; /etc/vdr/channels.conf</i>
563</pre>
564
565</body>
566</section>
567<section>
568<title>Using vdr-reelchannelscan</title>
569<body>
570
571<p>
572First, delete the contents of the existing channel list.
573</p>
574
575<pre caption="Cleaning old channel-list">
576# <i>rm /etc/vdr/channels.conf</i>
577</pre>
578
579<pre caption="Installing and activating vdr-reelchannelscan">
580# <i>emerge vdr-reelchannelscan</i>
581# <i>emerge --config vdr-reelchannelscan</i>
582</pre>
583
584</body>
585</section>
586<section>
587<title>Channels for systems using vdr-analogtv</title>
588<body>
589
590<p>
591You'll probably want to configure your channels at this point. The VDR project
592provides you with some examples which can be found at
593<path>/usr/share/doc/vdr-analogtv-$version/examples/</path>, as long as you've
594installed &gt;=<c>media-plugins/vdr-analogtv-1.0.00-r1</c>.
595</p>
596
597</body>
598</section>
599</chapter>
600
601<chapter>
602<title>Starting VDR</title>
603<section>
604<body>
605
606<p>
607After having all basic software parts ready on the system you need to
608configure VDR with its OSD.
609</p>
610
611<p>
612If you use a hardware decoder for picture output you should switch on the
613connected TV now. If you use software output the client for this must be started
614after VDR.
615</p>
616
617<p>
618First, you should learn your key definitions; that is, connecting keys on your
619remote control to VDR's internal commands.
620</p>
621
622<note>
623Just in case you need to edit the keyboard configuration, or (more likely) want
624to delete it to go back to learning the keys: VDR stores its key-definitions in
625<path>/etc/vdr/remote.conf</path>.
626</note>
627
628<p>
629We begin with starting VDR:
630</p>
631
378<pre caption="Restarting VDR"> 632<pre caption="Starting VDR">
379# <i>/etc/init.d/vdr restart</i> 633# <i>/etc/init.d/vdr start</i>
380* Stopping vdr ... [ ok ]
381* Preparing start of vdr: 634* Preparing start of vdr:
382* config files ... [ ok ] 635* config files ... [ ok ]
383* Waiting for prerequisites (devices nodes etc.) ... [ ok ] 636* Waiting for prerequisites (devices nodes etc.) ... [ ok ]
384* Starting vdr ... [ ok ] 637* Starting vdr ... [ ok ]
385* Waiting for working vdr ... [ ok ] 638* First start of vdr: No check for running vdr possible
386</pre> 639* until control device (remote/keyboard) keys are learnt!
387
388<p>
389Now, simply <c>emerge media-plugins/vdr-xineliboutput</c> on your client, and
390start it.
391</p> 640</pre>
392 641
393<pre caption="Client setup"> 642<note>
394# <i>emerge vdr-xineliboutput</i> 643Users of software decoders should now start the client program that opens the
644window to show the TV picture and the OSD.
645</note>
646
647<pre caption="Activating the software decoder for the client">
648<comment>(For users of vdr-softdevice)</comment>
649# <i>ShmClient</i>
650<comment>(For users of vdr-xineliboutput)</comment>
395$ <i>vdr-sxfe xvdr://hostname</i> 651# <i>vdr-sxfe xvdr://hostname</i>
396</pre> 652</pre>
397 653
398<p>
399Sit back and enjoy your new video streaming capabilities. :)
400</p> 654<p>
655The most useful keys for VDR are:
656</p>
657<ul>
658 <li>Cursor keys (Left/Right/Up/Down)</li>
659 <li>Menu/Exit/Ok</li>
660 <li>Colors (Red/Green/Yellow/Blue)</li>
661 <li>Number keys (0-9)</li>
662</ul>
663
664<impo>
665If you don't have many keys, make sure to assign these. (Some remotes have
666Play/Pause/etc. on the same keys as the colors, so use them for the colors).
667</impo>
668
669<p>
670Now that the basic installation is over, you need to configure VDR. Switch to
671your output screen and follow the on-screen instructions. VDR asks you to press
672various keys on your remote control to learn the correct key codes. If you don't
673own a remote control, you can use your keyboard.
674</p>
675
676<!--<p>
677TODO: Add a configuration howto for remote controls etc.
678</p>-->
679
680<p>
681Now you can add the VDR initscript to the default runlevel to get it started
682every time your computer boots up.
683</p>
684
685<pre caption="Adding vdr to the default runlevel">
686# <i>rc-update add vdr default</i>
687</pre>
688
689</body>
690</section>
691</chapter>
692
693<chapter>
694<title>Troubleshooting</title>
695<section>
696<body>
401 697
402<note> 698<note>
403If you need any help, you can always ask someone in <uri 699If you need any help, you can always ask someone in <uri
404link="irc://irc.freenode.org/gentoo-vdr">#gentoo-vdr</uri>, or look around on 700link="irc://irc.freenode.org/gentoo-vdr">#gentoo-vdr</uri>, or look around on
405our <uri link="http://forums.gentoo.org/">forums</uri>. 701our <uri link="http://forums.gentoo.org/">forums</uri>.

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.5

  ViewVC Help
Powered by ViewVC 1.1.20