http://cdn.x.indowebster.com/download-vip/85/p16q5cdaid1vek10vqro0umve83.mkv/%5B www.indowebster.com%5D-ByM-idfl.us-Underworld4.RCBDRIP.480p.Ganool.mkv buptwugh wrote: [ebuild R ] dev-lang/python-2.7.

2-r3 USE="berkdb* gdbm ipv6 ncurses readline ssl threads tk (wide-unicode) xml -build* -doc -examples -sqlite -wininst" 0 kB I think this output ( '-build' part, to be exact) makes it pretty obvious that t his python slot does need rebuild. Though the order makes it a bit tricky. Try 'emerge -1O python:2.7' first, if it works, rebuild afterwards, if not, tink er with useflags, till you can temporarily skip libxcb ('-tk', perhaps). -xml [ebuild U ] x11-libs/libxcb-1.8.1 [1.7] USE="doc* (-selinux) -static-libs" 368 kB [ebuild U ] x11-proto/xcb-proto-1.7.1 [1.6-r2] 104 kB [ebuild N ] app-text/asciidoc-8.6.7 USE="-examples -graphviz -highlight ( -test) -vim-syntax" 869 kB [ebuild NS ] app-text/docbook-xml-dtd-4.5-r1 [4.1.2-r6, 4.2-r2, 4.3-r1, 4. 4-r2] 97 kB ImportError: No module named _elementtree emerge --depclean -pv python-updater Traceback (most recent call last): File "/var/tmp/portage/x11-libs/libxcb-1.8.1/work/libxcb-1.8.1/src/c_client.py ", line 2, in <module> from xml.etree.cElementTree import * File "/usr/lib64/python2.7/xml/etree/cElementTree.py", line 3, in <module> from _elementtree import * #############<<< Gentoo Linux Documentation -- A Port age Introduction (p4 of 11) Code Listing 3.10: Updating your system # emerge --update --ask world Portage will then search for newer version of the applications you have insta lled. However, it will only verify the versions for the applications you have explicitly installed (the applications listed in /var/lib/portage/world) - it does not t horoughly check their dependencies. If you want to update the dependencies of th ose packages as well, add the --deep argument: Code Listing 3.11: Updating your system with dependencies # emerge --update --deep world Still, this doesn't mean all packages: some packages on your system are neede d during the compile and build process of packages, but once that package is ins talled, these dependencies are no longer required. Portage calls those build dependen cies. To include those in an update cycle, add --with-bdeps=y: Code Listing 3.12: Updating your entire system # emerge --update --deep --with-bdeps=y world

Since security updates also happen in packages you have not explicitly instal led on your system (but that are pulled in as dependencies of other programs), i t is recommended to run this command once in a while. If you have altered any of your USE flags lately you might want to add --newu se as well. Portage will then verify if the change requires the installation of new packages or recompilation of existing ones: Code Listing 3.13: Performing a full update # emerge --update --deep --with-bdeps=y --newuse world Metapackages Some packages in the Portage tree don't have any real content but are used to install a collection of packages. For instance, the kde-meta package will insta ll a complete KDE environment on your system by pulling in various KDE-related pac kages as dependencies. If you ever want to remove such a package from your system, running emerge -unmerge on the package won't have much effect as the dependencies remain on the system. Portage has the functionality to remove orphaned dependencies as well, but si nce the availability of software is dynamically dependent you first need to upda te your entire system fully, including the new changes you applied when changing USE flags. After this you can run emerge --depclean to remove the orphaned dependenc ies. When this is done, you need to rebuild the applications that were dynamically link ed to the now-removed software titles but don't require them anymore. All this is handled with the following three commands: Code Listing 3.14: Removing orphaned dependencies # emerge --update --deep --newuse world # emerge --depclean # revdep-rebuild ########################################## Leave out "bash#" as that only indicates a root bash prompt....you want to be ty ping just: mount -n -o remount,rw / Just looking at what caused the problem in the first place. The problem happened because you formatted the drive and didn't copy over the contents of /usr to it . When you now boot the system it mounts the empty drive under /usr....so you no longer have /usr/bin, /usr/lib, /usr/local, /usr/sbin, /usr/share etc. I would fix it the following way: 1) Boot into "diagnostic mode" or use a live CD like knoppix, just so that you c an have access to your root file system. 2) To fix it so you can boot suse again edit /etc/fstab. You want to comment out the line with /usr in it. To comment out the line just put a # at the beginning

