4 Textile 2009-09-08T10:27:59+02:00 10 1333 en 0 1 howto_same_look_for_qt_gtk2_and_gtk1_applications_on_gentoo queued

This manual solves the problem with different looks of Qt, GTK2 and GTK1. This will help if you are using GTK applications from KDE or Qt applications from Gnome.

2009-09-08T10:27:59+02:00 10 http://distro.ibiblio.org/pub/linux/distributions/amigolinux/download/DeskTop/Themes/HOWTO-Same-look-QT-GTK2-and-GTK1-apps-Gentoo.html 1 Textile 2009-09-08T10:27:40+02:00 10 1332 en 0 1 howto_same_look_for_qt_gtk2_and_gtk1_applications_on_gentoo queued

This manual solves the problem with different looks of Qt, GTK2 and GTK1. This will help if you are using GTK applications from KDE or Qt applications from Gnome.

2009-09-08T10:27:40+02:00 10 http://distro.ibiblio.org/pub/linux/distributions/amigolinux/download/DeskTop/Themes/HOWTO-Same-look-QT-GTK2-and-GTK1-apps-Gentoo.html 4 <p style="color:blue;margin:30px;">Tin Hat boots from CD, or optionally a pen drive, but it is not a LiveCD. It does not mount any file system from CD via unionfs or otherwise. Rather, Tin Hat is a massive image (approx. 2.3GB) which loads into tmpfs upon booting. One pays the prices of long boot times (5 minutes off CD, 2 minutes off pen drives), but the advantage afterwords is that there are no delays going back to the CD when starting applications. Needless to say, this has some rather extreme advantages and disadvantages, making Tin Hat a rather particular distribution.</p> <p><a href="http://opensource.dyc.edu/tinhat">Tin Hat</a></p> <p><a href="http://opensource.dyc.edu/tinhat-documentation">Documentation</a></p> <p><a href="http://opensource.dyc.edu/node/221">Tin Hat Screenshots</a></p> <p><a href="http://opensource.dyc.edu/tinhat-downloads">Download</a></p> Textile p{color:blue;margin:30px}. Tin Hat boots from CD, or optionally a pen drive, but it is not a LiveCD. It does not mount any file system from CD via unionfs or otherwise. Rather, Tin Hat is a massive image (approx. 2.3GB) which loads into tmpfs upon booting. One pays the prices of long boot times (5 minutes off CD, 2 minutes off pen drives), but the advantage afterwords is that there are no delays going back to the CD when starting applications. Needless to say, this has some rather extreme advantages and disadvantages, making Tin Hat a rather particular distribution. "Tin Hat":http://opensource.dyc.edu/tinhat "Documentation":http://opensource.dyc.edu/tinhat-documentation "Tin Hat Screenshots":http://opensource.dyc.edu/node/221 "Download":http://opensource.dyc.edu/tinhat-downloads 2009-07-29T11:15:23+02:00 69 1046 en 0 10 tin_hat 2009-07-31T00:38:32+02:00 published

Tin Hat is a Linux distribution derived from hardened Gentoo which aims to provide a very secure, stable and fast Desktop environment that lives purely in RAM.

2009-12-06T01:19:45+01:00 311 http://opensource.dyc.edu/tinhat 9 <h3>Introduction</h3> <p>Sometimes through over zealous unmasking of packages, sys-libs/glibc can be upgraded to a version not compatible with other bits of software. A particular version of glibc might be needed for certain 3rd party or hardware vendor tools. It could also be for consistency across a fleet of servers so that binary packages are more compatible.</p> <p><a href="http://gentoo-portage.com/sys-libs/glibc">Downgrade Glibc</a></p> Textile h3. Introduction Sometimes through over zealous unmasking of packages, sys-libs/glibc can be upgraded to a version not compatible with other bits of software. A particular version of glibc might be needed for certain 3rd party or hardware vendor tools. It could also be for consistency across a fleet of servers so that binary packages are more compatible. "Downgrade Glibc":http://gentoo-portage.com/sys-libs/glibc 2009-05-18T20:40:43+02:00 182 785 en 0 7 downgrade_glibc 2009-05-19T12:58:07+02:00 published

A safe and tested method of downgrading glibc from ACCEPT_KEYWORDS in make.conf

2009-05-21T19:12:11+02:00 10 http://en.gentoo-wiki.com/wiki/Downgrade_Glibc 4 <p>The needed printer-files are located at: http://software.canon-europe.com/software/0024302.asp</p> Textile The needed printer-files are located at: http://software.canon-europe.com/software/0024302.asp 2009-04-29T21:55:42+02:00 10 704 en 0 3 gentoo_canon_pixma_series 2009-05-18T08:47:43+02:00 published

A howto for Canon printers

2009-05-18T10:47:45+02:00 1 http://en.gentoo-wiki.com/wiki/Canon_Pixma_Series 4 Textile 2009-03-23T08:50:48+01:00 10 540 en 0 5 gnome_replace_gnome_screensaver_with_xscreensaver 2009-03-24T16:51:43+01:00 published

Gnome: Replace gnome-screensaver with xscreensaver

2009-04-05T18:25:14+02:00 108 http://ubuntuforums.org/showthread.php?t=195557 1 If an error occurs starting the gnome-settings-daemon, then try this: <pre>/usr/libexec/gnome-settings-daemon --no-daemon 2 The program 'gnome-settings-daemon' received an X Window System error. 3 This probably reflects a bug in the program. 4 The error was 'BadClass, invalid event class'. 5 (Details: serial 159 error_code 184 request_code 150 minor_code 6) 6 (Note to programmers: normally, X errors are reported asynchronously; 7 that is, you will receive the error a while after causing it. 8 To debug your program, run it with the --sync command line 9 option to change this behavior. You can then get a meaningful 10 backtrace from your debugger if you break on the gdk_x_error() function.) 11 [1237714027,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application</pre> <a href="http://bugs.gentoo.org/show_bug.cgi?id=256016#c6">Solution</a> If an error occurs starting the gnome-settings-daemon, then try this: [code]/usr/libexec/gnome-settings-daemon --no-daemon 2 The program 'gnome-settings-daemon' received an X Window System error. 3 This probably reflects a bug in the program. 4 The error was 'BadClass, invalid event class'. 5 (Details: serial 159 error_code 184 request_code 150 minor_code 6) 6 (Note to programmers: normally, X errors are reported asynchronously; 7 that is, you will receive the error a while after causing it. 8 To debug your program, run it with the --sync command line 9 option to change this behavior. You can then get a meaningful 10 backtrace from your debugger if you break on the gdk_x_error() function.) 11 [1237714027,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application[/code] [url=http://bugs.gentoo.org/show_bug.cgi?id=256016#c6]Solution[/url] BBCode 2009-03-22T10:56:35+01:00 10 539 en 0 4 gentoo_gnome_settings_daemon_does_not_start 2009-03-23T07:58:35+01:00 published

