Aero is a new modern, experimental, unix-like operating system following the monolithic kernel design. Supporting modern PC features such as long mode, 5-level paging, and SMP (multicore), to name a few.
Its already able to run programs such as the GNU coreutils, GNU binutils, Nyancat, TinyCC, GCC and soon doom generic and rust aswell :)
https://preview.redd.it/i4ofhde34t981.png?width=1074&format=png&auto=webp&s=a8972f82e1dd24cc101994bfd056f2a4f1953afc
GitHub: https://github.com/Andy-Python-Programmer/aero
Official Discord Server: https://discord.gg/8gwhTTZwt8
Forgive any and all ignorance as I ask this question please. As I understand it, Linux was the first open source UNIX-like OS, correct? And UNIX itself has been around since 1969!
My question is, if the robust stability and security features like protected memory, preemptive multitasking, secure user accounts/admin stuff and all that have existed for so long... why did Mac OS and Windows both lack any of that robustness until a full decade after Linux was created?
In other words, if we had a way to make an OS that would virtually never crash and had orderly memory management and security and the rest, why did Apple and Microsoft both ship such fragile OS's that could be toppled by a single rogue app and were generally terrible at security and for SO long?
Apple even had it's own UNIX implementation for the early Mac computers complete with the System 7 GUI laid over top. Anyone care to speculate why THAT wasn't just the Mac OS everyone got? Microsoft also licensed a UNIX version from AT&T in the early days. So it's not as if no one knew computers didn't have to suck. Why did it take so long to reach the average PC user? Thoughts?
After spending some weeks diving deep into OpenBSD, after years on the Linux ecosystem (multiple distros), there are reasons for which I love OpenBSD and other reasons for which I'm thinking about coming back to Linux. Although some of these OpenBSD attributes are inherited from the Unix way of doing things.
Pros of OpenBSD
- Favoring simplicity. In contrast to the GNU userland, OpenBSD utilities are meant to be more concise, without feature-creep. E.g. the POSIX tools implementations (
grep,cat,sed, etc.) vs. the GNU ones. Ordoasvssudo. Orrcvssystemd. Etc. This makes them easier to use, retain a clear full picture of them, and to master. And from the developer side: they are easier to develop, test and maintain. - Holistic approach. OpenBSD, AFAIC, is developed as a single unit (repository). All of it's components are meant to work in tandem with each other. Although it obviously also enables the user to add or change its different parts as they wish, since it's an open-source Unix OS. Actually, the whole concept of Linux distributions is this one exactly, isn't it? To glue all these packages so they can work properly together. Even so, I think OpenBSD might put more emphasis on this than the Linux distros I've tried, in my experience.
- Better Documentation. Specifically: manual pages. They are treated as a first-class citizen, and it shows. Although I think GNU's info pages can also be as extensive, they can be too verbose and convoluted (this relates to the first point). They are also not as interconnected (which relates to the previous point). It feels very good to just run
man afterbootand just be able to find anything I need from there (alsoapropos). - CLI centered. It follows the Unix axiom of avoiding interactive input. So your main platform is the shell and you can create pipelines of commands. E.g.
manvsinfo. The later is meant to be used interactively while the first can, e.g., be piped to stdout and searched withgrep.vi/mgvsGNU emacs. The first are meant to be used only as text editors while the shell is your main platform and Emacs is meant to be the platform itself. E.g. in Emacs you search content of files by usingisearchindired-mode, and if you are a vi user you usefindandgrepand then edit whatever files where outputted. Of course you can use one or the other in Linux or OpenBSD, these were just quick general examples to show the philosophy behind each.
Co
... keep reading on reddit โกI get that the UWP framework is not on those versions but... how hard would it be to rewrite it to utilize a different framework for macOS/Linux??
And I don't even think the question is how hard it is, it's how long it would take.
(I just wanted to rant, sorry :/)
Where's the C chord.
I solved easily in that way in my Big Sur...it requires 30 secs.
The motivation cause probably this will works in Linux too is based into file system: Windows file manager is completely different from Unix ones...probably that's a Unix problem as I have understood.
Unix own those weirdos(and usefull) Daemons(developed for the servers initially) but they are a bit problematic sometimes...some can just stop to working. Is really all into the file system...cut and past it will solve this easily.
Don't forget to empty the bin and if you are like me using daily side by side a Mac AND a Linux empty the usb key's bin too!
Rememeber to NEVER unite two The Sims's folders!
By the way usually after trashed a The Sims folder Origin will just create a new one.
Just because we humans come from apes, can we use apes and humans interchangeably? It is similar in case of Linux and UNIX.
We know that you can have a REPL that has a full on type system (Powershell) but what about enhancing Unix shells by outputting stoud into a structured format, so that at least you have value pairs instead of scraping giant strings.
The example that got me thinking was when someone used a CSV output of a command, just to import it and use one field.
Iโm not PL theorist, so I donโt know if itโs feasible, but basically this would entail every CLI program having one format as a common denominator.
Hello,
I have come to love common lisp more and more as I work with it, in fact I have considered ditching the POSIX core utilities for sbcl + come libraries, but there is no issue I can not seem to get past which not only makes it impossible to ditch core utilities but also extremely hard to even develop with common lisp over other languages.
I have run into an issue time and again where I need to something like killing a process, getting full permissions of a file, get the PID of a process I did not start, etc. and the solution I find every time is to make a call to a userland program like ps or pkill. While of course I know how to work with these and I do not mind using them when I am just in an sbcl session this do become an annoyance when I am rolling an actual program or script. First, not every system will have pkill some servers do not have it and on some of my workstations I do not have it as I use killall and while I could replace pkill with killall in my scripts that also does not work as not all systems have that! You get where I am going with this: I do not want to make assumptions about what the userland I am working with has or does not have nor do I want to force it to conform with certain dependencies. I have looked at UIOP and even OSIcat and while they do solve many problems with using common lisp on UNIX-like operating systems for some reason, for some unholy demonic reason, they never include anything for process management or getting file permissions in the UNIX dialect. This has made it very very very hard to work with common lisp and it is driving me crazy.
Does anyone know of a solid time tested library that provides a well rounded and full set of calls for working with UNIX-like operating systems?
I recently came across POSIX shared memory and thought like ... what can you do with this and numpy? Long story short: I searched for bits and pieces, found some tests by other people (good one here), but no complete, "clean" implementation. I'd love to know if there is some Python package for this that I may have overlooked.
Otherwise, meet multi-process (bypassing the GIL) shared-memory prange-style (just like in numba and Cython)) for-loops in virtually pure Python but very similar to what you can do with openMP & its threads in C & Fortran:
@parallel(processes = 2, shared = ('a',))
def task(a: np.ndarray, b: int):
for idx in prange(a.shape[0]):
print(f'[worker_id={worker_id:d} pid={os.getpid():d}] idx=={idx:d}')
a[idx] += b
def demo():
a = np.arange(1, 11, dtype = 'f8')
print(a)
task(a = a, b = 7)
print(a)
Complete implementation plus two demos: https://gist.github.com/s-m-e/bf01cba201d27c793873b819264d3a4b
Is there a proper library for this? If not, would you like having one?
Feedback of any kind of highly welcome!
What is the most Unix SysV-like distro out there?
