redox-os issueshttps://gitlab.redox-os.org/groups/redox-os/-/issues2023-06-13T04:42:45Zhttps://gitlab.redox-os.org/redox-os/redox/-/issues/800Redox is Untranslatable2023-06-13T04:42:45ZJeremy SollerRedox is Untranslatable*Created by: pharaone*
Can you make redox (and orbital, all the apps ...) translatable? I can translate redox in Italian. Thanks*Created by: pharaone*
Can you make redox (and orbital, all the apps ...) translatable? I can translate redox in Italian. Thankshttps://gitlab.redox-os.org/redox-os/redox/-/issues/774Build error on Arch Linux2018-06-15T11:40:02ZJeremy SollerBuild error on Arch Linux*Created by: UgnilJoZ*
Using an up to date Arch Linux and Rust Compiler, I am running into a build error.
**Reproduction**:
```
$ pacaur -S make nasm qemu pkg-config fuse
$ git clone https://github.com/redox-os/redox.git --origin up...*Created by: UgnilJoZ*
Using an up to date Arch Linux and Rust Compiler, I am running into a build error.
**Reproduction**:
```
$ pacaur -S make nasm qemu pkg-config fuse
$ git clone https://github.com/redox-os/redox.git --origin upstream --recursive
$ redox/
$ git submodule update --recursive --init
$ rustup update
$ make all
```
**Expected behavior**:
- A successful build
**Actual behavior**:
(output)
```
...
mkdir -p build/userspace
cp libstd/openlibm/libopenlibm.a build/userspace/libopenlibm.a
RUSTC="./rustc.sh" RUSTDOC="./rustdoc.sh" cargo rustc --verbose --manifest-path libstd/Cargo.toml --target x86_64-unknown-redox.json --release -- -o build/userspace/libstd.rlib
Updating git repository `https://github.com/redox-os/syscall.git`
error: failed to load source for a dependency on `redox_syscall`
Caused by:
Unable to update https://github.com/redox-os/syscall.git
Caused by:
failed to fetch into /home/joz/.cargo/git/db/syscall-2a6b827678b57cba
Caused by:
[16/-17] The SSL certificate is invalid
make: *** [Makefile:352: build/userspace/libstd.rlib] Fehler 101
```
**Build information**:
```
$ rustc -V && git rev-parse HEAD && qemu-system-x86_64 -version && uname -a
rustc 1.15.0-nightly (1c448574b 2016-11-28)
7ee0ea3c861dd5b6709e4f0a723619618c356b21
QEMU emulator version 2.7.0, Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers
Linux tower 4.8.11-1-ARCH #1 SMP PREEMPT Sun Nov 27 09:26:14 CET 2016 x86_64 GNU/Linux
```
```
$ cat /etc/os-release
NAME="Arch Linux"
ID=arch
PRETTY_NAME="Arch Linux"
ANSI_COLOR="0;36"
HOME_URL="https://www.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
```
https://gitlab.redox-os.org/redox-os/redox/-/issues/772[Virtualbox] Disk scheme creation error2018-06-15T11:40:02ZJeremy Soller[Virtualbox] Disk scheme creation error*Created by: Yamakaky*
```
thread unnamed panicked at 'ahcid: failed to create disk scheme: File exists'
0: redoxfs: mounted filesystem disk:0 on file:
```
Virtualbox config: https://lut.im/hmaAK2qjUk/cLueTWPpGnI89Lwz.png*Created by: Yamakaky*
```
thread unnamed panicked at 'ahcid: failed to create disk scheme: File exists'
0: redoxfs: mounted filesystem disk:0 on file:
```
Virtualbox config: https://lut.im/hmaAK2qjUk/cLueTWPpGnI89Lwz.pnghttps://gitlab.redox-os.org/redox-os/redox/-/issues/770ISO 0.0.3 fails to boot in VirtualBox2018-06-15T11:40:02ZJeremy SollerISO 0.0.3 fails to boot in VirtualBox*Created by: mattico*
`ahcid: failed to create disk scheme: file exists`
Host: Windows 10 x64 Build 14965
i5-4690K
Virtualbox: v5.1.10
![image](https://cloud.githubusercontent.com/assets/853158/20815552/f8c4bb4e-b7e3-11e6-9ba5-3...*Created by: mattico*
`ahcid: failed to create disk scheme: file exists`
Host: Windows 10 x64 Build 14965
i5-4690K
Virtualbox: v5.1.10
![image](https://cloud.githubusercontent.com/assets/853158/20815552/f8c4bb4e-b7e3-11e6-9ba5-3449b2e5fede.png)
![image](https://cloud.githubusercontent.com/assets/853158/20815572/0c87c05e-b7e4-11e6-8d02-a75da2d89c5b.png)
https://gitlab.redox-os.org/redox-os/redox/-/issues/795Could syscall/numbers.rs be enums?2023-06-13T04:42:45ZJeremy SollerCould syscall/numbers.rs be enums?*Created by: Yoric*
If so, that would make code a little easier to read.*Created by: Yoric*
If so, that would make code a little easier to read.https://gitlab.redox-os.org/redox-os/redox/-/issues/793[Capabilities] Implement revocation of file descriptors2023-06-13T04:42:45ZJeremy Soller[Capabilities] Implement revocation of file descriptors*Created by: Yoric*
The details are a bit fuzzy, but we'll need a mechanism to revoke a capability from a process and any process to which it may have sent it.*Created by: Yoric*
The details are a bit fuzzy, but we'll need a mechanism to revoke a capability from a process and any process to which it may have sent it.https://gitlab.redox-os.org/redox-os/redox/-/issues/773Kernel panic with no ethernet2018-06-15T11:40:02ZJeremy SollerKernel panic with no ethernet*Created by: Lewiscowles1986*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
Remove all ethernet devices from VirtualBox, start live-cd
**Expected behavior**: [describe the behavior you would ...*Created by: Lewiscowles1986*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
Remove all ethernet devices from VirtualBox, start live-cd
**Expected behavior**: [describe the behavior you would expect the repro to yield.]
OS to boot and self-assign local loopback address only, ignoring lack of ethernet
**Actual behavior**: [describe the actual behavior, which is presented through the repro.].
Kernel panic
![image](https://cloud.githubusercontent.com/assets/2605791/20820892/94118ec2-b836-11e6-8a87-2d709368d088.png)
**Build information**: [output of `rustc -V`, `git rev-parse HEAD`, `qemu-i386 -version`, `uname -a`, etc.]
N/A (binary run using 0.3 pre-release iso)
**Blocking/related**: [issues or PRs blocking or being related to this issue.]
Unknown
**Misc**: [optional: for other relevant information that should be known or cannot be described in the other fields.]
N/A
https://gitlab.redox-os.org/redox-os/redox/-/issues/791[Capabilities] Implement open_at2023-06-13T04:42:48ZJeremy Soller[Capabilities] Implement open_at*Created by: Yoric*
Implement a mechanism for opening a file based on a pre-existing file descriptor.
This operation is detailed in the RFC on [userspace capabilities](https://github.com/redox-os/rfcs/pull/2) but the scope is larger. I...*Created by: Yoric*
Implement a mechanism for opening a file based on a pre-existing file descriptor.
This operation is detailed in the RFC on [userspace capabilities](https://github.com/redox-os/rfcs/pull/2) but the scope is larger. In Linux, this operation is used for instance to decrease the amount of disk I/O while walking through directories.https://gitlab.redox-os.org/redox-os/redox/-/issues/766Virtualbox can not boot, got black screen2018-06-15T11:40:02ZJeremy SollerVirtualbox can not boot, got black screen*Created by: mzji*
**Reproduction**:
This is the configuration of my RedoxOS test virtual machine:
![VM config](https://cloud.githubusercontent.com/assets/23279426/20788495/020333ee-b77f-11e6-9624-6887a87ceb19.PNG)
Host: Windows 10 V...*Created by: mzji*
**Reproduction**:
This is the configuration of my RedoxOS test virtual machine:
![VM config](https://cloud.githubusercontent.com/assets/23279426/20788495/020333ee-b77f-11e6-9624-6887a87ceb19.PNG)
Host: Windows 10 Version 1607 (build 10.0.14393) x64 Education edition
Virtualbox version: 5.1.10
**Expected behavior**:
System boots up, after pressing F4 I will get a working desktop.
**Actual behavior**:
System boots up, scrolls a lot of hex numbers (un-gzipping?), then I got a black screen.
I tried F1 ~ F4, but none of these keys works. I tried ALL of them.
The disk/network indicator in the guest virtual machine window didn't blink, that means no disk/network activities.
**Build information**:
0.0.3 (Pre-released version)
https://gitlab.redox-os.org/redox-os/redox/-/issues/790[Capabilities] Implement dup_from/dup_to2023-06-13T04:42:47ZJeremy Soller[Capabilities] Implement dup_from/dup_to*Created by: Yoric*
Implement a way of sending a file descriptor across processes.
These operations are detailed in the RFC on [userspace capabilities](https://github.com/redox-os/rfcs/pull/2), although the scope is larger than securit...*Created by: Yoric*
Implement a way of sending a file descriptor across processes.
These operations are detailed in the RFC on [userspace capabilities](https://github.com/redox-os/rfcs/pull/2), although the scope is larger than security. In particular, it might be very useful to implement a high-level IPC mechanism.
@jackpot51 Could you assign this issue to me?https://gitlab.redox-os.org/redox-os/redox/-/issues/792[Capabilities] Clarify the behavior of file descriptors when calling `exec*`2023-06-13T04:42:45ZJeremy Soller[Capabilities] Clarify the behavior of file descriptors when calling `exec*`*Created by: Yoric*
In general, we probably want to close file descriptors.
I suspect that, to simplify IPC and capabilities, we may want to support a variant of `exec*` that lets us pass file descriptors, though.*Created by: Yoric*
In general, we probably want to close file descriptors.
I suspect that, to simplify IPC and capabilities, we may want to support a variant of `exec*` that lets us pass file descriptors, though.https://gitlab.redox-os.org/redox-os/redox/-/issues/786coreutils.cgu-0.rs: [...]: undefined reference to `log10'2018-06-15T11:40:02ZJeremy Sollercoreutils.cgu-0.rs: [...]: undefined reference to `log10'*Created by: Yoric*
My builds end with the following error:
```
Compiling coreutils v0.1.0 (file:///Users/david/Documents/Code/redox/programs/coreutils)
warning: ignoring --out-dir flag due to -o flag.
error: linking with `x8...*Created by: Yoric*
My builds end with the following error:
```
Compiling coreutils v0.1.0 (file:///Users/david/Documents/Code/redox/programs/coreutils)
warning: ignoring --out-dir flag due to -o flag.
error: linking with `x86_64-elf-gcc` failed: exit code: 1
|
= note: "x86_64-elf-gcc" "-m64" "-nostdlib" "-static" "-L" "/Users/david/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-unknown-redox/lib" "filesystem/bin/dd.0.o" "-o" "filesystem/bin/dd" "-Wl,--gc-sections" "-nodefaultlibs" "-L" "build/userspace" "-L" "/Users/david/Documents/Code/redox/programs/coreutils/target/x86_64-unknown-redox/release/deps" "-L" "/Users/david/Documents/Code/redox/programs/coreutils/target/release/deps" "-L" "/Users/david/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-unknown-redox/lib" "-Wl,-Bstatic" "-Wl,-Bdynamic" "/Users/david/Documents/Code/redox/programs/coreutils/target/x86_64-unknown-redox/release/deps/libcoreutils-e9abec9509129535.rlib" "/Users/david/Documents/Code/redox/build/userspace/libstd.rlib" "/Users/david/Documents/Code/redox/build/userspace/libunwind-33a24fd8028a45a4.rlib" "/Users/david/Documents/Code/redox/build/userspace/liblibc-da5b56675224ab74.rlib" "/Users/david/Documents/Code/redox/build/userspace/libsyscall-f10dde67b3ebebaf.rlib" "/Users/david/Documents/Code/redox/build/userspace/librand.rlib" "/Users/david/Documents/Code/redox/build/userspace/libcollections.rlib" "/Users/david/Documents/Code/redox/build/userspace/libstd_unicode.rlib" "/Users/david/Documents/Code/redox/build/userspace/liballoc.rlib" "/Users/david/Documents/Code/redox/build/userspace/libspin-320fb8ccccfe7367.rlib" "/Users/david/Documents/Code/redox/build/userspace/libcompiler_builtins-aa91fdc75676e135.rlib" "/Users/david/Documents/Code/redox/build/userspace/libralloc-ef7cfc16e012a7a4.rlib" "/Users/david/Documents/Code/redox/build/userspace/libralloc_shim-8ace3497bf57d728.rlib" "/Users/david/Documents/Code/redox/build/userspace/libsyscall-9542e66cfe957b75.rlib" "/Users/david/Documents/Code/redox/build/userspace/libpanic_abort-557f32b78880cc45.rlib" "/Users/david/Documents/Code/redox/build/userspace/libcore.rlib" "build/userspace/libopenlibm.a"
= note: /Users/david/Documents/Code/redox/programs/coreutils/target/x86_64-unknown-redox/release/deps/libcoreutils-e9abec9509129535.rlib(coreutils-e9abec9509129535.0.o): In function `coreutils::to_human_readable_string::h3882711dbf0bcdd0':
coreutils.cgu-0.rs:(.text._ZN9coreutils24to_human_readable_string17h3882711dbf0bcdd0E+0x7c): undefined reference to `log10'
coreutils.cgu-0.rs:(.text._ZN9coreutils24to_human_readable_string17h3882711dbf0bcdd0E+0x9c): undefined reference to `pow'
collect2: error: ld returned 1 exit status
```
Using MacOS X 10.11.6.
# Attached
- [libopenlibm.a (zipped)](https://github.com/redox-os/redox/files/654304/lib.zip)
https://gitlab.redox-os.org/redox-os/redox/-/issues/784Streamline pull + rebuild2018-06-15T11:40:02ZJeremy SollerStreamline pull + rebuild*Created by: Yoric*
So far, I haven't been able to come up with a reproducible workflow to pull and rebuild. All my attempts involve sequences of:
- `git pull --rebase --recurse-submodules`;
- `git clean -X -f -d`;
- `git submodule...*Created by: Yoric*
So far, I haven't been able to come up with a reproducible workflow to pull and rebuild. All my attempts involve sequences of:
- `git pull --rebase --recurse-submodules`;
- `git clean -X -f -d`;
- `git submodule update --recursive --init`;
- `make clean`;
- `make all`;
- `cargo update` in some subdirectories;
- head-scratching;
- rinse and repeat.
I am sure that there must be a good way to handle this that does not involve spending 1h each time I pull. We should:
1. find such a workflow;
2. turn it into a single command `make pull`.https://gitlab.redox-os.org/redox-os/redox/-/issues/758Archlinux dependencies2018-06-15T11:40:02ZJeremy SollerArchlinux dependencies*Created by: Yamakaky*
- `qemu-system-i386` doesn't exist on x86_64 (https://wiki.archlinux.org/index.php/QEMU#Running_virtualized_system)
- you could simplify if to
```
deps=(git nasm fuse)
if [ "$1" == "qemu" ]; then
deps+=(qemu...*Created by: Yamakaky*
- `qemu-system-i386` doesn't exist on x86_64 (https://wiki.archlinux.org/index.php/QEMU#Running_virtualized_system)
- you could simplify if to
```
deps=(git nasm fuse)
if [ "$1" == "qemu" ]; then
deps+=(qemu)
fi
sudo pacman -S --needed $deps
```
We already know `pacman` is for installing packages, no need to say it.https://gitlab.redox-os.org/redox-os/redox/-/issues/756Build fails after compiling init2018-06-15T11:40:01ZJeremy SollerBuild fails after compiling init*Created by: shawnanastasio*
**Reproduction**:
1. Clone fresh copy of repository
2. bash bootstrap.sh -d
3. rustup override set nightly
4. git submodule update --recursive --init
5. make all
**Expected behavior**: Redox compiles...*Created by: shawnanastasio*
**Reproduction**:
1. Clone fresh copy of repository
2. bash bootstrap.sh -d
3. rustup override set nightly
4. git submodule update --recursive --init
5. make all
**Expected behavior**: Redox compiles successfully
**Actual behavior**:
The build fails after compiling the `init` program. The program compiles successfully, but does not get outputted in the expected directory, and as a result, the build fails.
```
Compiling init v0.1.0 (file:///home/shawnanastasio/opt/redox/programs/init)
warning: ignoring specified output filename because multiple outputs were requested
warning: ignoring --out-dir flag due to -o flag.
Finished release [optimized] target(s) in 6.32 secs
strip initfs/bin/init
strip: 'initfs/bin/init': No such file
Makefile:325: recipe for target 'initfs/bin/init' failed
make: *** [initfs/bin/init] Error 1
```
**Build information**:
rustc: `rustc 1.15.0-nightly (ac635aa95 2016-11-18)`
cargo: `cargo 0.16.0-nightly (d1bfc01 2016-11-18)`
uname: `Linux 4.7.0-0.bpo.1-amd64 #1 SMP Debian 4.7.8-1~bpo8+1 (2016-10-19) x86_64 GNU/Linux`
**Blocking/related**:
Seems to be related to this issue with `cargo`: https://github.com/rust-lang/cargo/issues/2559
**Misc**:
Full build log: http://pastebin.com/bdum1wtG
https://gitlab.redox-os.org/redox-os/redox/-/issues/780VirtualBox+LiveISO on macOS Sierra: Only can boot with Null Audi Driver2018-06-15T11:40:02ZJeremy SollerVirtualBox+LiveISO on macOS Sierra: Only can boot with Null Audi Driver*Created by: johalun*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
Select CoreAudio audio driver.
**Expected behavior**: [describe the behavior you would expect the repro to yield.]
Boot to...*Created by: johalun*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
Select CoreAudio audio driver.
**Expected behavior**: [describe the behavior you would expect the repro to yield.]
Boot to login prompt.
**Actual behavior**: [describe the actual behavior, which is presented through the repro.].
Freeze during boot in console mode
**Build information**: [output of `rustc -V`, `git rev-parse HEAD`, `qemu-i386 -version`, `uname -a`, etc.]
Using VirtualBox with liveiso
**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.]
Freezes seem rather random. Either at console or at GUI before login prompt is visible.
Running single core in VirtualBox seem to have the best change of successful boot. Even with Null Audio Driver and single core, it freezes sometimes during boot. Keep on resetting the VM and eventually boot is successful.
------
_If the above does not fit the nature of the issue feel free to modify it._
https://gitlab.redox-os.org/redox-os/redox/-/issues/746Use Ripgrep as default search2023-06-13T04:42:45ZJeremy SollerUse Ripgrep as default search*Created by: st3soren*
Could you possibly make Ripgrep the default CLI search tool for redox? [0]
It's also written in Rust.
It's much faster than grep, and other search utilities. [1]
[0] https://github.com/BurntSushi/ripgrep
...*Created by: st3soren*
Could you possibly make Ripgrep the default CLI search tool for redox? [0]
It's also written in Rust.
It's much faster than grep, and other search utilities. [1]
[0] https://github.com/BurntSushi/ripgrep
[1] http://blog.burntsushi.net/ripgrep/https://gitlab.redox-os.org/redox-os/redox/-/issues/777failed to load source for a dependency on `redox_syscall`2018-06-15T11:40:02ZJeremy Sollerfailed to load source for a dependency on `redox_syscall`*Created by: Csega*
Hi Guys,
I see the following error for a few days. I thought it worth to mention it. Could you help me with this one?
Cheers!
Csega
**Reproduction**: Run the newest bootstrap.sh for a clean installation.
...*Created by: Csega*
Hi Guys,
I see the following error for a few days. I thought it worth to mention it. Could you help me with this one?
Cheers!
Csega
**Reproduction**: Run the newest bootstrap.sh for a clean installation.
**Expected behavior**: compile and run the code
**Actual behavior**: after cloning and cd redox, the make all gives the following error:
Updating git repository `https://github.com/redox-os/syscall.git`
error: failed to load source for a dependency on `redox_syscall`
Caused by:
Unable to update https://github.com/redox-os/syscall.git
Caused by:
failed to fetch into /home/my_user/.cargo/git/db/syscall-2a6b827678b57cba
Caused by:
[16/-17] The SSL certificate is invalid
Makefile:352: recipe for target 'build/userspace/libstd.rlib' failed
make: *** [build/userspace/libstd.rlib] Error 101
**Build information**: rustc 1.15.0-nightly (28d6623bc 2016-12-03), git rev-parse HEAD: 7ee0ea3c861dd5b6709e4f0a723619618c356b21, qemu version: 2.5, Linux elementaryOS 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:29:54 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
https://gitlab.redox-os.org/redox-os/redox/-/issues/776When I execute `sudo make virtualbox`, just show a Redox image background.2018-06-15T11:40:02ZJeremy SollerWhen I execute `sudo make virtualbox`, just show a Redox image background.*Created by: origel*
start up log seems OK.
$ sudo make virtualbox
[sudo] password for work:
#filesystem/bin/shutdown filesystem/bin/test
fusermount -u build/filesystem/
fusermount: failed to unmount /home/work/linux/redox...*Created by: origel*
start up log seems OK.
$ sudo make virtualbox
[sudo] password for work:
#filesystem/bin/shutdown filesystem/bin/test
fusermount -u build/filesystem/
fusermount: failed to unmount /home/work/linux/redox/build/filesystem: No such file or directory
make: [build/filesystem.bin] Error 1 (Ignore)
rm -rf build/filesystem.bin build/filesystem/
echo exit | cargo run --manifest-path schemes/redoxfs/Cargo.toml --bin redoxfs-utility build/filesystem.bin 128
Finished debug [unoptimized + debuginfo] target(s) in 0.0 secs
Running `schemes/redoxfs/target/debug/redoxfs-utility build/filesystem.bin 128`
redoxfs: created filesystem build/filesystem.bin
redoxfs# mkdir -p build/filesystem/
cargo build --manifest-path schemes/redoxfs/Cargo.toml --bin redoxfs-fuse --release
Finished release [optimized] target(s) in 0.0 secs
schemes/redoxfs/target/release/redoxfs-fuse build/filesystem.bin build/filesystem/ &
sleep 2
redoxfs: opened filesystem build/filesystem.bin
pgrep redoxfs-fuse
30748
cp -RL filesystem/* build/filesystem/
chown -R 0:0 build/filesystem
chown -R 1000:1000 build/filesystem/home/user
chmod -R uog+rX build/filesystem
chmod -R u+w build/filesystem
chmod -R og-w build/filesystem
chmod -R 755 build/filesystem/bin
chmod -R u+rwX build/filesystem/root
chmod -R og-rwx build/filesystem/root
chmod -R u+rwX build/filesystem/home/user
chmod -R og-rwx build/filesystem/home/user
chmod +s build/filesystem/bin/passwd
chmod +s build/filesystem/bin/su
chmod +s build/filesystem/bin/sudo
mkdir build/filesystem/tmp
chmod 1777 build/filesystem/tmp
sync
fusermount -u build/filesystem/
rm -rf build/filesystem/
nasm -f bin -o build/harddrive.bin -D ARCH_x86_64 -ibootloader/x86_64/ bootloader/x86_64/harddrive.asm
echo "Delete VM"
Delete VM
VBoxManage unregistervm Redox --delete; \
if [ $? -ne 0 ]; \
then \
if [ -d "$HOME/VirtualBox VMs/Redox" ]; \
then \
echo "Redox directory exists, deleting..."; \
rm -f -rf "$HOME/VirtualBox VMs/Redox"; \
fi \
fi
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
echo "Delete Disk"
Delete Disk
rm -f harddrive.vdi
echo "Create VM"
Create VM
VBoxManage createvm --name Redox --register
Virtual machine 'Redox' is created and registered.
UUID: 02682db8-97c3-49a6-a5e0-7d4a68b50943
Settings file: '/root/VirtualBox VMs/Redox/Redox.vbox'
echo "Set Configuration"
Set Configuration
VBoxManage modifyvm Redox --memory 1024
VBoxManage modifyvm Redox --vram 16
VBoxManage modifyvm Redox --nic1 nat
VBoxManage modifyvm Redox --nictype1 82540EM
VBoxManage modifyvm Redox --cableconnected1 on
VBoxManage modifyvm Redox --nictrace1 on
VBoxManage modifyvm Redox --nictracefile1 build/network.pcap
VBoxManage modifyvm Redox --uart1 0x3F8 4
VBoxManage modifyvm Redox --uartmode1 file build/serial.log
VBoxManage modifyvm Redox --usb off # on
VBoxManage modifyvm Redox --keyboard ps2
VBoxManage modifyvm Redox --mouse ps2
VBoxManage modifyvm Redox --audio "pulse"
VBoxManage modifyvm Redox --audiocontroller ac97
echo "Create Disk"
Create Disk
VBoxManage convertfromraw build/harddrive.bin build/harddrive.vdi
Converting from raw image file="build/harddrive.bin" to file="build/harddrive.vdi"...
Creating dynamic image with size 135755776 bytes (130MB)...
echo "Attach Disk"
Attach Disk
VBoxManage storagectl Redox --name ATA --add sata --controller IntelAHCI --bootable on --portcount 1
VBoxManage storageattach Redox --storagectl ATA --port 0 --device 0 --type hdd --medium build/harddrive.vdi
echo "Run VM"
Run VM
VBoxManage startvm Redox
Waiting for VM "Redox" to power on...
VM "Redox" has been successfully started.
https://gitlab.redox-os.org/redox-os/redox/-/issues/748Suggestion: Make use of rumpkernels2023-06-13T04:42:45ZJeremy SollerSuggestion: Make use of rumpkernels*Created by: pothos*
The [rump kernel project](http://rumpkernel.org/) defines a way in which drivers can be used in kernel space as well as user space (think microkernel) or linkable library. In NetBSD one can use rumpkernels for some ...*Created by: pothos*
The [rump kernel project](http://rumpkernel.org/) defines a way in which drivers can be used in kernel space as well as user space (think microkernel) or linkable library. In NetBSD one can use rumpkernels for some filesystem drivers already, so that they run in userspace. The [Rumprun unikernel](https://github.com/rumpkernel/rumprun) allows compiling a program against the NetBSD libc altogether with rumpkernel drivers as library in order to run this program on bare metal or KVM.
Using rumpkernels as drivers in redox would be interesting and expose functionality of existing C-drivers to it in a non-harmful way.
Genode OS already [did exactly this](http://genode.org/documentation/release-notes/14.02#NetBSD_file_systems_using_rump_kernels).
List of components available [here](https://github.com/rumpkernel/wiki/wiki/Info:-Available-rump-kernel-components).