ChanServ changed the topic of #haiku to: Open-source operating system that specifically targets personal computing. | | Nightlies: | Bugtracker: | SCM: | Logs: | Matrix: | XMPP:
OscarL has quit [Remote host closed the connection]
Maya-sama has quit [Ping timeout: 480 seconds]
zard has joined #haiku
AlaskanEmily has joined #haiku
bradsco has joined #haiku
zard has quit [Ping timeout: 480 seconds]
DragonMaus has quit [Quit: - Chat comfortably. Anywhere.]
DragonMaus has joined #haiku
Maturi0n_ has joined #haiku
bradsco has quit [Quit: bradsco]
mmu_man has quit [Ping timeout: 480 seconds]
Maturi0n has quit [Ping timeout: 480 seconds]
tuaris has quit [Read error: Connection reset by peer]
tuaris has joined #haiku
bradsco has joined #haiku
HaikuUser has joined #haiku
HaikuUser has quit []
<pairisto[m]> how would I get something like tun.cpp to run as a driver? I think there is enough code for it to run as a driver and have the network/devices/tun/v1 appear when you run ifconfig but even if it doesn't I would still like to know how eventually
HaikuUser has joined #haiku
HaikuUser has quit []
bradsco has quit [Quit: bradsco]
<zdykstra> welp, fixing #14782 is beyond my BLayoutBuilder knowledge right now
wintp has quit [Quit: Connection closed for inactivity]
tsukasa has quit [Quit: It never truly ends...]
tsukasa has joined #haiku
<botifico> [haikuports/haikuports] korli pushed 1 commit to master [+1/-1/±0]
<botifico> [haikuports/haikuports] enzo1982 b098a08 - mac: bump to 9.20 (#7922)
<botifico> [haikuports/haikuports] korli pushed 1 commit to master [+1/-1/±0]
<botifico> [haikuports/haikuports] enzo1982 0116b5f - smooth: bump to 0.9.10 (#7923)
<botifico> [haikuports/haikuports] korli pushed 1 commit to master [+0/-0/±1]
<botifico> [haikuports/haikuports] korli 7b7cea6 - asciinema: rebuild with updated python3.9
AlienSoldier has quit [Quit: Vision[]: i've been blurred!]
Yonle has quit [Quit: See you later.]
Yonle has joined #haiku
Yonle has quit []
Yonle has joined #haiku
vdamewood has quit [Quit: Life beckons.]
DKnoto has quit [Ping timeout: 480 seconds]
DKnoto has joined #haiku
freddietilley has joined #haiku
<Habbie> i think my haiku crashed - i was building a port, went away, came back, debian was booted :>
<Habbie> anything i can do to investigate/debug?
MajorBiscuit has joined #haiku
Major_Biscuit has joined #haiku
MajorBiscuit has quit [Ping timeout: 480 seconds]
<botifico> [haikuports/haikuports] korli pushed 1 commit to master [+2/-0/±0]
<botifico> [haikuports/haikuports] Habbie 8e654e4 - wdiff: new port for v1.2.2 (#7919)
<Habbie> oh yesssss
smalltalkman has joined #haiku
<BarmenduChakraborty[m]> Whosoever fixed the search functionality of the Haiku API Docs, I am grateful
kikadf_ has quit [Remote host closed the connection]
mmu_man has joined #haiku
KapiX has joined #haiku
KapiX has quit []
mmu_man has quit [Ping timeout: 480 seconds]
Forza has quit [Read error: Connection reset by peer]
Forza has joined #haiku
AlaskanEmily has quit [Remote host closed the connection]
gouchi has joined #haiku
gouchi has quit []
kikadf has joined #haiku
zard has joined #haiku
<andreasdr[m]> Nice.
mmu_man has joined #haiku
woffs has joined #haiku
OrangeBomb has quit [Quit: Slacking off]
OrangeBomb has joined #haiku
hightower2 has joined #haiku
matt1 has joined #haiku
matt1 has left #haiku [#haiku]
zard has quit [Ping timeout: 480 seconds]
bradsco has joined #haiku
zard has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
zard has quit [Ping timeout: 480 seconds]
zard has joined #haiku
OscarL has joined #haiku
<OscarL> Habbie: Congrats on the PR merge! :-)
<Habbie> OscarL, thanks! did you see the PATCHES thing I missed?
<OscarL> yeah, my bad for not noticing, heh, I've just focused on the missing .patchset, and forgot .recipe counterpart :-D
<Habbie> :)
<Habbie> running the linter on github PRs would probably be neat
<OscarL> I thought it did?
<Habbie> hmm
<Habbie> i see it
<Habbie> it doesn't actually do anything though
<OscarL> Then something got broken :-(
<Habbie> looks that way
<OscarL> It used to work.
<Habbie> Checking ports of: wdiff-1.2.2
<Habbie> ok, on my PR it did do something
<Habbie> not on 7925 because it's a bump, not a new recipe
<Habbie> however, on my PR it did not notice the missing PATCHES
<OscarL> not sure who handles that part of the infrastructure on GitHub. kallisti5[m] or waddlesplash, I would assume.
<OscarL> Might be worth asking/telling them about that lint check missing things :-D
<Habbie> i'll see if i can investigate
<Habbie> also you just mentioned them so perhaps they'l see :)
<Habbie> +l
<OscarL> might be too early in the day for them, if I got their timezones right :-), so if they don't react later, creating a new issue on Haikuports about that seems reasonable.
<Habbie> ack
<Habbie> i'll check a few things before i do that
tuaris has quit [Read error: Connection reset by peer]
<waddlesplash> zdykstra: what don't you know about blayoutbuilder?
<waddlesplash> Habbie: OscarL: CI just runs --lint
<waddlesplash> of HaikuPorter
<waddlesplash> easily adjusted if we want to add new things
mmu_man has joined #haiku
<OscarL> waddlesplash: seems like when Habbie locally ran "hp --lint wdiff" it found a problem that the linter on Github failed to find (missing PATCHSET reference on the recipe).
<Habbie> ok
<Habbie> i have an update
<Habbie> Warning: Patch file wdiff-1.2.2.patchset is not referenced in PATCHES, so it will not be used
<Habbie> it did see it
<Habbie> it just didn't fail the job for it
<Habbie> so the problem is much smaller
<waddlesplash> that might be worth making an error instead of a warning
<waddlesplash> easy fix probably
<Habbie> right
<waddlesplash> if you know some Python you can look into it yourself :)
<Habbie> where would that go? in haikuporter?
<Habbie> i do know some Python sir :)
<Habbie> (or ma'am)
<OscarL> or robot...
<OscarL> judging for his production level :-D
<waddlesplash> find the message, then figure out what's the function for reporting errors instead of warnings, and adjust it accordingly
<Habbie> will do
<kallisti5[m]> fun fact: waddlesplash is actually ChatGPT
<kallisti5[m]> We just pay the AI to keep it motivated
<OscarL> :-)
<BarmenduChakraborty[m]> Hello OscarL
<OscarL> Hey there BarmenduChakraborty[m]!
<BarmenduChakraborty[m]> long time :)
<Habbie> is there a Matrix client for Haiku?
<OscarL> BarmenduChakraborty[m]: Yeah... I kept away for a while. Brain more broken than usual... oh well :-). Hope you're doing OK!
<BarmenduChakraborty[m]> I'm doing fine. How about you?
<waddlesplash> Habbie: I think at least one of the Qt ones is ported
<Habbie> ah, of course
<waddlesplash> kallisti5[m]: LOL
<waddlesplash> clearly my anti-AI stance is a cover for the real story :-p
<BarmenduChakraborty[m]> is that how AI is trying to take over humans eh waddlesplash ?
<andreasdr[m]> Nonono. Waddlesplash is taking over!!! :DDD
<win8linux[m]> <Habbie> "is there a Matrix client for..." <- Quaternion and NeoChat are Qt-based Matrix clients available for Haiku.
<kallisti5[m]> We really need a first-class native Matrix client
<Habbie> maybe Vision is a good start?
<waddlesplash> Vision is extremely hardwired to IRC
<Habbie> ah
Yonle has quit [Quit: See you later.]
<andreasdr[m]> Quaternion crashes unfortunatly here.
Yonle has joined #haiku
HaikuUser has joined #haiku
HaikuUser has quit []
<PulkoMandy> why don't you all just use XMPP? We have *two* native clients for that :)
<PulkoMandy> I guess could be adapted for Matrix as well, if libpurple supports that?
frkzoid has joined #haiku
<andreasdr[m]> No idea. Matrix and IRC work for me usually here.
<kallisti5[m]> XML mostly
<kallisti5[m]> I was a big fan of XMPP, but nobody uses it
<win8linux[m]> <kallisti5[m]> "We really need a first-class..." <- Wasn't there one developed during GSoC? Chat-o_Matic or something?
<win8linux[m]> Also, a native Mastodon/Fediverse client too.
<kallisti5[m]> win8linux: you know where these live in github?
<PulkoMandy> I just linked to it (but it's XMPP/IRC, not Matrix)
frkazoid333 has quit [Ping timeout: 480 seconds]
<win8linux[m]> s/o_Matic/o-Matic/
<kallisti5[m]> oof. Thanks :-)
<kallisti5[m]> we do have libmatrix
<kallisti5[m]> I ported it to haikuports a while ago
<kallisti5[m]> ah. y'all renamed it
<win8linux[m]> PulkoMandy: True, but C-o-M can use libpurple which does support Matrix.
<kallisti5[m]> oh.. libpurple supports matrix?
<kallisti5[m]> dang
<PulkoMandy> there's an unmaintained plugin as far as I can see
<kallisti5[m]> yeah. unmaintained
<kallisti5[m]> matrix
<kallisti5[m]> ok. going to reboot to haiku to play with it.
<win8linux[m]> Based on some of what JadedCtrl said in their last GSoC post though, it may be better to have a native Matrix add-on for C-o-M:
<win8linux[m]> Speaking of native clients for federated protocols, have there been any attempts at a native ActivityPub client?
<win8linux[m]> MS-DOS and Classic Mac OS IIRC have AP clients at this point.
<PulkoMandy> it's easier when you don't have to "hey I have to write the OS first" :D
<kallisti5[m]> Hm. Not in haikudepot
<kallisti5[m]> Doesn't build on modern gcc.. just silly things though
<zdykstra> waddlesplash: re: BLayoutBuilder - if you have a few minutes some time, can you sanity check my current understanding of how something is done?
<waddlesplash> srue
<waddlesplash> sure
<OscarL> what's the "etiquette" for "resolving" comments on Gerrit? I'm never sure if I'm supposed to mark them as such when addressed by a new patchset, or if that's for the original commenter to decide if it's actually resolved :-/
<waddlesplash> if you resolved the problem, mark it resolved
<waddlesplash> if it's not really resolved the original commenter can reopen
<OscarL> Ok. Thanks. I guess it is more nuanced for comments that are more question that code change suggestions, right?
<zdykstra> waddlesplash: so for, is being added to an existing group at and each item has the same weight so they both take up 50% of the group ?
<waddlesplash> OscarL: yes
<waddlesplash> zdykstra: no, I don't think so
<waddlesplash> honestly AddChild should not be used in layout mode
<win8linux[m]> <PulkoMandy> "it's easier when you don't..." <- Rather sure that SerenityOS has an AP client too.
<zdykstra> okay, so my understanding is wrong. That's what I thought :)
<win8linux[m]> * client too. :D
<waddlesplash> zdykstra: the second parameter is "after"
<waddlesplash> err sorry. "before"
<waddlesplash> it's adding the specified view *before* the other one
<win8linux[m]> In theory, what kits would a native Haiku client use?
<waddlesplash> zdykstra: so actually your understanding is mostly correct I suppose
<waddlesplash> there's more items in the group than just those 2 though
<waddlesplash> and like I said, imho AddChild shouldn't be used in layout mode, instead you should add items to the layout directly
<zdykstra> so layouts can be appended at runtime?
<waddlesplash> yes, why wouldn't they be?
<waddlesplash> layouts aren't anything special
<PulkoMandy> the same weght would lead to 50% of the group if there are no other constraints. But usually each view has a minimal or a preferred size that the layout system will try to satisfy as well
<PulkoMandy> and the weight is used when all other constraints were not enough or too much, and the last resort is to distribute the remaining space to all views, wether they want it or not
<zdykstra> thanks for the input waddlesplash and PulkoMandy
<zdykstra> you've given me some direction to go on fixing this
bjorkintosh has quit [Quit: Leaving]
freddietilley has quit [Quit: WeeChat 3.8]
nosycat has joined #haiku
bjorkintosh has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
<zdykstra> so I was thinking for backups that I'd create a ~10GB or whatever image file, put BFS on it, mount it and then rsync key directories in to it, unmount it, and then rsync it to one of my systems with ZFS where it'll land in my snapshots. The followup rsyncs, both in to the image and to the ZFS host, shouldn't be too bad.
<zdykstra> I'm so used to having ZFS on all of my systems that replicate snapshots to a central host - I feel naked just having a bare nvme with Haiku on it
* OscarL on the other hand, only ever made a couple of backup CDs from his old BeOS days.
<OscarL> HDDs failures are met with a "damn it!" followed by a "oh, well... less stuff to organize, at least" :-P
mmu_man has joined #haiku
<zdykstra> I found my BeOS backup CDs a few years ago - pretty sure that's actually where I pulled the ffmpegGUI source from
<zdykstra> it might have been in the wild before then, I don't remember
<zdykstra> I'm less concerned about drive failure with an nvme, and more concerned with accidentally deleting something and having no way to recover it
<zdykstra> on my workstation, I take ZFS snapshots every 5 minutes of my home directory that are replicated to another machine
mmu_man has quit [Ping timeout: 480 seconds]
BrunoSpr has joined #haiku
<BrunoSpr> hi all
<nosycat> Hello!
<OscarL> Hola
michel has joined #haiku
KapiX has joined #haiku
<Habbie> so, hp --lint has warn() and sysExit()
<Habbie> warn() does not cause it to exit 1
<Habbie> sysExit() does - immediately
<Habbie> this will need some minor refactoring
<zdykstra> you know, I wonder if it'd be better to run Haiku in a VM, then rsync my Haiku machine to the VM, and then just snapshot the VM disk
<OscarL> Habbie: seems like --lint error MO is to give up as soon as it finds an error?
<Habbie> well, it would be nice to show all that is wrong, if possible
<Habbie> what you say would work too, but feels a bit like the easy way out
michel has quit []
smalltalkman has quit []
<OscarL> Is there any distinction on "hard errors", like... "this doesn't even parses as a shell script" (because for those, surely continuing sounds preposterous)
gouchi has joined #haiku
<OscarL> (LOL @ me using "big words" with my crappy "English" :-P)
<Habbie> :D
<Habbie> ah! i thought lint would take multiple package names, but it does not
<Habbie> so fatal errors already abort early now
<Habbie> ok, then i'll take the easy way out
ClaudioM has joined #haiku
<Habbie> waddlesplash, do you want CI to also lint recipe updates? currently it only lints new recipes
<waddlesplash> yes, it should
<Habbie> ok
<Habbie> i'll have a look :)
<waddlesplash> it should lint anything found in recent commits
<zdykstra> what's the haiku equivalent of a cron job?
<waddlesplash> probably a logic error in here
<Habbie> saw that
<Habbie> ack
tuaris has joined #haiku
<Habbie> shall I also move that script into .github? it's no use outside of it
KapiX has quit [Quit: KapiX]
Major_Biscuit has quit [Ping timeout: 480 seconds]
Maya-sama has joined #haiku
OscarL has quit [Remote host closed the connection]
kinkinkijkin is now known as Guest6966
kinkinkijkin has joined #haiku
OscarL has joined #haiku
<OscarL> zdykstra: haven't used it, but pkgman shows "cronie" as "a cron daemon".
<OscarL> not sure if Haiku proper has something.
<zdykstra> yeah - I was hoping there was a Haiku-native way. I haven't seen anything in the Haiku user guide though.
Guest6966 has quit [Ping timeout: 480 seconds]
<zdykstra> I suppose I could just make my own job, that shouldn't be too hard
<OscarL> write a deamon that reads its taks from file attributes, so you can edit them with Tracker? :-P
<OscarL> s/taks/tasks/
<zdykstra> that's an interesting idea
<zdykstra> but I'm looking for quick-and-dirty, now that my PoC seems to work
<zdykstra> rsync to an image, the rsync the image to a remote host. Subsequent rsyncs of a 10GB image file have an effective re-transfer rate of 300MB/sec.
<OscarL> zdykstra: maybe one of those old BeOS packages still works/compile?
<OscarL> there was "BeTasks 0.9 - sheduller with GUI-setup", but doesn't has source code :-(
<zdykstra> looks like cronie will do it
mmu_man has joined #haiku
<kallisti5[m]> Ok. Submitted a few minor fixes for chat-o-matic. Let's see if students still around
<zdykstra> nice
<zdykstra> hmm. I can actually just rsync files straight to ZFS, when extended attributes are enabled. getfattr shows that all of the attributes on a file were copied over, and rsyncing it back preserved them.
tqh has joined #haiku
<zdykstra> Anybody know off the top of their head the maximum data size of a BFS attribute?
Haikunaut has joined #haiku
chuggy has joined #haiku
<OscarL> I remember one prank "magic compressor" back in the day... reduced your files to zero bytes... by storing the full content as an attribute. If that's still possible, I would assume same max size of files in BFS, right?
<zdykstra> Oof. Max data size of extended attributes on Linux is 64k.
Haikunaut has quit [Remote host closed the connection]
<OscarL> Here's a nice article about BFS I'm scanning to see if it explicitly mentions the limit: (it does mentions some data structures, might be enough?)
kallisti5 has joined #haiku
kallisti5 has quit [Remote host closed the connection]
<OscarL> zdykstra: in any case, better ask one of the actual devs (or someone reading with some sources :-D)
kallisti5 has joined #haiku
kallisti5 has quit [Remote host closed the connection]
<pairisto[m]> how would I get the tun.cpp to run as a driver? I think there is enough code for it to run as a driver and have the network/devices/tun/v1 appear when you run ifconfig but even if it doesn't I would still like to know how when there is enough code eventually
kallisti5 has joined #haiku
kallisti5 has quit [Remote host closed the connection]
<waddlesplash> Habbie: yes, probably it should be moved, we didn't have .github when I made the script
<waddlesplash> zdykstra: only 64k on extfs
<waddlesplash> XFS supports larger attrs
nosycat has quit [Quit: Leaving]
HaikuUser has joined #haiku
HaikuUser is now known as choulth
<choulth> hi there
<zdykstra> hola
kallisti5 has joined #haiku
kallisti5 has quit [Remote host closed the connection]
mmu_man has quit [Ping timeout: 480 seconds]
choulth has quit [Quit: Vision[]: i've been blurred!]
<botifico> [haikuports/haikuports] korli pushed 3 commits to master [+0/-0/±6]
<botifico> [haikuports/haikuports] korli 6a86ae3 - python38: add sysconfig haiku schemes
<botifico> [haikuports/haikuports] korli da07c7b - python3.7: add sysconfig haiku schemes
<botifico> [haikuports/haikuports] korli 01a50ad - python3.10: default haiku schemes
kallisti5 has joined #haiku
kallisti5 has quit [Remote host closed the connection]
kallisti5 has joined #haiku
MrSunshine_ has joined #haiku
kallisti5 has quit [Remote host closed the connection]
<OscarL> Mmm, I hope korli's change to Python 3.10 fixes (or improves) (I couldn't keep up focus when attempting to fix that one :D)
MrSunshine has quit [Ping timeout: 480 seconds]
OscarL has quit [Remote host closed the connection]
mmu_man has joined #haiku
DKnoto has quit [Ping timeout: 480 seconds]
OscarL has joined #haiku
<OscarL> pairisto[m]: I'm not of much help (due to my lack of skills) but maybe comparing that tun.cpp file against src/add-ons/kernel/network/devices/ethernet/ethernet.cpp can give you some clues?
DKnoto has joined #haiku
<pairisto[m]> I am currently trying to add it to the build path and recompiling it to see if it actually appears in Haiku itself and with that I can maybe do something like ifconfig /dev/net/tun create? The documentation is fuzzy on how to actually add a driver to /dev
<pairisto[m]> unless I am just reading it wrong
<pairisto[m]> * OscarL: I am currently trying to add it to the build path and recompiling it to see if it actually appears in Haiku itself and with that I can maybe do something like `ifconfig /dev/net/tun create`? The documentation is fuzzy on how to actually add a driver to `/dev`
<zdykstra> should be able to add the build artifact to /boot/home/config/non-packaged/add-ons/kernel/drivers/dev
<zdykstra> (that
<zdykstra> 's just a WAG though, I've never done driver development)
<zdykstra> be prepared for KDL, though
<OscarL> This is a basic example of a "test" driver (using the older driver API) that actually publishes devices under "/dev" :
<pairisto[m]> do you know how you would make it a character driver since thats apparently what haiku wants for a network driver? (I ask because the ethernet driver is represented in haiku as a character driver)?
<pairisto[m]> * character driver?)
<pairisto[m]> * do you know how you would compile it as a character driver since thats apparently what haiku wants for a network driver? (I ask because the ethernet driver is represented in haiku as a character driver?)
<pairisto[m]> zdykstra: fair enough
<OscarL> <<< this one uses the newer API to also publish things under /dev
<botifico> [haikuports/haikuports] korli pushed 2 commits to master [+2/-2/±4]
<botifico> [haikuports/haikuports] korli 13a6cbe - python packages: rebuild to install directly as vendor-packages
<botifico> [haikuports/haikuports] korli 9dd78e2 - sip: also build with python 3.9
zard has quit [Quit: leaving]
<OscarL> pairisto[m]: notice that there seems to be a distinction between "drivers" (that publish "devices") and "modules", that can be used by other modules or by the drivers to help them do their job.
<OscarL> (that's my crude undertanding of that, at least)
<OscarL> I think that tun.cpp is a "module" and I don't know if those publish things under /dev (maybe under the newer API they can?).
<pairisto[m]> then wouldn't something like loopback.cpp also be a module?
<OscarL> does it publish under /dev?
<pairisto[m]> I believe so
<pairisto[m]> how did I never see that smh...........
<pairisto[m]> so would I have to include this in the `tun.cpp` "module"?
<pairisto[m]> or could I just call the driver itself?
<OscarL> You should use the API that's available for that.,,,
<OscarL> see the get_module() functions for example.
<OscarL> for example (from the poke.cpp driver I wrote LOOOOONG ago):
<OscarL> "if (get_module(B_PCI_MODULE_NAME, (module_info**)&pci) < B_OK) {"
<OscarL> that tries to get the PCI kernel module, so you can then access it from that "pci" variable.
<OscarL> accessing functions from said module like this: pci->read_pci_config() and so and so.
<OscarL> said modules have their interface available either in a publich header file (like "#include <PCI.h>"), others have them on "private" headers.
<OscarL> that you can still can access, after massaging a bit the jamfiles :-)
<pairisto[m]> in tun.cpp it has this:`get_module(NET_STACK_MODULE_NAME, (module_info**)&sStackModule);` but because `NET_STACK_MODULE_NAME` isn't defined, it wouldn't open anything right?
<OscarL> You can use that site to search the code for things that seems to not be there :-)
<OscarL> That NET_STACK_MODULE_NAME seems to be defined here:
<pairisto[m]> thank you for that! okay so it is defined but not to a name that would be useful
<pairisto[m]> in a tun/tap driver context
<OscarL> again, that seems to be a "module" name, not one for a "device" that will be published under /dev
<pairisto[m]> ah got it
<OscarL> there that acpi_thermal driver will publish under:
<OscarL> /dev/ + .... #define ACPI_THERMAL_BASENAME "power/acpi_thermal/%d"
<OscarL> (sorry for the piss poor formatting)
<pairisto[m]> you're all good!
<OscarL> Drivers using the older API (the one I'm a bit more familiar with)... had to define specific functions, such
Blendie has quit [Quit: Connection closed for inactivity]
<OscarL> The aptly named "publish_devices()" function :-D
KapiX has joined #haiku
<OscarL> As usual when I *dare* to offer some "help" (ha! that's a good joke!) is in hopes that if I err too much, more experienced/knowledgeable folks will chime-in to set me straight, and we can learn in the process.
<pairisto[m]> lol, so would I not have to exactly use tun.cpp if I were trying to import something like wireguard over and just use tun/driver.c directly?
<pairisto[m]> that is the ideal but your help is helping me understand a little better bit by bit
<OscarL> (while also making those experienced folks' blood boil a little for having to deal with my dumbness).
<pairisto[m]> lol
<OscarL> I can't really comment on your last question. I feel I've already stretched too much the little I know. Better quit when I'm "ahead" :-D
<botifico> [haikuports/haikuports] korli pushed 1 commit to master [+0/-0/±1]
<pairisto[m]> fair enough, I thank you for the help though
<botifico> [haikuports/haikuports] korli fe8f8e1 - pyqt: move to python 3.9
<OscarL> np!
ClaudioM has quit [Quit: leaving]
<OscarL> pairisto[m]: just in case... there are plenty of things in the haiku source repo that are not present on the images. Like for example, the mentioned acpi_thermal.c driver (and lots of others).
<OscarL> that can be because those are considered unfinished, or nothing else uses them (like the acpi_lid driver)...
<pairisto[m]> I have learned that the hard way and have found it sorta frustrating but I understand why that is
<OscarL> those you need to "jam -jN <target_you_want>" (eg: jam -jN acpi_thermal) and then move the resulting binary from the "generated/...../" folder, to the appropriate location...
<pairisto[m]> THANK YOU! I needed that
<pairisto[m]> * needed that information
<OscarL> either under "/system/non-packaged/add-ons/kernel/..." or under "~/config/non-packaged/add-ons/kernel/..."
<OscarL> pairisto[m]: sometimes you'll have a hard time figuring out what the target is called... don't try to guess it, just open the jamfile in the folder of the target you want...
<OscarL> that file contains the target name.
<pairisto[m]> got it
<OscarL> for example, the mentioned "test" driver...
<OscarL> I doubt using "jam test" will do you any good :-D
<OscarL> the correct name for that one is:
<OscarL> "jam <driver>test"
<pairisto[m]> it wouldn't have the extension after it right?
<pairisto[m]> like .c
<OscarL> I haven't seen targets with extensions.
<pairisto[m]> * like .c
<pairisto[m]> ok just making sure
BrunoSpr has quit [Remote host closed the connection]
KapiX has quit [Quit: KapiX]
<OscarL> Also of note, some drivers that go under "add-ons/kernel/drivers/bin", and you need to symlink them to the appropriate subdir of "add-ons/kernel/drivers/dev/" (depending on if the are net drivers, graphic drives, etc, etc).
<OscarL> That was the case for the drivers that use the older API at least. Not sure about the newer one.
<nekobot> [haiku/haiku] davidkaroly pushed 1 commit to master [hrev56809] -
<nekobot> [haiku/haiku] e490b6343abd - kernel/arm64: align interrupt postlude with other architectures
bradsco has quit [Quit: bradsco]
<pairisto[m]> do you know what "bone_tun.h" is supposed to be? I tried looking it up on OpenGrok but its just defined in the `tun/driver.c` and just isn't a file
<OscarL> acpi_thermal... I just placed it under add-ons/kernel/drivers/power, with no symlink so... appears that's a difference.
<OscarL> mmm BONE was an experimental networking API for BeOS.
<OscarL> That may indicate that that tun.c driver was written for BeOS and not Haiku.
<OscarL> (I mean... written ON BeOS, with the intention of it working one day on Haiku)
<pairisto[m]> well then I might want to update that
<OscarL> Lots of stuff accumulate and get a bit stale in a project of over 20 years :-D
<OscarL> One more thing that WILL byte you in the rear...
<zdykstra> I got a good laugh last night - I found an ifdef for DANO
bradsco has joined #haiku
<zdykstra> I remember when that hit BeShare / IRC back in the day. It was pretty exciting to run that.
<pairisto[m]> I think I could possibly replace some of the bone_tun.h stuff with the net_ libs
<OscarL> when working on drivers that use the old API... you can basically overwrite them with a new binary you just compiled... the newer code will be loaded up without the need for a reboot.
<OscarL> No such luck with the drivers that use the newer API. you HAVE to reboot for the changes to get picked up (otherwise, the old binary still gets used, and you get confused AF).
<pairisto[m]> makes sense
<OscarL> pairisto[m]: Dano was a development version of BeOS 5.1 that got leaked. It included the mentioned BONE networking stuff.
<OscarL> (among other improvements/changes)
<pairisto[m]> did it ever release?
<pairisto[m]> nrm
<OscarL> So, being seen as where BeOS was headed before imploding, some parts of it was taken as inspiration.
<pairisto[m]> didn't see the word leaked
<zdykstra> if memory serves, the build date on the kernel was the morning of the last day of Be Inc.
<OscarL> I was about to say 5 Nov 2001... but it was 15 Nov 2001, apparently:
bradsco has quit [Quit: bradsco]
<Habbie> where does the haiku tcp/ip-stack come from?
<PulkoMandy> we wrote it
<Habbie> ohh
<Habbie> nice
<Habbie> waddlesplash, found the logic error that skips over skipping changed recipes :D
HaikuUser has joined #haiku
bradsco has joined #haiku
HaikuUser has quit [Quit: Vision[]: i've been blurred!]
<Habbie> is binutils always installed?
<Habbie> or should i just list it in my port prereqs?
<OscarL> plenty of recipes ask for "cmd:ld" for example in their BUILD_PREREQUISITES, Habbie.
<Habbie> ah good
<Habbie> so by cmd, that makes even more sense
<Habbie> then people can swap out implementations if they like
<botifico> [haikuports/haikuports] korli pushed 1 commit to master [+0/-0/±1]
<botifico> [haikuports/haikuports] korli c80442d - dbuspython: build for python 3.9
<OscarL> have you configured the, really usefull "inrecipe()" and "inpatch()" helper functions in your bash profile, Habbie? they can be really handy when working with HaikuPorts.
<botifico> [haikuports/haikuports] korli pushed 1 commit to master [+0/-0/±1]
<botifico> [haikuports/haikuports] korli 7e52688 - pyqtwebengine5: build with python 3.9
<Habbie> i have configured them but have not used them
<Habbie> let me see
<OscarL> (was too slow with that link I guess :-D)
<Habbie> ack
<OscarL> I did, for example: > inrecipe "cmd:ld"
<OscarL> to be able to answer your question.
<Habbie> right, i did 'git grep binutils' in haikuports
<OscarL> (regarding binutils)
<Habbie> so the real problem was thinking of the right question!
<Habbie> (like cmd:ld instead of binutils)
<Habbie> but yes, these helpers are nice
<OscarL> yeah, you rearely will think of packages, but what you need (a cmd, a lib), welp... except for _devel packages, I guess :-P
* Habbie "inrecipe GPL"
<Habbie> ack
<Habbie> slight change of habit from other OSes i package for
<Habbie> many don't even have convenient cmd: handles on packages
<OscarL> seems there are two versions of the suggested "helpers":
<Habbie> i took mine from haikuports-sample.conf i think
<OscarL> I use a slightly modified version of the latter (excluding the haikuports/{repository,packages} dirs to help my slow HDD)
<Habbie> right
<Habbie> i bought this SSD a month ago so i'm good ;)
<OscarL> I even have to use "commit.status=false" on git (for the Haiku and Haikuports repos at least) to help with the slowness :-D (thanks to jessicah for the tip!!!)
<Habbie> Warning: POLICY ERROR: Invalid top-level package entry "share"
<Habbie> well, this will be educational
<OscarL> After korli's changes to Python 3.10.... first smoke test of "pip3.10 install pyserial" seems to work! Nice!
<OscarL> "pip3.10 uninstall pyserial" worked too. This is promising.
<botifico> [haikuports/haikuports] korli pushed 2 commits to master [+0/-0/±2]
<Habbie> ohh
<botifico> [haikuports/haikuports] korli 1e303b8 - calibre: build with python 3.9
<Habbie> that reminds me that i wanted to port 'tio'
<botifico> [haikuports/haikuports] korli b319c0d - qutebrowser: build with python 3.9
<Habbie> OscarL, what are you using pyserial for?
<OscarL> And... "pip3.10 install --user pyserial" is still broken (installs to /boot/home/.local/{bin,lib}), but I think I can fix that far easier than the previous issue korli has taclked.
<OscarL> Habbie: attempting to understand what was going on with my serial_mouse driver.
<Habbie> ah
<OscarL> managed to find and fix at least two bugs (on on the serial driver, one on the tty layer)... but there are still problems with the serial driver that prevents me to progress further on fixing that darn mouse driver :-D
<Habbie> like, an rs232 mouse?
<OscarL> yes.
<Habbie> nice
* OscarL is still using a PS/2 ball mouse, that's able to do serial via a simple adaptor.
<Habbie> :)
<OscarL> I lost track of how many times I've changed its microswitch.
<Habbie> single?
<OscarL> *microswitchs
<OscarL> :-D
<OscarL> hey! it is old, but has 3 buttons. (I alternate with another that also has TWO wheels :-D)
<Habbie> :)
<zdykstra> I'm on an Elecom HUGE these days. The trackball space is suprisingly limited compared to regular mice.
<OscarL> Had to make that to use both wheels on BeOS :-D
<zdykstra> huh, neat
<OscarL> Good thing the API was already there with "x vs y" wheels!
<zdykstra> I went to college with the guy that created the original BeBits. I saw a guy wearing a BeOS shirt during finals, and it surprised me so much I went to talk to him.
<OscarL> oh, nice! :-D
<Habbie> OscarL, ohh, do you still have the source for that?
<Habbie> because i asked about wheel direction here and somebody suggested i could build a filter
<OscarL> Habbie: heh.
<Habbie> assuming that i shouldn't be using some newer APIs for that
<OscarL> Yeah... it happens to be on one of the few backups CDs I ever made (and the ones I've mentioned earlier to zdykstra :-P)
<OscarL> Will have to dig it up, and upload it as-is to github, I guess.
<Habbie> :)
* Habbie uses freshly built pkgdiff to check changes in pkgdiff port
* Habbie submits PR
<OscarL> Habbie: (excuse the cringe-worthy code and Readme.txt... sins of the young! :-D)
<OscarL> If all you want is to invert the scroll wheel, you'll expend more time deleting code from there than anything else.
<Habbie> thanks! stored to notes
<Habbie> my note says "inspiration, check if APIs are old"
<OscarL> It works on Haiku.
<Habbie> and i guess *.sh would become a .recipe these days
<Habbie> ok
<Habbie> oh it has toggle_wheels
<OscarL> not sure if that exact version I just pushed, but pretty sure I still have it installed on one of my test installs :-)
<Habbie> ack :)
<OscarL> Can't upload the original .zip file tho, and the install scripts won't work (those are for BeOS).
<OscarL> *Can't upload it right now (Web+ is not collaborating).
<Habbie> sorry, i meant, it has invert_vertical :)
tqh has quit [Quit: Leaving]
<OscarL> The code is more complicated than it should, because I was attempting to making it (possibly) work with other mice than mine :-D
<Habbie> ack :)
<OscarL> most of the crap is trying to be general in the what wheel movement translates to what.
<OscarL> (when it was pretty fixed for my mouse)
<Habbie> :)
<OscarL> Mmm, seems I uploaded the version that compiles on Haiku already (and forgot to .gitignore a bunch of files :-P)
<Habbie> haha
<botifico> [haikuports/haikuports] korli pushed 3 commits to master [+2/-1/±1]
<botifico> [haikuports/haikuports] korli e6786b5 - markups: bump version, depend on markdown-math
<botifico> [haikuports/haikuports] korli c0fe8cb - markdown-math: new recipe
<botifico> [haikuports/haikuports] korli 830b451 - retext: build with python 3.9
<botifico> [haikuports/haikuports] korli pushed 1 commit to master [+0/-0/±1]
<botifico> [haikuports/haikuports] korli 6437065 - pandas: remove python 3.7
<OscarL> "- Invert vertical and/or horizontal wheels movement." heh, I didn't even remembered that :-D
<Habbie> :)
gouchi has quit [Remote host closed the connection]
<Habbie> what, no port for 'screen
<Habbie> '
<zdykstra> there's tmux
<Habbie> yeah, i actually needed something to talk to serial :)
<Habbie> for all other screen purposes, i do use tmux
<Habbie> hmm screen -is- in haikuports
<Habbie> ARCHITECTURES="?all !x86_gcc2"
<Habbie> SECONDARY_ARCHITECTURES="?x86_gcc2 x86"
<Habbie> ok
<Habbie> any recommended serial terminal clients?
<OscarL> SerialConnect?
<Habbie> that does nothing, which probably means a window appeared
<Habbie> (i'm not physically at my haiku desktop)
<OscarL> ah, I forget you're not using the GUI :-(
<OscarL> I would say pyserial-miniterm, but that's more of a test app.
<Habbie> :D
<Habbie> SerialConnect works
<Habbie> (the desktop is only a meter away but it means getting up and i'm old ;) )
<OscarL> (you can do "pkgman search pyserial" to see for what versions it is available)
<Habbie> how does SerialConnect know that /dev/ports/usb0 is serial?
<OscarL> I think all /dev/ports are assumed to be serial ports?
<Habbie> right
<Habbie> no by-id symlinks as on linux/udev i suppose?
<phschafft> isn't any kind of character device a serial device?
<Habbie> KERN: dosfs error: claims 1 fat tables
<Habbie> Last message repeated 1 time
<Habbie> KERN: dosfs error: failed to initialize volume
<Habbie> fun
<Habbie> (likely not a haiku bug)
<Habbie> phschafft, hmm, i suppose so!
<OscarL> phschafft: gets complicated with "line discipline", tty, modem status, etc, etc , I guess :-)
<Habbie> wow, haiku has a btrfs driver?!
* OscarL still has mild "pstd" after trying to understand termios/tty/serial interactions :-/
<phschafft> OscarL: they may all have different capabilities, physical interfaces and whatsnot. but in the end they are all serial devices.
<Habbie> oh i don't actually have btrfs partitions on this box
<Habbie> and the linux ext[234] partitions are hidden inside LVM
* OscarL cats audio.wav to /dev/dsp, serially, nodding to phschafft.
<phschafft> if you cat it, make sure it's purrr.wav ;)
<OscarL> :-D
<Habbie> a quick grep of the ports tree suggests no cli serial client is actually present
<Habbie> ah, except for minicom!
<Habbie> ah, doesn't say "serial" anywhere
<phschafft> screen?
<Habbie> minicom is not entirely happy
<Habbie> phschafft, i -think- my understanding is that the port is not enabled for x86_64
<OscarL> Try with ARCHITECTURES="all !x86_gcc2" and submit a patch if it works :-D
<Habbie> ack
<Habbie> what does ? mean in those?
<OscarL> "untested"
<Habbie> ah
<OscarL> ! is disabled
<Habbie> then i wonder why screen-4.6.1 is not built for x86_64
<OscarL> because the buildmaster is not configured to build untested packages.
<Habbie> clear :)
* Habbie "hp screen"
<Habbie> Warning: skipping screen-4.99.0~git, as it is untested on the target architecture.
<Habbie> Warning: skipping screen-4.6.1, as it is untested on the target architecture.
<Habbie> not just the buildmaster then
<OscarL> you can change that in your hp config, yes, but that's why I suggested removing the ? and trying to build locally.
<Habbie> ack
<Habbie> did you mean ?all x86_64 ?
<Habbie> ok, 4.6.1 has problems not related to architecture it seems
<OscarL> ARCHITECTURES="all !x86_gcc2" should make it build on 64 bits.
<Habbie> right, but might not be what I should PR
<Habbie> Error: Downloading from unsafe sources is disabled in haikuports.conf!
<Habbie> this is a ride
<Habbie> i'll look at it later :)
<zdykstra> might be time to get up and walk over to your haiku machine ;)
<Habbie> that won't change these things ;)
<Habbie> and i already confirmed SerialConnect works :)
<OscarL> I guess it is complaining because the source of the source code is a "git://" URI and not an https:// one?
<Habbie> maybe
<Habbie> but it contains a git hash
<Habbie> so it feels safe
<Habbie> but, i can only shave so many yaks in one evening
<OscarL> but there's no way to CHECKSUM_SHA256 to compare the download to.
<OscarL> s/way//
<Habbie> right
<OscarL> gah... I can't type anymore.
<Habbie> any verification would be on the wrong layer for hp
* Habbie zzz
* OscarL signs off too.
<OscarL> Later folks!
OscarL has quit []
<zdykstra> seeya, Habbie, OscarL
vdamewood has joined #haiku
netpositive has quit [Ping timeout: 480 seconds]