On Tue, 9 Mar 2004, Conrad Schilbe wrote: On Tue, 9 Mar 2004, Chris Devers wrote:
> > Did you try typing > > > > o conf urllist push ftp://myurl/ > > > > ? > > ftp://myurl/ is not an actual uri. It's telling you "Put _your_ uri > here". Right, of course :) I guess I should have been clearer, but I hoped that ftp://myurl/ was not likely to be a valid URI, unless you happened to have a friend on the local network with a CPAN mirror running on a host called 'myurl' :-) > ** NOTE: If you don't have a root password or don't know what it is, > please search for "Mac OSX set root password" or similar in google > http://www.google.ca > > % su > Password: Enter you root password here. > > # perl -MCPAN -eshell > cpan> o conf init *NO* *NO* *NO* *NO* *NO* This is precisely what sudo is for. On OSX, root should *never* have a login password. This solves no problem but raises several. Don't do it! As has been noted by myself & others, use this % sudo perl -MCPAN -eshell and then enter your *own* password. It's much safer, generally, to use sudo whenever in the past one would have used root. The sudo system allows for things like restricting which commands a user may execute, and auditing what thing were done with sudo granted priviliges. And that's all nice, but even just using sudo casually to request special access for individual commands -- as I suggest above -- is a big win over raw root access, if only because of the discipline that sudo encourages: rather than granting unrestricted access to root privs for an entire shell session -- as you suggest above -- you have to specifically ask for it for the commands that it's needed. The last thing a new OSX/Unix user needs is unfettered root access. Not that it isn't possible to do something destructive with `sudo`, of course, but at least that way you have the safety of prefixing your commands with a specific request for root priviliges rather than just casually opening up a root shell. Just say no to root! -- Chris Devers
