Help install PERL module

[DrWebber]

Ive recentlly has a filemanager isntalled, but there are some PERL modules missing..

Ive troubled support 3 or 4 times now, and feel I should have a go myself, but am a n00b and not familiar with linux.. Ive had a go via the terminal, but keep getting restricted messages... I cant even got to the dir Ive uploaded the file to to unzip, and make/install it...!!

The module I am trying to install is the gzip module from the cpan site... Ca n someone point me in the right direction...??

Ive got the VPS as firstly it was a bargain, and I like to jump in at the deep end...!!

Any help would be most appreciated, so I can give the guys in support a well earned break!!!

Theres a lot to get my head around.. so a nudge in the right direction would be great.. If Im shown once, I will learn for next time!!!!

Ive been working with CentOS (my first linux experience) for a few months, but am used to the gui environment for doing most things.. the shell is a whole new ball game, and well, its not dos!!!! Im a bit in the datk ages outside of dos..!!!

Pity I cant remote desktop to the CentOS gui!!!

Thanks

[Spathiphyllum]

Assuming you've not locked yourself out of the root account, here are some tips:

To access command line interface (CLI), use the program putty and not telnet. I don't know which you used, but telnet is generally disabled... or should be. Putty is a "terminal" client to communicate with a remote server securely. It's bigger cousin is WinSCP which doesn't allow for interactive commands. It'll give you a secure shell in which to operate.

Once logged in use CPAN to do your installs. Since you've been using CPAN's install module, just continue on since it has already been configured:

perl -MCPAN -e shell

At this point your cursor will change into the CPAN utility shell where you can add modules. Type the letter "h" (exclude quotes) to see a list of options. Of those listed, the quick and dirty command is:

install Sample::module

Obviously, use a real module name and not "Sample::module." This will cause the make/make test/make install routine run automatically. During the automated processing, if it pauses to ask about installing other modules first (out of dependency), then type "y" and "Enter/Return." The screen should scroll and everything should proceed fine unless it doesn't .

To see a list of "outdated" modules you have installed, type "r". To quit, type "q". After quitting you'll be out of the CPAN shell and back into the putty SSH shell. Type "logout" and hit "Enter/Return."

That should get you started.

[Gwaihir]

Ive had a go via the terminal, but keep getting restricted messages... I cant even got to the dir Ive uploaded the file to to unzip, and make/install it...!!

It sounds like you need to switch users, from whatever you logged in with to whatever you need to access that part. Try "su -l root". It will ask you for the root password. Once you've given it, you won't find any access barriers anymore. You may not always want to go around as root though. Perhaps you should be some other user (the installation instructions will hopefully tell you). That's easily done from root, just "su whom-ever-you-want-to-be" (you won't be asked for a password).

[Vin DSL]

Putty is a "terminal" client to communicate with a remote server securely. It's bigger cousin is WinSCP which doesn't allow for interactive commands. It'll give you a secure shell in which to operate...

Huh?

What are you talking about?

WinSCP has a PuTTY window available - it's built on top of PuTTY - I use it all the time!

Are you talking about the 'console', where you cannot interact?

If so, that's true, and you can use the 'console' 99% of the time because no user input is needed, however WinSCP is built on PuTTY, and to suggest user input is not an option is B.S.

[Spathiphyllum]

Are you talking about the 'console', where you cannot interact?

Yes, which is why I said "interactive commands". And one cannot interact with WinSCP's terminal. It's a one time shot when one runs a command via its CLI. When using CPAN's module, that is not desirable since you'll be sent into a cpan subshell and is quite often death for an install if user response is required either to set a runtime parameter or to OK a step. Further, unless one knows exactly which arguments to pass during the install routine and that routine can finish completely without response, then WinSCP works poorly. The thing is, you won't know it's working poorly... only that an install ceased in its tracks.

If so, that's true, and you can use the 'console' 99% of the time because no user input is needed, however WinSCP is built on PuTTY, and to suggest user input is not an option is B.S.

I didn't suggest that at all and I said "bigger cousin" WRT to WinSCP's relationship to putty. The fact that it's a pretty face to an underlying SSH terminal application wasn't minutiae that was germane to my point that DW wants (needs) an interactive tty to conduct his business in this particular scenario. DW declared he was a noob on linux. With that as an audience (and no disrespect to DW), CPAN is rather painless but requires user response during some steps and at different intervals (or not) depending on the package and the dependencies. Unless the CPAN Config.pm module is configured in advance to one's exact needs, and those needs don't change, ever, you'll find yourself with aborted installs and sometimes stare at a blank tty that does nothing... until your network connection disconnects and your terminal session freezes... or h*ll, whichever is first. When working with CPAN's install routine, which is generally more user friendly than hand-rolling, you don't want WinSCP... you want putty - the original.

