WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: tinycore_v2.10rc2  (Read 8842 times)

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v2.10rc2
« Reply #15 on: March 16, 2010, 06:35:55 AM »
The startup script of Xorg changes /etc/sysconfig/Xserver which is used to indicate the current Xserver, the one that exittc to uses to exit from.

Typically, I do not try to install Xorg from within any other Xserver, instead, I exit to prompt and use
ab Xorg

Early versions of exittc used a shotgun approach and tried successively Xvesa, Xfbdev, and finally Xorg. But such approach limits and is specific to the above collection.
10+ Years Contributing to Linux Open Source Projects.

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11541
Re: tinycore_v2.10rc2
« Reply #16 on: March 16, 2010, 06:36:58 AM »
Wishlist:
However on larger downloads it would be nice to see a progress meter.

Perhaps not optimal, but if you have a terminal window open, you can see what's going on from the wget commands echoed.

Again wishlist, but some sort of indication of progress on apps audit (where there's no indication in a terminal window) and things might take a while would be good.

Edit: a bit hard to tell as my connection is so poor, but I would guess update/check for updates did not find anything in /tce/optional that needs updating, but there's no indication of this?
« Last Edit: March 16, 2010, 06:43:45 AM by Juanito »

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7035
    • My Community Forum
Re: tinycore_v2.10rc2
« Reply #17 on: March 16, 2010, 06:46:00 AM »
The startup script of Xorg changes /etc/sysconfig/Xserver which is used to indicate the current Xserver, the one that exittc to uses to exit from.

Thanks, it was my suspect as well but had no time to go into details. Just checked Xorg-7.4.info instructions and while not explicitely refers to "Exit to prompt' instructions are not very precise how to install and start using. It would be good to enhance a bit :)

I will do it with my WIKI article too.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7035
    • My Community Forum
Re: tinycore_v2.10rc2
« Reply #18 on: March 16, 2010, 07:09:45 AM »
When 'Install Local Extension' used '... alerady installed' status message highlighted with yellow background, while finished installation is white. It just reversed compared to installation from remote repository.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline Onyarian

  • Sr. Member
  • ****
  • Posts: 336
Re: tinycore_v2.10rc2
« Reply #19 on: March 16, 2010, 09:11:53 AM »
Quote
When 'Install Local Extension' used '... alerady installed' status message highlighted with yellow background, while finished installation is white. It just reversed compared to installation from remote repository.

I find that the yellow final status is also interesting in the 'Install Local Extension' but with white starting, so after a download with 'connect to repository' is necessary a white refresh from the status message for the next apps load.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10161
Re: tinycore_v2.10rc2
« Reply #20 on: March 16, 2010, 09:38:36 AM »
I think the DEFAULT_BACKGROUND var in tc-config is now unused.
The only barriers that can stop you are the ones you create yourself.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v2.10rc2
« Reply #21 on: March 16, 2010, 06:12:37 PM »
That is true. Removed.

Speaking of some cleanup...
Someone had mentioned jwmTheme in .xsession
Code: [Select]
[ -n "$THEME" ] && cp /opt/jwmThemes/"$THEME" .jwmrc-themeSince jwm is an extension this option should be noted in the jwm extension info file.

And while we are at it.
Both flit and watcher are both extensions, so...
Code: [Select]
[ $(which flit) ] && flit &
[ $(which watcher) ] && watcher -g +0-0 &
Should also be removed and noted in their respective info files.

I had left them in .xsession only as a convience and possible example of both testing existence and starting extension upon startuo of X.

But if we are cleaning up a single unused variable, then these extension references should be removed from .xsession.
10+ Years Contributing to Linux Open Source Projects.

Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: tinycore_v2.10rc2
« Reply #22 on: March 16, 2010, 06:45:07 PM »
Talking of cleanups: I guess '/etc/inittab-save' is another candidate for removal. Bye the way, this file indicates to me that some time ago multiple terminals were used (which could be selected by Ctrl-Alt-Fn). I wonder if it would make sense to have at least one or two additional terminals available. I know, I could create a changed '/etc/inittab' file (and e.g. re-master the initrd) to (hopefully) achieve this. I just curious what lead to the decision to drop all but one.

With regards to the removal of entries from '/etc/skel/.xsession': I'd suggest to not merely mention something in some info files, but ensure that the '/usr/local/tce.installed' start-up scripts are adding those entries into '${HOME}/.xsession'. For a moment I thought of '/root/.xsession' as well, but since root should typically not start a X server, I'll now consider this a silly idea.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10161
Re: tinycore_v2.10rc2
« Reply #23 on: March 17, 2010, 01:41:42 AM »
Watcher info file edited.
The only barriers that can stop you are the ones you create yourself.

Offline jls

  • Hero Member
  • *****
  • Posts: 2133
Re: tinycore_v2.10rc2
« Reply #24 on: March 17, 2010, 07:27:54 AM »
I have problems with the new colors in the appbrowser, see attached screenshot
« Last Edit: March 17, 2010, 07:29:39 AM by jls_legalize »
dCore user

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10161
Re: tinycore_v2.10rc2
« Reply #25 on: March 17, 2010, 08:51:32 AM »
I have problems with the new colors in the appbrowser, see attached screenshot
Do you mean the status text?
The only barriers that can stop you are the ones you create yourself.

Offline jls

  • Hero Member
  • *****
  • Posts: 2133
Re: tinycore_v2.10rc2
« Reply #26 on: March 17, 2010, 08:52:55 AM »
yes
dCore user

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v2.10rc2
« Reply #27 on: March 17, 2010, 09:27:56 AM »
jwm & jwm-snapshot info files updated. flit info updated.

Extension references will be removed from .xsession as noted above.
« Last Edit: March 17, 2010, 09:57:50 AM by roberts »
10+ Years Contributing to Linux Open Source Projects.

Offline jls

  • Hero Member
  • *****
  • Posts: 2133
Re: tinycore_v2.10rc2
« Reply #28 on: March 20, 2010, 07:40:32 AM »
for example:
Code: [Select]
cat .wmx/OnDemand/alsa
#!/bin/sh
[ -e /opt/.tce_dir ] || exit 1
read TCEDIR < /opt/.tce_dir
[ -e /usr/local/tce.installed/alsa ] || tce-load -i $TCEDIR/optional/alsa.tcz
[ $(which alsa) ] && alsa
last line should terminate with an &
dCore user

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v2.10rc2
« Reply #29 on: March 20, 2010, 10:35:17 AM »
We don't run everything backgrounded. When backgrounding is necessary or desired you can enter such when prompted for the binary.
10+ Years Contributing to Linux Open Source Projects.