 | | | cd kickstarting question | cd kickstarting question 2006-02-14 - By Bob Flynn
Back
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) |
>+-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------+
>
>
I'd love a copy if you get a chance.
-Bob
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.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859 (See http://ISO-8859.ora-code.com)-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Greg Hosler wrote:<br>
<blockquote cite="midXFMail.20060214065603.greg@(protected)"
type="cite">
<pre wrap="">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:
</pre>
<blockquote type="cite">
<pre wrap="">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: <a class="moz-txt-link-abbreviated"
href="mailto:communications@(protected)">communications@(protected)</a>.
Thank You.
--
Taroon-list mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Taroon-list@(protected)">Taroon
-list@(protected)</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo
/taroon-list">https://www.redhat.com/mailman/listinfo/taroon-list</a>
</pre>
</blockquote>
<pre wrap=""><!---->
+-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------+
Please also check the log file at "/dev/null" for additional information.
(from /var/log/Xorg.setup.log)
| Greg Hosler <a class="moz-txt-link
-abbreviated" href="mailto:greg@(protected)">greg@(protected)</a> |
+-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------+
</pre>
</blockquote>
I'd love a copy if you get a chance.<br>
<br>
-Bob<br>
<br>
<BR><HR>
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.
<BR><HR><BR></body>
</html>
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
|