On Thu, 3 Aug 2000, you wrote:
One of our developers hacked autorpm to work with SuSE Linux as well. You can get the RPM from here (within the nex few hours, mirroring to the outside may take a while): http://www.suse.de/~grimmer/export/autorpm-1.9.8.4-0.noarch.rpm http://www.suse.de/~grimmer/export/autorpm-1.9.8.4-0.src.rpm This package already includes a suse-update configuration. Enjoy!
I checked the dependencies, and discovered that I don't have perl_net installed - nor can I find that package on the distribution CDs or on any SuSE site. Besides, I have to admit that enabling this feature on a production server seems somewhat scaring to me (especially since site-hijacking and other DNS troubles are not so uncommon in these days...). I'd probably try it for a while on a user's workstation. Greetings, Simon. ==================== Dr. Simone Grabstein listuser@egontek.net ====================
Simon, First off, most important, the beta-package that you have downloaded, adds the following lines to your /etc/rc.config: # # allow execution of autorpm via cron (cron.daily) # START_AUTORPM_CRON="yes" Soon after installation, change the "yes" to "no". This must have been an accident to enable this in a beta package... It is a comforting coincidence that the dependencies don't match. :-|
I checked the dependencies, and discovered that I don't have perl_net installed - nor can I find that package on the distribution CDs or on any SuSE site.
This is correct. perl_net is a split-off from the original perl package. Starting with SuSE-7.0, it will be seperate. In this case (6.4 or such), you can safely ignore it using the "--nodeps" rpm option. Use "--force", too, if it won't stop bitching around. Deletion of the package using "-e" should be safe (but the rc.config thing won't be erased!).
Besides, I have to admit that enabling this feature on a production server seems somewhat scaring to me (especially since site-hijacking and other DNS troubles are not so uncommon in these days...).
The security issues will hopefully be resolved with package signing. What also bothers me is that there is still no conclusive solution wrt the question if the package will really still work after the update (packages such as apache, wuftpd, ...).
I'd probably try it for a while on a user's workstation.
As do we! :-) Thanks for your efforts! Roman Drahtmüller. -- - - | Roman Drahtmüller <draht@suse.de> "Caution: Cape does not | SuSE GmbH - Security enable user to fly." | Nürnberg, Germany (Batman Costume warning label) | - -
Hi, On Fri, 4 Aug 2000, Simon wrote:
http://www.suse.de/~grimmer/export/autorpm-1.9.8.4-0.noarch.rpm http://www.suse.de/~grimmer/export/autorpm-1.9.8.4-0.src.rpm
I checked the dependencies, and discovered that I don't have perl_net installed - nor can I find that package on the distribution CDs or on any SuSE site.
You must be running SuSE Linux 6.3 or older, than. You can find a package for SuSE Linux 6.4 here: ftp://ftp.suse.com/pub/suse/i386/6.4/suse/d1/perl_net.rpm It should work on older SuSE Linux Versions, too. Otherwise you could install the Perl modules libnet and Net-SNMP manually from CPAN.
Besides, I have to admit that enabling this feature on a production server seems somewhat scaring to me (especially since site-hijacking and other DNS troubles are not so uncommon in these days...). I'd probably try it for a while on a user's workstation.
Yes, I totally agree. Automated updating should be taken with a grain of Salt :) Bye, LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany Winter in Arizona falls on a Tuesday this year.
participants (3)
-
Lenz Grimmer
-
Roman Drahtmueller
-
Simon