Bruce Platt wrote:
> [EMAIL PROTECTED] /home/root-export# rpm --initdb --root /home/root-export
> error: cannot open Packages index using db3 - No such file or directory (2)
> 
> Now, never having seen rpm actually used in such a way, and examining the
> rpm man page, I figured that this would create a new rpm database in
> /home/root-export.  Instead I got the error displayed above.

usually viper/anaconda does that behind the scenes for you..

> I then used this as an opportunity to install 3.0 on another box.  The above
> four steps worked fine, and I wound up with a "skeleton" system in
> /home/root-export.  Later in the Wiki post Morten suggests  "chroot
> /home/root-export" then some more package installs. This did not work as the
> swup installs failed due to failed dependency checks for various pam modules
> and various components of glibc.  I was surprised that the command swup

that is fixed by rpm --rebuilddb from the chroot environment - as the 
article now states..

> --root /home/root-export --install swup bash-static vim put alsmost an
> entire system in the /home/root-export tree.

that's the idea :) a shell, an editor and swup is basically all you need 
to start setting up a TSL box .. those three packages need a whole 
shitload of other stuff.. just take a look here:

http://84.234.141.4/base.png

> So, I am still scratching my head over this and some other aspects of my not
> being able to get my embedded system to recognize TSL, even though the
> pxeboot works fine and the custom bzImage I created transfers to the
> embedded box bit does not execute.

you lost me in the last part there.. pxeboot works, but bzImage doesn't? 
what errors did you get?

> I will provide more information as I work through all this.

Please do.. also feel free to edit the wiki if you catch something..

> Regards to all and thanks for being a great community.

we try :)

-- 
Morten
_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss

Reply via email to