11-04-2005
Mainly we don't have the computing/processing power, according to the literature. There are plenty of graphs on the net which show the prediction of when computers will have processing power that is similar to other life forms.
To date, we are still at the "earthworm" level, and AI reduces to procedural knowledge in expert systems, not true AI.
7 More Discussions You Might Find Interesting
1. What is on Your Mind?
This may not be the right forum to put up a question like the one I'm about to ask. I am hoping that I would get very fruitful responses.
i) I have been learning UNIX for sometime now, but my question is realistically what do I need to be able to be able to apply for UNIX jobs.
What sort of... (6 Replies)
Discussion started by: B_Jay
6 Replies
2. AIX
Hi ..
I need to assign role based permission to users... How to assign role based permission in aix...
Thanks.. (4 Replies)
Discussion started by: sumathi.k
4 Replies
3. Linux
Hello, I want to know why initrd need swap for work. In the shell of mkinitrd, it look for the swap partation for "swsuspdev", then write a sentence "resume /dev/sdXX" in the file init from initrd.gz, and the /dev/sdXX is the swap partation.
Why initrd need swap when it boot a system? what is... (4 Replies)
Discussion started by: ZR_Lang
4 Replies
4. Shell Programming and Scripting
Hi ,
I am planning for the interview . I am having one question here , I worked on unix and shellscripting for 2 years
Done-
Ø Coding and testing of Server Monitoring ShellScripts
Ø Deployment on UNIX production environment
I have written so many shellscripts for monitoring... (5 Replies)
Discussion started by: aish11
5 Replies
5. Solaris
Hello Guys,
I am studying RBAC. So I create a role called sysadm and gave it the "shutdown" profile.
Now when I switch to that role, and execute the shutdown command
$ shutdown -y -g0 -i5
The system responds with :
shutdown: not found
Can anyone help me with this please?... (1 Reply)
Discussion started by: cjashu
1 Replies
6. UNIX for Advanced & Expert Users
Hi guys
I hope I will not break any rules and guidelines on the forum with this post. I am Admir, working as a recruiter for execIT Recruitment Zurich, Switzerland.
Our client is an urgent need of a linux system administrator/support analyst who has trading floor experience and is eligible... (1 Reply)
Discussion started by: BosAd
1 Replies
7. Solaris
Hi all
I need to run a command that only a role user and root can run, I need to run that command remotely by script but the roles ask for a password.
Ex. from serverA with userA to serverB with userB:
userA can ssh serverB using userB without askink for a password.
ssh userB@serverB... (3 Replies)
Discussion started by: juanramos100
3 Replies
LEARN ABOUT MOJAVE
moosex::role::parameterized::extending
MooseX::Role::Parameterized::Extending(3) User Contributed Perl Documentation MooseX::Role::Parameterized::Extending(3)
NAME
MooseX::Role::Parameterized::Extending - extending MooseX::Role::Parameterized roles
DESCRIPTION
There are heaps of useful modules in the "MooseX" namespace that you can use to make your roles more powerful. However, they do not always
work out of the box with MooseX::Role::Parameterized, but it's fairly straight-forward to achieve the functionality you desire.
MooseX::Role::Parameterized was designed to be as extensible as the rest of Moose, and as such it is possible to apply custom traits to
both the parameterizable role or the ordinary roles they generate. In this example, we will look at applying the fake trait
"MooseX::MagicRole" to a parameterizable role.
First we need to define a new metaclass for our parameterizable role.
package MyApp::Meta::Role::Parameterizable;
use Moose;
extends 'MooseX::Role::Parameterized::Meta::Role::Parameterizable';
with 'MooseX::MagicRole';
This is a class (observe that it uses Moose, not Moose::Role) which extends the class which governs parameterizable roles.
MooseX::Role::Parameterized::Meta::Role::Parameterizable is the metaclass that packages using MooseX::Role::Parameterized receive by
default.
Note that the class we are extending, MooseX::Role::Parameterized::Meta::Role::Parameterizable, is entirely distinct from the similarly-
named class which governs the ordinary roles that parameterized roles generate. An instance of
MooseX::Role::Parameterized::Meta::Role::Parameterized represents a role with its parameters already bound.
Now we can take advantage of our new subclass by specifying that we want to use "MyApp::Meta::Role::Parameterizable" as our metaclass when
importing MooseX::Role::Parameterized:
package MyApp::Role;
use MooseX::Role::Parameterized -metaclass => 'MyApp::Meta::Role::Parameterizable';
role {
...
}
And there you go! "MyApp::Role" now has the "MooseX::MagicRole" trait applied.
perl v5.18.2 2012-08-14 MooseX::Role::Parameterized::Extending(3)