Porteus

Hello!
I have installed Nemesis and updated it using setup-pman and pacman -Syu (because for some reason pman -Syu didn't really work after all the installation process)
I really like the modularity of packages, but that doesn't seem to work very well with arch packages because everything must be updated for new packages to work.

Everything works if I boot from the graphical entry (except very slow), and copy2ram only gives me the fresh system.

So, I wish to make the "fresh system" the updated system with the things I installed. How to do that?

I might be doing something wrong, so sugestions are very welcome!

Thanks!

Good that you got to a functional system. Nemesis is in development. Presently, it has stopped to permit the main developper brokenman to work on the slackware/porteus version of this forum.

Istinjazz is the right guy to get info presently. He is from manjaro and has done some testing on nemesis, and seems quite enthusiastic about nemesis. See:

Many threads are from him in the Nemesis section.

He might be the right guy to answer your question. And to discuss of some of the issues with nemesis, Just wait for the man or send a PM.

Or maybe you just want to transform the persistent changes into a module which could become with the other modules your fresh system. And from there build with pman?

In this case, I might be your man.

Especially, that I would appreciate your updated system.

Are you on linux file system or fat32?

Vonverting changes to a module is good! It might take forever though :p
Let's proceed with that.
I'm using ext4.

Might be worth a try. It depends on the size of the file. Sorry that you did not used ext2 in the first place.

This is all I can offer now. Istinjazz might know better.

Whats the problem with ext4?
How I do that? dir2xzm changes modules/update.xzm?
Experience of doing that?
- It doesn't take forever. It's reasonably fast.
- Things are persistent as they should.
- Some minor issues with duplicate database. I'll try to fix them and see what happens

Once satisfied or before the system breaks you can transform the /porteus/changes folder into a module with /usr/local/bin/dir2xzm
example:
cd /porteus/changes
dir2xzm yourchangefolder nameofmodule.xzm

Yep I did that
It worked!

Some remarks:
- I had to write a python script to remove the duplicates (they were a lot)
- Packages that are no longer needed as the time goes don`t get deleted and have to be manually removed (upower-pm-utils libdbus)
- After that system updates are a lot faster (10 packages or so instead of 300+)

This is a workaround. A better solution would be to update the "base" system as the user updates and not appending new things.

What about this?

Hi, Will.
Nemesis have a bug with dcadec.
For correcting updating packages of Nemesis you are need to run these commands:

Posting your updated nemesis change folder as a xzm module on mediafire or the sort would be appreciated.

I could upload it but I have custom software installed. The update.xzm is about 1gb. :p
If someone explain how to make that base system .xzm I can make an updated version of it. Or even a script to update it for new users so Nemesis can be more useful.

To decompress each unit of base do: Packages are located at:
/mnt/sda5/1_nemesis/porteus/base/002-gui/var/lib/pacman/local/

To rebuild modules:
dir2xzm /path/dir /path/dir.xzm

or look at:
http://www.porteus.org/component/conten ... udies.html