I have started my own MorphOS docs site.
you can email your docs to: rll@twc.com
Unless I am passed out from beer or dead asleep I will add your item to the site.

http://bettyboopdatabase.0usa.com/mos/mos.html

Yes...before you ask...I run a betty boop database also:
http://bettyboopdatabase.0usa.com/

Boop-Oop-A-Doop

Quote:

This is bad, very bad! Never change anything in MOSSYS:

You should create s:network-startup like this:

Code:

Well,

Submit a new doc to my email.
I will replace it.
In html is best.

p.s. Why would you execute mossys:s/network-startup from s:network-startup?
It is already being run on bootup.
This would execute it twice.


[ Edited by bash64 03.07.2013 - 22:15 ]

Quote:

s:network-startup has priority over MOSSYS:S/network-startup as I understand it.

Can you host a wiki on your site? It would make community collaboration much easier.

Not sure.
I would have to ask the domain owner if I can run a wiki.
Get back with you.

http://en.wikibooks.org/wiki/Starting_and_Running_a_Wiki_Website/Hosted_Wikis

Please look over this wiki host list and see if you can help me find a decent site to host the wiki.
A lot of the listed sites on this page are no longer doing wiki.

If you know of a good wiki site with minimal learning curve then please suggest it.
Thanks

ok,

The wiki site is up:

http://rll.wikidot.com/

You will have to ask for permission to edit articles.

You want to help me get it started with some articles?
I think I'd prefer an html to wiki converter.
Not sure how to make a link to an article and then enter the new article.


[ Edited by bash64 03.07.2013 - 23:01 ]

Quote:

My time is very limited, but I can contribute the odd thing or two when I do have time for sure.

I'll have a proper look at your site later today hopefully.

thanks

This site seems to be the kind where you have to learn to code in wiki code.
Not my thing. I prefer point and click.

Please remind me, what is wrong with the MorphZone Library?

Quote:


If you have S:network-startup file it's executed instead the one in mossys:s/. The one in mossys: has important things for system, so it needs to be run too, so you have to execute it from S:.

Why you shouldn't edit the one in mossys: only? Becaue it will be replaced in the next system update and you'll lose all your own tunings. When you create file in S: your own setup will be preserved in forthcoming updates.

Then about your page. That hidden ssid guide is too complicated. You don't need to do those things at all. Just edit envarc:sys/Wireless.prefs file and add scan_ssid=1 line under the ssid="yournetwork" line.

You can take any tips you want from my page too: http://jpv.wmhost.com/morphos/tips/index.html

But in any case, it would be better to get proper documentation under MorphZone's Library section. These own docs scattered everywhere will be getting lost and never found by new users.

ok,

Points of confusion:
1) There is a s:network-starup file and a mossys:s/network-startup file on my system and the scripts are identical.

I edited mossys:s/network-startup and ran wetter on bootup and everything worked fine.
Using your advice I removed that line and added it to the s:network-startup file and it now runs fine also.
I have not executed mossys:s/network-startup from within s:network-startup and am having no issues and doing so would execute the same code twice on bootup.
As I said, both scripts are identical so I find no basis for saying one script has important OS functions over the other.



Asiegel - Webmaster,
Nothing wrong with the MOS Library, I wish to run my own site.
If you want to borrow docs there is no copyright and all articles are public domain.

Document on running an app after the network comes up has been corrected to refer to s:network-startup.

Quote:

The startup-sequence executes s:network-startup, it also adds mossys:s as an assign to s:

So, when it attempts to execute s:network-startup it first looks at the default location for s: which is sys:s/ if it cannot be found it then looks in the next assigned place which is sys:morphos/s where it finds network-startup and executes it.

If sys:s/network-startup does exist it executes it and doesn't look for it anywhere else.

You need to keep the sys:morphos/s/network-startup and remove everything from sys:s/network-startup except the first line as a call to mossys:s/network-startup and then just the c:run commands you need after it.

Quote:

By default there isn't any S:network-startup file, only in mossys:. You must have duplicated it by mistake at some point. When created S:network-startup should only contain your own and 3rd party stuff... and that execute of the system's network-startup file in the first line.

I don't remember duplicatng it.
I will check both machine I am running.

I'm new to MorphOS but the old AmigaOS in later versions was to leave Startup-Sequence alone and edit user-startup instead for custom assigns etc.

> I'm new to MorphOS but the old AmigaOS in later versions was to leave
> Startup-Sequence alone and edit user-startup instead for custom assigns etc.

That's still the same for MorphOS:
- startup-sequence, network-startup and shell-startup in MOSSYS: are to be left alone
- user-startup, network-startup and shell-startup in SYS: are free to be edited by the user

Apparently on one of the machines I duplicated network-startup at some point.
The issue is fixed.

Quote:

You forgot to add the mention that the first line in s:network-startup must be:
execute MOSSYS:s/network-startup

Will get to that.

On the "Wireless - Connect to hidden SSID on boot" page, it might be a good idea to have some explanation that it doesn't actually make the network any more secure, such as this article.

It's good information. Sometimes you DO need to connect to a hidden network (and sometimes cannot do anything about it being hidden), but some people have it enabled just because they for some reason think it makes it more secure.

I'd like to give you some advices, what should also appear on the docs site:
- Setting up Rdesktop connection to a Win machine.
- Samba settings
- Booting an *.iso file (without writing in to a CD)
- Usefull openfirmware commands
- Usefull links (development, downloads, etc.)

[ Edited by dekanyz 05.07.2013 - 14:27 ]

dekanyz,

Your a breath of fresh air.
Thanks for the ideas.



Jupp3,
Well noted. I can include links to articles pointing out security weaknesses.

I will not have more time off work till monday july 8th.
I will get back to writing knowledge base articles then.
Feel free to email your own.
L8r