had to bury the 6x/7x migration for the moment,
and as a result get to sign into email, banking,
whatever...with that pesky NO SHARED CRYPTO
message indicating I'm either in fake https land
with plain test transmissions or some other
crippled state. A lot of that may be issues
with email vendors and x.509 certs; as that
entire system is basically a corrupt, dysfunctional
train wreck anyway. As Snowden said; NSA
reads yer https in real time...indicating its
only a matter of time before teenagers
at Starbucks can too...pretty sure many
Read up on CDs and figured I'd try that route;
somehow get an ISO for 3x, then one for 4x
and work my way up to 6x slowly.
Problem (posted in other thread) is Cd's don't
seem to run extensions listed in onboot.lst
so mucking with that I tried the tce and cde
folder structures and bootlocal bootsync
all of that...no point describing it all here
as I just did there a second ago.
I did get one configuration to work once;
and it ran a script I used which then
checked for all extensions in onboot.lst
and loaded them - as they hadn't loaded
on the original boot - so I took care of
that after my bootsync.sh ran.
Problem was it made a mess of a lot of
other things; a persistent OPT folder
isn't a clean way of doing that - too many
programs want to use that area.
I also gave up on using the /opt/.tce_dir (3x)
and the etc (4x + ) methods for figuring
out where TCE is on the system and mapping
the optional folder.
Now on boot I scan everything in the /mnt folder
for any folder that has Xvesa.tcz in it - a rather
consistent indicator you're near the other
extensions - and then from there, the script
pokes around to find vmlinuz, bzImage, whatever,
and looks for onboot.lst and tries to RECONSTRUCT
the paths to tce and tce/optional and then
records those two folders for future calls
to tce-load or whatever...
That find works well...far more reliably than
the other .tce_dir method, which worked well
for years, but with the CD issues, now I get
a /tmp/tce in that file...when it should be
Lee suggested the CD is probably going
offline before TC has loaded or something;
so it gives up.
My scripts POUND the /mnt folder and
POUND the fdisk -l output and figure
out what devices MIGHT have the
boot files, extensions; whatever
and map it all up so I KNOW where
to find stuff later. No point skimping
on the "SYSTEM REGISTRY" if you wish
to use that term.
Anyway; with this inability of a CD
to load ANY extension at all, I am
still stuck in 3x land...happily though,
save the SSL problems...it is small,
tight, fast, ultra reliable and has served
me well for 6 frgin years.
I always said MSDOS 3.33 running on a 286
was the only reliable release Microsoft
ever put out...and to this day that remains
Apparently TC 3.5x has a similar quality.
Something about VERSION 3X in the
development process equates to both
speed and reliability. I think that
Version 1x is naturally buggy
Version 2x fixed old bugs, but
new features added more and
often it runs slower
Version 3x is really a fine tune or
a blend of 1x and 2x and at this
moment in time, developers think
they actually have a little gold in
their invention and really polish it up.
Then 4x comes out - the bigger, better
faster, fatter release; with its bugs,
and 5x and 6x just keep getting bigger,
and buggier, and slower.
I will guess that given the same weak CPU,
like the Intel ATOM I have in one box I
often use, if I ran a huge sort with 3x vs 6x
3x would kick 6x to the curb for speed.
A client I had who processed medical records
took 5 hrs to run 2 weeks of data for 1 hospital.
The code I delivered after 45 days ran
6 months (26 weeks, or 13 2 week blocks)
of data for 2 hospitals in 5 hrs. It ran
on Tiny Core and was compiled with TinyC;
the tcc.tcz tiny thingy in the tce tiny
core combo I do love.
In other words I processed 26 times more
data in the same 5 hrs.
The code I delivered after 90 days ran
6 months of data for 2 hospitals in
72 seconds...again on the TCC TCE combo.
Their systems guy fell out of his chair;
the owner thinks it'd save hospitals
tens of millions A MONTH, so they
hired a lawyer to patent it all up.
I declined and walked away from
that project when the lawyers
started elbowing everyone around.
...I declined to deliver the source; heh heh.
Sometimes you bring a nuke to a gun fight;
and its better to just go to the saloon
for a cold beer and a game of cards,
than stand out on the street at high noon
and watch everyone get all hot and