- l4-hackers - example.com Site

FLIPS and l4linux
by Leon 08 Sep '04

08 Sep '04

Hi all, I've got a running system and some small programs running on Fiasco with DoPE and l4linux-2.4. I want to investigate FLIPS to use as an extension to one of the programs (network capable). The difference between compiling L4 and all its packages now is that I must set the parameter LINUX24_DIR to point to a directory with vanilla kernel code (I used 2.4.27) instead of previously when the parameter pointed to the L4LINUX directory (l4linux-2.4). The last one is currently my working setup. Q1: Was I doing it wrong the whole time and was just lucky to get it working? Anyway the newly compiled FLIPS system starts to load as usual but as soon as l4linux is loaded is stops with a cursor blinking below the penguin with NO text (console) output. Here is the debug output: EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Warning: unable to open an initial console. simple_t| ERROR: task #13 doesn't match: client 11.03, owner 0.00 l4lx | l4ts_create_task(): failed (server=A.00, ret=-3, exc 0) The system is still operational and I can start my programs from the "doperun" terminal. Q2: Any suggestions on why my l4linux does not want to load anymore? Thanks Leon

4 5

New L4Env release
by Ronald Aigner 01 Sep '04

01 Sep '04

The TU Dresden OS team is happy to announce the next release of L4Env - the development environment for L4/Fiasco. Please visit the L4Env website http://os.inf.tu-dresden.de/l4env/ to download version 0.2 or browse the L4Env documentation. This new release contains our efforts to further improve L4Env, so you can look forward to enhanced functionality of, for instance, the loader or region manager, which make it easier to build applications for L4. Starting with this release we will also provide you with daily snapshots of the L4Env packages at http://os.inf.tu-dresden.de/l4env/. We would like to invite you and try L4Env 0.2 and help us improve it even more. Yours, the L4Env team.

1 0

Crypto Lib (X509)
by Robert Kutsch 27 Aug '04

27 Aug '04

Hallo, has anyone already compiled or used a crypto library for X509 certificates for the L4? Im trying to compile openSSL but i have many problems with the compiler option. Thx for replay Robert Kutsch

1 0

names for the L4 ipc functions for the x86 architecture
by Rafal Somla 26 Aug '04

26 Aug '04

Hi, I tried to compile and install Fiasco-ux and L4Env. It seems that the l4sys ipc functions for the x86 architecture have additional _i386_ part in their name. E.g., l4_i386_ipc_call instead of l4_ipc_call. The result is that, for instance, I can't compile the hello server without renaming the functions. Is that intentional or did I messed up the instalation? Thanks for any help on that, Rafal

2 1

L4 based schedulers
by Aidan Delaney 25 Aug '04

25 Aug '04

