Hi all,
Thanx for the responses!
Not long after sending the first email I was looking on the sl304 CD and
found the comps.xml and pkgorder files. Using the comps.xml file I built
a list of necessary rpms using the core and base sections and then
ordered them using pkgorder.
Using:
rpm -ivh --nodeps --root /new-chroot package-blah-123.rpm
I built myself a system. Well, it became a system following multiple:
rpm -Va --root /new-chroot followed by more package installation,
followed by rpm -vA
--> well, you get the gist.
That worked fine except the base system ending up being something like
600Mb! (I think my debian system was something like 200Mb) A quick
google search turned up a heated debate as to why RH makes their base
system so big (which stopped me from writing to the list and complaining
about redhat ;-)
After looking around some more, I stumbled across rpmstrap. I gave it my
original minimal list (just the base and core rpms) and it died
spectacularly! Tried it again with my sanctioned, enormous (600 Mb)
package list and it worked. But, it didn't occur to me to try the centos
list. I'll give that a go and see how big their system is.
So, I have one question:
Is my base system about the correct size (what is expected)?
So that's my experience with building a base (or something like that)
SciLin (RH) system without using the gui.
Parents, tell your children not to try this at home! ;)
Thanx again,
Marco.
On Thu, 2005-08-04 at 11:27 -0500, Connie Sieh wrote:
> rpmstrap comes with centos3 and centos4 config files. I suggest that you
> just change the "mirror" locations of these as SL is compatible with
> centos3 and centos4. There are a few entries that have "centos" in the
> name that need changing. Just remove the "centos-" part.
>
> -Connie Sieh
> On Thu, 4 Aug 2005, John A. Goebel wrote:
>
> > ++ 04/08/05 10:50 -0500 - <Connie Sieh>:
> >
> > Hi,
> >
> > > And the "core" entry too.
> > >
> > > -Connie Sieh
> > > On Thu, 4 Aug 2005, Troy Dawson wrote:
> > >
> > > > Marco La Rosa wrote:
> > > > > Hi all,
> > > > >
> > > > > I was wondering if anyone has a list of packages (in the correct
> > > > > installation order) required to build a minimal, bootable Sci Linux 304
> > > > > system?
> > > > >
> > > > > I have found a software package called rpmstrap (google rpmstrap) which
> > > > > works like debootstrap but it requires a package list.
> > > > >
> > > > > Thanx in advance,
> > > > > Marco.
> > > >
> > > > A good start would be to look in the comps.xml file and get all the
> > > > rpm's in the section "base"
> > > > To be honest, I think you can actually take out some of even the base
> > > > one's, but I'm not sure which ones. But it's the best place to start.
> > > >
> > > > ftp://ftp.scientificlinux.org/linux/scientific/304/i386/SL/base/comps.xml
> >
> > Troy pointed to the 304 version. I just wanted to give you a heads-up if your
> > thinking about using 40x. Unless the SciLinux developers have changed the
> > comps.xml list to include tftp client, it's not included in the base or
> > anywhere else in the list. This will hurt you if you plan to do PXE boot since
> > the common scheme is to tftp a file, often called 'Kickstart_end', to indicate
> > the install is done and remove the hex link file so PXE is ignored and the
> > system boots locally.
> >
> > This bit me last night.
> >
> > Modifying and rebuilding the list isn't hard though.
> >
> >
> > John
> >
> > > > Troy
> > > >
> >
> > ##############################################
> > # John Goebel <jgoebel(at)slac.stanford.edu> #
> > # Stanford Linear Accelerator Center #
> > # 2575 Sand Hill Road, Menlo Park, CA 94025 #
> > ############################################ #
> >
|
