Greets: I would like to setup an ftp server (internal first, then external) that others can use as an installation source to grab software that we are working on. So far I have only found notes on the susehelp/support system for doing this for SuSE cd's but this is of no interest. Can any one point me to some notes on how to set this up. Many moons ago this was dead simple with yast1 but this no longer seems to be the case. regards /ch
On Friday 22 October 2004 13:46, Chris H wrote:
Can any one point me to some notes on how to set this up. Many moons ago this was dead simple with yast1 but this no longer seems to be the case.
Seems that once again I spoke to soon. The suse support article; http://portal.suse.com/sdb/en/2004/02/yast_instsrc.html is most informative. So befor I go down this road, anyone tested this approach and any gotcha's? Regards and thanks as always /ch
Chris wrote regarding 'Re: [SLE] Yast ftp server source' on Fri, Oct 22 at 13:06:
On Friday 22 October 2004 13:46, Chris H wrote:
Can any one point me to some notes on how to set this up. Many moons ago this was dead simple with yast1 but this no longer seems to be the case.
Seems that once again I spoke to soon. The suse support article; http://portal.suse.com/sdb/en/2004/02/yast_instsrc.html is most informative.
So befor I go down this road, anyone tested this approach and any gotcha's?
Regards and thanks as always
I didn't read the link, but if it says "copy files to x, then point the installer at x", it's fine. I've installed almost every [suse] machine here at work using that method, and it works great. I actually prefer the http-based installs, mostly because https a little lighter and doesn't require logging in, but that doesn't (or didn't) work well with name-based http servers. SuSE - you listening? Send the darned host: header, and let me type in a hostname instead of an IP if resolv.conf is configured. :) --Danny
On Friday 22 October 2004 17:54, Danny Sauer wrote:
I didn't read the link, but if it says "copy files to x, then point the installer at x", it's fine.
Nah..thats not what it says..:) Its a rather good read especially if you want to create an internal or external http/ftp server that you can point your servers too.
I've installed almost every [suse] machine here at work using that method, and it works great.
Im sure this works fine for local machines but not remote machines ie: off-site or satelite offices. Especially not so for custom software that you want to mass deploy..eg: point all machines in all locations to a specific server that provides qa'd non suse software. Now i can simply tell someone to point yast to a specific URL and I know they will get the software that I want uploaded. /ch
Chris wrote regarding 'Re: [SLE] Yast ftp server source' on Sat, Oct 23 at 23:46:
On Friday 22 October 2004 17:54, Danny Sauer wrote:
I didn't read the link, but if it says "copy files to x, then point the installer at x", it's fine.
Nah..thats not what it says..:) Its a rather good read especially if you want to create an internal or external http/ftp server that you can point your servers too.
I've installed almost every [suse] machine here at work using that method, and it works great.
Im sure this works fine for local machines but not remote machines ie: off-site or satelite offices. Especially not so for custom software that you want to mass deploy..eg: point all machines in all locations to a specific server that provides qa'd non suse software.
Doh - I read too quickly. I thought you were talking about installing SuSE software, not extra custom software onto an existing SuSE box. Whoops. :) I have done the SuSE install at several remote locations this way, though, and it works fairly well. Even though it's not what you asked... --Danny
On Friday 22 October 2004 23:54, Danny Sauer wrote:
Chris wrote regarding 'Re: [SLE] Yast ftp server source' on Fri, Oct 22 at 13:06:
http://portal.suse.com/sdb/en/2004/02/yast_instsrc.html is most informative.
Chris: Good pointer! :)
I actually prefer the http-based installs, mostly because https a little lighter and doesn't require logging in, but that doesn't (or didn't) work well with name-based http servers. SuSE - you listening? Send the darned host: header, and let me type in a hostname instead of an IP if resolv.conf is configured. :)
Danny: I don't understand. I usually use: insmod=pcnet32 install=http://10.0.0.1/pub/suse/i386/9.1 autoyast=http://10.0.0.1/pub/suse/profiles (1 line, entered at the boot prompt). I have not had any problems with that. How do you install? Cheers, Leen
Leendert wrote regarding 'Re: [SLE] Yast ftp server source' on Sun, Oct 24 at 02:49:
On Friday 22 October 2004 23:54, Danny Sauer wrote:
I actually prefer the http-based installs, mostly because https a little lighter and doesn't require logging in, but that doesn't (or didn't) work well with name-based http servers. SuSE - you listening? Send the darned host: header, and let me type in a hostname instead of an IP if resolv.conf is configured. :)
Danny: I don't understand. I usually use:
insmod=pcnet32 install=http://10.0.0.1/pub/suse/i386/9.1 autoyast=http://10.0.0.1/pub/suse/profiles
(1 line, entered at the boot prompt). I have not had any problems with that.
How do you install?
I've got a web server hosting multiple virtual servers on the same IP address, so I have to remember to put the SuSE sources on the default virtual server. That's annoying - I'd rather make a new virtual server, call it "suse.mydomain.com", and just point the installer at that. I can't do that, though, because the darned http get thingie doesn't send the host header along. It's not *that* hard to pull the host part of the URL out (gotta be done for name reolution anyway) and to then stick it into the header just before the GET. I guess it's GPLd now, though, so I suppose I should either fix it myself or shut up, eh? :) --Danny, considering that maybe "http://install.mydomain.com/suse/9.2" might be more effective...
participants (3)
-
Chris H -
Danny Sauer -
Leendert Meyer