<PublicWiFi>
im really struggling with the virtual drives and how to properly abstract away the physical drive from it
eluks has joined #osdev
netbsduser has joined #osdev
netbsduser has quit [Ping timeout: 248 seconds]
c0co has joined #osdev
fedaykin has quit [Quit: leaving]
fedaykin has joined #osdev
edr has quit [Quit: Leaving]
<Mutabah>
PublicWiFi: You don't really need "virtual drives". The simplest VFS is the unix unified filesystem model - you mount filesystems at specific paths
marv7000 has quit [Quit: Ping timeout (120 seconds)]
marv7000 has joined #osdev
arminweigl_ has joined #osdev
arminweigl has quit [Ping timeout: 276 seconds]
arminweigl_ is now known as arminweigl
marv7000 has quit [Quit: Ping timeout (120 seconds)]
MrBonkers has quit [Remote host closed the connection]
melnary has quit [Remote host closed the connection]
melnary has joined #osdev
karenw has quit [Ping timeout: 252 seconds]
GeDaMo has joined #osdev
MrBonkers has joined #osdev
goliath has joined #osdev
Matt|home has quit [Quit: Matt|home]
dotexe1337 has joined #osdev
Yoofie6464463823 has quit [Read error: Connection reset by peer]
Yoofie6464463823 has joined #osdev
Lucretia has joined #osdev
dotexe1337 has quit []
<kof673>
PublicWiFi, drives sounds like something dos or cp/m invented. disk -> partition -> filesystem maybe if you have a disk simulated inside a file like an iso then "virtual disk" maybe, but that is just a "backend"
<kof673>
to each their own, just where are you getting this terminology?
<kof673>
muddled terminology -> muddled thinking. just find some clear terms for whatever you want to do :D
<bslsk05>
'Miroslav Franc, Marcela Mašláňová, Nikolay Gueorguiev: s390x architecture at SUSE' by SUSE Labs
<_Heat>
there you go
<nikolar>
yeah i've seen taht video actually
<_Heat>
ok good
<_Heat>
there you don't go then
<nikolar>
yeah thanks _Heat
<_Heat>
you're welcome _Nikolar
<nikolar>
i am not a reserved identifier
<_Heat>
you're a typedef?
<_Heat>
typedef _Heat heat;
_Heat is now known as heat
<kof673>
/* TODO: ugly hack for backwards compatibility, fix later */ #define heat _Heat
<heat>
i don't remember that being in C11
c0co_ has joined #osdev
c0co has quit [Killed (NickServ (GHOST command used by c0co_))]
c0co_ is now known as c0co
<nikolar>
it wasn't, he's halucinating
<kof673>
c11 forbids defines? good thing i stay on c89
<heat>
no, that's C++11
<heat>
if you say #define in r/cpp you'll be shot on sight
<nikolar>
in r slash c preprocessor?
<nikolar>
that's odd
<pog>
you do with template trickery what we used to do with preprocessor shenanigans
<kof673>
i woudln't blame that on typewriters, and comments say not a C issue either, logic error in code, but butterfly effect maybe ;D https://github.com/acheong08/CVE-2025-48384
<bslsk05>
acheong08/CVE-2025-48384 - Breaking git with a carriage return and cloning RCE (10 forks/16 stargazers)
<kof673>
the commentary referred to typewriters though as where it came from lol
<heat>
hey that's not good
<heat>
this is my experts' opinion on this
<heat>
Not Good
<kof673>
it was just meant as all language is preprocessed :D just it is taken for granted/etc.
<pog>
peeprocess
<nikolar>
heat: you're not a git guy so your expert opinion is disregarded
<pog>
git gud
<Ellenor>
gits u
Turn_Left has joined #osdev
Left_Turn has quit [Ping timeout: 272 seconds]
<heat>
oh i'm a git alright
<nikolar>
you're alright, git
mrpops2ko has quit [Read error: Connection reset by peer]
mrpops2ko has joined #osdev
<Ellenor>
my brain is full of nonsense.
mrpops2ko has quit [Read error: Connection reset by peer]
<Ellenor>
I wonder how a DOS programme would, theoretically, detect the presence of a multi-core CPU.
<nikolar>
oh i thought that was Ermine
<nikolar>
lol
<Ellenor>
do we look that alike?
<zid`>
a dos program would have to write it itself, I'd guess
<nikolar>
your nicks start with capital e and they are the same color in my client
mrpops2ko has joined #osdev
<zid`>
unless there's a multicore dos out there somewhere
mrpops2ko has quit [Read error: Connection reset by peer]
<nikolar>
i kind of remember hearing about somthing like that existing
<heat>
Ermine: cpuid
<nikolar>
not sure if i just imagined it
<aaabbb>
/6/6
<Ellenor>
zid`, yeah, probably
* kof673
points at netware j/k i wonder about older versions though
<nikolar>
heat: it's not Ermine kek
<Ellenor>
heat, I don't think Ermine wants to know anything.
<heat>
nikolar: it's definitely ermine
<kof673>
at some point it was dos-based, and at some point it had smp, just not sure if those intersect
<nikolar>
heat: is it
<heat>
yeah
mrpops2ko has joined #osdev
Ellenor is now known as ELENORO
<ELENORO>
This better?
<nikolar>
that's a different color now
<ELENORO>
Also: Ermine is Russian and probably a guy, I'm Anglo-Canadian and a lady (or something that rounds to one).
<zid`>
Up or down?
<ELENORO>
nearest-neighbour
<kof673>
there were many dos variants, multi-user dos etc. just ms-dos and ibm and maybe dr-dos were possibly the 'big' ones
<aaabbb>
tr-dos
<zid`>
tr/dos/g
heat is now known as nikolarian
<nikolarian>
we ballin
<ELENORO>
vucking hell
<ELENORO>
is this the #osdev sense of humo(u)r?
<nikolar>
oh heat, that's plagiarism
<zid`>
for realsies though I wonder how hard it'd be to run like, multiseat dos, one dos per core
<nikolar>
or nikolarian rather
<zid`>
I bet most biosen are not infact, re-entrant though
<nikolarian>
they're not
<zid`>
so you'd have to wrap everything in exclusively dos syscalls
<nikolar>
they indeed aren't lool
<ELENORO>
zid`, i mean how would you like, gate hardware access, ensure that each dos could access hardware in a manner that wouldn't step on each other
<zid`>
you sort of wanna do that anyway just for the screen drawing
<zid`>
one MASTER DOS on core 0 that does the i/o, the rest get neutered
<aaabbb>
trying to make dos smp aware? lol
<ELENORO>
no aaabbb, trying to keep dos blissfully unaware of being run next to something
<ELENORO>
or not exactly blissfully, but mostly
<goliath>
*cough* VM86
<zid`>
might be easier to hyperdos
<ELENORO>
i mean maybe
nikolarian is now known as heat
<ELENORO>
I guess I'd need to write my own EMM implementations to blank out swaths of memory reserved by my nonsense
<ELENORO>
assuming that's even, possible
<ELENORO>
i don't even know what i'm saying
<ELENORO>
i just know that tricking the system will be hard.
<zid`>
tricking dos not to use various memory is the easy bit the hard part will be stopping it using the bios :P
<zid`>
you're basically just reimplementing half a hypervisor though
<kof673>
^ i just don't want to say it is impossible. in software...question is how much work is needed
<nikolar>
i wonder how weechat colors nicks
<nikolar>
heat's was the same color as mine when he was nikolarian
<heat>
i think they usually run a hash function over the name
<heat>
and color based on that
<zid`>
100% a hash yea
<nikolar>
ermine and ellenore, and nikolar and nikolarian are suspiciously close in color then
<kof673>
ermine means/is spotted, you need to watch more eyes wide shut j/k you walked right into that :D
<ELENORO>
zid`, yeah, BIOS functions will need to be overrode
<ELENORO>
which will not be easy
<zid`>
Piece of piss
<zid`>
install your own handler that checks for ax=820, if not, call the original handler
<zid`>
easier than doing it on say, windows
<zid`>
because you don't have to fuck with relocations