Re: RSB documentation

[Sebastian Huber]

- Am 10. Jan 2019 um 0:51 schrieb Chris Johns chr...@rtems.org:

> On 10/1/19 3:41 am, Gedare Bloom wrote:
>> I'm OK with this proposal.  We used to include quite messy details about how 
>> to
>> bootstrap your own GCC in the user manual. This is a bit nicer. ;) At the
>> maturity of RSB now, merging the doco with the User Manual is sensible.
> 
> Agreed, this is sensible. I am fine with this happening.

At which position in the manual should it be placed? I think we should organize 
the chapters according to the relevance for new users and how the are used 
later during application development. I would use the RSB chapter as a 
reference chapter containing all the details and cover the common case in the 
Quick Start chapter. So, I would move the RSB chapter to the end after the Host 
Tools.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH] user: Add RSB content as a chapter

[Sebastian Huber]

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
From 85d0ca332ec5c86f793fbc00654db889b3e9a786 Mon Sep 17 00:00:00 2001
From: Sebastian Huber 
Date: Fri, 11 Jan 2019 10:20:08 +0100
Subject: [PATCH] user: Add RSB content as a chapter

Remove the separate RSB manual.
---
 rsb/conf.py  | 14 --
 rsb/index.rst| 40 
 rsb/wscript  | 11 
 user/index.rst   | 33 ---
 {rsb => user/rsb}/bug-reporting.rst  |  0
 {rsb => user/rsb}/commands.rst   |  0
 {rsb => user/rsb}/configuration.rst  |  0
 {rsb => user/rsb}/cross-canadian-cross.rst   |  0
 {rsb => user/rsb}/history.rst|  0
 rsb/source-builder.rst => user/rsb/index.rst | 15 +++
 {rsb => user/rsb}/project-sets.rst   |  0
 {rsb => user/rsb}/third-party-packages.rst   |  0
 {rsb => user/rsb}/why-build-from-source.rst  |  0
 wscript  |  1 -
 14 files changed, 33 insertions(+), 81 deletions(-)
 delete mode 100644 rsb/conf.py
 delete mode 100644 rsb/index.rst
 delete mode 100644 rsb/wscript
 rename {rsb => user/rsb}/bug-reporting.rst (100%)
 rename {rsb => user/rsb}/commands.rst (100%)
 rename {rsb => user/rsb}/configuration.rst (100%)
 rename {rsb => user/rsb}/cross-canadian-cross.rst (100%)
 rename {rsb => user/rsb}/history.rst (100%)
 rename rsb/source-builder.rst => user/rsb/index.rst (94%)
 rename {rsb => user/rsb}/project-sets.rst (100%)
 rename {rsb => user/rsb}/third-party-packages.rst (100%)
 rename {rsb => user/rsb}/why-build-from-source.rst (100%)

