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
>>
>>
>>
>>>  [EMAIL PROTECTED] wdist]# ls -w1
>>> \{arch\}/wisp-dist/wisp-dist/wisp-dist--1.3/[EMAIL PROTECTED]/patch-log
>>> | sed s/patch-// | sort -n | tail -n 1
>>> 36
>>> [EMAIL PROTECTED] wdist]# ls -w1
>>> \{arch\}/wisp-dist/wisp-dist/wisp-dist--1.3/[EMAIL PROTECTED]/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/[EMAIL PROTECTED]/patch-log
>>>> | sed s/patch-// | sort -n | tail -n 1
>>>>
>>>> ls -w1 \{arch
>>>> \}/wisp-dist/wisp-dist/wisp-dist--1.3/[EMAIL PROTECTED]/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/[EMAIL PROTECTED]
>>>>> 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" <[EMAIL PROTECTED]>
>>>>> To: <[EMAIL PROTECTED]>
>>>>> Cc: <leaf-wisp-dist@lists.sourceforge.net>
>>>>> 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/[EMAIL PROTECTED]
>>>>> 003/patch-log | sed s/patch-//
>>>>> >
>>>>> > What would be the output?
>>>>> >
>>>>> > On Thu, 2006-02-23 at 11:40 -0500, [EMAIL PROTECTED] 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@lists.sourceforge.net
>>>>> > > 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@lists.sourceforge.net
>>>>> > 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@lists.sourceforge.net
>>>> 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@lists.sourceforge.net
>> 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@lists.sourceforge.net
> 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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist

Reply via email to