Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

ActiveState Perl 5.8 805 issues

by softworkz (Monk)
on Feb 27, 2003 at 14:37 UTC ( #239107=perlquestion: print w/replies, xml ) Need Help??
softworkz has asked for the wisdom of the Perl Monks concerning the following question:

Hello monks... I've been testing the new perl release and I don't like it! I was wondering if anyone else had some concerns with it? The biggest downfall I think is how the ppm has changed.... being on a windoze system ppm 3.0 is a whole lot easier than the new 3.0.1 ppm. Some issues that changed were how modules are installed and how repository's are set. why do they change something that works??? I thought changes were made to flaws or what not, but why change the syntax of things?

Is there a way to suggest to go back to the way it was??

Title edit by tye

Replies are listed 'Best First'.
Re: ActiveState Perl 5.8 805 issues
by ibanix (Hermit) on Feb 28, 2003 at 01:46 UTC
    The biggest downfall I think is how the ppm has changed

    This is the biggest downfall? Then kudos to ActiveState for doing a kickass job! When you consider the workload it takes to setup and maintain a distribution of Perl on a non-Unix platform, AND consider that ActiveState gives this away for no cost, I think many thanks are in order for the fine folks at ActiveState.

    Some issues that changed were how modules are installed and how repository's are set.

    I apoligize in advance, as I usually dislike saying this; however: RTFM?

    Is there a way to suggest to go back to the way it was??

    Sure, you can send email to ActiveState on their contact page, or perhaps you want to bring up the topic on the ASPN Mailing Lists? Or maybe just become a member of the ActiveState Programmer Network?

    Of course, you've already read the release notes and change log for ActivePerl 5.8, right?

    Cheers,
    ibanix

    $ echo '$0 & $0 &' > foo; chmod a+x foo; foo;
Re: ActiveState Perl 5.8 805 issues
by Marza (Vicar) on Feb 27, 2003 at 18:39 UTC

    It is more of a retraining of what you know. PPM3 did annoy me but after I got it straightened out, I find it is not that bad.

    Now if all the mods were blessed for it! ;-) But that is what a compiler is for!

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: perlquestion [id://239107]
Approved by LostS
help
Chatterbox?
[davido]: so last -f /var/run/utmp on ubuntu provides similar (though more verbose) info
[oiskuu]: glibc getlogin just does ttyname() and falls back on getutline(); it's not security related at all. (reminds me of sendmail and remote finger services of the naive early spam era)
[Corion]: But yes, "who started this process" is interesting information :)
[tye]: no, I really believe that "login user" was added as a fundamental bit of info about each process in order to enhance the usefulness of auditing
[Corion]: Ah - if that information is saved in a file, then you could theoretically spam that file and confuse getlogin(). So, don't use it for authentication :)
[tye]: that is what getlogin() certainly *used* to do. I don't believe that is what it certainly should do.
[davido]: /var/run/utmp is 664 i think.
[tye]: Note that my "man getlogin" says that it uses stdin when it should use /dev/tty (calling a glibc bug). But that does not appear to be the case when I test it. But maybe Perl's getlogin() is not using glibc's getlogin().
[oiskuu]: well, run a strace and see what the getlogin does for you.... As I said. SELinux probably has those security labels. But not regular linux.
[tye]: for example, read https://unix. stackexchange.com/ questions/146138/ loginuid-should-be -allowed-to-change -or-not-mutable-or -not

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (9)
As of 2017-06-23 19:42 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    How many monitors do you use while coding?















    Results (554 votes). Check out past polls.