diff --git a/rsb/conf.py b/rsb/conf.py
deleted file mode 100644
index 2f3258a..000
--- a/rsb/conf.py
+++ /dev/null
@@ -1,14 +0,0 @@
-import sys, os
-sys.path.append(os.path.abspath('../common/'))
-
-from conf import *
-
-project = "RTEMS Source Builder"
-
-latex_documents = [
-('index',
- 'rsb.tex',
- u'RTEMS Source Builder',
- u'RTEMS Documentation Project',
- 'manual'),
-]
diff --git a/rsb/index.rst b/rsb/index.rst
deleted file mode 100644
index f4594ed..000
--- a/rsb/index.rst
+++ /dev/null
@@ -1,40 +0,0 @@
-.. SPDX-License-Identifier: CC-BY-SA-4.0
-
-.. comment Heading
-.. comment  1  ==
-.. comment  2  --
-.. comment  3  ~~
-.. comment  4  ^^
-
-.. highlight:: shell
-
-=
-RTEMS Source Builder (|version|).
-=
-
- | **COPYRIGHT (c) 2012 - 2015.**
- | **Chris Johns **
- | **COPYRIGHT (c) 2016-2018.**
- | **RTEMS Foundation, The RTEMS Documentation Project**
-
- | **License:**
- |  Creative Commons Attribution-ShareAlike 4.0 International Public License
- |  https://creativecommons.org/licenses/by-sa/4.0/legalcode
-
-.. include:: ../common/header.rst
-
-.. toctree::
-:maxdepth: 5
-:numbered:
-
-source-builder
-why-build-from-source.rst
-project-sets
-cross-canadian-cross
-third-party-packages
-configuration
-commands
-bug-reporting
-history
-
-* :ref:`genindex`
diff --git a/rsb/wscript b/rsb/wscript
deleted file mode 100644
index 26ab0ca..000
--- a/rsb/wscript
+++ /dev/null
@@ -1,11 +0,0 @@
-from sys import path
-from os.path import abspath
-path.append(abspath('../common/'))
-
-from waf import cmd_configure as configure
-from waf import cmd_build as build
-from waf import cmd_options as options
-from waf import spell
-from waf import cmd_spell
-from waf import linkcheck
-from waf import cmd_linkcheck
diff --git a/user/index.rst b/user/index.rst
index 2a92121..e20a22b 100644
--- a/user/index.rst
+++ b/user/index.rst
@@ -6,6 +6,8 @@
 RTEMS User Manual (|version|).
 ==
 
+ | **COPYRIGHT (c) 2012 - 2015.**
+ | **Chris Johns **
  | **COPYRIGHT (c) 2016-2018.**
  | **RTEMS Foundation, The RTEMS Documentation Project**
 
@@ -16,27 +18,28 @@ RTEMS User Manual (|version|).
 .. include:: ../common/header.rst
 
 .. toctree::
-	:maxdepth: 5
-	:numbered:
+:maxdepth: 5
+:numbered:
 
-	overview/index
-	ecosys/index
+overview/index
+ecosys/index
 
-	start/index
-	hosts/index
-	installation/index
+start/index
+hosts/index
+installation/index
 
-	hardware/index
-	bsps/index
+hardware/index
+bsps/index
 
-	exe/index
-testing/index
-tracing/index
+exe/index
+testing/index
+tracing/index
 
-	tools/index
+tools/index
+rsb/index
 
-	support/index
+support/index
 
-	glossary/index
+glossary/index
 
 * :ref:`genindex`
diff --git a/rsb/bug-reporting.rst b/user/rsb/bug-reporting.rst
similarity index 100%
rename from rsb/bug-reporting.rst
rename

[PATCH] Reformat and update copyright and license notices

[Sebastian Huber]

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
From 77ba5c92fcf9c9f1e16a6b46cdc20d784092f070 Mon Sep 17 00:00:00 2001
From: Sebastian Huber 
Date: Fri, 11 Jan 2019 10:39:19 +0100
Subject: [PATCH] Reformat and update copyright and license notices

For everything before 2015 an OAR copyright is assumed.  Later copyright
notices are based on Git commits on a best effort basis.

The copyright notices of the "RTEMS Software Engineering Handbook" and
the "RTEMS CPU Architecture Supplement" are incomplete.
---
 bsp-howto/index.rst| 16 
 c-user/index.rst   | 15 ---
 common/license.rst |  6 ++
 cpu-supplement/index.rst   | 15 +++
 develenv/index.rst | 13 +
 eclipse/index.rst  |  9 -
 eng/index.rst  | 13 +
 filesystem/index.rst   | 13 +
 networking/index.rst   | 14 ++
 porting/index.rst  | 13 +
 posix-compliance/index.rst | 11 ---
 posix-users/index.rst  | 15 +++
 shell/index.rst| 16 
 user/index.rst | 20 
 14 files changed, 90 insertions(+), 99 deletions(-)
 create mode 100644 common/license.rst

diff --git a/bsp-howto/index.rst b/bsp-howto/index.rst
index fc02463..730693f 100644
--- a/bsp-howto/index.rst
+++ b/bsp-howto/index.rst
@@ -4,14 +4,14 @@
 RTEMS BSP and Driver Guide (|version|).
 ===
 