. It should look something like: #/dev/hdb1 /usr reiserfs defaults 1 1 You should now be able to reboot and get back into suse. 3) Create a temp mount point for it and mount it: # mkdir /mnt/temp # mount /dev/hdb1 /mnt/temp I am guessing that /dev/hdb1 is correct. You may have to alter this to reflect y our system, the correct device will be on the same line in /etc/fstab as /usr. 4) Copy over the entire contents of your /usr to the new drive: # cp -r /usr/* /mnt/temp 5) Make a cup of tea, walk the dog or have a beer! ;) 6) Once copying has finished, mount the drive in the correct place and test: # umount /mnt/temp # mount /dev/hdb1 /usr # ls /usr You should be able to read the contents. 7) Uncomment that line from /etc/fstab so that the drive is mounted automaticall y when booting. ################################## FYI you may see command on this and other forums given with a prompt, a "#" indi cates a root prompt and a "$" is for just a regular user, eg: # mount -n -o remount,rw / or $ ls /home/user When using these commands leave out the # or $. http://distfiles.gentoo.org/distfiles/udev-init-scripts-10.tar.bz2 http://www.kernel.org/pub/linux/utils/kernel/kmod/kmod-7.tar.xz http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked /dev/fd/62: No such file or directory /dev/fd -> /proc/self/fd <sys-apps/openrc-0.9.9 (<sys-apps/openrc-0.9.9 is blocking sys-fs/udev-9999) blocks B sys-apps/openrc-0.9.9 <sys-apps/openrc-0.9.9 is blocking sys-fs/udev-99 99 'emerge -1 baselayout udev sysvinit openrc' Unmasking these packages and following the migration guide made the work. =sys-apps/baselayout-2.0.0 ~amd64 =sys-apps/openrc-0.4.2 ~amd64 =sys-fs/udev-141 ~amd64 =sys-apps/sysvinit-2.86-r12 ~amd64 =sys-fs/cryptsetup-1.0.6-r2 ~amd64 User-Specific Configuration When you need to override Portage's behaviour regarding the installation of soft ware, you will end up editing files within /etc/portage. You are highly recommen ded to use files within /etc/portage and highly discouraged to override the beha viour through environment variables! Within /etc/portage you can create the following files: package.mask which lists the packages you never want Portage to install package.unmask which lists the packages you want to be able to install even

though the Gentoo developers highly discourage you from emerging them package.accept_keywords which lists the packages you want to be able to inst all even though the package hasn't been found suitable for your system or archit ecture (yet) package.use which lists the USE flags you want to use for certain packages w ithout having the entire system use those USE flags These don't have to be files; they can also be directories that contain one file per package. More information about the /etc/portage directory and a full list of possible files you can create can be found in the Portage man http://distfiles.gentoo.org/distfiles/texlive-20110705-source.tar.xz http://ftp.halifax.rwth-aachen.de/gentoo/distfiles/kpathsea-texmf.d-3.tar.xz ############################################################ 1. What is udev? The /dev Directory When Linux-users talk about the hardware on their system in the vicinity of peop le who believe Linux is some sort of virus or brand of coffee, the use of "slash dev slash foo" will return a strange look for sure. But for the fortunate user (and that includ es you) using /dev/sda1 is just a fast way of explaining that we are talking about the primary master SATA, first partition. Or aren't we? We all know what a device file is. Some even know why device files have special numbers when we take a closer look at them when we issue ls -l in /dev. But what we always take for granted is that the primary SATA disk is referred to as /dev/sda. You might not see it this way, but this is a flaw by design. Think about hotpluggable devices like USB, IEEE1394, hot-swappable PCI, ... What is the first device? And for how long? What will the other devices be named whe n the first one disappears? How will that affect ongoing transactions? Wouldn't it be fun that a printing jo b is suddenly moved from your supernew laserprinter to your almost-dead matrix p rinter because your mom decided to pull the plug of the laserprinter which happened to be the first printer? Enter udev. The goals of the udev project are both interesting and needed: Runs in userspace Dynamically creates/removes device files Provides consistent naming Provides a user-space API Every time a change happens within the device structure, the kernel emits a ueve nt which gets picked up by udev. udev then follows the rules as declared in the /etc/udev/rules.d and /lib/udev/rules.d directories. Based on the informatio n contained within the uevent, it finds the rule or rules it needs to trigger and performs the required actions. These actions can be creating or deleting dev ice files, but can also trigger the loading of particular firmware files into th e kernel memory. 2. Using udev on Gentoo Requirements udev is meant to be used in combination with a 2.6 kernel (like gentoo-sources w

