Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Jason Brown on November 30, 1999, 04:39:30 PM
-
I am new to e-smith and interested in disabling several of the services. I am also interested in enabling ftp to external users. I would like to kill squid and several unneeded things such as this. Also, I noticed there are not c compilers such as gcc on e-smith. Is there an RPM for this or should I just get a standard redhat RPM? Thanks alot
-
Jason Brown wrote:
> I am new to e-smith and interested in disabling several of the
> services. I am also interested in enabling ftp to external
> users. I would like to kill squid and several unneeded things
> such as this.
I would only kill squid if you are not going to access the web...
If you plan to customise the system I would suggest that you read the design documentation on the e-smith.org web site and work out how the system fits together. You will need to change some templates, remove symlinks, and edit perl scripts to do the changes you mention.
> Also, I noticed there are not c compilers such as
> gcc on e-smith. Is there an RPM for this or should I just get > a standard redhat RPM? Thanks alot
I would recommend that you do C language development on a standard RedHat system rather than the e-smith server. You will need to install quite a few RPMs to do any real development, and you will also decrease the security of the system.
Charlie
-
>I would only kill squid if you are not going to access the web...
Why do you recommend this? If I am correct, squid is simply a caching proxy? I generally dislike the cached proxy because of gettting stale content on certain sites unless i reload. Should the web not work fine just via IPCHAINS? My setup is a p233 64 megs of ram and a 4 gig hard drive. This is simply for use with about 6 workstations.
>If you plan to customise the system I would suggest that you read the design >documentation on the e-smith.org web site and work out how the system fits >together. You will need to change some templates, remove symlinks, and edit perl >scripts to do the changes you mention.
That seems like a bit much just to allow several FTP accounts to access my system
>I would recommend that you do C language development on a standard RedHat >system rather than the e-smith server. You will need to install quite a few RPMs to >do any real development, and you will also decrease the security of the system.
I would assume this means that I would be comprimising the security of the system internally only as external users do not have telnet or any other access(unless i add ftp) and I am in no way concerned internally. I do not plan to do development but to compile some extra packages and have no other Linux machines here on premises.
Thanks
-
Jason Brown wrote:
> >I would only kill squid if you are not going to access the
> web...
>
> Why do you recommend this?
To give you better web access speed.
> I generally dislike the cached proxy because of
> gettting stale content on certain sites unless i reload.
Those sites are probably putting out content without the right
headers. But anyway, if you don't want squid you can eliminate it..
> Should the web not work fine just via IPCHAINS?
Yes.
> > You will need to change some templates, remove symlinks,
> > and edit perl scripts to do the changes you mention.
>
> That seems like a bit much just to allow several FTP accounts
> to access my system
I was talking about all of the changes you wanted to do.
> >I would recommend that you do C language development on a
> >standard RedHat system rather than the e-smith server.
> ... you will also decrease the security of the system.
> I would assume this means that I would be comprimising the
> security of the system internally only as external users do
> not have telnet or any other access (unless i add ftp) and
> I am in no way concerned internally. I do not plan to do
> development but to compile some extra packages and have no
> other Linux machines here on premises.
The decrease in security was "in theory" - if there is a compiler on your system there are a few more ways that security can be attacked after some access to the system is gained by exploiting a flow in one of the daemons.
If you have no other linux systems available then you can compile on the e-smith server, but you will need to add quite a number of packages to do so. I would still recommend that you find another system, and make rpms on it.
Charlie