- | **COPYRIGHT (c) 1988 - 2015.**
- | **On-Line Applications Research Corporation (OAR).**
- | **COPYRIGHT (c) 2016-2018.**
- | **RTEMS Foundation, The RTEMS Documentation Project**
-
- | **Licenses:**
- |  Creative Commons Attribution-ShareAlike 4.0 International Public License
- |  https://creativecommons.org/licenses/by-sa/4.0/legalcode
+.. topic:: Copyrights and License
+
+| © 2017 Christian Mauderer
+| © 2016, 2018 embedded brains GmbH
+| © 2016, 2018 Sebastian Huber
+| © 1988, 2017 On-Line Applications Research Corporation (OAR)
+
+.. include:: ../common/license.rst
 
 .. include:: ../common/header.rst
 
diff --git a/c-user/index.rst b/c-user/index.rst
index 2ef7ca4..f52b2f2 100644
--- a/c-user/index.rst
+++ b/c-user/index.rst
@@ -4,14 +4,15 @@
 RTEMS Classic API Guide (|version|).
 
 
- | **COPYRIGHT (c) 1988 - 2015.**
- | **On-Line Applications Research Corporation (OAR).**
- | **COPYRIGHT (c) 2016-2018.**
- | **RTEMS Foundation, The RTEMS Documentation Project**
+.. topic:: Copyrights and License
 
- | **Licenses:**
- |  Creative Commons Attribution-ShareAlike 4.0 International Public License
- |  https://creativecommons.org/licenses/by-sa/4.0/legalcode
+| © 2017 Chris Johns
+| © 2017 Kuan-Hsun Chen
+| © 2016, 2018 embedded brains GmbH
+| © 2016, 2018 Sebastian Huber
+| © 1988, 2018 On-Line Applications Research Corporation (OAR)
+
+.. include:: ../common/license.rst
 
 .. include:: ../common/header.rst
 
diff --git a/common/license.rst b/common/license.rst
new file mode 100644
index 000..9b88646
--- /dev/null
+++ b/common/license.rst
@@ -0,0 +1,6 @@
+.. SPDX-License-Identifier: CC-BY-SA-4.0
+
+.. Copyright (C) 2019 embedded brains GmbH
+
+This document is available under the
+`Creative Commons Attribution-ShareAlike 4.0 International Public License `_.
diff --git a/cpu-supplement/index.rst b/cpu-supplement/index.rst
index 6c2f2a9..f80373d 100644
--- a/cpu-supplement/index.rst
+++ b/cpu-supplement/index.rst
@@ -4,14 +4,13 @@
 RTEMS CPU Architecture Supplement (|version|).
 ==
 
- | **COPYRIGHT (c) 1988 - 2015.**
- | **On-Line Applications Research Corporation (OAR).**
- | **COPYRIGHT (c) 2016-2018.**
- | **RTEMS Foundation, The RTEMS Documentation Project**
-
- | **Licenses:**
- |  Creative Commons Attribution-ShareAlike 4.0 International Public License
- |  https://creativecommons.org/licenses/by-sa/4.0/legalcode
+.. topic:: Copyrights and License
+
+| © 2016, 2018 embedded brains GmbH
+| © 2016, 2018 Sebastian Huber
+| © 1988, 2018 On-Line Applications Research Corporation (OAR)
+
+.. include:: ../common/license.rst
 
 .. include:: ../common/header.rst
 
diff --git a/develenv/index.rst b/develenv/index.rst
index ddf62d4..d56a73f 100644
--- a/develenv/index.rst
+++ b/develenv/index.rst
@@ -4,14 +4,11 @@
 RTEMS Development Environment Guide (|version|).
 
 
- | **COPYRIGHT (c) 1988 - 2015.**
- | **On-Line Applications Research Corporation (OAR).**
- | **COPYRIGHT (c) 2016-2018.**
- | **RTEMS Foundati

Announce Mailing List?

[Sebastian Huber]

