General :: Differences Between LTIB And Menuconfig Tools?
Feb 21, 2010
I am interested in kernel configuration and compilation, so I have executed ltib and menuconfig, but I am not sure to understand what is the difference between Linux Target Image Builder and the Menuconfig tool? Is menuconfig used by or included in ltib? I understand that both tools generate a kernel, But I guess ltib can process "something more"? (packages/target selection? )
First, I'm trying to cross compile mono 2.6.4 so that it will run on Freescale Embedded Linux for a PowerPC CPU. My host machine is running Fedora 13 on an x86. Freescale provides a copy of the Linux Target Image Builder (LTIB) that has been pre-configured for the particular board I'm using, and LTIB seems to be able to help with the cross compilation of other stuff--you can add in your own packages to be built and included in your newly-built Linux image.
Mono depends on pkg-config and glib-2, so I have selected them in the LTIB package selection config. I've also added a new package for mono that builds mono-2.6.4 from the source tar (after the other deps have also been built).
I'm having a problem getting the glib-2.24.0 package libraries created. Basically they appear to build and link ok, but then libtool runs and errors out claiming it has a syntax error! (numerous wths followed...)
Here is LTIB's temporary build script for only the glib2 package:
Here is the output when building the glib2 package (configure + make):
Build path taken because: directory build, build key set, no prebuilt rpm,
Is there any way to record kernel menuconfig screens? I would like to have a record of the configuration as it looks to the menuconfig screen user, with each successive sub-menu indented. Copy and paste gets the data but the frame/box drawing characters are messy. Here's the first menu:
I need to modify fs/open.c and fs/read_write.c to make my modifications. I cannot find any options in 'make menuconfig' to make these files modules rather than compiled elements. I'm thinking these cannot be modules because the file system won't work without open.c and read_write.c. Is this correct - I cannot compile fs/open.c and fs/read_write.c as modules, only as compiled elements? Or, is there some way for a module to overwrite these routines when the module is installed and re-enable the routines when the module is removed?
I have a proprietary device - something like an iPad screen - which has a front panel display with touchscreen buttons that work internally as a USB keyboard. During testing/debugging I want to connect it to another keyboard via the external USB port.Any application which I open on the device by pressing some characters on the touchscreen accepts input codes from either USB keyboard. I want to limit the touchscreen USB keyboard input only to a specific set of apps.Is there a program which can help me detect which USB port or device the code is coming from? Or someway I can map one keyboard to send a different set of codes? The device is using Linux.
My old Intrepid box got old and senile in the hardware, so I had to take it back round the shed and put her down.I buried her next to her favorite tree in the backyard. So yes, I got this new Mini ITX setup with a dual core Atom processor and 4 gigs of ram for my new computer. I'm going to use it as a media center in my living room. However Atom 1.6 ghz is no screamer so I'd like to build a system using a light weight operating environment to leave more power for running programs and playing my media.
I could install the latest version of Kubuntu again but I thought this time I'd try to get a bit deeper into Linux and educate myself. Could someone clarify the differences between XFree86, Window Manager, and a Desktop Environment (KDE/GNOME/etc)? I know it goes like Hardware -> XServer -> XFree86 -> Window Manager (I read the tutorial on linux.org). But where does KDE or a "Desktop Environment" come in? Is KDE a decked out window manager with its own programs that runs on top of XFree86 or what? Or does it totally replace XFree86?
I took the simple approach and installed the gnome desktop, but I have read about KDE and Xfce and am curious. There may be a lot more that I just haven't heard about yet too. So the question is: Without doing a reinstall and messing up the downloads and settings I have now, how do I try a new desktop like Xfce or Kde? Also, what are the basic differences between the desktops?
What are the differences between shell , console & terminal?
This probably sounds like a stupid question but I'm having a lot of trouble clearly differentiating between a shell (such as Bourne or bash) and the Terminal application in GNOME. I realise that both are completely different but I can't seem to find a clear answer written in text. Could anyone clearly distinguish between both?
I have come across the use of the term terminal, virtual terminals/consoles, real-text terminals but do not understand what terminal refers to. Does it refer to the screen that is in-front of me whilst I post this question or does it refer to something specific?EDITI came across a similar post at What are the differences between shell , console & terminal? and it seems to be similar to the one I posted although am still confused about the use of the sentence Decades ago, this was a physical device consisting of little more than a monitor and keyboard. What does this device look like and how is different to a monitor?
1. similar nos in both the file 1 and file 2 > output= File 3; 2. In file 1, but not in file 2 > out put= file 4; 3. In file 2, but not in file 1 > output = file 5;
The command sdiff is giving output with symbols > < | etc, and the such output file is not clear and ready to print. I want to print directly the output files. AND ALSO TELL ME WHERE I HAVE TO WRITE AWK PROGRAMS AND HOW TO RUN IT.
I am only using the 128 character set defined in the original ANSI standard. But as a whole how are the files implmeneted differently. I am not concerned with the display, i.e. if a tab is displayed with 6 or 8 characters but the actual internal representation in memory
One differnce I've hear is the use of (Windows) vs. for line termination (Linux).
Well, let's suppose the file is very large, say 10 GB of disk space it is consuming. We perform the above steps. Which operations: cp (copying) or mv (moving) will be more efficient and less time consuming? The inode number 1566966 which was pointing to the file in my home directory is now pointing to the same file which is in some other directry, i.e. /tmp/. Isn't the inode value getting modified in some ways to point to the correct location / beginning of the data block on the hard disk? If the the physical location of the data would not change then we would not be able to free up space in our home directory. That means the mv operation is copying the file into some other location. In other words, it is also performing the cp operation first and then deleting the file from its original location, my home directory in the case above. However, when a file is copied it's inode value changes. But the mv operation is retaining the same indoe value. So, how to determine which operation - mv or cp - is more CPU-friendly or more efficient in terms of performance and time taken to perform the action?
I'm experimenting with 2.6.33-ck1 mainly because I want to try the BFS. I successfully configured and installed the patched kernel, but I'm experiencing various problems on the desktop. The biggest is Chromium not working at all, but there are several others, including graphical glitches in firefox. I'm sure I left some important module off or made a mistake for some settings My question is that is there a 2.6.33-fc12 kernel yet, and does it have a .config available? I'd like to load those settings in menuconfig and use them as a starting point to properly configure and complie a -ck patched kernel.