Network install failure

[Matt Whiteley]

I have tried to use the network install many times.  This is an attempt
with the .iso files.  Whenever I put them in a web or ftp directory, the
installer will not find them and pecularly returns to the screen with
extra slashes in the address box.  Such as cannot find
http://192.168.1.112//redhat/stage2.img .  I hope this is somewhat close
as I am taking it from memory.  Am I making some stupid mistake?  What
is the deal?

thanks,

-- 
Matt Whiteley <matt-whiteley(a)comcast.net&gt;

[Matt Whiteley]

On Wed, 2003-07-23 at 14:26, Tudor Popescu wrote:
>  Hello,
>  
>  I believe that in order to do a HTTP or FTP install you need to have the
>  extracted isos -
>  
>  however, I too had a problem while trying to FTP install from mounted iso
>  images
>  (disc1, disc2, disc3). Looking at the ftp logs showed that the install
>  program
>  (after succesfully loading stage2), right when searching for the first
>  packet
>  (glibc-common I believe) was trying to access a directory named
>  /ftp/pub/mirrors/ftp.redhat.com/linux/beta/severn/en/disc1/disc1 (note the
>  extra disc1).
>  
>  Using the rh_extract_iso.sh script to extract all isos into one 'os'
>  directory
>  and restarting install worked though.
>  
>  
>  --
>  Tudor Popescu
>  top(a)warp.ro 
I am not familiar with the script you are speaking of but I did the
copy
by hand and it worked.  I had been told that the iso network install
worked with the NFS, FTP, and HTTP variants.  It appears this was
incorrect.

thanks,

-- 
Matt Whiteley <matt-whiteley(a)comcast.net&gt;

Matt Whiteley wrote:

> On Thu, 2003-07-24 at 09:04, Mike McLean wrote:
>   
>
> ><snip>
> >The network install methods are: nfs, ftp, http, nfsiso, httpdisc, and 
> >ftpdisc.
> >
> >- nfs, ftp, and http installs work off of a unified tree (All rpms in a 
> >single tree) that is accessible via the given protocol.
> >
> >- nfsiso works off of an nfs directory containing the isos (and nothing 
> >else!).  No other network install method can use raw isos.
> >
> >- ftpdisc and httpdisc work off of a directory containing the split tree 
> >(one subdirectory per disc).  So you might point the installer at 
> >http://myserver/Severn/discs/ where the discs directory contains 
> >subdirectories disc1, disc2, and disc3 which themselves contain the 
> >contents of the three discs.  The idea behind these methods is that you 
> >can loopback mount the three isos on your server, make those mountpoint 
> >accessible via ftp or http, and run a network install off of that.
> >    
> > 
thanks

> This was so much easier and complete to understand than what I read
> in
> the manual.
>  
i have no luck with my
    intel etherexpress 100 / e100  driver
link is ok but no network-connection
no ping, http, nfs, ftp, ... is possible

with the rhl 9  bootdisk.img, drvnet.img  no problems


then i have to cdrecording at least cd #1 for a minimal 
english-installation,
german-mini-inst need 3 packages from cd #2 and no chance to come 
further without cd #2  :-(



while burning,
it seems that anaconda try his best to find  cd/iso/directory


tty3:

local cd-rom:
->
# trying to mount device hdd


harddisk:
  /dev/hdb1
  /severn
->
# partition /dev/hdb1 selected
# mounting hdb1 for harddrive install

    tty4
    <4> EXT2-fs warning ...




nfs:
# going to do nfsGetSetup
  192.168.0.1
  severn
->
# mounting nfs path 192.168.0.1:/severn


ftp:
  192.168.0.1
  severn
->
# starting to STEP_URL
# trying to mount device hdd
# transferring ftp://192.168.0.1//severn/RedHat/base/updates.img to fd
# transferring ftp://192.168.0.1//severn/RedHat/base/product.img to fd
# 2565000 are available
# transferring ftp://192.168.0.1//severn/RedHat/base/stage2.img to fd


http:
  192.168.0.1
  severn
->
# trying to mount device hdd
# transferring http://192.168.0.1//severn/RedHat/base/updates.img to fd
# transferring http://192.168.0.1//severn/disc1/RedHat/base/updates.img 
to fd
# transferring http://192.168.0.1//severn/RedHat/base/product.img to fd
# transferring http://192.168.0.1//severn/disc1/RedHat/base/product.img 
to fd
# 2565000 are available
# transferring http://192.168.0.1//severn/RedHat/base/stage2.img to fd
# transferring http://192.168.0.1//severn/disc1/RedHat/base/stage2.img to fd


-- 
shrek-m

[Matt Whiteley]

On Thu, 2003-07-24 at 09:04, Mike McLean wrote:
>  <snip>
>  The network install methods are: nfs, ftp, http, nfsiso, httpdisc, and 
>  ftpdisc.
>  
>  - nfs, ftp, and http installs work off of a unified tree (All rpms in a 
>  single tree) that is accessible via the given protocol.
>  
>  - nfsiso works off of an nfs directory containing the isos (and nothing 
>  else!).  No other network install method can use raw isos.
>  
>  - ftpdisc and httpdisc work off of a directory containing the split tree 
>  (one subdirectory per disc).  So you might point the installer at 
>  http://myserver/Severn/discs/ where the discs directory contains 
>  subdirectories disc1, disc2, and disc3 which themselves contain the 
>  contents of the three discs.  The idea behind these methods is that you 
>  can loopback mount the three isos on your server, make those mountpoint 
>  accessible via ftp or http, and run a network install off of that. 
This was so much easier and complete to understand than what I read in
the manual.

