**** BEGIN LOGGING AT Mon Jul 07 02:59:59 2014
Jul 07 12:50:04 <ant_work> Jay7: #define MOUNTPOINT	"/mnt"
Jul 07 12:50:34 <ant_work> then
Jul 07 12:50:35 <ant_work> 	"/mnt/boot/zImage",
Jul 07 12:50:35 <ant_work> "/mnt/zImage",
Jul 07 12:50:55 <ant_work> as default_kernels[]
Jul 07 12:51:12 <ant_work> now, what if we do mount in /boot?
Jul 07 19:49:44 <Jay7> ant: it will override /boot contents
Jul 07 19:50:04 <Jay7> may be dangerous in some cases I suspect
Jul 07 22:19:35 <ant__> Jay7, ehmm
Jul 07 22:19:42 <ant__> what does it mean?
Jul 07 22:19:43 <ant__> #define MOUNTPOINT "/mnt"
Jul 07 22:19:43 <ant__> #define BOOTCFG_PATH MOUNTPOINT "/boot/boot.cfg"
Jul 07 22:19:48 <ant__> ^
Jul 07 22:21:49 <ant__> used only once
Jul 07 22:21:51 <ant__> devicescan.c:	if (0 == parse_cfgfile(BOOTCFG_PATH, cfgdata)) {	/* Found and parsed */
Jul 07 22:25:40 <ant__> argh
Jul 07 22:25:41 <ant__> strcpy(sc->kernelpath, "/mnt");
Jul 07 22:32:07 <ant__> then
Jul 07 22:32:08 <ant__> tmp = malloc(strlen(hw) + 17 + 1);<---->/* strlen("/mnt/boot/zImage-") */
Jul 07 22:32:32 <ant__> thi sis ok for zImage and uImage..but not i.e. vmlinuz
Jul 07 22:33:11 <ant__> most of this code is in /* USE_MACHINE_KERNEL */
**** ENDING LOGGING AT Tue Jul 08 02:59:58 2014