Tiny Core Linux

dCore Import Debian Packages to Mountable SCE extensions => General dCore Talk => Topic started by: PDP-8 on July 12, 2020, 01:01:15 PM

Title: Track the TC busybox version?
Post by: PDP-8 on July 12, 2020, 01:01:15 PM
Just wondering if it would be possible to more closely track the TC version of busybox?

That way, freaks like myself who bounce back and forth between dCore and TC can be "bug for bug compatible", as Keith Bostic of nvi fame once stated. :)

Not a huge issue, I can compile, or steal my own busybox from other systems if I desire, but I think it would be nifty to track TC in this regard if possible.
Title: Re: Track the TC busybox version?
Post by: Jason W on July 12, 2020, 07:29:52 PM
Sure, I like to use the same version of Busybox as well as the kernel for a release of dCore that the current Core is using, for reasons you mention.  I thought I was doing that, but maybe I was not as closely as I intended. 
Title: Re: Track the TC busybox version?
Post by: Jason W on July 12, 2020, 08:04:13 PM
I compile the kernel on dCore, so it is a little different.  And Busybox the same, but I have used the same Busybox binary since dCore-bionic64 for the 64 bit dCores. 
Title: Re: Track the TC busybox version?
Post by: PDP-8 on July 13, 2020, 02:33:59 AM
Yep - no major problem.  Doesn't need to be in lock-step with TC.

Just noticed that on the RC of Focal64 that busybox | head reveals version 1.27.2 so I guess that makes sense.

Although I'm interested in vi/bc/dc improvements, and our own contributors fixes to same, I really like to use the latest fixes to the BB ash shell, which dCore uses.

P.S. at work, which is an all-windows shop wanted to bring up an older machine - and I didn't have my stick with me.  The ease of the rc release of focal64 burn-n-boot impressed the higher-ups since all we needed was a 10 minute fix until the IT guys could revive their downed windows box.  Yeah!