dCore-stretch

[Jason W]

dCore-stretch is now in the RC area.  Debian Stretch as of Nov 5 reached a transition freeze, and will reach a soft freeze on Jan 5 and a hard freeze on Feb 5.  I think we are good now to begin testing dCore-stretch.  I am using it now as my main desktop system, about a 1G sce, working nicely as expected, and will be keeping a lookout for base libraries that may get updated.  Anyone testing dCore-stretch is advised to run sce-update on all sces fairly frequently to ensure there are no conflicts in their sces due to updates of packages in Debian during the Debian testing cycle.

http://tinycorelinux.net/dCore/x86/release_candidates/dCore-stretch/

[netnomad]

hi jason,

what a great starting point to stretch, everything went so smooth for my first steps.
only a little error message according to the b44-modul.
unbelievable what good stable work you have already delivered :-)
in the attached photo you can see the boot messages.

thank you for your help and commitment.

[Jason W]

Hi netnomad,
Is this your first using a dCore with the 4.2.9 kernel?  The b44 or any other kernel behavior should be the same with any 4.2.9 dCore.  If these errors were not seen in other 4.2.9 dCores then there is an error somewhere in the packing of dCore-stretch.gz.

I remember having to blacklist ssb when I was using a usb wireless, and the errors on your screenshot look related to ssb. 

[netnomad]

hi jason,

yes, it's my first attempt to use 4.2.9.
in the former kernels i had to blacklist=snd_usb_audio.
lsmod shows me in 4.2.9 that the modules b44 and ssb are loaded,
so it seems to be only a cosmetic problem.
blacklist=ssb doesn't improve it.

thank you for any ideas and help.

[nitram]

Thanks for the Stretch release, running fine here.

[Jason W]

dCore-stretch has had it's base image updated due to minor updates to glibc and udev.   

[Jason W]

Being Stretch is in Debian's testing phase, they recently have further factored Glibc and this breaks current dCore-stretch installs for those who issue an update of SCEs.  I am working on bringing dCore-stretch base up to par with the Debian Stretch files that affect the dCore-stretch base image.

[Jason W]

Uploaded a new RC with the missing Glibc files.

[nitram]

Thanks for your hard work, updated boot list yesterday and everything is running well.

[Jason W]

There have been some minor updates to dCore-stretch involving the base files of glibc and gcc.  Users are advised to update their existing dCore-stretch to the latest release candidate.  This release candidate will be moved to release when there are no known issues in regards to this update.   

[Jason W]

dCore-stretch has been updated due to updates in libc6. 

http://tinycorelinux.net/dCore/x86/release_candidates/dCore-stretch/

[Jason W]

dCore-stretch has been updated due to an update in libc6 and other packages with files in the base system.

http://tinycorelinux.net/dCore/x86/release_candidates/dCore-stretch/

[Jason W]

dCore-stretch has been updated with Busybox version 1.27.2.

http://tinycorelinux.net/dCore/x86/release_candidates/dCore-stretch/

[PDP-8]

I just tested out dCore-stretch and dCore-plus-stretch with the new busybox 1.27.2.  THANK YOU Jason!

Appreciated how xterm in dCorePlus picked up on the built-in Luxi font with the usual ctrl-right click options etc.  Testing was just low key burn and boot from CD, using a home tce directory on a hard drive.  Works great.

I like busybox so much that I edited my path to put the /bb directory right up front in my .ashrc, and no problems there with dCore upon reboot.

When I put the /bb directory right up front in my path in .ashrc on dCorePlus however, it called the posix-police .. and dumps a temporary "-n" file in my home directory as punishment.

From memory:

Code: [Select]

expr: warning: '^/dev/tty[0-9]\+$'  ^ as the first character of a basic regular expression is not portable

mktemp unrecognized option --tmpdir
Hmm.. I never made a file beginning with a dash before, so this deletes it with the double-dash option (but it returns of course even after flushing it and a subsequent filetool.sh -b)

Code: [Select]

rm -- -n

Noticed too that if I just do a quickie without just manually editing my path, but use this instead in my .ashrc

Code: [Select]

PATH=/bb:$PATH

I'll end up with multiple instances of the /bb directory up front

Code: [Select]

echo $PATH
/bb:/bb:/home/tc  <==== rest of normal path

Just having fun with the RC's, and noting the quirks of putting busybox up front in the path.  Nothing crashes.... having a blast learning things...