Hey all (Güten tag or G'day), How many "full" operating systems use l4? I'm aware of DROPS and am wondering if there is anything else that has a "process" model and scheduler build around l4. Thank you, -- Aidan Delaney email: adelaney(a)cs.may.ie web: http://www.cs.may.ie/~adelaney gpg: http://www.cs.may.ie/~adelaney/public_key.asc

2 1

ANNOUNCE: L4Linux 2.6
by Adam Lackorzynski 20 Aug '04

20 Aug '04

We are happy to announce the release of the latest version of L4Linux based on Linux 2.6. L4Linux is a modified version of Linux running on L4. This version of L4Linux is based on L4Env and on the Fiasco microkernel. It supports the x86 architecture and is available via anonymous CVS. This release is not ready for performance assessments and still awaits improvements in some regions but is nevertheless stable enough to run most of the available Linux programs. For more information refer to the L4Linux-2.6 website: http://os.inf.tu-dresden.de/L4/LinuxOnL4/ For other available L4Linux versions start at http://l4linux.org/ Adam

1 0

fwd: SPARC Pistachio
by Benno 14 Aug '04

14 Aug '04

In case anyone isn't on l4ka... ----- Forwarded message from Dan Koren <dk(a)inraid.com> ----- Date: Fri, 13 Aug 2004 23:03:48 -0400 From: Dan Koren <dk(a)inraid.com> Subject: SPARC Pistachio Message-ID: <012b01c481ab$52452370$0300a8c0@inRAID007> Reply-To: Dan Koren <dk(a)inraid.com> To: l4ka(a)ira.uka.de Is there a SPARC Pistachio port? Best regards, dk --------- Dan Koren Principal, inRAID, LLC 775-833-1407/voice 775-833-1405/fax ============================================================== This email and any attachments thereto may contain private, confidential, and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto. ============================================================= ----- End forwarded message -----

1 0

file format
by Alexander Grotzsch 01 Aug '04

01 Aug '04

Hi everybody! Is there any tool out there, with which I can read files having the extension "&l3" with windows XP? I worked with the L3 system during my schooldays and found an old disk containing ELAN-code. I desperatly need to review this code, but unfortunately I can not install L3 because I do not have the Install-disks anymore! ---------------------------------------------------------------------------------------- Hallo Zusammen! Gibt es irgendwo ein Tool, mit dem ich ".&l3"-Dateien unter windwos XP lesen kann? Während meiner Schulzeit haben wir viel mit ELAN programmiert und ich habe eine Diskette, auf der verschiedene Quellcodes aus dieser Zeit sind. Ich muß diese Codes dringend lesen! Habe aber kein L3-System mehr auf meinem Rechner. ---------------------------------------------------------------------------------------- Thanks for any help Dankbar für jeden Tipp Alexander Grotzsch ________________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193

1 0

RE: qemu and l4linux2.4
by Volkmar Uhlig 16 Jul '04

16 Jul '04

There is a bug in the current interrupt handler code. I'm not 100% sure but I think we have a patch to that. The problem is that with Pistachio we run APIC interrupt mode and when IRQs are disabled they usually get re-injected with a self-IPI (I'm not arguing about the sensibility of that strategy though). Right now L4Linux doesn't do that and the IRQ gets lost. - Volkmar > > -- > Mat/tia Belletti - Undergraduate student @ cs.unibo.it > ICQ: 33292311 - email: mbellett(a)cs.unibo.it > IRC: RedGlow - site(s): http://www.cs.unibo.it/~mbellett > Linux registered user 299762 @ Linux registered machine 213003 > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >

1 0

qemu and l4linux2.4
by Mattia Belletti 16 Jul '04

16 Jul '04

I tried to run an l4linux (pistachio 0.4, l4linux from daily cvs), and it all went fine until: hda: QEMU HARDDISK, ATA DISK drive hdc: QEMU CD-ROM, ATAPI CD/DVD drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: attached ide-disk driver. irq 14 not enabled irq 14 not enabled IRQ resend (14) With quite a lot of delay after each of the two 'hda: QEMU HARDDISK...' and 'hdc: QEMU CD-ROM...', and, after that, it finally stops. Qemu runs normal linux fine - any idea where to go to find the problem? -- Mat/tia Belletti - Undergraduate student @ cs.unibo.it ICQ: 33292311 - email: mbellett(a)cs.unibo.it IRC: RedGlow - site(s): http://www.cs.unibo.it/~mbellett Linux registered user 299762 @ Linux registered machine 213003

1 0

paper about l4
by Fabian Sturm 04 Jul '04

04 Jul '04

Hi! I just wanted to let you know that I wrote a small paper about the L4 Microkernel for a seminar in my school. It's a summary of many of the information which is available on the various websites. I doubt that it has much usefulness since the reference manual and other sources are more detailed and precise. But anyways some might be interested. http://www.rtfs.org/ext/l4_microkernel.pdf Thanks a lot, Fabian P.s. even I already gave my talk I still would be interested in any wrong claims given in the paper.

1 0

The error "tempfile: command not found" on compliing fiasco.
by Daniel Yu 04 Jul '04

