xenos1984 has quit [Read error: Connection reset by peer]
cloudowind has quit [Ping timeout: 255 seconds]
xenos1984 has joined #osdev
netbsduser` has joined #osdev
grumbler has quit [Quit: Leaving]
grumbler has joined #osdev
orccoin has quit [Ping timeout: 250 seconds]
kneskade has quit [Remote host closed the connection]
Left_Turn has joined #osdev
Turn_Left has quit [Ping timeout: 240 seconds]
stolen has joined #osdev
agent314 has joined #osdev
agent314 has quit [Ping timeout: 248 seconds]
agent314 has joined #osdev
agent314 has quit [Client Quit]
<netbsduser`>
just having a look at the UDI specs out of curiosity
<netbsduser`>
this thing is quite mad
pg12 has quit [Remote host closed the connection]
<Mutabah>
quite
<Mutabah>
but, it's quite well thought out to not make assumptions about the system
pg12 has joined #osdev
<netbsduser`>
Mutabah: yes, as far as generic goes, i couldn't possibly imagine anything more so
<netbsduser`>
the original backers of it are a who's-who of big vendors of the 90s as well, which makes me wonder why it never arrived in any commercial product other than UnixWare
heat has joined #osdev
goliath has joined #osdev
<heat>
the solaris struct page was huuuuuuuuuuuuuuge
<heat>
the structure according to the book is 160 bytes
<Mutabah>
netbsduser`: at a punt, it was becuase it didn't get enough buy-in from the really big names to make it worth using as a primary target
<Mutabah>
maybe also because it required almost open-source drivers?
<Mutabah>
I think? fuzzy memories, it's been a long time since I implemented it
<netbsduser`>
Mutabah: i did read somewhere that a lot of OS vendors trashed it as something that would defeat their competitive advantage of having lots of drivers written for them
<Mutabah>
that makes sense
<netbsduser`>
and we all know what gnu stallman's opinions were on the matter
<netbsduser`>
heat: you think that's bad, tru64's was 192 bytes
<netbsduser`>
i think windows' lpc might have resembled doors at one point possibly
<heat_>
we already have that on freebshitd
<heat_>
ChavGPT, why?
<ChavGPT>
oh it's "we" now?
<netbsduser`>
but now it's asynchronous which is an interesting development (opposite of the usual trajectory)
<ChavGPT>
contenst was questionable already for the state from the 90s
<ChavGPT>
and it was not updated for the most part
<ChavGPT>
for the second edition released aroudn 2010
<netbsduser`>
anyway i can't be dealing with the C style they use on windows
<ChavGPT>
it's basically bogus
<CompanionCube>
heat_: that has 'we ported mach stuff and launchd to freebsd for reasons' vibes
<heat_>
nooooooooooo
<heat_>
mach stuff and launchd is a whole other vector of shithousery
<heat_>
this is the solaris lovers' corner
<netbsduser`>
CompanionCube: the horse bolted on that one over 3 decades ago when 4.4bsd imported mach vm
<CompanionCube>
netbsduser`: no i meant e.g. this ': The TrueOS fork of FreeBSD 10 has launchd running as init and a JSON-aware launchctl utility, along with notifyd, libdispatch and ASL integrated. This work has also been forward-ported to FreeBSD -CURRENT. FreeNAS 10, which is also based on FreeBSD 10.1, will be using launchd and a host of other tools ported from OS X / iOS. It has used the original, and latest, Apple
<CompanionCube>
sources and ported them along with MACH IPC. '
<netbsduser`>
CompanionCube: and now trueos is gone
<netbsduser`>
i know hubbard was very keen on this
<CompanionCube>
yup, aren't they a linux distro now?
<netbsduser`>
that FreeBSD X initiative
<netbsduser`>
i think they did try to spin off a linux distro but i can't find any mention of it now
<heat_>
trueos is one of the operating systems of all time
<gog>
hi
* ChavGPT
high fives gog
<ChavGPT>
ix systems is moving away from freebsd
<CompanionCube>
oh?
<ChavGPT>
at least a year now
<ChavGPT>
they have a zfs nas on linux
<ChavGPT>
the one on freebsd is now legacy
* gog
prr
<zid>
I believe the response is 'owo'
SGautam has quit [Quit: Connection closed for inactivity]
netbsduser has joined #osdev
netbsduser has quit [Ping timeout: 240 seconds]
<heat_>
ChavGPT, bruv u familiar with the linukz vfs path for write()?
<ChavGPT>
nope
<heat_>
rip in pieces
<heat_>
these fuckin codepaths are confusing
<heat_>
and locks and shit
<ChavGPT>
:d
<heat_>
and in theory there's a possibility for something cool to happen, where writes that are restricted to a single folio on Some Filesystems(tm) could just lock the folio and be done with it
<heat_>
so you would *not* need O_DIRECT to unserialize writes
vdamewood has quit [Quit: Life beckons]
grumbler has quit [Quit: Leaving]
Left_Turn has quit [Read error: Connection reset by peer]