I am currently making a custom CentOS disk in which i need it to skip the disk verify option all together. In past versions (V4&5) of CentOS I had just run:
So I run this, and there are no errors. However once the disk is burnt, and i boot, I still get prompted to verify the disk. Has something changed? I am trying to narrow it down as I am testing in a virtual box VM, and I am wondering if that is causing the issues.
Thank you,
D
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
08-09-2012, 11:21 PM
Jesse Keating
implantisomd5 - disk verify issue
On 08/09/2012 03:17 PM, DNK wrote:
Hi there,
I am currently making a custom CentOS disk in which i need it to skip
the disk verify option all together. In past versions (V4&5) of
CentOS I had just run:
So I run this, and there are no errors. However once the disk is
burnt, and i boot, I still get prompted to verify the disk. Has
something changed? I am trying to narrow it down as I am testing in a
virtual box VM, and I am wondering if that is causing the issues.
Thank you,
D
The prompt isn't triggered on having ran implantisomd5. It's hard coded
to prompt, period. You'd have to modify the anaconda code to alter that
behavior.
--
Jesse Keating
Fedora -- Freedom˛ is a feature!
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
08-09-2012, 11:26 PM
DNK
implantisomd5 - disk verify issue
On 2012-08-09, at 4:21 PM, Jesse Keating <jkeating@redhat.com> wrote:
> On 08/09/2012 03:17 PM, DNK wrote:
>> Hi there,
>>
>> I am currently making a custom CentOS disk in which i need it to skip
>> the disk verify option all together. In past versions (V4&5) of
>> CentOS I had just run:
>>
>> # /usr/lib/anaconda-runtime/./implantisomd5 --supported-iso
>> MYISO.iso
>>
>> In V6, the binary changed locations, but easy enough to deal with.
>>
>> # /usr/bin/implantisomd5 --supported-iso MYISO.iso
>>
>> So I run this, and there are no errors. However once the disk is
>> burnt, and i boot, I still get prompted to verify the disk. Has
>> something changed? I am trying to narrow it down as I am testing in a
>> virtual box VM, and I am wondering if that is causing the issues.
>>
>> Thank you,
>>
>> D
>>
>
>
> The prompt isn't triggered on having ran implantisomd5. It's hard coded to prompt, period. You'd have to modify the anaconda code to alter that behavior.
>
>
> --
> Jesse Keating
> Fedora -- Freedom˛ is a feature!
>
>
Ah, ok. This used to work though. a behaviour change in the source I guess?
I had actually gotten the recommendation to get rid of it that way from this list a few years ago.
D
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
08-09-2012, 11:34 PM
Jesse Keating
implantisomd5 - disk verify issue
On 08/09/2012 04:26 PM, DNK wrote:
Ah, ok. This used to work though. a behaviour change in the source I
guess?
I had actually gotten the recommendation to get rid of it that way
from this list a few years ago.
Oh, I misread, and missed the --supported-iso part. Yeah, since Red Hat
does pressed media, we set up that media so that it doesn't prompt for
media checking vs the isos we put up for download, where we force the
prompt. Honestly, I don't know how that's done for RHEL6 (or for any
RHEL for that matter). Probably best to explore the code.
--
Jesse Keating
Fedora -- Freedom˛ is a feature!
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
implantisomd5 - disk verify issue