Hello,

the last post to the Announce Mailing List was 2013:

https://lists.rtems.org/pipermail/announce/

Should we really mention this mailing list in the user manual? Can it be 
deactivated?

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Status of RISCV port on sis

[Jiri Gaisler]

On 1/9/19 10:46 AM, Sebastian Huber wrote:
> Hello Jiri,
>
> could you please rebase your work to this RTEMS commit:
>
> https://git.rtems.org/rtems/commit/?id=b9ffc41c9678fb3c5386c1a6ab394656ec85dbc6
>
This works fine for me - I can now pass all uni-processor tests. On SMP, I 
still have a few fails but I think they are related to the simulator and the 
compressed RISC-V instruction set. I will investigate further ...

$ rtems-test --rtems-bsp=riscv-sis riscv-rtems5/c/grlib/testsuites

Passed:    574
Failed:  0
User Input:  5
Expected Fail:   0
Indeterminate:   0
Benchmark:   3
Timeout: 0
Invalid: 0
Wrong Version:   0
Wrong Build: 0
Wrong Tools: 0
--
Total: 582
User Input:
 monitor.exe
 termios.exe
 top.exe
 capture.exe
 fileio.exe
Benchmark:
 dhrystone.exe
 whetstone.exe
 linpack.exe
Average test time: 0:00:00.711573
Testing time : 0:06:54.135695



___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Status of RISCV port on sis

[Sebastian Huber]

- Am 11. Jan 2019 um 13:36 schrieb Jiri Gaisler j...@gaisler.se:

> On 1/9/19 10:46 AM, Sebastian Huber wrote:
>> Hello Jiri,
>>
>> could you please rebase your work to this RTEMS commit:
>>
>> https://git.rtems.org/rtems/commit/?id=b9ffc41c9678fb3c5386c1a6ab394656ec85dbc6
>>
> This works fine for me - I can now pass all uni-processor tests. On SMP, I 
> still
> have a few fails but I think they are related to the simulator and the
> compressed RISC-V instruction set. I will investigate further ...

If you use the latest tools, then the OpenMP tests don't link. I have to update 
the RSB to include this fix:

https://github.com/gcc-mirror/gcc/commit/a415601710979a5e6ca443c7e914b7e334055642

> 
> $ rtems-test --rtems-bsp=riscv-sis riscv-rtems5/c/grlib/testsuites
> 
> Passed:    574
> Failed:  0
> User Input:  5
> Expected Fail:   0
> Indeterminate:   0
> Benchmark:   3
> Timeout: 0
> Invalid: 0
> Wrong Version:   0
> Wrong Build: 0
> Wrong Tools: 0
> --
> Total: 582
> User Input:
> monitor.exe
> termios.exe
> top.exe
> capture.exe
> fileio.exe
> Benchmark:
> dhrystone.exe
> whetstone.exe
> linpack.exe
> Average test time: 0:00:00.711573
> Testing time : 0:06:54.135695

This is great. You mentioned some spintrcritical* failures in your last report. 
Was this a simulator issue?
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Status of RISCV port on sis

[Jiri Gaisler]

On 1/11/19 1:45 PM, Sebastian Huber wrote:
> - Am 11. Jan 2019 um 13:36 schrieb Jiri Gaisler j...@gaisler.se:
>
>> On 1/9/19 10:46 AM, Sebastian Huber wrote:
>>> Hello Jiri,
>>>
>>> could you please rebase your work to this RTEMS commit:
>>>
>>> https://git.rtems.org/rtems/commit/?id=b9ffc41c9678fb3c5386c1a6ab394656ec85dbc6
>>>
>> This works fine for me - I can now pass all uni-processor tests. On SMP, I 
>> still
>> have a few fails but I think they are related to the simulator and the
>> compressed RISC-V instruction set. I will investigate further ...
> If you use the latest tools, then the OpenMP tests don't link. I have to 
> update the RSB to include this fix:
>
> https://github.com/gcc-mirror/gcc/commit/a415601710979a5e6ca443c7e914b7e334055642

