I was doing an Internet facing server reload for a client today and he mentioned that there is a minimal install selection somewhere and that I should take a disk 1 of centos 4.4 and it would be under custom
Is this the case?
How?
I couldn't find it, nor could he after the fact.
If it exists, where is it, or how do I get to it for future reference please?
I usually use a centos server cd myself. :-)
Thanks and kind regards!
- rh
-- Robert - Abba Communications Computer & Internet Services (509) 624-7159 - www.abbacomm.net
On Tue, 2006-09-05 at 13:25 -0700, Email Lists wrote:
I was doing an Internet facing server reload for a client today and he mentioned that there is a minimal install selection somewhere and that I should take a disk 1 of centos 4.4 and it would be under custom
Is this the case?
How?
I couldn't find it, nor could he after the fact.
If it exists, where is it, or how do I get to it for future reference please?
I usually use a centos server cd myself. :-)
Thanks and kind regards!
- rh
It is there on graphical installs ...
On text installs it is:
All visible groups unchecked ... should be ~600-800mb on i386 ...
-> > -> It is there on graphical installs ... -> -> On text installs it is: -> -> All visible groups unchecked ... should be ~600-800mb on i386 ...
Thanks!!!
That figures since I mainly use
linux text nousb nousbstorage skipddc
installs.
- rh
-- Robert - Abba Communications Computer & Internet Services (509) 624-7159 - www.abbacomm.net
Johnny Hughes wrote:
On Tue, 2006-09-05 at 13:25 -0700, Email Lists wrote:
I was doing an Internet facing server reload for a client today and he mentioned that there is a minimal install selection somewhere and that I should take a disk 1 of centos 4.4 and it would be under custom
It is there on graphical installs ...
On text installs it is:
All visible groups unchecked ... should be ~600-800mb on i386 ...
It can go even lower if doing kickstart install. Define packages section as:
%packages --nobase
By default, core and base groups of packages are always installed. The "--nobase" option tells Anaconda not to include base group. You can add things you need later on.
Aleksandar Milivojevic napsal(a):
It can go even lower if doing kickstart install. Define packages section as:
%packages --nobase
By default, core and base groups of packages are always installed. The "--nobase" option tells Anaconda not to include base group. You can add things you need later on.
Yes, as mentioned Aleksandar, stick with kickstart. For servers I also use this within ks:
yum -y remove \ apmd \ atk \ bluez* \ cups \ desktop-file-utils \ diskdumputils \ gtk2 \ htmlview \ irda-utils \ isdn4k-utils \ keyutils \ lksctp-tools \ mgetty \ minicom \ mt-st \ nano \ nc \ netdump \ NetworkManager \ nfs-utils \ nscd \ OpenIPMI* \ pango \ pcmcia-cs \ pinfo \ portmap \ psacct \ rdist \ rmt \ rsh \ sendmail \ setserial \ specspo \ statserial \ stunnel \ system-c* \ talk \ up2date \ wireless-tools \ wvdial \ xinetd
You might have to change the list a bit. Regards, David
David Hrbáč wrote:
Aleksandar Milivojevic napsal(a):
It can go even lower if doing kickstart install. Define packages section as:
%packages --nobase
By default, core and base groups of packages are always installed. The "--nobase" option tells Anaconda not to include base group. You can add things you need later on.
Yes, as mentioned Aleksandar, stick with kickstart. For servers I also use this within ks:
yum -y remove \ apmd \ atk \ bluez* \
Hmmm.... You know, you could also list packages you want to exclude in %packages section by prepending them with dash. Something like
%packages --nobase -apmd -atk -bluez
... etc ...
The only downside is, if package is required by something else that gets installed, it will be reincluded (while yum method will also remove the dependency).
Hmmm.... You know, you could also list packages you want to exclude in %packages section by prepending them with dash. Something like
%packages --nobase -apmd -atk -bluez
... etc ...
The only downside is, if package is required by something else that gets installed, it will be reincluded (while yum method will also remove the dependency).
That's why I prefer to use yum. Removes packages with dependencies. :o) But I can change our ks's to include:
%packages --nobase
....
yum remove ...
Maybe we can shorten install time. :o) David
-
Aleksandar Milivojevic -
David Hrbáč -
Email Lists -
Johnny Hughes