Porteus/Arch aka Sensei (Porteus w/pacman package manager)

[brokenman]

heh. BrokenArch. Is that a dig?

[Ed_P]

heh. BrokenArch. Is that a dig?

Not at all.

Brokenman + Arch Linux = 1st part of Brokenman + 1st part of Arch Linux = BrokenArch

[francois]

AMI Archlinux Module Installer

[stifiling]

first name comes to mind for me is..."Nemesis"

[neko]

@stifiling

My how to convert "64bit ISO" to "32bit ISO".

1.Sensei-v3.1-i486.iso@/boot/syslinux/initrd.xz,vmlinuz
Sensei-v3.1-i486.iso@/porteus/base/000-kernel.xzm
are gotten from upkernel command.
And the "/lib and /sbin" directories of 000-kernel.xzm were changed on ArchLinux format.

"upkernel" command is included in upkernel-3.18.21-noarch-3.xzm.
http://forum.porteus.org/viewtopic.php? ... 788#p34856
Also This article explains how to build kernel.

2.Sensei-v3.1-i486.iso@/porteus/base/001-core.xzm
are constructed from the packages that were gotten by archpkgs using 64bit's list.
The 64bit's list was gotten from
"Sensei-v3.1-x86_64.iso@/porteus/base/001-core64.xzm@/var/lib/pacman/local/".
And contents of some packages were reduced as same as 64bit.

There are all package informations in
Sensei-v3.1-i486.iso@/porteus/base/001-core.xzm@/var/log/packages/

"archpkgs" is included in archspm-15.09.27-noarch-2.xzm.
http://forum.porteus.org/viewtopic.php? ... 997#p36687

3.Sensei-v3.1-i486.iso@/porteus/base/001-core_sensei-v3.1.xzm
were copied from 64bit except ArchLinux packages.
And binary entities were replaced by ones of "Porteus v3.1 32bit".

On this operation, "/var/lib/pacman/local/" were not copied.

There are all package informations in
"Sensei-v3.1-i486.iso@/porteus/base/001-core_sensei-v3.1.xzm@/var/log/packages/".


Thanks.

[francois]

@stifiling:

Nemesis is a great name for a new OS. It has a lot of meaning, including the one that you meant to give. Which was?

synonyms and analogs:
http://www.thesaurus.com/browse/nemesis

Personally, I like nemesis in terms of destiny, fortune, predestination ...

wikipedia english:
https://en.wikipedia.org/wiki/Nemesis_(mythology)

Great name.

[stifiling]

yea i like that name. think it sounds slick, cool, dark, and holds a powerful meaning.

only issue w/"BrokenArch" is it sounds like one of those systems where it's developed broken by design, and we know it's broken, and we're testing it as broken. similar to like ReactOS...or as if maybe we're using the GNU Hurd kernel or something.

[francois]

I think that brokenman was serious when replying to Ed's suggestion. brokenman as an alias is great, and even brokenman and stifiling have given birth to nemesis looks good. But broken OS

This with all my respect to you Jay.

But more seriously Nemesis, this arch linux clone, could be an interesting way to get familiar with systemd and to see how modularity could improve the performance and accessibility of a distribution with a great variety of packages an pkgbuild.

[Rava]

You all know that most free software pals like irony and such.

So, choosing "Broken OS" for an OS known for its stability and non-broken-ness would be quite in-universe with that irony themed naming, like "Lame ain't no MP3 encoder" or such...

[brokenman]

I love the name nemesis! Very powerful. There is a package injection tool with this name. It also has a relation to arch as in "Lex Luthor is superman's arch-nemesis". I also like the name "enemy" and "JaX" just another X. In any case stiffling, please join the bitbucket and I will create your access. Since you gave birth to arch porteus and have the most experience it stands to reason that you should lead the charge.

Francois, your reasoning about getting to know systemd is precisely why I decided to do this. If you can't kill the beast you'd better tame it.

[Rava]

I am also in favour of Nemesis.

[brokenman]

Reminds me of the comic.

[Rava]

^
For me, negative. Archie is not really... trusty robust OS material, in my book..

[ncmprhnsbl]

Please stay on topic, folks, this thread is way long already...

[francois]

Understood!