I have not been hit by this (yet), but I will keep it in mind.


>
>> $ rtems-test --rtems-bsp=riscv-sis riscv-rtems5/c/grlib/testsuites
>>
>> Passed:    574
>> Failed:  0
>> User Input:  5
>> Expected Fail:   0
>> Indeterminate:   0
>> Benchmark:   3
>> Timeout: 0
>> Invalid: 0
>> Wrong Version:   0
>> Wrong Build: 0
>> Wrong Tools: 0
>> --
>> Total: 582
>> User Input:
>>  monitor.exe
>>  termios.exe
>>  top.exe
>>  capture.exe
>>  fileio.exe
>> Benchmark:
>>  dhrystone.exe
>>  whetstone.exe
>>  linpack.exe
>> Average test time: 0:00:00.711573
>> Testing time : 0:06:54.135695
> This is great. You mentioned some spintrcritical* failures in your last 
> report. Was this a simulator issue?

Yes, the sim did not always disable external interrupts after a trap. Obviously 
not a good idea ... :-)


___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Bug reporting instructions

[Sebastian Huber]

Hello,

I would like to centralize the bug reporting instructions.  Currently we have:

https://devel.rtems.org/wiki/NewTicket

https://devel.rtems.org/wiki/Developer/Bug_Reporting

https://docs.rtems.org/branches/master/user/support/index.html#bug-tracker

I would like to move all information to the user manual and reference the HTML 
page of the user manual as the only source containing bug reporting 
instructions.

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

RSB: Why is "/usr" the default prefix?

[Sebastian Huber]

Hello,

why is "/usr" the default prefix? RTEMS does not belong to the host system. I 
think it should be "/opt"

http://refspecs.linuxbase.org/FHS_3.0/fhs/ch03s13.html#purpose14

or "/usr/local"

http://refspecs.linuxbase.org/FHS_3.0/fhs/ch04s09.html#purpose24

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: RSB: Why is "/usr" the default prefix?

[Sebastian Huber]

- Am 11. Jan 2019 um 15:38 schrieb Sebastian Huber 
sebastian.hu...@embedded-brains.de:

> Hello,
> 
> why is "/usr" the default prefix? RTEMS does not belong to the host system. I
> think it should be "/opt"
> 
> http://refspecs.linuxbase.org/FHS_3.0/fhs/ch03s13.html#purpose14
> 
> or "/usr/local"
> 
> http://refspecs.linuxbase.org/FHS_3.0/fhs/ch04s09.html#purpose24

Sorry, I mean why is it "/usr" on Linux.

Another question, the user manual says in the prefixes section:

"A further reason not to use the standard prefix is to allow more than one 
version of RTEMS to exist on your host machine at a time. The autoconf and 
automake tools required by RTEMS are not versioned and vary between the various 
versions of RTEMS. If you use a single prefix such as the standard prefix there 
is a chance parts from a package of different versions may interact. This 
should not happen but it can."

I think this is quite inconvenient from RSB to use such a prefix. Why can't it 
use OS standard prefix (e.g. "/opt" or "/usr/local") + rtems + version, e.g. 
"/opt/rtems/5" by default? You still have the root permission problem, but the 
we get rid of the conflicting versions stuff.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Rework parts of the user manual

[Sebastian Huber]

Hello,

this is the first patch set targeting the user manual. My goal is to write an 
easy to follow quick start chapter which references other chapters for the 
details.

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
From 40ec2e1636c40f77d79b6cecf6d28be091110170 Mon Sep 17 00:00:00 2001
From: Sebastian Huber 
Date: Fri, 11 Jan 2019 12:45:30 +0100
Subject: [PATCH 1/6] user: Move "Support" to "Introduction"

New users may find it useful to get this information in the
introduction.
---
 user/index.rst  |   2 -
 user/overview/index.rst | 130 ++--
 user/support/index.rst  | 121 
 3 files changed, 125 insertions(+), 128 deletions(-)
 delete mode 100644 user/support/index.rst

