 | | | cd kickstarting question | cd kickstarting question 2006-02-14 - By Clif Smith
Back
Please share your knowledge when you're done. I'm needed to solve this as
well.
Thanks!
On 2/13/06, Greg Hosler <greg@(protected)> 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 share your knowledge when you're done. I'm needed to solve this as
well.<br><br>Thanks!<br><br><div><span class="gmail_quote">On 2/13/06, <b class
="gmail_sendername">Greg Hosler</b> <<a href="mailto:greg@(protected)">
greg@(protected)</a>> wrote:</span><blockquote class="gmail_quote" style=
"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding
-left: 1ex;">What I did, was I created a bootable usb disk, and I have grub
entries that
<br>allow me to chose one of multiple boot options. Each boot entry will point
to<br>it's separate boot isolinux directory for it's respective kernel &
initrd<br>(which, of course need to match the respective install tree, but you
pass the
<br>pointer to the install tree in the kickstart file. since the boot entry
points<br>to the kickstart file, this is not a problem...)<br><br>I'm in the
process of writing up how I set this up for some overseas collegues,
<br>if you want, I'll forward you a copy.<br><br>best rgds,<br><br>-Greg<br><br
>On 13-Feb-2006 (See http://Feb-2006.ora-code.com) bob flynn wrote:<br>> Hi,<br>><br>> I am kickstarting a
variety of machines, and I have the following issue.<br>><br>
> My kickstart works as follows;<br>><br>> Maintain NFS server with
ISO images of distributions available.<br>> Kickstart file and any pre
/postscripts available on NFS server.<br>><br>> Boot from CD1 from
whatever distribution version I intend to install.
<br>> Once at the linux prompt, specifying the kickstart file and a NFS<br>
> installation and off I go.<br>><br>> The problem<br>><br>> I
have to boot from the 1st disk of whatever distribution I am using to
<br>> use the NFS copy of the ISO image of the same distribution. This is a
<br>> pain if I have to keep a set of CD's simply to boot to a kickstart. An
<br>> exampple. If I am looking to installed Red Hat Enterprise WS
3.0 U2,<br>> then I have to boot from disk 1 of Red Hat
Enterprise WS 3.0 U2,<br>> anything else and it will complain. So I am
looking for workarounds.<br>><br>> Possible solutions.<br>><br>> 1.
PXE and ignore the requirement to boot from CD to start. The downside
<br>> is I am supporting some boxes which are not PXE enabled.<br>><br>
> 2. A generic boot disk which will allow me to kickstart without having<br>
> the boot disk having to match the NFS version of whatever I am
<br>> kickstarting via NFS ?<br>><br>> This would be a reasonable
solution ( extra points for the image<br>> supporting booting via USB, for
those machines for which a USB boot is<br>> simplier ).<br>><br>
> Ideas ?<br>><br>><br>> The information contained in this e-mail
and in any attachments is<br>> confidential and is designated solely for the
attention of the intended<br>> recipient(s). If you are not an intended
recipient, you must not use,
<br>> disclose, copy, distribute or retain this e-mail or any part thereof.
If you<br>> have received this e-mail in error, please notify the sender by
return e-mail<br>> and delete all copies of this e-mail from your computer
system(s).
<br>> Please direct any additional queries to: <a href="mailto
:communications@(protected)">communications@(protected)</a>.<br>> Thank You.
<br>><br>> --<br>> Taroon-list mailing list<br>> <a href="mailto
:Taroon-list@(protected)">
Taroon-list@(protected)</a><br>> <a href="https://www.redhat.com/mailman
/listinfo/taroon-list">https://www.redhat.com/mailman/listinfo/taroon-list</a>
<br><br>+-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------+
<br><br>Please also check the log file at "/dev/null" for additional
information.<br>
(from /var/log/Xorg.setup.log)<br><br>| Greg
Hosler
<a href="mailto:greg
@(protected)">
greg@(protected)</a> |<br>+-- ---- ---- ---- ---- ----
-- ---- ---- ---- ---- ---- ---- ---- ----+<br><br>--<br>Taroon-list mailing
list<br><a href="mailto:Taroon-list@(protected)">Taroon-list@(protected)</a><br>
<a href="https://www.redhat.com/mailman/listinfo/taroon-list">
https://www.redhat.com/mailman/listinfo/taroon-list</a><br></blockquote></div>
<br>
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
|