On Tuesday 04 November 2008 18:48, you wrote: > Thank you for the explanation! > I regret to say that I don't have enough storage on my laptop disk for > two root filesystem copies, so it would be very hard for me to migrate > into this kind of setup.
probably my last mail was somewhat unclear. You do not need to maintain two root filesystems. It is enough to have a clean t2-tree (which is not too big) in your root filesystem and use scripts/Emerge-Pkg in order to add new packages. You can remove installed packages using mine -r. In /var/adm you will find all metadata related to the installed system. If for some reason (e.g. a lot of failed builds, or many source-tarballs) the t2-tree gets to big you can use scripts/Cleanup to reduce the size of the t2-subdir. Sorry, for having been a bit unclear in my last mail. -- Lars > > However, I will try to see if it fits to my embedded needs. > > Thank you, > Alon. > > On 11/4/08, Lars Kuhtz <[EMAIL PROTECTED]> wrote: > > On Tuesday 04 November 2008 13:13, Alon Bar-Lev wrote: > > > Thank you for quick response! > > > > > > If I understand correctly it means that I have two copies of root file > > > system, one of my workstation and the other the target of the build. > > > Am I right? > > > > In principle, yes. Once you have installed the system on your > > workstation, you can delete the build and you can still manage your > > system via the Emerge-Pkg script. In order to do so all you need is a > > t2-tree within the system on your workstation. (I think, there is an > > option that includes the matching t2-tree as a package into your build > > such that it is installed into the target system.) > > > > I usually prefer to keep the original build. In case I want to update > > the system I do it within the original build. I can then test the results > > first before I apply the changes onto my workstation. (On can simply > > chroot into the result of the build.) Moreover, I allways have the config > > updated. This way the next time when I a do a build from scratch I > > already have an up to date config. > > > > > Also I don't quite understand where the metadata of installed files > > > resides, does the package manager know which files to remove? > > > > The metadata is stored under /var/adm in the rootfs of both systems, the > > build-target and the image generated from the build-target (actually the > > system in the image is a clone of the target of the build). > > > > > Thanks! > > > Alon. > > > > > > On 11/4/08, Lars Kuhtz <[EMAIL PROTECTED]> wrote: > > > > Hi Alon, > > > > > > > > indeed, you can manage a standalone desktop machine. Usually you > > > > start with a target-build (e.g. the desktop target) that bootstraps > > > > a new system. Once you have installed that system (via some kind of > > > > output image or directly via cp, mv, etc.) you can either use the > > > > Emerge-Pkg script to build packages directly into the running system > > > > or you can incrementally modify the original build and synchronize > > > > (via binary packages, rsync, etc) with the running system. > > > > > > > > Regards, > > > > Lars > > > > > > > > On Tuesday 04 November 2008 12:12, Alon Bar-Lev wrote: > > > > > Hello, > > > > > > > > > > I am Gentoo user and former developer (crypto & mobile herds). > > > > > > > > > > I got a reference to your project recently, I was amazed that I > > > > > did not knew it earlier... > > > > > > > > > > It looks a great piece of work! > > > > > > > > > > I read the documentation and the FAQ, and did not quite > > > > > understood one major fact, I will appreciate if some one can > > > > > help. > > > > > > > > > > Can the package management manage (Install, remove, update) > > > > > packages on root filesystem? > > > > > > > > > > I read that the package management can create various output > > > > > images and it is great for some of my embedded scenarios... But > > > > > can it be used to manage standalone desktop machine? > > > > > > > > > > If there is documentation for this please refer me. > > > > > > > > > > Thanks, > > > > > Alon Bar-Lev. > > > > > > > > > > ----------------------------------------------------------- > > > > > > > > > > If you wish to unsubscribe from this mailing, send mail to > > > > > [EMAIL PROTECTED] with a subject of: unsubscribe t2 > > > > > > > > ----------------------------------------------------------- > > > > If you wish to unsubscribe from this mailing, send mail to > > > > [EMAIL PROTECTED] with a subject of: unsubscribe t2 > > > > ----------------------------------------------------------- > > > > If you wish to unsubscribe from this mailing, send mail to > > [EMAIL PROTECTED] with a subject of: unsubscribe t2 ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe t2
