I have a complicated kickstart based install that I have been using with
DVDs. I Would like to use USB drives, but I have a few questions that I
haven't gotten answers to yet.
1. what's the best way to create a bootable USB key/drive? I have been
using dd to put the ISO onto the device, but tha
n, but the core application is not happy about
running on 7 yet, so I have to wait. At least I should be able to get the
build system updated to support RHEL 7 in preparation. much better than
trying to play catch up.
Andrew Simpson
On Thu, Jan 29, 2015 at 8:15 PM, Spike White wrote:
> >
>
hich is included via %include /ks/pre.ks
at the beginning of the kickstart. Makes it fairly dynamic.
Andrew Simpson
On Mon, Mar 9, 2015 at 10:02 AM, Jerry Billing
wrote:
> Hi
>
> For virtual servers it is nice to use the whole disk for LVM instead of
> creating a LVM partition on the
have you thought about trying to find it by UUID or Label? I had a similar
issue in a kickstart where I could not determine the boot drive while
making a USB boot image. I ended up formatting the drives with a specific
LABEL and using that in the kickstart instead of using sda/sdb/etc...
Andrew
* How do you use kickstart right now? What work flows do you have
around it? Do you generate kickstart files from some process? Do you
store them in version control?
-use ks to generate developer and production installs in a consistent and
flexible manner
- we have a large script that assembles
chine. probably has been window-ized.
3. See my %pre section provided to Chris L a few posts back.
>
Andrew Simpson
On Mon, Mar 7, 2016 at 1:32 PM, Chris Lumens wrote:
> > Per requirements our application is installed standalone via DVD.
> > %pre : we only do --log= . No cu
devices
are available?
thanks!
Andrew Simpson
___
Kickstart-list mailing list
Kickstart-list@redhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
the volume name in your mkisofs command (—V option) must match the LABEL
value in the isolinux.cfg file exactly minus the x20 used for spaces.
yours don't match :
-V
'Red Hat Enterprise Linux 7.2'
hd:LABEL=RHEL-7.2\x20Server.x86_64
On Jun 8, 2016 2:28 AM, "C. Petro" wrote:
> I'm reasona
No. and you might want to use genisoimage going forward.
On Jun 8, 2016 9:05 AM, "Hearn, Stan J." wrote:
> Do I have to build the ISO on a RHEL 7 system?
>
>
>
> *From:* kickstart-list-boun...@redhat.com [mailto:
> kickstart-list-boun...@redhat.com] *On Behalf Of *Mr. Pushpendra Chavan
> *Sent:
yeah... that one bit me for almost a day lol. It was buried in the RHEL 7
documentation somewhere. I think if you tried to use something other than
hd:LABEL for the inst.stage2 option, you might not have to worry about it.
Andrew Simpson
On Wed, Jun 8, 2016 at 10:05 AM, C. Petro wrote
This is purely cosmetic, as mentioned.
If you need to install packages later on, simply mount the source in the
%post section and install via RPM or YUM and exclude those packages from
the %packages section
Andrew Simpson
On Thu, Aug 18, 2016 at 11:13 AM, Jason L Tibbitts III
wrote:
> Just
yet. comment out the RPM
install portion and see what's hanging. If it is indeed hanging on the
rpm, then there's probably an issue with one of the scriptlets in the rpm
spec file. The were likely be a log of that somewhere under /tmp or
/var/log/anaconda/
Andrew Simpson
On Thu, Sep
so we would unfortunately need to see the entire set of logs to find what's
stopping the install from rebooting/completing.
Andrew Simpson
On Fri, Sep 30, 2016 at 8:42 AM, Jacquet Romain <
romain.jacq...@telespazio.com> wrote:
> Hi Andrew,
>
> Thank you very much
just an FYI, lspci is now available during kickstart in 7.3
Andrew Simpson
On Wed, May 25, 2016 at 2:51 PM, Andrew Simpson
wrote:
> Doing a new kickstart setup under RHEL 7.2. The %pre section used lspci
> to determine what video devices are available at that time. In RHEL 6 was
&
eeing this on recent installs of
RHEL 7
Andrew Simpson
___
Kickstart-list mailing list
Kickstart-list@redhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
I have had a few issues migrating from RHEL 6 kickstart installs to RHEL 7.
1. pxeboot installs were failing because I did not have the LiveOS
directory included in the customized ISO. Is the LiveOS directory (and the
images in it) required in RHEL 7 now?
2. in pxeboot, I had to have the proper
Is anyone else getting immediate spam replies from posts to this list?
"karen chavez" is getting a wee bit annoying...
Can a list admin block this email: (yeah, I'm sure it will change)
Karen Chavez
Andrew Simpson
___
Kickstart-li
t times, as i'm not always in an environment
where pxe is available.
I, too, use the LABEL nomenclature. If you don't, you'll be guessing all
day about which device to use.
Andrew Simpson
On Thu, Mar 9, 2017 at 5:20 PM, Greg Oliver wrote:
> On Wed, Mar 8, 2017 at 6:39 AM, Andrew
Is there anyway to use an encrypted passphrase for luks disk encryption
when encrypting partitions?
Andrew Simpson
___
Kickstart-list mailing list
Kickstart-list@redhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
e in the chroot
mkdir -p /mnt/sysimage/tmp/source
mount --bind /tmp/source /mnt/sysimage/tmp/source
"""""""""""""# End Post Section ##
here's the genisoimage command:
genisoimage -r -v \
-V "LABELNAME.
Has anyone successfully automated installing and setting up a system using
an Nvidia Optimus graphics card under rhel/centos 7?
___
Kickstart-list mailing list
Kickstart-list@redhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
I have a kickstart that detects if nvidia cards are present in the pre
section and creates a .ks file with the appropriate nvidia RPMS for install
during the normal package installation section. This seems to work fine.
after all of the post sections are completed, every system that has the
nvidi
suggestions on how to test installation of a kickstart usb drive via
command line with kvm?
I used to do something like this for a quick test to make sure everything
ran fine:
/usr/libexec/qemu-kvm -hda /dev/sdc -m 2048 -vga std
but I'd rather be able to mount the iso and install from that as usb
Is it possible to require/force a user to enter in their user account
information before the install gets to the %post section via the graphical
installer? I need everything else to be automated, except this step, and
need to modify that user's groups in the "post" section. It appears that
if not
START BODY
>
>
> %post --nochroot
>
> mv /tmp/test /mnt/sysimage/tmp/test
>
> %end
>
>
> %post
>
> # Use /tmp/test to perform %post actions
>
> %end
>
>
>
> *Thanks,*
> *Pushpendra Chavan.*
>
>
>
> On Tue, Jun 29, 2021 at
en instead of using it in
>> %post, use the following line in ks
>>
>> %include /path/to/file
>>
>> Please make sure you have the file /path/to/file written in appropriate
>> Kickstart format.
>>
>> %pre section can be utilized to properly format
26 matches
Mail list logo
