jaromil,

thanks for the tip off on the 'mkusr' command.

what is the current activity of developing dynebolic? figurin out what to do
next? i spend way too much time tinkerin on the comp as it is so if there is
anything i can do to help let me know.

and as far as 2.5.2 --> 2.6 i've just been unpacking in 2.5 and repacking in
2.6. i have noticed that 2.6 attempts to automount all the modules it can
find, even on other partitions. for instance, my 2.5.2 dock is on a seperate
HDD than my 2.6 dock, yet it still finds and automounts them (it just
creates empty folders of the same name).

tyler

On Wed, Apr 21, 2010 at 10:48 PM, jaromil <jaromil@???> wrote:

> >
> hi Tyler,
>
> nice to read now and then that people is good busy!!
>
> i'm also quite active on FreeJ and... even on a new project that
> you'll soon hear about by the end of the year ;) something quite
> powerful, tailored for autonomous use in our different local
> communitites.
>
> but well back to our topic, when working with the 2.6 alpha please
> keep in mind this terrible problem of SquashFS 3.0 *not* being
> backward compatible with 2.0 (and 2.0 not even being available for
> latest Linux kernels...) which will probably prevent us from deploying
> it as it is. For *stable* developments that can be shared by our
> community and last in time, i recommend still using dyne:bolic 2.5.2
> to make new modules.
>
> said that, to unpack the dyne.sys you can still use dynesdk with the
> 'mkusr' command it will repack everything in your SDK.
>
> happy hacking :)
>
> ciao
>
> - --
> jaromil, dyne.org developer, http://jaromil.dyne.org
>
> GPG: B2D9 9376 BFB2 60B7 601F 5B62 F6D3 FBD9 C2B6 8E39
>
>
> > _______________________________________________
> dynebolic mailing list
> dynebolic@???
> http://lists.dyne.org/mailman/listinfo/dynebolic
>