Hello Raja Sekhar,

On 07.06.2012 13:55, Raja Sekhar wrote:

Hi to all,

          I am running Genode12.05 on Fiasco kernel on top  of

Ubuntu .here i am running l4linux... my problem is... i don't want to boot every time .iso file.

I guess you mean that you normally use the l4linux run-script? If you want to build L4Linux on top of Genode without QEMU being started after every build, simply don't use a run-script. You can build the components you like manually, e.g.: 'make core init drivers l4linux'.

Or, if you want to use the run-script e.g. to build a ready to use ISO-image, just comment out the stuff in the run-script that executes QEMU, especially the line that starts with 'run_genode_until'.

I want a stabilized Root File System. can u suggest me how to fix a Root File System permanently

Seriously, I don't know what you mean by this. Do you mean the root-filesystem used by the l4linux run-script contains bugs, or what is the problem?

Regards Stefan

Hello again,

On 07.06.2012 15:15, Raja Sekhar wrote:

what am i asking is ...... generally in our system. if i download any file or something else. it will store in my root file system. after restarting my system. it will be there .. because of it's not a virtual file file system.

like that i want. when i boot that l4linux.iso i will get a terminal. there if gave

$ qemu-system-i386 -no-kvm -m 128 -serial unix:/tmp/qemu-pipe,server,nowait -serial mon:stdio -net nic,model=e1000 -net user -cdrom var/run/l4linux.iso

after giving this i will get qemu window inside that i'm giving

           $wget

http://genode-labs.com/publications/bastei-design-2006.pdf

now that .pdf file is downloading...

again when i reboot it. there is no downloaded pdf.

i want it to be there....

The L4Linux scenario you're using (which is simply an automated test to check whether l4linux is still compiling and running that is triggered nightly by our buildbot) starts a L4Linux instance with network, framebuffer, and serial line support, but without any block-device. You can see that already by investigating how QEMU and it's command-line arguments work. There is no block-device enabled given your posted QEMU command (beside the cd-rom). L4Linux uses an initramfs only, no persistence storage is involved here.

Nevertheless, in general it's possible to use a block-device in L4Linux, and thereby have the ability to store things persistently. You might use the l4android run-script as a starting-point. In that scenario L4Linux uses a harddisk.

Regards Stefan

Hello,

On 08.06.2012 07:32, Raja Sekhar wrote:

what I'm asking is init-rd(Temporary File System) is using as a file system. i want to mount real root file system. how to do it.

as I've said in my previous mail, you should consider the l4android run-script for this, in 'ports-foc/run/l4android.run'

Of special interest for you are the following things:

* How to provide a block-device to qemu (e.g.: -hda option), you can inspect the QEMU manual for more details * Which block device-driver shall I use, this depends on your hardware platform, for x86 the 'atapi' driver should be fine (location: 'os/drivers/src/atapi'), having a look into the README files of the corresponding driver is advisable if one is available * How can I integrate a block-device in L4Linux, have a look in the 'ports-foc/README' in section "Block session connection" * Potentially the block-device partition manager is of interest to you, when you want to share one block-device between different clients (see 'os/src/server/part_blk/README') * How can I route certain services to certain clients in init's configuration so that L4Linux reaches the right block-service, you can derive this potentially by inspecting the l4android run-script, and/or read the first sections of Genode's release- notes 10.05 (http://genode.org/documentation/release-notes/10.05)

If you've more specific questions after studying above sources, please feel free to ask.

Regards Stefan

PS: I forgot to mention, potentially you'll have to choose another initramfs (aka initrd) or adapt it, so that Linux will mount your persistence root filesystem automatically.