If an error occurs starting the gnome-settings-daemon, then try this:

2009-03-24T17:50:08+01:00 1 4 Textile 2008-12-20T19:14:42+01:00 4 486 en 0 6 enable_real_media_support_on_gentoo_linux 2008-12-23T00:00:59+01:00 published

How to enable real media support on Gentoo. It's disabled by default.

2009-01-02T04:38:00+01:00 1 http://forums.gentoo.org/viewtopic-t-713051.html 4 <p>emerge&#8212;keep-going</p> <p>After installation it will give you a short summary of failed packages.</p> Textile emerge --keep-going After installation it will give you a short summary of failed packages. 2008-11-13T19:09:20+01:00 4 475 en 0 4 gentoo_linux_emerge_all_packages_at_once_even_with_failures 2009-03-18T05:47:54+01:00 published

emerge --keep-going

2009-03-24T17:50:12+01:00 1 4 Textile 2008-07-31T14:40:13+02:00 10 359 en 0 6 gentoo_printing_to_a_shared_windows_xp_printer_via_cups 2008-08-03T14:35:51+02:00 published

This tutorial describes how to print from a Gentoo-Linux computer to a printer, that is shared at a Windows XP system, using CUPS (Common UNIX Printing System)

2008-09-10T02:11:51+02:00 107 http://forums.gentoo.org/viewtopic.php?t=88582&highlight=windows+share+printer 4 <h2>Symptom</h2> <p>Folgende Fehlermeldung kann viele Ursachen haben, aber sie tritt vor allem auch auf, wenn man binutils mit emerge -C binutils deinstalliert hat.</p> <pre> <code> checking for C compiler default output file name... configure: error: C compiler cannot create executables </code> </pre> <h2>Lösung</h2> <p>Es wird ein vorkompiliertes Binärpaket installiert:</p> <pre> <code> mkdir -p $(portageq envvar PKGDIR)/All cd $(portageq envvar PKGDIR)/All # Für amd64: wget http://tinderbox.dev.gentoo.org/default-linux/amd64/sys-devel/binutils-2.18-r3.tbz2 # Für x86: wget http://tinderbox.dev.gentoo.org/default-linux/x86/sys-devel/binutils-2.18-r3.tbz2 emerge -K binutils </code> </pre> <p>Danach sollte man nochmals binutils emergen, damit ein an das System angepasstes binutils gebaut wird:</p> <pre> <code> emerge binutils </code> </pre> Textile h2. Symptom p. Folgende Fehlermeldung kann viele Ursachen haben, aber sie tritt vor allem auch auf, wenn man binutils mit emerge -C binutils deinstalliert hat. <pre> <code> checking for C compiler default output file name... configure: error: C compiler cannot create executables </code> </pre> h2. Lösung p. Es wird ein vorkompiliertes Binärpaket installiert: <pre> <code> mkdir -p $(portageq envvar PKGDIR)/All cd $(portageq envvar PKGDIR)/All # Für amd64: wget http://tinderbox.dev.gentoo.org/default-linux/amd64/sys-devel/binutils-2.18-r3.tbz2 # Für x86: wget http://tinderbox.dev.gentoo.org/default-linux/x86/sys-devel/binutils-2.18-r3.tbz2 emerge -K binutils </code> </pre> p. Danach sollte man nochmals binutils emergen, damit ein an das System angepasstes binutils gebaut wird: <pre> <code> emerge binutils </code> </pre> 2008-07-30T13:32:48+02:00 1 356 en 0 6 gentoo_binutils_deinstalliert_hier_die_rettung 2009-04-05T15:59:16+02:00 published

Sollte man es aus irgendeinem Grund (wir reden lieber nicht darüber) geschafft haben, das für ein funktionierendes Gentoo-System essenzielle Paket binutils zu deinstallieren, dann sollte man diesem Trick folgen.

2009-04-16T04:43:43+02:00 111 4 Textile 2008-06-23T13:19:36+02:00 81 287 en 0 6 gentoo_booting_encrypted_system_from_usb_stick 2008-06-23T13:16:44+02:00 published

A tutorial that shows you how to encrypt the entire hard drive with LUKS, partition it with LVM, and boot it from USB stick. All done manually, but it follows the KISS principle (tries to keep things as simple as possible). If you want a no-frills, do it yourself guide on how to encrypt your entire hard disk and boot it from an USB stick, this article may be of use to you.

2008-09-25T19:54:38+02:00 111 http://www.gentoo-wiki.com/Booting_encrypted_system_from_USB_stick 4 #<Comment:0x2ae48550f6d8>#<Comment:0x2ae48550f0e8> <p>emerge has the functionality to resume from the next package in line:</p> <pre> <code> emerge kde-meta # just an example emerge --resume --skipfirst </code> </pre> <p>If you do the following, a few more packages would be emerged unattended if a compile error occurs:</p> <pre> <code> emerge kde-meta ; emerge --resume --skipfirst ; emerge --resume --skipfirst ; emerge --resume-skipfirst </code> </pre> <p>Obviously, this isn&#8217;t the perfect solution, so we should use an <em>until loop</em>:</p> <pre> <code> emerge kde-meta || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done </code> </pre> <p>This way, the emerge is resumed until no further packages can be compiled successfully. When you wake up the next morning, you should check which packages failed with <em>emerge -pv kde-meta</em>.</p> Textile p. emerge has the functionality to resume from the next package in line: <pre> <code> emerge kde-meta # just an example emerge --resume --skipfirst </code> </pre> p. If you do the following, a few more packages would be emerged unattended if a compile error occurs: <pre> <code> emerge kde-meta ; emerge --resume --skipfirst ; emerge --resume --skipfirst ; emerge --resume-skipfirst </code> </pre> p. Obviously, this isn't the perfect solution, so we should use an _until loop_: <pre> <code> emerge kde-meta || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done </code> </pre> p. This way, the emerge is resumed until no further packages can be compiled successfully. When you wake up the next morning, you should check which packages failed with _emerge -pv kde-meta_. 2008-06-16T18:13:13+02:00 1 265 en 0 5 gentoo_resume_emerge_automatically 2008-06-16T16:45:43+02:00 published

You know that: you entered something like emerge kde-meta , let it compile over-night only to realize the next morning that one of the first packages stopped the whole show with an error message. This trick might be a relieve.

