--- In "Jesse Off" <> wrote:
>
> Are you a student closing in on your assignment due date? You'd be
> surprised how much support time we waste helping students with
their
> homework.
No, I'm a customer trying to use your product. I'll ignore the
pointless jibe with a smile. And to be honest I don't see anyone from
TS wasting much time helping anyone with their homework, at least on
this list. So you are correct , I would be surprised.
> Like you, they can often get especially aggravated and
> desperate for help when their due date comes round.
>
I don't think it's my posts that show aggravation ...
Ronald and Eddie have been very positive in their replies , please
try not to undo thier efforts.
> Replace your /bin/awk with a binary from Debian and run this:
>
> cp /bin/busybox /x; dd if=/dev/zero of=/x bs=1 seek=431248 count=1
> conv=notrunc; mv /x /bin/busybox
>
> Problem solved. Now, stop it or please go away. Really.
>
> //Jesse Off
>
Thanks, interesting approach blasting a whole in the list of progs
busybox tries to imitate. This allows my symlink to debian's mawk to
get used.
Currently defined functions:
[, addgroup, adduser, adjtimex, ar, ash, , basename, bunzip2,
busybox, bzcat, cat, chgrp, chmod, chown, chroot, chvt, clear,
$ echo 1 2 3 | awk '{print $2}'
2
Correct answer. Sussed! This is a useful piece of knowlege for the
list , I'll post a binary, many thanks.
As I said in an earlier post the better way would be to build a more
recent busybox, this remains a problem with the arm debian image
provided.
I don't think this is a broken find in busybox but an incompatibility
between the debs image and -ts11 on the servers.
I see similar messages on booting debian via nfs coming from run-
parts (also a bb applet). These relate to the network stuff not
starting.
Since debian arm image is "highly recommended" for development it
would be good to resolve this issue too which, amongst other things,
would enable a clean rebuild of busybox with required functionality.
If Eddie , or anyone else inclined to help, can shed some light on
the
"Value too large" errors , I'd like to resolve that one and establish
a working developement system.
TIA, jacques.
> --- In "j.chitte" <j.chitte@> wrote:
> >
> > --- In "dawydiuk" <eddie@> wrote:
> > >
> > > TS-Linux is supported and it is finished, please keep in mind
> > > Technologic Systems is not the author of busybox. You should be
> > able
> > > to copy awk and find binaries from the Debian tarball above.
> > >
> > > The mailing list has been growing recently and I haven't had
the
> > > oppurtunity to follow the list as much as I'd like to. If you
> have
> > > any filesystem problems with any of our products please CC me
and
> > I
> > > will be able to help you to resolve any problems you have...
> > >
> > > //Eddie
> > >
> >
> > Hi Eddie, good to see you back in action on the list, your posts
> are
> > helpful.
> >
> > Narrowing this discussion down to the specific issue that you
have
> > addressed.
> >
> > I did grab awk (mawk) for the debian tarball but the problem
> largely
> > remains since busybox is already loaded and responds to awk so
the
> > true awk never gets called. (I remove the symlink and mv mawk awk)
> >
> > This means this solution can only work if anything that uses awk
> > calls mawk. It's a work around of sorts but not really fix.
> >
> > It seems a better approach to either rebuild bb as used in
> TSlinux ,
> > but with awk taken out, or build a more recent bb. Since may
other
> > bugs have been fixed since the pre-release version used in
TSlinux
> > this seems the obvious way to go.
> >
> > This presents two other problems.
> >
> > 1/ reverse engineer busybox config so as to not prevoke other
> issues
> > by it's being differently built from the distibuted busybox. Here
> > including on the server a copy of the bubybox .config used to
> build
> > TSlinux would be a quick reliable solution.
> >
> > 2/ The debian tarball provided is recommended if a compiler is
> > required. While I was able to build my own code by booting to
> debian
> > over nfs it fails with busybox due to the "value too large"
errors
> > that are also seen in the boot log.
> >
> > ### 50 Value too large errors , then fails.
> >
> > find: use: Value too large for defined data type
> > find: verbose: Value too large for defined data type
> > find: with: Value too large for defined data type
> > scripts/basic/split-include: find: No such file or directory
> > make: *** [include/config/MARKER] Error 1
> >
> > #onboard kernel
> > Linux arm 2.4.26-ts11 #3 Tue Jun 6 14:13:14 MST 2006 armv4l
unknown
> >
> >
> > This would seem to imply some incompatiblity between -ts11 and
the
> > debian tarball since 'find' does not show this issue in TSlinux.
> >
> > Can you shed any light on that?
> >
> > Thanks for picking this up.
> >
> > best regards, jacques.
> >
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|