Tiny Core Linux

Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: Juanito on February 11, 2016, 04:14:06 AM

Title: Core v7.0rc1
Post by: Juanito on February 11, 2016, 04:14:06 AM

Team Tiny Core is pleased to announce that Tiny Core 7.0 rc1 is available for public testing:

http://repo.tinycorelinux.net/7.x/x86/release_candidates/
http://repo.tinycorelinux.net/7.x/x86_64/release_candidates/

This is a release candidate. If you decide to help test, then please test carefully. We don't want anyone to lose data.

We appreciate testing and feedback.

If you use distribution files note that you need a new vmlinuz and core.gz (or rootfs.gz + modules.gz)

Changelog for 7.0 rc1:
* kernel updated to 4.2.9 with the latest stable patch, with these config changes:
  - minstrel enabled for some wireless cards
  - vmmouse disabled for VMWare + Xvesa
  - the cpu limit on the 64-bit kernel raised to 64
* busybox updated to 1.24.1
* busybox patched to fix "crontab -e" error
* glibc updated to 2.22
* gcc updated to 5.2.0
* e2fsprogs base libs/apps updated to 1.42.13
* util-linux base libs/apps updated to 2.27

Note:

* there is a drm/i915 kernel driver error pending a fix
* the alsa extensions have been refactored and updated
* the Xorg-7.7 extensions have been updated.
* there is a significant (+/-20mb) increase in CorePlus iso size due to an increase in firmware extension size
* most other extensions have been copied over from the 6.x repo

Title: Re: Core v7.0rc1
Post by: Misalf on February 12, 2016, 03:58:15 AM

I'm on tc-7.x since beta and didn't need to boot tc-6.x except for comparing things.

Only the drm/i915 kernel driver error still restricts me in using certain software, also some self made extensions might need a recompile of their containing apps but that's my own issue.
Everything else seems to work great.

One thing though, I'd like to suggest the following change in  tc-config  to workaround an error/usage message that appears if  util-linux  is extracted into an initrd.

Code: [Select]

--- tc-config.old
+++ tc-config.new
@@ -176,9 +176,9 @@
 else
  while [ ! -e /dev/rtc0 ]; do usleep 50000; done
  if [ -n "$NOUTC" ]; then
- hwclock -l -s &
+ /sbin/hwclock -l -s &
  else
- hwclock -u -s &
+ /sbin/hwclock -u -s &
  fi
 fi
 


Thanks!

Title: Re: Core v7.0rc1
Post by: Misalf on February 12, 2016, 06:46:45 AM

And this seems to be needed if  coreutils  is added to an initrd , otherwise  /tmp/98-tc.rules  won't get moved:

Code: [Select]

--- tc-config.old
+++ tc-config.new
@@ -149,7 +149,7 @@
 else
  echo "${BLUE}Scanning hard disk partitions to create ${YELLOW}/etc/fstab ${NORMAL}"
  /usr/sbin/rebuildfstab & fstab_pid=$!
- mv /tmp/98-tc.rules /etc/udev/rules.d/. 2>/dev/null
+ /bin/mv /tmp/98-tc.rules /etc/udev/rules.d/. 2>/dev/null
  /sbin/udevadm control --reload-rules &
 fi
 


I hope it's OK to request this kind workarounds, even though fixing such things is probably more a responsibility of whoever creates their own initrd.

Title: Re: Core v7.0rc1
Post by: curaga on February 12, 2016, 11:20:35 AM

I'd say it's fine if you come with patches ;)

Applied the hwclock one, but I don't understand why the mv path is needed. If GNU mv requires a library, say libattr for example's sake, surely you've added that library as well, and ran "sudo ldconfig -r /tmp/ex" to update ldconfig's caches?

Title: Re: Core v7.0rc1
Post by: Misalf on February 13, 2016, 05:33:05 AM

Deps have been added but I wouldn't have known ldconfig could be needed if rebooting, while everything is available from the very beginning.