Re: [RULE] Structure of slinky filesystem/bin folder

[C David Rigby]

Marco,
	I used slinky-v0.3.96 to install RedHat 9 on deepthought, the server 
that is hosting the test site.  But that required me to finish the 
process by downloading relevant update RPMs from a RedHat mirror, as 
well as initializing the RAID array by hand.  So what would be useful 
would be an already "up2date" RULE-based RH9 installer, all on a single 
CD.  In other words, a bootable CD that included the RULE installer and 
all of the needed RPMs all on the same disk, yes?  Do you know what your 
target system for the installation is?

	In other news, I am making my final comments on my previously-promised 
report on SPIP.  It has gotten rather long, so I am going to put it on 
the server and then post the link to the mailing list shortly.

CDR

M. Fioretti wrote:
> On Sat, Mar 20, 2004 15:33:40 PM +0100, C David Rigby (address@hidden) wrote:
>
> > Marco,
> > 	Yes, IIRC, that makes sense, since busybox is a single binary that 
> > handles all of the calls that would normally be separate files.  If I 
> > issue this command:
> >
> > ls -l public_html/rule-tool/slinky_devel/filesystem/bin
> >
> > I get this result:
> >
> > lrwxrwxrwx    1 rule     rule            7 Mar 20 10:58 ash -> busybox
> > -rwxr-xr-x    1 rule     rule       348540 Dec 11  2002 busybox
> > lrwxrwxrwx    1 rule     rule            7 Mar 20 10:58 cat -> busybox
> > lrwxrwxrwx    1 rule     rule            7 Mar 20 10:58 chgrp -> busybox
> > lrwxrwxrwx    1 rule     rule            7 Mar 20 10:58 chmod -> busybox
>
> [snip]
>
> > So, it seems that wget is following the links and getting the file
> > each time.
> >
> > Is there some particular portion of that directory structure that I
> > can tar/zip for you and include separately?  Or possibly I can
> > simply create here a slinky boot disk image that you could download?
>
>
> no need now, thanks. My primary purpose was to figure out again all
> the pieces of the puzzle, so we can document everything when spip or
> whatever is up and running. That remains the highest priority. What we
> have learned here is that we probably have to rebuild (after the
> website) a RULE developer kit in a tarball with just busybox and a
> scripts which recreates all the links. For the record, even the
> filesystem/sbin an filesystem/usr/bin folders are made like this, so
> the devel tarball could be much smaller.
>
> Contradicting myself: *if* you have time, after working on the
> website, I could really use a RULE ISO for Red Hat 9, with latest
> kernel from RH, for the install fest I'll attend to next saturday (see
> my other message here). I have the standard RH9 cdroms, and could ask
> some friend to download this one. Otherwise no problem, I'll have him
> download the slinky-something iso you already put online.
>
> Ciao,
>         Marco Fioretti