I don’t plan on making that code public. This is purely a learning project for myself. I think going for real-mode 8086 + BIOS is a good idea as a *first step*. I am well aware that this isn’t going anywhere – but now I’ve gained some experience and learned a ton of stuff, so maybe 32 bit or even 64 bit mode might be doable in the future? We’ll see.
It provides a syscall interface, can launch processes, read/write files (in a very simple filesystem).
Here’s a video where I run it natively on my old Dell Inspiron 6400 laptop (and Warp 3 later in the video, because why not):
https://movq.de/v/893daaa548/los86-p133-warp3.mp4
(Sorry for the skewed video. It’s a glossy display and super hard to film this.)
It starts with the laptop’s boot menu and then boots into the kernel and launches a shell as PID 1. From there, I can launch other processes (anything I enter is a new process, except for the exit at the end) and they return the shell afterwards.
And a screenshot running in QEMU:
I don’t plan on making that code public. This is purely a learning project for myself. I think going for real-mode 8086 + BIOS is a good idea as a *first step*. I am well aware that this isn’t going anywhere – but now I’ve gained some experience and learned a ton of stuff, so maybe 32 bit or even 64 bit mode might be doable in the future? We’ll see.
It provides a syscall interface, can launch processes, read/write files (in a very simple filesystem).
Here’s a video where I run it natively on my old Dell Inspiron 6400 laptop (and Warp 3 later in the video, because why not):
https://movq.de/v/893daaa548/los86-p133-warp3.mp4
(Sorry for the skewed video. It’s a glossy display and super hard to film this.)
It starts with the laptop’s boot menu and then boots into the kernel and launches a shell as PID 1. From there, I can launch other processes (anything I enter is a new process, except for the exit at the end) and they return the shell afterwards.
And a screenshot running in QEMU:
I don’t plan on making that code public. This is purely a learning project for myself. I think going for real-mode 8086 + BIOS is a good idea as a *first step*. I am well aware that this isn’t going anywhere – but now I’ve gained some experience and learned a ton of stuff, so maybe 32 bit or even 64 bit mode might be doable in the future? We’ll see.
It provides a syscall interface, can launch processes, read/write files (in a very simple filesystem).
Here’s a video where I run it natively on my old Dell Inspiron 6400 laptop (and Warp 3 later in the video, because why not):
https://movq.de/v/893daaa548/los86-p133-warp3.mp4
(Sorry for the skewed video. It’s a glossy display and super hard to film this.)
It starts with the laptop’s boot menu and then boots into the kernel and launches a shell as PID 1. From there, I can launch other processes (anything I enter is a new process, except for the exit at the end) and they return the shell afterwards.
And a screenshot running in QEMU:
I don’t plan on making that code public. This is purely a learning project for myself. I think going for real-mode 8086 + BIOS is a good idea as a *first step*. I am well aware that this isn’t going anywhere – but now I’ve gained some experience and learned a ton of stuff, so maybe 32 bit or even 64 bit mode might be doable in the future? We’ll see.
It provides a syscall interface, can launch processes, read/write files (in a very simple filesystem).
Here’s a video where I run it natively on my old Dell Inspiron 6400 laptop (and Warp 3 later in the video, because why not):
https://movq.de/v/893daaa548/los86-p133-warp3.mp4
(Sorry for the skewed video. It’s a glossy display and super hard to film this.)
It starts with the laptop’s boot menu and then boots into the kernel and launches a shell as PID 1. From there, I can launch other processes (anything I enter is a new process, except for the exit at the end) and they return the shell afterwards.
And a screenshot running in QEMU:
https://movq.de/v/a6dc0491a9/s.png
https://movq.de/v/a6dc0491a9/s.png
https://movq.de/v/a6dc0491a9/s.png
https://movq.de/v/a6dc0491a9/s.png
> Early on, I was thinking about WAN IP address changes as well but it hasn't happened in ~2.5 years with this ISP.
You mean to say you have the same public IP all the time? For 2.5 years now? Without paying extra? 🤔~
> Early on, I was thinking about WAN IP address changes as well but it hasn't happened in ~2.5 years with this ISP.
You mean to say you have the same public IP all the time? For 2.5 years now? Without paying extra? 🤔~
> Early on, I was thinking about WAN IP address changes as well but it hasn't happened in ~2.5 years with this ISP.
You mean to say you have the same public IP all the time? For 2.5 years now? Without paying extra? 🤔~
> Early on, I was thinking about WAN IP address changes as well but it hasn't happened in ~2.5 years with this ISP.
You mean to say you have the same public IP all the time? For 2.5 years now? Without paying extra? 🤔~
(I was cleaning up spiders on my balcony.)
(I was cleaning up spiders on my balcony.)
(I was cleaning up spiders on my balcony.)
(I was cleaning up spiders on my balcony.)
It’s unfortunate that so many people in tech have such an unfriendly communication style. I won’t read comments on HackerNews, for example. It’s sad, because these people might be more knowledgeable and they might have important things to add, but I just don’t like “being shouted at”. 🫤
It’s unfortunate that so many people in tech have such an unfriendly communication style. I won’t read comments on HackerNews, for example. It’s sad, because these people might be more knowledgeable and they might have important things to add, but I just don’t like “being shouted at”. 🫤
It’s unfortunate that so many people in tech have such an unfriendly communication style. I won’t read comments on HackerNews, for example. It’s sad, because these people might be more knowledgeable and they might have important things to add, but I just don’t like “being shouted at”. 🫤
It’s unfortunate that so many people in tech have such an unfriendly communication style. I won’t read comments on HackerNews, for example. It’s sad, because these people might be more knowledgeable and they might have important things to add, but I just don’t like “being shouted at”. 🫤
Ctrl+w happens to me all the time. 🥴
Ctrl+w happens to me all the time. 🥴
Ctrl+w happens to me all the time. 🥴
Ctrl+w happens to me all the time. 🥴
The keyboard as a password store? Something something “keystore”. 🤪
The keyboard as a password store? Something something “keystore”. 🤪
The keyboard as a password store? Something something “keystore”. 🤪
The keyboard as a password store? Something something “keystore”. 🤪
~/.mozilla on Linux), there’s a chrome folder. You can put a file called userContent.css in there.This also needs the setting
toolkit.legacyUserProfileCustomizations.stylesheets to be true.(I hope they never remove this, it’s super helpful.)
~/.mozilla on Linux), there’s a chrome folder. You can put a file called userContent.css in there.This also needs the setting
toolkit.legacyUserProfileCustomizations.stylesheets to be true.(I hope they never remove this, it’s super helpful.)
~/.mozilla on Linux), there’s a chrome folder. You can put a file called userContent.css in there.This also needs the setting
toolkit.legacyUserProfileCustomizations.stylesheets to be true.(I hope they never remove this, it’s super helpful.)
~/.mozilla on Linux), there’s a chrome folder. You can put a file called userContent.css in there.This also needs the setting
toolkit.legacyUserProfileCustomizations.stylesheets to be true.(I hope they never remove this, it’s super helpful.)
Tab and expected it to auto-complete. 🤦
Tab and expected it to auto-complete. 🤦
Tab and expected it to auto-complete. 🤦
Tab and expected it to auto-complete. 🤦