ith the default 10.0 profile). If you're using such a kernel then you just shoul d have no issues whatsoever with using udev as the necessary support is built-in in all stable sys-apps/base layout versions. Normally, udev should already be installed on your system, but if this is not the case, then it is easy to install: Code Listing 2.1: Installing udev # emerge udev Kernelwise, be sure to activate the following options: Code Listing 2.2: Required kernel options General Setup ---> (Make sure the following item is *not* enabled) [ ] enable deprecated sysfs features to support old userspace tools File Systems ---> [*] Inotify support for userspace Pseudo filesystems ---> [*] Virtual memory file system support (former shm fs) If you use genkernel, you don't need to do anything special. Genkernel sets up u dev by default. 3. Known Issues Missing device node files at boot If you can't boot successfully because you get an error about /dev/null not foun d, or because the initial console is missing, the problem is that you lack some device files that must be available before /dev is mounted and handled by udev. This is commo n on Gentoo machines installed from old media. If you run sys-apps/baselayout-1.8.12 or later, this problem is alleviated since the boot process should still manage to complete. However, to get rid of those annoying warnings, you should create the missing de vice nodes as described below. To see which devices nodes are present before the /dev filesystem is mounted, ru n the following commands: Code Listing 3.1: Listing device nodes available at boot # # # # mkdir test mount --bind / test cd test/dev ls

The devices needed for a successful boot are /dev/null and /dev/console. If they didn't show up in the previous test, you have to create them manually. Issue the following commands in the test/dev/ directory: Code Listing 3.2: Creating necessary device node files # mknod -m 660 console c 5 1 # mknod -m 660 null c 1 3 When you're finished, don't forget to unmount the test/ directory: Code Listing 3.3: Unmounting the test/ directory # cd ../.. # umount test # rmdir test udev and nvidia

If you use the proprietary driver from nVidia and the X server fails to start on a udev-only system, then make sure you have the nvidia module listed in /etc/conf.d/modules. No Consistent Naming between DevFS and udev Even though our intention is to have a consistent naming scheme between both dyn amical device management solutions, sometimes naming differences do occur. One reported clash is with a HP Smart Array 5i RAID controller (more precisely t he cciss kernel module). With udev, the devices are named /dev/cciss/cXdYpZ with X, Y and Z regular numbers. With devfs, the devices are / dev/hostX/targetY/partZ or symlinked from /dev/cciss/cXdY. If this is the case, don't forget to update your /etc/fstab and bootloader confi guration files accordingly. The same happens with all-round symlinks that used to exist in /dev, such as /de v/mouse, which udev doesn't create anymore. Be certain to check your X configura tion file and see if the Device rule for your mouse points to an existing device file. Another issue is the difference in naming of terminals between devfs and udev. W hile devfs calls its terminals tty, udev calls them vc and tty. This could lead to a problem in case you are restricting root logins from consoles using /etc/se curetty. You will need to make sure that both tty1 and vc/1 are listed in /etc/s ecuretty to ensure that root can login using the console. Block device renaming Recent versions of udev (104 and up) along with newer kernel versions (2.6.19 an d up) may change your disc device names, due to a change in the kernel's libata implementation. A CD-RW device at /dev/hdc may be changed to /dev/sr0. While thi s is not normally a problem, it may cause issues for some applications that are hardcoded to look for devices at other locations. For example, media-sound/rip e xpects to find discs at /dev/cdrom, which becomes a problem if you use a newer k ernel and udev renames your device to /dev/cdrom1. To work around these issues, you must edit /etc/udev/rules.d/70-persistent-cd.ru les and assign the correct name to the device. For more information on writing udev rules, be sure to read Daniel Drake's guide . Network device renaming Sometimes unplugging and replugging a network device (like a USB WiFi card) can rename your net device each time, incrementing the number by one. When this happens, you'll see it become wlan0, wlan1, wlan2, etc. This is becaus e udev is adding additional rules to its rules file, instead of reloading the ex isting rules. Since udev watches its rules directory via inotify, you need inoti fy support in your kernel config: Code Listing 3.4: Enabling inotify support in the kernel File systems ---> [*] Inotify file change notification support [*] Inotify support for userspace

