RE: [Cooker] Beta2 ISOs: followup
Actually, that's what I'm doing. I may have misunderstood what you were saying in your earlier message. I thought that you were saying that ever creating a beta ISO was silly and unnecessary. I agree that it pointless to download both the tree and the ISO. The only time I've ever wanted to d/l an ISO instead of mirroring is when mirroring is not an option (such as when I'm at work on a T1 and all the machines are running Windows NT). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ron Stodden Sent: Sunday, May 21, 2000 10:22 AM To: [EMAIL PROTECTED] Subject: Re: [Cooker] Beta2 ISOs: followup James Tucker wrote: > > Actually, I can think of one reason why being able to make an ISO image is > nice. I have a high speed connection and mirror Cooker (which I install > from the hard drive). I then create CDs for my friends (who only have 56k > modems) about once a week so that they can also play with the new beta. But, since you have the disk space, it would be very easy for you to run mkisofs via the Mandrake-published script to create the iso images from the tree and then you would not have to download both the tree and the iso. -- Regards, Ron. [AU, Mandrake Linux].
RE: [Cooker] Beta2 ISOs: followup
Actually, I can think of one reason why being able to make an ISO image is nice. I have a high speed connection and mirror Cooker (which I install from the hard drive). I then create CDs for my friends (who only have 56k modems) about once a week so that they can also play with the new beta. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ron Stodden Sent: Sunday, May 21, 2000 8:17 AM To: [EMAIL PROTECTED] Subject: Re: [Cooker] Beta Do you not realise how silly this approach is for beta testers? If you have distribution room for the 2 iso image files (which are of little direct use unless one burns two CDs, since you do NOT supply an iso.img floppy from which we can directly install or upgrade), then you have room for a distribution tree to replace it, from which those unenlightened souls who need CDs can mkisofs an iso image, and we enlightened others can use the hd.img floppy to install or upgrade from it. The only iso image file you should need to make is for the final 7.1 gold release to the CD pressing shop. We quite simply have NO need of it, and do not understand what you are on about. Until that time, as I have said before, cooker is to contain the 7.1 frozen hydrogen beta you want us to test - in accordance with Gael Duval's promise in his beta announcement. It is that simple! If you wish to work on the i486, sparc, and alpha ports without disturbing the beta, keep them in-house until they have passed their alpha tests. The beta test of them will then require additional separately-named distribution space separate from Cooker. If you phase their release, then they are different products, which implies separation. -- Regards, Ron. [AU, Mandrake Linux].
[Cooker] httpd/error_log and ssl_engine_log
I recently mirrored the cooker install (about two days ago or so) and noticed that my httpd error_log and ssl_engine_log have grown to about 28 megs each. They are filled with the following errors: [Thu May 18 18:35:22 2000] [error] mod_ssl: Child could not open SSLMutex lockfile /etc/httpd/logs/ssl_mutex.688 (System error follows) [Thu May 18 18:35:22 2000] [error] System: Permission denied (errno: 13) [Thu May 18 18:35:22 2000] [error] mod_ssl: Child could not open SSLMutex lockfile /etc/httpd/logs/ssl_mutex.688 (System error follows) [Thu May 18 18:35:22 2000] [error] System: Permission denied (errno: 13) Looks like permissions aren't set correctly in the latest install.
RE: [Cooker] first try
>> At the networking stage, the first dialog says "Networking is already >> configured" and gives me the options to change it or not. Why would it already >> be configured if I'm doing a fresh install? >it usually happens for network installs. Strange that it may happen in hd >install! >>I was able to set up both my NICs >> and configure them easily after selecting "reconfigure". Very nice. >> Couldn't get crypto going. Any site I selected gave me a warning on F3. >> "Warning: Net::FTP: Bad peer address ...propogated at >> /usr/bin/perl-install/ftp.pm line 41". I just wanted to add that I did a complete mirror yesterday and ran into the exact same problems doing a similar install from the hd. When I rebooted my network card was not configured correctly despite the fact that the install detected the Netgear card and seemed to configure it for me. I also had problems configuring X (neither 3.3.6 or 4.0 worked correctly). I was able to manually configuring them using XFdrake after I finished the install and rebooted. (I'm using a Voodoo 3 card).
