- This topic is empty.
March 19, 2010 at 6:18 pm #5769
I needed an xterm access locally on the S50 and was able to locate the UTILS-3.0.8.pak which provides rxvt. Excellent. I will have to figure out how to make a .pak with the information and PDF I have found on this site for the program/scripts I have, but I need a few other standard Open Source programs my script needs.
Is there a possibility someone has or could easily build a .pak that has the following programs in one .pak or in separate .pak files of some combination that makes sense for future uses of others.
The following are key to my needs:
I know the S50 does sync with a time server, but I need the ntpdate command to know the delta difference so I can track the drift of the clock on the S50 as the application I have is time sensitive.
The following is helpful and I know I can get this from the /proc file system
These would be helpful:
As I see it it may be best to make all of these separate .pak files. With the exception of nedit, none need any icon. Clearly to access these command line programs one will need rxvt or similar.
If someone can make these with ease I would be most grateful. I would also like to know if the binaries for these were simply pulled from an existing built distribution package or had to be compiled for V6.6.2-02. That way I have a sense in case I need binaries in future without having to make requests like this posting again.
For the moment I am going to see if I can run the static linked binary (too complicated to have the required libraries only one program will use) from a USB and make a batch file I will have to start manually until I learn the ins/outs of .pak files and have the other programs I need noted above.
I have about 3 weeks of development effort to modify the program I will be using on the S50 so it is much easier to effect changes to the device connected to the S50 the program reads data from. It will likely take 2-3 months of lapsed time for me to accomplish.
John L. Males
19 March 2010 14:18March 20, 2010 at 12:09 am #17982
I have been busy since the posting gathering up all the hardware pieces I need for the external device I will be using with the S50. In the past 20 minutes I have figured out all of the must haves and nice to haves except for nedit and lftp are in the BusyBox code. If someone is able to build the 1.16 BusyBox code for the S50 Linux V6.6.2-02 with all the commands enabled that would be great. The file config appears to be what was used to build downloadable binaries for 1.16. There appears to be no binary suitable for the AMD Geode GX processor of the S50 😥 I have not figured out yet how to compile BusyBox for the AMD Geode GX processor yet.
The next challenge is how to compile nedit to work with the libraries of Linux V6.6.2-02. Then I am all set. I need nedit rather than the built in VI of BusyBox for certain features in nedit not in vi.
John L. Males
19 March 2010 20:09March 20, 2010 at 5:44 pm #17983
As I cannot figure out what build environment and related versions of libraries to use I cannot even attempt to build BusyBox for the S50 Linux V6.6.2. I had actually requested the source code and build environment from Wyse a few days ago before knowing I need these so soon and still not a hint from Wyse of responding to my request for the Linux Source and Build environment for the S50 Linux.
This now brings me to a temporary option for the moment, using a Live USB Linux on the S50. The upside is I have access to the key programs I need except for nedit and the ability to have a couple of local terminal sessions open for running the external device from the S50. The down side is the Live USBs, even just a command line basic Live USB takes about 3-4 minutes to boot. I really like how fast the wyse S50 Linux boots and frankly has most of what I need except for the few key programs I need and multiple local terminal sessions.
So for now until Wyse can send me the source code and build environment I have to use a far heavier approach than I need. I know about DSL, but it has some bugs and missing elements for what I need and the heavier solutions have alot more than I need.
John L. Males
20 March 2010 13:44March 21, 2010 at 12:30 am #17984
After hours of trial and error I have DSL booting from a USB on the S50. Even though I changed the boot order in the S50 BIOS to do USB first and saved the changes the S50 lost those changes and reverted back to an order that only included IDE and PXE, and USB was not even on the boot order list. I did not discover that for a couple hours between different attempts on how or not to create bootable USB’s. Added to that the Debian Live images no matter what vga or sync or screen size you provide at the boot prompt keeps sending an invalid video mode to the screen such that nothing displays on the display other than the hardware message from the screen about an invalid video mode. complicating this is even when a known bootable USB was in the S50 it would not boot from the USB often and just boot the Wyse firmware image. In all cases of this the BIOS did show the USB as the first boot device, but for reasons unknown and some sort of now figured out (just not any logical reason for the behaviour) when the S50 will not boot from a working bootable USB the S50 has booted from a number of times with no issue. All in all these trials and errors and trying to convince the S50 there is a properly imaged bootable USB in the S50 USB port (only ever had one USB flash/drive plugged in ever) and redoing USB creates because the S50 changed its mind if it would boot from USB leading me to believe the format/data on the USB was not correct for booting resulted in about 9 hours of effort to figure some of the issues out and just be aware of other issues that make no sense.
John L. Males
20 March 2010 20:30March 24, 2010 at 3:05 am #18001
After thinking I had made some coding errors with the program I wish to use with the S50 it turns out the coding like problems were caused by DSL 4.4.10 and I suspect would happen with any version of DSL. This meant I spent 2 very long days thinking I was the cause of the error when it was DSL.
DSL also has a nasty habbit of using 100% CPU for the most basic GUI programs that one would keep open for awhile for reasons that make no sense. This means DSL heats up the device for a long time not to mention anything else you run, including other offending GUI programs, and as you do so or other instances of the the same GUI programs DSL get gets slower!!!! There are also bugs in some of the GUI based programs that result in runaway instances of these same GUI programs when these GUI programs never started their GUI interface. All the while the system has lots of memory available for use despite this. Usually at least 70Mb so the CPU 100% issue has nothing to do with memory. DSL was very disappointing.
I still have no reply from Wyse for the Linux source code and build environment. This means it is back to drawing board to find a USB bootable version of Linux that will work on the S50 and work with the command line program I wish to use. So sad that Debian Live will not work due to incorrect video mode settings that I have not been able to find a VGA= code to rectify.
John L. Males
23 March 2010 23:05
23 March 2010 23:28 Typo correction and added DSL comments. jlmMarch 24, 2010 at 5:54 pm #18008ConfGenKeymaster
- Total Post: 11485
- Jedi Master
I doubt you will ever get the source code from Wyse. It s their IP and I don’t think they hand it out.
Speaking of a build environment, there is one available but honestly all you need is the PDF from this website to create your own addons.
The SDK is not doing more for you.
- You must be logged in to reply to this topic.