David Krider (david@davidkrider.com) wrote:

Paul Benjamin wrote:

...

A source based distribution is OK if you have three things:

1. A fast connection to the internet. 2. A fast processor/hard drive 3. Times when there is low utilization of your CPU/Hard drive and can compile the source you download.

I second this. I tried it out. I have a dual Athlon 1800+ with 1 GB of RAM, and an all-SCSI I/O system. It took me about 3 full days to get a system going with KDE and Gnome. Then I wanted to build Mozilla with Xft2 support, and I was going to have to rebuild everything down to and including X. Pass. I went back to Red Hat, got disappointed with their recent product realignment, and bought SuSE 8.2 So far, so good. I'm just saying that -- to me -- it's a rare person who is going to be happier running a source-based distro.

I don't have fast connection to the Internet (ISDN), neither fast processor/hard drive. Since I'm thinking about SOHO, the item 3) is satisfied :-) But, at the present moment, I still have to update my system via apt-get and I did it also for bigger packages like KDE or XFree. Main point is, however, that since the packages for older releases are in general not updated (if there are no security issues), one has to upgrade/buy new releases or compile required packages from sources, and then one is facing one of the limits of RPM - cannot recognize packages compiled from the source (this fact was confirmed to me by one SuSE guy I had exchange with). Morever, if I want/need two versions of the package, I'm ending up playing with tools like epkg, which again means fiddling with the sources, or learn the art of writing RPM spec file to keep the system in the order, and all these just to do the work one is expected to be done by package manager. Portage is capable to handle such things since all the packages are compiled from the source. Having fast connection to the Internet, as well as fast cpu/hard is nice, but, imho, not necessary to run Gentoo. One can buy for 5€ LiveCD which contains install pacakge and some bigger ones like KDE, GNOME, and for the price of two SuSE updates (in Croatia), here I can get 30GB Firewire HD which I can bring to the friend with permanent Internet connection, plug in, dowload the whole Portage tree and bring back on my computer, plug in and sync my tree from the local HD. Sincerely, Gour -- Gour gour@mail.inet.hr Registered Linux User #278493

Radu Voicu wrote:

Hi there!

Did anyone tried to "convince" the Internet Explorer to "Automatically detect proxy settings"?

P.S. On SuSE 8.1, DHCP, SQUID - and I want the windows machines to detect proxy settings...

Regards, Radu

i've never had a browser automatically detect proxy settings yet! for any browser we've had to setup to go through proxy, you have to set it manually

On Thursday 17 April 2003 10:08, Radu Voicu wrote:

I know the "manual" version of setting a proxy server, but I've heard about a small piece of LINUX program who tells to MSIE the proxy settings, almost the same way Win2000 server's DHCP does:

"Network servers using Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) can automatically detect and configure a browser's settings when the user first starts the browser on a network."

So any hints? Radu

----- Original Message ----- From: "Oskar Teran" To: "Radu Voicu" Cc: "SLE" Sent: Thursday, April 17, 2003 6:02 PM Subject: Re: [SLE] IEAK on SuSE

...

Radu Voicu wrote:

...

Hi there!

Did anyone tried to "convince" the Internet Explorer to "Automatically detect proxy settings"?

P.S. On SuSE 8.1, DHCP, SQUID - and I want the windows machines to detect proxy settings...

Regards, Radu

i've never had a browser automatically detect proxy settings yet! for any browser we've had to setup to go through proxy, you have to set it manually

As far as "detection" i don't think this is possible. It is possible to "declare" these configurations during network logon. However, at work we utilize a proxy configuration file --- proxy.pac. This declares all the needed configurations for various services that the client may need to utilize. Problem is that it gets downloaded every time a new session is started with the proxy. We just ask the users to leave a browser open in the toolbar, which reduces their DL time...as well as bandwidth usage. I don't have a copy of it on-hand. But i am pretty sure that it is simply: Service = Server i.e. HTTP = http://www.domain.com HTTPS = http://www.domainproxy2.com FTP = http://www.domainproxy.com TELNET = HTH. -- Thomas Jones Linux-Howtos Administrator

Paul Benjamin (pben_suse@cox.net) wrote:

Every markets has it niches. SuSE has been going after the coporate niche for a while now and the suits are not going to like the idea of compiling everything locally, time is money!

I can second on that, but at least one can try. At least, Linux is about the choices :-) Sincerely, Gour -- Gour gour@mail.inet.hr Registered Linux User #278493