Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Installation - Getting started with Red Hat Linux
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
X Windows problem (xauth)
Upgrading openoffice 1 1 rpm
FTP: connection refused
FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
broadcom network interface
make mrproper
sendmail configuration on redhat
Couldn 't open PID file /var/run/named/named pid Permission denied
Promise 378 controller
kernel 2 6 and /dev/sound/mixer not found
Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
Lotus Notes under Wine
/etc/security/limits conf question
Intel E/1000 driver
Command stream end of file while reading
rpm database corrupt
qla2300 modules
 
cd kickstarting question

cd kickstarting question

2006-02-13       - By inode0

 Back
Reply:     1     2     3     4     5     6     7  

On 2/13/06, bob flynn <bob.flynn@(protected)> wrote:
> The problem
>
> I have to boot from the 1st disk of whatever distribution I am using to
> use the NFS copy of the ISO image of the same distribution. This is a
> pain if I have to keep a set of CD's simply to boot to a kickstart. An
> exampple. If I am looking to installed Red Hat Enterprise WS 3.0 U2,
> then I have to boot from disk 1 of  Red Hat Enterprise WS 3.0 U2,
> anything else and it will complain. So I am looking for workarounds.
>
> Possible solutions.
>
> 1. PXE and ignore the requirement to boot from CD to start. The downside
> is I am supporting some boxes which are not PXE enabled.
>
> 2. A generic boot disk which will allow me to kickstart without having
> the boot disk having to match the NFS version of whatever I am
> kickstarting via NFS ?
>
> This would be a reasonable solution ( extra points for the image
> supporting booting via USB, for those machines for which a USB boot is
> simplier ).
>
> Ideas ?

I tried chasing down this problem a while back. I recall that when an
old boot.iso image or equivalent is used the logs showed it was
looking for an update image on the server to, I presume, be used to
correct diffs between the versions. This update image appears to no
longer be provided by Red Hat with newer updates so the installation
bails.

I did not check whether the floppy/usb boot image also suffered from
this at the time. We have no happy solution other than updating our
boot media at the same time we update our install trees.

John

--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list