dCore Import Debian Packages to Mountable SCE extensions > dCore X86
Latest busybox version for dCore?
PDP-8:
I just burned dCore-Stretch and noticed that the busybox version is 1.20.2.
Do all the dCore versions use 1.20.2 (as of now)?
I like busybox a LOT, and wonder if compiling my own version of the latest BB release and running it as a user would (soft links to all the commands in it's own directory and path etc etc) would confuse dCore somehow?
Jason W:
Hi. Yes, the current dCores use busybox 1.20.2. I am working on dCore-bionic, the next LTS Ubuntu release due in April. And it will have Busybox 1.27.2.
I can build 1.27.2 on dCore-stretch and dCore-stretch64 and it should fit right in as I see no issues with on dCore-bionic. I will do that in the coming days and see how it goes and if all is well I can upgrade Busybox to 1.27.2. If it will compile on dCore-wheezy, then I can upgrade all dCores to Busybox 1.27.2.
Jason W:
dCore-trusty, dCore-jessie, dCore-xenial, dCore-stretch, and dCore-artful have been updated in the release candidates area with Busybox 1.27.2. The new Busybox for these x86 dCore ports was built on dCore-trusty. dCore-wheezy has too old of GCC to build the newer Busybox based on the errors I saw so it remains with the old version.
All is working as expected in my testing.
PDP-8:
Wow! I'll have to fire up an RC and check it out!
Heh, my initial query was more of an observation and looked what happens... thanks Jason..
My biggest problem with the 'core family is now keeping track of which one I'm running! :)
Awesome work guys..
Greg Erskine:
Word of warning! We have been using BusyBox v1.27.2 (2017-10-31 19:09:48 UTC) multi-call binary on piCorePlayer for a few months now. If you have been writing shell scripts, as we do, a couple of the commands have changed causing scripts to fail. From memory, options for wget changed and fdisk output format changed.
Probably won't affect anybody else but might just save some head scratching.
Navigation
[0] Message Index
[#] Next page
Go to full version