Re: [Cooker] alpha architecture..
I am the systems administrator for a University and have an Alpha machine which I can use to test your builds. I will setup an FTP for the binaries and host them for others on my server. Give me till tommorrow to get the site online. You can contact me at work with the following e-mail address: [EMAIL PROTECTED] - Original Message - From: Stefan van der Eijk [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 25, 1999 3:54 PM Subject: [Cooker] alpha architecture.. Hi, I've continued my quest compiling packages on my alpha... ;-) Now... where can I upload them to share them with you all?? I think it's pretty anti-social if I bomb all of it up to the /incoming directory on ftp.linux-mandrake.com. (I don't have the bandwidth or space to host them myself, I'm sorry). _IS_ there anybody who will use / test the packages?? Greetings, Stefan
Re: [Cooker] Problems with advanced extranet server
I am not an expert with Midgard, but to the best of my knowledge, the advantage behind Midgard is the ability to create dynamic pages with Apache. A disadvantage with Midgard when using PHP3 is that it loads the module dynamically when requested. Apache does not load php3 and keep it resident. Instead, when a user requests a PHP3 document from Apache, Midgard will load the module dynamically for the request and release the module afterwards. The disadvantage from their web page reads: As noted in the overview, you will need to compile Apache with mod_so within. I'm not sure but if you have already compiled Apache with a static module version of PHP (mod_php3) AND mod_so then you will need to recompile Apache again, leaving out the static PHP module. A static PHP module would have been configured into Apache if --activate-module=src/modules/php3/libphp3.a were included when running ./configure. Sidetracking a little, this is a real pity as a static module PHP would run a lot faster than a dynamic module. Midgard-1.1.1 is said to be compatible with Apache 1.3.3 onwards. Although it is recommended that you use at least version 1.3.4 as it supports mod_dav which will be in Midgard soon. In the end, I simply upgraded to Apache 1.3.6 for the Midgard installation. That being the case, below are the steps I took to compile Apache I guess the dynamic module takes a performance hit - Original Message - From: Eric Mings [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 11, 1999 11:14 PM Subject: Re: [Cooker] Problems with advanced extranet server Install the Midgard packages. There are some dependencies. I don't exactly remember, but you need to install about 4 or 5 RPMS from the CD related to Midgard. This should work. Thanks much for the info! However, I give up, what is midgard? Snooping around in the Apache directories it appears to be some sort of replacement for the the regular php module. What is it and why would I want it to replace a standard php module? Regards, Eric Mings Ph.D.
Re: [Cooker] Advanced Extranet Server
From the Midgard web page: How difficult would it be to replace MySQL with Oracle or some other RDBMS? With the current releases of Midgard, impossible. There is some MySQL-specific stuff in the Midgard code. However, there has been some talk of supporting other databases. Why this hasn't been done already is because there just hasn't been enough need for it. Midgard 2.0 (due out in Q4 1999) should work with any ODBC-enabled database. - Original Message - From: Vincent Danen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, October 12, 1999 12:43 AM Subject: [Cooker] Advanced Extranet Server Ok, I'm having some pretty serious problems with the AES that comes with Mandrake 6.1, and I hope someone here can help me out. I posted to the expert list and no one replied, so I'm gonna try here... =( this is really important and it's really starting to annoy me. I want to use the PHP modules (mod_php3, midgard-php3, I don't really care at this point) to connect to my PostgreSQL server. Midgard can't do it, it keeps coming back with unknown function pg_connect() which is no good. Looks like mod_php3 has the same problem, so I downloaded the source RPM for mod_php3 and tried changing the .spec file. Now, in the .spec file it's configured --with-mysql but not --with-pgsql, so I added it and now I get this problem when I try to build the RPM: In file included from internal_functions.c:63: functions/php3_pgsql.h:46: libpq-fe.h: No such file or directory functions/php3_pgsql.h:47: libpq/libpq-fs.h: No such file or directory In file included from internal_functions.c:63: functions/php3_pgsql.h:89: parse error before `*' functions/php3_pgsql.h:96: parse error before `PGconn' functions/php3_pgsql.h:96: warning: no semicolon at end of struct or union functions/php3_pgsql.h:98: parse error before `}' functions/php3_pgsql.h:98: warning: data definition has no type or storage class functions/php3_pgsql.h:101: parse error before `PGconn' functions/php3_pgsql.h:101: warning: no semicolon at end of struct or union functions/php3_pgsql.h:102: warning: data definition has no type or storage class functions/php3_pgsql.h:103: parse error before `}' functions/php3_pgsql.h:103: warning: data definition has no type or storage class Now, I'm no programmer or I might hop in those header files and fix whatever the problem is, but I can't do that... =( Sounds like something is wrong with the pgsql code? I've got some small existing databases with pgsql and I'd like to continue using them. It wouldn't be *that* difficult to use mysql, but I find pgsql a little easier to use than mysql, and I'd like to continue using it. Does anyone have any suggestions or help for me? This has been driving me crazy for about a week... I had Midgard installed up until this morning and all the other PHP stuff works great... it just looks like Midgard requires mysql whereas mod_php3 doesn't require anything, from what I can see.. and it can use either pgsql or mysql. Now, if Midgard can use pgsql also, that's a bigger bonus, but I think the same problem exists for Midgard as does for mod_php3 since they seem to be using the same pgsql files (or at least the module names are similar and I would guess interchangeable?). Thank you *very* much in advance for help with this. Vincent Danen ([EMAIL PROTECTED]) . ICQ: 16978834 http://shx.tzo.net . telnet://shx.tzo.net . http://tux.tzo.net BBBS/LiI . Internet Rex for Linux Beta . Stronghold Enterprises/X BBS Check out the new Linux Information site at http://tux.tzo.net
Re: [Cooker] Is the Tekram dc-390u2w Supported?
I am currently using this card with an IBM DRVS 10,000 RPM Ultra2 LVD SCSI Drive - works great, but the current drivers do not support the 80 MB / sec only 40 MB /sec - still good enough for my purposes. The installation should autodetect the controller and recognizes the NCR / Symbios Logic chipset. Hope this helps!! - Original Message - From: Jake Johnson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 30, 1999 5:18 PM Subject: [Cooker] Is the Tekram dc-390u2w Supported? I was wondering if the Mandrake 6.1 or cooker is supporting the Tekram dc-390u2w card. Really I was hoping that someone was using it for reasurance reasons. It has the symbios chipset so I think it will work but will autoprobe find it? Please add some insight to this if you know of anything about these cards. Thanks in advance, Jake Johnson = __ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com
