Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • perl stuff on solaris is a pain in the butt.
    you have to make sure you have your own compiled perl using the compiler you actually have. even then ld sometimes bites you in the arse.
    the perl installed by default is compiled with the sun compiler. which almost noone actaully has.

    it is just pain. and is why im thankful i sysadmin for java developers :)
  • As a Solaris administrator of about 10 years now, I'm constantly amazed at the number of misconfigured Sun boxes out there. Beyond the initial setup, Solaris is NOT an easy OS to configure and maintain if you don't know what you're doing. This is especially important when creating a usable and flexible user environment on the machine, which you now seem to know all too well.

    Part of the problem is that too many companies don't know the difference between an experienced Solaris administrator and an admini

    • Solaris is not easy to maintain and configure. But Sun will sell more training courses to sysadmins that way...

      -Dom (ex solaris admin)

    • This is my impression as well. It might not be the fault of Solaris itself (although there appears to be a correlation between Solaris and badly maintained machines). It's just that over the time fear has begun creaping up inside me when there's the prospect of having to deal with Solaris.
  • The Solaris-PerlGcc [] module may be of interest to you.
    • That's pretty sweet. So simple, yet so useful.
    • Some time ago I tried to make compilation work with it, but it still failed in a way that I didn't understand. More current releases probably work better.

      In any way, I am not trying to install my module on Solaris. I am just testing it. Therefore going the hard way is the right thing to do, I think. Thus I know what Solaris users might have to expect when dealing with my modules and I can foresee some of their problems and mention them in the README.

      At least I do have some access to Solaris. I wonder abou
      • The problem is that the current version relies on being used with the version of MakeMaker that shipped with Solaris - if you've updated MakeMaker from CPAN it doesn't work, as the MM guts changed sufficiently to break it. I've submitted a patch to MakeMaker to make it possible to do this in a generic way, but unfortunately the MM that shipped in 5.8.3 didn't include the patch, and in fact the version of MM with the patch in it *still* hasn't shipped :-(

        I've included the patch in the perl 5.8.3 I integrat
        • I'm considering including perlgcc in Solaris 10 as well, so people will be able to use gcc out of the box (and gcc comes on the Companion CD that ships with Solaris).

          So far, every Solaris machine I touched did in fact have a gcc (luckily so). It is more tricky to find one with SUN's C compiler. I remember that SourceForge's compile-farm once had it, but right now only the gcc appears to be there. That's quite a pity as my stuff seldom compiled out of the box on compilers other than the gcc. For suncc I re
      • You could try the Compaq^WHP testdrive []

  • When Sun moved from SunOS 4.x to Solaris, they moved from BSD to SysV Unix and folded in some of the old BSD stuff for backward compatibility and familiarity.

    If you've always been on a BSD Unix, you have the advantage of living with a Unix who's sys admin structure has been relatively stable.

    If you've always been on Linux, you have the advantage of a sys admin structure that is user-driven: the community has taken what makes sense and kept it.

    But Solaris (SunOS) has had a long history before Linux and th