Tiny Core Base > Release Candidate Testing

tinycore_v2.8rc3

<< < (11/12) > >>

curaga:
All of the inetutils clients will come in the future; unlike with dropbear, there have been updates since.

roberts:
Just a friendly reminder, release candidates are for public preview and testing only.
Anything can change based on public input before final release or next release candidate.
As such, one should not use release candidates as their primary system.
Thank you for your participation in testing and feedback.

roberts:
After reflecting on feedback from both microcore and tinycore topic areas, regarding both the .core.gz/initramfs change and the vfat/symlinks change.

Here is what I done:

1. Drop symlinks and use a simple text file, onboot.lst, for determining which to load on boot. I have modified tce-load, tce-setup, and appsaudit.

2. Add a new boot code lst=mylist.lst.  This will skip the onboot.lst and load up only that which is in mylist.lst I have modified tce-setup.

This should satisfy microcore users that need to 'preload' special extensions, keyboard, etc...,
then after boot can run tce-setup to get full X with onboot specified extensions.

3. Update tc-config to ensure persistent home and/or  persistent opt  is on a supported Linux file system. If not such boot code(s) will be ignored.  I have modified tc-config.

4. Leave usbinstall script as is. Fat support not cut. onboot.lst being a simple text file should present no issues hosted on fat file system.

I feel this will solve most issues and concerns expressed from the combined microcore and tinycore communities' feedback, while also providing even greater flexibility moving forward.

I have coded these changes and am in early testing phase. As such, I will issue a release candidate 4.

Robert

 

jur:
Interesting, that now for the 2nd time, tcl direction is changing to align almost exactly with how I have been using it.  I changed my setup to on-demand quite a few releases ago, tcl 2.8 has gone there. Now with rc3, I have been using my own onboot file instead of symlinks, tcl is going there also.  ;D

In my mind there is no doubt, tcl is unbeatable. Thanks very much Robert and the team.

tclfan:
Jur - this is where contribution and experience of others helps roberts to decide the best strategy.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version