[Rule-list] Slinky questions
Ed Blackman
rule-list at edgewood.to
Mon Aug 12 23:11:00 EEST 2002
On Mon, Aug 12, 2002 at 12:44:47AM -0400, Michael Fratoni wrote:
> http://www.tuxfan.homeip.net:8080/rule/slinky/build_scripts/
>
> They should give you a general idea of the process.
Thanks, I'll take a look later.
I've been playing around with Lua, and like it more the more I work
with it. The interpreter binary is 122k statically linked, not 77k
like I mistakenly said before. At that size, it will still fit on
disk1 without having to kick anything else off, though there's
precious little space left.
I do have some ideas on how to save space, some of which can be
implemented even without going to Lua.
- Extract rpm files (the binary and config files) from the rpm package
file, rather than including them on the disks. (Package files are
just cpio archives with a non-standard header, so you can extract
files from them without needing rpm installed.)
- Advantages:
- 40k savings on rootfs, 732k (!) savings on disk2
- No rpm version incompatibilities: the version in the rpm
package is always going to be the right one for that version of
Redhat.
- Disadvantages:
- Could be tricky locating the rpm package, given the differences
in version between Redhat versions, and the potential that users
have upgraded it.
- Loopmount RedHat/base/stage2.img from the first RH CD, use rpm from
there.
- Advantages:
- same as above
- easier to find reliably than the rpm package
- Disadvantages:
- Additional memory usage of one extra loopmount
- Load nfs modules (nfs, lockd, sunrpc) from disk2
- Advantages:
- Approx. 275k savings on rootfs
- Disadvantages:
- Some additional complexity in installer
- Strip parser from Lua binary. Lua executes a script by parsing it
to produce bytecode, then executing the bytecode produced. It's
designed to be embedded, though, so it's easy to eliminate the
parser and only use preparsed ("compiled") bytecode.
- Advantages:
- Approx. 40k savings on rootfs
- Approx 50-75% savings on each script
- Disadvantages:
- Bytecode isn't human readable or editable.
Thoughts?
Ed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://lists.hellug.gr/pipermail/rule-list/attachments/20020812/954b7620/attachment.pgp>
This full static mirror of the Run Up to Date Linux Everywhere Project mailing list, originally hosted at http://lists.hellug.gr/mailman/listinfo/rule-list, is kept online by Free Software popularizer, researcher and trainer Marco Fioretti. To know how you can support this archive, and Marco's work in general, please click here