Could be [tiny]core improved?

[Rich]

Hi neonix

Is it possible to offer another flavour, called tiny core deluxe?

Is it possible, yes.
Is it likely, absolutely not.

One of the reasons for Tinycore is you get to pick and install
the extensions you want, instead of having to remove extensions
that come prepackaged and you don't want.

If you feel you need  "tiny core deluxe"  because installing extensions
is too much work, then maybe Tinycore is the wrong distro for you.

There are other distros available with multiple apps preinstalled.

[Rich]

Hi neonix

Is it possible to add copy and paste function to aterm?

It already has copy/paste.

To copy, using the mouse, highlight the text with the left button held down.

If you then click the middle button, it will paste the text in the terminal
at the current cursor location.

Or, if you left click in an editor, then click the middle button, it will paste the
text in the editor at the current cursor location.

You can copy/paste from an editor to a terminal the same way.

[neonix]

Hi neonix

Is it possible to add copy and paste function to aterm?

It already has copy/paste.

To copy, using the mouse, highlight the text with the left button held down.

If you then click the middle button, it will paste the text in the terminal
at the current cursor location.

Or, if you left click in an editor, then click the middle button, it will paste the
text in the editor at the current cursor location.

You can copy/paste from an editor to a terminal the same way.

It's not possible on touchpad.

[GNUser]

Hi Rich. The select-to-copy, middle-button-to-paste is a great feature. X11 called it "primary selection." I'm happy to say labwc kept it.

The feature may be absent from GNOME and Firefox soon, though, because it is "unexpected." And, you know, "Goodbye X11" and all. https://itsfoss.com/news/gnome-firefox-middle-click-paste-removal

I'm chomping at the bit to live in the GNOME utopia where nothing from yesteryear remains, where everything is shiny and new.

[Leee]

I think something similar to the "Tiny Core Deluxe" idea can be achieved simply through the use of alternative "onboot.lst" files to load sets (collections) of extensions to achieve the desired level of deluxity.  If that functionality is sufficient for what you have in mind then it's already there and is highly customizable right from the start.

@Rich - is it possible to specify multiple extension lists (at the same time) right from the boot loader?  So that you could specify, for instance, a base onboot.lst (common to all configs) -and- a desktop.lst or a web_server.lst etc to set up for a specific task?  Just thinking out loud on this - it doesn't seem all that hard to just load additional extensions after the initial bootup.

[Rich]

Hi Leee
The problem with that idea is that onboot.lst (or an alternative "onboot.lst") relies
on the extensions already being present in the cde directory.

So now we need to create ISOs that are bloated up with a bunch of extra extensions.
This sounds like it flies in the face of Tinycore philosophy.
 

[nick65go]

is it possible to specify multiple extension lists (at the same time) right from the boot loader?  So that you could specify, for instance, a base onboot.lst (common to all configs) -and- a desktop.lst or a web_server.lst etc to set up for a specific task?  Just thinking out loud on this - it doesn't seem all that hard to just load additional extensions after the initial bootup.

I think this is already possible, by using a new line in your boot-loader (grub or syslinux) and in that line just use use TC parameter lst=MyOnbootList-example.lst; multiply this line as many time as you like, just changing (in grub.cfg) your lst=

Or just enter in edit mode in grub and change on the fly your LST (if you have if already created and remember its name). But in general is so easy to just boot with minim TCZ and then just tce-load -iw multiple extensions in one go / line.

[neonix]

Because 64-bit version of TC will be more popular than 32-bit, download link should be in this page
http://tinycorelinux.net/downloads.html
not only here
http://tinycorelinux.net/ports.html

[nick65go]

If you want to know how much TC17 32 (kernel 6.18.2) bits could need to boot+run, then the answer is 27 MB RAM !
Yes, without swap in RAM and without swap on HDD, and without compiling anything. Amazing!
For the the details, if you are interested, see the topic

TC17 needs RAM: 71MB(CLI) or 90MB(GUI) just to run (which should be changed as "TC17 CLI booting with just 27 MB RAM"
https://forum.tinycorelinux.net/index.php/topic,28067.msg181777.html#msg181777
Maybe TC developers could implement the small changes I did to obtain this "performance" regarding minimal / tiny TC requirements.

[neonix]

Tiny Core Linux server edition with preinstalled telnet.
Headless Tiny Core Linux used as server.

[Leee]

Tiny Core Linux server edition with preinstalled telnet.
Headless Tiny Core Linux used as server.

What sort of server do you have in mind?

Much of what you need is already close at hand - except for telnetd.

telnet (client) is in busybox

telnetd (server) is in inetutils-servers.tcz... BUT it ends up symlinked into /usr/local/lib/inetutils/ instead of /usr/local/sbin/ so the system doesn't know where to find it.  I haven't tried it but I suspect that it would work if you add /usr/local/lib/inetutils to PATH... but DON'T DO SO WITHOUT CONSIDERING THE FOLLOWING:


The issue with telnetd has probably gone unnoticed because telnet is widely deprecated, with ssh/sshd being a much better alternative.  ssh and sshd are both included in openssh.tcz.

Headless setup is simple and I set up all of my Tiny Core installs to be accesible headlessly - even this, my main desktop - in case I might want to access it from some other machine here in the house (I'm behind a firewall so nothing's accepting incoming connections from the internet).  This practice has saved me a great deal of pain on more than one occasion and has proved super convenient on many other occasions.  My little in-house web server (an old thin client) hasn't had a monitor and keyboard hooked up to it in years.  Same with my backup/storage server.

[CNK]

I use telnetd, it's much easier than SSH in many respects when security isn't required (over a private LAN - definitely use encryption for connections over the internet). The path isn't unnoticed, but telnetd doesn't run as a daemon, it's supposed to be run by inetd (which is in Busybox).

Here is the line I use in /opt/inetd.conf to enable it. It's typical to specify the full path there regardless:

Code: [Select]

telnet stream tcp nowait root /usr/local/lib/inetutils/telnetd telnetd

Start inetd with:

Code: [Select]

inetd /opt/inetd.conf


[Leee]

Thanks CNK.  I hadn't taken inetd into account at all.

I use ssh for pretty much everything because of key authentication ("safer" and scripts don't need to worry about passwords) and because I regularly use SCP and SFTP - so openssh is kind of a one-stop shop.  And I do occasionally poke a hole in my firewall to allow an external connection for ssh/scp/sftp.