redox-os issueshttps://gitlab.redox-os.org/groups/redox-os/-/issues2018-10-10T02:20:04Zhttps://gitlab.redox-os.org/redox-os/libc-artifacts/-/issues/4Header files provided by gcc2018-10-10T02:20:04ZIan Douglas ScottHeader files provided by gccThis is missing the header files provided by gcc, such as `stddef.h` and the headers for the C++ library. Those should be included here, right?This is missing the header files provided by gcc, such as `stddef.h` and the headers for the C++ library. Those should be included here, right?https://gitlab.redox-os.org/redox-os/book/-/issues/122Navigation through book results in infinite loop2018-09-07T01:22:53ZJeremy SollerNavigation through book results in infinite loop*Created by: staktrace*
Go to https://doc.redox-os.org/book/getting_started/preparing_the_build.html
Go to the bottom and click on the next arrow, this will take you to https://doc.redox-os.org/book/getting_started/installing_the_toolc...*Created by: staktrace*
Go to https://doc.redox-os.org/book/getting_started/preparing_the_build.html
Go to the bottom and click on the next arrow, this will take you to https://doc.redox-os.org/book/getting_started/installing_the_toolchain.html
Go to the bottom of this page and click on the next arrow. It takes you back to the previous page instead of onwards to compiling. So always going to the "next" page gets you stuck in an infinite loop :(https://gitlab.redox-os.org/redox-os/book/-/issues/128How to Build book2020-02-17T02:34:27ZJeremy SollerHow to Build book*Created by: stratosmacker*
Running mdbook is not the only step to building the HTML, what build steps do you run? I'd like to build this for offline use, but running `mdbook build` in src/ only builds a blank page*Created by: stratosmacker*
Running mdbook is not the only step to building the HTML, what build steps do you run? I'd like to build this for offline use, but running `mdbook build` in src/ only builds a blank pagehttps://gitlab.redox-os.org/redox-os/book/-/issues/118Documentation: Translation into Spanish language2023-06-13T04:57:50ZJeremy SollerDocumentation: Translation into Spanish language*Created by: michaelizer*
Greetings, I would like to contribute to the project by translating it into Spanish. Spanish is my native language so don't panic, but a lot of Spanish speakers are still limited by the language so this is prim...*Created by: michaelizer*
Greetings, I would like to contribute to the project by translating it into Spanish. Spanish is my native language so don't panic, but a lot of Spanish speakers are still limited by the language so this is primarily to help them.
Thanks in advance and for your time. Keep up the great work.https://gitlab.redox-os.org/redox-os/book/-/issues/104Redox vs Linux2020-02-17T02:31:56ZJeremy SollerRedox vs Linux*Created by: thomaskuntzz*
>
> Will Redox replace Linux?
> =========================
>
> No.
https://github.com/redox-os/book/blob/master/src/introduction/will_redox_replace_linux.md
Really? Bro?
Explaaaaaaaaaaaaaaaaaaaain!...*Created by: thomaskuntzz*
>
> Will Redox replace Linux?
> =========================
>
> No.
https://github.com/redox-os/book/blob/master/src/introduction/will_redox_replace_linux.md
Really? Bro?
Explaaaaaaaaaaaaaaaaaaaain!!! We want to know **why** the guys that created it think this! It doesn't have the same goal? Purpose? The same use cases? Too young? Linux community is too big? I don't know, but atcual reasons...
Elaborate, we'd like to know what you think 😉 https://gitlab.redox-os.org/redox-os/book/-/issues/115Remove ZFS Section2018-09-07T01:22:53ZNick PaladinoRemove ZFS SectionSince RedoxFS, and eventually TFS, is the main file system, seems like a good idea. Or just rename it to TFS so the book can start to document it.Since RedoxFS, and eventually TFS, is the main file system, seems like a good idea. Or just rename it to TFS so the book can start to document it.https://gitlab.redox-os.org/redox-os/book/-/issues/116"This books ..." should be "This book ..."2018-09-07T01:22:53ZJeremy Soller"This books ..." should be "This book ..."*Created by: victorz*
Also *operating system* is written without a dash.
https://github.com/redox-os/book/blob/55cde920ea5af88dc71c400329600f7156bfac72/book.json#L3*Created by: victorz*
Also *operating system* is written without a dash.
https://github.com/redox-os/book/blob/55cde920ea5af88dc71c400329600f7156bfac72/book.json#L3https://gitlab.redox-os.org/redox-os/book/-/issues/70Error on "Preparing the build"2018-09-07T01:22:53ZJeremy SollerError on "Preparing the build"*Created by: CleanCut*
On the [Preparing the build page](https://doc.redox-os.org/book/getting_started/preparing_the_build.html) there is this line:
brew install make nasm qemu gcc49 pkg-config Caskroom/cask/osxfuse
But there ...*Created by: CleanCut*
On the [Preparing the build page](https://doc.redox-os.org/book/getting_started/preparing_the_build.html) there is this line:
brew install make nasm qemu gcc49 pkg-config Caskroom/cask/osxfuse
But there is no `make` package for brew to install:
Error: No available formula with the name "make"
Perhaps you meant one of these pacakages? (maybe `cmake`?)
```
$ brew search make
automake ✔ cmake libpagemaker makeicns makepp remake xmake
bmake colormake makedepend makensis makeself smake
bsdmake gnustep-make makefile2graph makepkg premake snakemake
homebrew/dupes/make Caskroom/cask/dataurlmaker Caskroom/cask/makemkv
homebrew/science/biomake Caskroom/cask/diskcatalogmaker Caskroom/cask/makerbot-desktop
homebrew/science/maker Caskroom/cask/diskmaker-x Caskroom/cask/popmaker
homebrew/versions/automake112 Caskroom/cask/filemaker-odbc Caskroom/cask/texmaker
homebrew/x11/imake Caskroom/cask/makehuman Caskroom/cask/th-makerx
Caskroom/cask/cmake Caskroom/cask/makeiphoneringtone Caskroom/cask/treemaker
```https://gitlab.redox-os.org/redox-os/book/-/issues/101book should explain programs and their libraries (newlib, libstd, libredox, ...)2018-09-07T01:22:53ZJeremy Sollerbook should explain programs and their libraries (newlib, libstd, libredox, ...)*Created by: skierpage*
Hi, congratulations on this amazing project.
I'm confused how programs work at all in Redox. It offers a number of big C programs and I think uses a port of newlib to make these work. But Rust programs use lib...*Created by: skierpage*
Hi, congratulations on this amazing project.
I'm confused how programs work at all in Redox. It offers a number of big C programs and I think uses a port of newlib to make these work. But Rust programs use libstd. I read in Rust-land about the difficulties of running libstd on non-standard architectures but I don't know where Redox wound up.
The only references to all this in the Redox-OS book are two mentions of newlib in passing, and https://doc.redox-os.org/book/contributing/best_practices/rusting_properly.html says "libredox should be 1-to-1 with the official libstd"
I think the best place to address this is in a section after 5.2 The kernel and before 5.4. Coreutils, called **5.x Programs and Libraries**. I'd make a pull request for this but I was unable to get Redox working, neither from the book, nor building new libc, nor from docker :-( , so here's a guess at what the chapter should say.
5.x Programs and Libraries
====================
Redox can run programs. Some programs are interpreted by a runtime for the program's language, such as a script running in the Ion shell or a Python program. Others are compiled into machine instructions that run on a particular operating system (Redox) and specific hardware (e.g. x86 compatible CPU in 64-bit mode).
* In Redox compiled binaries use the standard [ELF](https://en.wikipedia.org/wiki/Executable_and_Linkable_Format) ("Executable and Linkable Format") format.
Programs could directly invoke Redox syscalls, but most call library functions that are higher-level and more comfortable to use. You link your program with the libraries it needs.
* Redox does not support dynamic-link libraries yet *(issue #927)*, so the libraries that a program uses are statically linked into its compiled binary.
* Most C and C++ programs call functions in a [C standard library](https://en.wikipedia.org/wiki/C_standard_library) ("libc") such as `fopen`
* Redox includes a port of the newlib Standard C library. This is how programs such as git can run on Redox. newlib has some POSIX compatibility.
* Rust programs implicitly or explicitly call functions in the Rust standard library (libstd).
* ?? ~~Redox implements a subset of this in libredox~~
* The Rust libstd now includes an implementation of its system-dependent parts (such as file access and setting environment variables) for Redox, in `src/libstd/sys/redox`. ?? Most of libstd works in Redox, so many command-line Rust programs can be compiled for Redox.
The Redox "cookbook'' project includes recipes for compiling C and Rust projects into Redox binaries.https://gitlab.redox-os.org/redox-os/book/-/issues/100Pin version of mdBook2023-06-13T04:57:01ZJeremy SollerPin version of mdBook*Created by: azerupi*
Hi!
I am not totally sure this applies to this repository, because I don't know if you release automatically?
We would like to issue a new release of mdBook containing some changes that could potentially break cu...*Created by: azerupi*
Hi!
I am not totally sure this applies to this repository, because I don't know if you release automatically?
We would like to issue a new release of mdBook containing some changes that could potentially break current books, the config file changed a bit for example. However we found out that a lot of projects automatically deploy using the latest available version and so any breaking update could result in books not being deployed anymore..
We would like to avoid that and recommend pinning the version of mdBook in your deployment script. Cargo supports semver ranges on `cargo install` (right now it issues a deprecation warning, but in the future this warning should go away thanks to rust-lang/cargo#4229)
You can thus simply change `cargo install mdbook` to
```
cargo install mdbook --vers "^0.0.22"
```
Next release will be `0.1.0` and we will try to adhere to semver as much as possible.
For more info, azerupi/mdBook#327 is the tracking issue on our repository.https://gitlab.redox-os.org/redox-os/book/-/issues/412.3.1. Heartbleed: A case study2018-09-07T01:22:53ZJeremy Soller2.3.1. Heartbleed: A case study*Created by: getreu*
I just wrote an [article](http://getreu.net/public/downloads/doc/Enhance%20Embedded%20System%20Security%20With%20Rust/Enhance%20Embedded%20System%20Security%20With%20Rust--Example%20of%20Heartbleed.html) about Rust ...*Created by: getreu*
I just wrote an [article](http://getreu.net/public/downloads/doc/Enhance%20Embedded%20System%20Security%20With%20Rust/Enhance%20Embedded%20System%20Security%20With%20Rust--Example%20of%20Heartbleed.html) about Rust and Heartbleed. Please free to take from the text if you like it.
https://gitlab.redox-os.org/redox-os/book/-/issues/60C style strings used instead of pascal style strings in book2022-09-23T22:19:41ZJeremy SollerC style strings used instead of pascal style strings in book*Created by: bjorn3*
At `https://doc.redox-os.org/book/design/url/how_it_works.html#Opening a URL` it is said that the `open` syscall takes a C style string, but it takes a pascal style string.*Created by: bjorn3*
At `https://doc.redox-os.org/book/design/url/how_it_works.html#Opening a URL` it is said that the `open` syscall takes a C style string, but it takes a pascal style string.https://gitlab.redox-os.org/redox-os/book/-/issues/93Link to package manager repo broken2018-09-07T01:22:53ZJeremy SollerLink to package manager repo broken*Created by: jplatte*
In sections 1.2.1 and 7.2.1 there are links to "Magnet", the package manager. They are both broken.*Created by: jplatte*
In sections 1.2.1 and 7.2.1 there are links to "Magnet", the package manager. They are both broken.https://gitlab.redox-os.org/redox-os/book/-/issues/57Can one use the orbital modules for GUIs outside of redox?2019-09-29T02:11:32ZJeremy SollerCan one use the orbital modules for GUIs outside of redox?*Created by: strpipe*
is it possible to use orbital also for Rendering app on different platforms?
Meaning can one use this as a Rust Gui framework?*Created by: strpipe*
is it possible to use orbital also for Rendering app on different platforms?
Meaning can one use this as a Rust Gui framework?https://gitlab.redox-os.org/redox-os/book/-/issues/84Does glendc/gcc_cross_compilers still work for anyone?2018-09-07T01:22:53ZJeremy SollerDoes glendc/gcc_cross_compilers still work for anyone?*Created by: qntnrbns*
I am trying to do the initial build, and the "Preparing the build" instructions recommend using glendc/gcc_cross_compilers. It doesnt work for me, and the bootstrap.sh script in the redox repo uses redox-os/gcc_cr...*Created by: qntnrbns*
I am trying to do the initial build, and the "Preparing the build" instructions recommend using glendc/gcc_cross_compilers. It doesnt work for me, and the bootstrap.sh script in the redox repo uses redox-os/gcc_cross_compilers. Does this need to be updated?https://gitlab.redox-os.org/redox-os/book/-/issues/78Error style2018-09-07T01:22:53ZJeremy SollerError style*Created by: Mojo4242*
Hi,
I often see some programs aborting with `expect()` or with an `unwrap()`.
This makes message quite not user-friendly.
For examples:
```
# sudo
thread 'main' panicked at 'sudo: no command provided', r...*Created by: Mojo4242*
Hi,
I often see some programs aborting with `expect()` or with an `unwrap()`.
This makes message quite not user-friendly.
For examples:
```
# sudo
thread 'main' panicked at 'sudo: no command provided', rust/src/libcore/option.rs:785
Invalid opcode fault at 23:0000000000413B74
TRACE: FFFFFF400010E318
FFFFFF400010E318: FFFFFF00001224FD
FFFFFF400010E3C8: FFFFFF0000122401
00000180000FF6F0: 0000000000413B69
00000180000FF700: 00000000004065FD
00000180000FF770: 00000000004065EF
00000180000FF7F0: 00000000004067C3
00000180000FF820: 00000000004064F6
00000180000FF890: 0000000000406488
00000180000FF8F0: 0000000000416E0E
00000180000FF960: 0000000000416C18
00000180000FF9D0: 0000000000401AF7
00000180000FFDC0: 0000000000413B5C
00000180000FFDD0: 0000000000406726
00000180000FFE00: 000000000040E0EE
00000180000FFE20: 0000000000406AF4
00000180000FFE80: 000000000041A13C
0000008000000018: EMPTY RETURN
SIGNAL 4, CPU 0, PID ContextId(41)
NAME file:/bin/sudo
Child ended by signal
```
The essential message here is `sudo: no command provided`
This lead to the question of style in error management:
1. Should we nearly banish `expect()` and `unwrap()`, manage error, print an error message to stderr and exit if appropriate ?
2. Should we abort with these function and adapt them to print a nicer output ?
I would go for 1. as it's makes safer code and when it backtrace, you know that's _BAD_. I would add a new line about this in `rusting_properly`
What do you think about that ?https://gitlab.redox-os.org/redox-os/book/-/issues/47Build does not list fuse as dependency2018-09-07T01:22:53ZJeremy SollerBuild does not list fuse as dependency*Created by: shaleh*
make failed for me because I did not have libfuse-dev install on my Ubuntu system.
*Created by: shaleh*
make failed for me because I did not have libfuse-dev install on my Ubuntu system.
https://gitlab.redox-os.org/redox-os/book/-/issues/46Dead Why MIT link2018-09-07T01:22:53ZJeremy SollerDead Why MIT link*Created by: aidylewis*
On the [Why Redox page](https://doc.redox-os.org/book/introduction/why_redox.html), the link to Why MIT is broken (https://doc.redox-os.org/book/why_mit.html). It should be this (https://doc.redox-os.org/book/int...*Created by: aidylewis*
On the [Why Redox page](https://doc.redox-os.org/book/introduction/why_redox.html), the link to Why MIT is broken (https://doc.redox-os.org/book/why_mit.html). It should be this (https://doc.redox-os.org/book/introduction/why_mit.html).
https://gitlab.redox-os.org/redox-os/book/-/issues/67Provide (markdown) syntax highlighting for Ion scripts2019-09-29T01:28:21ZJeremy SollerProvide (markdown) syntax highlighting for Ion scripts*Created by: GlenDC*
Currently there is no support for [Ion][ion] scripts in the code syntax highlighting capabilities of the markdown-based generator used for this book. Additionally the markdown files as part of the redox-os/ion also ...*Created by: GlenDC*
Currently there is no support for [Ion][ion] scripts in the code syntax highlighting capabilities of the markdown-based generator used for this book. Additionally the markdown files as part of the redox-os/ion also do not have syntax-highlighting support currently for [Ion][ion] scripts.
A great starting point to solve this issue would be to add syntax information for Ion to [azerup/mdBook][mdbook] (as a contribution), or whatever library it uses to support syntax highlighting for code snippets. [azerup/mdBook][mdbook] is the technology we use to generate this book.
[mdbook]: https://github.com/azerupi/mdBook
[ion]: https://github.com/redox-os/ionhttps://gitlab.redox-os.org/redox-os/book/-/issues/25Why NASM2019-10-03T01:03:29ZJeremy SollerWhy NASM*Created by: vinipsmaker*
This isn't explained.
*Created by: vinipsmaker*
This isn't explained.