diff --git a/user/index.rst b/user/index.rst
index 7ec34bd..1eda925 100644
--- a/user/index.rst
+++ b/user/index.rst
@@ -42,8 +42,6 @@ RTEMS User Manual (|version|).
 tools/index
 rsb/index
 
-support/index
-
 glossary/index
 
 * :ref:`genindex`
diff --git a/user/overview/index.rst b/user/overview/index.rst
index 3a38bc5..a3718d2 100644
--- a/user/overview/index.rst
+++ b/user/overview/index.rst
@@ -1,10 +1,10 @@
 .. SPDX-License-Identifier: CC-BY-SA-4.0
 
 Introduction
-
+
 
 Overview
-
+
 
 You are someone looking for a real-time operating system.  This document
 
@@ -17,7 +17,7 @@ You are someone looking for a real-time operating system.  This document
 - helps you to build an example application on top of RTEMS.
 
 Features
-
+
 
 The Real-Time Executive for Multiprocessor Systems (:ref:term:`RTEMS`) is a
 multi-threaded, single address-space, real-time operating system with no
@@ -182,8 +182,128 @@ RTEMS provides the following basic feature set:
 
 - Support to stay in synchronization with FreeBSD
 
+Support
+===
+.. index:: Support
+
+RTEMS offers a variety of support options.
+
+This section covers all options available to both users and developers.  If you
+believe this is a bug report please submit it to the bug tracker otherwise the
+developers mailing list is the default location to send the report.
+
+RTEMS Project Support
+-
+.. index:: RTEMS Project Support
+
+The following support channels are provided by the RTEMS Project and provide
+direct access to the RTEMS community.
+
+Bug Tracker
+~~~
+.. index:: Bugs
+.. index:: Reporting bugs
+
+The bug tracker can be found at the :r:url:`bugs`.
+
+See the `Submission Guidelines `_ for
+details on submitting a ticket.
+
+Be sure to do a cursory search for any tickets that may be relevant to your
+problem.
+
+If you are unsure about your issue status submit a ticket and we will help you
+sort it out.
+
+Documentation
+~
+
+The latest user documentation can always be found at the :r:url:`docs`.
+
+.. _support-mailing-lists:
+
+Mailing Lists
+~
+.. index:: Community
+.. index:: Mailing lists
+
+We have several mailing lists for RTEMS users and developers.
+
+	* :r:list:`announce`
+		* Announcements for major and other project-related issues.
+
+	* :r:list:`bugs`
+		* Bugs email from :r:url:`bugs`.
+
+	* :r:list:`devel`
+		* Developers list, this is for developers of RTEMS itself.
+
+
+	* :r:list:`build`
+		* Results from the testing and building of RTEMS.
+
+	* :r:list:`users`
+		* Users of RTEMS.
+
+	* :r:list:`vc`
+		* Commits to the RTEMS master repository.
+
+
+IRC
+~~~
+.. index:: Community
+.. index:: IRC
+
+RTEMS IRC is available on the Freenode network. See the `Freenode
+`_ web site for details on connecting, selecting a
+nickname, and general usage tips. If you are new to IRC it is recommended
+reading.
+
+These are the current IRC channels.
+
+  **#rtems**
+
+This is a general channel for all things RTEMS. You can just hang out with
+other RTEMS users and developers to talk about RTEMS, using RTEMS or to make
+contact with other RTEMS users.
+
+The ``#rtems`` channel is logged. You can find the logs at
+http://www.rtems.org/irclogs/. You can search the logs using Google by adding:
+
+  **site:rtems.org inurl:irclogs**
+
+to your search terms.
+
+Developers
+~~
+.. index:: Community
+.. index:: Developers
+
+Developers can find help and support on the mailing lists, see
+:ref:`support-mailing-lists`.
+
+Technical documents including design, :r:url:`gsoc`, :r:url:`socis` can be
+found on the :r:url:`devel`.
+
+Commercial Support Services
+---
+
+The wider RTEMS community has developers and organizations who can provide
+commercial support services. These services range from training, implement

