On Wed, Feb 25, 2004, Stephan Buys wrote:

> Hi all,
> 
> We are interested in creating a "LiveCD" for the Kolab server and I was 
> wondering what the absolute minimum system requirements would be to get
> OpenPKG running? And possibly run most of your distributions' functions
> from within OpenPKG.
> 
A "LiveCD" will not be easy to create. The %{l_prefix}/var directory
must be writable. Because nobody I know of has ever tried running
OpenPKG from a read-only media other places might be found that need
write access - or fixing ;-)

As far as I know a complete Kolab install takes something like 500MB disk
space not including the RPMs. Too much for the average memory filesystem.

My suggestion for a (Knoppix-like) self contained bootable CD:
- do a union/translucent mount
drawback: hard to create

My suggestion for a mount-into-existing-system CD:
- create binary RPMs
- let the user to create a symlink to a huge disk space
- boostrap/install using binary RPMs (maybe using obmtool)
drawback: existing system is touched, see "entry-points" below

> Apart from the following utilities:
> 
> uuencode 
> uudecode 
> 
These are no longer needed with OpenPKG 2.0

> - I guess you also need to set up a user database /etc/passwd (for the Kolab
> users)
> - Cron
> - And a couple of other utils?
> 
see http://www.openpkg.org/faq.html#entry-points
/etc/openpkg is new to OpenPKG 2.0

> Another question, would it be possible to run OpenPKG without a prefix? So that
> our %l_prefix == ""?
> 
> The potential here would be to create a couple of "Skeleton OS's" like a barebones
> Linux or BSD system, and run the rest from within OpenPKG...
> 
> Is this in any way feasible?
> 
An empty prefix, won't work because many code pathes within various
OpenPKG scriptlets change the working directory and assume access to
%{l_prefix} through an absolute path. Hashpling aka shebang (#!/...
at the top of a script) accept relative pathes but they will fail if
not executed from within the proper directory. For the same reasons, a
prefix with a relative path won't work, too.

--
[EMAIL PROTECTED], Cable & Wireless
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
User Communication List                      [EMAIL PROTECTED]

Reply via email to