Cdemu( работает) (SOLVED)

Не знаю в чём толком проблема, не пускается и не работает cdemu. Пишет ошибку о неподерживаемой опции в Python, но тогда как её исправить ?


gateway dem # cdemu stat
/usr/lib64/python2.6/site-packages/cdemu/cdemu.py:698: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
  self.__print_error(_("Failed to connect to CDEmu daemon: %s") % (e.message))
ERROR: Failed to connect to CDEmu daemon: The name net.sf.cdemu.CDEMUD_Daemon was not provided by any .service files
ERROR: Failed to connect to daemon (bus: 'system')!
gateway dem # 

Установил и апплет для X к нему, он никак не реагирует на кликанья на нём, это и понятно.
Вот emerge --info http://pastebin.com/V89BGBKx
Есть Python в двух слотах:

gateway dem # eselect python list
Available Python interpreters:
  [1]   python2.6 *
  [2]   python3.1

Я думал над тем чтобы перейти на 3.1, но почитав анотацию( read news), не стал, там чётко и ясно пишут что пока не следует переходить на Python 3.1
Собственно и сама анотация:

gateway dem # eselect news read 2
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.

p.s. python-updater я не пускал после установки Python 3.1, хотя об этом пишется что следедует её выполнить, стоит ?

питон-апдейтер следует

питон-апдейтер следует запустить хотя бы потому, что есть проблемы с питоном ;)
для третьего питона это нужно сделать, только если ты сделаешь его системным, просто программы, которые в нем нуждаются, и так его используют и знают о нем ;)

Запустил python-updater,

Запустил python-updater, проблема так и осталась:

 * Compilation and optimization of Python modules for CPython 2.6 ...     [ ok ]
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.
gateway dem # cdemu stat
/usr/lib64/python2.6/site-packages/cdemu/cdemu.py:698: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
  self.__print_error(_("Failed to connect to CDEmu daemon: %s") % (e.message))
ERROR: Failed to connect to CDEmu daemon: The name net.sf.cdemu.CDEMUD_Daemon was not provided by any .service files
ERROR: Failed to connect to daemon (bus: 'system')!

И запуск соответсвенно:


gateway dem # /etc/init.d/cdemud start
cdemud               | * Caching service dependencies ...                 [ ok ]
cdemud               | * Loading CDemu userspace daemon ...               [ !! ]
cdemud               | * ERROR: cdemud failed to start
gateway dem # 

Demontager

Demontager написал(а):
gateway dem # /etc/init.d/cdemud start
cdemud               | * Caching service dependencies ...                 [ ok ]
cdemud               | * Loading CDemu userspace daemon ...               [ !! ]
cdemud               | * ERROR: cdemud failed to start
gateway dem # 

а ты добавил vhba модуль в автозагрузку? ))
lsmod | grep vhba

Да, vhba нет модулях.

Да, vhba нет в модулях. Соответсвенно, я отправился его заново компилить и тут ещё одни грабли появились, я сменил ядро на 2.6.36 и не genkernel(давненько), но vhba потом не рекомпилировал, на 2.6.35 у меня он компилировался, что сейчас не так, не пойму.


gateway dem # emerge -av vhba

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] sys-fs/vhba-1.2.1  0 kB

Total: 1 package (1 reinstall), Size of downloads: 0 kB

