Thread: where to start?
Status: Planning
Brought to you by:
lukisi71
From: Rainer P. F. <gor...@go...> - 2006-10-10 15:18:07
|
> i always write with little line > it's for the case where someone send long lines > anyway you find no options so there's no auto-wrapping > > this list is for Massix > and we speak about emails :) > what's new ??? > > i don't see nothing about devel Massix > things that we must test, ways we want, and all > or discutions are elsewhere ? > > -- > > THANKS && REGARDS > CIAO > KRISS I am afraid not that much new, we have to start somewhere, but no discussion yet. Do we want to write a new OS or do we want to put something on top of ... anything. What should it provide, and how could we achieve that? Which Problems do we see and which solutions. -- H CUH Rainer Peter Feller H |
From: kriss <chr...@al...> - 2006-10-10 18:34:40
|
> > Do we want to write a new OS or do we want to put something on top of > ... anything. i'm afraid we must have both the goal is to use material on all pc we have so we need to work on every os to begin linux is probably the best but the kernel will not be our friend finally to reach the goal we need to redo kernel parts i'm not enough documented to point the real problems in code we need real time acces on (block) devices without interruption for my understanding so Luca if i'm right we may design the roadmap in 2 subprojects : Massix interfaces (Linux, Bsd, window, ...) Massix os : the only os able to reach goals we want as i'm not the owner of the project and i'm not a real devel i will not go too far in what i imagine without your advises -- THANKS && REGARDS CIAO KRISS |
From: Luca D. <luc...@gm...> - 2006-10-11 12:49:17
|
Ok, I see that we have to do a bit of clarification about the goals of the project, as they were on my mind. I don't want to create a new OS. I simply want to use at the best of my possibilities the (already great) capability of a GNU/Linux system in particular the capabilities about network, remote execution, and so on. And I would like to create a distribution that makes it easy to do this. When I wrote about using material and devices on all machines of a network I was referring to a GNU/Linux network. The examples about a PlayStation were *provocatory* but perhaps misleading. Were they? The type of tools I was planning to use (well, a minimum) are shown in the web site at http://massix.sourceforge.net/goals.html especially under section "Technical info". I think that the first step could be: - create a bare LFS system which boots, mounts a NFS partition for most of the basic commands and for /home. - create a set of scripts that automate what we have done to achieve this. Afterwards, we can look at some enhancement, such as to choose the commands that we want to have in the local hard disk and those that could be placed in a remote partition. When we have a system that has the features described for massix (install once, use everywhere, see personal settings, ...) even for basic tools (such as those in LFS) we can go on with X Window. Comments? --Luca |
From: kriss <chr...@al...> - 2006-10-11 23:00:53
|
Luca > I don't want to create a new OS. I simply want to use at the best of > my possibilities the (already great) capability of a GNU/Linux system > in particular the capabilities about network, remote execution, and so > on. And I would like to create a distribution that makes it easy to do > a new distro is a new os ( the kernel is not os ) ok for only linux (there's a linux on playstation 2) to have better understanding yes we'll do what you say but the need to change kernel parts will come (i think) also don't give up too fast about using each pc material it will come in time what about x86-64 ? ( i only have one very noisy x86 and i can't use it for now, 3 x86-64 ) you speak about lfs (clfs ?) i think this time i'm clear maybe X can do more -- THANKS && REGARDS CIAO KRISS |
From: Luca D. <luc...@gm...> - 2006-10-12 08:45:38
|
On 10/12/06, kriss <chr...@al...> wrote: > a new distro is a new os ( the kernel is not os ) Ok. Then we will make a new OS. > but the need to change kernel parts will come (i think) I was thinking there was no need. I don't know for sure. > also don't give up too fast about using each pc material At the initial stage we'll try with a network of machines with any kind of architecture, but all running our OS. > what about x86-64 ? ( i only have one very noisy x86 > and i can't use it for now, 3 x86-64 ) you speak about > lfs (clfs ?) An LFS system can be built on a x86-64. Right? Why mention CLFS? In conclusion, I don't see (now) the need of a Massix-interface or 2 subprojects. --Luca |
From: kriss <chr...@al...> - 2006-10-12 09:11:16
|
> > > An LFS system can be built on a x86-64. Right? > Why mention CLFS? at lfs mailling-list they said that problem i had was due to the fact that lfs is for i686 and less they said that if i wanted a x86_64 system the only way is clfs > In conclusion, I don't see (now) the need of a > Massix-interface or 2 subprojects. me too --Kriss |