Subject: | |
From: | |
Reply To: | |
Date: | Tue, 11 Jan 2005 12:29:02 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Hi Dashamir
We are able to install RAID with kickstart and SL3.03. We use a combination
of RAID1 and RAID0. Here are the relevant sections of my ks file.
It creates a /boot with raid1, / with raid0, and
/export/u10 with raid0.
clearpart --all --initlabel
part raid.00 --size 256 --ondisk sda
part raid.01 --size 256 --ondisk sdb
part swap --size 2048 --asprimary --ondisk sda
part swap --size 2048 --asprimary --ondisk sdb
part raid.10 --size 2048 --ondisk sda
part raid.11 --size 2048 --ondisk sdb
part raid.20 --size 1 --grow --ondisk sda
part raid.21 --size 1 --grow --ondisk sdb
raid /boot --level 1 --device md0 --fstype ext3 raid.00 raid.01
raid / --level 0 --device md1 --fstype ext3 raid.10 raid.11
raid /export/u10 --level 0 --device md2 --fstype ext3 raid.20 raid.21
Eric
-----Original Message-----
From: [log in to unmask]
[mailto:[log in to unmask]]On Behalf Of
Dashamir Hoxha
Sent: Tuesday, January 11, 2005 1:56 AM
To: csieh
Cc: [log in to unmask]
Subject: Re: Kickstart file
I think that it is a bug too.
I have also noticed some problems with disc partitions.
Initially they are commented and this is obviously by design.
Then I uncomment them and modify them in order to use the
existing partitions, but it doesn't work. There is always some
kind of error message and I never managed to do a re-installation
totally automatically. I comment the partition instructions in ks.cfg
and during installation select the partitions manually. I have two
disks in my server and I am trying to use RAID1, and maybe this
makes things a little bit more complicated for the kickstart file.
In general, I don't like the policy of protecting the user from himself.
The default assumption in Linux/UNIX is that the user knows
what he is doing.
On Tuesday 11 January 2005 02:26, csieh wrote:
> Dashamir,
>
> On Sun, 9 Jan 2005, Dashamir Hoxha wrote:
> > Hi,
> >
> > I am using SLC303 for my workstations and servers. Usually, after making
> > an installation, I backup the file anaconda-ks.cfg (and any other config
> > files that I have touched), so that I can re-install the server easily
in
> > case of disaster or in case of making another similar installation.
> >
> > But I have noticed that anaconda does not reckognize the format of the
> > file that it has generated itself. First, it does not save the method of
> > installation (url --url http://...). Second, it does not reckognize
> > firewall --enabled --port=httpd:tcp (it should be firewall --enabled
> > --httpd).
> >
> > It is not hard to fix it by hand, but I just wonder: is it a bug or
> > rather it is by design?
>
> I suspect it is a bug.
>
> -Connie Sieh
>
> > Dashamir
|
|
|