Extension Development :: gnu-utils



Another BIG issue with gnu-utils...

Looks like a snapshot of /usr/X11R6/lib/X11 is included in gnu-utils.
Why? I don't have a clue. That has nothing to do with busybox. Likely a cude way to add some additional fonts?

Anyway, It has caused me much grief and I am cutting it from gnu-utils.

If it beaks some extensions, then post here and let me know.

BTW, a question for you font experts? Is there an easy way to see the fonts that a binary is going to be needing?

Perhaps a better method is to build an extension for adding fonts?
Quote (roberts @ May 05 2008,14:39)
Anyway, It has caused me much grief and I am cutting it from gnu-utils.

If it beaks some extensions, then post here and let me know.

Will do. (Actually, I was a bit surprised about the new size (1.2 vs 9) that I am used to seeing, when I downloaded it).

Anyway, quick question, is it necessary to run mkwritable when loading gnu-utils.dsl to a toram session?
Quote
is it necessary to run mkwritable when loading gnu-utils.dsl to a toram session?
Yes. All toram does is load the KNOPPIX file into ram; the directories that are read-only are still read-only.  Most of the directories are merely links to /KNOPPIX/* initially, regardless of whether you're running directly from CD or toram.  The mkwriteable script replaces these links with writable directories, and populates those directories with links to the individual files in /KNOPPIX/* directories.

If you wish to avoid mkwriteable, you must use extensions that do not write outside of /opt: uci, unc, or tar.gz
Quote (mikshaw @ May 08 2008,22:08)
Quote
is it necessary to run mkwritable when loading gnu-utils.dsl to a toram session?
Yes. All toram does is load the KNOPPIX file into ram; the directories that are read-only are still read-only.  Most of the directories are merely links to /KNOPPIX/* initially, regardless of whether you're running directly from CD or toram.  The mkwriteable script replaces these links with writable directories, and populates those directories with links to the individual files in /KNOPPIX/* directories.

If you wish to avoid mkwriteable, you must use extensions that do not write outside of /opt: uci, unc, or tar.gz

I ask because the update to gnu-utils script does it (calls mkwriteable, then mydsl-install), while reading through the mydsl-load it does not. (I save a copy of gnu-utils.dsl on my flash instead of redownloading it each time)


Edit: Actually it does. mydsl-load -> mydsl-install which calls mkwriteable.

So then a better question, why call mkwriteable twice? (Once in gnu-utils-restore, then again in mydsl-install)
Any .dsl calls that script whether from boot or on-demand mydsl loading of a .dsl. However, it is only actually performed only once. Look at said script, if previously run, it immediately exits.
Next Page...
original here.