http://permalink.gmane.org/gmane.os.hurd.l4 hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.os.hurd.l4/6019 <pre>FOSDEM 2012 - Multiserver, microkernel-based operating systems devroom *CALL FOR PARTICIPATION* http://fosdem.org/2012 (apologies for cross-posting) The developers of several free and open-source multiserver and/or microkernel-based operating systems will meet at FOSDEM 2012 in Brussels, Belgium and will share a developer room. The devroom is currently looking for content in the form of talks related to the area of multiserver and/or microkernel-based operating systems. Possible topics include, but are not limited to: OS introduction to developers of other OS Subsystems and architecture Hardware and device drivers Tools and languages Release engineering and testing Experience and learning from mistakes Technical challenges Community and life with an OS-project Academia and education Please send your talk proposal(s) to: microkernel-devroom&lt; at &gt;lists.fosdem.org no later than by 2011-12-31. Make sure to include the following in your proposal: - title of your talk (will be printed in the</pre> Jakub Jermar 2011-11-22T22:29:48 http://permalink.gmane.org/gmane.os.hurd.l4/6018 <pre>Hi! I was contacted by jermar on IRC, a developer of HelenOS, which is another multiserver microkernel based OS, &lt;http://www.helenos.org/&gt;. He and also some folks from the MINIX3 group were thinking whether to propose a developer room for the upcoming FOSDEM 2012. The idea is for having a devroom dedicated to [multiserver] microkernels, or a generic alt-OS room as a fallback. The deadline for applications is in three days already. Are we interested in this? I said we generally are, but that I have no idea how many of us will make it to FOSDEM next year. Then, our group will need to find things to do in the devroom, provide a portion of the content. This can be (but is not limited to): presentations, brainstorming, coding sessions. Please answer quickly. Are you interested in this? Can you already forsee whether you'll make it to FOSDEM next year, 4th/5th February 2012, &lt;http://fosdem.org/2012/&gt;. Grüße, Thomas </pre> Thomas Schwinge 2011-10-24T17:01:01 http://permalink.gmane.org/gmane.os.hurd.l4/6017 <pre>Hi, The NOVA project is happy to announce that there is a new prerelease of the NOVA microhypervisor available for download at http://www.hypervisor.org/ under the terms of the GNU General Public License version 2. NOVA is based on a modern microhypervisor written in C++ and assembler. The current implementation runs on multi-core x86 machines that support ACPI, under QEMU (including VM support), and as a microkernel in a virtual machine on top of itself. NOVA makes use of hardware virtualization features such as Intel VT-x/VT-d or AMD-V, and facilitates running unmodified guest operating systems in virtual machines with near-native performance. Among other things, the new prerelease improves the security of device- and interrupt assignment by using capabilities for these operations. There is also a new hypercall for interacting with the scheduler. At the same time, we've released a new version of the NOVA Userland (NUL). While there are few user-visible changes, a lot has changed under the hood. We ha</pre> Udo A. Steinberg 2011-07-28T18:04:47 http://permalink.gmane.org/gmane.os.hurd.l4/6013 <pre>Today I got the source again from (git.savannah.gnu.org/hurd/viengoos.git ) then switch to viengoos-on-bare-metal Got the cross-compiler and so. As i'd trying to fix some of my problems i saw at the file i named bellow some mistake might occurred. /libviengoos/t-addr.c line 67 &gt; l4_uint64_t used ,but doesn't declared! even at &lt;l4/type.h&gt; Does uint64_t mistyped as l4_uint64_t? (uint64_t had declared at hurd/addr.h) -Naghizodeh </pre> Naghizodeh,T.A-H 2011-04-07T15:52:57 http://permalink.gmane.org/gmane.os.hurd.l4/6012 <pre>Opps, I forgot to send the original message to the mailing list. Here it is: Try using the instructions here: http://www.gnu.org/software/hurd/microkernel/viengoos/building.html Viengoos only builds on x86_64 IIRC. Following those instructions should atomatically build the cross-compiler that you need. It worked for me, on PPC Debian Squeeze. -Andrew </pre> Andrew Engelbrecht 2011-04-06T23:01:39 http://permalink.gmane.org/gmane.os.hurd.l4/6011 <pre>Has anyone gotten viengoos to boot using GRUB2 v. 1.99~rc1? I get the following errors in qemu when try to boot Viengoos: error: invalid offset in section header. error: you need to load the multiboot kernel first Looking at the date of the patch recommended for GRUB at http://www.gnu.org/software/hurd/microkernel/viengoos/building.html , I figured that v. 1.97 would be the closest tried and tested version of GRUB and therefore might work with viengoos. Unfortunately, v1.97, v1.97.1, v1.97.2 and v1.98 don't cross-compile on my PPC computer. Here are the errors I get when compiling v1.97: gcc -Iutil/i386/pc -I../util/i386/pc -I. -I./include -I../include -Wall -W -DGRUB_LIBDIR=\"/home/sudoman/src/gnuhurd/failedgrub/7/build/../install/lib/`echo grub/i386-pc | sed 's&amp;^&amp;i386-pc-linux-gnu-&amp;'`\" -g -O2 -DGRUB_UTIL=1 -MD -c -o grub_setup-util_i386_pc_grub_setup.o ../util/i386/pc/grub-setup.c ../util/i386/pc/grub-setup.c:38: error: initializer element is not constant ../util/i386/pc/grub-setup.c:38: error: (near i</pre> Andrew Engelbrecht 2011-04-06T22:43:54 http://permalink.gmane.org/gmane.os.hurd.l4/6010 <pre>At Wed, 6 Apr 2011 22:24:58 +0430, Naghizodeh,T.A-H wrote: This is wrong. Viengoos does not use L4. Are you sure you are using the right branch? </pre> Neal H. Walfield 2011-04-07T07:45:14 http://permalink.gmane.org/gmane.os.hurd.l4/6009 <pre>Hi,there as i following building instruction, faced some problems: $ autoreconf -i $ mkdir test build $ cd test/ $ ../configure --enable-l4 --host=i686-pc-viengoos-gnu \ --enable-tests // this configuration successfully finished with two warning // warning - Unrecognized Options : --enable-tests $make check // first the compilations process got terminated , // compile process stopped since it couldn't find one header file // at ../../libviengoos/viengoos // i temporary fix this problem but there are still some problems // the i found that in directory="test/libviengoos" // at Makefiles , there has been used variable $(INCLUDES) but never // assigned value . $cat &lt;dir&gt;/test/libviengoos/Makefile | egrep '^INCLUDES' // but no result founded //after i called '$make check' the process show this messages on // screen make[2] : Leaving direcotry '&lt;DIR&gt;/test/libviengoos' make check-TESTS make[</pre> Naghizodeh,T.A-H 2011-04-06T17:54:58 http://permalink.gmane.org/gmane.os.hurd.l4/6008 <pre>At Tue, 05 Apr 2011 21:21:44 +0430, Naghizodeh T.,A-H wrote: You want to use the viengoos-on-bare-metal on bare metal branch. May be the rest of the output is going to the serial console. Neal </pre> Neal H. Walfield 2011-04-06T13:14:50 http://permalink.gmane.org/gmane.os.hurd.l4/6007 <pre>Hi there, I used qemu and Grub Legacy (floppy disk image) for running kernel with it's modules I follow mostly from the instruction on README when i try to boot on grub i saw this , it's seem the kernel going to starting , but ,it doesn't . system stop by give me this log file on the screen (i'd typed them) laden (ff0720ff):kip_fixup:54: Booting an x2 Kernel. laden (ff0720ff):kip_fixup:70: Sigma0: Low 0x20000, Hight 0x29524, IP 0x20000, SP 0x0 laden (ff0720ff):kip_fixup:75: Root: Low 0x400000, Hight 0x4d40cc, IP 0x400000, SP 0x0 laden (ff0720ff):kip_fixup:93: Memory Map 1: Type shared(4)/0, Low 0x0, Hight 0xfffffffffffffc00 laden (ff0720ff):kip_fixup:93: Memory Map 2: Type conventional(1)/0, Low 0x0, High 0x9f000 laden (ff0720ff):kip_fixup:93: Memory Map 3: Type arch(15)/2, Low 0x9f400, High 0x9fc00 laden (ff0720ff):kip_fixup:93: Memory Map 4: Type arch(15)/2, Low 0xf0000, High 0xffc00 laden (ff0720ff):kip_fixup:93: Memory Map 5: Type conventional(1)/0, Low 0x100000, High 0x7ffcc00 laden (ff0720ff):kip_f</pre> Naghizodeh T.,A-H 2011-04-05T16:51:44 http://permalink.gmane.org/gmane.os.hurd.l4/6005 <pre>Thus spake "Udo A. Steinberg" &lt;udo&lt; at &gt;hypervisor.org&gt;: And of course there is also a new prerelease[1] of the NOVA Userland available under the same conditions. The NOVA Userland (or NUL) is a multiserver userland consisting of a root partition manager, a deprivileged virtual machine monitor (Vancouver), and several tools. As always, we have prepared a Demo CD[2] with several virtual machines ready for you to try. This time it is a bit larger than usual, because we have included the GRML Live CD[3] as virtual machine template. Be sure to check out its "Addons", such as gPXE. If you do not have a CD handy, the image can also be dd'ed to a USB key. Thanks to SVM support in the new NOVA release most of the demo should work in Qemu as well. In practice, only the most recent version from the Qemu git[4] seems to work. NUL is the work of Bernhard Kauer, who has written Vancouver almost single-handedly, Alexander Böttcher and myself. Have fun, Julian Footnotes: [1] http://os.inf.tu-dresden.de/~jsteckli/nova/</pre> Julian Stecklina 2011-02-16T23:08:56 http://permalink.gmane.org/gmane.os.hurd.l4/6004 <pre>Hi, The NOVA project is happy to announce that there is a new prerelease of the NOVA microhypervisor available for download at http://www.hypervisor.org/ or http://os.inf.tu-dresden.de/~us15/nova/ under the terms of the GNU General Public License version 2. NOVA is based on a modern microhypervisor written in C++ and assembler. The current implementation runs on multi-core x86 machines that support ACPI, under QEMU (including VM support), and as a microkernel in a virtual machine on top of itself. NOVA makes use of hardware virtualization features such as Intel VT-x/VT-d or AMD-V, and facilitates running unmodified guest operating systems in virtual machines with near-native performance. The new release brings virtual-machine support to QEMU and older AMD CPUs, both of which lack nested paging. Furthermore, the microhypervisor can now translate related capabilities during message passing. Cheers, - Udo </pre> Udo A. Steinberg 2011-02-16T21:55:10 http://permalink.gmane.org/gmane.os.hurd.l4/6002 <pre>Hi, On Mon, Dec 27, 2010 at 02:07:23PM +1100, William ML Leslie wrote: Well, empirical evidence seems to contradict... -antrik- </pre> olafBuddenhagen< at >gmx.net 2011-01-03T14:11:34 http://permalink.gmane.org/gmane.os.hurd.l4/6001 <pre> Better yet: Tell all your friends about your new finding :) That *will* help the Hurd. Best wishes, Arne </pre> Arne Babenhauserheide 2010-12-31T08:46:33 http://permalink.gmane.org/gmane.os.hurd.l4/6000 <pre>thanks i think i might have learned something new so I'll quit trolling for now. On Thu, Dec 30, 2010 at 1:12 PM, Arne Babenhauserheide &lt;arne_bab&lt; at &gt;web.de&gt; wrote: </pre> Oz 2010-12-31T05:29:54 http://permalink.gmane.org/gmane.os.hurd.l4/5999 <pre> See the heading of http://hurd.gnu.org → mission statement of the Hurd :) We have Olaf/Antrik to thank for that! Best wishes, Arne</pre> Arne Babenhauserheide 2010-12-30T19:12:02 http://permalink.gmane.org/gmane.os.hurd.l4/5998 <pre>Hi Have these aspects been decided and fixed ? </pre> Parantapa Bhattacharya 2010-12-29T14:23:17 http://permalink.gmane.org/gmane.os.hurd.l4/5997 <pre>ok thanks i understand better now On Mon, Dec 27, 2010 at 12:17 AM, &lt;olafBuddenhagen&lt; at &gt;gmx.net&gt; wrote: </pre> Oz 2010-12-29T12:05:38 http://permalink.gmane.org/gmane.os.hurd.l4/5996 <pre>Hi, On Sun, Dec 26, 2010 at 09:57:03AM -0600, Oz wrote: That would be a pointless exercise. Several free (monolithic) kernels already exist; there is no need to create another one. The reason we still work on the Hurd is that we believe the architecture offers unique benefits. If we can't make it work as a microkernel system, there is no use in working on it at all. BTW, we are not trying to create a perfect kernel (well, most of us aren't :-) ) -- just something that is superior to current mainstream kernels in certain regards. -antrik- </pre> olafBuddenhagen< at >gmx.net 2010-12-27T06:17:06 http://permalink.gmane.org/gmane.os.hurd.l4/5995 <pre> It's no easier to write a monolithic kernel than it is to write a modular kernel. For as long as I have been following the development of the Hurd, the problems (from the perspective of "why isn't pure GNU as usable and feature-complete as GNU/Linux") that the team have been having aren't architectural at all, they are engineering and manpower problems, and aren't solved by the many handwavy suggestions like writing a monolithic kernel that get thrown around from time to time. They are solved by people sitting down and doing the work. Similarly, the only way to settle architectural arguments seems to be to do the work - because where progress is being made, interested people will follow. </pre> William ML Leslie 2010-12-27T03:07:23 http://permalink.gmane.org/gmane.os.hurd.l4/5994 <pre>Wrong project, see http://kernel.org/ </pre> Bjartur Thorlacius 2010-12-26T18:19:27 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.os.hurd.l4