Re: RSB: Why is "/usr" the default prefix?

[Joel Sherrill]

On Fri, Jan 11, 2019, 8:45 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de wrote:

> - Am 11. Jan 2019 um 15:38 schrieb Sebastian Huber
> sebastian.hu...@embedded-brains.de:
>
> > Hello,
> >
> > why is "/usr" the default prefix? RTEMS does not belong to the host
> system. I
> > think it should be "/opt"
> >
> > http://refspecs.linuxbase.org/FHS_3.0/fhs/ch03s13.html#purpose14
> >
> > or "/usr/local"
> >
> > http://refspecs.linuxbase.org/FHS_3.0/fhs/ch04s09.html#purpose24
>
> Sorry, I mean why is it "/usr" on Linux.
>
> Another question, the user manual says in the prefixes section:
>
> "A further reason not to use the standard prefix is to allow more than one
> version of RTEMS to exist on your host machine at a time. The autoconf and
> automake tools required by RTEMS are not versioned and vary between the
> various versions of RTEMS. If you use a single prefix such as the standard
> prefix there is a chance parts from a package of different versions may
> interact. This should not happen but it can."
>
> I think this is quite inconvenient from RSB to use such a prefix. Why
> can't it use OS standard prefix (e.g. "/opt" or "/usr/local") + rtems +
> version, e.g. "/opt/rtems/5" by default? You still have the root permission
> problem, but the we get rid of the conflicting versions stuff.
>

That's essentially what I always do. /opt is a very old convention I
remember using on Solaris. Texlive installs there. Personally, I would
recommend /opt/rtems/version or something off a home directory that is
similar. Again, personally, I create a directory
$HOME/rtems-XXX/tools/version where XXX indicates a project or purpose. I
add nothing to my PATH until I commit to working in that RTEMS instance.
This let's me keep normal work separate from new class instances away from
customer project instances.

Forn5heb


___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Bug reporting instructions

[Joel Sherrill]

On Fri, Jan 11, 2019, 7:58 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de wrote:

> Hello,
>
> I would like to centralize the bug reporting instructions.  Currently we
> have:
>
> https://devel.rtems.org/wiki/NewTicket
>
> https://devel.rtems.org/wiki/Developer/Bug_Reporting
>
> https://docs.rtems.org/branches/master/user/support/index.html#bug-tracker
>
> I would like to move all information to the user manual and reference the
> HTML page of the user manual as the only source containing bug reporting
> instructions
>

My personal desire is to migrate all of this type of content from the wiki
to Sphinx, have one canonical version, and fix links to it.


> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax : +49 89 189 47 41-09
> E-Mail  : sebastian.hu...@embedded-brains.de
> PGP : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: RSB: Why is "/usr" the default prefix?

[Gedare Bloom]

On Fri, Jan 11, 2019 at 10:30 AM Joel Sherrill  wrote:

