Sharma

i have big problem, hope can me because i've finished "bullet"... i'm working linux-rpi-3.6.y kernel on raspberrypi let's explain problem: created new syscall called sys_defclose closes files of given process's pid, putted source file in linux-rpi-3.6.y/arch/arm/kernel; then modified following files: linux-rpi-3.6.y/include/linux/syscalls.h linux-rpi-3.6.y/arch/arm/include/asm/unistd.h linux-rpi-3.6.y/arch/arm/kernel/calls.s for correctly install new system call. after cross-compiled following http://elinux.org/rpi_kernel_compilation guide , arrived problem: if transfer via ssh new kernel image "kernel.img" /boot raspberry's directory , reboot unless load module syscall works properly; naturally no modules installed ( lsmod empty )..., if follow steps have load compiled modules, generated make arch=arm cross_compile=${ccprefix} modules export modules_temp=~/modules make arch=arm cross_compile=${ccprefix} install_mod...

i having trouble not find main class error complicated program working on. eliminate possible problems decided try hello world program see if work. working on server i'm pretty sure running red hat enterprise 6. followed these steps provided bart kiers in answer this question : create file called helloworld.java; paste code posted below inside helloworld.java: compile executing command: javac helloworld.java in same folder helloworld.java in; execute code doing: java -cp . helloworld in same folder helloworld.java in. i following error after last step: exception in thread "main" java.lang.noclassdeffounderror: helloworld/ caused by: java.lang.classnotfoundexception: helloworld. @ java.net.urlclassloader$1.run(urlclassloader.java:217) @ java.security.accesscontroller.doprivileged(native method) @ java.net.urlclassloader.findclass(urlclassloader.java:205) @ java.lang.classloader.loadclass(classloader.java:321) @ sun...

given following: import akka.dispatch.{futuretimeoutexception, future} val f1 = future({ thread.sleep(2000); 0}, 500) f1.onexception { case timeout: futuretimeoutexception => -1 } f1.recover { case timeout: futuretimeoutexception => -2 } println(f1.get) why still exception? there way recover timeout such real value returned instead? building off victor said, if want recover particular type of failure future using recover need aware recover returns new future , that's 1 need call get on in order recover functionality. this: val f1 = future({ thread.sleep(2000); 0}, 500) val withrecover = f1.recover { case timeout: futuretimeoutexception => -2 } println(withrecover.get) or chain onto future creation so: val f1 = future({ thread.sleep(2000); 0}, 500).recover { case timeout: futuretimeoutexception => -2 } println(f1.get) edit so looks things work different in akka 1.3 own internal futures compared futures , promises scala 2.10...

i have searched many similar posts, cannot find definitive answer on correct way build , deploy jsf applications, therefore i'm hoping can help... currently using eclipse maven build simple jsf application , deploy onto tomcat 7, 1 dependency in pom.xml of: <dependency> <groupid>javax</groupid> <artifactid>javaee-api</artifactid> <version>6.0</version> </dependency> when deploy onto server get: java.lang.classnotfoundexception: com.sun.faces.config.configurelistener i cant figure out coming from? have no listeners defined in web.xml. if change dependency to: <dependency> <groupid>javax</groupid> <artifactid>javaee-api</artifactid> <version>6.0</version> <scope>provided</provided> </dependency> and attempt run application on server get: java.lang.classnotfoundexception: javax.faces.webapp.facesservlet which can understand bec...

i've been reading code used following import statement: import __ompc__ when tried grep find being imported, found was: me@bedrock1:~/projects/pythonprojects/ompc$ grep -r "__ompc__" ./* ./build/lib.linux-x86_64-2.7/ompclib/m_compile.py:import __ompc__ ./build/lib.linux-x86_64-2.7/ompclib/m_compile.py: codeobject = __ompc__.compile(codestring, dfile or file,'exec') ./build/bdist.linux-x86_64/egg/ompclib/m_compile.py:import __ompc__ ./build/bdist.linux-x86_64/egg/ompclib/m_compile.py: codeobject = __ompc__.compile(codestring, dfile or file,'exec') binary file ./build/bdist.linux-x86_64/egg/ompclib/m_compile.pyc matches ./ompclib/m_compile.py:import __ompc__ ./ompclib/m_compile.py: codeobject = __ompc__.compile(codestring, dfile or file,'exec') since __ompc__ used find method named ' compile ', did recursive grep on that. found __init__.py file in ./ompc/ompc directory had compile method. is impor...

i have program brings in skill ratings assessment people title of "worker” have take along file number assigned. program brings in reporting line each worker part of. select distinct o.vp, o.avp, o.director, o.supervisor, o.worker, bs.file_nbr, s.skill bs.score [new_ees].[dbo].[sbc_best_scores] bs inner join new_ees.dbo.sbc_skills s on bs.skill_nbr=s.skill_nbr inner join gw_ppp.dbo.org_hierarchy oon bs.file_nbr=o.file_nbr; i dataset this: vp avp director supervisor worker file_nbr skill rating gerald kris doris null mack 107812 b2 4 gerald kris doris null mack 107812 d1 3 gerald kris doris null mack 107812 d2 3 gerald kris doris null mack 107812 d3 3 gerald kris doris null mack 107812 e1 4 gerald kris mike null brady 109080 a1 5 gerald kris mike null brady 109080 b1 4 gerald kris mike null brady 109080 b2 3 gerald kris mike null bra...

it looks mahapps.metro progressring control defaults minimum size of 60x60. there property progressring called "islarge", when set "false" seems have no effect on being able make progressring smaller 60x60. obiviously changing height , width properties not affect either. looking on github actual c# code progressring, looks there several properties affect ellipse diameter, etc, these properties private properties, , can not set outside calls. how can make smaller? 20x20 or 30x30? in below code specify islarge=false, , set size 30x30, still defaults 60x60. <window x:class="wpfapplication3.mainwindow" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:controls="clr-namespace:mahapps.metro.controls;assembly=mahapps.metro" title="mainwindow" height="350" width="525"> ...