Unfortunately, Rick I can't due to non-disclosure agreements and such but
here is a quick
run down:
1) Use mknod to create the device files you need.
2) Use "fdisk -l <device>" to get the current partition table. Using
read in the
the shell you can parse the output fairly handily.
3) Once your output is parsed create a multiline string that would
generate
the appropriate commands for fdisk to create the exact partition
table you
need.
4) Pipe this command string into fdisk as in:
echo "${cmdString}" | fdisk
Note double quoting the var is important as otherwise the end of
line chars will
become spaces.
The kickstart directives to partition your drive should be omitted from
your kickstart file of course.
Sorry I can't be more helpful...james
rick bradshaw <bradshaw@xxxxxxxxxxx>@redhat.com on 12/19/2002 09:56:48 AM
Please respond to kickstart-list@xxxxxxxxxx
Sent by: kickstart-list-admin@xxxxxxxxxx
To: kickstart-list@xxxxxxxxxx
cc:
Subject: Re: dealing with persistant data
james.oden@xxxxxxxxxxx writes:
> I don't know if this the best way of doing this, but at my company we are
> working on
> a very simular problem, and what we do is actually lay down the
partitions
> in our
> %pre script. This allows us to examine the partition table, and do the
> right thing.
> Then we just have anconda lay down the filesystems that are part of our
> core
> platform, but not filesystems that are the location of the persistant
data.
>
> In case its not obvious, we simply pipe commands into fdisk to actually
> create or alter the
> partition table while in the %pre script.
Could you possible send some examples from your kickstart file so I may get
a better idea.
Rick
>
> Cheers...james
>
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/kickstart-list
