Auf dieser Seite: http://gentoo-portage.com/ findest du viele Informatonen, zu den verschiedenen Versionen.
Zudem sind auf http://packages.gentoo.org/ alle verfügbaren Pakete mit Versionsangabe aufgelistet.
Nach der Installation von 'app-portage/gentoolkit' & 'dev-util/lafilefixer':
# lafilefixer --justfixit # revdep-rebuild
Nach dem das System läuft, kommen Updates dazu. Dabei sammeln sich mit der Zeit beachtliche Mengen an veralteten Daten, vor allem, wenn Spiele dabei sind.
Diese Dateien findet man mit folgendem Befehl:
# eclean-dist --pretend
Der Befehl zeigt auch gleich an, wie viel Speicher er freigeben könnte, da er sich jedoch durch die Festplatte arbeiten muss, braucht er seine Zeit.
Auf älteren Systemen kommt es immer wieder vor, dass Pakete ersetzt oder nicht mehr gebraucht werden. Diese kann man normalerweise problemlos entfernen:
| Prüfen ob es nicht mehr verwendet wird: | emerge -pvD –unmerge ${Paket} |
|---|---|
| Paket entfernen | emerge –unmerge ${Paket} |
| Veraltetes Paket: | Ersetzt durch: | Begründung: |
|---|---|---|
| dev-libs/libxml Version: 1.8.17-r3 | dev-libs/libxml2 | http://bugs.gentoo.org/show_bug.cgi?id=281446 |
Zuerst brauchst du den neusten Quell-Code:
# emerge gentoo-sources
Dann wechseln wir in das Verzeichnis:
# cd /usr/src/linux
… und erstellen die Konfiguration.
Wichtig: Es müssen alle Dateisysteme und Treiber im Kernel drinn sein, welche nötig sind um das System zu starten. Fehlt etwas während dem Booten, kann das vielfältige Folgen haben.
# make menuconfig
Ist die Konfiguration in Ordnung, wird der Kern mit 'make' kompiliert.
# make # make modules_install
Zum Schluss muss der Kernel noch kopiert werden:
# cp arch/x86_64/boot/bzImage /boot/kernel-2.6.XX-gentoo-rY
Wird dieser Schritt übersprungen, werden die Änderungen nicht übernommen.
Es empfielt sich die Beispiele im GRUB-Artikel durchzulesen.
Wichtig: sollten Fehler bezüglich des „Nichtfindes“ des Root-Devices auftreten, lohnt es sich
'sdaX' durch 'hdaX' zu ersetzen.Will man nicht bei jedem Start die nötigen Treiber laden oder suchen lassen (es braucht schliesslich Zeit), kann man die Module manuell in der autoload-Konfig eintragen:
# cp /etc/modules.autoload.d/kernel-2.6 /etc/modules.autoload.d/kernel-2.6.original
# lsmod | cut -f 1 -d " " >> /etc/modules.autoload.d/kernel-2.6
'lsmod' das Wort 'Module' steht, muss man es vonhand entfernen bzw. auskommentieren: # nano /etc/modules.autoload.d/kernel-2.6
title Gentoo Linux 2.6.30-r5 (static) uuid 28af12ac-1234-abcd-bf42-0123456789ab kernel /boot/kernel-2.6.30-gentoo-r5 root=/dev/sda3
Muss der Kernel mehrfach kompiliert werden, weil z.B. nur die nötigsten Treiber installiert werden sollen, kann es helfen die temporären Dateien zu löschen. Dazu muss man im Ordner mit dem Source-Code sein (meistens /usr/src/linux) und dann folgenden Befehl abschicken:
# make clean
Bei anderen Distributionen ist es vergleichsweise einfach, die neusten Versionen zu installieren. Unter Gentoo müssen alle Pakete jedesmal neu kompiliert werden. Dies ist jedoch meistens nicht notwendig. Nach einem Kernel-Update ist es jedoch zu empfehlen:
# emerge --sync /* ... Viel Text & ein paar Statusmeldungen */
Jetzt musst du entscheiden, ob du nur die Programme, welche du installiert hast updaten willst,
# emerge --update --ask world
oder ob du die Abhängikeiten der als Favoriten gespeicherten Programme, welche mit emerge installiert worden sind, aktualisieren willst:
# emerge --update --deep --ask world
Mit diesen Optionen werden alle möglichen Updates in einem Abhängigkeitsbaum dargestellt:
# emerge -ptvDuN world
und so angewendet:
# emerge -qDuN world
# find -L /etc/ssl/certs/ -type l -exec rm {} +
In der Datei '/etc/udev/rules.d/70-persistent-net.rules' gelistete Module können umbenannt werden.
Die Einstellungen müssen in der Datei '/etc/sysctl.conf' vorgenommen werden und sollten mit den iptables gesichert werden.
Zuerst, der grafische Installer ist in dieser Version noch nicht vollstaendig ausgereift.
Zuerst brauchen wir ein ISO von Gentoo.org. Das ISO fuer die amd64-Architektur findest du hier: http://bouncer.gentoo.org/fetch/gentoo-2008.0-livecd/amd64/
Im naechsten Schritt wird das Abbild/Image auf eine CD gebrannt oder mit etwas hoeherem Aufwand auf einen Memorystick kopiert. Zum Schluss musst du den PC nur noch neustarten.
Nach dem Booten brauchst du zuerst ein Terminal (in Menue oder unten in der Startliste. Dann muessen wir zwei Befehle ausfuehren, welche wegen eines Fehlers im Startprozess (genauer in der Datei '/etc/conf.d/local.start') noch nicht ausgefuehrt worden sind (Bug 230998):
sudo cp /mnt/cdrom/extlinux/gentoo /boot/`uname -r` sudo cp /mnt/cdrom/extlinux/gentoo.igz /boot/initrd sudo cp /usr/livecd/System.map* /boot
Um die Installation zu starten gibst du am einfachsten noch folgenden Befehl ein und folgst dann den Anweisungen:
sudo installer-dialog
Wenn die Meldung 'Install done!' erscheint, musst du nur noch neustarten und die Installationsmedien entfernen.
Dieses Tutorial ist noch nicht fertig! Wer es benutzen möchte, sollte zuerst ein Backup von allem machen, was ihm/ihr lieb ist.
Wenn du solche eingriffe in deinen Computer machst, solltest du zumindest wissen, was du tust. Ich schreibe das hier nach dem Motto 'Learning by Doing'! Hab keine Angst es auch Mal zu probieren. Das was du hier siehst ist mein zweite Versuch. Den ersten habe ich ausversehen verschossen.
Greets The TUX! 8.7.08
http://www.gentoo.org/doc/de/handbook/handbook-x86.xml
mount /dev/sda8 /mnt/gentoo mount -t proc none /mnt/gentoo/proc mount -o bind /dev /mnt/gentoo/dev cp /etc/resolv.conf /mnt/gentoo/etc
tar xvf stage3*
tar xvf portage* -C /mnt/gentoo/usr
mirrorselect -i -o >> /mnt/gentoo/etc/make.conf mirrorselect -i -r -o >> /mnt/gentoo/etc/make.conf
chroot /mnt/gentoo /bin/bash
env-update source /etc/profile export PS1="(chroot) $PS1"
passwd
echo 'de_CH.UTF-8 UTF-8' >> /etc/locale.gen echo 'de_CH ISO-8859-1' >> /etc/locale.gen mkdir /etc/profile.d echo 'export LANG="de_CH.utf8"' > /etc/profile.d/locale.sh locale-gen env-update source /etc/profile export PS1="(chroot) $PS1"
TIMEZONE auf 'Europe/Zurich' setzen: nano /etc/conf.d/clock
cp /usr/share/zoneinfo/Europe/Zurich /etc/localtime
'Hardware-Clock' auf 'UTC' (Linux/Unix Standard) oder 'Localtime' (Bei Dual-Boot mit Windows) läuft. Dazu muss die Variabel CLOCK in der Datei '/etc/conf.d/clock' entweder auf 'UTC' oder 'local' gesetzt werden.emerge -a gentoo-sources emerge -a genkernel genkernel all
emerge -a grub
Hier findest du eine Anleitung.
'/etc/conf.d/keymaps': # /etc/conf.d/keymaps # Use KEYMAP to specify the default console keymap. There is a complete tree # of keymaps in /usr/share/keymaps to choose from. #KEYMAP="us" KEYMAP="de_CH-latin1" # Should we first load the 'windowkeys' console keymap? Most x86 users will # say "yes" here. Note that non-x86 users should leave it as "no". SET_WINDOWKEYS="yes" # The maps to load for extended keyboards. Most users will leave this as is. EXTENDED_KEYMAPS="" #EXTENDED_KEYMAPS="backspace keypad euro" # Tell dumpkeys(1) to interpret character action codes to be # from the specified character set. # This only matters if you set UNICODE="yes" in /etc/rc.conf. # For a list of valid sets, run `dumpkeys --help` DUMPKEYS_CHARSET=""
emerge -a syslog-ng app-admin/logrotate rc-update add syslog-ng default
emerge -a vixie-cron rc-update add vixie-cron default
emerge -a dhcpcd
Automatisches laden von Modulen:
nano -w /etc/modules.autoload.d/kernel-2.6
Kommen nach der installation von 'net-wireless/wireless-tools' folgende Fehler ist die installation des Pakets 'net-wireless/iwl3945-ucode' nötig.
Aus '/var/log/messages':
iwl3945 0000:03:00.0: firmware: requesting iwlwifi-3945-2.ucode iwl3945: iwlwifi-3945-2.ucode firmware file req failed: Reason -2 iwl3945 0000:03:00.0: firmware: requesting iwlwifi-3945-1.ucode firmware.sh[28754]: Cannot find firmware file 'iwlwifi-3945-2.ucode' iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 iwl3945: Could not read microcode: -2 iwl3945 0000:03:00.0: PCI INT A disabled
Nach 'ifconfig':
# ifconfig wlan0 up SIOCSIFFLAGS: No such file or directory #
Firefox benötigt auf der amd64-Platform das Paket www-plugins/nspluginwrapper umd Adobe Flash ein zu binden.
* All the packages built against mozilla-firefox won't compile, * if after installing firefox 3.0 you get some blockers, * please add 'xulrunner' to your USE-flags.
* Messages for package net-libs/xulrunner-1.9.1.6: * You are enabling system sqlite. Do not file a bug with gentoo if you have * issues that arise from enabling system sqlite. All bugs will be considered * invalid. All patches are welcomed to fix any issues that might be found with * system sqlite. If you are starting with a fresh profile you can enable sqlite * without any major issues. * If firefox fails to start with "failed to load xpcom", run revdep-rebuild * If that does not fix the problem, rebuild dev-libs/nss * Try dev-util/lafilefixer if you get build failures related to .la files * Please remember to rebuild your browser(s) after update to prevent an xpcom error. * This bump is needed in order to bring icecat to the tree to replace iceweasel useflag. * Messages for package www-client/mozilla-firefox-3.5.6: * You are enabling official branding. You may not redistribute this build * to any users on your network or the internet. Doing so puts yourself into * a legal problem with Mozilla Foundation * You can disable it by emerging mozilla-firefox _with_ the bindist USE-flag * Fallback PaX marking -m * /var/tmp/portage/www-client/mozilla-firefox-3.5.6/image///usr/lib64/mozilla-firefox/firefox * All the packages built against mozilla-firefox won't compile, * any package that fails to build warrants a bug report.
* Messages for package dev-libs/nss-3.12.6-r1: * We have reverted back to using upstreams soname. * Please run revdep-rebuild --library libnss3.so.12 , this * will correct most issues. If you find a binary that does * not run please re-emerge package to ensure it properly * links after upgrade. * * Messages for package net-libs/xulrunner-1.9.2.3-r1: * If firefox fails to start with "failed to load xpcom", run revdep-rebuild * If that does not fix the problem, rebuild dev-libs/nss * Try dev-util/lafilefixer if you get build failures related to .la files * Any package that requires xulrunner:1.9 slot could and most likely will * have issues. These issues should be reported to maintainer, and mozilla herd * should be cc'd on the bug report. Thank you anarchy@gentoo.org . * Messages for package www-client/mozilla-firefox-3.6.3: * You are enabling official branding. You may not redistribute this build * to any users on your network or the internet. Doing so puts yourself into * a legal problem with Mozilla Foundation * You can disable it by emerging mozilla-firefox _with_ the bindist USE-flag * Fallback PaX marking -m * /var/tmp/portage/www-client/mozilla-firefox-3.6.3/image///usr/lib64/mozilla-firefox/firefox * All the packages built against mozilla-firefox won't compile, * any package that fails to build warrants a bug report.
Nach dem Update auf Firefox 5.0 (auch bekannt als Firefox 4.0.2) hat er Flash nicht mehr gefunden. Abhilfe schafte folgender Befehl:
$ nspluginwrapper -a -v -i
Um Skype verwenden zu können, muss es entmaskiert & auf Beta gesetzt werden sowie die Lizenz akzeptiert werden:
echo net-im/skype skype-eula >>/etc/portage/package.license echo "=net-im/skype-2.1.0.81" >> /etc/portage/package.unmask echo "net-im/skype" >> /etc/portage/package.keywords emerge -q skype
Bei Reinstall: evt. Binary löschen
* //etc/portage/postsync.d/q-reinitialize has been installed for convenience * If you wish for it to be automatically run at the end of every --sync simply chmod +x //etc/portage/postsync.d/q-reinitialize * Normally this should only take a few seconds to run but file systems such as ext3 can take a lot longer. * If ever you find this to be an inconvenience simply chmod -x //etc/portage/postsync.d/q-reinitialize
* /etc/portage/postsync.d/q-reinitialize has been installed for convenience * If you wish for it to be automatically run at the end of every --sync: * # chmod +x /etc/portage/postsync.d/q-reinitialize * Normally this should only take a few seconds to run but file systems * such as ext3 can take a lot longer. To disable, simply do: * # chmod -x /etc/portage/postsync.d/q-reinitialize
* If you have issues with packages unable to locate libstdc++.la, * then try running 'fix_libtool_files.sh' on the old gcc versions.
* Messages for package * This version of libogg has stopped installing .la files. This may * cause compilation failures in other packages. To fix this problem, * install dev-util/lafilefixer and run: * lafilefixer --justfixit
* Using the following options to build: * gentoorelease --without-mpi --user-config=/var/tmp/portage/dev-libs/boost-1.35.0-r2/work/boost_1_35_0/user-config.jam --boost-build=/usr/share/boost-build
* Adding back_dnssrv.so * Adding back_ldap.so * Adding back_meta.so * Adding back_monitor.so * Adding back_null.so * Adding back_passwd.so * Adding back_perl.so * Adding back_relay.so * Adding back_shell.so * Adding back_sock.so * Self-signed SSL certificates are treated harshly by OpenLDAP 2.[12] * Self-signed SSL certificates are treated harshly by OpenLDAP 2.[12] * add 'TLS_REQCERT never' if you want to use them. * Getting started using OpenLDAP? There is some documentation available: * Gentoo Guide to OpenLDAP Authentication * (http://www.gentoo.org/doc/en/ldap-howto.xml) * --- * An example file for tuning BDB backends with openldap is * DB_CONFIG.fast.example in /usr/share/doc/openldap-2.4.24/
* It is possible to start/stop daemons separately:
* Create a symlink from /etc/init.d/samba.{smbd,nmbd,winbind} to
* /etc/init.d/samba. Calling /etc/init.d/samba directly will start
* the daemons configured in /etc/conf.d/samba
* The mount/umount.cifs helper applications are not included anymore.
* Please install net-fs/mount-cifs instead.
* If you're upgrading from 3.0.24 or earlier, please make sure to
* restart your clients to clear any cached information about the server.
* Otherwise they might not be able to connect to the volumes.
* The default value of 'wide links' has been changed to 'no' in samba 3.5
* to avoid an insecure default configuration
* ('wide links = yes' and 'unix extensions = yes'). For more details,
* please see http://www.samba.org/samba/news/symlink_attack.html .
*
* An EXPERIMENTAL implementation of the SMB2 protocol has been added.
* SMB2 can be enabled by setting 'max protocol = smb2'. SMB2 is a new
* implementation of the SMB protocol used by Windows Vista and higher
*
* For further information make sure to read the release notes at
* http://samba.org/samba/history/samba-3.5.9.html and
* http://samba.org/samba/history/samba-3.5.0.html
Das Einstellen der Bildschirmauflösung wird mit dem Programm 'xrandr' gemacht.
* * USE flag 'truetype' needs one of these additional flag(s) set: * gd gd-external * * 'gd' was automatically selected and enabled. * You can change that by enabling/disabling those flags accordingly * in /etc/portage/package.use. * * Enabling ZTS for Apache2 MPM * Enabling ZTS for Apache2 MPM * If you have additional third party PHP extensions (such as * dev-php5/phpdbg) you may need to recompile them now. * * USE="pic" slows down PHP but has to be enabled on setups where TEXTRELs * are disabled (e.g. when using PaX in the kernel). On hardened profiles this * USE flag is enabled automatically *
* Berkeley DB support is deprecated and will be removed in future versions! * MySQL MY_DATADIR is /var/lib/mysql * Berkeley DB support was disabled due to build failures * on multiple arches, go to a version earlier than 5.0.60 * if you want it again. Gentoo bug #224067. * You might want to run: * "emerge --config =dev-db/mysql-5.0.84-r1" * if this is a new install. * Berkeley DB support is deprecated and will be removed in future versions!
* Upstream has noted that the NDB cluster support in the 5.0 and * 5.1 series should NOT be put into production. In the near * future, it will be disabled from building. * * If you need NDB support, you should instead move to the new * mysql-cluster package that represents that upstream NDB * development. * MySQL MY_DATADIR is /var/lib/mysql * You might want to run: * "emerge --config =dev-db/mysql-5.1.50-r1" * if this is a new install.
* To use readline you need to add the following to your registry * * python.console=org.python.util.ReadlineConsole * python.console.readlinelib=GnuReadline * * The global registry can be found in /usr/share/jython/registry * User registry in $HOME/.jython * See http://www.jython.org/docs/registry.html for more information *
* You have both the 'gdbm' and 'berkdb' USE flags enabled. * Will default to GNU DB as your SASLdb database backend. * If you want to build with BerkeleyDB support, hit Control-C now, * change your USE flags -gdbm and emerge again. * Waiting 10 seconds before starting ... * (Control-C to abort) ...
* QMYSQL has been set as your default akonadi storage backend. * You can override it in your ~/.config/akonadi/akonadiserverrc. * Available drivers are: * QMYSQL, QPSQL (testing), QSQLITE (experimental) * Be advised that QMYSQL is the one fully tested and officially supported.
* You must reinstall perl-core/PodParser ! * You must reinstall perl-core/Test-Harness !
* "bsddb" module is out-of-date and no longer maintained inside dev-lang/python. It has * been additionally removed in Python 3. You should use external, still maintained "bsddb3" * module provided by dev-python/bsddb3 which supports both Python 2 and Python 3. * It is highly recommended to additionally install Python 3, but without configuring Python wrapper to use Python 3.
*
* WARNING!
* Many Python modules have not been ported yet to Python 3.*.
* Python 3 has not been activated and Python wrapper is still configured to use Python 2.
* You can manually activate Python 3.1 using `eselect python set python3.1`.
* It is recommended to currently have Python wrapper configured to use Python 2.
* Having Python wrapper configured to use Python 3 is unsupported.
*
*
* ************************************************************************
*
* You have just upgraded from an older version of Python.
* You should run 'python-updater ${options}' to rebuild Python modules.
*
* ************************************************************************
*
Zudem gab's noch eine kleine Info:
2010-03-25-python-3.1 Title Python 3.1 Author Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org> Posted 2010-03-25 Revision 1 Python 3 is a new major version of Python and is intentionally incompatible with Python 2. Many external modules have not been ported yet to Python 3, so Python 2 still needs to be installed. You can benefit from having Python 3 installed without setting Python 3.1 as main active version of Python. Currently you should not set Python 3.1 as main active version of Python. When setting it becomes recommended, a separate news item will be created to notify users. Although Python 3.1 should not be set as main active version of Python, you should run python-updater after installation of Python 3.1. By default, modules that support both Python 2 and Python 3 are installed for both the active version of Python 2 and the active version of Python 3 when both Python 2 and Python 3 are installed. It is recommended to use a UTF-8 locale to avoid potential problems. Especially C and POSIX locales are discouraged. If locale has not been explicitly set, then POSIX locale is used, so you should ensure that locale has been set. Problems occurring only with non-UTF-8 locales should be reported directly to upstream developers of given packages. See http://www.gentoo.org/doc/en/utf-8.xml for more information about UTF-8.
* If you use startx to start X instead of a login manager like gdm/kdm, * you can set the XSESSION variable to anything in /etc/X11/Sessions/ or * any executable. When you run startx, it will run this as the login session. * You can set this in a file in /etc/env.d/ for the entire system, * or set it per-user in ~/.bash_profile (or similar for other shells). * Here's an example of setting it for the whole system: * echo XSESSION="Gnome" > /etc/env.d/90xsession * env-update && source /etc/profile
Wichtigste Änderungen:
* udev-146 does not support Linux kernel before version 2.6.25! * For a reliable udev, use at least kernel 2.6.27 * * Updating persistent-net rules file * * restarting udevd now. * * If after the udev update removable devices or CD/DVD drives * stop working, try re-emerging HAL before filling a bug report * * persistent-net does assigning fixed names to network devices. * If you have problems with the persistent-net rules, * just delete the rules file * rm /etc/udev/rules.d/70-persistent-net.rules * and then reboot. * * This may however number your devices in a different way than they are now. * * If you build an initramfs including udev, then please * make sure that the /sbin/udevadm binary gets included, * and your scripts changed to use it,as it replaces the * old helper apps udevinfo, udevtrigger, ... * * mount options for directory /dev are no longer * set in /etc/udev/udev.conf, but in /etc/fstab * as for other directories. * * You have devfs-compat use flag enabled. * This enables devfs compatible device names. * If you use /dev/md/*, /dev/loop/* or /dev/rd/*, * then please migrate over to using the device names * /dev/md*, /dev/loop* and /dev/ram*. * The devfs-compat rules will be removed in the future. * For reference see Bug #269359. * * For more information on udev on Gentoo, writing udev rules, and * fixing known issues visit: * http://www.gentoo.org/doc/en/udev-guide.xml
Wichtig: sys-fs/udev-151-r4 USE=“-devfs-compat“ ← sonst gibt es Konflikte mit dem device-mapper und lvm2
* udev-151 does not support Linux kernel before version 2.6.25! * For a reliable udev, use at least kernel 2.6.27 * * If after the udev update removable devices or CD/DVD drives * stop working, try re-emerging HAL before filling a bug report * * persistent-net does assigning fixed names to network devices. * If you have problems with the persistent-net rules, * just delete the rules file * rm /etc/udev/rules.d/70-persistent-net.rules * and then reboot. * * This may however number your devices in a different way than they are now. * * If you build an initramfs including udev, then please * make sure that the /sbin/udevadm binary gets included, * and your scripts changed to use it,as it replaces the * old helper apps udevinfo, udevtrigger, ... * * mount options for directory /dev are no longer * set in /etc/udev/udev.conf, but in /etc/fstab * as for other directories. * * This version of udev no longer has devfs-compat enabled * If you use /dev/md/*, /dev/loop/* or /dev/rd/*, * then please migrate over to using the device names * /dev/md*, /dev/loop* and /dev/ram*. * The devfs-compat rules will be removed on the next udev update. * For reference see Bug #269359. * * This version of udev no longer has use flag old-hd-rules enabled * So all special rules for /dev/hd* devices are missing * Please migrate to the new libata if you need these rules. * They will be completely removed on the next udev update. * * For more information on udev on Gentoo, writing udev rules, and * fixing known issues visit: * http://www.gentoo.org/doc/en/udev-guide.xml
* The HAL daemon needs to be running for certain applications to * work. Suggested is to add the init script to your start-up * scripts, this should be done like this : * `rc-update add hald default` * Access to hal is not protected by either policykit or the plugdev group. * If you have problems discovering/configuring hardware, try adding * yourself to plugdev. * IF you have additional applications which consume ACPI events, you * should consider installing acpid to allow applications to share ACPI * events. * If you wish to use a non US layout, you may do so by executing: * setxkbmap <layout> or by utilizing your Desktop Environment's * Keyboard Layout Settings mechanism. * Under GNOME, this is gnome-keyboard-properties, and under KDE * it is kxkb. * In order have suspend/hibernate function with HAL or apps that use HAL * (such as gnome-power-manager), you should build HAL with the laptop * useflag which will install pm-utils. * X Input Hotplugging (if you build xorg-server with the HAL useflag) * reads user specific configuration from /etc/hal/fdi/policy/. * You should remove the Input sections from your xorg.conf once you have * migrated the rules to a HAL fdi file.
* Installation of SQLite with "tcl" USE flag enabled provides more (TCL-unrelated) functionality.
* Please note that this ebuild makes the assumption that you're * using /boot/grub/ for your grub configuration. * * To use your new grub splashes edit your /boot/grub/grub.conf * You can see available splash screens by running * `ls /boot/grub/ | grep xpm`
* Please install app-text/evince for print preview functionality. * Alternatively, check "gtk-print-preview-command" documentation and * add it to your gtkrc.
* Old versions of installed libraries were detected on your system. * In order to avoid breaking packages that depend on these old libs, * the libraries are not being removed. You need to run revdep-rebuild * in order to remove these old dependencies. If you do not have this * helper program, simply emerge the 'gentoolkit' package. * * # revdep-rebuild --library libhistory.so.5 * # revdep-rebuild --library libreadline.so.5 * * Once you've finished running revdep-rebuild, it should be safe to * delete the old libraries. Here is a copy & paste for the lazy: * # rm '/lib64/libhistory.so.4' * # rm '/lib64/libhistory.so.5' * # rm '/lib64/libreadline.so.4' * # rm '/lib64/libreadline.so.5'
* After upgrading app-text/poppler you may need to reinstall packages * depending on it. If you have gentoolkit installed, you can find those * with `equery d poppler`.
* * If after upgrading it doesn't work, please remove the * '~/.config/deluge' directory and try again, but make a backup * first! * * * To start the daemon either run 'deluged' as user * or modify /etc/conf.d/deluged and run * /etc/init.d/deluged start as root * You can still use deluge the old way * * For more information look at http://dev.deluge-torrent.org/wiki/Faq
* * To enable mod_proxy_html, you need to edit your /etc/conf.d/apache2 file and * add '-D PROXY_HTML' to APACHE2_OPTS. * * * Configuration file installed as * /etc/apache2/modules.d/27_mod_proxy_html.conf * You may want to edit it before turning the module on in /etc/conf.d/apache2 *
* Please run `/usr/sbin/sensors-detect' in order to setup * /etc/conf.d/lm_sensors. * * /etc/conf.d/lm_sensors is vital to the init-script. * Please make sure you also add lm_sensors to the desired * runlevel. Otherwise your I2C modules won't get loaded * on the next startup. * * You will also need to run the above command if you're upgrading from * <=lm_sensors-2.9.0, as the needed entries in /etc/conf.d/lm_sensors has * changed. * * Be warned, the probing of hardware in your system performed by * sensors-detect could freeze your system. Also make sure you read * the documentation before running lm_sensors on IBM ThinkPads. * * Please refer to the lm_sensors documentation for more information. * (http://www.lm-sensors.org/wiki/Documentation)
* Please run `/usr/sbin/sensors-detect' in order to setup * /etc/conf.d/lm_sensors. * * /etc/conf.d/lm_sensors is vital to the init-script. * Please make sure you also add lm_sensors to the desired * runlevel. Otherwise your I2C modules won't get loaded * on the next startup. * * You will also need to run the above command if you're upgrading from * <=lm_sensors-2, as the needed entries in /etc/conf.d/lm_sensors has * changed. * * Be warned, the probing of hardware in your system performed by * sensors-detect could freeze your system. Also make sure you read * the documentation before running lm_sensors on IBM ThinkPads. * * Also make sure you have read: * http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31 * * Please refer to the lm_sensors documentation for more information. * (http://www.lm-sensors.org/wiki/Documentation)
* dhcpcd-3 command line support enabled * You have installed dhcpcd with zeroconf support. * This means that it will always obtain an IP address even if no * DHCP server can be contacted, which will break any existing * failover support you may have configured in your net configuration. * This behaviour can be controlled with the -L flag. * See the dhcpcd man page for more details.
* Starting from version 20080801, pambase optionally enables * SHA512-hashed passwords. For this to work, you need sys-libs/pam-1.0.1 * built against sys-libs/glibc-2.7 or later. * If you don't have support for this, it will automatically fallback * to MD5-hashed passwords, just like before. * * Please note that the change only affects the newly-changed passwords * and that SHA512-hashed passwords will not work on earlier versions * of glibc or Linux-PAM.
* Could not locate user configfile, so we will save a default one
* Your configuration for sys-apps/busybox-1.15.3 has been saved in
* /etc/portage/savedconfig/sys-apps/busybox-1.15.3 for your editing pleasure.
* You can edit these files by hand and remerge this package with
* USE=savedconfig to customise the configuration.
* You can rename this file/directory to one of the following for
* its configuration to apply to multiple versions:
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
* Sorry, but acl does not support the LINGUAS: de en
* If using baselayout-2 and not relying on kernel auto-detect * of your RAID devices, you need to add 'mdraid' to your 'boot' * runlevel. Run the following command: * rc-update add mdraid boot
* The utilities and demos previously bundled with freetype are now * optional. Enable the utils USE flag if you would like them * to be installed.
* The /etc/wget/wgetrc file has been relocated to /etc/wgetrc
* The default location for revdep-rebuild files has been moved * to /var/cache/revdep-rebuild when run as root.
* glsa-check since gentoolkit 0.3 has modified some output, * options and default behavior. The list of injected GLSAs * has moved to /var/lib/portage/glsa_injected, please * run 'glsa-check -p affected' before copying the existing checkfile.
* You need to restart ConsoleKit to get the new features. * This can be done with /etc/init.d/consolekit restart * but make sure you do this and then restart your session * otherwise you will get access denied for certain actions
* local configurations (also includes extensions) are moved from
* ${HOME}/.inkscape to ${HOME}/.config/inkscape within
* >=media-gfx/inkscape-0.47
* GNU info directory index is up-to-date.
* You must rebuild all drivers if upgrading from xorg-server 1.6 * or earlier, because the ABI changed. If you cannot start X because * of module version mismatch errors, this is your problem. * You can generate a list of all installed packages in the x11-drivers * category using this command: * emerge portage-utils; qlist -I -C x11-drivers/
* Please make sure you run revdep-rebuild after upgrade. * This is *extremely* important to ensure your system nspr works properly.
* It appears you are removing your system-vm! * Please run java-config -L to list available VMs, * then use java-config -S to set a new system-vm!
* A revdep-rebuild control file was installed to prevent reinstalls due to * missing dependencies (see bug #177925 for more info). Note that some parts * of the JVM may require dependencies that are pulled only through respective * USE flags (typically X, alsa, odbc) and some Java code may fail without them.
* The amd64 version ships the new 'plugin2' browser plugin which works * in Firefox 3+ and other recent browser versions. * For more info see https://jdk6.dev.java.net/plugin2/
* /etc/sgml/sgml-docbook.cat still exists! Not removing from /etc/sgml/xml-docbook-4.4.cat * This is normal behavior for an upgrade ... * /usr/share/sgml/docbook/xml-dtd-4.4/docbook.cat still exists! Not removing from /etc/sgml/xml-docbook-4.4.cat * This is normal behavior for an upgrade ...
* /etc/sgml/sgml-docbook.cat still exists! Not removing from /etc/sgml/xml-docbook-4.5.cat * This is normal behavior for an upgrade ... * /usr/share/sgml/docbook/xml-dtd-4.5/docbook.cat still exists! Not removing from /etc/sgml/xml-docbook-4.5.cat * This is normal behavior for an upgrade ...
* rtorrent colors patch * Set colors using the options below in .rtorrent.rc: * Options: done_fg_color, done_bg_color, active_fg_color, active_bg_color * Colors: 0 = black, 1 = red, 2 = green, 3 = yellow, 4 = blue, * 5 = magenta, 6 = cyan and 7 = white * Example: done_fg_color = 1
* NOTE: To run wireshark as normal user you have to add yourself into * wireshark group. This security measure ensures that only trusted * users allowed to sniff your traffic.
* Neon has a policy of breaking API across minor versions, this means * that any package that links against Neon may be broken after * updating. They will remain broken until they are ported to the * new API. You can downgrade Neon to the previous version by doing: * * emerge --oneshot '<net-misc/neon-0.29' * * You may also have to downgrade any package that has not been * ported to the new API yet.
* The following fontconfig configuration files have been installed: * * 20-unhint-small-dejavu-sans-mono.conf * 20-unhint-small-dejavu-sans.conf * 20-unhint-small-dejavu-serif.conf * 57-dejavu-sans-mono.conf * 57-dejavu-sans.conf * 57-dejavu-serif.conf * * Use `eselect fontconfig` to enable/disable them. * * Starting with dejavu-2.22 font ligatures were re-imported in DejaVu * That means that you'll possibly encounter the infamous ligature bug * with pango-enabled Firefox (e.g. 'fi' and 'fl' will occasionally * overlap). This will be fixed in Firefox-3.x. Until this happens * either use Firefox without pango (MOZ_DISABLE_PANGO=1), or use * dejavu-2.21
* To use this package you will also need a dictionary. * Hunspell uses myspell format dictionaries; find them * in the app-dicts category as myspell-<LANG>.
* For information about installing a printer and general cups setup * take a look at: http://www.gentoo.org/doc/en/printing-howto.xml
* In the case that you haven't yet enabled command-line completion * for eselect, you can run: * * eselect bashcomp enable eselect * * to install locally, or * * eselect bashcomp enable --global eselect * * to install system-wide.
* Please follow the munin documentation to set up the plugins you * need, afterwards start munin-node via /etc/init.d/munin-node. * To have munin's cronjob automatically configured for you if this is * your munin master installation, please: * emerge --config net-analyzer/munin * * Please note that the crontab has undergone some modifications * since 1.3.2, and you should update to it!
Nach dem Update musste ich den Nodenamen von Hand auf das gleiche wie in der 'munin.conf' setzten.
Datei: /etc/munin/munin-node.conf
# Set this if the client doesn't report the correct hostname when # telnetting to localhost, port 4949 # host_name meinhost
Und dann den Node neustarten:
# /etc/init.d/munin-node restart
* In the case that you haven't yet enabled command-line completion * for dbus-glib, you can run: * * eselect bashcomp enable dbus * * to install locally, or * * eselect bashcomp enable --global dbus * * to install system-wide.
* Sorry, but meld does not support the LINGUAS: en
* To complete the installation, run: * nxsetup --install --setup-nomachine-key * This will use the default Nomachine SSH key * If you had older NX servers installed, you may need to add "--clean --purge" to the nxsetup command
* rrdtool dump 1.3 does emit completely legal xml. Basically this means that * it contains an xml header and a DOCTYPE definition. Unfortunately this * causes older versions of rrdtool restore to be unhappy. * * To restore a new dump with an old rrdtool restore version, either remove * the xml header and the doctype by hand (both on the first line of the dump) * or use rrdtool dump --no-header. * * Note: rrdtool-1.3.x doesn't have any default font bundled. Thus if you've * upgraded from rrdtool-1.2.x and don't have any font installed to make * lables visible, please, install some font, e.g. media-fonts/dejavu.
* XChat binary has been renamed from xchat-2 to xchat.
* To use the -A (askpass) option, you need to install a compatible * password program from the following list. Starred packages will * automatically register for the use with sudo (but will not force * the -A option): * * [*] net-misc/ssh-askpass-fullscreen * net-misc/x11-ssh-askpass * * You can override the choice by setting the SUDO_ASKPASS environmnent * variable to the program you want to use.
* If you need a symlink to one of Erlang's binaries, * please open a bug on http://bugs.gentoo.org/ * * Gentoo's versioning scheme differs from the author's, so please refer to this version as R13B04
* OpenEXR was divided into IlmBase, OpenEXR, and OpenEXR_Viewers. * Viewers are available in OpenEXR_Viewers package. * If you want them, run: emerge media-gfx/openexr_viewers
* blender uses python integration. As such, may have some * inherit risks with running unknown python scripting. * * CVE-2008-1103-1.patch has been removed as it interferes * with autosave undo features. Up stream blender coders * have not addressed the CVE issue as the status is still * a CANDIDATE and not CONFIRMED. * * It is recommended to change your blender temp directory * from /tmp to ~tmp or another tmp file under your home * directory. This can be done by starting blender, then * dragging the main menu down do display all paths.
* If this is your first install of avahi please reload your dbus config * with /etc/init.d/dbus reload before starting avahi-daemon!
* You have to configure your mt-daapd.conf following * /etc/mt-daapd.conf.example file. * You need to edit you extensions list in /etc/mt-daapd.conf * if you want your mt-daapd to serve ogg files. * If you want to start more than one mt-daapd service, symlink * /etc/init.d/mt-daapd to /etc/init.d/mt-daapd.<name>, and it will * load the data from /etc/mt-daapd.d/<name>.conf. * Make sure that you have different cache directories for them.
* This package no longer provides a separate init script. * Please utilize the new bridge support in baselayout.
* cblas has been eselected to gsl
* If you seek support, please file a bug report at * https://bugs.gentoo.org and post the output of * `emerge --info =www-client/opera-10.11' * To change the UI language, choose [Tools] -> [Preferences], open the * [General] tab, click on [Details...] then [Choose...] and point the * file chooser at /opt/opera/share/opera/locale/, then enter the * directory for the language you want and [Open] the .lng file.
* * Run /usr/sbin/libpng-1.4.x-update.sh to fix libtool archives (.la) * * Old versions of installed libraries were detected on your system. * In order to avoid breaking packages that depend on these old libs, * the libraries are not being removed. You need to run revdep-rebuild * in order to remove these old dependencies. If you do not have this * helper program, simply emerge the 'gentoolkit' package. * * # revdep-rebuild --library libpng12.so.0 * * Once you've finished running revdep-rebuild, it should be safe to * delete the old libraries. Here is a copy & paste for the lazy: * # rm '/usr/lib64/libpng12.so.0'
* Library names have changed since earlier versions of xcb-util; * you must rebuild packages that have linked against <xcb-util-0.3.0.
* The Gstreamer plugins setup has changed quite a bit on Gentoo, * applications now should provide the basic plugins needed. * The new seperate plugins are all named 'gst-plugins-<plugin>'. * To get a listing of currently available plugins execute 'emerge -s gst-plugins-'. * In most cases it shouldn't be needed though to emerge extra plugins.
* The Gstreamer plugins setup has changed quite a bit on Gentoo, * applications now should provide the basic plugins needed. * * The new seperate plugins are all named 'gst-plugins-<plugin>'. * To get a listing of currently available plugins execute 'emerge -s gst-plugins-'. * In most cases it shouldn't be needed though to emerge extra plugins.
* /etc/conf.d/rc is no longer used for configuration. * Please migrate your settings to /etc/rc.conf as applicable * and delete /etc/conf.d/rc * Auto-adding 'termencoding' service to your boot runlevel * Auto-adding 'bootmisc' service to your boot runlevel * Auto-adding 'fsck' service to your boot runlevel * Auto-adding 'hostname' service to your boot runlevel * Auto-adding 'hwclock' service to your boot runlevel * Auto-adding 'keymaps' service to your boot runlevel * Auto-adding 'localmount' service to your boot runlevel * Auto-adding 'modules' service to your boot runlevel * Auto-adding 'mtab' service to your boot runlevel * Auto-adding 'net.lo' service to your boot runlevel * Auto-adding 'procfs' service to your boot runlevel * Auto-adding 'root' service to your boot runlevel * Auto-adding 'swap' service to your boot runlevel * Auto-adding 'sysctl' service to your boot runlevel * Auto-adding 'termencoding' service to your boot runlevel * Auto-adding 'urandom' service to your boot runlevel * Auto-adding 'device-mapper' service to your boot runlevel * Auto-adding 'lvm' service to your boot runlevel * Add on services (such as RAID/dmcrypt/LVM/etc...) are now stand alone * init.d scripts. If you use such a thing, make sure you have the * required init.d scripts added to your boot runlevel. * Converting your /etc/modules.autoload.d/ files to /etc/conf.d/modules * Auto-adding 'udev' service to your sysinit runlevel * //etc/conf.d/net.example has been removed. * The new file is //usr/share/doc/openrc-0.6.1-r1/net.example * //etc/conf.d/wireless.example is deprecated and has been removed. * If you are using the old style network scripts, * Configure wireless settings in //etc/conf.d/net * after reviewing //usr/share/doc/openrc-0.6.1-r1/net.example * You should now update all files in /etc, using etc-update * or equivalent before restarting any services or this host. * * Please read the migration guide available at: * http://www.gentoo.org/doc/en/openrc-migration.xml
LOG: preinst /etc/conf.d/rc is no longer used for configuration. Please migrate your settings to /etc/rc.conf as applicable and delete /etc/conf.d/rc LOG: postinst You should now update all files in /etc, using etc-update or equivalent before restarting any services or this host. Please read the migration guide available at: http://www.gentoo.org/doc/en/openrc-migration.xml
* It is required that you add 'console=tty1' to your kernel * command line parameters. * * After these modifications, the relevant part of the kernel command * line might look like: * splash=silent,fadein,theme:emergence console=tty1 * * Please note that the 'fbsplash' kernel patch has now been renamed to * 'fbcondecor'. Accordingly, the old 'splash' initscript is now called * 'fbcondecor'. Make sure you update your system. See: * http://dev.gentoo.org/~spock/projects/fbcondecor/#history * for further info about the name changes. * * Also note that splash_util has now been split into splash_util, fbsplashd * and fbcondecor_ctl.
* You have an invalid TIMEZONE setting in /etc/timezone * Your /etc/localtime has been reset to Factory; enjoy!
* libdrm's ABI may have changed without change in library name * Please rebuild media-libs/mesa, x11-base/xorg-server and * your video drivers in x11-drivers/*.
* You have enabled the Cairo XCB backend which is used only by * a select few apps. The Cairo XCB backend is presently * un-maintained and needs a lot of work to get it caught up * to the Xrender and Xlib backends, which are the backends used * by most applications. See: * http://lists.freedesktop.org/archives/xcb/2008-December/004139.html
* Warning, we no longer overwrite /sbin/lvm and /sbin/dmsetup with * their static versions. If you need the static binaries, * you must append .static the filename! * USE flag nocman is deprecated and replaced * with the cman USE flag. * * USE flags clvm and cman are masked * by default and need to be unmasked to use them * * If you are using genkernel and root-on-LVM, rebuild the initramfs. * lvm volumes are no longer automatically created for * baselayout-2 users. If you are using baselayout-2, be sure to * run: # rc-update add lvm boot * Do NOT add it if you are using baselayout-1 still.
* CONFIG_DM_CRYPT: is not set (required for cryptsetup) * * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. * This ebuild introduces a new set of scripts and configuration * than the last version. If you are currently using /etc/conf.d/cryptfs * then you *MUST* copy your old file to: * /etc/conf.d/dmcrypt * Or your encrypted partitions will *NOT* work. * Please see the example for configuring a LUKS mountpoint * in /etc/conf.d/dmcrypt * * If you are using baselayout-2 then please do: * rc-update add dmcrypt boot * This version introduces a command line arguement 'key_timeout'. * If you want the search for the removable key device to timeout * after 10 seconds add the following to your bootloader config: * key_timeout=10 * A timeout of 0 will mean it will wait indefinitely. * * Users using cryptsetup-1.0.x (dm-crypt plain) volumes must use * a compatibility mode when using cryptsetup-1.1.x. This can be * done by specifying the cipher (-c), key size (-s) and hash (-h). * For more info, see http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Issues_with_Specific_Versions_of_cryptsetup
* If you don't have kvm compiled into the kernel, make sure you have * the kernel module loaded before running kvm. The easiest way to * ensure that the kernel module is loaded is to load it on boot. * For AMD CPUs the module is called 'kvm-amd' * For Intel CPUs the module is called 'kvm-intel' * Please review /etc/conf.d/modules for how to load these * * Make sure your user is in the 'kvm' group * Just run 'gpasswd -a <USER> kvm', then have <USER> re-login. * * You will need the Universal TUN/TAP driver compiled into your * kernel or loaded as a module to use the virtual network device * if using -net tap. You will also need support for 802.1d * Ethernet Bridging and a configured bridge if using the provided * kvm-ifup script from /etc/kvm.
* You can find an example /etc/ntp.conf in /usr/share/ntp/ * Review /etc/ntp.conf to setup server info. * Review /etc/conf.d/ntpd to setup init.d info. * The way ntp sets and maintains your system time has changed. * Now you can use /etc/init.d/ntp-client to set your time at * boot while you can use /etc/init.d/ntpd to maintain your time * while your machine runs
* The upstream tarball for the 'Natural Gentoo' theme also contains a GRUB * splash image which is not installed by this ebuild. See: * http://www.kde-look.org/content/show.php?content=49074 * if you are interested in this.
* * To avoid automounting and auto(un)installing with /boot, * just export the DONT_MOUNT_BOOT variable. *
* * To avoid automounting and auto(un)installing with /boot, * just export the DONT_MOUNT_BOOT variable. * * *** IMPORTANT NOTE: you must run grub and install * the new version's stage1 to your MBR. Until you do, * stage1 and stage2 will still be the old version, but * later stages will be the new version, which could * cause problems such as an unbootable system. * This means you must use either grub-install or perform * root/setup manually! For more help, see the handbook: * http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=10#grub-install-auto * To interactively install grub files to another device such as a USB * stick, just run the following and specify the directory as prompted: * emerge --config =grub-0.97-r10 * Alternately, you can export GRUB_ALT_INSTALLDIR=/path/to/use to tell * grub where to install in a non-interactive way.
* Some software with pre-loaded PAM libraries might experience * warnings or failures related to missing symbols and/or versions * after any update. While unfortunate this is a limit of the * implementation of PAM and the software, and it requires you to * restart the software manually after the update. * * You can get a list of such software running a command like * lsof / | egrep 'DEL.*libpam\.so' * * Because of a bug present up to version 1.1.1-r2, you might have * an executable /var/log/tallylog file. If it is so, you can safely * correct it by running the command * chmod -x /var/log/tallylog
* This package can use iconv or icu for loading messages * and transcoding, but not both. ICU will precede.
* This package installs one or more file names containing characters that * do not match your current locale settings. The current setting for * filesystem encoding is 'UTF-8'. * * usr/share/games/glest/data/lang/espa�ol.lng * usr/share/games/glest/scenarios/storming/storming_espa�ol.lng * usr/share/games/glest/tutorials/advanced_tutorial/advanced_tutorial_espa�ol.lng * usr/share/games/glest/tutorials/basic_tutorial/basic_tutorial_espa�ol.lng * * Remember, in order to play games, you have to * be in the 'games' group. * Just run 'gpasswd -a <USER> games', then have <USER> re-login.
* Nouveau DRM not detected. If you want any kind of * acceleration with nouveau, emerge x11-base/nouveau-drm or * enable CONFIG_DRM_NOUVEAU in the kernel.
* SVGA and nouveau drivers are available only via gallium interface. * Enable gallium useflag if you want to use them.
* CONFIG_USB_SUSPEND: is not set when it should be. * CONFIG_IDE: should not be set. But it is. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. * In the case that you haven't yet enabled command-line completion * for udisks, you can run: * * eselect bashcomp enable udisks * * to install locally, or * * eselect bashcomp enable --global udisks * * to install system-wide.
* For more verbose debug information, export the following variables: * PHONON_VLC_DEBUG=3 * PHONON_DEBUG=1 * * To make KDE detect the new backend without reboot, run: * kbuildsycoca4 --noincremental
* For improved key search functionality, install app-crypt/dirmngr.
* QA: do not use full paths with rpm_unpack -- use ./ paths instead * Make sure you have recieved the a license for ifc * To receive a restrictive non-commercial licenses , you need to register at: * http://www.intel.com/cd/software/products/asmo-na/eng/download/download/219771.htm * Read the website for more information on this license. * You cannot run ifc without a license file. * Then put the license file into //opt/intel/licenses * * To use ifc issue first * source /etc/profile * Debugger is installed with dev-lang/idb
* Select an overlay and add it using * * layman -a overlay-name * * If this is the very first overlay you add with layman, * you need to append the following statement to your * /etc/make.conf file: * * source /var/lib/layman/make.conf * * If you modify the 'storage' parameter in the layman * configuration file (/etc/layman/layman.cfg) you will * need to adapt the path given above to the new storage * directory. * * Please add the 'source' statement to make.conf only AFTER * you added your first overlay. Otherwise portage will fail.