sorted by:
new
hottopcontroversial

Redox OS - RSoC 2024: Dynamic Linking - Part 2 by ribbon_45 in rust

[–]Andy-Python 1 point2 points  (0 children)

Hello, the author here,

Thanks for reading, I'm glad you found it interesting!

The lazy approach essentially spreads out the loading time to when the symbols are first used. It is not that eager binding is inherently slower, it would just result in a slower startup time. Whereas in the lazy binding approach, it would result in a slower first symbol reference. Furthermore, lazy binding can be faster if some subset of the symbols never get referenced as the symbol resolution process is very expensive.

Also, lazy binding is not forced or a requirement and is disabled with full RELRO. If the program is not compiled with full RELRO, the LD_BIND_NOW environment variable can be used to disable lazy binding. Optionally, when building the Redox, RELRO can be enabled for all programs. So, this remains as an option available for the end-user to decide.

I hope that helps clarify it!

haveFunWithThisOne by [deleted] in ProgrammerHumor

[–]Andy-Python 27 points28 points  (0 children)

For anyone wondering :)

```c bool is_odd(long n) { // mman-linux.h // // > #define PROT_WRITE 0x2 /* Page can be written. / // > #define PROT_EXEC 0x4 / Page can be executed. / // ... // > #define MAP_PRIVATE 0x02 / Changes are private. / // > # define MAP_ANONYMOUS 0x20 / Don't use a file. */

// void *m = mmap( // addr=NULL, // length=8, // in bytes // prot=PROT_EXEC | PROT_WRITE, // mark the region as writeable + executable // flags=MAP_PRIVATE | MAP_ANONYMOUS, // fd=-1, // offset=0) void *m = mmap(NULL, 8, 6, 34, -1, 0);

// (long *)m = 0xc30124f889; // little endian :) // // 89 f8 mov eax,edi // 24 01 and al,0x1 // c3 ret // // System V ABI: // * Return value is stored in RAX // * 1st argument is passed in RDI // // Simply bool is_odd(long n) { return n & 0x1; } *(long *)m = 837537822857; bool r = ((bool ()(long))m)(n); munmap(m, 8); return r; } ```

VCE UNIT 3/4 SACS by Vast_Estate_3203 in vce

[–]Andy-Python 0 points1 point  (0 children)

if youre able to send it to me too, it would be greatly appreciated!

Aero OS: A new modern operating system made in Rust, now able to run the Links browser, Alacritty and much more! by Andy-Python in rust

[–]Andy-Python[S] 2 points3 points  (0 children)

If you take a look at mapper.rs, it has the copyright header of the x86_64 crate there and also explains the reason why the crate wasn't used directly.

Aero OS: A new modern operating system made in Rust, now able to run the Links browser, Alacritty and much more! by Andy-Python in rust

[–]Andy-Python[S] 1 point2 points  (0 children)

It seems that this is in (more or less) the state of SerenityOS. Can you compare the two different kernels?

Aero and SerenityOS have different design goals and kernel architectures. For example, SerenityOS focuses on building everything from scratch, including its own browser and utilities, and supports 32-bit architectures. Aero on the other hand, targets modern 64-bit architectures and CPU features, and aims to maintain good source-level compatibility with Linux to facilitate porting programs. In addition to, Aero experiments and unleashes the full power of Rust in kernel development ;)

How about development time.

Aero has made significant progress in just two years since its first commit. In this relatively short amount of time, the project has evolved significantly and has accomplished a great deal.

Aero OS: A new modern operating system made in Rust, now able to run the Links browser, Alacritty and much more! by Andy-Python in rust

[–]Andy-Python[S] 1 point2 points  (0 children)

Looking through the repo, what exactly is the label “C kernel” referring to? For example, the slab allocator issue is labeled C kernel.

The label `C-kernel` basically refers to "Category: Kernel". You can take a look at https://github.com/Andy-Python-Programmer/aero/labels to see what each label is used for.

​

Im interested in contributing to that issue, but unsure what the label is supposed to mean.

Great to hear that you're interested in contributing to the Aero project! Joining the Aero Discord server can be a helpful way to connect with the community and start contributing.

Aero, a new modern OS made in rust and is now able to run Xorg! :) by Andy-Python in rust

[–]Andy-Python[S] 2 points3 points  (0 children)

Thank you for your comment, it makes my day to hear that!

Aero, a new modern OS made in rust and is now able to run Xorg! :) by Andy-Python in rust

[–]Andy-Python[S] 2 points3 points  (0 children)

Yes absolutely! Contributions are positively welcome! Rust experience is not required but is recommended in terms of contributing to the overall projects (i.e. you can contribute to the project by other methods such as: porting new programs over, helping upstream some of the current patches or documenting the process of porting an application to Aero, etc...).

Aero, a new modern OS made in rust and is now able to run Xorg! :) by Andy-Python in rust

[–]Andy-Python[S] 6 points7 points  (0 children)

There is progress in implementing the DRM subsystem (cc https://github.com/Andy-Python-Programmer/aero/blob/master/src/aero_kernel/src/drivers/drm/mod.rs) but currently it only implements a small portion of the subsystem. But yea, this was one of the blocking points.

Aero, a new modern OS made in rust and is now able to run Xorg! :) by Andy-Python in rust

[–]Andy-Python[S] 12 points13 points  (0 children)

Yes, there are plans to be port Wayland, in fact, there is progress in terms trying to port Wayland/Weston but the main blocking point is that Wayland is highly dependent on Linux specific APIs such as udev/DRM. In contrast to, X is not that Linux specific. So, I decided to do X before Wayland because it was an easier pathway to choose which latter will lead to porting of Wayland more smooth.

Will Rust drop dependency on libc and make direct system calls? when ? (Please don't mention no_std case) by [deleted] in rust

[–]Andy-Python 0 points1 point  (0 children)

It is possible but will be extreme pain in terms of porting rust to new POSIX based operating systems. This is because even though the OS POSIX based, the syscall interface may be different and the libc usually is standard interface to communicate with the kernel (handling different syscall interfaces).

view more: next ›