WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: tinycore_v2.0rc3  (Read 6599 times)

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
tinycore_v2.0rc3
« on: May 26, 2009, 07:08:57 AM »
Now ready for testing Tiny Core V2.0 Release Candidate 3.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release/

Combined change log:
rc1:
* New kernel 2.6.29.1
* New glibc 2.9
* New libstdc++ and libgcc
* New ldconfig
* New base Xlibs
* New squashfs module to base for support of squash'ed extensions.
* New cryptohome to use AES.
* New mount and losetup
* New virtual drive support.
* Updated .xsession
* Updated mousetool
* Updated appbrowser
rc2:
* FLWM replaces JWM (see notes below)
* New tc-config & desktop.sh to support for window managers via WM interface programs.
* New cd-dvd-symlinks.sh to create generic cdrom and dvd devices.
* New updated udev rules 75-cd-dvd.rules to automatically create cdrom and dvd device names.
* Updated .xsession to call wbar.sh to support a single point for options.
* Updated wbar.sh to retain HOME focus.
* Updated xsetup.sh mouse menu label change.
* Added /usr/local/sbin, /usr/local/bin to boot time PATH.
* Added tce-wget wrapper for CLI alternate to appbrowser.
* Updated flpicsee, new scaling, zomming, and popup informaton.
* Updated appbrowser Search now searches v2.x repositories.
* Updated cpanel to use generic HOME for tftpd.
* Updated extitc to be smaller via a single nix call.
rc3:
* New microcore boot option boots without the X system.
* New architecture with the X system factored into core elements in /opt/tce to support the microcore boot option.
* Updated imlib2 to 1.4.2
* Squashfs support for extensions has been enabled.
* Added Esetroot for background image support.
* Updated cpanel - Backgrounds button returns.
* Updated wallpaper GUI now supports multiple window managers via standardized calls to interface files. (See notes below)
* New flwm_setbackground supports background both images and colors for flwm and is part of the standard WM interface.
* New extension driven "desktop" boot option. Adding a WM extension no longer requires the corresponding desktop=xyz option.
* New restore=xyz-less restore. If your mydata.tgz is moved to or otherwise specified to use the same location as your extensions then no need to specify restore=xyz.

Files likely in your backup that need update:
.xsession
/opt/.xfiletool.lst

Note:  home/tc/.desktop file should be added to /opt/.xfiletool.lst

Notes: In order for the window manager extension driven opt to work and for Backgrounds support each window manager extensions needs to supply the following interface files:

wm_initmenu
wm_makemenu
wm_restart
wm_setbackground

Where "wm" is replaced by the actual window manager name, e.g.,

hackedbox_initmenu
hackedbox_makemenu
hackedbox_restart
hackedbox_setbackground

See examples in flwm in the base at /usr/bin/flwm*, and/or see the extensions jwm and/or hackedbox
« Last Edit: May 26, 2009, 07:45:04 AM by roberts »
10+ Years Contributing to Linux Open Source Projects.

Offline robc

  • Sr. Member
  • ****
  • Posts: 447
Re: tinycore_v2.0rc3
« Reply #1 on: May 26, 2009, 12:09:15 PM »
Quote
Notes: In order for the window manager extension driven opt to work and for Backgrounds support each window manager extensions needs to supply the following interface files:

wm_initmenu
wm_makemenu
wm_restart
wm_setbackground
Are the menu interfaces required when using a window manager that does not have a menu? (i.e. evilwm)

or should they be kept as a blank file or only with
Code: [Select]
#!/bin/shin them?

Edit:
I booted tinycore_v2.0rc3 with the boot code desktop=hackedbox and have hackedbox and dependencies in my tce folder. Upon startup hackedbox does not start. The background is set to black and wbar starts. hackedbox isn't in top. I killed Xvesa then ran startx...this started the windowmanager
I also tried jwm, aewm++, and tinywm and got the same results
« Last Edit: May 26, 2009, 01:21:59 PM by robc »
"Never give up! Never surrender!" - Commander Peter Quincy Taggart

