Hello Hackers again..
I've reconstituted my Fiasco box with a Debian (Stable) and a SuSE (8.0) dual boot. My aim is to have a workable approximation to the Dresden configurations using Debian, while the SuSE version will enable me to help test on that platform.
I have acquired gcc3.2 and binutils to match and those will be installed shortly.
I have a question for the group.
My disk space is limited. I can build on this computer but it would be ideal if after building I could move the bulk of the l4, ($BUILDDIR), oskit, and the rest onto another machine, retaining on my "Fiasco" box only those files needed for a running installation, i.e. kernel modules, libraries, and whatever else.
(It goes without saying that I need to reserve space for any linux executables that I intend to run on top of Fiasco)
I'm happy to experiment with this question, but if the group already possesses a list of executables, libraries, and so on, it would be nice to start from there. OTOH if you don't then perhaps I could make a contribution to the project by creating this list.
David,
I've reconstituted my Fiasco box with a Debian (Stable) and a SuSE (8.0) dual boot. My aim is to have a workable approximation to the Dresden configurations using Debian, while the SuSE version will enable me to help test on that platform.
So, you want to *build* the L4 programs and Fiasco on this machine, right?
My disk space is limited. I can build on this computer but it would be ideal if after building I could move the bulk of the l4, ($BUILDDIR), oskit, and the rest onto another machine, retaining on my "Fiasco" box only those files needed for a running installation, i.e. kernel modules, libraries, and whatever else.
From this I assume, you want to *run* Fiasco and the L4 programs on this
machine too, right?
Generally, all L4 programs (despite Fiasco itself) will be installed to $(L4DIR)/bin/ upon compilation. Here in Dresden this directory is typically a symlink to an NFS-mounted partition on our central fileserver. The latter is used by our testmachines (different from the compilation machines) to get the files using tftp during L4 startup.
I would suggest a similar setup to you. However, if you are forced to use the same machine for compilation and running, you can save space by doing a "make install" in l4 first. This installs all the libraries and includes into DROPS_STDDIR (the directory you specified during configuring the DROPS tree). Then, you can safely remove the OSKIT10 and the OSKIT tree, as well as the whole l4/pkg tree and l4/tool tree.
Best regards, Jork
-- The truth is that for reasons that have a lot to do with the U.S. government bureaucracy we settled on the one issue that everyone could agree on which was weapons of mass destruction as the core reason... P. Wolfowitz
Hello Hackers
I've got Debian Testing installed.
with a minimal functional base Linux software set.
I am doing "make -C l4 config" in the home directory above l4/ and receive fatal error "Menuconfig requires bash"
Well, bash is installed here.
The problem seems to stem from the first line of l4/tool/config/Menuconfig
containing #! /bin/sh
(verbatim)
on changing this to #!/bin/bash
I get a working Menuconfig
HTH David
PS to Sarah, I also have a SuSE install on this machine ;-)
l4-hackers@os.inf.tu-dresden.de