04 Jul '04

Hi all: I meet the troubles when "make config" the fiasco. After the graphic configure setting, the make process is stopped by error: .......... echo INT_CPP_x86_NAME= 'cat $X.out' >> ./.Makeconf.bid.converted;\ rm -f $X $X.{c,out} /bin/bash: line1: tempfile: command not found. .......... I have browsed the source code of Makefile, there is one sentence: X='tempfile -s .c' . But there is not a command named tempfile in bash or /bin, /sbin. Then what's wrong about the error? Thanks! Daniel

2 1

The build error on l4linux and fiasco!
by Daniel Yu 01 Jul '04

01 Jul '04

Hello All: I am a newbie for using u-kernel: fiasco and l4linux. However, I meet some problems when building them. For building l4linux: Under redhat 9.0, kernel version is linux-2.4.20-8 and gcc version is 3.2.2. After typing the command: "make config". the error is as following: /bin/sh scripts/Configure arch/l4/config.in : command not foundline 51: ' script/Configure: line 72: syntax error near unexpected token `{ ' script/Configure: line 72: ' function mainmenu_option () { make: *** [config] Error 2 Under the same environment, it is successful to build linux-2.4.20 kernel. So what's wrong? For Fiasco building, I get the other error information:(Using fiasco-1.1) Malformed UTF-8 character (unexpected continuation byte 0xb5, with no preceding start byte) in substitution (s///) at /fiasco-1.1/tool/preprocess/src/preprocess line 672, <> line 2058. When compiling process went this place, it dies and I must use CTRL-C to stop it. Can you give me some suggestions? Thank yu all very much!

2 2

L4 & ADX
by Frederic BOYER 29 Jun '04

29 Jun '04

Hello L4 hackers ! I restarted to work on my project ADX (write a real time unix like OS on top of L4). In fact I restart from scratch. I did not work on it since two years, and all my old sources died with my old computer and its hard drive. I plan to port GNAT run-time on top of L4 and begin to write the servers on top of it. do this projet interest any body ? Thanks to contact me and give me your feeling about this project. Frederic BOYER. "This message, including any attachments may contain confidential and privileged material; it is intended only for the person to whom it is addressed. Its contents do not constitute a commitment by Credit Agricole Cheuvreux except where provided for in a written agreement. Credit Agricole Cheuvreux assumes no liability or responsibility for the consequences arising out of a delay and/or loss in transit of this message, or for corruption or other error(s) arising in its transmission and for any misuse or fraudulent use which may be made thereof. If you are not the intended recipient, please contact us and abstain from any disclosure, use or dissemination. To the extent that this message contains research information and/or recommendations, these are provided on the same basis as Credit Agricole Cheuvreux's published research and the recipient must have regard to all disclosures and disclaimers contained therein."

1 0

KernelInterface @ IA32
by Louis 16 Jun '04

16 Jun '04

Hi L4 hackers, I'm a newbie in L4 and reading L4 X.2 spec. In IA32 interface, KernelInterface is implemented by 'lock: nop'. That really confuses me. Is it not just a placeholder? Any special side-effect? I can not find any clue in IA32 manuals. Yours truly, - Louis

3 2

ANNOUNCE: L4Ka::Pistachio version 0.4
by Espen Skoglund 04 Jun '04

04 Jun '04

The L4Ka team is happy to announce the release of L4Ka::Pistachio version 0.4. With L4Ka::Pistachio the L4Ka team aims at providing a robust, portable, high performance implementation of the L4 Version 4 API. It has been a long time since our last release, but we hope that all the new functionality and bug fixes were worth the wait. Among other things, the version 0.4 release adds support for 3 new hardware architectures. All in all the L4Ka::Pistachio kernel now runs on the following architectures: o Intel IA32 (Pentium and higher) o Intel IA64 (Itanium1, Itanium2, Ski) o AMD64 [NEW] o PowerPC 32bit (IBM 750) o PowerPC 64bit (Power3, Power4) [NEW] o Alpha (21164) o MIPS 64bit (R4000, VR41xx, R5000) o ARM (SA1100, XScale, ARM925T) [NEW] L4Ka::Pistachio version 0.4 incorporates a number of enhancements, modifications, and bug fixes. The following is a list of the major architecture independent changes since the last release: o Most system calls have been extended to report error codes upon failure. This substantially improves the ease of application development. o The kernel now implements "over-mapping" of flexpages correctly. Over-mapping occurs when a new page frame is mapped into the location of an already existing page frame in the destination address space. o Better support for reporting and resetting reference bits. o The ExchangeRegisters system call has been modified so that it can no longer activate inactive threads. o The L4 Version 4 API now specifies an architecture independent protocol for communicating boot loader specific data to the application programs. This protocol is supported by several L4 bootloaders (including kickstart). o Sigma0 now implements setting of memory attributes. o A bug (actually several bugs) in sigma0 would in some cases cause sigma0 to refuse to hand out certain memory regions, or cause incorrect memory to be handed out. o A new 'grabmem' example application has been added to the distribution. The following is a list of architecture specific changes and additions: Alpha: o Added FPU support. o Implemented SystemClock system call. AMD64: o This release adds support for the AMD64 architecture to L4Ka::Pistachio. o The AMD64 kernel is almost feature complete. It only lacks support for I/O flexpages and implementations of the Lipc, ProcessorControl and MemoryControl system calls. It also does not support SMP yet. o The kernel also features a hand-optimized fast IPC path. ARM: o This release adds support for the ARM architecture to L4Ka::Pistachio. o PLEB (Intel StrongARM SA-1100), Intel XScale IXP425 and TI OMAP1510 (ARM925T) platform support is included. o The kernel features fast address-space switching (FASS) [1] as a compile option. o The kernel is currently missing a fast-IPC path. Even without this optimization, context-switching and IPC performance across address spaces, when FASS is used appropriately, improves on any existing ARM implementation of L4 by approximately two orders-of-magnitude. o As with other architectures in L4Ka::Pistachio, currently no LIPC optimization is implemented - the LIPC path is identical to the IPC path. IA32: o Added a proper implementation of the SystemClock system call. o The support for small address spaces has been greatly improved. o Fixed a bug in the interrupt handing code that caused edge triggered interrupts to be handled incorrectly. o The kickstart utility now handles a number of command line options (see http://l4ka.org/projects/pistachio/kickstart.php for details). IA64: o The kernel now supports lazy handling of the upper 96 floating-point registers. o Preliminary support for performance profiling has been added. o Fixed a bug in the fast-IPC path that could cause interrupt handling to crash the kernel. o Low-level performance optimizations. o Fixed SystemClock system call to always report correct times. MIPS 64bit: o The kernel has been fixed to compile without debugging. o Added support for NEC VR41XX processors. o Changed the system call encoding. o The fast-IPC path has been fixed. o Reworked the exception handling code. o More accurate timer implementation. o Floating point support. o SMP support. PowerPC 32bit: o The kernel can run without debugging and without the debugger. o Proper exception message dispatching, including support for the system call exception. o Added correct implementation of the SystemClock system call. o Can prevent verbose kernel initialization. o Added a user-level I/O driver for the psim COM port, which can be used when the kernel is compiled without debug support. o Code restructuring to (1) minimize code, (2) improve readability, and (3) parameterize more kernel features. PowerPC 64bit: o This release adds support for the 64 bit PowerPC architecture to L4Ka::Pistachio. o The kernel supports Power3 and Power4 architectures (no SMP). o Optimized selective SLB replacement context switching on Power4. For more information on L4Ka::Pistachio and the L4 Version 4 API in general, refer to the L4Ka::Pistachio whitepaper: http://l4ka.org/projects/pistachio/pistachio-whitepaper.pdf L4Ka::Pistachio is available under the two-clause BSD license. Source and binary distributions, documentation, and other online resources can be found on the L4Ka website: http://l4ka.org/ The latest version of L4Ka::Pistachio, including any changes since the latest release, is also available through a public read-only CVS repository. See our website for instructions on how to access the public CVS. Happy hacking, The L4Ka Development Team [1] A. Wiggins, H. Tuch, V. Uhlig, and G. Heiser. Implementation of Fast Address-Space Switching and TLB Sharing on the StrongARM Processor. In Eighth Asia-Pacific Computer Systems Architecture Conference (ACSAC'03), Aizu-Wakamatsu City, Japan, September 23-26, 2003.

1 0

Re: ARM Port of L4/Linux?
by Yann Dirson 04 Jun '04

04 Jun '04

Hi Dave, You'll find more info about L4 for various archs on http://os.inf.tu-dresden.de/L4/impl.html L4Ka::Pistachio is also told to work on ARM, but not the 0.3 release AFAIK - see http://l4hq.org/arch/arm/ HTH, -- Yann Dirson <ydirson(a)altern.org> | Why make M$-Bill richer & richer ? Debian-related: <dirson(a)debian.org> | Support Debian GNU/Linux: Pro: <yann.dirson(a)fr.alcove.com> | Freedom, Power, Stability, Gratuity http://ydirson.free.fr/ | Check <http://www.debian.org/>

2 1

bochs/plex86 vs. qemu
by Yann Dirson 03 Jun '04

03 Jun '04

Hi Fiasco team, I see in http://os.inf.tu-dresden.de/fiasco/wishlist.html that someone had the idea that porting plex86 to L4 would be useful. Incidently, I had a similar idea a couple of weeks ago, but I was more thinking about qemu, so I was wondering whether qemu had been considered here. One major benefit I see is that qemu is a fast multi-architecture emulator (although only x86 support is complete for now, powerpc appears to be on good tracks), and would make it possible to run OS for arbitrary processors. Interested people can check it a thttp://fabrice.bellard.free.fr/qemu/ Best regards, -- Yann Dirson <ydirson(a)altern.org> | Why make M$-Bill richer & richer ? Debian-related: <dirson(a)debian.org> | Support Debian GNU/Linux: Pro: <yann.dirson(a)fr.alcove.com> | Freedom, Power, Stability, Gratuity http://ydirson.free.fr/ | Check <http://www.debian.org/>

1 0

ARM Port of L4/Linux?
by David Krause 29 May '04

29 May '04

As far as I can tell, L4/Linux only runs on x86. Is there an ARM port in existence, or in progress that a kind soul on this list could point me to? Thanks in advance, -- Dave

1 0

ipc- where to send message(ipc).
by manish regmi 27 May '04

27 May '04

thanks, i got it. The client need to request tid of the server to name space server. But how much does it slows down a system. For example servers like i/o severs and fileservers need to be frequently called. Some systems like QNX decreases the no. of message passing by directly sending messages to file descriptor(fd) once a file is opened.i.e. directly send to i/o manager. will it be good to implement? thanks >Manish, > >(You were asking both the list and me, so I repeat here) > > > I am new to l4. Is it true that the allocation of tid is given to user. >How >[...] > > >Kind of. As Espen said, the Microkernel provides no name space (except its >namespaces for kernel resources such as threads, tasks and memory). >This must be done at user level. > >*One* scheme is to have names ("strings") for servers, and identify >servers (their offered services) by these names. Then servers have to >register their (string, thread_id) pair at a nameserver, and clients have >to ask the nameserver for the (string -> thread_id) translation. Of >course, the nameserver must somehow be found. In the case of DROPS (our >OS on top of L4), this nameserver is registered at rmgr, and rmgr has a >fixed and well-known threadid. Thus, name resolution works as follows: >The client asks the rmgr (threadid 4.0 per definition) for the threadid of >the nameserver, and then the nameserver for the threadid of the target >server. The rmgr does not have the flexibility we need for dynamic name >registering, therefore the nameserver. > >*Other* policies could for instance be one hierarchical namespace, >resolved by a root nameserver and client nameservers. The root nameserver >(and the client nameservers) could provide mounting other namespaces. This >way one could construct a namespace comparable to the UNIX filesystem >namespace. Drivers could per definition be found under a name like >'/dev/*'. A user-land file system could provide the part of the namespace >for /home/, another for /proc/, and another for /usr/. > >You should watch our seminar page, in a couple of weeks some slides about >namespace issues should show up. > > >Regards, >Jork > _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

1 0

ipc- where to send message(ipc).
by manish regmi 26 May '04

26 May '04

hi, I am new to l4. Is it true that the allocation of tid is given to user. How do i know the tid of the server i am sending a msg to? What should i do for a robust design. Giving a static tid for server threads is not flexible. What would be a more flexible way. What have others done. thanks. _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail

2 1

ipc- where to send message(ipc).
by manish regmi 25 May '04

25 May '04

hi, L4 send a message using a thread id. how will an application developer will know where to send the thread. he needs to know the tid of the server which is making a receive call. how to we know at runtime, which thread of File server(say) is receiveing a read() request. I mean how is namespace resolved in l4. thanks _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail

3 2

L4Linux booting problems
by Luis Araujo 25 May '04

25 May '04

Hi, i got a problem with L4Linux while booting, Im using: L4Ka::Pistachio Downloaded from CVS 23 - 05 - 2004 Compiling Pistachio and L4Linux with gcc-3.3.1 Debian3.0 ramdisk1.0 This is the grub menu.lst: title=L4Linux on L4Ka::Pistachio with Debian ramdisk kernel=/l4boot/kickstart module=/l4boot/ia32-kernel module=/l4boot/sigma0 module=/l4boot/vmlinuz.VX2 devfs=mount ramdisk_size=65536 root=/dev/ram0 rw console=herc console=tty module=/l4boot/ramdisk.gz Everything goes fine during configuration and compilation, and it starts up booting with no problem at all, until it reaches "Starting kswapd" , then it stops in that line, do i need to set (or unset) something in the configuration? Any help is appreciated, Thanks -- Luis

2 1

X.2-compatible L4Env
by Leonid Ryzhyk 11 May '04

11 May '04

Hi We are developing an operating system on top of Pistachio. At the moment we are looking for a framework which would allow to quickly port existing device drivers (e.g., from Linux) to our system as well as develop our own drivers. L4Env with its Omega0 server, l4io library and DDE seems to be a perfect match. Unfortunately, L4Env does not currently support Pistachio. L4hq site says that such support will follow shortly. Is this work being carried out, and, if so, when (approximately) will X.2-compatible L4Env be released? Thanks in advance. Leonid

2 1

L4Linux 2.4.22 on Pistachio can not boot
by �� 11 Mar '04

11 Mar '04

I grabbed the latest source of L4Ka::Pistachio and L4Linux 2.4.22 from CVS, and compiled them using GCC 2.95 (Debian/Woody). When the system was booting, I got the following error message: Launching kernel ... L4Ka::Pistachio - built on Mar 11 2004 20:48:53 by root@Bo using gcc version 2.95.4 20011002 (Debian prerelease) init_emulibpager initialized to c0001 e0019000 pf @ ffa00002, ip=000c0103 --- "KD# user touches kernel area" --- --------------------------------- (eip=f0107a3c, esp=f0118f3b) --- It seems that the L4Linux kernel did not boot at all. The options related to L4Linux in .config is: # # L4Linux options # CONFIG_L4=y # CONFIG_L4_V2 is not set # CONFIG_L4_VX0 is not set CONFIG_L4_VX2=y # CONFIG_L4_L4ENV is not set # CONFIG_L4_SMALL is not set CONFIG_L4_TAMED=y CONFIG_L4_L4DIR="/usr/src/pistachio/user" # CONFIG_L4_USERPRIV_ONLY is not set # CONFIG_L4_EXTERNAL_RTC is not set CONFIG_L4_DBG=y # CONFIG_L4_IDLETHREAD is not set # CONFIG_L4_IRQ_WHEELS is not set # CONFIG_L4_DBG_SHOW_CURRENT is not set CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_L4_ROOTTASK=y The options in Pistachio's config.h is: /* Hardware */ /* Basic Architecture */ #define CONFIG_ARCH_IA32 1 #undef CONFIG_ARCH_IA64 #undef CONFIG_ARCH_POWERPC #undef CONFIG_ARCH_ALPHA #undef CONFIG_ARCH_MIPS64 /* Processor Type */ #undef CONFIG_CPU_IA32_I586 #undef CONFIG_CPU_IA32_I686 #define CONFIG_CPU_IA32_P4 1 /* Platform */ #define CONFIG_PLAT_PC99 1 #undef CONFIG_SMP /* Miscellaneous */ #undef CONFIG_IOAPIC /* Kernel */ #undef CONFIG_IPC_FASTPATH #define CONFIG_DEBUG 1 #define CONFIG_IA32_SMALL_SPACES 1 /* Debugger */ #define CONFIG_KDB 1 /* Kernel Debugger Console */ #define CONFIG_KDB_CONS_KBD 1 #undef CONFIG_KDB_CONS_COM #undef CONFIG_KDB_CONS_SKI #define CONFIG_KDB_COMPORT 0x3f8 #define CONFIG_KDB_COMSPEED 115200 #define CONFIG_KDB_DISAS 1 #undef CONFIG_KDB_ON_STARTUP #undef CONFIG_KDB_BREAKIN #undef CONFIG_KDB_NO_ASSERTS /* Trace Settings */ #undef CONFIG_VERBOSE_INIT #undef CONFIG_TRACEPOINTS #undef CONFIG_KMEM_TRACE #undef CONFIG_TRACEBUFFER #undef CONFIG_IA32_KEEP_LAST_BRANCHES /* Code Generator Options */ /* Derived symbols */ #define CONFIG_IA32_SYSENTER 1 #undef CONFIG_CPU_ALPHA_A21164 #undef CONFIG_SWIZZLE_IO_ADDR #undef CONFIG_ALPHA_FASTPATH /* Code Generator Options */ /* Derived symbols */ #define CONFIG_IA32_SYSENTER 1 #undef CONFIG_CPU_ALPHA_A21164 #undef CONFIG_SWIZZLE_IO_ADDR #undef CONFIG_ALPHA_FASTPATH #undef CONFIG_CPU_ALPHA_A21064 #undef CONFIG_CPU_ALPHA_A21264 #define CONFIG_IA32_HTT 1 #undef CONFIG_IS_64BIT #undef CONFIG_ACPI #define CONFIG_IA32_PGE 1 #undef CONFIG_BIGENDIAN #define CONFIG_IS_32BIT 1 #define CONFIG_ALPHA_CONSOLE_RESERVE 321 #undef CONFIG_HAVE_MEMORY_CONTROL #define CONFIG_IA32_FXSR 1 #define CONFIG_IA32_SMALL_SPACES_GLOBAL /* That's all, folks! */ #define AUTOCONF_INCLUDED And the menu.lst file in /boot/grub is: Bo:/boot# less grub/menu.lst title Linux root (hd0,0) kernel /boot/bzImage title L4Ka::Pistachio kernel /boot/L4/kickstart module /boot/L4/ia32-kernel module /boot/L4/sigma0 module /boot/L4/vmlinuz.VX2 no-scroll console=herc console=tty l4irqack=linux root=/dev/hda1 Some one kindly tell me what terrible mistakes I've made? Best wishes. _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

1 0