Re: install fedora 3 over lan ftp or nfs not seen by the client machine
From: nntp_usr (urjunkhere_at_foobar.nit)
Date: Sat, 23 Apr 2005 22:29:29 GMT
> nntp_usr wrote:
>> Tim wrote:
>>> On Tue, 19 Apr 2005 17:28:01 GMT,
>>> nntp_usr <email@example.com> posted:
>>>> FTP SET-UP
>>>> I su'd to root, opened k3b, put in a blank cdr, and made a iso of
>>>> boot.img; copied the dvd by cp-a /media/cdrecorder-whatever-dvd
>>>> /var/ftp/pub/rh; copied the discinfo file to the target directory.
>>> Are you sure you've used the right image file? Though I'd guess so if
>>> you've gotten something to boot and ask you how you want to install.
>>> Though I know with older versions of Linux you might be able to pick an
>>> image that didn't include what you needed for network installation,
>>> need a driver disc, too. There's still a possiblity that your network
>>> card isn't supported by the install routine.
>>>> CLIENT SET-UP
>>>> I placed the cdr into the machine to get to the install screen, and the
>>>> machine boots to the Fedora F menus. I choose "linux text." I also
>>>> tried "linux askmethod" (yet neither method works for me).
>>>> The client's terminal output shows proper configuration on the network
>>>> adapter card.
>>>> I set up the machine manually with no dhcp nor host name, but with an
>>>> IP address, netmask, and gateway. There isn't any DNS. I've tried
>>>> 127.0.0.1, leaving it blank, and 0.0.0.0. The install says it's looking
>>>> for its hostname via DNS / RARP (which it should not do since I assign
>>>> the IP to the machine manually).
>>> 0.0.0.0 isn't an IP address, and 127.0.0.1 is itself. Give it a network
>>> address for the same network as where you're trying to access the
>>> installation files.
>>> e.g. Install files being fetched from 192.168.0.1
>>> And the new computer you're installing to as 192.168.0.2
>>> With a netmask of 255.255.255.0
>>>> The computer then asks for the hostname / IP and fedora core directory.
>>>> I enter the information and it returns that it cannot find the tree or
>>>> NFS image. I've tried several different paths and tried to use
>>>> non-anon. authorization (no-go).
>>> For NFS or FTP it wants to find ISO files to install from. For HTTP
>>> installs it can be ISOs or individual files. I prefer HTTP with
>>> individual files, it's much quicker to install from, and easy to add
>>> more packages from the server later on, just by getting the ones that
>>> you want.
>>> I'm not sure of the structure needed for ISO files to be served, but for
>>> HTTP make a directory somewhere, dump the contents of the CD-ROMs
>>> directly into it.
>>> e.g. If you made a www/fedora/ directory, the root files from the CD
>>> would be in the fedora/ directory.
>> The correct driver is assigned the network adapter, per the control-alt
>> F3 terminal.
>> I used the "boot.img" from the DVD. The image gets me through to picking
>> a language, assigning an IP to the client.
>> I tried the DNS entry of the lan, but that doesn't work either.
>> Nevertheless, the client machine to-get-the-install
>> should not
>> even try
>> to use DNS, it seems to me, as I provide all the information myself, not
>> relying on DNS. Yet the installer insists on locating host name / IP.
>> The output is: transering ftp://x.x.x.x/pub/rh/Fedora/base/netstg2.img to
>> a fd
>> --then the install process drops back to asking for the host name / IP
>> address of the ftp server. The text cursor shows up in the host name IP
>> line of the installer, the part that asks for ftp server location.
>> FROM THE DVD
>> "This directory [the images directory] contains image files that can be
>> used to create media
>> capable of starting the Fedora Core installation process.
>> The boot.iso file is an ISO 9660 image of a bootable CD-ROM. It is
>> useful in cases where the CD-ROM installation method is not desired, but
>> the CD-ROM's boot speed would be an advantage.
>> To use this image file, burn the file onto CD-R (or CD-RW) media as you
>> normally would.
>> The diskboot.img file is a VFAT filesystem image that can be written to a
>> USB pendrive or other bootable media larger than a floppy. Note that
>> booting via USB is dependent on your BIOS supporting this. It should
>> be written to the device using dd."
> Also the tty log output about tranfering ftp://whatever to an fd: well, fd
> is sort of memory leak.
Anybody else? Any "takers"?.