"Make it so." - Captain Picard

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v2.0rc3
« Reply #2 on: May 26, 2009, 05:04:23 PM »
A black screen with large X cursor means you have no window manger.
Did you .xfilelist your .desktop so that it does not conflict?
Did you upgdade your .xsession?
Did you grab the latest hackedbox extension whose info says says it is for rc3?

Obviously sometime as you describe would not make it past QA let alone my testing.
It has to be a file out of sync, start with the two I suggested.
10+ Years Contributing to Linux Open Source Projects.

Offline junan

  • Jr. Member
  • **
  • Posts: 88
Re: tinycore_v2.0rc3
« Reply #3 on: May 27, 2009, 01:36:21 AM »
with background/wallpaper and working Application menu ... flwm is OK!
for install hackedbox , i don't know why , but i need to reboot 2 times
and the window manager works. first time reboot i dont have any window
manager. and when i back again to flwm , i need 2 time to reboot to make
it back to flwm.

after that change from and to hackedbox or flwm works fine ...
fun and fearless ...

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v2.0rc3
« Reply #4 on: May 27, 2009, 06:06:11 AM »
Thanks for feedback. I am continuing to try to improve in this area.
Do you have a fast or slow machine? Does adjusting sleep in .xsession help?
When you get a black screen with no wm, you can typically ctrl-alt-bksp to get back to cli prompt.
When at cli $ prompt what is the contents of /etc/sysconfig/desktop and /home/tc/.desktop?
While still at cli $, does typing startx then properly start the wm without rebooting or adjusting any configuration?
10+ Years Contributing to Linux Open Source Projects.

Offline robc

  • Sr. Member
  • ****
  • Posts: 447
Re: tinycore_v2.0rc3
« Reply #5 on: May 27, 2009, 09:21:06 AM »
Quote
A black screen with large X cursor means you have no window manger.
Did you .xfilelist your .desktop so that it does not conflict?
Did you upgdade your .xsession?
Did you grab the latest hackedbox extension whose info says says it is for rc3?
I am not using a backup so .xsession and .desktop should be what is in the base system. I do have the updated hackedbox for 2.0rc3.

I tried this again with jwm (2.0rc3 version) today without the desktop bootcode (no bootcodes used). The .desktop and /etc/sysconfig/desktop both have the correct window manager:
Code: [Select]
tc@box:~$ cat .desktop
wm: jwm
icons: wbar
tc@box:~$ cat /etc/sysconfig/desktop
jwm
but jwm did not start....using jwm & or ./.xsession & in a terminal fixes this

Quote
Note:  home/tc/.desktop file should be added to /opt/.xfiletool.lst
my .desktop file has jwm as the window manager without the need to use a backup as seen above.


Edit:
having base-devs.tce in the tce directory on boot causes the window manager to not start  ???
« Last Edit: May 27, 2009, 10:19:21 AM by robc »
"Never give up! Never surrender!" - Commander Peter Quincy Taggart

"Make it so." - Captain Picard

Offline siriusfox

  • WikiUser
  • *
  • Posts: 4
Re: tinycore_v2.0rc3
« Reply #6 on: May 27, 2009, 07:00:40 PM »
Is there any way to get back the traditional Window manager found in 1.x for this release?

Offline junan

  • Jr. Member
  • **
  • Posts: 88
Re: tinycore_v2.0rc3
« Reply #7 on: May 27, 2009, 09:01:40 PM »
Quote
Is there any way to get back the traditional Window manager found in 1.x for this release?

install jwm.tce , and add desktop=jwm in kernel parameter
fun and fearless ...

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v2.0rc3
« Reply #8 on: May 27, 2009, 09:41:03 PM »
Just a friendly reminder, all release candidates are not final.

