I have been running Ubuntu Linux for a few years now, but I am new to Suse. I am working on setting up some servers for a class at my school. There is one server that sits on the internet and there are nine servers that sit behind this one on a switch. Only the first server has any access to the internet. We are trying to install G++. I don’t want to run into the dependency hell that comes with manually downloading and installing a package and it’s dependencies, but don’t have the option of connecting each system to the internet. My question is is it possible to download and install G++ and it’s dependencies on one system and then just copy all of the packages off of some sort of cache or something onto the other systems?
briansvgs wrote:
> Hello,
>
> I have been running Ubuntu Linux for a few years now, but I am new to
> Suse. I am working on setting up some servers for a class at my school.
> There is one server that sits on the internet and there are nine servers
> that sit behind this one on a switch. Only the first server has any
> access to the internet. We are trying to install G++. I don’t want to
> run into the dependency hell that comes with manually downloading and
> installing a package and it’s dependencies, but don’t have the option of
> connecting each system to the internet. My question is is it possible to
> download and install G++ and it’s dependencies on one system and then
> just copy all of the packages off of some sort of cache or something
> onto the other systems?
>
> Thank you,
> Brian
>
>
I’m not an expert but you haven’t had an answer yet. So …
(1) you need to make YaST (or zypper) keep the RPMs it downloads. I
believe this is done by editing sysconfig
(2) you need to make the cached RPMs available as a repository for YaST
on other machines. This may help
It might be worth checking out the openSUSE:Education-Li-f-e - openSUSE DVD to see if it has what you want; you may have to install to each server separately but you will be guaranteed that all the dependencies will be the same.
In addition to what djh-novell mentioned, another simple solution is to just install a caching proxy on your Internet Gateway machine. Whether that machine proxies or blocks access to the Internet for your other machines would be unimportant, anything recently downloaded should be served from the cache. I’m not sure what reasons you have for not connecting the other machines to the Internet, a proxy does terminate network connections on both sides so technically it’s not permitting direct Internet connections to your other machines but it is permitting specified content to be requested and downloaded by those machines (to the caching proxy).
Note that cached content isn’t held indefinitely, the TTL is just longer than the original content. But, you’ll find that this solution would mean no restrictions on what you can serve indirectly to your other machines and no special configuration should be necessary for any specific kind of content.