2008-06-24T05:17:15+02:00 69 4 <p>Every Gentoo user knows the helpful tool <em>genlop</em>, the emerge.log parser. With it, you can get the merge time of previously installed packages and the estimated merge time of a currently running emerge. Not everyone knows that it is also possible to get the estimated merge time for new packages.</p> <p>Here, I&#8217;m emerging a new package that has never been installed before on my machine. <em>genlop -c</em> alone returns <strong><span class="caps">ETA</span>: unknown</strong>, but with the additional option <strong>-q</strong> it queries an external database and returns a (very rough) estimation:</p> <pre> <code> noname ~ # genlop -c Currently merging 1 out of 2 * app-admin/hddtemp-0.3_beta15-r3 current merge time: 4 seconds. ETA: unknown. noname ~ # genlop -cq Currently merging 1 out of 2 * app-admin/hddtemp-0.3_beta15-r3 current merge time: 8 seconds. ETA: any time now. </code> </pre> <p>This also works with the <strong>-p</strong> option, to get the estimated merge/update time of a pretending emerge:</p> <pre> <code> noname ~ # emerge -pv hddtemp | genlop -p These are the pretended packages: (this may take a while; wait...) [ebuild N ] app-admin/hddtemp-0.3_beta15-r3 USE="nls" 0 kB !!! Error: couldn't get previous merge of hddtemp; skipping... !!! Error: hddtemp never merged; estimated time unknown. noname ~ # emerge -pv hddtemp | genlop -pq These are the pretended packages: (this may take a while; wait...) [ebuild N ] app-admin/hddtemp-0.3_beta15-r3 USE="nls" 0 kB Estimated update time: less than a minute. </code> </pre> <p>You can find more Gentoo tricks <a href="http://howflow.com/tags/gentoo">here</a></p> Textile p. Every Gentoo user knows the helpful tool _genlop_, the emerge.log parser. With it, you can get the merge time of previously installed packages and the estimated merge time of a currently running emerge. Not everyone knows that it is also possible to get the estimated merge time for new packages. p. Here, I'm emerging a new package that has never been installed before on my machine. _genlop -c_ alone returns *ETA: unknown*, but with the additional option *-q* it queries an external database and returns a (very rough) estimation: <pre> <code> noname ~ # genlop -c Currently merging 1 out of 2 * app-admin/hddtemp-0.3_beta15-r3 current merge time: 4 seconds. ETA: unknown. noname ~ # genlop -cq Currently merging 1 out of 2 * app-admin/hddtemp-0.3_beta15-r3 current merge time: 8 seconds. ETA: any time now. </code> </pre> p. This also works with the *-p* option, to get the estimated merge/update time of a pretending emerge: <pre> <code> noname ~ # emerge -pv hddtemp | genlop -p These are the pretended packages: (this may take a while; wait...) [ebuild N ] app-admin/hddtemp-0.3_beta15-r3 USE="nls" 0 kB !!! Error: couldn't get previous merge of hddtemp; skipping... !!! Error: hddtemp never merged; estimated time unknown. noname ~ # emerge -pv hddtemp | genlop -pq These are the pretended packages: (this may take a while; wait...) [ebuild N ] app-admin/hddtemp-0.3_beta15-r3 USE="nls" 0 kB Estimated update time: less than a minute. </code> </pre> p. You can find more Gentoo tricks "here":http://howflow.com/tags/gentoo 2008-06-16T01:32:54+02:00 1 260 en 0 5 gentoo_estimated_merge_time_for_previously_not_installed_packages 2008-06-16T01:40:54+02:00 published

Tiny but handy trick to get the estimated merge time for packages which have never been installed before.

2008-06-29T17:36:26+02:00 4 4 #<Comment:0x2ae4854ee050>#<Comment:0x2ae4854eda88> <h2>Problem</h2> <p>After unpacking the stage3 tar-ball, editing the <span class="caps">CHOST</span> in /etc/make.conf, one of the first emerge stops with an error message <em>like</em> this:</p> <pre> <code> g++: /usr/lib/gcc/i486-pc-linux-gnu/4.1.1/../../../crti.o: No such file or directory g++: /usr/lib/gcc/i486-pc-linux-gnu/4.1.1/crtbeginS.o: No such file or directory g++: /usr/lib/gcc/i486-pc-linux-gnu/4.1.1/crtendS.o: No such file or directory g++: /usr/lib/gcc/i486-pc-linux-gnu/4.1.1/../../../crtn.o: No such file or directory </code> </pre> <p>Basically, the compiler can&#8217;t find some of its object files.</p> <h2>Solution</h2> <p>I&#8217;m sorry, but the best solution is to start from scratch, reformat your partitions and this time take <strong>really good care</strong> to download the <strong>correct</strong> stage3 tar-ball! If you want to have a <span class="caps">CHOST</span>=&#8221;i686-pc-linux-gnu&#8221;, you shouldn&#8217;t download the x86 version of the stage3 tar-ball. Nowadays, the i686-stage3 is the best choice for most 32 bit systems. The current file is called <strong>stage3-i686-2007.0.tar.bz2</strong> and the beta-version is called <strong>stage3-i686-2008.0_beta2.tar.bz2</strong>.</p> <p>Of course you could try to unpack the correct stage3 over the wrong installation, but there is absolutely no guarantee that it&#8217;ll work flawlessly. Start from scratch as long as you haven&#8217;t finished the Gentoo installation.</p> Textile h2. Problem p. After unpacking the stage3 tar-ball, editing the CHOST in /etc/make.conf, one of the first emerge stops with an error message _like_ this: <pre> <code> g++: /usr/lib/gcc/i486-pc-linux-gnu/4.1.1/../../../crti.o: No such file or directory g++: /usr/lib/gcc/i486-pc-linux-gnu/4.1.1/crtbeginS.o: No such file or directory g++: /usr/lib/gcc/i486-pc-linux-gnu/4.1.1/crtendS.o: No such file or directory g++: /usr/lib/gcc/i486-pc-linux-gnu/4.1.1/../../../crtn.o: No such file or directory </code> </pre> p. Basically, the compiler can't find some of its object files. h2. Solution p. I'm sorry, but the best solution is to start from scratch, reformat your partitions and this time take *really good care* to download the *correct* stage3 tar-ball! If you want to have a CHOST="i686-pc-linux-gnu", you shouldn't download the x86 version of the stage3 tar-ball. Nowadays, the i686-stage3 is the best choice for most 32 bit systems. The current file is called *stage3-i686-2007.0.tar.bz2* and the beta-version is called *stage3-i686-2008.0_beta2.tar.bz2*. p. Of course you could try to unpack the correct stage3 over the wrong installation, but there is absolutely no guarantee that it'll work flawlessly. Start from scratch as long as you haven't finished the Gentoo installation. 2008-06-15T20:56:58+02:00 1 259 en 0 3 gentoo_installation_and_crti_o_no_such_file_or_directory 2008-06-22T21:15:00+02:00 published

