Tiny Core Extensions > TCE Corepure64

Need I update TC64 installation?

(1/3) > >>

labeas:
Looking at: Index of /8.x/x86_64/release/
I see that TC64 is continually updated.

I wasn't able to install pan [NNTP client] which apparently needed
full-X, and not just the <Fbuf> that I've installed; but I'm afraid
to mess with what's working so far. And since opera-12 runs OK, except
that I didn't succeed to fetch NNTP yet, I may still be able to do
NNTP with only <Fbuf>.

Obviously with a new substantial system like TC64, there will be
quirks which need fixing, like when returning from VT to X:
* sometimes X-windows have changed size,
* sometimes X-windows have moved to the left, so that the <moveBar>
is hidden and I don't know how to close the window.

TC is not designed for users in 3rd-going-4th world societies,
where apart from your Inet connection, you must worry about the
security of your electricity and drinking water.
So I can't risk losing TC's off-line capability, by trying to be
up-to-date, and end up with a lame M$ only device.
Only TC is unique in being a realistically USBstik-based linux.

So, am I advised to install a newer than 3 months old TC64;
and can that be done to not-partition-one of one of several USB
devices that I've got?

== TIA

Rich:
Hi labeas

--- Quote from: labeas on April 09, 2017, 04:29:46 PM ---* sometimes X-windows have changed size,
* sometimes X-windows have moved to the left, so that the <moveBar>
is hidden and I don't know how to close the window.
--- End quote ---
If a windows titlebar is offscreen, give the window focus and hit  Ctrl-Alt-M  a couple of times.

Juanito:

--- Quote from: labeas on April 09, 2017, 04:29:46 PM ---So, am I advised to install a newer than 3 months old TC64;
and can that be done to not-partition-one of one of several USB
devices that I've got?

--- End quote ---

An update can be done alongside your existing installation - rename the distributions file to, say, rootfs64_tc8.gz, modules64_tc8.gz, vmlinuz64_tc8, create a tce64_tc8 folder, add an extra menu item to your bootloader and off you go...

labeas:
You seem to suggest that a <new boot entry> in the booter,
which points to to a new KERNEL /boot/vmlinuz64
 and INITRD /boot/corepure64.gz
will allow choice/for-testing between the proven & new installations ?

I like that; but my problem is that, for reasons which I can't trace
in my logs, I installed the original TC64 in a FATfs on the USBstik.
That brought many problems, so I've made a 2nd ext4 partition for my
data & script directories; which is where I want NewTC64 to boot from.

But, also for unknown reasons, I'm using the isolinux booter, which
apparently can only access its own partition, unlike GRUB.

Since TC64 caters for GRUB, I'd much rather use that:
which would apparently solve the problem of booting  TC64 from the
2nd partition, and also allow me to experiment with booting some of
my old installations, to fetch info which a `chroot oldInstl` can't
see because of no access to /dev & /proc.

Eg. I've put the <TCbook>.pdf in one of these other installations
which has pdfRendering ability. But while reading it recently, I didn't
think to search about GRUB. So I guess installing GRUB would overwrit
the present installation. So best buy ANOTHER USBstik! ?

The following multi-screen TCinstructions/description seems applicable;
"* Howto make a legacy bios/uefi dual boot usb stick with grub2" ?

Juanito:
Optionally you could use the tc-install extension in the tc-8.x x86_64 repo, but this uses syslinux

Navigation

[0] Message Index

[#] Next page