redox-os issueshttps://gitlab.redox-os.org/groups/redox-os/-/issues2018-06-12T14:22:02Zhttps://gitlab.redox-os.org/redox-os/ion/-/issues/507Enhance String Join Method Argument Parsing2018-06-12T14:22:02ZMichael Aaron Murphymmstick@pm.meEnhance String Join Method Argument ParsingWe may want to do a much more comprehensive look into our existing argument parsing logic for our methods -- both method parsing in general, and better handling of arguments for methods like join. Method arguments currently aren't evalua...We may want to do a much more comprehensive look into our existing argument parsing logic for our methods -- both method parsing in general, and better handling of arguments for methods like join. Method arguments currently aren't evaluated at all. This is causing some problems with certain use cases of methods.
In example, one use case that we might want to support is using the join method for creating a new, newline-delimited string. But that's difficult to do at the moment, because method arguments aren't evaluated at all. Usage like the following: `$join(@args[1..], "\n")` will literally just return each argument with "\n" between each element in the array.https://gitlab.redox-os.org/redox-os/ion/-/issues/506dmenu doesn't work as expected2018-07-01T17:59:19ZMichael Aaron Murphymmstick@pm.medmenu doesn't work as expected*Created by: bb010g*
**Reproduction**:
Run the following script with no arguments and press enter when prompted:
```
#!/usr/bin/env ion
echo $join(@args[1..], "|")
let foo = $(dmenu @args[1..])
let foo = $(echo hi | dmenu @arg...*Created by: bb010g*
**Reproduction**:
Run the following script with no arguments and press enter when prompted:
```
#!/usr/bin/env ion
echo $join(@args[1..], "|")
let foo = $(dmenu @args[1..])
let foo = $(echo hi | dmenu @args[1..])
echo got foo
ion -c "echo "$foo | /usr/bin/cat
ion -c "echo "$foo | dmenu @args[1..]
echo $foo | dmenu @args[1..]
```
**Expected behavior**:
I'd expect it to work equivalently to this dash script:
```
#!/usr/bin/env dash
(IFS="|"; echo "$*")
foo="`dmenu "$@"`"
foo="`echo hi | dmenu "$@"`"
echo got foo
dash -c "echo "$foo | /usr/bin/cat
dash -c "echo "$foo | dmenu "$@"
echo $foo | dmenu "$@"
```
The output will first be a blank line followed by execution stopping as dmenu waits for input. Enter a line and press `^D` to make it prompt you and keep going. `foo` will get `hi` assigned to it. `got foo` will be printed, followed by `hi` three times.
**Actual behavior**:
Ion will cause dmenu to show up with no choices. Type `bar`, press enter, and Ion presents a proper dmenu with `hi` as the choice. `got foo` and `hi` will be printed, followed by:
```
usage: dmenu [-bfiv] [-l lines] [-p prompt] [-fn font] [-m monitor]
[-nb color] [-nf color] [-sb color] [-sf color] [-w windowid]
usage: dmenu [-bfiv] [-l lines] [-p prompt] [-fn font] [-m monitor]
[-nb color] [-nf color] [-sb color] [-sf color] [-w windowid]
```
The script exits with 1.
**Build information**: [output of `rustc -V`, `git rev-parse HEAD`, `qemu-i386 -version`, `uname -a`, etc.]
```
rustc 1.19.0 (0ade33941 2017-07-17)
HEAD: 3319ffb00e3ff54db1446302a7debd7e7f7ff893
Linux bb010g-lat 4.12.8-1-ARCH #1 SMP PREEMPT Thu Aug 17 08:37:20 CEST 2017 x86_64 GNU/Linux
dmenu -v: dmenu-4.7
```
**Blocking/related**: Maybe #424? I'm not sure here.Ion Shell v1.0.0https://gitlab.redox-os.org/redox-os/cookbook/-/issues/75Some mechanism for detecting update of TAR2023-06-12T23:51:18ZIan Douglas ScottSome mechanism for detecting update of TARIf `TAR=` is used to specify a source tarball, there is currently no way for `fetch` to detect when the version has been bumped, and download the new release.If `TAR=` is used to specify a source tarball, there is currently no way for `fetch` to detect when the version has been bumped, and download the new release.https://gitlab.redox-os.org/redox-os/ion/-/issues/503Add environment variable to define commands that should NOT be saved in the h...2018-06-12T14:22:02ZMichael Aaron Murphymmstick@pm.meAdd environment variable to define commands that should NOT be saved in the history*Created by: BafDyce*
For example, bash (and probably other shells too) ignores commands starting with a space when `HISTCONTROL` is set to `ignorespace` or `ignoreboth` (see www.delorie.com/gnu/docs/bash/bashref_62.html). This would be...*Created by: BafDyce*
For example, bash (and probably other shells too) ignores commands starting with a space when `HISTCONTROL` is set to `ignorespace` or `ignoreboth` (see www.delorie.com/gnu/docs/bash/bashref_62.html). This would be a useful feature and is part of my current daily workflow.
For ion, we could add a variable such as `HISTORY_IGNORE` which contains rules to influence which commands are saved to the history.
**Blocking/related**: #502
**Misc**:
I'd be happy to implement this feature, however I'd like to have it discussed it first:
* Do you/the community think this is a useful addition?
* Is `HISTORY_IGNORE` a good name?
* Should the "ignore-character" always be a space? Any whitespace? Any user-defined character?
* What's a sane way to combine this with the issue mentioned in #502?
**Note**:
I've created two separate issues, feel free to merge them if you think that would be better.
------
_If the above does not fit the nature of the issue feel free to modify it._
https://gitlab.redox-os.org/redox-os/ion/-/issues/502Only commands with exit status != `NO_SUCH_COMMAND` are saved in history?2018-06-12T14:22:02ZMichael Aaron Murphymmstick@pm.meOnly commands with exit status != `NO_SUCH_COMMAND` are saved in history?*Created by: BafDyce*
**Reproduction**: enter a command which is not found, e.g. `gerp -rn "some_complex_regex" .`; note the typo in `grep`
**Expected behavior**: Even though the command was not found, it's invocation attempt should...*Created by: BafDyce*
**Reproduction**: enter a command which is not found, e.g. `gerp -rn "some_complex_regex" .`; note the typo in `grep`
**Expected behavior**: Even though the command was not found, it's invocation attempt should be stored in the history, so that one can press `arrow up`, fix the mistake, and rerun the command.
```
# echo hi
hi
# gerp -rn "some_complex_regex" .
ion: command not found: gerp
# history | tail -1
gerp -rn "some_complex_regex" .
```
**Actual behavior**:
```
# echo hi
hi
# gerp -rn "some_complex_regex" .
ion: command not found: gerp
# history | tail -1
echo hi
```
**Build information**:
```
# rustc -V
rustc 1.19.0 (0ade33941 2017-07-17)
# git rev-parse HEAD
5bbc65d55f1eb75e89eb5141d51b57d0eecd91c8
# uname -a
Linux <hostname> 4.12.6-1-ARCH #1 SMP PREEMPT Sat Aug 12 09:16:22 CEST 2017 x86_64 GNU/Linux
```
**Misc**:
I understand that the current behavior might be desired for some people and it probably is a sane default. However, if the command was rather complex/long its a pain to a) retype or b) copy & paste it with the mouse.
Maybe, it would be possible to add an environment variable to modify this behavior? What would be a good name for that variable? `HISTORY_IGNORE` maybe?
------
_If the above does not fit the nature of the issue feel free to modify it._
https://gitlab.redox-os.org/redox-os/cookbook/-/issues/70Compiling ncurses fails.2018-06-16T13:33:58ZJeremy SollerCompiling ncurses fails.*Created by: Nickforall*
So whenever I do `./cook.sh ncurses build` it fails because it can't find `termios.h`, instead it tries to include `<sgtty.h>`.
I tried fixing it myself, but couldn't figure it out due to my lack of experienc...*Created by: Nickforall*
So whenever I do `./cook.sh ncurses build` it fails because it can't find `termios.h`, instead it tries to include `<sgtty.h>`.
I tried fixing it myself, but couldn't figure it out due to my lack of experience with autoconf, here's what I found however:
* Checking whether `termios.h`/`termio.h` exists is done somewhere in ./configure
* It created a variable called `_HAVE_TERMIOS_H` that is set to 0
* The code that is generated doesn't include termios.h, because autoconf thinks it's non-existent, instead.https://gitlab.redox-os.org/redox-os/ion/-/issues/498Multi-Line structures and in-line comments.2018-06-12T14:22:02ZMichael Aaron Murphymmstick@pm.meMulti-Line structures and in-line comments.*Created by: jwarner112*
Hello,
I'm playing with Ion shell right now and it's so far proven to be very powerful. I'm looking forward to the way this project develops, as well as maybe being a contributor some time soon.
One proble...*Created by: jwarner112*
Hello,
I'm playing with Ion shell right now and it's so far proven to be very powerful. I'm looking forward to the way this project develops, as well as maybe being a contributor some time soon.
One problem I'm encountering where Bash has proven superior is in multi-line arrays. In Bash:
```
paths=(
"/opt/bin" `# A comment`
"/bin" `# Another comment`
"/usr/bin" `# Yet another comment`
"/usr/local/bin" `# Some kind of comment I guess?`
)
```
This is a sequence that allows me to neatly edit my `$PATH` with all the above paths, and the backtick trick allows me to have inline comments explaining what each one is. The example is trivial but in production I make good use of this. I'd rather not _need_ the backtick hack, but that's the only way to get the desired behavior.
In Ion, there appears to be no equivalent-- I can't get inline comments and can't get a `#` to simultaneously respect the final `\` without the shell crashing on me.
I'm looking to discuss possible solutions, ranging from a simple inline-comment syntax to even a special syntax for collections that span multiple lines. For example, I like the way this looks:
```
let paths = [
/opt/bin, # The quotes here are optional
/bin, # I left them out of this example because what the hey
/usr/bin, # the ',' character tells Ion explicitly not to IGNORE the newline,
/usr/local/bin, # but omit it when storing the array, so that the comment can properly be dropped
# mixed feelings on this end comment
# And also on this last-element-trailing-comma, but I normally work in Python
];
```
Still, it might be easier to implement this:
```
let paths = [ \
/opt/bin /*Inline comment that ends here ->*/ \
/bin /*Another comment*/ \
/usr/local/bin /*You get the idea*/ \
];
```
Thoughts?
**Build information**:
```
jwarner:~$ rustup -V
rustup 1.5.0 (92d0d1e9e 2017-06-24)
jwarner:~$ rustc -V
rustc 1.19.0 (0ade33941 2017-07-17)
jwarner:~$ cargo -V
cargo 0.20.0 (a60d185c8 2017-07-13)
jwarner:~$ uname -a
Linux jwarner 4.4.0-81-generic #104~14.04.1-Ubuntu SMP Wed Jun 14 12:45:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
jwarner:~$ # ion-shell = 1.0.5 (but can't find where to get that via CLI)
```https://gitlab.redox-os.org/redox-os/newlib/-/issues/58Implement more termios functions2023-09-24T10:03:05ZJeremy SollerImplement more termios functionsImplement stubs left from https://github.com/redox-os/newlib/pull/57Implement stubs left from https://github.com/redox-os/newlib/pull/57https://gitlab.redox-os.org/redox-os/tfs/-/issues/65Hybrid EBR and HBR approach2018-06-13T19:39:49ZJeremy SollerHybrid EBR and HBR approach*Created by: ticki*
cc @stjepang*Created by: ticki*
cc @stjepanghttps://gitlab.redox-os.org/redox-os/redox/-/issues/1025Build failed: Could not compile `std`. (E0597)2018-06-15T11:40:00ZJeremy SollerBuild failed: Could not compile `std`. (E0597)*Created by: Nickforall*
I'm not sure if this is an issue with the current build of rust, or redox.
**Reproduction**: `make all` on the latest nightly build
**Expected behavior**: Redox successfully compiling
**Actual behavior**: ...*Created by: Nickforall*
I'm not sure if this is an issue with the current build of rust, or redox.
**Reproduction**: `make all` on the latest nightly build
**Expected behavior**: Redox successfully compiling
**Actual behavior**:
```
cd kernel && xargo clean
rm -rf build/initfs
cargo run --manifest-path installer/Cargo.toml -- --cookbook=cookbook initfs.toml
Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
Running `installer/target/debug/redox_installer --cookbook=cookbook initfs.toml`
Install Config {
general: GeneralConfig {
prompt: false,
sysroot: Some(
"build/initfs"
)
},
packages: {
"drivers": PackageConfig {
version: None,
git: None,
path: None
},
"init": PackageConfig {
version: None,
git: None,
path: None
},
"redoxfs": PackageConfig {
version: None,
git: None,
path: None
}
},
files: [
FileConfig {
path: "/etc/init.rc",
data: "export PATH /bin\nexport TMPDIR /tmp\nvesad T T G\nstdio display:1\nps2d\npcid /etc/pcid/initfs.toml\nredoxfs disk:0 file\ncd file:\nrun.d /etc/init.d\n"
}
],
users: {}
}
Create directory /home/nick/programming/redox/build/initfs/
repo - building drivers
cook - drivers build
Updating registry `https://github.com/rust-lang/crates.io-index`
Compiling libc v0.0.0 (file:///home/nick/programming/redox/rust/src/rustc/libc_shim)
Compiling gcc v0.3.51
Compiling libc v0.2.29
Compiling unwind v0.0.0 (file:///home/nick/programming/redox/rust/src/libunwind)
Compiling core v0.0.0 (file:///home/nick/programming/redox/rust/src/libcore)
Compiling filetime v0.1.10
Compiling build_helper v0.1.0 (file:///home/nick/programming/redox/rust/src/build_helper)
Compiling compiler_builtins v0.0.0 (file:///home/nick/programming/redox/rust/src/rustc/compiler_builtins_shim)
Compiling std v0.0.0 (file:///home/nick/programming/redox/rust/src/libstd)
Compiling rand v0.0.0 (file:///home/nick/programming/redox/rust/src/librand)
Compiling std_unicode v0.0.0 (file:///home/nick/programming/redox/rust/src/libstd_unicode)
Compiling panic_abort v0.0.0 (file:///home/nick/programming/redox/rust/src/libpanic_abort)
Compiling alloc v0.0.0 (file:///home/nick/programming/redox/rust/src/liballoc)
Compiling collections v0.0.0 (file:///home/nick/programming/redox/rust/src/libcollections)
Compiling alloc_system v0.0.0 (file:///home/nick/programming/redox/rust/src/liballoc_system)
Compiling panic_unwind v0.0.0 (file:///home/nick/programming/redox/rust/src/libpanic_unwind)
warning: dropping unsupported crate type `dylib` for target `x86_64-unknown-redox`
error[E0597]: borrowed value does not live long enough
--> /home/nick/programming/redox/rust/src/libstd/thread/local.rs:178:17
|
178 | __KEY.get()
| ^^^^^ does not live long enough
179 | }
| - temporary value only lives until here
|
::: /home/nick/programming/redox/rust/src/libstd/collections/hash/map.rs
|
2356 | / thread_local!(static KEYS: Cell<(u64, u64)> = {
2357 | | let r = rand::OsRng::new();
2358 | | let mut r = r.expect("failed to create an OS RNG");
2359 | | Cell::new((r.gen(), r.gen()))
2360 | | });
| |___________- in this macro invocation
|
= note: borrowed value must be valid for the static lifetime...
error[E0597]: borrowed value does not live long enough
--> /home/nick/programming/redox/rust/src/libstd/thread/local.rs:178:17
|
178 | __KEY.get()
| ^^^^^ does not live long enough
179 | }
| - temporary value only lives until here
|
::: /home/nick/programming/redox/rust/src/libstd/io/stdio.rs
|
23 | / thread_local! {
24 | | static LOCAL_STDOUT: RefCell<Option<Box<Write + Send>>> = {
25 | | RefCell::new(None)
26 | | }
27 | | }
| |_- in this macro invocation
|
= note: borrowed value must be valid for the static lifetime...
error[E0597]: borrowed value does not live long enough
--> /home/nick/programming/redox/rust/src/libstd/thread/local.rs:178:17
|
178 | __KEY.get()
| ^^^^^ does not live long enough
179 | }
| - temporary value only lives until here
|
::: /home/nick/programming/redox/rust/src/libstd/sys_common/thread_info.rs
|
21 | thread_local! { static THREAD_INFO: RefCell<Option<ThreadInfo>> = RefCell::new(None) }
| -------------------------------------------------------------------------------------- in this macro invocation
|
= note: borrowed value must be valid for the static lifetime...
error[E0597]: borrowed value does not live long enough
--> /home/nick/programming/redox/rust/src/libstd/thread/local.rs:178:17
|
178 | __KEY.get()
| ^^^^^ does not live long enough
179 | }
| - temporary value only lives until here
|
::: /home/nick/programming/redox/rust/src/libstd/panicking.rs
|
35 | / thread_local! {
36 | | pub static LOCAL_STDERR: RefCell<Option<Box<Write + Send>>> = {
37 | | RefCell::new(None)
38 | | }
39 | | }
| |_- in this macro invocation
|
= note: borrowed value must be valid for the static lifetime...
error[E0597]: borrowed value does not live long enough
--> /home/nick/programming/redox/rust/src/libstd/thread/local.rs:178:17
|
178 | __KEY.get()
| ^^^^^ does not live long enough
179 | }
| - temporary value only lives until here
|
::: /home/nick/programming/redox/rust/src/libstd/panicking.rs
|
407 | thread_local! { static PANIC_COUNT: Cell<usize> = Cell::new(0) }
| ---------------------------------------------------------------- in this macro invocation
|
= note: borrowed value must be valid for the static lifetime...
error[E0597]: borrowed value does not live long enough
--> /home/nick/programming/redox/rust/src/libstd/thread/local.rs:178:17
|
178 | __KEY.get()
| ^^^^^ does not live long enough
179 | }
| - temporary value only lives until here
|
::: /home/nick/programming/redox/rust/src/libstd/rand/mod.rs
|
166 | / thread_local!(static THREAD_RNG_KEY: Rc<RefCell<ThreadRngInner>> = {
167 | | let r = match StdRng::new() {
168 | | Ok(r) => r,
169 | | Err(e) => panic!("could not initialize thread_rng: {}", e)
... |
174 | | Rc::new(RefCell::new(rng))
175 | | });
| |_______- in this macro invocation
|
= note: borrowed value must be valid for the static lifetime...
error: aborting due to 6 previous errors
error: Could not compile `std`.
To learn more, run the command again with --verbose.
error: `"cargo" "build" "--release" "--manifest-path" "/tmp/xargo.85ywWqqH4H1K/Cargo.toml" "--target" "x86_64-unknown-redox" "-p" "std"` failed with exit code: Some(101)
note: run with `RUST_BACKTRACE=1` for a backtrace
./repo.sh failed.mk/initfs.mk:2: recipe for target 'build/initfs.tag' failed
make: *** [build/initfs.tag] Error 1
```
**Build information**:
* rustc 1.21.0-nightly (f774bced5 2017-08-12)
* git head `3c5116424bdc2330d247fa31c9497446e3898ef5`
* uname `Linux nick-1337-linux 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux`
https://gitlab.redox-os.org/redox-os/tfs/-/issues/64Implement `Clone` for `conc::Guard`.2018-06-13T19:39:49ZJeremy SollerImplement `Clone` for `conc::Guard`.*Created by: ticki*
*Created by: ticki*
https://gitlab.redox-os.org/redox-os/redox/-/issues/1023Build failed : (Ubuntu 17.04) : "error: Could not compile `core`."2018-06-15T11:40:00ZJeremy SollerBuild failed : (Ubuntu 17.04) : "error: Could not compile `core`."*Created by: sinkarharshad*
Reproduction: ```make all```
Expected behavior: build should get completed successfully
Actual behavior: stuck with: "error: Could not compile `core`."
Build information:
```
make
cd kernel && xa...*Created by: sinkarharshad*
Reproduction: ```make all```
Expected behavior: build should get completed successfully
Actual behavior: stuck with: "error: Could not compile `core`."
Build information:
```
make
cd kernel && xargo clean
rm -rf build/initfs
cargo run --manifest-path installer/Cargo.toml -- --cookbook=cookbook initfs.toml
Finished dev [unoptimized + debuginfo] target(s) in 0.2 secs
Running `installer/target/debug/redox_installer --cookbook=cookbook initfs.toml`
Install Config {
general: GeneralConfig {
prompt: false,
sysroot: Some(
"build/initfs"
)
},
packages: {
"drivers": PackageConfig {
version: None,
git: None,
path: None
},
"init": PackageConfig {
version: None,
git: None,
path: None
},
"redoxfs": PackageConfig {
version: None,
git: None,
path: None
}
},
files: [
FileConfig {
path: "/etc/init.rc",
data: "export PATH /bin\nexport TMPDIR /tmp\nvesad T T G\nstdio display:1\nps2d\npcid /etc/pcid/initfs.toml\nredoxfs disk:0 file\ncd file:\nrun.d /etc/init.d\n"
}
],
users: {}
}
Create directory /home/harshads/devel/redox/build/initfs/
repo - building drivers
cook - drivers build
Updating registry `https://github.com/rust-lang/crates.io-index`
Compiling libc v0.0.0 (file:///home/harshads/devel/redox/rust/src/rustc/libc_shim)
Compiling gcc v0.3.51
Compiling core v0.0.0 (file:///home/harshads/devel/redox/rust/src/libcore)
Compiling libc v0.2.29
Compiling unwind v0.0.0 (file:///home/harshads/devel/redox/rust/src/libunwind)
Compiling filetime v0.1.10
Compiling build_helper v0.1.0 (file:///home/harshads/devel/redox/rust/src/build_helper)
Compiling compiler_builtins v0.0.0 (file:///home/harshads/devel/redox/rust/src/rustc/compiler_builtins_shim)
Compiling std v0.0.0 (file:///home/harshads/devel/redox/rust/src/libstd)
error: variable does not need to be mutable
--> /home/harshads/devel/redox/rust/src/libcore/ops/function.rs:190:41
|
190 | extern "rust-call" fn call_once(mut self, args: A) -> F::Output {
| ^^^^^^^^
|
note: lint level defined here
--> /home/harshads/devel/redox/rust/src/libcore/lib.rs:68:9
|
68 | #![deny(warnings)]
| ^^^^^^^^
= note: #[deny(unused_mut)] implied by #[deny(warnings)]
error: variable does not need to be mutable
--> /home/harshads/devel/redox/rust/src/libcore/option.rs:875:18
|
875 | fn into_iter(mut self) -> IterMut<'a, T> {
| ^^^^^^^^
error: variable does not need to be mutable
--> /home/harshads/devel/redox/rust/src/libcore/result.rs:912:18
|
912 | fn into_iter(mut self) -> IterMut<'a, T> {
| ^^^^^^^^
error: aborting due to 3 previous errors
error: Could not compile `core`.
To learn more, run the command again with --verbose.
error: `"cargo" "build" "--release" "--manifest-path" "/tmp/xargo.iu4N7cH6a68m/Cargo.toml" "--target" "x86_64-unknown-redox" "-p" "std"` failed with exit code: Some(101)
note: run with `RUST_BACKTRACE=1` for a backtrace
./repo.sh failed.mk/initfs.mk:2: recipe for target 'build/initfs.tag' failed
make: *** [build/initfs.tag] Error 1
```
Help is appreciated, thank you in advance!
Tried:
+ #884
https://gitlab.redox-os.org/redox-os/ion/-/issues/496JIT2018-06-18T16:34:37ZMichael Aaron Murphymmstick@pm.meJIT*Created by: mcandre*
Will ion get a JIT? So that large, looping shell scripts can finally run faster than they have been!*Created by: mcandre*
Will ion get a JIT? So that large, looping shell scripts can finally run faster than they have been!https://gitlab.redox-os.org/redox-os/ion/-/issues/495src/parser/shell_expand/mod.rs:277 is reachable2018-06-12T14:22:02ZMichael Aaron Murphymmstick@pm.mesrc/parser/shell_expand/mod.rs:277 is reachable*Created by: msehnout*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
```
let PROMPT = "${USER}@${PWD} (${git::branch})"
thread 'main' panicked at 'internal error: entered unreachable code', sr...*Created by: msehnout*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
```
let PROMPT = "${USER}@${PWD} (${git::branch})"
thread 'main' panicked at 'internal error: entered unreachable code', src/parser/shell_expand/mod.rs:277
note: Run with `RUST_BACKTRACE=1` for a backtrace.
```
see the `@${PWD}` which should have been `\@${PWD}`, but I forgot to backslash it.
**Expected behavior**: [describe the behavior you would expect the repro to yield.]
no crash
**Actual behavior**: [describe the actual behavior, which is presented through the repro.].
**Build information**: [output of `rustc -V`, `git rev-parse HEAD`, `qemu-i386 -version`, `uname -a`, etc.]
$ git rev-parse HEAD
d144f190bdc3fda5760333896fb4511728010326
**Blocking/related**: [issues or PRs blocking or being related to this issue.]
**Misc**: [optional: for other relevant information that should be known or cannot be described in the other fields.]
------
_If the above does not fit the nature of the issue feel free to modify it._
https://gitlab.redox-os.org/redox-os/ion/-/issues/494support CDPATH2019-03-23T17:46:26ZMichael Aaron Murphymmstick@pm.mesupport CDPATH*Created by: aeosynth*
> The search path for the `cd` command. This is a colon-separated list of directories in which the shell looks for destination directories specified by the `cd` command. A sample value is ".:~:/usr".
as seen in...*Created by: aeosynth*
> The search path for the `cd` command. This is a colon-separated list of directories in which the shell looks for destination directories specified by the `cd` command. A sample value is ".:~:/usr".
as seen in bash, zsh, fish...Ion Shell v1.0.0https://gitlab.redox-os.org/redox-os/redox/-/issues/10220.3.0 Bootup Hangs on Hardware: "Startup Arch"2023-06-13T04:42:47ZJeremy Soller0.3.0 Bootup Hangs on Hardware: "Startup Arch"*Created by: Amavect*
**Reproduction**: First, I burned the 0.3.0 ISO to a USB flash drive using Rufus, settings supplied below. Then, I changed my boot order so the USB takes priority.
**Expected behavior**: I would expect the boot...*Created by: Amavect*
**Reproduction**: First, I burned the 0.3.0 ISO to a USB flash drive using Rufus, settings supplied below. Then, I changed my boot order so the USB takes priority.
**Expected behavior**: I would expect the boot sequence to reach a point of user input.
**Actual behavior**: After booting, I am able to input my screen resolution. After confirming the correct resolution, a new screen appears and subsequently hangs. All buttons do nothing. A few cryptic messages are displayed in the attached photos.
**Build information**: https://github.com/redox-os/redox/releases/tag/0.3.0
**Redox release**: Official release 0.3.0
**Blocking/related**: These issues appear to have the same issue: #989 #1000
**Misc**: I see that RAM in QEMU is a common issue. My hardware has 8 GB of RAM. Hardware specs are provided below. My USB drive is 1.8 GB, so I wouldn't think that would cause any issues.
I would like to contribute what little I can to this project, but if I cannot run it on real hardware, what's the point?
Here are the Rufus settings (though likely not the issue):
![rufus](https://user-images.githubusercontent.com/28678586/29137936-9d8ae91c-7d07-11e7-9b1c-e8f3b99c41b8.png)
The boot sequence works fine:
![c1ypxyw](https://user-images.githubusercontent.com/28678586/29137945-a46ab3d4-7d07-11e7-9bb0-e037b5cec4a7.jpg)
Here is where the bootup hangs:
![68crssg](https://user-images.githubusercontent.com/28678586/29137949-a83b811e-7d07-11e7-8ce0-bc13145e750c.jpg)
Hardware specs:
![specs](https://user-images.githubusercontent.com/28678586/29138242-b1cb52b2-7d08-11e7-904e-a0b98db8d0af.png)https://gitlab.redox-os.org/redox-os/redox/-/issues/1021build failed : Could not compile `vesad`.2018-06-15T11:40:00ZJeremy Sollerbuild failed : Could not compile `vesad`.*Created by: sinkarharshad*
Reproduction: ```make / make all```
Expected behavior: Build process should work
Actual behavior: Here is the problem:
```
Create directory /home/shk4abt/devel/redoxos/redox/build/initfs/
repo - buil...*Created by: sinkarharshad*
Reproduction: ```make / make all```
Expected behavior: Build process should work
Actual behavior: Here is the problem:
```
Create directory /home/shk4abt/devel/redoxos/redox/build/initfs/
repo - building drivers
cook - drivers build
Compiling unicase v1.4.2
Compiling vesad v0.1.0 (file:///home/shk4abt/devel/redoxos/redox/cookbook/recipes/drivers/build/vesad)
Compiling ps2d v0.1.0 (file:///home/shk4abt/devel/redoxos/redox/cookbook/recipes/drivers/build/ps2d)
Compiling idna v0.1.4
Compiling syn v0.11.11
error[E0609]: no field `raw_mode` on type `screen::text::ransid::Console`
--> vesad/src/screen/text.rs:120:25
|
120 | if self.console.raw_mode {
| ^^^^^^^^ did you mean `save_x`?
error[E0609]: no field `raw_mode` on type `screen::text::ransid::Console`
--> vesad/src/screen/text.rs:226:27
|
226 | if ! self.console.raw_mode && sync {
| ^^^^^^^^ did you mean `save_x`?
error: aborting due to 2 previous errors
error: Could not compile `vesad`.
warning: build failed, waiting for other jobs to finish...
error: build failed
./repo.sh failed.mk/initfs.mk:2: recipe for target 'build/initfs.tag' failed
make: *** [build/initfs.tag] Error 1
```
Tried:
- ``` make update```
- #960 : While fetching getting this error:
```
cook - acid fetch
Already up-to-date.
cook - binutils fetch
Already up-to-date.
cook - ca-certificates fetch
/home/shk4abt/devel/redoxos/redox/cookbook/recipes/ca-certificates/source /home/shk4abt/devel/redoxos/redox/cookbook/recipes/ca-certificates
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
/home/shk4abt/devel/redoxos/redox/cookbook/recipes/ca-certificates
cook - cargo fetch
Already up-to-date.
cook - contain fetch
Already up-to-date.
cook - coreutils fetch
Updating 10eceaa..a5396b7
error: Your local changes to the following files would be overwritten by merge:
Cargo.lock
Please, commit your changes or stash them before you can merge.
Aborting
```
- ```make clean```
Appreciate your help, thank you in advance.
https://gitlab.redox-os.org/redox-os/ion/-/issues/493`not` ignores global paths2018-06-12T14:22:02ZMichael Aaron Murphymmstick@pm.me`not` ignores global paths*Created by: suhr*
```
# ping
Usage: ping [-aAbBdDfhLnOqrRUvV] [-c count] [-i interval] [-I interface]
[-m mark] [-M pmtudisc_option] [-l preload] [-p pattern] [-Q tos]
[-s packetsize] [-S sndbuf] [-t ttl] [-...*Created by: suhr*
```
# ping
Usage: ping [-aAbBdDfhLnOqrRUvV] [-c count] [-i interval] [-I interface]
[-m mark] [-M pmtudisc_option] [-l preload] [-p pattern] [-Q tos]
[-s packetsize] [-S sndbuf] [-t ttl] [-T timestamp_option]
[-w deadline] [-W timeout] [hop1 ...] destination
# not ping
Error: Unable to find `ping' in PATH: No such file or directory
```
https://gitlab.redox-os.org/redox-os/tfs/-/issues/63Treiber stacks as recursive `Atomic`.2018-06-13T19:39:49ZJeremy SollerTreiber stacks as recursive `Atomic`.*Created by: ticki*
*Created by: ticki*
https://gitlab.redox-os.org/redox-os/redox/-/issues/1020It should be possible to .join() a thread from a thread other than the one th...2023-06-13T04:42:51ZJeremy SollerIt should be possible to .join() a thread from a thread other than the one that created it*Created by: ids1024*
This code works on Linux, but never terminates on Redox; the `waitpid` call never terminates because it is not the parent of the thread it is waiting on.
I originally saw this issue running rustc on Redox.
```rus...*Created by: ids1024*
This code works on Linux, but never terminates on Redox; the `waitpid` call never terminates because it is not the parent of the thread it is waiting on.
I originally saw this issue running rustc on Redox.
```rust
use std::thread;
use std::time;
fn main() {
let child1 = thread::spawn(|| {
thread::sleep(time::Duration::from_secs(5));
});
thread::spawn(|| {
child1.join().unwrap();
println!("joined");
}).join().unwrap();
}
```
I don't know how this should be solved; only one copy of the `JoinHandle` is possible (`pthread_join` says it has undefined behavior when called from several threads, and Rust of course doesn't allow that) but it could be in a different thread than the parent.
Normally I would just send a PR for something like this, but I'm not really sure how it should be handled... I guess the logic of `waitpid` should be changed so it isn't tied to the parent process? But I think that behavior is standard, for waitpid but not pthread_join...