Make a 20MB /boot partition and you're troubles will go away. The installer
recognizes that /boot should be put on a primary partition, as close to the
front of the disk as possible, which (except in really extreme examples)
keeps your kernel under the 1024 cylinder limit. If you're going to bui
On Thu, Jun 29, 2000 at 03:01:42PM +0200, R.I.Pienaar wrote:
>
> It all works great but i have run into a bit of a problem, in the base in the
> comps file i have chkconfig and other needed stuff, but for some or other
> reason it doesnt install the base prior to other rpms. My apache rpm for
>
On Wed, 5 Apr 2000, Vilius Puidokas wrote:
> hi,
> i've been folowing kickstart for a while lately..
> according to RH the bug with partitioning was fixed (or at least bug
> was closed on bugzilla), by adding --onpart. I checked installation code
> (one of the pre6.2) it doesn't look like --onp
On Wed, 5 Apr 2000, Anne POSSOZ wrote:
> Hi,
>
> What is the redhat list where kickstart issues are discussed?
> Do we have only one? Could we get on only on that matter?
There's '[EMAIL PROTECTED]' which focuses only on this topic..
>
> We have kickstart running now for redhat 6.0 on our camp
hi,
i've been folowing kickstart for a while lately..
according to RH the bug with partitioning was fixed (or at least bug
was closed on bugzilla), by adding --onpart. I checked installation code
(one of the pre6.2) it doesn't look like --onpart can solve this
problem:
if onPart:
Hi,
What is the redhat list where kickstart issues are discussed?
Do we have only one? Could we get on only on that matter?
We have kickstart running now for redhat 6.0 on our campus.
We want to prepare it for redhat 6.2.
Dedicated discussion on that matter would be welcome to
share all kind of
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
12 matches
Mail list logo
