|
View:
New views
15 Messages
—
Rating Filter:
Alert me
|
|
|
Problem building image... weirdI have had the same problem building images from RH9; not exactly true...
the images I built would not completely boot. It would stop at Init Level:. I switched to RedHat 7.3 and the images built with ./build.sh -f work. However, none of the images built would contain the name of the latest release. Example of my last build after uping my kernel to 2.4.25: (the same result with 7.3's original kernel) mkfs.msdos 2.8 (28 Feb 2001) Preparing root ... lrp md5 cramfs Preparing local ... lrp md5 Preparing zebra ... lrp md5 cramfs Preparing net-snmp ... lrp md5 cramfs Preparing sshd ... lrp md5 cramfs Preparing netdiag ... lrp md5 cramfs adding: initrd.lrp (deflated 0%) adding: ldlinux.sys (deflated 21%) adding: linux (deflated 1%) adding: local.lrp (stored 0%) adding: local.md5 (deflated 44%) adding: netdiag.cfs (deflated 0%) adding: netdiag.lrp (stored 0%) adding: netdiag.md5 (deflated 38%) adding: net-snmp.cfs (deflated 1%) adding: net-snmp.lrp (stored 0%) adding: net-snmp.md5 (deflated 46%) adding: readme (stored 0%) adding: root.cfs (deflated 0%) adding: root.lrp (deflated 0%) adding: root.md5 (deflated 49%) adding: sshd.cfs (deflated 1%) adding: sshd.lrp (deflated 1%) adding: sshd.md5 (deflated 37%) adding: syslinux.cfg (deflated 28%) adding: syslinux.dpy (stored 0%) adding: zebra.cfs (deflated 1%) adding: zebra.lrp (stored 0%) adding: zebra.md5 (deflated 44%) == Build complete. Boot image can be found at '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. Both files created: wisp-dist_1.3.1p_img.bin wisp-dist_1.3.1p_pkg.zip Question: What happened to: wisp.1.3.1p35 ? PLease help... what could I have done wrong? ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdProbably get_patchlevel() function does not return correct information for some reason. Go to source root directory and run ls -w1 \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log | sed s/patch-// What would be the output? On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: > I have had the same problem building images from RH9; not exactly true... > the images I built would not completely boot. It would stop at Init > Level:. > > I switched to RedHat 7.3 and the images built with ./build.sh -f work. > > However, none of the images built would contain the name of the latest > release. Example of my last build after uping my kernel to 2.4.25: > > (the same result with 7.3's original kernel) > > mkfs.msdos 2.8 (28 Feb 2001) > Preparing root ... lrp md5 cramfs > Preparing local ... lrp md5 > Preparing zebra ... lrp md5 cramfs > Preparing net-snmp ... lrp md5 cramfs > Preparing sshd ... lrp md5 cramfs > Preparing netdiag ... lrp md5 cramfs > adding: initrd.lrp (deflated 0%) > adding: ldlinux.sys (deflated 21%) > adding: linux (deflated 1%) > adding: local.lrp (stored 0%) > adding: local.md5 (deflated 44%) > adding: netdiag.cfs (deflated 0%) > adding: netdiag.lrp (stored 0%) > adding: netdiag.md5 (deflated 38%) > adding: net-snmp.cfs (deflated 1%) > adding: net-snmp.lrp (stored 0%) > adding: net-snmp.md5 (deflated 46%) > adding: readme (stored 0%) > adding: root.cfs (deflated 0%) > adding: root.lrp (deflated 0%) > adding: root.md5 (deflated 49%) > adding: sshd.cfs (deflated 1%) > adding: sshd.lrp (deflated 1%) > adding: sshd.md5 (deflated 37%) > adding: syslinux.cfg (deflated 28%) > adding: syslinux.dpy (stored 0%) > adding: zebra.cfs (deflated 1%) > adding: zebra.lrp (stored 0%) > adding: zebra.md5 (deflated 44%) > == Build complete. Boot image can be found at > '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. > > Both files created: > > wisp-dist_1.3.1p_img.bin > wisp-dist_1.3.1p_pkg.zip > > Question: What happened to: wisp.1.3.1p35 ? > > PLease help... what could I have done wrong? > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > leaf-wisp-dist mailing list > leaf-wisp-dist@... > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist Best Regards, Vladimir Ivashchenko Chief Technology Officer Thunderworx Cyprus - www.thunderworx.com ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdi got the same problem:
> > the images I built would not completely boot. It would stop at Init > > Level:. except that my image is wisp-dist_1.3.1p36_img.bin and before Init Level: i got echo: need libc.so.6 (GLIBC2.3) i try like Valdimir said: > Go to source root directory and run > > ls -w1 > \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... 003/patch-log | sed s/patch-// > > What would be the output? and the output is: base-0 1 10 11 12 13 14 15 16 17 18 19 2 20 21 22 23 24 25 26 27 28 29 3 30 31 32 33 34 35 36 4 5 6 7 8 9 ------------------------------------------------------------------- What does it mean ? What is my problem ? ----- Original Message ----- From: "Vladimir Ivashchenko" <hazard@...> To: <register@...> Cc: <leaf-wisp-dist@...> Sent: Thursday, February 23, 2006 11:47 AM Subject: Re: [leaf-wisp] Problem building image... weird > > Probably get_patchlevel() function does not return correct information > for some reason. > > Go to source root directory and run > > ls -w1 > \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... 003/patch-log | sed s/patch-// > > What would be the output? > > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: > > I have had the same problem building images from RH9; not exactly true... > > the images I built would not completely boot. It would stop at Init > > Level:. > > > > I switched to RedHat 7.3 and the images built with ./build.sh -f work. > > > > However, none of the images built would contain the name of the latest > > release. Example of my last build after uping my kernel to 2.4.25: > > > > (the same result with 7.3's original kernel) > > > > mkfs.msdos 2.8 (28 Feb 2001) > > Preparing root ... lrp md5 cramfs > > Preparing local ... lrp md5 > > Preparing zebra ... lrp md5 cramfs > > Preparing net-snmp ... lrp md5 cramfs > > Preparing sshd ... lrp md5 cramfs > > Preparing netdiag ... lrp md5 cramfs > > adding: initrd.lrp (deflated 0%) > > adding: ldlinux.sys (deflated 21%) > > adding: linux (deflated 1%) > > adding: local.lrp (stored 0%) > > adding: local.md5 (deflated 44%) > > adding: netdiag.cfs (deflated 0%) > > adding: netdiag.lrp (stored 0%) > > adding: netdiag.md5 (deflated 38%) > > adding: net-snmp.cfs (deflated 1%) > > adding: net-snmp.lrp (stored 0%) > > adding: net-snmp.md5 (deflated 46%) > > adding: readme (stored 0%) > > adding: root.cfs (deflated 0%) > > adding: root.lrp (deflated 0%) > > adding: root.md5 (deflated 49%) > > adding: sshd.cfs (deflated 1%) > > adding: sshd.lrp (deflated 1%) > > adding: sshd.md5 (deflated 37%) > > adding: syslinux.cfg (deflated 28%) > > adding: syslinux.dpy (stored 0%) > > adding: zebra.cfs (deflated 1%) > > adding: zebra.lrp (stored 0%) > > adding: zebra.md5 (deflated 44%) > > == Build complete. Boot image can be found at > > '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. > > > > Both files created: > > > > wisp-dist_1.3.1p_img.bin > > wisp-dist_1.3.1p_pkg.zip > > > > Question: What happened to: wisp.1.3.1p35 ? > > > > PLease help... what could I have done wrong? > > > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > that extends applications into web and mobile media. Attend the live webcast > > and join the prime developer group breaking into this new coding territory! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > > _______________________________________________ > > leaf-wisp-dist mailing list > > leaf-wisp-dist@... > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > -- > Best Regards, > Vladimir Ivashchenko > Chief Technology Officer > Thunderworx Cyprus - www.thunderworx.com > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > leaf-wisp-dist mailing list > leaf-wisp-dist@... > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdSome precision about the stop at the Init Level: line
Just before i can read no inittab found that's the reason why it stock i guess, but what is wrong in the installation ? Did i miss a step ? ----- Original Message ----- From: "Michael Plourde" <mplourde@...> To: "Vladimir Ivashchenko" <hazard@...>; <register@...> Cc: <leaf-wisp-dist@...> Sent: Thursday, February 23, 2006 2:12 PM Subject: Re: [leaf-wisp] Problem building image... weird > i got the same problem: > > > the images I built would not completely boot. It would stop at Init > > > Level:. > except that my image is wisp-dist_1.3.1p36_img.bin > and before Init Level: i got > echo: need libc.so.6 (GLIBC2.3) > > > i try like Valdimir said: > > Go to source root directory and run > > > > ls -w1 > > > > 003/patch-log | sed s/patch-// > > > > What would be the output? > and the output is: > base-0 > 1 > 10 > 11 > 12 > 13 > 14 > 15 > 16 > 17 > 18 > 19 > 2 > 20 > 21 > 22 > 23 > 24 > 25 > 26 > 27 > 28 > 29 > 3 > 30 > 31 > 32 > 33 > 34 > 35 > 36 > 4 > 5 > 6 > 7 > 8 > 9 > ------------------------------------------------------------------- > > What does it mean ? > What is my problem ? > > ----- Original Message ----- > From: "Vladimir Ivashchenko" <hazard@...> > To: <register@...> > Cc: <leaf-wisp-dist@...> > Sent: Thursday, February 23, 2006 11:47 AM > Subject: Re: [leaf-wisp] Problem building image... weird > > > > > > Probably get_patchlevel() function does not return correct information > > for some reason. > > > > Go to source root directory and run > > > > ls -w1 > > > > 003/patch-log | sed s/patch-// > > > > What would be the output? > > > > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: > > > I have had the same problem building images from RH9; not exactly > true... > > > the images I built would not completely boot. It would stop at Init > > > Level:. > > > > > > I switched to RedHat 7.3 and the images built with ./build.sh -f work. > > > > > > However, none of the images built would contain the name of the latest > > > release. Example of my last build after uping my kernel to 2.4.25: > > > > > > (the same result with 7.3's original kernel) > > > > > > mkfs.msdos 2.8 (28 Feb 2001) > > > Preparing root ... lrp md5 cramfs > > > Preparing local ... lrp md5 > > > Preparing zebra ... lrp md5 cramfs > > > Preparing net-snmp ... lrp md5 cramfs > > > Preparing sshd ... lrp md5 cramfs > > > Preparing netdiag ... lrp md5 cramfs > > > adding: initrd.lrp (deflated 0%) > > > adding: ldlinux.sys (deflated 21%) > > > adding: linux (deflated 1%) > > > adding: local.lrp (stored 0%) > > > adding: local.md5 (deflated 44%) > > > adding: netdiag.cfs (deflated 0%) > > > adding: netdiag.lrp (stored 0%) > > > adding: netdiag.md5 (deflated 38%) > > > adding: net-snmp.cfs (deflated 1%) > > > adding: net-snmp.lrp (stored 0%) > > > adding: net-snmp.md5 (deflated 46%) > > > adding: readme (stored 0%) > > > adding: root.cfs (deflated 0%) > > > adding: root.lrp (deflated 0%) > > > adding: root.md5 (deflated 49%) > > > adding: sshd.cfs (deflated 1%) > > > adding: sshd.lrp (deflated 1%) > > > adding: sshd.md5 (deflated 37%) > > > adding: syslinux.cfg (deflated 28%) > > > adding: syslinux.dpy (stored 0%) > > > adding: zebra.cfs (deflated 1%) > > > adding: zebra.lrp (stored 0%) > > > adding: zebra.md5 (deflated 44%) > > > == Build complete. Boot image can be found at > > > '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. > > > > > > Both files created: > > > > > > wisp-dist_1.3.1p_img.bin > > > wisp-dist_1.3.1p_pkg.zip > > > > > > Question: What happened to: wisp.1.3.1p35 ? > > > > > > PLease help... what could I have done wrong? > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > > > that extends applications into web and mobile media. Attend the live > webcast > > > and join the prime developer group breaking into this new coding > territory! > > > > > > _______________________________________________ > > > leaf-wisp-dist mailing list > > > leaf-wisp-dist@... > > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > -- > > Best Regards, > > Vladimir Ivashchenko > > Chief Technology Officer > > Thunderworx Cyprus - www.thunderworx.com > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > > that extends applications into web and mobile media. Attend the live > webcast > > and join the prime developer group breaking into this new coding > territory! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > > _______________________________________________ > > leaf-wisp-dist mailing list > > leaf-wisp-dist@... > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > leaf-wisp-dist mailing list > leaf-wisp-dist@... > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdActually do the following commands ls -w1 \{arch \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log | sed s/patch-// | sort -n | tail -n 1 ls -w1 \{arch \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log | sed s/patch-// | sort -n These commands are used to find out tree version. For some reason in your case it thinks that it is on patchlevel 1. On Thu, 2006-02-23 at 14:12 -0500, Michael Plourde wrote: > i got the same problem: > > > the images I built would not completely boot. It would stop at Init > > > Level:. > except that my image is wisp-dist_1.3.1p36_img.bin > and before Init Level: i got > echo: need libc.so.6 (GLIBC2.3) > > > i try like Valdimir said: > > Go to source root directory and run > > > > ls -w1 > > > \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... > 003/patch-log | sed s/patch-// > > > > What would be the output? > and the output is: > base-0 > 1 > 10 > 11 > 12 > 13 > 14 > 15 > 16 > 17 > 18 > 19 > 2 > 20 > 21 > 22 > 23 > 24 > 25 > 26 > 27 > 28 > 29 > 3 > 30 > 31 > 32 > 33 > 34 > 35 > 36 > 4 > 5 > 6 > 7 > 8 > 9 > ------------------------------------------------------------------- > > What does it mean ? > What is my problem ? > > ----- Original Message ----- > From: "Vladimir Ivashchenko" <hazard@...> > To: <register@...> > Cc: <leaf-wisp-dist@...> > Sent: Thursday, February 23, 2006 11:47 AM > Subject: Re: [leaf-wisp] Problem building image... weird > > > > > > Probably get_patchlevel() function does not return correct information > > for some reason. > > > > Go to source root directory and run > > > > ls -w1 > > > \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... > 003/patch-log | sed s/patch-// > > > > What would be the output? > > > > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: > > > I have had the same problem building images from RH9; not exactly > true... > > > the images I built would not completely boot. It would stop at Init > > > Level:. > > > > > > I switched to RedHat 7.3 and the images built with ./build.sh -f work. > > > > > > However, none of the images built would contain the name of the latest > > > release. Example of my last build after uping my kernel to 2.4.25: > > > > > > (the same result with 7.3's original kernel) > > > > > > mkfs.msdos 2.8 (28 Feb 2001) > > > Preparing root ... lrp md5 cramfs > > > Preparing local ... lrp md5 > > > Preparing zebra ... lrp md5 cramfs > > > Preparing net-snmp ... lrp md5 cramfs > > > Preparing sshd ... lrp md5 cramfs > > > Preparing netdiag ... lrp md5 cramfs > > > adding: initrd.lrp (deflated 0%) > > > adding: ldlinux.sys (deflated 21%) > > > adding: linux (deflated 1%) > > > adding: local.lrp (stored 0%) > > > adding: local.md5 (deflated 44%) > > > adding: netdiag.cfs (deflated 0%) > > > adding: netdiag.lrp (stored 0%) > > > adding: netdiag.md5 (deflated 38%) > > > adding: net-snmp.cfs (deflated 1%) > > > adding: net-snmp.lrp (stored 0%) > > > adding: net-snmp.md5 (deflated 46%) > > > adding: readme (stored 0%) > > > adding: root.cfs (deflated 0%) > > > adding: root.lrp (deflated 0%) > > > adding: root.md5 (deflated 49%) > > > adding: sshd.cfs (deflated 1%) > > > adding: sshd.lrp (deflated 1%) > > > adding: sshd.md5 (deflated 37%) > > > adding: syslinux.cfg (deflated 28%) > > > adding: syslinux.dpy (stored 0%) > > > adding: zebra.cfs (deflated 1%) > > > adding: zebra.lrp (stored 0%) > > > adding: zebra.md5 (deflated 44%) > > > == Build complete. Boot image can be found at > > > '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. > > > > > > Both files created: > > > > > > wisp-dist_1.3.1p_img.bin > > > wisp-dist_1.3.1p_pkg.zip > > > > > > Question: What happened to: wisp.1.3.1p35 ? > > > > > > PLease help... what could I have done wrong? > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > > > that extends applications into web and mobile media. Attend the live > webcast > > > and join the prime developer group breaking into this new coding > territory! > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > > > _______________________________________________ > > > leaf-wisp-dist mailing list > > > leaf-wisp-dist@... > > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > -- > > Best Regards, > > Vladimir Ivashchenko > > Chief Technology Officer > > Thunderworx Cyprus - www.thunderworx.com > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > > that extends applications into web and mobile media. Attend the live > webcast > > and join the prime developer group breaking into this new coding > territory! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > > _______________________________________________ > > leaf-wisp-dist mailing list > > leaf-wisp-dist@... > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > Best Regards, Vladimir Ivashchenko Chief Technology Officer Thunderworx Cyprus - www.thunderworx.com ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdProblem is with "echo: need libc.so.6 (GLIBC2.3)" Apparently indeed images built on RH9 would not work, as stock Wisp-Dist uses glibc 2.2. You can try replacing WISP-Dist's glibc 2.2 with glibc 2.3. Meaning that you need to replace following files in bin/root/prebuilt-cfs/lib libc.so.6 ld-2.2.4.so libcrypt-2.2.4.so libdl-2.2.4.so libm-2.2.4.so libnss_compat-2.2.4.so libnss_dns-2.2.4.so libnss_files-2.2.4.so libresolv-2.2.4.so libutil-2.2.4.so with their counterparts from glibc 2.3. On Thu, 2006-02-23 at 15:09 -0500, Michael Plourde wrote: > Some precision about the stop at the Init Level: line > Just before i can read no inittab found that's the reason why it stock i > guess, but what is wrong in the installation ? > Did i miss a step ? > > ----- Original Message ----- > From: "Michael Plourde" <mplourde@...> > To: "Vladimir Ivashchenko" <hazard@...>; <register@...> > Cc: <leaf-wisp-dist@...> > Sent: Thursday, February 23, 2006 2:12 PM > Subject: Re: [leaf-wisp] Problem building image... weird > > > > i got the same problem: > > > > the images I built would not completely boot. It would stop at Init > > > > Level:. > > except that my image is wisp-dist_1.3.1p36_img.bin > > and before Init Level: i got > > echo: need libc.so.6 (GLIBC2.3) > > > > > > i try like Valdimir said: > > > Go to source root directory and run > > > > > > ls -w1 > > > > > > \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... > > 003/patch-log | sed s/patch-// > > > > > > What would be the output? > > and the output is: > > base-0 > > 1 > > 10 > > 11 > > 12 > > 13 > > 14 > > 15 > > 16 > > 17 > > 18 > > 19 > > 2 > > 20 > > 21 > > 22 > > 23 > > 24 > > 25 > > 26 > > 27 > > 28 > > 29 > > 3 > > 30 > > 31 > > 32 > > 33 > > 34 > > 35 > > 36 > > 4 > > 5 > > 6 > > 7 > > 8 > > 9 > > ------------------------------------------------------------------- > > > > What does it mean ? > > What is my problem ? > > > > ----- Original Message ----- > > From: "Vladimir Ivashchenko" <hazard@...> > > To: <register@...> > > Cc: <leaf-wisp-dist@...> > > Sent: Thursday, February 23, 2006 11:47 AM > > Subject: Re: [leaf-wisp] Problem building image... weird > > > > > > > > > > Probably get_patchlevel() function does not return correct information > > > for some reason. > > > > > > Go to source root directory and run > > > > > > ls -w1 > > > > > > \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... > > 003/patch-log | sed s/patch-// > > > > > > What would be the output? > > > > > > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: > > > > I have had the same problem building images from RH9; not exactly > > true... > > > > the images I built would not completely boot. It would stop at Init > > > > Level:. > > > > > > > > I switched to RedHat 7.3 and the images built with ./build.sh -f work. > > > > > > > > However, none of the images built would contain the name of the latest > > > > release. Example of my last build after uping my kernel to 2.4.25: > > > > > > > > (the same result with 7.3's original kernel) > > > > > > > > mkfs.msdos 2.8 (28 Feb 2001) > > > > Preparing root ... lrp md5 cramfs > > > > Preparing local ... lrp md5 > > > > Preparing zebra ... lrp md5 cramfs > > > > Preparing net-snmp ... lrp md5 cramfs > > > > Preparing sshd ... lrp md5 cramfs > > > > Preparing netdiag ... lrp md5 cramfs > > > > adding: initrd.lrp (deflated 0%) > > > > adding: ldlinux.sys (deflated 21%) > > > > adding: linux (deflated 1%) > > > > adding: local.lrp (stored 0%) > > > > adding: local.md5 (deflated 44%) > > > > adding: netdiag.cfs (deflated 0%) > > > > adding: netdiag.lrp (stored 0%) > > > > adding: netdiag.md5 (deflated 38%) > > > > adding: net-snmp.cfs (deflated 1%) > > > > adding: net-snmp.lrp (stored 0%) > > > > adding: net-snmp.md5 (deflated 46%) > > > > adding: readme (stored 0%) > > > > adding: root.cfs (deflated 0%) > > > > adding: root.lrp (deflated 0%) > > > > adding: root.md5 (deflated 49%) > > > > adding: sshd.cfs (deflated 1%) > > > > adding: sshd.lrp (deflated 1%) > > > > adding: sshd.md5 (deflated 37%) > > > > adding: syslinux.cfg (deflated 28%) > > > > adding: syslinux.dpy (stored 0%) > > > > adding: zebra.cfs (deflated 1%) > > > > adding: zebra.lrp (stored 0%) > > > > adding: zebra.md5 (deflated 44%) > > > > == Build complete. Boot image can be found at > > > > '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. > > > > > > > > Both files created: > > > > > > > > wisp-dist_1.3.1p_img.bin > > > > wisp-dist_1.3.1p_pkg.zip > > > > > > > > Question: What happened to: wisp.1.3.1p35 ? > > > > > > > > PLease help... what could I have done wrong? > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > language > > > > that extends applications into web and mobile media. Attend the live > > webcast > > > > and join the prime developer group breaking into this new coding > > territory! > > > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > > > > _______________________________________________ > > > > leaf-wisp-dist mailing list > > > > leaf-wisp-dist@... > > > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > -- > > > Best Regards, > > > Vladimir Ivashchenko > > > Chief Technology Officer > > > Thunderworx Cyprus - www.thunderworx.com > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > language > > > that extends applications into web and mobile media. Attend the live > > webcast > > > and join the prime developer group breaking into this new coding > > territory! > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > > > _______________________________________________ > > > leaf-wisp-dist mailing list > > > leaf-wisp-dist@... > > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > > that extends applications into web and mobile media. Attend the live > webcast > > and join the prime developer group breaking into this new coding > territory! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > > _______________________________________________ > > leaf-wisp-dist mailing list > > leaf-wisp-dist@... > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > Best Regards, Vladimir Ivashchenko Chief Technology Officer Thunderworx Cyprus - www.thunderworx.com ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdi do
> ls -w1 \{arch > \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../p atch-log | sed s/patch-// | sort -n | tail -n 1 and the output is 36 so i'm ok with patchlevel i have try to rebuilt an image with build.sh -f and gcc-2.95 compilator to avoid need GLIBC2.3 message, but now the problem is worst i had kernel panic message ! Any idea ? Could i send you build.sh - f output ? ----- Original Message ----- From: "Vladimir Ivashchenko" <hazard@...> To: "Michael Plourde" <mplourde@...> Cc: <register@...>; <leaf-wisp-dist@...> Sent: Thursday, February 23, 2006 3:20 PM Subject: Re: [leaf-wisp] Problem building image... weird > > Actually do the following commands > > ls -w1 \{arch > \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../p atch-log | sed s/patch-// | sort -n | tail -n 1 > > ls -w1 \{arch > \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../p atch-log | sed s/patch-// | sort -n > > These commands are used to find out tree version. For some reason in > your case it thinks that it is on patchlevel 1. > > On Thu, 2006-02-23 at 14:12 -0500, Michael Plourde wrote: > > i got the same problem: > > > > the images I built would not completely boot. It would stop at Init > > > > Level:. > > except that my image is wisp-dist_1.3.1p36_img.bin > > and before Init Level: i got > > echo: need libc.so.6 (GLIBC2.3) > > > > > > i try like Valdimir said: > > > Go to source root directory and run > > > > > > ls -w1 > > > > > > > 003/patch-log | sed s/patch-// > > > > > > What would be the output? > > and the output is: > > base-0 > > 1 > > 10 > > 11 > > 12 > > 13 > > 14 > > 15 > > 16 > > 17 > > 18 > > 19 > > 2 > > 20 > > 21 > > 22 > > 23 > > 24 > > 25 > > 26 > > 27 > > 28 > > 29 > > 3 > > 30 > > 31 > > 32 > > 33 > > 34 > > 35 > > 36 > > 4 > > 5 > > 6 > > 7 > > 8 > > 9 > > ------------------------------------------------------------------- > > > > What does it mean ? > > What is my problem ? > > > > ----- Original Message ----- > > From: "Vladimir Ivashchenko" <hazard@...> > > To: <register@...> > > Cc: <leaf-wisp-dist@...> > > Sent: Thursday, February 23, 2006 11:47 AM > > Subject: Re: [leaf-wisp] Problem building image... weird > > > > > > > > > > Probably get_patchlevel() function does not return correct information > > > for some reason. > > > > > > Go to source root directory and run > > > > > > ls -w1 > > > > > > > 003/patch-log | sed s/patch-// > > > > > > What would be the output? > > > > > > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: > > > > I have had the same problem building images from RH9; not exactly > > true... > > > > the images I built would not completely boot. It would stop at Init > > > > Level:. > > > > > > > > I switched to RedHat 7.3 and the images built with ./build.sh -f > > > > > > > > However, none of the images built would contain the name of the latest > > > > release. Example of my last build after uping my kernel to 2.4.25: > > > > > > > > (the same result with 7.3's original kernel) > > > > > > > > mkfs.msdos 2.8 (28 Feb 2001) > > > > Preparing root ... lrp md5 cramfs > > > > Preparing local ... lrp md5 > > > > Preparing zebra ... lrp md5 cramfs > > > > Preparing net-snmp ... lrp md5 cramfs > > > > Preparing sshd ... lrp md5 cramfs > > > > Preparing netdiag ... lrp md5 cramfs > > > > adding: initrd.lrp (deflated 0%) > > > > adding: ldlinux.sys (deflated 21%) > > > > adding: linux (deflated 1%) > > > > adding: local.lrp (stored 0%) > > > > adding: local.md5 (deflated 44%) > > > > adding: netdiag.cfs (deflated 0%) > > > > adding: netdiag.lrp (stored 0%) > > > > adding: netdiag.md5 (deflated 38%) > > > > adding: net-snmp.cfs (deflated 1%) > > > > adding: net-snmp.lrp (stored 0%) > > > > adding: net-snmp.md5 (deflated 46%) > > > > adding: readme (stored 0%) > > > > adding: root.cfs (deflated 0%) > > > > adding: root.lrp (deflated 0%) > > > > adding: root.md5 (deflated 49%) > > > > adding: sshd.cfs (deflated 1%) > > > > adding: sshd.lrp (deflated 1%) > > > > adding: sshd.md5 (deflated 37%) > > > > adding: syslinux.cfg (deflated 28%) > > > > adding: syslinux.dpy (stored 0%) > > > > adding: zebra.cfs (deflated 1%) > > > > adding: zebra.lrp (stored 0%) > > > > adding: zebra.md5 (deflated 44%) > > > > == Build complete. Boot image can be found at > > > > '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. > > > > > > > > Both files created: > > > > > > > > wisp-dist_1.3.1p_img.bin > > > > wisp-dist_1.3.1p_pkg.zip > > > > > > > > Question: What happened to: wisp.1.3.1p35 ? > > > > > > > > PLease help... what could I have done wrong? > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > language > > > > that extends applications into web and mobile media. Attend the live > > webcast > > > > and join the prime developer group breaking into this new coding > > territory! > > > > > > > > _______________________________________________ > > > > leaf-wisp-dist mailing list > > > > leaf-wisp-dist@... > > > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > -- > > > Best Regards, > > > Vladimir Ivashchenko > > > Chief Technology Officer > > > Thunderworx Cyprus - www.thunderworx.com > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > language > > > that extends applications into web and mobile media. Attend the live > > webcast > > > and join the prime developer group breaking into this new coding > > territory! > > > > > > _______________________________________________ > > > leaf-wisp-dist mailing list > > > leaf-wisp-dist@... > > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > > -- > Best Regards, > Vladimir Ivashchenko > Chief Technology Officer > Thunderworx Cyprus - www.thunderworx.com > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > leaf-wisp-dist mailing list > leaf-wisp-dist@... > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdI'm on Debian can i use some trick to compile it in glibc 2.2 ?
----- Original Message ----- From: "Vladimir Ivashchenko" <hazard@...> To: "Michael Plourde" <mplourde@...> Cc: <register@...>; <leaf-wisp-dist@...> Sent: Thursday, February 23, 2006 3:28 PM Subject: Re: [leaf-wisp] Problem building image... weird > > Problem is with "echo: need libc.so.6 (GLIBC2.3)" > > Apparently indeed images built on RH9 would not work, as stock Wisp-Dist > uses glibc 2.2. You can try replacing WISP-Dist's glibc 2.2 with glibc > 2.3. Meaning that you need to replace following files in > bin/root/prebuilt-cfs/lib > > libc.so.6 > ld-2.2.4.so > libcrypt-2.2.4.so > libdl-2.2.4.so > libm-2.2.4.so > libnss_compat-2.2.4.so > libnss_dns-2.2.4.so > libnss_files-2.2.4.so > libresolv-2.2.4.so > libutil-2.2.4.so > > with their counterparts from glibc 2.3. > > On Thu, 2006-02-23 at 15:09 -0500, Michael Plourde wrote: > > Some precision about the stop at the Init Level: line > > Just before i can read no inittab found that's the reason why it stock i > > guess, but what is wrong in the installation ? > > Did i miss a step ? > > > > ----- Original Message ----- > > From: "Michael Plourde" <mplourde@...> > > To: "Vladimir Ivashchenko" <hazard@...>; <register@...> > > Cc: <leaf-wisp-dist@...> > > Sent: Thursday, February 23, 2006 2:12 PM > > Subject: Re: [leaf-wisp] Problem building image... weird > > > > > > > i got the same problem: > > > > > the images I built would not completely boot. It would stop at > > > > > Level:. > > > except that my image is wisp-dist_1.3.1p36_img.bin > > > and before Init Level: i got > > > echo: need libc.so.6 (GLIBC2.3) > > > > > > > > > i try like Valdimir said: > > > > Go to source root directory and run > > > > > > > > ls -w1 > > > > > > > > > > > > 003/patch-log | sed s/patch-// > > > > > > > > What would be the output? > > > and the output is: > > > base-0 > > > 1 > > > 10 > > > 11 > > > 12 > > > 13 > > > 14 > > > 15 > > > 16 > > > 17 > > > 18 > > > 19 > > > 2 > > > 20 > > > 21 > > > 22 > > > 23 > > > 24 > > > 25 > > > 26 > > > 27 > > > 28 > > > 29 > > > 3 > > > 30 > > > 31 > > > 32 > > > 33 > > > 34 > > > 35 > > > 36 > > > 4 > > > 5 > > > 6 > > > 7 > > > 8 > > > 9 > > > ------------------------------------------------------------------- > > > > > > What does it mean ? > > > What is my problem ? > > > > > > ----- Original Message ----- > > > From: "Vladimir Ivashchenko" <hazard@...> > > > To: <register@...> > > > Cc: <leaf-wisp-dist@...> > > > Sent: Thursday, February 23, 2006 11:47 AM > > > Subject: Re: [leaf-wisp] Problem building image... weird > > > > > > > > > > > > > > Probably get_patchlevel() function does not return correct > > > > for some reason. > > > > > > > > Go to source root directory and run > > > > > > > > ls -w1 > > > > > > > > > \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... > > > 003/patch-log | sed s/patch-// > > > > > > > > What would be the output? > > > > > > > > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: > > > > > I have had the same problem building images from RH9; not exactly > > > true... > > > > > the images I built would not completely boot. It would stop at Init > > > > > Level:. > > > > > > > > > > I switched to RedHat 7.3 and the images built with ./build.sh -f work. > > > > > > > > > > However, none of the images built would contain the name of the latest > > > > > release. Example of my last build after uping my kernel to 2.4.25: > > > > > > > > > > (the same result with 7.3's original kernel) > > > > > > > > > > mkfs.msdos 2.8 (28 Feb 2001) > > > > > Preparing root ... lrp md5 cramfs > > > > > Preparing local ... lrp md5 > > > > > Preparing zebra ... lrp md5 cramfs > > > > > Preparing net-snmp ... lrp md5 cramfs > > > > > Preparing sshd ... lrp md5 cramfs > > > > > Preparing netdiag ... lrp md5 cramfs > > > > > adding: initrd.lrp (deflated 0%) > > > > > adding: ldlinux.sys (deflated 21%) > > > > > adding: linux (deflated 1%) > > > > > adding: local.lrp (stored 0%) > > > > > adding: local.md5 (deflated 44%) > > > > > adding: netdiag.cfs (deflated 0%) > > > > > adding: netdiag.lrp (stored 0%) > > > > > adding: netdiag.md5 (deflated 38%) > > > > > adding: net-snmp.cfs (deflated 1%) > > > > > adding: net-snmp.lrp (stored 0%) > > > > > adding: net-snmp.md5 (deflated 46%) > > > > > adding: readme (stored 0%) > > > > > adding: root.cfs (deflated 0%) > > > > > adding: root.lrp (deflated 0%) > > > > > adding: root.md5 (deflated 49%) > > > > > adding: sshd.cfs (deflated 1%) > > > > > adding: sshd.lrp (deflated 1%) > > > > > adding: sshd.md5 (deflated 37%) > > > > > adding: syslinux.cfg (deflated 28%) > > > > > adding: syslinux.dpy (stored 0%) > > > > > adding: zebra.cfs (deflated 1%) > > > > > adding: zebra.lrp (stored 0%) > > > > > adding: zebra.md5 (deflated 44%) > > > > > == Build complete. Boot image can be found at > > > > > '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. > > > > > > > > > > Both files created: > > > > > > > > > > wisp-dist_1.3.1p_img.bin > > > > > wisp-dist_1.3.1p_pkg.zip > > > > > > > > > > Question: What happened to: wisp.1.3.1p35 ? > > > > > > > > > > PLease help... what could I have done wrong? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > > language > > > > > that extends applications into web and mobile media. Attend the > > > webcast > > > > > and join the prime developer group breaking into this new coding > > > territory! > > > > > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > > > > > _______________________________________________ > > > > > leaf-wisp-dist mailing list > > > > > leaf-wisp-dist@... > > > > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > > -- > > > > Best Regards, > > > > Vladimir Ivashchenko > > > > Chief Technology Officer > > > > Thunderworx Cyprus - www.thunderworx.com > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > > language > > > > that extends applications into web and mobile media. Attend the live > > > webcast > > > > and join the prime developer group breaking into this new coding > > > territory! > > > > > > > > _______________________________________________ > > > > leaf-wisp-dist mailing list > > > > leaf-wisp-dist@... > > > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > language > > > that extends applications into web and mobile media. Attend the live > > webcast > > > and join the prime developer group breaking into this new coding > > territory! > > > > > > _______________________________________________ > > > leaf-wisp-dist mailing list > > > leaf-wisp-dist@... > > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > > -- > Best Regards, > Vladimir Ivashchenko > Chief Technology Officer > Thunderworx Cyprus - www.thunderworx.com > > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdThe results: I ran ls -l1 |sed s/patch-// from the
{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log/ directory. My results: [root@unclescrooge patch-log]# ls -w1 |sed s/patch-// base-0 1 10 11 12 13 14 15 16 17 18 19 2 20 21 22 23 24 25 26 27 28 29 3 30 31 32 33 34 35 36 4 5 6 7 8 9 [root@unclescrooge patch-log]# pwd /root/wdist/{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log > > Probably get_patchlevel() function does not return correct information > for some reason. > > Go to source root directory and run > > ls -w1 > \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log > | sed s/patch-// > > What would be the output? > > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: >> I have had the same problem building images from RH9; not exactly >> true... the images I built would not completely boot. It would stop >> at Init Level:. >> >> I switched to RedHat 7.3 and the images built with ./build.sh -f work. >> >> However, none of the images built would contain the name of the latest >> release. Example of my last build after uping my kernel to 2.4.25: >> >> (the same result with 7.3's original kernel) >> >> mkfs.msdos 2.8 (28 Feb 2001) >> Preparing root ... lrp md5 cramfs >> Preparing local ... lrp md5 >> Preparing zebra ... lrp md5 cramfs >> Preparing net-snmp ... lrp md5 cramfs >> Preparing sshd ... lrp md5 cramfs >> Preparing netdiag ... lrp md5 cramfs >> adding: initrd.lrp (deflated 0%) >> adding: ldlinux.sys (deflated 21%) >> adding: linux (deflated 1%) >> adding: local.lrp (stored 0%) >> adding: local.md5 (deflated 44%) >> adding: netdiag.cfs (deflated 0%) >> adding: netdiag.lrp (stored 0%) >> adding: netdiag.md5 (deflated 38%) >> adding: net-snmp.cfs (deflated 1%) >> adding: net-snmp.lrp (stored 0%) >> adding: net-snmp.md5 (deflated 46%) >> adding: readme (stored 0%) >> adding: root.cfs (deflated 0%) >> adding: root.lrp (deflated 0%) >> adding: root.md5 (deflated 49%) >> adding: sshd.cfs (deflated 1%) >> adding: sshd.lrp (deflated 1%) >> adding: sshd.md5 (deflated 37%) >> adding: syslinux.cfg (deflated 28%) >> adding: syslinux.dpy (stored 0%) >> adding: zebra.cfs (deflated 1%) >> adding: zebra.lrp (stored 0%) >> adding: zebra.md5 (deflated 44%) >> == Build complete. Boot image can be found at >> '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. >> >> Both files created: >> >> wisp-dist_1.3.1p_img.bin >> wisp-dist_1.3.1p_pkg.zip >> >> Question: What happened to: wisp.1.3.1p35 ? >> >> PLease help... what could I have done wrong? >> >> >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by xPML, a groundbreaking scripting >> language that extends applications into web and mobile media. Attend >> the live webcast and join the prime developer group breaking into this >> new coding territory! >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >> _______________________________________________ >> leaf-wisp-dist mailing list >> leaf-wisp-dist@... >> https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > -- > Best Regards, > Vladimir Ivashchenko > Chief Technology Officer > Thunderworx Cyprus - www.thunderworx.com ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weird [root@unclescrooge wdist]# ls -w1
\{arch\}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log | sed s/patch-// | sort -n | tail -n 1 36 [root@unclescrooge wdist]# ls -w1 \{arch\}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log | sed s/patch-// | sort -n base-0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 > > Actually do the following commands > > ls -w1 \{arch > \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log > | sed s/patch-// | sort -n | tail -n 1 > > ls -w1 \{arch > \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log > | sed s/patch-// | sort -n > > These commands are used to find out tree version. For some reason in > your case it thinks that it is on patchlevel 1. > > On Thu, 2006-02-23 at 14:12 -0500, Michael Plourde wrote: >> i got the same problem: >> > > the images I built would not completely boot. It would stop at >> Init Level:. >> except that my image is wisp-dist_1.3.1p36_img.bin >> and before Init Level: i got >> echo: need libc.so.6 (GLIBC2.3) >> >> >> i try like Valdimir said: >> > Go to source root directory and run >> > >> > ls -w1 >> > >> \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... >> 003/patch-log | sed s/patch-// >> > >> > What would be the output? >> and the output is: >> base-0 >> 1 >> 10 >> 11 >> 12 >> 13 >> 14 >> 15 >> 16 >> 17 >> 18 >> 19 >> 2 >> 20 >> 21 >> 22 >> 23 >> 24 >> 25 >> 26 >> 27 >> 28 >> 29 >> 3 >> 30 >> 31 >> 32 >> 33 >> 34 >> 35 >> 36 >> 4 >> 5 >> 6 >> 7 >> 8 >> 9 >> ------------------------------------------------------------------- >> >> What does it mean ? >> What is my problem ? >> >> ----- Original Message ----- >> From: "Vladimir Ivashchenko" <hazard@...> >> To: <register@...> >> Cc: <leaf-wisp-dist@...> >> Sent: Thursday, February 23, 2006 11:47 AM >> Subject: Re: [leaf-wisp] Problem building image... weird >> >> >> > >> > Probably get_patchlevel() function does not return correct >> information for some reason. >> > >> > Go to source root directory and run >> > >> > ls -w1 >> > >> \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... >> 003/patch-log | sed s/patch-// >> > >> > What would be the output? >> > >> > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: >> > > I have had the same problem building images from RH9; not exactly >> true... >> > > the images I built would not completely boot. It would stop at >> Init Level:. >> > > >> > > I switched to RedHat 7.3 and the images built with ./build.sh -f >> work. >> > > >> > > However, none of the images built would contain the name of the >> latest release. Example of my last build after uping my kernel to >> 2.4.25: >> > > >> > > (the same result with 7.3's original kernel) >> > > >> > > mkfs.msdos 2.8 (28 Feb 2001) >> > > Preparing root ... lrp md5 cramfs >> > > Preparing local ... lrp md5 >> > > Preparing zebra ... lrp md5 cramfs >> > > Preparing net-snmp ... lrp md5 cramfs >> > > Preparing sshd ... lrp md5 cramfs >> > > Preparing netdiag ... lrp md5 cramfs >> > > adding: initrd.lrp (deflated 0%) >> > > adding: ldlinux.sys (deflated 21%) >> > > adding: linux (deflated 1%) >> > > adding: local.lrp (stored 0%) >> > > adding: local.md5 (deflated 44%) >> > > adding: netdiag.cfs (deflated 0%) >> > > adding: netdiag.lrp (stored 0%) >> > > adding: netdiag.md5 (deflated 38%) >> > > adding: net-snmp.cfs (deflated 1%) >> > > adding: net-snmp.lrp (stored 0%) >> > > adding: net-snmp.md5 (deflated 46%) >> > > adding: readme (stored 0%) >> > > adding: root.cfs (deflated 0%) >> > > adding: root.lrp (deflated 0%) >> > > adding: root.md5 (deflated 49%) >> > > adding: sshd.cfs (deflated 1%) >> > > adding: sshd.lrp (deflated 1%) >> > > adding: sshd.md5 (deflated 37%) >> > > adding: syslinux.cfg (deflated 28%) >> > > adding: syslinux.dpy (stored 0%) >> > > adding: zebra.cfs (deflated 1%) >> > > adding: zebra.lrp (stored 0%) >> > > adding: zebra.md5 (deflated 44%) >> > > == Build complete. Boot image can be found at >> > > '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. >> > > >> > > Both files created: >> > > >> > > wisp-dist_1.3.1p_img.bin >> > > wisp-dist_1.3.1p_pkg.zip >> > > >> > > Question: What happened to: wisp.1.3.1p35 ? >> > > >> > > PLease help... what could I have done wrong? >> > > >> > > >> > > >> > > >> > > >> > > ------------------------------------------------------- >> > > This SF.Net email is sponsored by xPML, a groundbreaking scripting >> language >> > > that extends applications into web and mobile media. Attend the >> live >> webcast >> > > and join the prime developer group breaking into this new coding >> territory! >> > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >> _______________________________________________ >> > > leaf-wisp-dist mailing list >> > > leaf-wisp-dist@... >> > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist >> > -- >> > Best Regards, >> > Vladimir Ivashchenko >> > Chief Technology Officer >> > Thunderworx Cyprus - www.thunderworx.com >> > >> > >> > >> > ------------------------------------------------------- >> > This SF.Net email is sponsored by xPML, a groundbreaking scripting >> language >> > that extends applications into web and mobile media. Attend the live >> webcast >> > and join the prime developer group breaking into this new coding >> territory! >> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >> _______________________________________________ >> > leaf-wisp-dist mailing list >> > leaf-wisp-dist@... >> > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist >> > > -- > Best Regards, > Vladimir Ivashchenko > Chief Technology Officer > Thunderworx Cyprus - www.thunderworx.com > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language that extends applications into web and mobile media. Attend the > live webcast and join the prime developer group breaking into this new > coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > leaf-wisp-dist mailing list > leaf-wisp-dist@... > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdVladimir,
Permissions on the files common.sh and common-config.sh are not executable. Would what have any bearing? -Boatner > > Probably get_patchlevel() function does not return correct information > for some reason. > > Go to source root directory and run > > ls -w1 > \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log > | sed s/patch-// > > What would be the output? > > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: >> I have had the same problem building images from RH9; not exactly >> true... the images I built would not completely boot. It would stop >> at Init Level:. >> >> I switched to RedHat 7.3 and the images built with ./build.sh -f work. >> >> However, none of the images built would contain the name of the latest >> release. Example of my last build after uping my kernel to 2.4.25: >> >> (the same result with 7.3's original kernel) >> >> mkfs.msdos 2.8 (28 Feb 2001) >> Preparing root ... lrp md5 cramfs >> Preparing local ... lrp md5 >> Preparing zebra ... lrp md5 cramfs >> Preparing net-snmp ... lrp md5 cramfs >> Preparing sshd ... lrp md5 cramfs >> Preparing netdiag ... lrp md5 cramfs >> adding: initrd.lrp (deflated 0%) >> adding: ldlinux.sys (deflated 21%) >> adding: linux (deflated 1%) >> adding: local.lrp (stored 0%) >> adding: local.md5 (deflated 44%) >> adding: netdiag.cfs (deflated 0%) >> adding: netdiag.lrp (stored 0%) >> adding: netdiag.md5 (deflated 38%) >> adding: net-snmp.cfs (deflated 1%) >> adding: net-snmp.lrp (stored 0%) >> adding: net-snmp.md5 (deflated 46%) >> adding: readme (stored 0%) >> adding: root.cfs (deflated 0%) >> adding: root.lrp (deflated 0%) >> adding: root.md5 (deflated 49%) >> adding: sshd.cfs (deflated 1%) >> adding: sshd.lrp (deflated 1%) >> adding: sshd.md5 (deflated 37%) >> adding: syslinux.cfg (deflated 28%) >> adding: syslinux.dpy (stored 0%) >> adding: zebra.cfs (deflated 1%) >> adding: zebra.lrp (stored 0%) >> adding: zebra.md5 (deflated 44%) >> == Build complete. Boot image can be found at >> '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. >> >> Both files created: >> >> wisp-dist_1.3.1p_img.bin >> wisp-dist_1.3.1p_pkg.zip >> >> Question: What happened to: wisp.1.3.1p35 ? >> >> PLease help... what could I have done wrong? >> >> >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by xPML, a groundbreaking scripting >> language that extends applications into web and mobile media. Attend >> the live webcast and join the prime developer group breaking into this >> new coding territory! >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >> _______________________________________________ >> leaf-wisp-dist mailing list >> leaf-wisp-dist@... >> https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > -- > Best Regards, > Vladimir Ivashchenko > Chief Technology Officer > Thunderworx Cyprus - www.thunderworx.com > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language that extends applications into web and mobile media. Attend the > live webcast and join the prime developer group breaking into this new > coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > leaf-wisp-dist mailing list > leaf-wisp-dist@... > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdAh! I found the problem... build.sh does not know where tla is (for that
matter, I don't know right now either :-\ ) I'll fix that problem and let you know if that works. -Boatner > [root@unclescrooge wdist]# ls -w1 > \{arch\}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log > | sed s/patch-// | sort -n | tail -n 1 > 36 > [root@unclescrooge wdist]# ls -w1 > \{arch\}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log > | sed s/patch-// | sort -n > base-0 > 1 > 2 > 3 > 4 > 5 > 6 > 7 > 8 > 9 > 10 > 11 > 12 > 13 > 14 > 15 > 16 > 17 > 18 > 19 > 20 > 21 > 22 > 23 > 24 > 25 > 26 > 27 > 28 > 29 > 30 > 31 > 32 > 33 > 34 > 35 > 36 > >> >> Actually do the following commands >> >> ls -w1 \{arch >> \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log >> | sed s/patch-// | sort -n | tail -n 1 >> >> ls -w1 \{arch >> \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log >> | sed s/patch-// | sort -n >> >> These commands are used to find out tree version. For some reason in >> your case it thinks that it is on patchlevel 1. >> >> On Thu, 2006-02-23 at 14:12 -0500, Michael Plourde wrote: >>> i got the same problem: >>> > > the images I built would not completely boot. It would stop at >>> Init Level:. >>> except that my image is wisp-dist_1.3.1p36_img.bin >>> and before Init Level: i got >>> echo: need libc.so.6 (GLIBC2.3) >>> >>> >>> i try like Valdimir said: >>> > Go to source root directory and run >>> > >>> > ls -w1 >>> > >>> \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... >>> 003/patch-log | sed s/patch-// >>> > >>> > What would be the output? >>> and the output is: >>> base-0 >>> 1 >>> 10 >>> 11 >>> 12 >>> 13 >>> 14 >>> 15 >>> 16 >>> 17 >>> 18 >>> 19 >>> 2 >>> 20 >>> 21 >>> 22 >>> 23 >>> 24 >>> 25 >>> 26 >>> 27 >>> 28 >>> 29 >>> 3 >>> 30 >>> 31 >>> 32 >>> 33 >>> 34 >>> 35 >>> 36 >>> 4 >>> 5 >>> 6 >>> 7 >>> 8 >>> 9 >>> ------------------------------------------------------------------- >>> >>> What does it mean ? >>> What is my problem ? >>> >>> ----- Original Message ----- >>> From: "Vladimir Ivashchenko" <hazard@...> >>> To: <register@...> >>> Cc: <leaf-wisp-dist@...> >>> Sent: Thursday, February 23, 2006 11:47 AM >>> Subject: Re: [leaf-wisp] Problem building image... weird >>> >>> >>> > >>> > Probably get_patchlevel() function does not return correct >>> information for some reason. >>> > >>> > Go to source root directory and run >>> > >>> > ls -w1 >>> > >>> \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... >>> 003/patch-log | sed s/patch-// >>> > >>> > What would be the output? >>> > >>> > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: >>> > > I have had the same problem building images from RH9; not exactly >>> true... >>> > > the images I built would not completely boot. It would stop at >>> Init Level:. >>> > > >>> > > I switched to RedHat 7.3 and the images built with ./build.sh -f >>> work. >>> > > >>> > > However, none of the images built would contain the name of the >>> latest release. Example of my last build after uping my kernel to >>> 2.4.25: >>> > > >>> > > (the same result with 7.3's original kernel) >>> > > >>> > > mkfs.msdos 2.8 (28 Feb 2001) >>> > > Preparing root ... lrp md5 cramfs >>> > > Preparing local ... lrp md5 >>> > > Preparing zebra ... lrp md5 cramfs >>> > > Preparing net-snmp ... lrp md5 cramfs >>> > > Preparing sshd ... lrp md5 cramfs >>> > > Preparing netdiag ... lrp md5 cramfs >>> > > adding: initrd.lrp (deflated 0%) >>> > > adding: ldlinux.sys (deflated 21%) >>> > > adding: linux (deflated 1%) >>> > > adding: local.lrp (stored 0%) >>> > > adding: local.md5 (deflated 44%) >>> > > adding: netdiag.cfs (deflated 0%) >>> > > adding: netdiag.lrp (stored 0%) >>> > > adding: netdiag.md5 (deflated 38%) >>> > > adding: net-snmp.cfs (deflated 1%) >>> > > adding: net-snmp.lrp (stored 0%) >>> > > adding: net-snmp.md5 (deflated 46%) >>> > > adding: readme (stored 0%) >>> > > adding: root.cfs (deflated 0%) >>> > > adding: root.lrp (deflated 0%) >>> > > adding: root.md5 (deflated 49%) >>> > > adding: sshd.cfs (deflated 1%) >>> > > adding: sshd.lrp (deflated 1%) >>> > > adding: sshd.md5 (deflated 37%) >>> > > adding: syslinux.cfg (deflated 28%) >>> > > adding: syslinux.dpy (stored 0%) >>> > > adding: zebra.cfs (deflated 1%) >>> > > adding: zebra.lrp (stored 0%) >>> > > adding: zebra.md5 (deflated 44%) >>> > > == Build complete. Boot image can be found at >>> > > '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. >>> > > >>> > > Both files created: >>> > > >>> > > wisp-dist_1.3.1p_img.bin >>> > > wisp-dist_1.3.1p_pkg.zip >>> > > >>> > > Question: What happened to: wisp.1.3.1p35 ? >>> > > >>> > > PLease help... what could I have done wrong? >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > ------------------------------------------------------- >>> > > This SF.Net email is sponsored by xPML, a groundbreaking >>> scripting >>> language >>> > > that extends applications into web and mobile media. Attend the >>> live >>> webcast >>> > > and join the prime developer group breaking into this new coding >>> territory! >>> > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >>> _______________________________________________ >>> > > leaf-wisp-dist mailing list >>> > > leaf-wisp-dist@... >>> > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist >>> > -- >>> > Best Regards, >>> > Vladimir Ivashchenko >>> > Chief Technology Officer >>> > Thunderworx Cyprus - www.thunderworx.com >>> > >>> > >>> > >>> > ------------------------------------------------------- >>> > This SF.Net email is sponsored by xPML, a groundbreaking scripting >>> language >>> > that extends applications into web and mobile media. Attend the >>> live >>> webcast >>> > and join the prime developer group breaking into this new coding >>> territory! >>> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >>> _______________________________________________ >>> > leaf-wisp-dist mailing list >>> > leaf-wisp-dist@... >>> > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist >>> > >> -- >> Best Regards, >> Vladimir Ivashchenko >> Chief Technology Officer >> Thunderworx Cyprus - www.thunderworx.com >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by xPML, a groundbreaking scripting >> language that extends applications into web and mobile media. Attend >> the live webcast and join the prime developer group breaking into this >> new coding territory! >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >> _______________________________________________ >> leaf-wisp-dist mailing list >> leaf-wisp-dist@... >> https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdThat was the answer, Hooray! (i'm a dummy). I saved a partition with all
my downloaded tar files and directory trees so it would not have to be downloaded again. Apparently I also kept the binary: tla, which was compiled on my original RH9. Sorry for the false alarm. I appreciate all your selfless work, Vladimir. With my kindest regards, Boatner Howell > Ah! I found the problem... build.sh does not know where tla is (for > that matter, I don't know right now either :-\ ) > > I'll fix that problem and let you know if that works. > > -Boatner > > > >> [root@unclescrooge wdist]# ls -w1 >> \{arch\}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log >> | sed s/patch-// | sort -n | tail -n 1 >> 36 >> [root@unclescrooge wdist]# ls -w1 >> \{arch\}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log >> | sed s/patch-// | sort -n >> base-0 >> 1 >> 2 >> 3 >> 4 >> 5 >> 6 >> 7 >> 8 >> 9 >> 10 >> 11 >> 12 >> 13 >> 14 >> 15 >> 16 >> 17 >> 18 >> 19 >> 20 >> 21 >> 22 >> 23 >> 24 >> 25 >> 26 >> 27 >> 28 >> 29 >> 30 >> 31 >> 32 >> 33 >> 34 >> 35 >> 36 >> >>> >>> Actually do the following commands >>> >>> ls -w1 \{arch >>> \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log >>> | sed s/patch-// | sort -n | tail -n 1 >>> >>> ls -w1 \{arch >>> \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log >>> | sed s/patch-// | sort -n >>> >>> These commands are used to find out tree version. For some reason in >>> your case it thinks that it is on patchlevel 1. >>> >>> On Thu, 2006-02-23 at 14:12 -0500, Michael Plourde wrote: >>>> i got the same problem: >>>> > > the images I built would not completely boot. It would stop at >>>> Init Level:. >>>> except that my image is wisp-dist_1.3.1p36_img.bin >>>> and before Init Level: i got >>>> echo: need libc.so.6 (GLIBC2.3) >>>> >>>> >>>> i try like Valdimir said: >>>> > Go to source root directory and run >>>> > >>>> > ls -w1 >>>> > >>>> \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... >>>> 003/patch-log | sed s/patch-// >>>> > >>>> > What would be the output? >>>> and the output is: >>>> base-0 >>>> 1 >>>> 10 >>>> 11 >>>> 12 >>>> 13 >>>> 14 >>>> 15 >>>> 16 >>>> 17 >>>> 18 >>>> 19 >>>> 2 >>>> 20 >>>> 21 >>>> 22 >>>> 23 >>>> 24 >>>> 25 >>>> 26 >>>> 27 >>>> 28 >>>> 29 >>>> 3 >>>> 30 >>>> 31 >>>> 32 >>>> 33 >>>> 34 >>>> 35 >>>> 36 >>>> 4 >>>> 5 >>>> 6 >>>> 7 >>>> 8 >>>> 9 >>>> ------------------------------------------------------------------- >>>> >>>> What does it mean ? >>>> What is my problem ? >>>> >>>> ----- Original Message ----- >>>> From: "Vladimir Ivashchenko" <hazard@...> >>>> To: <register@...> >>>> Cc: <leaf-wisp-dist@...> >>>> Sent: Thursday, February 23, 2006 11:47 AM >>>> Subject: Re: [leaf-wisp] Problem building image... weird >>>> >>>> >>>> > >>>> > Probably get_patchlevel() function does not return correct >>>> information for some reason. >>>> > >>>> > Go to source root directory and run >>>> > >>>> > ls -w1 >>>> > >>>> \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... >>>> 003/patch-log | sed s/patch-// >>>> > >>>> > What would be the output? >>>> > >>>> > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: >>>> > > I have had the same problem building images from RH9; not >>>> exactly >>>> true... >>>> > > the images I built would not completely boot. It would stop at >>>> Init Level:. >>>> > > >>>> > > I switched to RedHat 7.3 and the images built with ./build.sh -f >>>> work. >>>> > > >>>> > > However, none of the images built would contain the name of the >>>> latest release. Example of my last build after uping my kernel to >>>> 2.4.25: >>>> > > >>>> > > (the same result with 7.3's original kernel) >>>> > > >>>> > > mkfs.msdos 2.8 (28 Feb 2001) >>>> > > Preparing root ... lrp md5 cramfs >>>> > > Preparing local ... lrp md5 >>>> > > Preparing zebra ... lrp md5 cramfs >>>> > > Preparing net-snmp ... lrp md5 cramfs >>>> > > Preparing sshd ... lrp md5 cramfs >>>> > > Preparing netdiag ... lrp md5 cramfs >>>> > > adding: initrd.lrp (deflated 0%) >>>> > > adding: ldlinux.sys (deflated 21%) >>>> > > adding: linux (deflated 1%) >>>> > > adding: local.lrp (stored 0%) >>>> > > adding: local.md5 (deflated 44%) >>>> > > adding: netdiag.cfs (deflated 0%) >>>> > > adding: netdiag.lrp (stored 0%) >>>> > > adding: netdiag.md5 (deflated 38%) >>>> > > adding: net-snmp.cfs (deflated 1%) >>>> > > adding: net-snmp.lrp (stored 0%) >>>> > > adding: net-snmp.md5 (deflated 46%) >>>> > > adding: readme (stored 0%) >>>> > > adding: root.cfs (deflated 0%) >>>> > > adding: root.lrp (deflated 0%) >>>> > > adding: root.md5 (deflated 49%) >>>> > > adding: sshd.cfs (deflated 1%) >>>> > > adding: sshd.lrp (deflated 1%) >>>> > > adding: sshd.md5 (deflated 37%) >>>> > > adding: syslinux.cfg (deflated 28%) >>>> > > adding: syslinux.dpy (stored 0%) >>>> > > adding: zebra.cfs (deflated 1%) >>>> > > adding: zebra.lrp (stored 0%) >>>> > > adding: zebra.md5 (deflated 44%) >>>> > > == Build complete. Boot image can be found at >>>> > > '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. >>>> > > >>>> > > Both files created: >>>> > > >>>> > > wisp-dist_1.3.1p_img.bin >>>> > > wisp-dist_1.3.1p_pkg.zip >>>> > > >>>> > > Question: What happened to: wisp.1.3.1p35 ? >>>> > > >>>> > > PLease help... what could I have done wrong? >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > ------------------------------------------------------- >>>> > > This SF.Net email is sponsored by xPML, a groundbreaking >>>> scripting >>>> language >>>> > > that extends applications into web and mobile media. Attend the >>>> live >>>> webcast >>>> > > and join the prime developer group breaking into this new coding >>>> territory! >>>> > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >>>> _______________________________________________ >>>> > > leaf-wisp-dist mailing list >>>> > > leaf-wisp-dist@... >>>> > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist >>>> > -- >>>> > Best Regards, >>>> > Vladimir Ivashchenko >>>> > Chief Technology Officer >>>> > Thunderworx Cyprus - www.thunderworx.com >>>> > >>>> > >>>> > >>>> > ------------------------------------------------------- >>>> > This SF.Net email is sponsored by xPML, a groundbreaking scripting >>>> language >>>> > that extends applications into web and mobile media. Attend the >>>> live >>>> webcast >>>> > and join the prime developer group breaking into this new coding >>>> territory! >>>> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >>>> _______________________________________________ >>>> > leaf-wisp-dist mailing list >>>> > leaf-wisp-dist@... >>>> > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist >>>> > >>> -- >>> Best Regards, >>> Vladimir Ivashchenko >>> Chief Technology Officer >>> Thunderworx Cyprus - www.thunderworx.com >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by xPML, a groundbreaking scripting >>> language that extends applications into web and mobile media. Attend >>> the live webcast and join the prime developer group breaking into >>> this new coding territory! >>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >>> _______________________________________________ >>> leaf-wisp-dist mailing list >>> leaf-wisp-dist@... >>> https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language that extends applications into web and mobile media. Attend the > live webcast and join the prime developer group breaking into this new > coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > leaf-wisp-dist mailing list > leaf-wisp-dist@... > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdMay I ask a "stupid" question?... When you ssh into the CPE, how can I
tell which version/patch the software is? Thanks, Boatner > That was the answer, Hooray! (i'm a dummy). I saved a partition with > all my downloaded tar files and directory trees so it would not have to > be downloaded again. Apparently I also kept the binary: tla, which was > compiled on my original RH9. > > Sorry for the false alarm. I appreciate all your selfless work, > Vladimir. > > With my kindest regards, > > Boatner Howell > > > > >> Ah! I found the problem... build.sh does not know where tla is (for >> that matter, I don't know right now either :-\ ) >> >> I'll fix that problem and let you know if that works. >> >> -Boatner >> >> >> >>> [root@unclescrooge wdist]# ls -w1 >>> \{arch\}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log >>> | sed s/patch-// | sort -n | tail -n 1 >>> 36 >>> [root@unclescrooge wdist]# ls -w1 >>> \{arch\}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log >>> | sed s/patch-// | sort -n >>> base-0 >>> 1 >>> 2 >>> 3 >>> 4 >>> 5 >>> 6 >>> 7 >>> 8 >>> 9 >>> 10 >>> 11 >>> 12 >>> 13 >>> 14 >>> 15 >>> 16 >>> 17 >>> 18 >>> 19 >>> 20 >>> 21 >>> 22 >>> 23 >>> 24 >>> 25 >>> 26 >>> 27 >>> 28 >>> 29 >>> 30 >>> 31 >>> 32 >>> 33 >>> 34 >>> 35 >>> 36 >>> >>>> >>>> Actually do the following commands >>>> >>>> ls -w1 \{arch >>>> \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log >>>> | sed s/patch-// | sort -n | tail -n 1 >>>> >>>> ls -w1 \{arch >>>> \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log >>>> | sed s/patch-// | sort -n >>>> >>>> These commands are used to find out tree version. For some reason in >>>> your case it thinks that it is on patchlevel 1. >>>> >>>> On Thu, 2006-02-23 at 14:12 -0500, Michael Plourde wrote: >>>>> i got the same problem: >>>>> > > the images I built would not completely boot. It would stop at >>>>> Init Level:. >>>>> except that my image is wisp-dist_1.3.1p36_img.bin >>>>> and before Init Level: i got >>>>> echo: need libc.so.6 (GLIBC2.3) >>>>> >>>>> >>>>> i try like Valdimir said: >>>>> > Go to source root directory and run >>>>> > >>>>> > ls -w1 >>>>> > >>>>> \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... >>>>> 003/patch-log | sed s/patch-// >>>>> > >>>>> > What would be the output? >>>>> and the output is: >>>>> base-0 >>>>> 1 >>>>> 10 >>>>> 11 >>>>> 12 >>>>> 13 >>>>> 14 >>>>> 15 >>>>> 16 >>>>> 17 >>>>> 18 >>>>> 19 >>>>> 2 >>>>> 20 >>>>> 21 >>>>> 22 >>>>> 23 >>>>> 24 >>>>> 25 >>>>> 26 >>>>> 27 >>>>> 28 >>>>> 29 >>>>> 3 >>>>> 30 >>>>> 31 >>>>> 32 >>>>> 33 >>>>> 34 >>>>> 35 >>>>> 36 >>>>> 4 >>>>> 5 >>>>> 6 >>>>> 7 >>>>> 8 >>>>> 9 >>>>> ------------------------------------------------------------------- >>>>> >>>>> What does it mean ? >>>>> What is my problem ? >>>>> >>>>> ----- Original Message ----- >>>>> From: "Vladimir Ivashchenko" <hazard@...> >>>>> To: <register@...> >>>>> Cc: <leaf-wisp-dist@...> >>>>> Sent: Thursday, February 23, 2006 11:47 AM >>>>> Subject: Re: [leaf-wisp] Problem building image... weird >>>>> >>>>> >>>>> > >>>>> > Probably get_patchlevel() function does not return correct >>>>> information for some reason. >>>>> > >>>>> > Go to source root directory and run >>>>> > >>>>> > ls -w1 >>>>> > >>>>> \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... >>>>> 003/patch-log | sed s/patch-// >>>>> > >>>>> > What would be the output? >>>>> > >>>>> > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: >>>>> > > I have had the same problem building images from RH9; not >>>>> exactly >>>>> true... >>>>> > > the images I built would not completely boot. It would stop at >>>>> Init Level:. >>>>> > > >>>>> > > I switched to RedHat 7.3 and the images built with ./build.sh >>>>> -f >>>>> work. >>>>> > > >>>>> > > However, none of the images built would contain the name of the >>>>> latest release. Example of my last build after uping my kernel to >>>>> 2.4.25: >>>>> > > >>>>> > > (the same result with 7.3's original kernel) >>>>> > > >>>>> > > mkfs.msdos 2.8 (28 Feb 2001) >>>>> > > Preparing root ... lrp md5 cramfs >>>>> > > Preparing local ... lrp md5 >>>>> > > Preparing zebra ... lrp md5 cramfs >>>>> > > Preparing net-snmp ... lrp md5 cramfs >>>>> > > Preparing sshd ... lrp md5 cramfs >>>>> > > Preparing netdiag ... lrp md5 cramfs >>>>> > > adding: initrd.lrp (deflated 0%) >>>>> > > adding: ldlinux.sys (deflated 21%) >>>>> > > adding: linux (deflated 1%) >>>>> > > adding: local.lrp (stored 0%) >>>>> > > adding: local.md5 (deflated 44%) >>>>> > > adding: netdiag.cfs (deflated 0%) >>>>> > > adding: netdiag.lrp (stored 0%) >>>>> > > adding: netdiag.md5 (deflated 38%) >>>>> > > adding: net-snmp.cfs (deflated 1%) >>>>> > > adding: net-snmp.lrp (stored 0%) >>>>> > > adding: net-snmp.md5 (deflated 46%) >>>>> > > adding: readme (stored 0%) >>>>> > > adding: root.cfs (deflated 0%) >>>>> > > adding: root.lrp (deflated 0%) >>>>> > > adding: root.md5 (deflated 49%) >>>>> > > adding: sshd.cfs (deflated 1%) >>>>> > > adding: sshd.lrp (deflated 1%) >>>>> > > adding: sshd.md5 (deflated 37%) >>>>> > > adding: syslinux.cfg (deflated 28%) >>>>> > > adding: syslinux.dpy (stored 0%) >>>>> > > adding: zebra.cfs (deflated 1%) >>>>> > > adding: zebra.lrp (stored 0%) >>>>> > > adding: zebra.md5 (deflated 44%) >>>>> > > == Build complete. Boot image can be found at >>>>> > > '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. >>>>> > > >>>>> > > Both files created: >>>>> > > >>>>> > > wisp-dist_1.3.1p_img.bin >>>>> > > wisp-dist_1.3.1p_pkg.zip >>>>> > > >>>>> > > Question: What happened to: wisp.1.3.1p35 ? >>>>> > > >>>>> > > PLease help... what could I have done wrong? >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > ------------------------------------------------------- >>>>> > > This SF.Net email is sponsored by xPML, a groundbreaking >>>>> scripting >>>>> language >>>>> > > that extends applications into web and mobile media. Attend the >>>>> live >>>>> webcast >>>>> > > and join the prime developer group breaking into this new >>>>> coding >>>>> territory! >>>>> > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >>>>> _______________________________________________ >>>>> > > leaf-wisp-dist mailing list >>>>> > > leaf-wisp-dist@... >>>>> > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist >>>>> > -- >>>>> > Best Regards, >>>>> > Vladimir Ivashchenko >>>>> > Chief Technology Officer >>>>> > Thunderworx Cyprus - www.thunderworx.com >>>>> > >>>>> > >>>>> > >>>>> > ------------------------------------------------------- >>>>> > This SF.Net email is sponsored by xPML, a groundbreaking >>>>> scripting >>>>> language >>>>> > that extends applications into web and mobile media. Attend the >>>>> live >>>>> webcast >>>>> > and join the prime developer group breaking into this new coding >>>>> territory! >>>>> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >>>>> _______________________________________________ >>>>> > leaf-wisp-dist mailing list >>>>> > leaf-wisp-dist@... >>>>> > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist >>>>> > >>>> -- >>>> Best Regards, >>>> Vladimir Ivashchenko >>>> Chief Technology Officer >>>> Thunderworx Cyprus - www.thunderworx.com >>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.Net email is sponsored by xPML, a groundbreaking scripting >>>> language that extends applications into web and mobile media. Attend >>>> the live webcast and join the prime developer group breaking into >>>> this new coding territory! >>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >>>> _______________________________________________ >>>> leaf-wisp-dist mailing list >>>> leaf-wisp-dist@... >>>> https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist >> >> >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by xPML, a groundbreaking scripting >> language that extends applications into web and mobile media. Attend >> the live webcast and join the prime developer group breaking into this >> new coding territory! >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >> _______________________________________________ >> leaf-wisp-dist mailing list >> leaf-wisp-dist@... >> https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language that extends applications into web and mobile media. Attend the > live webcast and join the prime developer group breaking into this new > coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > leaf-wisp-dist mailing list > leaf-wisp-dist@... > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
|
|
Re: Problem building image... weirdIt shows it on top of the main menu.
On Fri, 2006-02-24 at 13:23 -0500, register@... wrote: > May I ask a "stupid" question?... When you ssh into the CPE, how can I > tell which version/patch the software is? > > Thanks, > > Boatner > > > > That was the answer, Hooray! (i'm a dummy). I saved a partition with > > all my downloaded tar files and directory trees so it would not have to > > be downloaded again. Apparently I also kept the binary: tla, which was > > compiled on my original RH9. > > > > Sorry for the false alarm. I appreciate all your selfless work, > > Vladimir. > > > > With my kindest regards, > > > > Boatner Howell > > > > > > > > > >> Ah! I found the problem... build.sh does not know where tla is (for > >> that matter, I don't know right now either :-\ ) > >> > >> I'll fix that problem and let you know if that works. > >> > >> -Boatner > >> > >> > >> > >>> [root@unclescrooge wdist]# ls -w1 > >>> \{arch\}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log > >>> | sed s/patch-// | sort -n | tail -n 1 > >>> 36 > >>> [root@unclescrooge wdist]# ls -w1 > >>> \{arch\}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log > >>> | sed s/patch-// | sort -n > >>> base-0 > >>> 1 > >>> 2 > >>> 3 > >>> 4 > >>> 5 > >>> 6 > >>> 7 > >>> 8 > >>> 9 > >>> 10 > >>> 11 > >>> 12 > >>> 13 > >>> 14 > >>> 15 > >>> 16 > >>> 17 > >>> 18 > >>> 19 > >>> 20 > >>> 21 > >>> 22 > >>> 23 > >>> 24 > >>> 25 > >>> 26 > >>> 27 > >>> 28 > >>> 29 > >>> 30 > >>> 31 > >>> 32 > >>> 33 > >>> 34 > >>> 35 > >>> 36 > >>> > >>>> > >>>> Actually do the following commands > >>>> > >>>> ls -w1 \{arch > >>>> \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log > >>>> | sed s/patch-// | sort -n | tail -n 1 > >>>> > >>>> ls -w1 \{arch > >>>> \}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@.../patch-log > >>>> | sed s/patch-// | sort -n > >>>> > >>>> These commands are used to find out tree version. For some reason in > >>>> your case it thinks that it is on patchlevel 1. > >>>> > >>>> On Thu, 2006-02-23 at 14:12 -0500, Michael Plourde wrote: > >>>>> i got the same problem: > >>>>> > > the images I built would not completely boot. It would stop at > >>>>> Init Level:. > >>>>> except that my image is wisp-dist_1.3.1p36_img.bin > >>>>> and before Init Level: i got > >>>>> echo: need libc.so.6 (GLIBC2.3) > >>>>> > >>>>> > >>>>> i try like Valdimir said: > >>>>> > Go to source root directory and run > >>>>> > > >>>>> > ls -w1 > >>>>> > > >>>>> \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... > >>>>> 003/patch-log | sed s/patch-// > >>>>> > > >>>>> > What would be the output? > >>>>> and the output is: > >>>>> base-0 > >>>>> 1 > >>>>> 10 > >>>>> 11 > >>>>> 12 > >>>>> 13 > >>>>> 14 > >>>>> 15 > >>>>> 16 > >>>>> 17 > >>>>> 18 > >>>>> 19 > >>>>> 2 > >>>>> 20 > >>>>> 21 > >>>>> 22 > >>>>> 23 > >>>>> 24 > >>>>> 25 > >>>>> 26 > >>>>> 27 > >>>>> 28 > >>>>> 29 > >>>>> 3 > >>>>> 30 > >>>>> 31 > >>>>> 32 > >>>>> 33 > >>>>> 34 > >>>>> 35 > >>>>> 36 > >>>>> 4 > >>>>> 5 > >>>>> 6 > >>>>> 7 > >>>>> 8 > >>>>> 9 > >>>>> ------------------------------------------------------------------- > >>>>> > >>>>> What does it mean ? > >>>>> What is my problem ? > >>>>> > >>>>> ----- Original Message ----- > >>>>> From: "Vladimir Ivashchenko" <hazard@...> > >>>>> To: <register@...> > >>>>> Cc: <leaf-wisp-dist@...> > >>>>> Sent: Thursday, February 23, 2006 11:47 AM > >>>>> Subject: Re: [leaf-wisp] Problem building image... weird > >>>>> > >>>>> > >>>>> > > >>>>> > Probably get_patchlevel() function does not return correct > >>>>> information for some reason. > >>>>> > > >>>>> > Go to source root directory and run > >>>>> > > >>>>> > ls -w1 > >>>>> > > >>>>> \{arch}/wisp-dist/wisp-dist/wisp-dist--1.3/hazard@... > >>>>> 003/patch-log | sed s/patch-// > >>>>> > > >>>>> > What would be the output? > >>>>> > > >>>>> > On Thu, 2006-02-23 at 11:40 -0500, register@... wrote: > >>>>> > > I have had the same problem building images from RH9; not > >>>>> exactly > >>>>> true... > >>>>> > > the images I built would not completely boot. It would stop at > >>>>> Init Level:. > >>>>> > > > >>>>> > > I switched to RedHat 7.3 and the images built with ./build.sh > >>>>> -f > >>>>> work. > >>>>> > > > >>>>> > > However, none of the images built would contain the name of the > >>>>> latest release. Example of my last build after uping my kernel to > >>>>> 2.4.25: > >>>>> > > > >>>>> > > (the same result with 7.3's original kernel) > >>>>> > > > >>>>> > > mkfs.msdos 2.8 (28 Feb 2001) > >>>>> > > Preparing root ... lrp md5 cramfs > >>>>> > > Preparing local ... lrp md5 > >>>>> > > Preparing zebra ... lrp md5 cramfs > >>>>> > > Preparing net-snmp ... lrp md5 cramfs > >>>>> > > Preparing sshd ... lrp md5 cramfs > >>>>> > > Preparing netdiag ... lrp md5 cramfs > >>>>> > > adding: initrd.lrp (deflated 0%) > >>>>> > > adding: ldlinux.sys (deflated 21%) > >>>>> > > adding: linux (deflated 1%) > >>>>> > > adding: local.lrp (stored 0%) > >>>>> > > adding: local.md5 (deflated 44%) > >>>>> > > adding: netdiag.cfs (deflated 0%) > >>>>> > > adding: netdiag.lrp (stored 0%) > >>>>> > > adding: netdiag.md5 (deflated 38%) > >>>>> > > adding: net-snmp.cfs (deflated 1%) > >>>>> > > adding: net-snmp.lrp (stored 0%) > >>>>> > > adding: net-snmp.md5 (deflated 46%) > >>>>> > > adding: readme (stored 0%) > >>>>> > > adding: root.cfs (deflated 0%) > >>>>> > > adding: root.lrp (deflated 0%) > >>>>> > > adding: root.md5 (deflated 49%) > >>>>> > > adding: sshd.cfs (deflated 1%) > >>>>> > > adding: sshd.lrp (deflated 1%) > >>>>> > > adding: sshd.md5 (deflated 37%) > >>>>> > > adding: syslinux.cfg (deflated 28%) > >>>>> > > adding: syslinux.dpy (stored 0%) > >>>>> > > adding: zebra.cfs (deflated 1%) > >>>>> > > adding: zebra.lrp (stored 0%) > >>>>> > > adding: zebra.md5 (deflated 44%) > >>>>> > > == Build complete. Boot image can be found at > >>>>> > > '/usr/src/wisp-dist/wisp-dist_1.3.1p_img.bin'. > >>>>> > > > >>>>> > > Both files created: > >>>>> > > > >>>>> > > wisp-dist_1.3.1p_img.bin > >>>>> > > wisp-dist_1.3.1p_pkg.zip > >>>>> > > > >>>>> > > Question: What happened to: wisp.1.3.1p35 ? > >>>>> > > > >>>>> > > PLease help... what could I have done wrong? > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > ------------------------------------------------------- > >>>>> > > This SF.Net email is sponsored by xPML, a groundbreaking > >>>>> scripting > >>>>> language > >>>>> > > that extends applications into web and mobile media. Attend the > >>>>> live > >>>>> webcast > >>>>> > > and join the prime developer group breaking into this new > >>>>> coding > >>>>> territory! > >>>>> > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > >>>>> _______________________________________________ > >>>>> > > leaf-wisp-dist mailing list > >>>>> > > leaf-wisp-dist@... > >>>>> > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > >>>>> > -- > >>>>> > Best Regards, > >>>>> > Vladimir Ivashchenko > >>>>> > Chief Technology Officer > >>>>> > Thunderworx Cyprus - www.thunderworx.com > >>>>> > > >>>>> > > >>>>> > > >>>>> > ------------------------------------------------------- > >>>>> > This SF.Net email is sponsored by xPML, a groundbreaking > >>>>> scripting > >>>>> language > >>>>> > that extends applications into web and mobile media. Attend the > >>>>> live > >>>>> webcast > >>>>> > and join the prime developer group breaking into this new coding > >>>>> territory! > >>>>> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > >>>>> _______________________________________________ > >>>>> > leaf-wisp-dist mailing list > >>>>> > leaf-wisp-dist@... > >>>>> > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > >>>>> > > >>>> -- > >>>> Best Regards, > >>>> Vladimir Ivashchenko > >>>> Chief Technology Officer > >>>> Thunderworx Cyprus - www.thunderworx.com > >>>> > >>>> > >>>> > >>>> ------------------------------------------------------- > >>>> This SF.Net email is sponsored by xPML, a groundbreaking scripting > >>>> language that extends applications into web and mobile media. Attend > >>>> the live webcast and join the prime developer group breaking into > >>>> this new coding territory! > >>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > >>>> _______________________________________________ > >>>> leaf-wisp-dist mailing list > >>>> leaf-wisp-dist@... > >>>> https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > >> > >> > >> > >> > >> > >> ------------------------------------------------------- > >> This SF.Net email is sponsored by xPML, a groundbreaking scripting > >> language that extends applications into web and mobile media. Attend > >> the live webcast and join the prime developer group breaking into this > >> new coding territory! > >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > >> _______________________________________________ > >> leaf-wisp-dist mailing list > >> leaf-wisp-dist@... > >> https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > language that extends applications into web and mobile media. Attend the > > live webcast and join the prime developer group breaking into this new > > coding territory! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > > _______________________________________________ > > leaf-wisp-dist mailing list > > leaf-wisp-dist@... > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > Best Regards, Vladimir Ivashchenko Chief Technology Officer Thunderworx Cyprus - www.thunderworx.com ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ leaf-wisp-dist mailing list leaf-wisp-dist@... https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist |
| Free embeddable forum powered by Nabble | Forum Help |