Stick to PHP and 565.72 Gazillion Hz CPU's.

[Vin DSL]

When working with CPAN's install routine, which is generally more user friendly than hand-rolling, you don't want WinSCP... you want putty - the original.

Stick to PHP and 565.72 Gazillion Hz CPU's.

What am I missing?

WinSCP is built on top of PuTTY, and you can execute a PuTTY terminal directly from WinSCP (with full interaction)...

WinSCP-PuTTY.png

Why "you don't want WinSCP"?

[Spathiphyllum]

It's still just putty. However it's wrapped a full putty initiated shell is required. Yes, you can open WinSCP only to then get it to open putty as a virtual "third-party application" via the WinSCP GUI (as you noted), but why? For this particular case, he just needs a putty tty and WinSCP is superfluous add-on, the default of which is limited accessibility.

[Vin DSL]

Yes, you can open WinSCP only to then get it to open putty as a virtual "third-party application" via the WinSCP GUI (as you noted), but why?

Well, as you said, 'we' are dealing with a n00b!

It's a LOT easier to go to a folder using WinSCP, then execute a PuTTY shell in that folder, rather than trying to navigate using CLI, yes?

I just use it 'cause I'm lazy...

[Spathiphyllum]

It's a LOT easier to go to a folder using WinSCP, then execute a PuTTY shell in that folder, rather than trying to navigate using CLI, yes?

I just use it 'cause I'm lazy...

I'm lazy too, generally. This is a somewhat exceptional case. First, if the user is unfamiliar with WinSCP, it saves some time to not have to worry about the WinSCP interface. It may seem trivial and in the long run, it's useful to learn yet another client interface, but avoiding it cuts to the chase. The most direct way is just the secure client that provides a secure tty. Second, browsing to a directory is unnecessary for yum (OS package installer) and cpan (Perl/CPAN package installer). Just log in and run wherever you are in the tree and the applications know where to get the source and where to place the install. Easy peasy as long as you can respond to prompting.

[mattsiegman]

for this, just using good ol putty works fine

[Vin DSL]

I'm lazy too, generally...

Just log in and run wherever you are in the tree and the applications know where to get the source and where to place the install. Easy peasy as long as you can respond to prompting.

for this, just using good ol putty works fine

Okay, we're all on the same page...

The thing is, WinSCP is basically a PuTTY interface with multiple add-ons (and growing).

AND, if you install the whole package (not just the standalone) the most recent version of PuTTY/Pageant is available in it's own folder.

So, you're killing two birds by installing WinSCP. You can use the WinSCP interface or just simply use PuTTY - your choice...

[Vin DSL]

...if the user is unfamiliar with WinSCP, it saves some time to not have to worry about the WinSCP interface. It may seem trivial and in the long run, it's useful to learn yet another client interface, but avoiding it cuts to the chase...

Speaking of which...

I digress.

How do you like the look of WinSCP in Windows Vista HP, with Aero running (the graphic above)?

Just curious... It's a good example of shading and 3D in Vista!

[mattsiegman]

WinSCP looks the same in Vista...

[Spathiphyllum]

How do you like the look of WinSCP in Windows Vista HP, with Aero running (the graphic above)?

Just curious... It's a good example of shading and 3D in Vista!

It looks fine. Some of the finer points I'm probably missing since to appreciate the full effect, I'd need to see the full page. I don't work with Vista (of any style) so there's lots of eye candy I'm certainly missing.

Did you do something unique to achieve the effect, or is this another theme Microsoft is developing?

I just don't get all caught up in the frills. Clean and fast (but not quite ASCII text ) is my preference. In fact I usually dump the "new and improved" Win32 interfaces to keep 'em "old and lousy" looking. I just don't want fade in/outs, kaleidoscopes, scrolling, Clippy, circus tricks, and sound effects. In fact I kinda figured you for a stark presence given your gray-scaled web.

[Daniel_DBS]

Did you do something unique to achieve the effect, or is this another theme Microsoft is developing?

that is the standard interface for the new windows vista... i have vista now on two of my computers at home and love it... looks great and runs great too