Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262064AbUDDADT (ORCPT ); Sat, 3 Apr 2004 19:03:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262068AbUDDADT (ORCPT ); Sat, 3 Apr 2004 19:03:19 -0500 Received: from opersys.com ([64.40.108.71]:15623 "EHLO www.opersys.com") by vger.kernel.org with ESMTP id S262064AbUDDADS (ORCPT ); Sat, 3 Apr 2004 19:03:18 -0500 Message-ID: <406F4FCD.7020506@opersys.com> Date: Sat, 03 Apr 2004 18:59:09 -0500 From: Karim Yaghmour Reply-To: karim@opersys.com Organization: Opersys inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en, fr, fr-be, fr-ca, fr-fr MIME-Version: 1.0 To: Amit CC: Linux Kernel Mailing List Subject: Re: kernel 2.4.16 References: <1080849830.91ac1e3f85274@system.cs.fsu.edu> <406C79E4.1060700@opersys.com> <1081012426.5c22c66499b13@system.cs.fsu.edu> <406F21CB.8070908@opersys.com> <1081026049.f64d5288b5aaa@system.cs.fsu.edu> <406F2851.6050304@opersys.com> <003b01c419d0$67e59e50$af7aa8c0@VALUED65BAD02C> <406F476D.8050002@opersys.com> <005901c419d5$5ecd7c70$af7aa8c0@VALUED65BAD02C> In-Reply-To: <005901c419d5$5ecd7c70$af7aa8c0@VALUED65BAD02C> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1829 Lines: 41 Amit wrote: > The installation has gone through smoothly and I have managed to get an > linux-2.6.3 up and running with LTT. > I checked the documentation and it says that I need to do an insmod on the > tracer but I have compiled it as a part of the kernel. Now the documentation > says that I should execute the createdev.sh to create the devices. When I > execute that I get errors related to tracer. When I try to execute the > tracedaemon I get that relayfs is not mounted. Can you please tell me how to > go about doing the first part. After doing all this I want to run some test > cases and see how does LTT generate traces. Later on I would also like to > add rtai to this and see the traces from that too. The documentation is out of date. Basically, the createdev.sh script isn't needed anymore because of relayfs. You need to mount relayfs to use LTT. See the classic dox on filesystem mounting for this kind of thing. It's going to be something like: # mount -t relayfs nodev /mnt/relay There's no insmod for LTT. It isn't a device driver module, following LKML recommendations. As for RTAI, there's currently no RTAI support in relayfs. If you want to have RTAI tracing, then you'd have to fall back on earlier stable versions of LTT. > PS. I would like to write down a small howto on this and pass it on to you > so that newbies like me can have a good ref. Thanks for the help. Sure. Karim -- Author, Speaker, Developer, Consultant Pushing Embedded and Real-Time Linux Systems Beyond the Limits http://www.opersys.com || karim@opersys.com || 1-866-677-4546 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/