>
>
> On Fri, Jan 11, 2019, 8:45 AM Sebastian Huber <
> sebastian.hu...@embedded-brains.de wrote:
>
>> - Am 11. Jan 2019 um 15:38 schrieb Sebastian Huber
>> sebastian.hu...@embedded-brains.de:
>>
>> > Hello,
>> >
>> > why is "/usr" the default prefix? RTEMS does not belong to the host
>> system. I
>> > think it should be "/opt"
>> >
>> > http://refspecs.linuxbase.org/FHS_3.0/fhs/ch03s13.html#purpose14
>> >
>> > or "/usr/local"
>> >
>> > http://refspecs.linuxbase.org/FHS_3.0/fhs/ch04s09.html#purpose24
>>
>> Sorry, I mean why is it "/usr" on Linux.
>>
>> Another question, the user manual says in the prefixes section:
>>
>> "A further reason not to use the standard prefix is to allow more than
>> one version of RTEMS to exist on your host machine at a time. The autoconf
>> and automake tools required by RTEMS are not versioned and vary between the
>> various versions of RTEMS. If you use a single prefix such as the standard
>> prefix there is a chance parts from a package of different versions may
>> interact. This should not happen but it can."
>>
>> I think this is quite inconvenient from RSB to use such a prefix. Why
>> can't it use OS standard prefix (e.g. "/opt" or "/usr/local") + rtems +
>> version, e.g. "/opt/rtems/5" by default? You still have the root permission
>> problem, but the we get rid of the conflicting versions stuff.
>>
>
> That's essentially what I always do. /opt is a very old convention I
> remember using on Solaris. Texlive installs there. Personally, I would
> recommend /opt/rtems/version or something off a home directory that is
> similar. Again, personally, I create a directory
> $HOME/rtems-XXX/tools/version where XXX indicates a project or purpose. I
> add nothing to my PATH until I commit to working in that RTEMS instance.
> This let's me keep normal work separate from new class instances away from
> customer project instances.
>
> We may suggest in the prolog of this discussion that a user considers to
mkdir /opt/rtems and to chown/chgrp it in order to allow for installation
without the root permission. This means only root is needed in the initial
setup. We should also mention that a prefix within the users ${HOME} is a
good alternative.


> Forn5heb
>
Huh?


>
>
> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: RSB: Why is "/usr" the default prefix?

[Sebastian Huber]

- Am 11. Jan 2019 um 16:30 schrieb joel j...@rtems.org:

> On Fri, Jan 11, 2019, 8:45 AM Sebastian Huber <
> sebastian.hu...@embedded-brains.de wrote:
> 
>> - Am 11. Jan 2019 um 15:38 schrieb Sebastian Huber
>> sebastian.hu...@embedded-brains.de:
>>
>> > Hello,
>> >
>> > why is "/usr" the default prefix? RTEMS does not belong to the host
>> system. I
>> > think it should be "/opt"
>> >
>> > http://refspecs.linuxbase.org/FHS_3.0/fhs/ch03s13.html#purpose14
>> >
>> > or "/usr/local"
>> >
>> > http://refspecs.linuxbase.org/FHS_3.0/fhs/ch04s09.html#purpose24
>>
>> Sorry, I mean why is it "/usr" on Linux.
>>
>> Another question, the user manual says in the prefixes section:
>>
>> "A further reason not to use the standard prefix is to allow more than one
>> version of RTEMS to exist on your host machine at a time. The autoconf and
>> automake tools required by RTEMS are not versioned and vary between the
>> various versions of RTEMS. If you use a single prefix such as the standard
>> prefix there is a chance parts from a package of different versions may
>> interact. This should not happen but it can."
>>
>> I think this is quite inconvenient from RSB to use such a prefix. Why
>> can't it use OS standard prefix (e.g. "/opt" or "/usr/local") + rtems +
>> version, e.g. "/opt/rtems/5" by default? You still have the root permission
>> problem, but the we get rid of the conflicting versions stuff.
>>
> 
> That's essentially what I always do. /opt is a very old convention I
> remember using on Solaris. Texlive installs there. Personally, I would
> recommend /opt/rtems/version or something off a home directory that is
> similar. Again, personally, I create a directory
> $HOME/rtems-XXX/tools/version where XXX indicates a project or purpose. I
> add nothing to my PATH until I commit to working in that RTEMS instance.
> This let's me keep normal work separate from new class instances away from
> customer project instances.

Yes, I think the cited paragraph sounds more like an RSB bug report to me. We 
should change the default OS prefix on Linux to "/opt" and use OS prefix + 
"/rtems/${version}" as the default prefix.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: RSB: Why is "/usr" the default prefix?

[Chris Johns]

> On 12 Jan 2019, at 1:38 am, Sebastian Huber 
>  wrote:
> 
> why is "/usr" the default prefix?

It is the same as the default for rpmbuild and the SpecBuilder was a copy of 
that tool.

> RTEMS does not belong to the host system. I think it should be "/opt"

Fine with me, the RSB has evolved since the SpecBuilder days. The default 
should be version based somehow. 


Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel