Re: Evaluating a port to RTEMS (embedded OS with single address space and no processes)

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

 



On Thu, Feb 4, 2016 at 5:42 PM, Shinose <shinose@xxxxxxxxx> wrote:
> On Thu, Feb 4, 2016 at 7:49 PM, Christian Mauderer
> <christian.mauderer@xxxxxxxxxxxxxxxxxx> wrote:
>> Am 04.02.2016 um 14:46 schrieb Roland Mainz:
>> > On Thu, Feb 4, 2016 at 1:40 PM, Christian Mauderer
>> > <christian.mauderer@xxxxxxxxxxxxxxxxxx> wrote:
[snip]
> We have successfully ported OpenSSH along with SFTP-Server for a Greenhills
> platform, where it was only having single address space and threads.
>
> But I could say it was really a painful work to resolve the global variables
> and data structures to each threads.

Gnnn... bit offtopic, but that reminds me of the two regrets the
original UNIX authors had:
1. Avoid spelling error and write creat() as create() - would have
saved lots of emails...
2. Global variables in the K&R C language, more or less inherited from
BCPL - caused *pain* over (first in the linker, than everywhere else)
and over again...

That said, global variables aren't the only issue, there are other
global resources like signals and other per-process or per-thread
properties which need to be tracked.

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz@xxxxxxxxxxx
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 3992797
 (;O/ \/ \O;)
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@xxxxxxxxxxx
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev



[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux