rule-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Michael Fratoni
Subject: Re: [RULE] Structure of slinky filesystem/bin folder
Date: Sat, 20 Mar 2004 10:23:52 -0500
User-agent: KMail/1.4.3

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 20 March 2004 09:35 am, M. Fioretti wrote:

> " BusyBox is a multi-call binary that combines many common Unix
> utilities into a single executable.  Most people will create a link to
> busybox for each function they wish to use, and BusyBox will act like
> whatever it was invoked as."
>
> Now the question is (if) how to recreate such links on the website,
> and in any related tarball, to decrease download size. This *is* less
> important than setting the CMS system up of course. Once we have a
> structure to quickly document what we are doing it becomes much easier
> for everybody to contribute and change things.
>
> Ciao,
>       Marco Fioretti

Hi Marco,
The development tarball (slinky_devel-0.3.97.tar.gz), when extracted as 
root, will create all needed symlinks and device files. (Only root has 
the permissions to create device files).

All of the rule files are still available here:
ftp://ftp.gnu.org/savannah/files/rule/slinky/
Use at your own risk, and verify MD5 sums, the old server was compromised. 
All accounts were reset in the process.
http://savannah.nongnu.org/forum/forum.php?forum_id=2752

I am currently trying to recreate my FSF account so that I can upload the 
files again to the http://savannah.nongnu.org/download/rule/slinky/ 
directory.

- -- 
- -Michael

pgp key:  http://www.tuxfan.homeip.net:8080/gpgkey.txt
Red Hat Linux 7.{2,3}|8.0|9 in 8M of RAM: http://www.rule-project.org/en/
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQFAXGIIn/07WoAb/SsRAtpAAKCijF1goL32RpoKzTTTBo1I+ea2/QCcD+Au
6yzqm0R0zzHqiByZhtmNMfE=
=UDA5
-----END PGP SIGNATURE-----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]