in reply to un-installing perl core modules inside a freebsd jail

Pull out the contents of your @INC and manually move the .pm for each of the modules that you do not want used on that system to a different location.

If your the freeBSD virtual system does not boot then you can use the main system to restore whatever is needed.

Replies are listed 'Best First'.
Re^2: un-installing perl core modules inside a freebsd jail
by gideondsouza (Pilgrim) on Feb 20, 2013 at 10:15 UTC
    So you're saying a plain directory removal will work without breaking anything else. I mean perl itself won't stop running or anything, just that module will vanish?
[reply]
      I mean perl itself won't stop running or anything, just that module will vanish?

      Yes. Perl code which tries to load a vanished module will fail with the usual 

      Can't locate Vanished/Module.pm in @INC (@INC contains: ... )
BEGIN failed--compilation aborted.

      [download]

      which means that perl is working fine :)

[reply]
[d/l]

      Well there are a bunch of modules that can access the net ( if thats what you are trying to block ) and this thread has some ways to find all modules installed.

      Regarding Perl breaking - I cannot think of any core module that allows for access to the internet ( and so removal of that will break the system ); Since I am not a 100% sure, you should, like I said earlier, keep them in a different location just so you can put them back if your OS were to break - you can do that from the main system.

[reply]

        I think the low level networking functions (socket, bind, listen, connect) are built in to Perl. If that is the case, then you can't prevent internet access by removing modules. I'm not a freebsd person, but perhaps a more complete approach would be to address this via OS and network.

[reply]

In Section Seekers of Perl Wisdom