WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: tinycore_v3.6rc3  (Read 9429 times)

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
tinycore_v3.6rc3
« on: April 17, 2011, 02:12:37 PM »
The Third Release Candidate of Tiny Core v3.6 is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates

tinycore_3.6rc3.iso
tinycore_3.6rc3.iso.md5.txt

Change log for rc1:

* Fixed mousetool for left handed 2 button serial mouse.
* Updated flrun - added input search capability.
* New tc-install.sh replaces usbinstall - added frugal install to partition with formatting options.
* New tc-install Fltk GUI front end to tc-install.sh callable from cpanel.
* Updated cpanel change to tc-install for HD/USB Install.
* Moved showrgb from base to Xprogs.
* Updated tce-load to better support download error conditions.
* Updated appbrowser to better support download error conditions.
* Updated ab - added tree and size views and overall presentation tweaks.
* New tcemirror.sh to present select list of both local (/opt/localmirrors) and remote (mirrors.tcz) mirrors.
* Updated appbrowser to also support local and remote mirror selection.
* Moved sethostname from function to script, callable from /opt/bootsync.sh

Change log for rc2:
* Added Select Mirror to Updates tab in AppsAudit.
* Updated search.sh and provides.sh to target new host server.
* Updated AppsAudit/tce-update to fetch new dependencies.
* Updated AppsAudit Updates to display info file.
* Updated tc-install to allow USB-HDD to select format option, corrected partition labeling.
* AppsAudit now handles lst= boot option for OnBoot maintenance.
* Updated tc-config moved keymap, secure, and protect to after extension loading but before restore.

Change log for rc3:
* Updated tc-install/tc-install.sh to support installs from .iso and text cleanup.
* Updated tc-config added -m option to chpasswd for consistency in password encoding.
* Updated /etc/.profile to determine proper EDITOR environment variable.
* Updated tce-setup to better support microcore when used with Xprogs.
* New mydata= boot code to support alternate name for backup. Defaults to mydata.tgz.
* Updated wallpaper to allow suppression of TC logo.

Please note release candidates are for the sole purpose of testing.
Please test carefully. Do not use for regular day to day use.

FYI: Feature freeze for 3.6
« Last Edit: April 17, 2011, 05:34:25 PM by roberts »
10+ Years Contributing to Linux Open Source Projects.

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: tinycore_v3.6rc3
« Reply #1 on: April 17, 2011, 10:07:05 PM »
mydata= works great. Thanks.
Now I can have mc and tc in the same tce directory.

Offline floppy

  • Hero Member
  • *****
  • Posts: 577
Re: tinycore_v3.6rc3
« Reply #2 on: April 18, 2011, 01:41:22 PM »
my beautifull picture from brittany in france.. is in still in "opt" but not displayed anymore on the screen.
boot option "bkg" buggy in tc3.6rc3? (in rc2 it was fine).
I can activate it with the wallpaper tool in the ControlPanel. Ouf..
« Last Edit: April 18, 2011, 01:46:08 PM by floppy »
AMD K6-IIIATZ 550MHz MB DFI K6xv3/+66
P4 HP DC7100 3GB 3GHz
Samsung NC10 boot from SD card port (via USB reader)
.. all TinyCore proofed

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: tinycore_v3.6rc3
« Reply #3 on: April 18, 2011, 01:50:32 PM »
I don't believe there was any change there.
It works for me.
Are you POSITIVE the jpg is in /opt/backgrounds ?

Offline floppy

  • Hero Member
  • *****
  • Posts: 577
Re: tinycore_v3.6rc3
« Reply #4 on: April 18, 2011, 02:00:50 PM »
yes.
Microcore works fine with another wallpaper in the same directory.
In tried 2 times. It dont appear on the screen of tcl3.6rc3; but the file is in the indicated directory.
Perhaps a new limitation in the size. Will have a look tomorrow at the size and will try the bootcode with the other wallpaper of my microcore 3.6rc3.
AMD K6-IIIATZ 550MHz MB DFI K6xv3/+66
P4 HP DC7100 3GB 3GHz
Samsung NC10 boot from SD card port (via USB reader)
.. all TinyCore proofed

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v3.6rc3
« Reply #5 on: April 18, 2011, 02:36:17 PM »
Both bkg and theme boot codes are relics from early TC v1.x days for JWM.
Now with ever increasing options for image, full, tile, center, fill which cannot be easily specified as a boot code. And since FLWM does not support themes, it would make sense to drop both bkg and theme as boot codes. Use control panel->wallpaper to easily select options desired.
10+ Years Contributing to Linux Open Source Projects.

Offline Guy

  • Hero Member
  • *****
  • Posts: 1089
Re: tinycore_v3.6rc3
« Reply #6 on: April 19, 2011, 06:17:19 AM »
I have successfully used the installer to install from the iso. This is good, as it gives the user more options, and avoids confusion.


Another issue, which is a variation on something we have discussed already.

I installed Tiny Core on a usb drive using the installer. I had already formatted it as ext2, so I chose "Existing Partition," and "No formatting, use existing." After installation, it would not boot.

However, it does boot after making the partition Boot or Active.

I think it would be a good idea to include an additional option for users here. When choosing "Existing Partition," I think users should be presented with a choice like:

Quote
Do you want your computer to boot Tiny Core? Select Yes if Tiny Core is the only operating system on the drive. Select No if you have another operating system on the same drive. Instead, add the Tiny Core boot commands to your bootloader.

If they select Yes, have the partition be made Boot or Active.

The wording could possibly be improved on, but I think you should get the idea.
« Last Edit: April 19, 2011, 06:21:01 AM by Guy »
Many people see what is. Some people see what can be, and make a difference.

Offline netnomad

  • Hero Member
  • *****
  • Posts: 1027
