WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Tiny Core v2.3.1  (Read 8409 times)

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Tiny Core v2.3.1
« on: September 12, 2009, 03:05:48 PM »
This is a bug fix release. No new features.
Tiny Core V2.3.1 is now posted at http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release/

Change log for 2.3.1
* Updated flwm, ignore Alt+Enter, removed "caught esc" debug message
* Fixed bug in tc-config regarding overwrite of cryptohome default home files.
* Fixed bug in tce-load regarding non-existent extensions via improved error handling.
* Fixed bug in swapfile GUI, needed a sudo.
* Dropped doswapfile boot code, use swapfile instead.
* Fixed tce-load/appbrowser to return to home or from where started.
* Enhanced appsaudit for better completion of marked deletions in a single pass.
* Cleanup logic in tce-load & desktop.sh to reduce calls and lessen appbrowser hangs.
* Upgraded flit for better battery reporting.
10+ Years Contributing to Linux Open Source Projects.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10957
Re: Tiny Core v2.3.1
« Reply #1 on: September 13, 2009, 01:57:09 AM »
- Unused function getbootdevice in tc-functions
- the new swapfile logic always scans for the file. I suggest moving the line
Quote
[ -z "$SWAPFILE" ] && SWAPFILE="$(autoscan 'tc.swp' 'f')"
inside the noswap check, so that the autoscan for a swapfile is not done with "noswap", but a swap file still works with "noswap swapfile=hda1" specified for example.
The only barriers that can stop you are the ones you create yourself.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: Tiny Core v2.3.1
« Reply #2 on: September 13, 2009, 06:02:31 AM »
On second thought, I think that swpafile should not be a candidate for autoscan.
I believe it is rare that one actually creates a swapfile, yet everyone pays for the delay of its autoscan.

Even if I move to noswap test as suggested, still everyone pays for the autoscan delay, unless they don't use any swap at all. I think typically users do have a swap partition and it is rare to have setup a swapfile. So why make users wait for an autoscan completion on a rarely used configuration. Witness the fact that it took so long for the bug in this area to even be reported.

I will make the use of a swapfile require the swapfile= boot option in the next cut.
10+ Years Contributing to Linux Open Source Projects.