If you get the error message 'crti.o: No such file or directory' or something similar while you're installing Gentoo, here is the explaination.

2008-06-22T23:15:00+02:00 16 4 <h2>Prerequisites</h2> <p>If you don&#8217;t have the <strong>bash-completion</strong> USE flag set, please do so now in your /etc/make.conf. After that, you have to rebuild the affected packages with the following command:</p> <pre> <code> emerge -uN world </code> </pre> <h2>Installation</h2> <p>We now have to install two packages: <strong>bash-completion</strong> (<em>Programmable Completion for bash</em>) and <strong>gentoo-bashcomp</strong> (<em>Gentoo-specific bash command-line completions (emerge, ebuild, equery, etc)</em>):</p> <pre> <code> emerge bash-completion gentoo-bashcomp </code> </pre> <p>The bash-completion package tells you to add a line to the <strong>~/.bashrc</strong>. We want to have it system-wide, so let&#8217;s add it to the file <strong>/etc/bash/bashrc</strong>:</p> <pre> <code> echo "[[ -f /etc/profile.d/bash-completion ]] &#38;&#38; source /etc/profile.d/bash-completion" &gt;&gt;/etc/bash/bashrc source /etc/bash/bashrc </code> </pre> <h2>Configuration</h2> <p>To disable the portage bash-completion for any user, except <em>root</em>, execute the following commands:</p> <pre> <code> eselect bashcomp disable --global gentoo eselect bashcomp enable gentoo source /etc/bash/bashrc </code> </pre> <h2>Usage</h2> <p>If everything went well, we can now try out the new feature:</p> <pre> <code> emerge ap&lt;tab&gt; emerge app-&lt;tab&gt;&lt;tab&gt; emerge app-t&lt;tab&gt; emerge app-text/&lt;tab&gt;&lt;tab&gt; emerge app-text/pi&lt;tab&gt; emerge app-text/pinfo </code> </pre> <p>For more Gentoo tricks, click <a href="http://howflow.com/tags/gentoo">here</a></p> Textile h2. Prerequisites p. If you don't have the *bash-completion* USE flag set, please do so now in your /etc/make.conf. After that, you have to rebuild the affected packages with the following command: <pre> <code> emerge -uN world </code> </pre> h2. Installation p. We now have to install two packages: *bash-completion* (_Programmable Completion for bash_) and *gentoo-bashcomp* (_Gentoo-specific bash command-line completions (emerge, ebuild, equery, etc)_): <pre> <code> emerge bash-completion gentoo-bashcomp </code> </pre> p. The bash-completion package tells you to add a line to the *~/.bashrc*. We want to have it system-wide, so let's add it to the file */etc/bash/bashrc*: <pre> <code> echo "[[ -f /etc/profile.d/bash-completion ]] && source /etc/profile.d/bash-completion" >>/etc/bash/bashrc source /etc/bash/bashrc </code> </pre> h2. Configuration p. To disable the portage bash-completion for any user, except _root_, execute the following commands: <pre> <code> eselect bashcomp disable --global gentoo eselect bashcomp enable gentoo source /etc/bash/bashrc </code> </pre> h2. Usage p. If everything went well, we can now try out the new feature: <pre> <code> emerge ap<tab> emerge app-<tab><tab> emerge app-t<tab> emerge app-text/<tab><tab> emerge app-text/pi<tab> emerge app-text/pinfo </code> </pre> p. For more Gentoo tricks, click "here":http://howflow.com/tags/gentoo 2008-06-01T18:17:10+02:00 1 217 en 0 7 gentoo_enable_bash_tab_completion_for_portage_tools 2008-06-02T01:30:32+02:00 published

If you like the bash tab-completion for files and directories, you might try out this trick to enable tab-completion for your portage tools (emerge, equery, revdep-rebuild, ...).

2009-04-18T04:19:55+02:00 69 4 Textile 2008-05-26T11:35:48+02:00 37 200 en 0 9 updating_microcode_on_intel_processors 2008-05-26T16:17:04+02:00 published

This is a short howto about updating the intel processor microcode with gentoo.

2008-09-06T12:37:19+02:00 111 http://psykil.livejournal.com/324031.html 4 #<Comment:0x2ae4854c8850>#<Comment:0x2ae4854c8260> <h2>Error Message</h2> <pre> <code> (chroot) livecd / # etc-update diff: %file1: No such file or directory diff: %/var/tmp/etc-update-11759/.diff-test-2: No such file or directory ERROR: 'diff -uN %file1 %file2' does not seem to work, aborting </code> </pre> <h2>Solution</h2> <p>Just don&#8217;t run etc-update until at least the system is fully emerged. I told you, the solution is simple but Gentoo newbies can be very confused when they encounter the mentioned error message.</p> Textile h2. Error Message <pre> <code> (chroot) livecd / # etc-update diff: %file1: No such file or directory diff: %/var/tmp/etc-update-11759/.diff-test-2: No such file or directory ERROR: 'diff -uN %file1 %file2' does not seem to work, aborting </code> </pre> h2. Solution p. Just don't run etc-update until at least the system is fully emerged. I told you, the solution is simple but Gentoo newbies can be very confused when they encounter the mentioned error message. 2008-05-23T17:40:27+02:00 1 196 en 0 3 gentoo_installation_diff_error_message 2008-05-27T20:50:09+02:00 published

While installing Gentoo and doing an etc-update in between package updates, the error message "diff: %file1: No such file or directory" shows up. Here the "solution". Well, it's just a tiny trick.

2008-06-01T17:30:16+02:00 1 4 <p>With this small snippet a bash code, you should be able to easily sort <strong><em>/etc/portage/package.*</em></strong> :</p><p>&nbsp;</p><blockquote><pre>CONFIGDIR=&quot;/etc/portage&quot;<br />for i in keywords mask unmask use<br />do<br />&nbsp; [[ -f ${CONFIGDIR}/package.${i} ]] &amp;&amp; {<br />&nbsp;&nbsp;&nbsp; TMPFILE=$(mktemp)<br />&nbsp;&nbsp;&nbsp; mv ${CONFIGDIR}/package.${i} ${CONFIGDIR}/package.${i}.backup<br />&nbsp;&nbsp;&nbsp; sort -g &lt; ${CONFIGDIR}/package.${i}.backup &gt; ${TMPFILE}<br />&nbsp;&nbsp;&nbsp; mv ${TMPFILE} ${CONFIGDIR}/package.${i}<br />&nbsp; }<br />done</pre></blockquote> HTML <p>With this small snippet a bash code, you should be able to easily sort <strong><em>/etc/portage/package.*</em></strong> :</p><p>&nbsp;</p><blockquote><pre>CONFIGDIR=&quot;/etc/portage&quot;<br />for i in keywords mask unmask use<br />do<br />&nbsp; [[ -f ${CONFIGDIR}/package.${i} ]] &amp;&amp; {<br />&nbsp;&nbsp;&nbsp; TMPFILE=$(mktemp)<br />&nbsp;&nbsp;&nbsp; mv ${CONFIGDIR}/package.${i} ${CONFIGDIR}/package.${i}.backup<br />&nbsp;&nbsp;&nbsp; sort -g &lt; ${CONFIGDIR}/package.${i}.backup &gt; ${TMPFILE}<br />&nbsp;&nbsp;&nbsp; mv ${TMPFILE} ${CONFIGDIR}/package.${i}<br />&nbsp; }<br />done</pre></blockquote> 2008-05-17T20:22:29+02:00 24 /var/rails/howflow/public/trick/file/185/sortportagefiles.sh 185 en 0 6 automatically_sort_your_gentoo_portage_files 2008-05-18T02:06:56+02:00 published