thanks,

-- 
Matt Whiteley <matt-whiteley(a)comcast.net&gt;

[Mike McLean]

Matt Whiteley wrote:
>  I have tried to use the network install many times.  This is an
> attempt
>  with the .iso files.  Whenever I put them in a web or ftp directory, the
<snip>
The network install methods are: nfs, ftp, http, nfsiso, httpdisc, and 
ftpdisc.

- nfs, ftp, and http installs work off of a unified tree (All rpms in a 
single tree) that is accessible via the given protocol.

- nfsiso works off of an nfs directory containing the isos (and nothing 
else!).  No other network install method can use raw isos.

- ftpdisc and httpdisc work off of a directory containing the split tree 
(one subdirectory per disc).  So you might point the installer at 
http://myserver/Severn/discs/ where the discs directory contains 
subdirectories disc1, disc2, and disc3 which themselves contain the 
contents of the three discs.  The idea behind these methods is that you 
can loopback mount the three isos on your server, make those mountpoint 
accessible via ftp or http, and run a network install off of that.

[Tudor Popescu]

Hello,

I believe that in order to do a HTTP or FTP install you need to have the
extracted isos -

however, I too had a problem while trying to FTP install from mounted iso
images
(disc1, disc2, disc3). Looking at the ftp logs showed that the install
program
(after succesfully loading stage2), right when searching for the first
packet
(glibc-common I believe) was trying to access a directory named
/ftp/pub/mirrors/ftp.redhat.com/linux/beta/severn/en/disc1/disc1 (note the
extra disc1).

Using the rh_extract_iso.sh script to extract all isos into one 'os'
directory
and restarting install worked though.


--
Tudor Popescu
top(a)warp.ro


----- Original Message ----- 
From: "Matt Whiteley" <matt-whiteley(a)comcast.net&gt;
To: "rhl beta list" <rhl-beta-list(a)redhat.com&gt;
Sent: Thursday, July 24, 2003 12:11 AM
Subject: Network install failure


>  I have tried to use the network install many times.  This is an
> attempt
>  with the .iso files.  Whenever I put them in a web or ftp directory, the
>  installer will not find them and pecularly returns to the screen with
>  extra slashes in the address box.  Such as cannot find
>  http://192.168.1.112//redhat/stage2.img .  I hope this is somewhat close
>  as I am taking it from memory.  Am I making some stupid mistake?  What
>  is the deal?
>
>  thanks,
>
>  -- 
>  Matt Whiteley <matt-whiteley(a)comcast.net&gt;
>
>
>  --
>  Rhl-beta-list mailing list
>  Rhl-beta-list(a)redhat.com
>  http://www.redhat.com/mailman/listinfo/rhl-beta-list
>

[Michael Steele]

On Wed, 23 Jul 2003, Matt Whiteley wrote:

>  I have tried to use the network install many times.  This is an
> attempt
>  with the .iso files.  Whenever I put them in a web or ftp directory, the
>  installer will not find them and pecularly returns to the screen with
>  extra slashes in the address box.  Such as cannot find
>  http://192.168.1.112//redhat/stage2.img .  I hope this is somewhat close
>  as I am taking it from memory.  Am I making some stupid mistake?  What
>  is the deal?
>
>  thanks,
>
>  --
>  Matt Whiteley <matt-whiteley(a)comcast.net&gt;
>
>
>  --
>  Rhl-beta-list mailing list
>  Rhl-beta-list(a)redhat.com
>  http://www.redhat.com/mailman/listinfo/rhl-beta-list
>  
I don't think you can do that.  You first have to mount the .iso images,
and copy the files out of them into your http server.

If I recall correctly, after you've mounted disc 1, you will need to
copy the whole file structure to your webserver's /redhat directory.

For the other CDs you just need to copy all of the .rpm files from the
iso image's /RedHat/RPMS directory into the /redhat/RedHat/RPMS
directory of your web server.

If your web server is another linux box, you can mount the images with
somthing similar to this:

# mkdir /mnt/iso
# mount -o loop -t iso9660 psyche-i386-disc1.iso /mnt/iso

Then:

# cd /mnt/iso
# cp -av * /path-to-document-root/redhat

Then:

# cd; umount /mnt/iso
# mount -o loop -t iso9660 psyche-i386-disc2.iso /mnt/iso
# cd /mnt/iso/RedHat/RPMS
# cp * //path-to-document-root/redhat/RedHat/RPMS

Then do the same for CD 3.

+===============================================+
| N     Michael V. Steele                     M |
| A     UNIX Systems Administrator            S |
| S     Computer Sciences Corporation         F |
| A     NASA/IFMP/MSFC                        C |
+===============================================+
|       Red Hat Certified Engineer              |
|       Sun Certified System Administrator      |
|       Cisco Certified Network Associate       |
+===============================================+


:wq