Anything and eveything should be consider in flux until 2.0 final.

That is why I ask, do not remaster release candidates, the final could be significantly different.
Since 2.0 is addressing the support of alternate window managers, the extensions being used during testing, namely, jwm.tc(e,z} and hackedbox.tc{e,z} should also be considered in flux and checked often for updates during the testing cycle.

Note with 2.0rc3 and using the latest jwm.tce one should not need the desktop=jwm boot option.

I continue to thank those who have decided to participate in the road to 2.0.
10+ Years Contributing to Linux Open Source Projects.

Offline alu

  • Sr. Member
  • ****
  • Posts: 429
Re: tinycore_v2.0rc3
« Reply #9 on: May 28, 2009, 01:53:32 PM »
i must say Tc 2.0 is a winner; the only thing which i miss is skype; although not tc depending, i guess

Offline meo

  • Hero Member
  • *****
  • Posts: 563
Re: tinycore_v2.0rc3
« Reply #10 on: May 28, 2009, 03:16:33 PM »
Hi Robert!

I have tried TC v2.0rc3 for a while and I still have issues with the jwm extension. Flwm works just fine but when I load jwm.tce and reboot I get the famous black screen with an x. The wbar appears though but no menu. I know that I probably can't give it a fair try because I have a pretty complicated 12-boot system on my 8+ year old laptop. I have to be a bit careful not to mess up this system. So for now I go with the v2.0rc1 version since I prefer jwm over flwm. This might seem to be a negative post but I really appreciate the TC v2.0 and I think it will be just fine when the final release comes.

Have fun and many thanks for the work you put down,
meo

PS I have 2 versions of DSL, 8 versions of TC, Windows XP and the last version of ubuntu in the 12-boot system. So I pick the one that fits best with what I'm going to do and boot that one DS
"All that is very well," answered Candide, "but let us cultivate our garden." - Francois-Marie Arouet Voltaire

Offline Kingdomcome

  • Sr. Member
  • ****
  • Posts: 286
Re: tinycore_v2.0rc3
« Reply #11 on: May 28, 2009, 06:44:12 PM »
I was seeing the same behavior when trying to use jwm as well.  I was seeing a "could not open display" error after the creation of .XAuthoriy that I assumed was from jwm starting. Following Roberts suggestion to play with the sleep time in .xsession, I had no success.  So tried adding a "sleep 1" before the line that starts the WM and jwm has started properly since.  I rebooted at least 10 times to test, and that appears to be working for me.  FWIW I am using fairly new hardware that would boot 2.0rc2 to the desktop in about 10 seconds.

Kingdomcome

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v2.0rc3
« Reply #12 on: May 28, 2009, 06:52:07 PM »
Thanks for the feedback. I am working to improve consistency in this area by deprecating .desktop this will be in the next rc.
« Last Edit: May 28, 2009, 06:54:40 PM by roberts »
10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v2.0rc3
« Reply #13 on: May 28, 2009, 09:41:43 PM »
Quote
Are the menu interfaces required when using a window manager that does not have a menu? (i.e. evilwm)

or should they be kept as a blank file or only with
Code:
#!/bin/sh
in them?
Good point. I am addressing this in the next RC.
If they, the interface files, don't exist, they won't try to execute.
So, bottom line, no. YOu should not be required to make empty ones.
10+ Years Contributing to Linux Open Source Projects.

Offline robc

  • Sr. Member
  • ****
  • Posts: 447
Re: tinycore_v2.0rc3
« Reply #14 on: May 29, 2009, 07:23:41 AM »
Quote
Good point. I am addressing this in the next RC.
If they, the interface files, don't exist, they won't try to execute.
So, bottom line, no. YOu should not be required to make empty ones.
I can update those extensions for 2.0rc3 now  :)
Thank you for the hard work
"Never give up! Never surrender!" - Commander Peter Quincy Taggart

"Make it so." - Captain Picard