sudo Yang wrote:
> On 8/3/05, Ugo Bellavance <ugob@xxxxxxxxxxxxxx> wrote:
>
>>sudo Yang wrote:
>>
>>>On 8/3/05, Ugo Bellavance <ugob@xxxxxxxxxxxxxx> wrote:
>>>
>>>
>>>>sudo Yang wrote:
>>>>
>>>>
>>>>>On 8/3/05, Steven Vishoot <sir_funzone@xxxxxxxxx> wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Ugo,
>>>>>>
>>>>>>hmmmm at first i was saying to myself, well sudo said
>>>>>>that he knew about the riserfs support in centosplus
>>>>>>directory but that he cant do that with kickstart. Now
>>>>>>i see what you are talking about, use kickstart and
>>>>>>then do a yum update kernel(for riserfs) and then
>>>>>>reboot. ah i see said the blind man to the deaf man.
>>>>>
>>>>>
>>>>>Keep in mind that the kernel used during the kickstart process (used
>>>>>to be called the BOOT kernel) has to support the file system type,
>>>>>otherwise you can't create the file system(s) during the kick
>>>>>process. Someone recommended installing a kernel that supports the
>>>>>file system then do mkfs using that kernel after the kick, but this
>>>>>seems kind of kludgy.
>>>>
>>>>Why would you need to create a FS if it is an upgrade?
>>>
>>>
>>>Because we currently add about 5-10 new servers a month. Both upgrade
>>>and new installation have to be considered.
>>>
>>
>>But, in the case of an install, you cannot create the filesystem after
>>the install?
>
>
> You can by doing it yourself or with a script. Anything is doable --
> just trying to determine the best way. Everything else seems kludgy
> unless it's integrated into Anaconda/kickstart.
Isn't there a post-install script option in kickstart? I wonder if it
could support an action (create FS) after a reboot (for the new kernel).
>
>
>>--
>>Ugo
>>
>>-> Please don't send a copy of your reply by e-mail. I read the list.
>>-> Please avoid top-posting, long signatures and HTML, and cut the
>>irrelevant parts in your replies.
>>
>>_______________________________________________
>>CentOS mailing list
>>CentOS@xxxxxxxxxx
>>http://lists.centos.org/mailman/listinfo/centos
>>
--
Ugo
-> Please don't send a copy of your reply by e-mail. I read the list.
-> Please avoid top-posting, long signatures and HTML, and cut the
irrelevant parts in your replies.
