appbrowser problem

[stanner]

I am having a problem getting appbrowser to connect to the mirror site.

I am using 3.6 that was downloaded last Thursday.  (I need to set up a kiosk machine running a browser for a time clock.)

I have the network working and can resolve URL's.

I have TC talking to the internet and can use wget to download extensions manually from http://distro.ibiblio.org/tinycorelinux/3.x/tcz/

Having read a thread discussing apbrowser connection issues (http://forum.tinycorelinux.net/index.php?topic=7898.0), I have edited /opt/tcemirror and tried to enter the path from the wget command which did not work.  

I have shortened the entry to http://distro.ibiblio.org/tinycorelinux/ (reference the comment about getMirror() using the contents if /usr/share/doc/tc/release.txt).  

I have even edited /usr/share/doc/tc/release.txt so that it is blank and edited /opt/tcemirror to read http://distro.ibiblio.org/tinycorelinux/3.x/tcz/ without success.

What should the correct entry be for both files?

[maro]

I'd suggest not to screw up the determination of the proper repository by changing 'usr/share/doc/tc/release.txt' (unless you really know what you are doing).

Furthermore leave '/opt/tcemirror' initially on it's default value of http://distro.ibiblio.org/tinycorelinux/ (or http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/ for versions prior to v3.6).

To troubleshoot your issue I'd suggest to use 'tce-load' in a shell (e.g. tce-load -wil mirrors) as this might provide you with some warning messages that could help to identify your problem (and then report back to us here).

[stanner]

Here's a transcript of your requested test:

Downloading: mirrors.tcz
wget: can't open 'mirrors.tcz.md5.txt': Read-only file system
Connecting to distro.ibiblio.org (152.19.134.43:80)
wget: can't open 'mirrors.tcz': Read-only file system
md5sum: mirrors.tcz.md5.txt: No such file or directory
Error on mirrors.tcz

Note: I have booted from a cdrom and I had to include firmware.tcz on the cdrom following the wiki "Remastering TC" and "Integrating extensions into an ISO" pages.

[Guy]

Downloading: mirrors.tcz
wget: can't open 'mirrors.tcz.md5.txt': Read-only file system
Connecting to distro.ibiblio.org (152.19.134.43:80)
wget: can't open 'mirrors.tcz': Read-only file system
md5sum: mirrors.tcz.md5.txt: No such file or directory
Error on mirrors.tcz

Note: I have booted from a cdrom and I had to include firmware.tcz on the cdrom following the wiki "Remastering TC" and "Integrating extensions into an ISO" pages.

If you have a tce directory on the cd, it is read only, so you cannot add more apps.

To overcome this, have an ext4 partition on the hard drive, create the /tce/optional directory there, and put apps there. You can now write to the hard drive, so you can install more apps.

[maro]

Or if you just want a kind of "live CD" setup or for a one-off test you could change back to the "cloud mode" with
    echo /tmp/tce > /opt/.tce_dir
This overwrites the determination done during the boot process to assign the 'tce' directory to the read-only CD-ROM (which puzzles me a bit anyway as I would have thought that the scripts that control this matter should be "smart" enough to prevent this situation to occur). Clearly this is not a permanent solution as the one suggested in reply #3, since in the "cloud mode" all downloaded extensions will be lost when one reboots.

An alternative to including the entire 'firmware.tcz' extensions via a 'tce/optional' directory on the CD-ROM would be to integrate just the files one needs from the extension into the initrd (i.e. 'tinycore.gz') by following this Wiki page.

[roberts]

Users should never be instructed to create their live tce directory on a read-only device.
Users should never be instructed to be editing systems files to recover from such.
Talk about confusing users! Oh my!

[maro]

Users should never be instructed to create their live tce directory on a read-only device.
Users should never be instructed to be editing systems files to recover from such.
Talk about confusing users! Oh my!

Hmmm, I'm not quite sure what to make out of this. Are those of us who (at least consider themselves to be knowledgeable enough) provide troubleshooting support and suggestions? I don't know what went "wrong" to end up with the scenario as described in the OP (and reply #2), but I think I've indicated surprise. Nevertheless I was not aware that the files in '/opt' (whether hidden or not) are "sacred cows" never to be mentioned and not to "disturb the magic" that happens "under the covers" during the boot process.

[roberts]

Not only confusing to the OP but also subverts any efforts to support OP when such hacking is the first advice given. Obviously many things are broken when users are advised to setup their live tce directories on a read only device. They are not aware of it and therefore when things don't work and our forums are filled with complaints of such things not working.  Then to compound matters instead of explaining why things are not working. instruct the user to further hack the system. Tiny Core is easily hackable and obviously many of the regulars do. But it is bad advice to start users with. I feel the same way when I see new users told to sudo this and mkdir that and command line this, when an easy GUI is already provided. Gives a bad first impression of Tiny Core that one must be masterful with the command line as witnessed by the recent posts. I don't consider it "trouble shooting" to compound an already bad configuration. Instead only compounds the confusion. Apparently the Wiki needs some policing.

[Guy]

Robert

As far as I know, this is the only page which suggests having a tce directory on read only media.

http://wiki.tinycorelinux.net/wiki:integrating_extensions

This page has been in the wiki for over 2 years. It has been updated at times.

Do you object to this page?

[roberts]

I do object, especially, given the  outcome of the OP's 2nd post in the forum, i.e., a new user. The confusion in things not working and the discord of attempting to determine such and support such.

I do not read every wiki item. I suffer with limited vision. I have to rely on the team and a knowledgeable community to support my efforts to move this distro's ease of use forward.

We need to be on the same page to promote ease of use of the system and avoid that which does not.

[Guy]

Ask the team what they think of this page.

This page was written by a member of your team, over 2 years ago. It has been edited a number of times since.

I think it is useful, and should be kept.

It includes the following:

The CD is Read Only

While using the tce directory on the CD, you won't be able to install, update or remove applications

[Guy]

Robert

To please some people, you need to be able to read their mind, and then you can't because they change it.

I would like to see you taking a more positive approach.

People are trying to support what you are doing, and make a positive contribution, but they don't think exactly like you.

I would like to see you encouraging them. I am concerned that you may be discouraging them.

Tell us about important issues, but don't complain about trivial things.

If saying this upsets you so much that you don't want me to make any further contributions, let me know.

If you don't want me to make any further contributions, I wish you all the best in the future.

[stanner]

I must take the blame for the apparent hard feelings and consternation.  I completely missed the statement regarding the CD being read only.  As a long time Linux user (but a new TinyCore user), I know to search the documentation, wiki's and forums and to read.  What bit me was reading too much.

I had to add firmware.tcz to the ISO to get networking to function. 

I also assumed that, subject to ram limitations, applications could be added in memory, even when booted from a CD. 

Would the FAQ's be a place for simply restating that applications cannot be added when running from a CD and having a writeable persistance directory?

(By the way, when I understood my problem, my geeky pride took a hit.)

[aus9]

RE: wiki

WIKI in my mind and in the minds of most are "Unofficial" docuementation as they are provided my members.
Some members are moderators so their wiki has higher value?

If you go down the path of policing wikis....can I suggest you remove the right of anyone to edit and change to a wki submission process.

And as soon as you do that.....I predict wiki creations and wiki editting will die off at TC.

I feel very strongly about this.....sorry to take it personally.

IMHO having submitted useful and "useless" wiki pages, a friendly forum is made friendlier by having wikis
and any process that slows down wikis tends to cause that distro to fail

I am alluding to sidux wiki....which had numerous wiki pages and when it became aptosid the wiki pages that could have been there dropped off.

Of course the reason for that drop off....relates to the "friendliess" factor and that is my point.

end of rant

[gerald_clark]

Why would you recommend a procedure that you state will result in failure of the wiki?

Some level of trust should be established before unlimited edit rights are granted.
Verified registration or moderator approval of first article could be sufficient.

I have seen wikis filled with spam and . when no controls are in place.
That is much more likely to kill interest.