Re: tinycore_v3.6rc3
« Reply #7 on: April 21, 2011, 12:35:41 PM »
hi friends,

and what is the bootcode for the protected mode, something like mydata=mydata.tgz.bfe?

does the bootcode order make a difference?
is there a difference between
   1. tinycore restore=LABEL=tc protect mydata=mydata.tgz.bfe
   2. tinycore restore=LABEL=tc mydata=mydata.tgz.bfe protect !?

did someone succeed in restoring mydata.tgz.bfe in tinycore_v3.6rc3, in rc2 everything works fine for me?

Offline floppy

  • Hero Member
  • *****
  • Posts: 577
Re: tinycore_v3.6rc3
« Reply #8 on: April 21, 2011, 01:03:20 PM »
Both bkg and theme boot codes are relics from early TC v1.x days for JWM.
. Use control panel->wallpaper to easily select options desired.
how to make this setup persistent?
AMD K6-IIIATZ 550MHz MB DFI K6xv3/+66
P4 HP DC7100 3GB 3GHz
Samsung NC10 boot from SD card port (via USB reader)
.. all TinyCore proofed

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v3.6rc3
« Reply #9 on: April 21, 2011, 04:28:13 PM »
I have successfully used the installer to install from the iso. This is good, as it gives the user more options, and avoids confusion.


Another issue, which is a variation on something we have discussed already.

I installed Tiny Core on a usb drive using the installer. I had already formatted it as ext2, so I chose "Existing Partition," and "No formatting, use existing." After installation, it would not boot.

However, it does boot after making the partition Boot or Active.

I think it would be a good idea to include an additional option for users here. When choosing "Existing Partition," I think users should be presented with a choice like:

Quote
Do you want your computer to boot Tiny Core? Select Yes if Tiny Core is the only operating system on the drive. Select No if you have another operating system on the same drive. Instead, add the Tiny Core boot commands to your bootloader.

If they select Yes, have the partition be made Boot or Active.

The wording could possibly be improved on, but I think you should get the idea.
Looks like I got this working, It will mean an rc4 as I would want more testing on it.
Look for it in starting with rc4.
10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v3.6rc3
« Reply #10 on: April 21, 2011, 04:30:43 PM »
hi friends,

and what is the bootcode for the protected mode, something like mydata=mydata.tgz.bfe?

does the bootcode order make a difference?
is there a difference between
   1. tinycore restore=LABEL=tc protect mydata=mydata.tgz.bfe
   2. tinycore restore=LABEL=tc mydata=mydata.tgz.bfe protect !?

did someone succeed in restoring mydata.tgz.bfe in tinycore_v3.6rc3, in rc2 everything works fine for me?

Using protect automatically add the .bfe to data file to be restored.
If you had existing encrypted data then the password hashing has changed with the chpassd -m as noted in the change log. You may want to use the prior rc to restore it.
10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v3.6rc3
« Reply #11 on: April 21, 2011, 04:32:10 PM »
Both bkg and theme boot codes are relics from early TC v1.x days for JWM.
. Use control panel->wallpaper to easily select options desired.
how to make this setup persistent?

If you are using images then simply add /opt/backgrounds to /opt/.filetool.lst
10+ Years Contributing to Linux Open Source Projects.

Offline netnomad

  • Hero Member
  • *****
  • Posts: 1027
Re: tinycore_v3.6rc3
« Reply #12 on: April 22, 2011, 04:06:08 AM »
unencryptic backups, for example the bootcode mydata=data36 restores perfectly.

then i made a new backup in the protected mode and the data36.tgz.bfe was produced.

after a reboot with the bootcodes:
kernel (hd32)/boot/bzImage waitusb=5 mydata=data36 restore=LABEL=tc protect
the backup data36.tgz.bfe is not used at all.

my config files in /etc:
/etc/sysconfig/bfe             has the stored my password correctly.
/etc/sysconfig/mydata     has the standard-entry mydata, not common to my above example: data36

after i correct the /etc/sysconfig/mydata and i try to restore over the gui, /etc/sysconfig/bfe is deleted and the correct /etc/sysconfig/mydata is in /etc.

afterwards if i touch a new /etc/sysconfig/bfe with the correct password, i can restore the data36.tgz.bfe without any problems.
« Last Edit: April 22, 2011, 12:24:23 PM by netnomad »

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v3.6rc3
« Reply #13 on: April 22, 2011, 10:13:52 AM »
Could not reproduce. Works as expected.
Not sure of what you are attempting as it appears your config files are not what TC uses.
Perhaps you are, again,  attempting to mix manual, command line, with TC system generated encryption.
10+ Years Contributing to Linux Open Source Projects.

Offline floppy

  • Hero Member
  • *****
  • Posts: 577
Re: tinycore_v3.6rc3
« Reply #14 on: April 22, 2011, 11:14:36 AM »
Both bkg and theme boot codes are relics from early TC v1.x days for JWM.
. Use control panel->wallpaper to easily select options desired.
how to make this setup persistent?

If you are using images then simply add /opt/backgrounds to /opt/.filetool.lst
image.jpg and leuchtturm.jpg were already both in /opt/backgrounds
tcl3.6rc3 with bootcode bkg=image.jpg.. dont show the "image" (can be activated with the wallpaper menue)
mc3.6.3 with bootcode bkg=leuchtturm.jpg show the "leuchtturm" direct after boot
Curious. Different on both release.
the microcore is using the lst=microorg.lst bootoption, not tcl, which is automaticaly loading the onboot.lst file
AMD K6-IIIATZ 550MHz MB DFI K6xv3/+66
P4 HP DC7100 3GB 3GHz
Samsung NC10 boot from SD card port (via USB reader)
.. all TinyCore proofed