[BusyBox] Busybox- tutorial needed for installing -- modules ??

John van Vlaaderen john-at-thinman at nyc.rr.com
Sun Jan 26 12:07:03 UTC 2003


Hi,

Thomas Cameron wrote:
 >Perhaps, if a site existed
 >to act as a repository for BusyBox modules, it would make this sort of 
thing
 >easier, as users could pick and choose from said repository

What do you mean by modules ??   Just add linux ??  Ooooo a website 
cross compiles it for you, you untar it, switch the root and kexec... ??

I drifted into this list because I have been fooling around w/ 
Devil-Linux which uses some busybox/uClibc in its Initrd bootup.

I have a resonably stable iMac here, so to be running yellowdog linux.  
It is behind a cable modem and redirected from hypermart.net -- this 
works pretty well despite breaking a whole lot of corporate rules.

My parents, who host the data center, have only pulled the plug once in 
as many financial quarters.  And a surprising number have downloaded my 
eLSD bz2 files.

The eLSD architecture dictates a small Linux, possibly now 
busybox/uClibc in a LinuxBIOS matirx, with an /opt directory supplying  
gcc kernel and opensource/GNU compiling tools.

All applications, be it uClibc or not, are compiled on board and go into 
/opt/<app_name> where those app directories mimic linux/unix file 
structures -- bin,sbin,etc, etc, etc.  Config files are linked from the 
app's etc directory to /etc.  Devil Linux keeps its /etc on a floppy 
(for its firewall role) and will soon be able to pull it down from https 
for other lesser roles.

eLSD will extend this by also allowing apps to be loaded the same way 
and optionally stored on some old pair of disks containing mirrored LVM 
Reiser filesystems along with the huge swap volume (unlike ramdisks, 
vritual filesystems just page out to disk).  Network block devices look  
mighty inviting as well.

Now I would like to extend my DL evolution, called eLSD,  to be uClibc 
only, and return to my perl roots since no other language satisfies the 
OS admin in me.  I have been out of the loop since October, so much so 
that I didnt even notice the Oct DOW slide -- deeper than 9/11/2000 and 
Jul 2002 --

I can't imagine even imagine the depth of the slide when Busybox/uClibc 
Linux renders all other computing enterprise obsolete.  It will be total 
capitulation where the perls of knowledge replace the federal reserve as 
america's primary asset.  Save your pennies and busyboxtops -- mansions 
and yachts will suddenly become affordable even to us geeks.


On Saturday, January 25, 2003, at 11:36 PM, Thomas Cameron wrote:

> Hello all,
>
> 	I think that once things start to settle down with development of 
> the two
> components in question (busybox and uClibc), there will be more of an 
> effort
> on documentation.  Currently, things are changing on a daily basis in 
> CVS for
> BusyBox, and uClibc has not reached binary compatibility.  I think that 
> by
> the time uClibc has reached "1.0" status, things will be much easier to
> document.
>
> 	As far as BusyBox is concerned, I have no idea when things would 
> settle down.
> I think there will eventually be a critical point, where no further 
> module
> inclusion (generally speaking) would be needed.  Perhaps, if a site 
> existed
> to act as a repository for BusyBox modules, it would make this sort of 
> thing
> easier, as users could pick and choose from said repository.  I would
> personally offer the space, but right now I do not have the necessary
> bandwidth, or a stable enough server setup.
>
> 	Anyway, these are just my thoughts.  I'm certainly no authority, but I
> figured I'd just throw the thoughts out there.
>
> Good Luck,
> Thomas Cameron
> CEI Systems, Inc.
>
>
> On Saturday 25 January 2003 12:53 pm, John van Vlaaderen wrote:
>> Hi -- I have been lurking, my last admin work w/ busybox/uClibc was in
>> early October.  I took a long drive around the US to relieve lingering
>> symptoms from PTSD from working at the WTC disaster the day of the
>> attack.
>>
>> Since then there have been remarkable strides in the LinuxBIOS 
>> field.  I
>> have been concentrating on Initrd as part of my work for the 
>> Devil-Linux
>> project, but LinuxBIOS seems to be making Initrd obsolete.  Initrd - rd
>> for ram disk - is showing its age - should be virtual file system - yet
>> it is key to booting Linux.
>>
>> Creating sophisticated tutorials for both Initrd and LinuxBIOS, I
>> believe, is key to recruiting testers to assure that busy box (and
>> uClibc, I suppose) dont miss out on key testing.
>>
>> Furthermore, many people on the busybox and uClibc lists seem 
>> interested
>> in evoloving  new OSs from linux, I see these two projects key to
>> initiating the process.
>>
>> It has been slow going, but I am building a semi-portal to support 
>> these
>> kinds of projects.
>>
>> John
>>
>>
>> On Saturday, January 25, 2003, at 07:01 AM, Nick Fedchik wrote:
>>
>> On Sat, 25 Jan 2003, Andrew Sim wrote:
>>
>>      Hi all, I am looking for a updated tutorial to install and
>>      run busybox.
>>      I downloaded busybox and I think i didnt managed to get it
>> work.
>>      because when i type mksf.minix --> command not found.
>>      Anyway how u tell if it really been install properly ?
>>
>> BTW: I also has no usage messages for
>> fsck.minix
>> mkfs.minix
>> start_stop_daemos
>>
>> IADM, it's depends on applet.h/usage.h declarations, namelly by
>> '_' symbol.
>>
>> But after clear recompiling of latest code, it's still have a
>> place for
>> [root at fusion sbin]# ./pivot_root
>> BusyBox v0.61.pre (2003.01.25-11:29+0000) multi-call binary
>>
>> Usage: busybox [function] [arguments]...
>>     or: [function] [arguments]...
>> ...
>>
>> and
>> [root at fusion bin]# ./dpkg-deb
>> dpkg-deb: (null): Bad address
>>
>> Any ideas?
>
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/mailman/listinfo/busybox
>
>
  CXN, Inc. Contact: john at thinman.com
President, The Linux Society
http://groups.yahoo.com/group/linux-society
linux society distro -> http://www.thinman.com/eLSD/readme
ThinMan is a registered trademark of CXN, Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 5925 bytes
Desc: not available
Url : http://lists.busybox.net/pipermail/busybox/attachments/20030126/9a80a110/attachment-0001.bin 


More information about the busybox mailing list