Here is one nice write about gcc.
Linux kernel actively use __attribute__ all over the places. Here is a nice introduction and also with links to complete reference.
see how rich VC and tech guys do social networking
VMWware server 1.0.1 build-29996 can not install flawlessly on FC6 with kernel 2.6.19-1.2911.fc6. Need some simple hack.
* Linux kernel version magic dismatch. You will dmesg show your something like “vmmon: version magic ’2.6.19-1.2911.fc6 SMP mod_unload 686 REGPARM 4KSTACKS ‘ should be ’2.6.19-1.2911.fc6 SMP mod_unload 586 REGPARM 4KSTACKS “. I modified the include/asm/module.h file, changed #elif defined CONFIG_M686 #define MODULE_PROC_FAMILY “686 ” to “586 “
* module compilation failure. change vmnet source by following http://www.abclinuxu.cz/blog/tucnacek/2006/12/6/160636. also need to link autoconf.h to config.h under include/linux in kernel source code.
Setup kgdb with supported kernel is quite straight forward by following the document. But there do have some small roadblocks, especially when you try to run the Linux as a VM in VMWare server.
- With 2.6.8 or later kernel, you will not see “Waiting for connection from remote gdb…”, as pointed out at here. I was panic for a while when I could not figure out where the kernel stopped at;
- Setup VMWare virtual serial port by following this.
- Tricky: by default, kgdb over serial will use serial port 1 in CONFIG_KGDB_PORT_NUM, which is 2nd serial port. Had better change this to serial port 0, which is 1st serial port. The reason is we, at least I, usually add only 1 serial port in VMWare server…
- kdgb cvs 02/07/2007 version can apply cleanly on 2.6.17 and runs ok.
- kgdb latest can be found via “git clone git://www.kernel.org/pub/scm/linux/kernel/git/trini/linux-2.6-kgdb-testing.git”, as of 02/07/07, it is based on 2.6.18
Linux has a complete remote serial console how to available. So why need another one?
- I just need a really simple guide to finish my work. And later when my 256KB main brain memory overflow, I can pick it up quickly.
- I also want to run Linux virtual machine within VMWare server using virtual serial console support from VMWare.
Let us call the Linux virtual machine as “target” and Linux host running VMWare as “host”:
Target side: [most c&p from previously mentioned howto]
- To enable kernel support. Select Y for -> Device Drivers-> Character devices-> Serial drivers-> 8250/16550 and compatible serial support (SERIAL_8250 [=y]). Recompile kernel.
- To add kernel run time parameter. Modify grub.conf and use parameter like “title 126.96.36.199 root (hd0,0) kernel /vmlinuz-188.8.131.52 ro root=/dev/sda3 console=ttyS0,9600n8 console=tty0″. These are recommended parameters. 9600 baud rate, no parity bit, 8 bit data bit, 1 stop bit, no flow control. Also leave the original tty0 usable. Of course, faster baud rate like 57600 will be better.
- Check and make sure mgetty is installed.
- To enable login prompt. Add one line in /etc/inittab “S0:23:respawn:/sbin/mgetty ttyS0″. Modify /etc/mgetty+sendfax/mgetty.config. Add “port ttyS0 speed 9600 direct yes data-only yes toggle-dtr yes need-dsr yes port-owner root port-group root port-mode 600 login-prompt @ \P login:40 login-time 60 term vt102″
- To enable root login. Add ttyS0 to /etc/securetty.
VMWare VM setting:
- [C&P from here]. Power down your virtual machine and click “Edit Virtual Machine Settings”. Add a serial port, select “Connect to named pipe”, and provide the pipe name “/tmp/com_1″. (note that this isn’t really a named pipe, but a Unix-domain socket) Click “advanced settings” and set “yield CPU on poll”. You can also get to this setting from the device list once you finish adding the port.
- You can start the Linux VM now.
- Install socat from here.
- run “socat -d -d /tmp/com_1 PTY:”. socat should report something like “PTY is /dev/pts/x”.
- start minicom, configure it with right serial port setting, save the configuration and run it.
- now from minicom should get a full functional console. Sometime need to be patient to wait the login console appear.
Note: VMWare allows a serial port to be (1) physical port, (2) output to file, and (3) named pipe. So if we only need to capture console output like oops or boot message, we can use (2) to output to foo, and do “tail -f foo” in host.