Sometimes, you might just want to sort /etc/portage/package.* to make them more readable. This is how you can do it :)

2008-09-16T01:46:11+02:00 17 4 Textile 2008-05-12T21:44:01+02:00 4 171 en 0 4 gentoo_configure_the_powermanagment 2008-05-22T17:36:17+02:00 published

A complete guide how to safe batterytime of your laptop. Also useful for other distributions

2008-05-26T18:25:23+02:00 37 http://www.gentoo.org/doc/en/power-management-guide.xml 8 #<Comment:0x2ae4854a5918> Textile 2008-05-04T22:42:34+02:00 10 143 en 0 4 configure_shoutcast_on_gentoo_linux 2008-05-08T09:05:26+02:00 published

I looked a very long time for a good SHOUTcast-configuration-manual but this documentation lead me to a very good configuration.

2008-07-19T14:24:47+02:00 4 http://www.gentoo.org/doc/en/shoutcast-config.xml 4 <h2>Getting Screenie (on Gentoo)</h2> <pre> <code> $ emerge screenie </code> </pre> <h2>Launching screenie</h2> <pre> <code> $ screenie </code> </pre> <h2>Using screenie</h2> <pre> <code> SCREENIE - terminal screen-session handler written by Marc O. Gloor &lt;mgloor&#38;fhzh.ch&gt; a) add job q) quit select: </code> </pre> <p>Lets add a job called &#8220;Systems&#8221;. Once you hit a, enter the name. Hit enter unless you know the process id of existing screen sessions. Lets add a second job called &#8220;Email&#8221;. Now you should see:</p> <pre> <code> SCREENIE - terminal screen-session handler written by Marc O. Gloor &lt;mgloor&#38;fhzh.ch&gt; 1) 15468.Systems 2) 15504.Email a) add job q) quit select: </code> </pre> <p>You now have two screen sessions that you can go into and out of. Select one of the sessions. You are now inside of screen where you can do whatever you usually do.</p> <p><strong>Note: See the tips and tricks describing screen.</strong></p> <p>To go to another screen session, press <span class="caps">CTRL</span>+a+d (or however you usually exit your screen sessions). You should be back to the screenie menu and ready to choose to go to another screen session.</p> <p>One use of screenie might be to have a screen session for every task and for every machine you have access to making multi-tasking much more organized. This should also make it much easier to start working again after a long break.</p> Textile h2. Getting Screenie (on Gentoo) <pre> <code> $ emerge screenie </code> </pre> h2. Launching screenie <pre> <code> $ screenie </code> </pre> h2. Using screenie <pre> <code> SCREENIE - terminal screen-session handler written by Marc O. Gloor <mgloor&fhzh.ch> a) add job q) quit select: </code> </pre> p. Lets add a job called "Systems". Once you hit a, enter the name. Hit enter unless you know the process id of existing screen sessions. Lets add a second job called "Email". Now you should see: <pre> <code> SCREENIE - terminal screen-session handler written by Marc O. Gloor <mgloor&fhzh.ch> 1) 15468.Systems 2) 15504.Email a) add job q) quit select: </code> </pre> p. You now have two screen sessions that you can go into and out of. Select one of the sessions. You are now inside of screen where you can do whatever you usually do. p. *Note: See the tips and tricks describing screen.* p. To go to another screen session, press CTRL+a+d (or however you usually exit your screen sessions). You should be back to the screenie menu and ready to choose to go to another screen session. p. One use of screenie might be to have a screen session for every task and for every machine you have access to making multi-tasking much more organized. This should also make it much easier to start working again after a long break. 2008-04-30T19:24:45+02:00 8 118 en 0 3 organize_your_command_line_screen_sessions_with_screenie 2008-05-01T16:41:38+02:00 published

Want to organize your command line screen session or sessions better? Want to have a separate screen session for every task that you do? Want something that will organize you in general?

2008-05-01T20:47:54+02:00 4 4 #<Comment:0x2ae48548eb50>#<Comment:0x2ae48548e5d8> <h2>Tell Gentoo&#8217;s startup system to turn on services in parallel</h2> <pre> <code> $ nano -w /etc/conf.d/rc </code> </pre> <p>Change:</p> <pre> <code> RC_PARALLEL_STARTUP="no" </code> </pre> <p>To:</p> <pre> <code> RC_PARALLEL_STARTUP="yes" </code> </pre> <h2>Prevent the kernel from displaying status messages</h2> <p>Assuming you are using <span class="caps">GRUB</span> and /boot is mounted correctly</p> <pre> <code> $ nano -w /boot/grub/grub.conf </code> </pre> <p>Append the &#8216;quiet&#8217; option to the kernel you use, for example:</p> <pre> <code> kernel /boot/vmlinuz-2.6.23.9 root=/dev/hda2 quiet </code> </pre> <h2>Remove services that you do not need</h2> <p>View what services are currently activated on boot:</p> <pre> <code> $ rc-status boot </code> </pre> <p>Check what is good with a default runlevel:</p> <pre> <code> $ rc-status default </code> </pre> <p>For example, you probably won&#8217;t need keymap if you&#8217;re building a carputer:</p> <pre> <code> $ rc-update del keymap </code> </pre> <p>Don&#8217;t forget to subscribe to the Gentoo Monthly Newsletter for more tricks.</p> Textile h2. Tell Gentoo's startup system to turn on services in parallel <pre> <code> $ nano -w /etc/conf.d/rc </code> </pre> p. Change: <pre> <code> RC_PARALLEL_STARTUP="no" </code> </pre> p. To: <pre> <code> RC_PARALLEL_STARTUP="yes" </code> </pre> h2. Prevent the kernel from displaying status messages p. Assuming you are using GRUB and /boot is mounted correctly <pre> <code> $ nano -w /boot/grub/grub.conf </code> </pre> p. Append the 'quiet' option to the kernel you use, for example: <pre> <code> kernel /boot/vmlinuz-2.6.23.9 root=/dev/hda2 quiet </code> </pre> h2. Remove services that you do not need p. View what services are currently activated on boot: <pre> <code> $ rc-status boot </code> </pre> p. Check what is good with a default runlevel: <pre> <code> $ rc-status default </code> </pre> p. For example, you probably won't need keymap if you're building a carputer: <pre> <code> $ rc-update del keymap </code> </pre> p. Don't forget to subscribe to the Gentoo Monthly Newsletter for more tricks. 2008-04-29T16:02:35+02:00 8 111 en 0 6 gentoo_speedup_boot_time 2008-04-30T00:10:27+02:00 published

