in reply to Re^4: /usr/bin/instmodsh: Permission denied.
in thread /usr/bin/instmodsh: Permission denied.

Lol, always check the obvious first. But there is no way Bundle::CPAN changed the permissions on instmodsh/perldoc... thats unpossable
  • Comment on Re^5: /usr/bin/instmodsh: Permission denied.

Replies are listed 'Best First'.
Re^6: /usr/bin/instmodsh: Permission denied.
by MidLifeXis (Monsignor) on May 24, 2010 at 13:53 UTC
    s/unpossible/unlikely/

    Having seen way to many "unpossible" things happen, especially around users, I tend to avoid assigning the impossible attribute.

    --MidLifeXis

[reply]
[d/l]
      cd /usr/bin
ln -fs foo myproggie

...

cd /tmpdirMISSPELL/
rm *

      [download]

      Yes, I have seen code like this. CPAN executes code handed to it by another module's author (with your permission, but still). Impossible is not a word I apply to systems. Period.

      Update: Whoops, replied to myself, not the AM above.

      --MidLifeXis

[reply]
[d/l]
      Having seen way to many "unpossible" things happen, especially around users, I tend to avoid assigning the impossible attribute.

      instmodsh is core program , CPAN won't touch it, so yes, impossible for CPAN to break the permissions, its a user problem.

[reply]
        cd /usr/bin
ln -fs foo myproggie

...

cd /tmpdirMISSPELL/
chmod $perms *

        [download]

        Yes, I have seen code like this. CPAN executes code handed to it by another module's author (with your permission, but still). Impossible is not a word I apply to systems. Period.

        --MidLifeXis

[reply]
[d/l]

In Section Seekers of Perl Wisdom