Off-Topic > Release Candidate Testing

microcore_v3.5rc1

(1/2) > >>

roberts:
The First Release Candidate of Micro Core v3.5 is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates/microcore

microcore_3.5rc1.iso
microcore_3.5rc1.iso.md5.txt

Change log for Micro Core v3.5:

* Clean up of tce-audit 'delete' spurious messages.
* New tce-remove support for tce-audit/appsaudit.
* Moved thinkpad_acpi.ko from base to extension.
* Updated tc-config crond call and removed duplicate crond script.
* Updated busybox 1.18.1 plus patches.
* Scripts adjusted to remove extra spaces to reduce size.
* fsck replaced with busybox fsck
* zsync upgraded to 0.6.2.
* Changed all core components from .gz to tcz.
  (Note need to add them to onboot.lst, order is important.)

gerald_clark:
Looks good.
I am already using gzs converted to tczs in my optional directory.

I was wondering if the rc core components could have rc in their names.
Ex: Xprogs-rc.tcz
I use symlinks to share optional between release and release-candidate tce directories.

tinypoodle:
Particularly using "rc" as suffix of files unrelated to 'run commands' might potentially lead to confusion.
Perhaps "-rel" or something else might be less problematic.

Lee:

--- Quote ---Perhaps "-rel" or something else might be less problematic.
--- End quote ---

Well... "-rel" would seem to lose the "condidate" part.  I like the idea of using some kind of signal, though.  How about something indicating to -which- rc it applies, for the benefit of those of us who don't do cleanup diligently?  Something like  Xprogs-3.5rc1.tcz

jur:

--- Quote from: roberts on January 29, 2011, 03:01:04 PM ---* Changed all core components from .gz to tcz.
  (Note need to add them to onboot.lst, order is important.)


--- End quote ---
What should the order be? If this is indeed important, it could perhaps be mentioned in the OP?

Navigation

[0] Message Index

[#] Next page