Are you impatient when booting your computer? If yes, try the following:

2008-05-23T18:04:52+02:00 37 http://www.gentoo.org/news/en/gmn/20080424-newsletter.xml 4 Textile 2008-04-29T10:16:33+02:00 10 107 en 0 3 firefox_using_java_as_a_plugin_on_gentoo 2008-04-29T12:05:15+02:00 published

Adding Java-Support to Firefox on Gentoo needs only a few commands. This WIKI describes them

2008-05-01T18:52:17+02:00 1 http://gentoo-wiki.com/HOWTO_Java_and_Firefox 4 <h3>Problem:</h3> <pre> <code> make[4]: Entering directory `/var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17/libc/bcc' ncc -Mn -O -D__LIBC__ -O2 -c -o __ldivmod.o __ldivmod.c copt: can't open pattern file /var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17/lib/rules.286 make[4]: *** [__ldivmod.o] Error 1 make[4]: Leaving directory `/var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17/libc/bcc' make[3]: *** [/var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17/libc/libc.a] Error 1 make[3]: Leaving directory `/var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17/libc' make[2]: *** [library] Error 2 make[2]: Leaving directory `/var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17' make[1]: *** [all] Error 2 make[1]: Leaving directory `/var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17' make: *** [all] Error 2 * * ERROR: sys-devel/dev86-0.16.17-r5 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2104: Called die * The specific snippet of code: * emake -j1 DIST="${D}" || die; * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/sys-devel:dev86-0.16.17-r5:20080421-014407.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/dev86-0.16.17-r5/temp/environment'. * </code> </pre> <h3>Solution:</h3> <p>Temporarily remove any optimization from the <span class="caps">CFLAGS</span> in <em>/etc/make.conf</em>. Emerge dev86 and don&#8217;t forget to reset your <span class="caps">CFLAGS</span> afterwards.</p> Textile h3. Problem: <pre> <code> make[4]: Entering directory `/var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17/libc/bcc' ncc -Mn -O -D__LIBC__ -O2 -c -o __ldivmod.o __ldivmod.c copt: can't open pattern file /var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17/lib/rules.286 make[4]: *** [__ldivmod.o] Error 1 make[4]: Leaving directory `/var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17/libc/bcc' make[3]: *** [/var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17/libc/libc.a] Error 1 make[3]: Leaving directory `/var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17/libc' make[2]: *** [library] Error 2 make[2]: Leaving directory `/var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17' make[1]: *** [all] Error 2 make[1]: Leaving directory `/var/tmp/portage/sys-devel/dev86-0.16.17-r5/work/dev86-0.16.17' make: *** [all] Error 2 * * ERROR: sys-devel/dev86-0.16.17-r5 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2104: Called die * The specific snippet of code: * emake -j1 DIST="${D}" || die; * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/sys-devel:dev86-0.16.17-r5:20080421-014407.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/dev86-0.16.17-r5/temp/environment'. * </code> </pre> h3. Solution: Temporarily remove any optimization from the CFLAGS in _/etc/make.conf_. Emerge dev86 and don't forget to reset your CFLAGS afterwards. 2008-04-21T04:00:02+02:00 1 67 en 0 2 gentoo_how_to_compile_the_package_dev86 queued

This trick might be helpful if emerge dev86 returns the error message "ncc -Mn -O -D__LIBC__ -O2 -c -o __ldivmod.o __ldivmod.c make[4]: *** [__ldivmod.o] Error 1".

2008-05-01T19:55:38+02:00 1 1 2008-04-17T13:00:00+02:00 1 31 en 0 2 a_complete_virtual_system 2008-04-18T14:41:28+02:00 published

The purpose of this HOWTO is to establish a virtual mail system that can handle multiple domains with a variety of different interface options. This is not intended to be used by the average user who is looking for a mail client, this is a full-scale Mail Transfer Agent (MTA) intended for individuals who are hosting their own domains and/or need to provide support for virtual domains.

