On Wed Dec 15 1999 at 23:30, Matt Wilson wrote:
> Sorry - I should have known the problem from inspection of your
> ks.cfg. Remove the /dev/ from each device. Also, --onpart only works
> for ext2 partitions.
Ahh, thanks again. This is the sort of doc that's missing.
However, it still doesn't
Sorry - I should have known the problem from inspection of your
ks.cfg. Remove the /dev/ from each device. Also, --onpart only works
for ext2 partitions.
--onpart was added for a very specific case and wasn't meant for
general consumption...
Matt
On Thu, Dec 16, 1999 at 12:38:46PM +1000, Tony
On Wed Dec 15 1999 at 21:19, Matt Wilson wrote:
> > (I can give you the traceback messages if you like).
>
> Please. The bottom has the most useful part, make sure to scroll down
> to get it all.
This is what I'm getting (apologies if there are any typos)...
Traceback (innermost last):
File "
> (I can give you the traceback messages if you like).
Please. The bottom has the most useful part, make sure to scroll down
to get it all.
Matt
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
On Wed Dec 15 1999 at 09:26, Matt Wilson wrote:
Thanks for the reply Matt...
> On Wed, Dec 15, 1999 at 01:03:35PM +1000, Tony Nugent wrote:
> > There is no real documentation describing the --onpart parameter, and
> > I was hoping to get a lot more control over how the disk partitioning
> > is
On Wed, Dec 15, 1999 at 01:03:35PM +1000, Tony Nugent wrote:
> First (quick) question:
>
> It is possible to get kickstart to set up raid partitions? If so, how
> is it done.
Not yet.
> Second question:
>
>
> I have in a kickstart file (rh61, updates included) specifying the
> following conf
First (quick) question:
It is possible to get kickstart to set up raid partitions? If so, how
is it done.
Second question:
I have in a kickstart file (rh61, updates included) specifying the
following config:
part /boot --size 8 --onpart /dev/hda1
part / -- size 1024 --onpart /dev/hda2
part /