Hello..
I tried booting tyros.. Initially i cud not.. got an error code 10... but later did boot successfully
in text mode..
in certain directories. the cmd "ls" works.. but not in all directories.. as of now what are the commands supported..? the ntxbase is initialized properly.well thats what the message says... chdir takes place (as per the message)...
in graphics mode..
clear does not work whereas in text mode this cmd works... i tried fiddling with all the keys on my keyboard.. for everythings it showed error...
the fate of "ls" remains as in text mode.
I pressed ctrl-c continously.. i got the following message:
/***********************************************/
Task 0 has caused an unrecoverable error
ASSERTION FAILED: gid != -1
Line: 436
Func: kill_task
P.S: Pink Screen of death - cool, haha? ;)))
direct comments to lonesome@lowlevel.ru
/***********************************************/
and the system hung..
well in text mode.. i dint get any message of this sort when i pressed ctrl-c continously..
of course the child process gets killed.. some mesg similar to this was shown in both txt and graohical modes..
Will make a small doc of this process...maybe we cud put it in our cvs repo..
Any comments on the booting process.. ???
How is the support for threads on tyros, at the moment ??
Cheers,
Chetan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> Hello..
> I tried booting tyros.. Initially i cud not.. got an
> error code 10... but later did boot successfully
> in text mode..
> in certain directories. the cmd "ls" works.. but not
> in all directories.. as of now what are the commands
> supported..?
standalone commands:
ls, cat, hexdump, less
These commands are supported in my local version, but some of them may not yet exist in 23th july snapshot.
ls not works... hmm i think that's because some pseudo-filesystems (mounted on /sys/proc, /sys/info and /sys/control) don't support readdir() yet
> in graphics mode..
<skipped>
> and the system hung..
> well in text mode.. i dint get any message of this
> sort when i pressed ctrl-c continously..
> of course the child process gets killed.. some mesg
you've found a bug :) After you press ctrl-c system tries to kill process currently attached to terminal. When you've already killed the shell, there is no more processes attached to terminal, so system tries to kill already killed process and panics.
> similar to this was shown in both txt and graohical
> modes..
>
> Will make a small doc of this process...maybe we cud
> put it in our cvs repo..
Yes, this is a good idea
> Any comments on the booting process.. ???
> How is the support for threads on tyros, at the
> moment ??
there was support for threads until 0.01, then there were no work on threads (because there were no need in them). Although there is load_thread() syscall, i'm not sure it works with new versions. I'll devote more work to threads when they are really useful in tyros
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello..
I tried booting tyros.. Initially i cud not.. got an error code 10... but later did boot successfully
in text mode..
in certain directories. the cmd "ls" works.. but not in all directories.. as of now what are the commands supported..? the ntxbase is initialized properly.well thats what the message says... chdir takes place (as per the message)...
in graphics mode..
clear does not work whereas in text mode this cmd works... i tried fiddling with all the keys on my keyboard.. for everythings it showed error...
the fate of "ls" remains as in text mode.
I pressed ctrl-c continously.. i got the following message:
/***********************************************/
Task 0 has caused an unrecoverable error
ASSERTION FAILED: gid != -1
Line: 436
Func: kill_task
P.S: Pink Screen of death - cool, haha? ;)))
direct comments to lonesome@lowlevel.ru
/***********************************************/
and the system hung..
well in text mode.. i dint get any message of this sort when i pressed ctrl-c continously..
of course the child process gets killed.. some mesg similar to this was shown in both txt and graohical modes..
Will make a small doc of this process...maybe we cud put it in our cvs repo..
Any comments on the booting process.. ???
How is the support for threads on tyros, at the moment ??
Cheers,
Chetan
> Hello..
> I tried booting tyros.. Initially i cud not.. got an
> error code 10... but later did boot successfully
> in text mode..
> in certain directories. the cmd "ls" works.. but not
> in all directories.. as of now what are the commands
> supported..?
shell builtins:
cd, pwd, ps, go, up, load, unload, rm, mkdir, mount, touch, clear
standalone commands:
ls, cat, hexdump, less
These commands are supported in my local version, but some of them may not yet exist in 23th july snapshot.
ls not works... hmm i think that's because some pseudo-filesystems (mounted on /sys/proc, /sys/info and /sys/control) don't support readdir() yet
> in graphics mode..
<skipped>
> and the system hung..
> well in text mode.. i dint get any message of this
> sort when i pressed ctrl-c continously..
> of course the child process gets killed.. some mesg
you've found a bug :) After you press ctrl-c system tries to kill process currently attached to terminal. When you've already killed the shell, there is no more processes attached to terminal, so system tries to kill already killed process and panics.
> similar to this was shown in both txt and graohical
> modes..
>
> Will make a small doc of this process...maybe we cud
> put it in our cvs repo..
Yes, this is a good idea
> Any comments on the booting process.. ???
> How is the support for threads on tyros, at the
> moment ??
there was support for threads until 0.01, then there were no work on threads (because there were no need in them). Although there is load_thread() syscall, i'm not sure it works with new versions. I'll devote more work to threads when they are really useful in tyros