Now udev will retain proper names for your network devices. udev loads modules in an unpredictable order Sometimes udev loads modules in an undesired, unpredictable, or seemingly random order. This is especially common for systems that have multiple devices of the same type, as well as multimedia devices. This can affect the assigned numbers o f devices; for example, sound cards may sometimes swap numbers. There are a few solutions to fix device numbers and/or module load order. Ideall y, you can just use module parameters to specify your desired device number. Som e modules, such as ALSA, include the "index" parameter. Modules that use the ind ex parameter can be adjusted as shown. This example is for a system with two sou nd cards. The card with an index of 0 is designated as the first card. Once the parameters are changed, the module config files must be updated. Code Listing 3.5: Specifying module parameters # echo "option snd-ice1724 index=0" >> /etc/modprobe.d/alsa.conf # echo "option snd-ymfpci index=1" >> /etc/modprobe.d/alsa.conf # update-modules The above example is the preferred solution, but not all modules support paramet ers such as index. For these modules, you'll have to force the correct module lo ad order. First, you must stop udev from autoloading the modules by blacklisting them. Be sure to use the exact name of the module being loaded. For PCI devices , you'll need to use the module names obtained from the output of lspci -k, avai lable in the pciutils package. The following example uses DVB modules. Code Listing 3.6: Blacklisting modules # echo "blacklist b2c2-flexcop-pci" >> /etc/modprobe.d/dvb # echo "blacklist budget" >> /etc/modprobe.d/dvb # update-modules Next, load the modules in the correct order. Add them to /etc/conf.d/modules in the exact order you want them loaded. Code Listing 3.7: Loading modules in the correct order # nano -w /etc/conf.d/modules modules="budget b2c2-flexcop-pci" Other issues Support for the framebuffer devices (/dev/fb/*) comes with the kernel starting f rom version 2.6.6-rc2. For kernels older than 2.6.4 you have to explicitly include support for the /dev /pts filesystem. Code Listing 3.8: Enabling the /dev/pts filesystem File systems ---> Pseudo filesystems ---> [*] /dev/pts file system for Unix98 PTYs ######################################################################### During boot I get this message:

Code: * The mdraid init script is written for baselayout-2 * Please do not use it with baselayout-1 I found that a bit odd since I've just installed my gentoo system and I thought that if mdadm required baselayout-2=< it would have pulled that version during i nstall. However, baselayout-2 was not surprisingly masked. This confused me sinc e then you would expect mdadm being masked because it depends on a masked packag e. After some searching I dug up the Baselayout and OpenRC Migration Guide. Read ing it I imagined unmasking sys-apps/baselayout-2.0.0 and sys-apps/openrc-0.4.2 would be a logical decision, but then the version of udev was to low, expecting at least version 133, while the highest available in portage was 124-r2 (or 9999 but that seemed to obscure). The migration guide doesn't mention anything about this. Searching the forums doesn't yield any results what so ever. I did an "em erge --sync" prior to writing this, so an old portage tree is not the issue. emerge -v baselayout Code: Calculating dependencies... done! [ebuild U ] sys-apps/baselayout-2.0.0 [1.12.11.1] USE="-build (-bootstrap%) (-static%) (-unicode%*)" 23 kB [ebuild N ] sys-apps/openrc-0.4.2 USE="ncurses pam unicode -debug" 142 kB [blocks B ] <sys-fs/udev-133 ("<sys-fs/udev-133" is blocking sys-apps/openrc -0.4.2) [blocks B ] <sys-apps/sysvinit-2.86-r11 ("<sys-apps/sysvinit-2.86-r11" is bl ocking sys-apps/openrc-0.4.2) Total: 2 packages (1 upgrade, 1 new), Size of downloads: 164 kB Conflict: 2 blocks (2 unsatisfied) emerge --info Code: Portage 2.1.6.11 (default/linux/amd64/2008.0, gcc-4.3.2, glibc-2.8_p20080602-r1, 2.6.28.9 x86_64) ================================================================= System uname: Linux-2.6.28.9-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q9550_@_2.83GHzwith-glibc2.2.5 Timestamp of tree: Thu, 30 Apr 2009 08:45:02 +0000 app-shells/bash: 3.2_p39 dev-lang/python: 2.5.4-r2 dev-util/cmake: 2.6.2-r1 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.6-r2 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.5, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -mtune=nocona -mmmx -msse -msse2 -pipe -O3 -ftracer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shu tdown /usr/share/config" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf

/etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/ php/cli-php5/ext-active/ /etc/sandbox.d /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-march=nocona -mtune=nocona -mmmx -msse -msse2 -pipe -O3 -ftracer" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms str ict unmerge-orphans userfetch" GENTOO_MIRRORS="http://mirror.mdfnet.se/mirror/gentoo http://ftp.ing.umu.se/linu x/gentoo/ http://ftp.ds.karen.hj.se/gentoo/ http://ftp.df.lth.se/pub/gentoo/ " LANG="sv_SE.UTF-8" LC_ALL="sv_SE.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="sv sv_SE" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclu de=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X a52 acl alsa amd64 bash-completion berkdb bzip2 cdparanoia cdr cli crackl ib crypt cups dri dvd dvdr dvdread exif ffmpeg flac fortran freetype gdbm gpm gt k hal iconv isdnlog jabber jpeg lcms mad matroska midi mmx mmxext mp3 mpeg mudfl ap multilib ncurses nls nptl nptlonly offensive ogg opengl openmp pam pcre perl php png pppd python quicktime readline reflection ruby sdl session speex spell s pl sqlite sqlite3 sse sse2 sse3 ssl stream svg symlink sysfs tcpd theora tiff tr uetype unicode usb vim-syntax vorbis x264 xcomposite xinerama xorg xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens 1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident u sb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dm ix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear met er mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn _default authn_file authz_dbm authz_default authz_groupfile authz_host authz_own er authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env exp ires ext_filter file_cache filter headers include info log_config logio mem_cach e mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CAMERAS="canon" ELIBC="glibc" INPUT_DEVICES="evdev keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses te xt" LINGUAS="sv sv_SE" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, PORTAGE_CO MPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS cat /etc/portage/package.keywords Code: =net-p2p/transmission-1.52 ** =sys-apps/baselayout-2.0.0 ** =sys-apps/openrc-0.4.2 **

Thanks in advance! Last edited by mantono on Tue May 05, 2009 4:49 pm; edited 1 time in total Back to top View user's profile Send private message VoidMage Advocate Advocate Joined: 14 Oct 2006 Posts: 3964 PostPosted: Thu Apr 30, 2009 11:51 am Post subject: Reply with quote IIRC, you have to explicitly emerge all those packages at once: Code: 'emerge -1 baselayout udev sysvinit openrc' then portage will resolve that automatically. And '**' is nearly always unneeded - that's not for ~keyword packages, but for those, that lack a keyword for the arch (like 9999 ebuilds). Back to top View user's profile Send private message sera Developer Developer Joined: 29 Feb 2008 Posts: 938 Location: CEST PostPosted: Thu Apr 30, 2009 3:20 pm Post subject: Reply with quote Quote: [...], but then the version of udev was to low, expecting at least version 133, while the highest available in portage was 124-r2 (or 9999 but that seemed to ob scure). Code: equery list udev -p Lists also a version 141. Unmask this one as well. (equery is in gentoolkit) Make sure there is no init script for baselayout 1. An init script is a weak rea son to upgrade to baselayout 2 and openrc. Back to top View user's profile Send private message mantono n00b n00b Joined: 07 Apr 2006 Posts: 17 Location: Sweden, Stockholm

PostPosted: Fri May 01, 2009 8:48 am Post subject: Okey, thanks. I'll try that. Back to top View user's profile Send private message mantono n00b n00b Joined: 07 Apr 2006 Posts: 17 Location: Sweden, Stockholm

Reply with quote

PostPosted: Tue May 05, 2009 4:49 pm Post subject: Reply with quote Unmasking these packages and following the migration guide made the work. =sys-apps/baselayout-2.0.0 ~amd64 =sys-apps/openrc-0.4.2 ~amd64 =sys-fs/udev-141 ~amd64 =sys-apps/sysvinit-2.86-r12 ~amd64 =sys-fs/cryptsetup-1.0.6-r2 ~amd64 Problem solved. ################ http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked http://gentoo-distfiles.mirrors.tds.net/distfiles/openrc-0.9.9.3.tar.bz2 http://distfiles.gentoo.org/distfiles/baselayout-2.1.tar.bz2 http://distfiles.gentoo.org/distfiles/qt-everywhere-opensource-src-4.8.1.tar.gz http://distfiles.gentoo.org/distfiles/network-manager-applet-0.9.4.1.tar.xz