Tiny Core Base > Release Candidate Testing

tinycore_2.5rc2

<< < (3/3)

bmarkus:

--- Quote from: roberts on November 02, 2009, 12:24:52 AM ---
While there is still some debate whether to have too many (no harm) or not enough in certain (but rare) situations. I will try out an alternate build, but will do so for the next rc1 cycle, not  in our current rc cycle.


--- End quote ---

Thanks, that's fine. Problem with /dev/hda4 in the above example is that it is a misleading information, as it is just a place holder for real partions like /dev/hda5 which may be not so trivial for ordinary users not very familiar with LINUX and with certain applications (I do not have example).

JoXo009:


Starting a terminal and typing 'tce-update' results in a scary warning text.

Why not offering a working solution instead of making people feel bad who can't use command line.

The query feature probably could be offered without problems without leaving the running windows manager.

And a GUI solution for the update feature maybe is possible by creating a one time flag, resulting in auto-update during next reboot. So that the user could be adviced, 'Do you want to set a flag, that next reboot an auto-update is executed?

After setting that flag the user just would reboot and the extension update would be executed automatically. The auto-update should end with an auto-reboot bringing back the interface and possibly showing some message as 'Just successfully/unsucsessfully updated X extensions'.

I think such solution wouldnt be too difficult to implement and would be a great improvement in usability for all these users who are uncomfortable with command line.


----
remark to user experience with interface Tool->Upgrade

Clicking the interface Tool->Upgrade never resulted in update and stopped working totally in version 2.5rc.

roberts:
Appears that the jwm.tcz extension needs adjusting. You should post extension issues in the extension area under the jwm.tcz thread.

When testing a release candidate before you post, you should always verify your claim by booting base norestore. Doing such you will see the system menu is correct for the default window manager, thereby showing that it is an extension issue.

As to your suggestion, I have already answered it but will do so again:

--- Quote ---I did consider an option as suggested, but I have concerns on space requirements, up to double the size of current tce directory and on a smallish device, pendrive, or CF, etc, could be problematic.
--- End quote ---

BTW, You can run 'query' within X. And it is really not too difficult to "Exit to prompt" and type tce-update.

JoXo009:

--- Quote ---When testing a release candidate before you post, you should always verify your claim by booting base norestore
--- End quote ---
Good to know, thanks for the hint.


--- Quote ---concerns on space requirements, up to double the size of current tce directory
--- End quote ---

I think the update suggestion you already answered suggested to download updates with TC running into a second directory and then move the download during next reboot, what obviously means you need (double) space for the old and the new version of the extension.

That's not what I meant. My suggestion is exactly the same what a user would do. Rebooting with boot codes base norestore text and calling tce-update - My suggestion is to do it automatically by a script and to trigger the script by a flag (maybe the existence of the file 'update-requested) which can be set from running TC.


--- Quote ---And it is really not too difficult to "Exit to prompt" and type tce-update.
--- End quote ---
True, for an expert, who knows how - after a typo - to get through without plugging off electricity and ruin all his code, it's really not difficult.

But for someone who, following such suggestions crashed his system several times resulting in countless hours of rebuilding work, it can be a nightmare.

roberts:
base norestore text does not easily allow for wireless/dialup or other extension required net access.
That is why I had posted:
--- Quote ---In 2.5rc2 tce-update takes into consideration wireless and/or other net access issues, by allowing updates to occur with user selectable options to minimize the number of running extensions.
--- End quote ---

Navigation

[0] Message Index

[*] Previous page