2008-05-01T19:35:42+02:00 1 http://gentoo-wiki.com/HOWTO_Email:_A_Complete_Virtual_System 4 <h2>1. Background</h2> <h3>What&#8217;s baselayout?</h3> <p>Baselayout provides a basic set of files that are necessary for all systems to function properly, such as /etc/hosts. It also provides the basic filesystem layout used by Gentoo (i.e. /etc, /var, /usr, /home directories).</p> <h3>What&#8217;s OpenRC?</h3> <p>OpenRC is a dependency-based rc system that works with whatever init is provided by the system, normally /sbin/init. However, it is not a replacement for /sbin/init. The default init used by Gentoo Linux is sys-apps/sysvinit, while Gentoo/FreeBSD uses the FreeBSD init provided by sys-freebsd/freebsd-sbin.</p> <h3>So why migrate?</h3> <p>Originally Gentoo&#8217;s rc system was built into baselayout 1 and written entirely in bash. This led to several limitations. For example, certain system calls need to be accessed during boot and this required C-based callouts to be added. These callouts were each statically linked, causing the rc system to bloat over time.</p> <p>Additionally, as Gentoo expanded to other platforms like Gentoo/FreeBSD and Gentoo Embedded, it became impossible to require a bash-based rc system. This led to a development of baselayout 2, which is written in C and only requires a <span class="caps">POSIX</span>-compliant shell. During the development of baselayout 2, it was determined that it was a better fit if baselayout merely provided the base files and filesystem layout for Gentoo and the rc system was broken off into its own package. Thus we have OpenRC.</p> <p>OpenRC is primarily developed by Roy Marples and supports all current Gentoo variations (i.e. Gentoo Linux, Gentoo/FreeBSD, Gentoo Embedded, and Gentoo Vserver) and other platforms such as FreeBSD and NetBSD.</p> <h2>2. Migration to OpenRC</h2> <p>Migration to OpenRC is fairly straightforward; it will be pulled in as part of your regular upgrade process by your package manager. The most important step actually comes after you install the new &gt;=sys-apps/baselayout-2 and sys-apps/openrc packages. It is critical that you run dispatch-conf and ensure your /etc is up to date before rebooting. Failure to do so will result in an unbootable system and will require the use of the Gentoo LiveCD to perform the steps below to repair your system.</p> <p>Once you&#8217;ve finished updating your config files, there are a few things to verify prior to rebooting.</p> <h3>/etc/conf.d/rc</h3> <p>/etc/conf.d/rc has been deprecated and any settings you have in there will need to be migrated to the appropriate settings in /etc/rc.conf. Please read through /etc/rc.conf and /etc/conf.d/rc and migrate the settings. Once you are complete, delete /etc/conf.d/rc.</p> <h3>Kernel modules</h3> <p>Normally, when you want certain kernel modules automatically loaded at boot, you place them into /etc/modules.autoload.d/kernel-2.6 along with any parameters you wanted to pass to them. In baselayout-2, this file is not used anymore. Instead, autoloaded modules and module parameters are placed in one file, /etc/conf.d/modules, no matter the kernel version.</p> <p>An example old style configuration would be:</p> <pre> <code> Code Listing 2.1: /etc/modules.autoload.d/kernel-2.6 ivtv cx88_dvb video_br=2 </code> </pre> <p>Converting the above example would result in the following:</p> <pre> <code> Code Listing 2.2: /etc/conf.d/modules # Modules autoloaded at boot modules_2_6="ivtv cx88_dvb" # Module parameters module_cx88_dvb_args_2_6="video_br=2" </code> </pre> <p>In the above examples, the modules and their parameters would only be passed to 2.6.x series kernels. The new configuration allows for fine grained control over the modules and parameters based on kernel version.</p> <p>An in-depth example would be:</p> <pre> <code> Code Listing 2.3: detailed example of /etc/conf.d/modules # Always load ochi1394 and ieee1394, no matter the kernel version modules="ohci1394 ieee1394" # Only load tun and usbserial for 2.6.x series kernels modules_2_6="tun usbserial" # Only load cx88_dvb for 2.6.23 kernels modules_2_6_23="cx88_dvb" # Only load ivtv for 2.6.23-gentoo-r5 modules_2_6_23_gentoo_r5="ivtv" # For 2.6.23-gentoo-r5, pass video_br=2 to cx88_dvb module_cx88_dvb_args_2_6_23_gentoo_r5="video_br=2" # For 2.6.x series kernels, always pass vendor and product module_usbserial_args_2_6="vendor=0x1410 product=0x2110" # Always pass debug to ieee1394 module_ieee1394_args="debug" </code> </pre> <p>Note: Please note the difference between module_ and modules_.</p> <h3>Boot runlevel</h3> <p>The boot runlevel performs several important steps for every machine. For example, making sure your root filesystem is mounted read/write, that your filesystems are checked for errors, that your mountpoints are available, and that the /proc pseudo-filesystem is started at boot.</p> <p>With OpenRC, volume management services for your block storage devices are no longer run automatically at boot. This includes lvm, raid, swap, device-mapper (dm), dm-crypt, evms, and the like. You must ensure the appropriate initscript for these services is in the boot runlevel, otherwise it&#8217;s possible that your system will not boot!</p> <p>While the OpenRC ebuild will attempt to do this migration for you, you should verify that it migrated all the volume management services properly:</p> <pre> <code> Code Listing 2.4: Display all services in boot runlevel # ls -l /etc/runlevels/boot/ </code> </pre> <p>If you don&#8217;t see root, procfs, mtab, swap, and fsck in the above listing, perform the following to add them to the boot runlevel:</p> <pre> <code> Code Listing 2.5: Adding missing volume management services to the boot runlevel # rc-update add root boot # rc-update add procfs boot # rc-update add mtab boot # rc-update add fsck boot # rc-update add swap boot </code> </pre> <p>If you know you use mdraid and lvm but do not see them above, you would run the following to add initscripts to the boot runlevel:</p> <pre> <code> Code Listing 2.6: Adding raid and lvm to the boot runlevel # rc-update add raid boot # rc-update add lvm boot </code> </pre> <h3>Clock</h3> <p>Clock settings have been renamed from /etc/conf.d/clock to your system&#8217;s native tool for adjusting the clock. This means on Linux it will be /etc/conf.d/hwclock and on FreeBSD it will be /etc/conf.d/adjkerntz. The initscript in /etc/init.d/ has also been renamed accordingly, so make sure it&#8217;s in the appropriate runlevel.</p> <p>Additionally, the <span class="caps">TIMEZONE</span> variable is no longer in this file. Its contents are instead found in the /etc/timezone file. Please review both of these files to ensure their correctness.</p> <h3><span class="caps">XSESSION</span></h3> <p>The <span class="caps">XSESSION</span> variable is no longer found in /etc/rc.conf. The x11-apps/xinit package now provides /etc/env.d/90xsession, which can be used to set the <span class="caps">XSESSION</span> variable.</p> <p>This variable will <span class="caps">NOT</span> be migrated for you by default, so you will need to edit /etc/env.d/90xsession.</p> <p>Important: You must run env-update after creating a file in /etc/env.d, and then logout and login for it to take effect.</p> <h3><span class="caps">EDITOR</span></h3> <p>The <span class="caps">EDITOR</span> variable is no longer found in /etc/rc.conf, and at this time is not provided by any other package. Users are encouraged to set it as needed in their ~/.bashrc file or create /etc/env.d/99editor and set it there.</p> <p>Important: You must run env-update after creating a file in /etc/env.d, and then logout and login for it to take effect. If you set the variable in ~/.bashrc, you can re-source the file with source ~/.bashrc.</p> <h3>Finishing up</h3> <p>Once you&#8217;ve finished updating your config files and initscripts, the last thing to do is reboot. This is necessary because system state information is not preserved during the upgrade, so you&#8217;ll need to provide it with a fresh boot.</p> Textile h2. 1. Background h3. What's baselayout? p. Baselayout provides a basic set of files that are necessary for all systems to function properly, such as /etc/hosts. It also provides the basic filesystem layout used by Gentoo (i.e. /etc, /var, /usr, /home directories). h3. What's OpenRC? p. OpenRC is a dependency-based rc system that works with whatever init is provided by the system, normally /sbin/init. However, it is not a replacement for /sbin/init. The default init used by Gentoo Linux is sys-apps/sysvinit, while Gentoo/FreeBSD uses the FreeBSD init provided by sys-freebsd/freebsd-sbin. h3. So why migrate? p. Originally Gentoo's rc system was built into baselayout 1 and written entirely in bash. This led to several limitations. For example, certain system calls need to be accessed during boot and this required C-based callouts to be added. These callouts were each statically linked, causing the rc system to bloat over time. p. Additionally, as Gentoo expanded to other platforms like Gentoo/FreeBSD and Gentoo Embedded, it became impossible to require a bash-based rc system. This led to a development of baselayout 2, which is written in C and only requires a POSIX-compliant shell. During the development of baselayout 2, it was determined that it was a better fit if baselayout merely provided the base files and filesystem layout for Gentoo and the rc system was broken off into its own package. Thus we have OpenRC. p. OpenRC is primarily developed by Roy Marples and supports all current Gentoo variations (i.e. Gentoo Linux, Gentoo/FreeBSD, Gentoo Embedded, and Gentoo Vserver) and other platforms such as FreeBSD and NetBSD. h2. 2. Migration to OpenRC p. Migration to OpenRC is fairly straightforward; it will be pulled in as part of your regular upgrade process by your package manager. The most important step actually comes after you install the new >=sys-apps/baselayout-2 and sys-apps/openrc packages. It is critical that you run dispatch-conf and ensure your /etc is up to date before rebooting. Failure to do so will result in an unbootable system and will require the use of the Gentoo LiveCD to perform the steps below to repair your system. p. Once you've finished updating your config files, there are a few things to verify prior to rebooting. h3. /etc/conf.d/rc p. /etc/conf.d/rc has been deprecated and any settings you have in there will need to be migrated to the appropriate settings in /etc/rc.conf. Please read through /etc/rc.conf and /etc/conf.d/rc and migrate the settings. Once you are complete, delete /etc/conf.d/rc. h3. Kernel modules p. Normally, when you want certain kernel modules automatically loaded at boot, you place them into /etc/modules.autoload.d/kernel-2.6 along with any parameters you wanted to pass to them. In baselayout-2, this file is not used anymore. Instead, autoloaded modules and module parameters are placed in one file, /etc/conf.d/modules, no matter the kernel version. p. An example old style configuration would be: <pre> <code> Code Listing 2.1: /etc/modules.autoload.d/kernel-2.6 ivtv cx88_dvb video_br=2 </code> </pre> p. Converting the above example would result in the following: <pre> <code> Code Listing 2.2: /etc/conf.d/modules # Modules autoloaded at boot modules_2_6="ivtv cx88_dvb" # Module parameters module_cx88_dvb_args_2_6="video_br=2" </code> </pre> p. In the above examples, the modules and their parameters would only be passed to 2.6.x series kernels. The new configuration allows for fine grained control over the modules and parameters based on kernel version. p. An in-depth example would be: <pre> <code> Code Listing 2.3: detailed example of /etc/conf.d/modules # Always load ochi1394 and ieee1394, no matter the kernel version modules="ohci1394 ieee1394" # Only load tun and usbserial for 2.6.x series kernels modules_2_6="tun usbserial" # Only load cx88_dvb for 2.6.23 kernels modules_2_6_23="cx88_dvb" # Only load ivtv for 2.6.23-gentoo-r5 modules_2_6_23_gentoo_r5="ivtv" # For 2.6.23-gentoo-r5, pass video_br=2 to cx88_dvb module_cx88_dvb_args_2_6_23_gentoo_r5="video_br=2" # For 2.6.x series kernels, always pass vendor and product module_usbserial_args_2_6="vendor=0x1410 product=0x2110" # Always pass debug to ieee1394 module_ieee1394_args="debug" </code> </pre> p. Note: Please note the difference between module_ and modules_. h3. Boot runlevel p. The boot runlevel performs several important steps for every machine. For example, making sure your root filesystem is mounted read/write, that your filesystems are checked for errors, that your mountpoints are available, and that the /proc pseudo-filesystem is started at boot. p. With OpenRC, volume management services for your block storage devices are no longer run automatically at boot. This includes lvm, raid, swap, device-mapper (dm), dm-crypt, evms, and the like. You must ensure the appropriate initscript for these services is in the boot runlevel, otherwise it's possible that your system will not boot! p. While the OpenRC ebuild will attempt to do this migration for you, you should verify that it migrated all the volume management services properly: <pre> <code> Code Listing 2.4: Display all services in boot runlevel # ls -l /etc/runlevels/boot/ </code> </pre> p. If you don't see root, procfs, mtab, swap, and fsck in the above listing, perform the following to add them to the boot runlevel: <pre> <code> Code Listing 2.5: Adding missing volume management services to the boot runlevel # rc-update add root boot # rc-update add procfs boot # rc-update add mtab boot # rc-update add fsck boot # rc-update add swap boot </code> </pre> p. If you know you use mdraid and lvm but do not see them above, you would run the following to add initscripts to the boot runlevel: <pre> <code> Code Listing 2.6: Adding raid and lvm to the boot runlevel # rc-update add raid boot # rc-update add lvm boot </code> </pre> h3. Clock p. Clock settings have been renamed from /etc/conf.d/clock to your system's native tool for adjusting the clock. This means on Linux it will be /etc/conf.d/hwclock and on FreeBSD it will be /etc/conf.d/adjkerntz. The initscript in /etc/init.d/ has also been renamed accordingly, so make sure it's in the appropriate runlevel. p. Additionally, the TIMEZONE variable is no longer in this file. Its contents are instead found in the /etc/timezone file. Please review both of these files to ensure their correctness. h3. XSESSION p. The XSESSION variable is no longer found in /etc/rc.conf. The x11-apps/xinit package now provides /etc/env.d/90xsession, which can be used to set the XSESSION variable. p. This variable will NOT be migrated for you by default, so you will need to edit /etc/env.d/90xsession. p. Important: You must run env-update after creating a file in /etc/env.d, and then logout and login for it to take effect. h3. EDITOR p. The EDITOR variable is no longer found in /etc/rc.conf, and at this time is not provided by any other package. Users are encouraged to set it as needed in their ~/.bashrc file or create /etc/env.d/99editor and set it there. p. Important: You must run env-update after creating a file in /etc/env.d, and then logout and login for it to take effect. If you set the variable in ~/.bashrc, you can re-source the file with source ~/.bashrc. h3. Finishing up p. Once you've finished updating your config files and initscripts, the last thing to do is reboot. This is necessary because system state information is not preserved during the upgrade, so you'll need to provide it with a fresh boot. 2008-04-15T16:40:57+02:00 8 27 en 0 6 gentoo_baselayout_and_openrc_migration_guide 2008-04-15T18:00:02+02:00 published

This is the official Gentoo OpenRC migration guide. Please make sure to visit the original site.

2009-05-10T19:27:15+02:00 17 http://www.gentoo.org/doc/en/openrc-migration.xml