Tiny Core Base > Release Candidate Testing

tinycore_v3.8rc2

<< < (3/9) > >>

curaga:
Lee, what you're describing is almost what the busybox source tarball is ;)

make menuconfig && make && make install

gerald_clark:
Perhaps a complete busybox initrd would be preferable.
It would completely replace the one in base, and there would not be two copys present.

Lee:
@ curaga: You make it sound so easy that now I have to go play with it some.  :)

@ gerald_clark: I started down that path in my previous post then backed out that part because I always lean toward keeping the base intact - just a personal pref.

(an hour passes)

OK.  That -was- easy.  Read README and INSTALL from the busybox source tarball.  Loaded up compiletc.  Built busybox with just uuencode and uudecode (and a few others that looked interesting).

edit: corrected typo. 20110718 2146

ixbrian:

--- Quote from: gerald_clark on July 18, 2011, 12:58:52 PM ---Perhaps a complete busybox initrd would be preferable.
It would completely replace the one in base, and there would not be two copys present.

--- End quote ---

By complete busybox initrd, do you mean an extension?   If so, it probably would not be a good idea to have an extension (full BusyBox) replace functionality (BusyBox) in Core.   In my opinion this would be a recipe for problems down the road (for example if the extension BusyBox version, options, etc. where ever out of sync with the Core BusyBox)

Brian

floppy:
rc1
...
* Updated mnttool - added a refresh button.
...

My feedback:
- Refresh button: very good
- A bit disturbing: after boot, the mntool window is top right. By clicking "refresh", it jumps top left (over my conky window).

Navigation

[0] Message Index

[#] Next page

[*] Previous page