Re: boot images v9.0
From: JM Fraser (jmf_at_cybertrex.co.uk)
Date: 11/19/03
- Next message: Pete Zaitcev: "Re: RHEL, first impressions"
- Previous message: Tommy Reynolds: "Re: boot images v9.0"
- In reply to: Tommy Reynolds: "Re: boot images v9.0"
- Next in thread: Michael Thomas: "Re: boot images v9.0"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 19 Nov 2003 18:31:20 +0000
I am using an FTP server to access the installation files so I do not
use ISO for boot images. With V8.0, you use to be able to create a
boot disk using just Rawrite and bootnet.img which is how I have
always done it. Now that there is no bootnet.img with v9.0 I am a
little unsure as to how I can create the boot disk.
If I have to then yes I suppose I will have to go about the CD ISO
route, but having already downloaded the installation files, I am
loathe to go thru this labourious process. JM
On Wed, 19 Nov 2003 12:00:47 -0600, "Tommy Reynolds"
<TommyReynolds@yahoo.com> wrote:
On Wed, 19 Nov 2003 16:30:41 +0000, JM Fraser wrote:
> Are there any specific differences between bootnet.img and drvnet.img?
> I am trying to create a boot disk for v9.0 but am unable to. Under
> v8.0, bootnet.img was the image file I used but this is not available
> under v9.0. Is there any reason for this or is there some other way to
> create a boot disk via command line? thx. JM
Check the README file in the "images/" directory of your first distro
iso CD image. You need to make two floppies: the bootdisk.img one,
and
then either "drvblock.img", "drvnet.img", or "pcmciadd.img" depending
on
how you are intending to access the RPMs.
_
Before Microsoft, it was alleged that there was chaos. I chose Redhat.
- Next message: Pete Zaitcev: "Re: RHEL, first impressions"
- Previous message: Tommy Reynolds: "Re: boot images v9.0"
- In reply to: Tommy Reynolds: "Re: boot images v9.0"
- Next in thread: Michael Thomas: "Re: boot images v9.0"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|