Hi Jaromil,

In reference to my gmail's inbox:

--- (from    jaromil <jaromil@???>
reply-to    dynebolic mailinglist <dynebolic@???>,
to    bryan@???,
dynebolic mailinglist <dynebolic@???>,
date    Dec 10, 2007 1:05 AM
subject    Re: [dyne:bolic] RASTASOFT operating system - dyne:III GNU/Linux
mailing list    dynebolic.lists.dyne.org Filter messages from this mailing list
mailed-by    lists.dyne.org)

---You said: "also i hope that some developer of gnewsense likes to
get in touch on it and join us in brainstorming."

I've been using gnewsense to chroot into and gain access to
gnewsense-synaptic's nonproprietary universe repository.

I was 'dd-imaging' the gnewsense installed-system and placing the
image into a "dyne.nst"--deleting the gnewsense's kernel and cdrom
shortcut and stuff like that that dyne 'proc'esses would take over.

The chroot into gnewsense works so well with the Xfce integration.
However, I've been using gobuntu recently for 'chrooting' into only
because it seems that gnewsense's progress has frozen for quite some
time.

I've mostly worried that, when installing gnewsense and its automatic
updates, that some programs might depend on some kernel-update
versions that may exceed the working kernel-version that I'm using in
dyne.

I've considered the Idea of getting synaptic into dyne and, ideally,
having a script automatically takeover for 'dyneconfiguring' and
squashing the packages into modules.

Or alternatively, a 'gnewsense-module' can be dropped into the
modules-folder, and invoked to build a 'gnewsense chroot-system'--for
building itself; to the 'current' 'working-dyne-kernel'.

Jaromil, thanks to The Cosmos for you, and to you, thanks for Dyne!!!


#############################################################
#############################################################


On Dec 10, 2007 1:05 AM, jaromil <jaromil@???> wrote:
> >
>
> hi Bryan,
>
> On Thu, Dec 06, 2007 at 12:33:22PM +0100, Bryan wrote:
> > Hi Jaromil et. al,
>
> first of all thanks for the precious suggestions you sent me in
> private during the last months of development, they have been useful
> and your name is actually missing from the (hard to mantain) list of
> contributors, so mentioning it here is the minimum i can do now.
>
> > You have hinted before on revamping dyne and that that should be the
> > core of dyne:III. Also you mentioned (on/offline/irc?) that you are
> > looking for a different development model. Combining all this
> > together, together with the donation programme, I suspect you do
> > have a plan.
>
> i have a plan, but it is still in the making. i'm also coordinating
> with the pure:dyne developers and we agreed that we will spend the
> coming 3 months to research on it and define something only after this
> period. also i hope that some developer of gnewsense likes to get in
> touch on it and join us in brainstorming.
>
> > Care to share it? That way I, and I suspect many others, can see
> > where we can help out building, creating, steering etc as well.
>
> i'll do my best to share it in the coming weeks, at least share what i
> have formulated so far in my mind and talked with some people around.
> but let me suggest we use another mailinglist for these speculations,
> may them lead or not to a dyne:III (or dyne:3?) release i'd prefer to
> not disturb the mantainance of dyne:II which is definitely more
> important at the moment.
>
> for the purpose of early discussion on the topic i opened the dyne3
> mailinglist (still silent as of today) that you are welcome to join.
> i forgot the subscription url at the moment while writing this email
> offline, so have a look on the gnewsense forum with a search for dyne3
> and you'll find it there.
>
> > O so looking forward to your ideas...
>
> thanks!
>
> on a quick note, some of my opinions:
>
> an important aim of dyne:3 should be to solve the issue of different
> binary architectures. my approach will be to hook up (support with
> compatibility) binary packages from various distros to inherit as much
> as possible from existing efforts.
>
> as they say in Asia: Unity in Diversity.
>
> another aim should be to make our effort sustainable by enlarging the
> core group of developers and distributing the tasks, while for that
> the maintainance of dyne:II should be already a good start.
>
> ciao
>
> - --
> (_ http://jaromil.dyne.org _)
>
>
> >
> _______________________________________________
> dynebolic mailing list
> dynebolic@???
> http://lists.dyne.org/mailman/listinfo/dynebolic
>