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-16       - By Greg Hosler

 Back
Reply:     1     2     3     4     5     6     7  

took me a few days to finish off and tidy this up.

The attached describes the following: how to create a bootable USB disk, and
configure it such that you can have

       - multiple ks files you boot
       - those ks files can be for different version of RHEL

The secret (as described in the attached howto), is to copy the isolinux
directory from the boot.iso of each release that you need to support.

the respective kickstart file has the following for the install method:

       harddrive --partition /dev/sda1 --dir RHEL4-U2-isos

where the mentioned dir is relative to the the base of the partition mentioned,
and contains iso images (installs from hard drive doesn't support installing
from a laid out tree).

enjoy,

best rgds,

-Greg Hosler




On 13-Feb-2006 (See http://Feb-2006.ora-code.com) Greg Hosler wrote:
> What I did, was I created a bootable usb disk, and I have grub entries that
> allow me to chose one of multiple boot options. Each boot entry will point to
> it's separate boot isolinux directory for it's respective kernel & initrd
> (which, of course need to match the respective install tree, but you pass the
> pointer to the install tree in the kickstart file. since the boot entry
> points
> to the kickstart file, this is not a problem...)
>
> I'm in the process of writing up how I set this up for some overseas
> collegues,
> if you want, I'll forward you a copy.
>
> best rgds,
>
> -Greg
>
> On 13-Feb-2006 (See http://Feb-2006.ora-code.com) bob flynn wrote:
>> Hi,
>>
>> I am kickstarting a variety of machines, and I have the following issue.
>>
>> My kickstart works as follows;
>>
>> Maintain NFS server with ISO images of distributions available.
>> Kickstart file and any pre/postscripts available on NFS server.
>>
>> Boot from CD1 from whatever distribution version I intend to install.
>> Once at the linux prompt, specifying the kickstart file and a NFS
>> installation and off I go.
>>
>> 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 ?
>>
>>
>> The information contained in this e-mail and in any attachments is
>> confidential and is designated solely for the attention of the intended
>> recipient(s). If you are not an intended recipient, you must not use,
>> disclose, copy, distribute or retain this e-mail or any part thereof. If you
>> have received this e-mail in error, please notify the sender by return
>> e-mail
>> and delete all copies of this e-mail from your computer system(s).
>> Please direct any additional queries to: communications@(protected)
>> Thank You.
>>
>> --
>> Taroon-list mailing list
>> Taroon-list@(protected)
>> https://www.redhat.com/mailman/listinfo/taroon-list
>
> +-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------+
>
> Please also check the log file at "/dev/null" for additional information.
>                 (from /var/log/Xorg.setup.log)
>
>| Greg Hosler                                   greg@(protected)    |
> +-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------+
>
> --
> Taroon-list mailing list
> Taroon-list@(protected)
> https://www.redhat.com/mailman/listinfo/taroon-list

+-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------+

Please also check the log file at "/dev/null" for additional information.
               (from /var/log/Xorg.setup.log)

| Greg Hosler                                   greg@(protected)    |
+-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------+

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