Well, since we are here I might aswell put up my wishlist (of items i want to work on)
Dark mode (already good progress in beta3, slight issues remain+lots of web presence)
better Hyper-V guest support (VMbus, native resolution etc)
(My main trouble here is that I don’t actually have a windows machine to test this on, heh)
Of the above mentioned Items I also like bluetooth audio and SMBv3/SMBv4 support
@nipos : Locking screen with a password is already available in pref/ScreenSaver
Honestly all that’s missing for me to make my first-gen i5 notebook a dedicated Haiku machine is support for setting video modes on “newer” Nvidia chips. The VBE bios on that GeForce 320M only goes up to 1024x768 =/
Research Clover and it’s VBIOS patching ability. Maybe it would help.
I do happen to have a Windows machine and I have some interest in helping on this. I don’t know if you have any hints though maybe it is just a matter of reading the docs. I see some of the related tickets on Trac.
Here are my wishes:
Excerptfrom the documentation:
PatchVBios
PatchVBios
Clover applies corrections to the shadow ROM at address 0xC0000 to allow support of the highest monitor resolution. For instance, a monitor’s EDID contains the mode 1920x1080 but the video bios does not. Clover will apply it as the first mode to be used. In case the monitor does not produce an EDID, it can be injected manually.
In case
ScreenResolutionin sectionGUIis set, it will be used for this patch.Should the automatic patch fail, then you can specify a manual one.
On that note, better VirtualBox and VMWare support would be really good too.
Thanks for the hint,I didn’t know this setting before.But for me it’s a bit too unsecure.
We need an implementation of VMBus which seems to basically be a command ring buffer in a share memory region (docs are not that clear with which interupts you set that up initually but I had seen someone who explored that more precisely)
After that we can use the VMBus interface to add a driver for the virtual screen and other devices.
Anyway, I’d be happy to work with you on this.
We already have vmware guest drivers I think, I’ve heard about some complaints about those maybe we can figure out what is wrong and or integrate the guest drivers more directly.
This probably goes hand-in-hand with improving the VMWare Addons package which is currently unmaintained, as well as adding a VirtualBox Guest Additions package as well.
Kernel loader support for running Btrfs as root (system-wide) fs. I very much like CoW, and the fact that it ensures power outage safety.
Good day,
In my case I “would want”:
And now, the big one:
What can I do to help achieve those?
Regards,
RR
Interesting, I’d consider that a bug. Is there a ticket?
That’s basically the same as windows, you can just disable password prompts or change passwords on a computer if you boot smth else. (bios passwords can be circumvented too by reseting it via mainboard pins or unplugging thr cmos battery)
I see what you mean though generally, I’d think running this on boot to lock the screen could work fine?
I tried searching for a ticket but couldn’t find much useful stuff.When searching for “screen saver” I got at least something that has anything to do with the lock feature,but not exactly this problem.
And needing to boot something else isn’t the same as just needing to reboot Haiku.Everyone can simply reboot Haiku to unlock it but not everyone may be able to change BIOS settings and boot another OS.I mean,it’s not really secure but it’s something at least.Can you tell me which command I have to run on boot to lock the screen?
It is kind of a hack for now but the screen saver program is screen_blanker and you could set that up to run with launch_daemon when the system starts. Long term we need to add a proper login system, but our current goal is to reproduce BeOS which did not have that feature. All the needed infrastructure is there to add it though.
Here is information about the launch_daemon, but more from a developer perspective:
https://www.haiku-os.org/docs/api/launch_intro.html
I don’t know if we have better user documentation, we probably should add something.
There are a couple of disabled recipes for this targeting older versions of VirtualBox. I’ve made some progress on putting together an updated version for 6.1.26, at least for x86_64 - this is based on some of the existing code and patches.
I’m not sure how much of it I’ll be able to get going or whether I’ll be able to get it going at all. I’ve got the driver building and starting up OK now, there are issues with the Shared Folders module, probably some other stuff too - haven’t even tried the VGA driver. I’d minimally at least like to get copy/paste to work since that’d be very convenient for me.
There are a number of issues with the current code (as in the actual VirtualBox source - there’s some Haiku Additions code already in it), including some checks on return values which are blatantly wrong for Haiku - which is quite confusing.
If someone else is working on it feel free to get in touch.
Thank you very much for that hint,that seems to work pretty good.
I want to add for other people trying that: The Launch Daemon documentation is wrong/outdated,the actual path is ~/config/settings/boot/launch but a complicated Launcher service isn’t even needed,you can simply add the line “screen_blanker” at the bottom of the file ~/config/settings/boot/UserBootscript
Unfortunately,this still doesn’t solve the problem with being able to open the start menu in locked state.
I can see the recently used files and all installed applications and I can even launch them!
They won’t show up as long as the screen is locked but applications being executed in the background can be enough to cause damage.
Nevermind,someone could have a shortcut to a bash script with “rm -rf --no preserve-root /” and anyone could start it from the start menu on a locked computer,that would be pretty evil…
Yes that issue needs to be fixed. The screen saver lock screen is not really a proper lock screen and to fix this we really need an actual lock screen which is deeply tied into the system.
I don’t know how much work that would be but a proper lock screen sounds like a good idea.
The current one works better than nothing but it isn’t easy to enable for a normal end-user and it’s not really secure.
Especially with multi-user support being planned,a working account management with login screen and lock screen will be required anyway.
You can use bit locker on Windows to encrypt your HD, which makes it impossible to modify the system by booting something else.