|
From: | C David Rigby |
Subject: | Re: [RULE] Structure of slinky filesystem/bin folder |
Date: | Sat, 20 Mar 2004 15:33:40 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312 Debian/1.6-3 |
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 lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 chown -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 cp -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 cpio -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 date -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 dd -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 df -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 echo -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 false -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 grep -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 gunzip -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 gzip -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 hostname -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 kill -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 ln -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 ls -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 mkdir -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 mknod -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 more -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 mount -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 mv -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 pidof -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 ping -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 ps -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 pwd -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 rm -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 rmdir -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 sed -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 sh -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 sleep -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 sync -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 tar -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 touch -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 true -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 umount -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 uname -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 vi -> busybox lrwxrwxrwx 1 rule rule 7 Mar 20 10:58 zcat -> busyboxSo, 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 iamge that you could download? I do not believe that Michael intended for the development tarball to be a "finished" release. Instead, it was the tool to allow us to build our own boot disks.
CDR M. Fioretti wrote:
Hello, I am downloading right now the content of the slinky_devel folder in David's server:http://rule-test.homelinux.org/~rule/rule-tool/Hoping to find the time to write some documentation. Now, downloading with wget yelds lots of copies of the same files, with different names: -rw-rw-r-- 1 marco marco 348540 Dec 11 2002 ash -rw-rw-r-- 1 marco marco 348540 Dec 11 2002 busybox -rw-rw-r-- 1 marco marco 348540 Dec 11 2002 cat -rw-rw-r-- 1 marco marco 348540 Dec 11 2002 chgrp -rw-rw-r-- 1 marco marco 348540 Dec 11 2002 chmod -rw-rw-r-- 1 marco marco 348540 Dec 11 2002 chown and so on. Maybe in the original structure there was only busybox, and lots of links to it with different names? Ciao, Marco Fioretti
[Prev in Thread] | Current Thread | [Next in Thread] |