Would you like to merge these packages? [Yes/No] 

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-fs/vhba-1.2.1
 * vhba-module-1.2.1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                           [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                   [ ok ]
 * checking auxfile checksums ;-) ...                                                                                                  [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                 [ ok ]
 * CPV:  sys-fs/vhba-1.2.1
 * REPO: gentoo
 * USE:  amd64 elibc_glibc kernel_linux multilib userland_GNU
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/2.6.36-gentoo/build
 * Found sources for kernel version:
 *     2.6.36-gentoo
 * Checking for suitable kernel configuration options...                                                                                [ ok ]
 * Checking for suitable kernel configuration options...                                                                                [ ok ]
>>> Unpacking source...
>>> Unpacking vhba-module-1.2.1.tar.bz2 to /var/tmp/portage/sys-fs/vhba-1.2.1/work
>>> Source unpacked in /var/tmp/portage/sys-fs/vhba-1.2.1/work
>>> Preparing source in /var/tmp/portage/sys-fs/vhba-1.2.1/work/vhba-module-1.2.1 ...
 * Applying 1.2.1-parallel_build.patch ...                                                                                              [ ok ]
 * Applying 1.2.1-kerneldir.patch ...                                                                                                   [ ok ]
 * Applying vhba-1.2.1-kernel-2.6.33.patch ...                                                                                          [ ok ]
 * Applying vhba-1.2.1-kernel-2.6.34.patch ...                                                                                          [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-fs/vhba-1.2.1/work/vhba-module-1.2.1 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sys-fs/vhba-1.2.1/work/vhba-module-1.2.1 ...
ln: creating symbolic link `Module.symvers': File exists
 * Preparing vhba module
make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= KDIR=/usr/src/linux all 
kat/kat /usr/src/linux kernel.api.h kat/have_scsi_macros.c kat/scatterlist_has_page_link.c
KAT will test if C compiler works...ok
Checking kat/have_scsi_macros.c... true
Checking kat/scatterlist_has_page_link.c... true
make -C /usr/src/linux M=/var/tmp/portage/sys-fs/vhba-1.2.1/work/vhba-module-1.2.1 modules
make[1]: Entering directory `/usr/src/linux-2.6.36-gentoo'
make[1]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule.
  CC [M]  /var/tmp/portage/sys-fs/vhba-1.2.1/work/vhba-module-1.2.1/vhba.o
/var/tmp/portage/sys-fs/vhba-1.2.1/work/vhba-module-1.2.1/vhba.c:785: error: unknown field ‘ioctl’ specified in initializer
/var/tmp/portage/sys-fs/vhba-1.2.1/work/vhba-module-1.2.1/vhba.c:785: warning: initialization from incompatible pointer type
make[2]: *** [/var/tmp/portage/sys-fs/vhba-1.2.1/work/vhba-module-1.2.1/vhba.o] Error 1
make[1]: *** [_module_/var/tmp/portage/sys-fs/vhba-1.2.1/work/vhba-module-1.2.1] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.36-gentoo'
make: *** [modules] Error 2
 * ERROR: sys-fs/vhba-1.2.1 failed:
 *   Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=  KDIR=/usr/src/linux all
 * 
 * Call stack:
 *     ebuild.sh, line   54:  Called src_compile
 *   environment, line 3551:  Called linux-mod_src_compile
 *   environment, line 2723:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" 						CROSS_COMPILE=${CHOST}- 		LDFLAGS=\"$(get_abi_LDFLAGS)\" 						${BUILD_FIXES} 						${BUILD_PARAMS} 						${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
 * 
 * If you need support, post the output of 'emerge --info =sys-fs/vhba-1.2.1',
 * the complete build log and the output of 'emerge -pqv =sys-fs/vhba-1.2.1'.
 * The complete build log is located at '/var/tmp/portage/sys-fs/vhba-1.2.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/vhba-1.2.1/temp/environment'.
 * S: '/var/tmp/portage/sys-fs/vhba-1.2.1/work/vhba-module-1.2.1'

>>> Failed to emerge sys-fs/vhba-1.2.1, Log file:

>>>  '/var/tmp/portage/sys-fs/vhba-1.2.1/temp/build.log'

 * Messages for package sys-fs/vhba-1.2.1:

 * ERROR: sys-fs/vhba-1.2.1 failed:
 *   Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=  KDIR=/usr/src/linux all
 * 
 * Call stack:
 *     ebuild.sh, line   54:  Called src_compile
 *   environment, line 3551:  Called linux-mod_src_compile
 *   environment, line 2723:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" 						CROSS_COMPILE=${CHOST}- 		LDFLAGS=\"$(get_abi_LDFLAGS)\" 						${BUILD_FIXES} 						${BUILD_PARAMS} 						${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
 * 
 * If you need support, post the output of 'emerge --info =sys-fs/vhba-1.2.1',
 * the complete build log and the output of 'emerge -pqv =sys-fs/vhba-1.2.1'.
 * The complete build log is located at '/var/tmp/portage/sys-fs/vhba-1.2.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/vhba-1.2.1/temp/environment'.
 * S: '/var/tmp/portage/sys-fs/vhba-1.2.1/work/vhba-module-1.2.1'
gateway dem # /etc/init.d/vhba start
bash: /etc/init.d/vhba: No such file or directory
gateway dem # equery files vhba
[ Searching for packages matching vhba... ]
* Contents of sys-fs/vhba-1.2.1:
/etc
/etc/udev
/etc/udev/rules.d
/etc/udev/rules.d/70-vhba.rules
/lib
/lib/modules
/lib/modules/2.6.35-gentoo-r8
/lib/modules/2.6.35-gentoo-r8/block
/lib/modules/2.6.35-gentoo-r8/block/vhba.ko

для 36-го ядра нужно

для 36-го ядра нужно использовать версию vhba посвежее ;)

Theli написал(а): для 36-го

Theli написал(а):
для 36-го ядра нужно использовать версию vhba посвежее ;)

Да, да, абсолютно верно, я так и сделал.

Всё заработало после того как

Всё заработало после того как я добавил vhba в package.keywords , в итоге, установилась более новая версия, которая скомпилировалсь. Потом я сделал modprobe vhba и запустил демон cdemud. Проверил cdemu, монтирует, как и положено, благодарю Theli за оказанную помощь!

Настройки просмотра комментариев

Выберите нужный метод показа комментариев и нажмите "Сохранить установки".