Repositories
paloxena
Main repository (everything needed for kernel development)
-
Cloning this repository:
git clone git://gitorious.org/paloxena/paloxena.git paloxena cd paloxena
Add this repository as a remote to an existing local repository:
git remote add paloxena git://gitorious.org/paloxena/paloxena.git git fetch paloxena git checkout -b my-local-tracking-branch paloxena/master_or_other_branch
newlib
The newlib for Paloxena
-
Cloning this repository:
git clone git://gitorious.org/paloxena/newlib.git newlib cd newlib
Add this repository as a remote to an existing local repository:
git remote add newlib git://gitorious.org/paloxena/newlib.git git fetch newlib git checkout -b my-local-tracking-branch newlib/master_or_other_branch
kernel2
A new version of Paloxena, let’s see if it becomes something good. Modules (running in userspace), SMP, threads and other cute stuff like that would be nice.
It looks like if this kernel gets very Unix-like—the syscalls will be the same as those of Linux. To use the OS, you’ll need to fetch the PPP repo (“Paloxena’s Patched Packages”). You build all packages there (“./build.sh build-env” and then “./build.sh build packages/[package-name]”) and after you've done that, you can compile paloxena2 via “make image-floppy-ppp” which will ask you for the path to ppp.
more…
If you want to build paloxena2 with µsh and ls:
$ git clone git://gitorious.org/paloxena/kernel2.git
[…]
$ git clone git://gitorious.org/paloxena/ppp.git
[…]
$ cd ppp
$ ./build.sh build-env
[…]
$ ./build.sh build packages/ush
[…]
$ ./build.sh build packages/ls
[…]
$ cd ../kernel2
$ make image-floppy-ppp
[…]
Path to ppp? ../ppp
[…]
And there will be a floppy disk image in ./build called “floppy.img”.
-
Cloning this repository:
git clone git://gitorious.org/paloxena/kernel2.git kernel2 cd kernel2
Add this repository as a remote to an existing local repository:
git remote add kernel2 git://gitorious.org/paloxena/kernel2.git git fetch kernel2 git checkout -b my-local-tracking-branch kernel2/master_or_other_branch
ppp
Paloxena’s Patched Packages is a package system for paloxena2 to build packages with a foreign origin—those packages are not necessarily ported, it’s enough to use the diet libc (i. e. µsh is not ported but it uses this libc).
-
Cloning this repository:
git clone git://gitorious.org/paloxena/ppp.git ppp cd ppp
Add this repository as a remote to an existing local repository:
git remote add ppp git://gitorious.org/paloxena/ppp.git git fetch ppp git checkout -b my-local-tracking-branch ppp/master_or_other_branch
kernel3
Yet another version of paloxena. This should finally achieve the goals set by paloxena2 (SMP, threads, etc.).
The branch named “streams” introduced some kind of rewrite, especially for the VFS and driver interface. Thus, the current version is called paloxena3.5.
-
Cloning this repository:
git clone git://gitorious.org/paloxena/kernel3.git kernel3 cd kernel3
Add this repository as a remote to an existing local repository:
git remote add kernel3 git://gitorious.org/paloxena/kernel3.git git fetch kernel3 git checkout -b my-local-tracking-branch kernel3/master_or_other_branch
ppp35
Paloxena’s patched packages for paloxena3.5.
-
Cloning this repository:
git clone git://gitorious.org/paloxena/ppp35.git ppp35 cd ppp35
Add this repository as a remote to an existing local repository:
git remote add ppp35 git://gitorious.org/paloxena/ppp35.git git fetch ppp35 git checkout -b my-local-tracking-branch ppp35/master_or_other_branch
kernel4
Well, yet another approach.
-
Cloning this repository:
git clone git://gitorious.org/paloxena/kernel4.git kernel4 cd kernel4
Add this repository as a remote to an existing local repository:
git remote add kernel4 git://gitorious.org/paloxena/kernel4.git git fetch kernel4 git checkout -b my-local-tracking-branch kernel4/master_or_other_branch
