Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: labeas on July 17, 2019, 05:17:48 AM
-
Correct my wrong assumptions, below:-
# version = 7.2
because so-called-updating without losing one's own jewel-applications
is very difficult.
As an example, let's analyse my attempt to fix the lost partn-1 [of 2]
from the December 23, 2015 project: [which cost many hours of labour]
"Howto make a legacy bios/uefi dual boot usb stick with grub2"
Just considering 1 line/instruction of this
(cat grubConfig |wc -l =) 273 instruction-lines:-
$ tce-load -i grub2-multi
The user should install the LATEST version. AFAIK = 10.1, today.
Q. Will the GUI-AppTool fetch the latest or the running-OS version ?!
The following instruction (entered as a single line):
"grub-install --target=x86_64-efi --boot-directory=/mnt/sdd2/EFI/BOOT
--efi-directory=/mnt/sdd2 --removable" ; returns:
"grub-install: error while loading shared libs: libdevmapper.so.1.02"
But GUI:Apps lists NO libdevmapper*, although it DID fetch other files
higher up the dependency tree.
The <grub2> project under consideration dates from 2015...
And <online:TC>/10.x/x86_64/tcz also has NO libdev* ?
If GUI:Apps is syncronised to the latest version, then the users have
lost control over their existing/invested software!
If it's set to the user's running version: how does he conveniently
install later versions of TC?
IMO "Version" should be one of the parameters of the GUI:Apps.
I've just noticed in the Comment section of GUI:Apps :-
sudo grub-mkrescue -o myiso.iso iso
Q. Would this have a <man file> ?
-
Hi labeas
... The user should install the LATEST version. AFAIK = 10.1, today.
Q. Will the GUI-AppTool fetch the latest or the running-OS version ?! ...
The Apps tool will always fetch from the repository that matches the running kernel.
The following instruction (entered as a single line):
"grub-install --target=x86_64-efi --boot-directory=/mnt/sdd2/EFI/BOOT
--efi-directory=/mnt/sdd2 --removable" ; returns:
"grub-install: error while loading shared libs: libdevmapper.so.1.02"
But GUI:Apps lists NO libdevmapper*, although it DID fetch other files
higher up the dependency tree.
Install liblvm2.tcz.
-
Thanks, Rich.
I'm uncomfortable replying via this Win10, with its absurd cartoons.
> AppsTool fetches from repository matching "the running kernel".
Good, but why's there no function/cmnd with an arg for the version?
> Install liblvm2.tcz
… like `fetchTcz 10.1 liblvm2
-----------------
This relates to a problem, where now we can't get poplog [from
the 90s] to run on newer linuxS. With difficulty, I manages to DL
an old <slakware.iso> which I hope will run my old poplog:FileTree.
Judging from the fix-error-reports: it's futile trying to match the
old poplog package to current systems.
They should accept that they CAN'T know how/why oldPoplog
mismatches new *nix versions... nor eliminate accidents/death.
-
Hi labeas
... Good, but why's there no function/cmnd with an arg for the version? ...
I'm not sure what question you are trying to ask, so here are my 2 answers:
1. The command to find out what version you are running is version.
2. Apps knows what version it is running on and does not need someone giving it an incorrect version number.
… like `fetchTcz 10.1 liblvm2 ...
Like:
tce-load -wi liblvm2
-
Hi Hi labeas
... This relates to a problem, where now we can't get poplog [from
the 90s] to run on newer linuxS. ...
Then maybe you should consider a more current version:
http://www.cs.bham.ac.uk/research/projects/poplog/freepoplog.html
This is from July 2019, 64 bit:
http://www.cs.bham.ac.uk/research/projects/poplog/amd64/poplog16/
-
No! Sometimes the SIMPLISTIC view of "buy a new one"
is the wrong approach; as is "else we'll bomb them" …
The URLs that you pasted shows how they [including me
initially] are spinning wheels - going nowhere.
W.H. from the Polish University has been debugging down
at the asm-level. Even if they go down to quantum-physics
level of the computer's transistors, they may not solve it.
----------------------
Q. How2:
fetch X.tcz plus dependencies for installing
a: from/via ver 7 FOR ver 10;
b: from/via ver 10 FOR ver 7
?
PS. I have traced the `tce-load` script, which is quiet big.
-
Hi labeas
... Q. How2:
fetch X.tcz plus dependencies for installing
a: from/via ver 7 FOR ver 10;
b: from/via ver 10 FOR ver 7 ...
There is a script that can do that located here:
http://forum.tinycorelinux.net/index.php/topic,23034.0.html
TC7 extensions are not guaranteed to work with TC10.
TC10 extensions are not guaranteed to work with TC7.
Blindly mixing different versions of extensions and Tinycore is not supported.
-
s there some thing I'm missing ?
>> like `fetchTcz 10.1 liblvm2 ...
Has 2 parameters; which explicitly acknowledges that
differnt-version-files may not be mixed - in general.
The script author wrote:-
]> my attempt to try to ease a situation that
]> comes up on a regular basis ...
How long has TC been in use, without this obviously needed function?
I gave the script a test and it seems very good; but I don't want
to mess with his code. Is there a good reason for *nix scripts to
<comment and set parameters at the script start> instead of passing
them when evoking the script?
Eg. back to my initailly proposed syntax: `fetchTcz 10.1 liblvm2`
The GUI:tool just needs one-more setting.
-
s there some thing I'm missing ?
I
-
How long has TC been in use, without this obviously needed function?
I think the fact why it’s never been implemented all these years speaks for itself.
Repos are kept separate for a reason.
Just think of all the conflicts people would experience by freely installing extensions and deps from previous repos
Better to take the time to learn how to use the tools provided, instead of complaining.
There are exceptions, like extensions accidentally missed in the transfer to a new repo. In that case what’s wrong with downloading using
wget from any disto, or
A decent browser from any OS
There’s even a download section in this forum which required only slight modification to the address to access any prior repo
Sent from my iPhone using Tapatalk
-
Q. How2:
fetch X.tcz plus dependencies for installing
a: from/via ver 7 FOR ver 10;
b: from/via ver 10 FOR ver 7
If you are upgrading across several tc versions, it would be better to use a new tce folder and download all your required extensions again.
i.e. use:
tce_7
tce_7_64
tce_10
tce_10_64
..or similar.
That way you can still boot and use both tc-7.x and tc-10.x