duncsauce has quit [Read error: Connection reset by peer]
MisthaLu has joined #haiku
akashkumar has joined #haiku
<akashkumar>
is there a way to see entire history of commands i put on terminal ?
<phschafft>
if you're using bash you can use: history
<phschafft>
hope it is what you're looking for. sadly I need to hit the road now. see you later!
MisthaLu has quit [Quit: Leaving]
akashkumar7902 has joined #haiku
<akashkumar7902>
I get this error: https://pastebin.com/3iwZdCba, when i try to run jam -q haiku.hpkg after running ./configure on cloned haiku codebase
moparisthebest has quit [Ping timeout: 480 seconds]
akashkumar has quit [Ping timeout: 480 seconds]
erysdren has joined #haiku
<nipos>
This is because the BIOS bootloader is 32bit,but you can only build 64bit stuff on 64bit Haiku by default
<nipos>
If you need to build the BIOS loader,you must also download the buildtools repository to make this work.If you don't need it,you can edit the build target to disable building it.
<nipos>
I always disable the build target,since I already have the BIOS bootloader from the package installed and don't need to build one from source anymore.To do that,edit the file build/jam/packages/Haiku and add a # before lines 19-22
<akashkumar7902>
eu.hpkg.haiku-depot.org is too slow for me, does mirrors exists ?
<nipos>
There's one that I know that is well-maintained and works fine for me,but mirrors are not officially supported so use at your own risk.It's here: https://mirror.truenetwork.ru/haiku/haikuports/x86_64/current/ Also,it offers only haikuports packages,not the haiku base packages.For those,no mirrors exist as far as I know
<nekobot>
[haiku/haiku] 64a0bc243c2e - pthread_key: when calling destructors, iterates over keys again
x10z has joined #haiku
andreaallegri has joined #haiku
andreaallegri has left #haiku [#haiku]
Nasina has joined #haiku
freakazoid332 has quit [Read error: Connection reset by peer]
frkazoid333 has joined #haiku
Nasina has quit [Ping timeout: 480 seconds]
oco has joined #haiku
myriad has joined #haiku
tktech287 has joined #haiku
oco2 has joined #haiku
oco has quit [Read error: Connection reset by peer]
tktech28 has quit [Ping timeout: 480 seconds]
tktech287 is now known as tktech28
mmu_man has joined #haiku
zard has quit [Ping timeout: 480 seconds]
mmu_man has quit [Ping timeout: 480 seconds]
x10z has quit [Ping timeout: 480 seconds]
x10z has joined #haiku
HaikuUser has joined #haiku
HaikuUser has quit []
jmairboeck has joined #haiku
dalme has joined #haiku
yann64 has joined #haiku
BrunoSpr has joined #haiku
<Begasus[m]>
ok, done for today
<Begasus[m]>
cu peeps!
tombhadAC has joined #haiku
BrunoSpr has quit [Quit: Vision[]: Ich wurde eingeweicht!]
MisthaLu has quit [Ping timeout: 480 seconds]
yann64 has quit [Quit: Vision[]: i've been blurred!]
mmu_man has joined #haiku
jmairboeck has quit [Quit: Konversation terminated!]
dalme has quit []
x10z has quit [Ping timeout: 480 seconds]
cptaffe` has joined #haiku
cptaffe has quit [Ping timeout: 480 seconds]
<myriad>
Hello, I was curious about the sleep/suspend function in Haiku, so I searched for it online to get some idea about it's progress but the last mention about it I could find was from Feb 2020 where Pulkomandy said Haiku doesn't support it yet. What's the status now? And can I help if I am a beginner in OS dev ?
x10z has joined #haiku
nephele_xmpp has joined #haiku
<mmu_man>
myriad: nothing more yet really. It's not like Haiku takes long to boot or shutdown
<mmu_man>
but it's really complex to implement properly
<Habbie>
and if you get it wrong, your document was not saved, which shutdown does get right
Nasina has joined #haiku
<phschafft>
maybe time is better invested in allowing for easy close/restore in all the different tools.
<phschafft>
which doesn't mean that one could not work into the right direction.
<phschafft>
to prepare for such a feature later on.
<nephele_xmpp>
phschafft: we mostly already have that
<phschafft>
nephele_xmpp: and that is why I suggest to get that from good to perfect.
<nephele_xmpp>
I don’t know if there is anything misssing in that respect… if there is no gui visible way to trigger this then the code mostly is untested ;)
<myriad>
I see, I was just asking because I have a habit of taking my laptop outside for my college stuff and pressing superkey+L does it really fast when I need to leave in a hurry or quickly hide something lol
<Habbie>
if the reason is 'hiding' or 'locking', that's a simpler problem
<phschafft>
again, my suggestion was because of the good support. just that with software there is always something to make better. ;)
<nephele_xmpp>
Sure there is. Mostly all classes in our api support archiving/unarchiving. You’d have to extend that to be suported in app classes if it isn’t. And then add a message so apps archive themselves on command. (Could include the document you are editing). And then a way for the app to un-archive on startup. Anyhow, a bit complex. but possible
<nephele_xmpp>
It’s a bit more structured than just a “continue where you left off”. I reckon it could work better. But I don’t know, nobody really tested stuff like that yet
Nasina has quit [Remote host closed the connection]
Nasina has joined #haiku
<nephele_xmpp>
but then “the app server crashed! reconnect with your data model and make new windows” is a similar problem
<phschafft>
you know I'm a big fan of good serialisation for store/restore in contrast of dumping random memory to disk ;)
mmu_man has quit [Ping timeout: 480 seconds]
<phschafft>
plus there are more possible features. such as restore half a session.
<phschafft>
... and restore the rest later.
<myriad>
:Habbie I mean usually on windows or Linux once you lock your system, it goes to sleep automatically after a certain time which does help in saving battery but just the 'locking' feature on it's own is also pretty useful ig.
<Habbie>
myriad, yeah i understand
<myriad>
Habbie: If it's simple, can you give any ideas for how can I start working on it?
<nephele_xmpp>
we don’t have any real “security” when it comes to locking the desktop. But there is one screensaver that has a password if you want. But sttill no real securitty
<Habbie>
myriad, i did not say simple; i said simpler :> all very relative
dqk has quit [Ping timeout: 480 seconds]
<Habbie>
suspend involves convincing all pieces of hardware to cooperate
<Habbie>
locking involves making sure no input to the system happens until the right password is entered
<Habbie>
perhaps they are just mostly very different problems; "simpler" might be unfair
<nephele_xmpp>
if you just want to prevent input you could hijack the input server :P
mmu_man has joined #haiku
<myriad>
Habbie: makes sense, but still I feel I can try working on the locking feature at least
<Habbie>
yes
<nephele_xmpp>
do you want protection from people who would not try to unlock it? then you are already set. If you want protection from people who would byppass the passsword prompt, well, that would be a huge ammount of work :)
<myriad>
nephele_xmpp: I was just going to ask you about that, sorry i am not really experienced with the security stuff but there must be a middleground between those two right? Like if someone does try to bypass it maybe we can implement a simple mechanism to not allow it to a certain level, just for a start you know
<myriad>
Like security against some basic common attacks
<nephele_xmpp>
not really. You can’t make a “kinda secure” architecture. Take for example Screen lockers on X11, those have been over the years defeated by 10 year olds or cats sittting on the keyboard. If you want to make it secure you have to make the underlying stuff secure aswell
<nephele_xmpp>
That means the screen locker can’t be an overlay “Window” that just gives you back your session when it crashes for example
<Habbie>
even apple, who own the whole stack, didn't get it right the first 15 years
<Habbie>
yeah crash to unlock is the famou sone
<Habbie>
*famous one
<nephele_xmpp>
and if you don’t want an overlay window now you have to adjust app_server, input_server, and possibly also add some sesssion code to make this screen unlocking a new session
<nephele_xmpp>
and make the only way to restore the other session beeing the correct password beeing entered
<waddlesplash>
this is why I want to write display_server
<waddlesplash>
not just to run accelerants/userland 3D graphics drivers in
<waddlesplash>
but so that when you lock your screen, the app_server actually detaches from the display buffers, and a secondary app_server just for displaying the screen locker runs instead
<nephele_xmpp>
Yeah, that would be a possible architecture. But then we also need to be extra carefull that when we have resumeable app_server connections that a crashed app_server doesn’t make apps connect to the other one for example
<waddlesplash>
sure
<nephele_xmpp>
:)
HaikuUser has joined #haiku
HaikuUser has quit []
<nephele_xmpp>
Or, come to think off it, that a display_server crash doesn’t make app_server of the acive session atttach to the visible buffer again
<myriad>
I see, I will just stick to the screen locker for now then. Can anyone guide me a little on how to start working on it. I intend to finish it soon if possible so that I can focus on my gsoc proposal
<nephele_xmpp>
I don’t think anything needs to be done there?
<myriad>
nephele_xmpp: are you talking about the screensaver feature? I tried it, but it somehow doesn't feel quick to me, or rather I was thinking of adding a shortcut key to lock it instead of being dependent on the screensaver
<nephele_xmpp>
quick?
x10z has quit [Ping timeout: 480 seconds]
<myriad>
Like compared to windows or Linux. I am not saying it's bad, but first I have to take my mouse pointer to a specified corner to start the screensaver instantly, right? Or am I missing something? And sometimes I don't have my mouse with me and my mousepad doesn't work smoothly anymore so in that sense I thought a shortcut key combination feels much faster
<nephele_xmpp>
You can set a shorcut in the shortcut preferences
<nephele_xmpp>
Not sure if you can “directly” invoke the screensaver to start it, but i would expect it to work
<nephele_xmpp>
I asked “quick?” because i did not understand what you ment by does not feel quick
Nasina has quit [Ping timeout: 480 seconds]
<myriad>
I am not entirely fluent in English, so I am unable to correctly express my thoughts sometimes.
<myriad>
I didn't know that we can set a shortcut for that, will try that
<myriad>
Thanks
oco2 has quit [Ping timeout: 480 seconds]
<gordonjcp>
myriad: I wouldn't worry about it, your English is better than a lot of people I deal with every day who *only* speak English ;-)
<Habbie>
indeed!
<myriad>
gordonjcp: Okay :)
<Habbie>
some of those don't even know the word "myriad"
x10z has joined #haiku
<gordonjcp>
it's a font isn't it?
<gordonjcp>
myriad: where are you from?
<Habbie>
many words are font names these days, but it's also just a word
<myriad>
gordonjcp: I am from India.
<myriad>
It's a synonym for infinite afaik. I like the concept of infinity and I thought myriad was cool so I use it nowadays haha
oco has joined #haiku
x10z has quit [Ping timeout: 480 seconds]
Nasina has joined #haiku
x10z has joined #haiku
nephele_xmpp has left #haiku [Error from remote client]