(In addition to weirdness surrounding the sound drivers and video, the current setup does not do a great job at Japanese input, so please pardon the romaji.)
@r@hakui I have played it briefly; I think I played more xiangqi than shougi.
I play chess. (But I refuse to hand over my weeb card because this is the background image on the machine I am using and I have sung a Morning Musume song at karaoke on a date with a girl that inexplicably wanted a second date.) misatohax.jpg
@lanodan@hakui@r Well, it hooks in differently (and then does the stupid backspace behavior which makes it faster for some uses but completely breaks some other uses) but it behaves more or less like anthy running under uim-xim.
@p@r@hakui Oooh even has support for Henkan/Muhenkan (my T495 got a JIS keyboard), and I guess ktrans is close enough to an IME in terms of use-case rather than exact behavior. (Quite like how ed(1) and sam(1) are both editors)
@p@r 1. join https://lishogi.org/team/groups 2. next sesh is in ~23h, join the "team tournament" (it's not actually a tournament, it's just to use their automatching function
@p@r@hakui Well I have played around in ⑨ before, been wanting to have it on baremetal but hardware is a fuck so it's been mostly VMs so far. Like I got it to boot up on my T495 ~6 years ago and it was really nice but sadly modern laptops barely allow secondary disks, maybe once MNT Reform Next ships it'll transform into a machine for ⑨.
@lanodan@hakui@r I think VM is fine, just get proper VM with its ethernet talking to br0 so it can be in control of its network stack and you can do things like ping and then you drawterm into it.
I don't use it very often, but I have a 9front VM running on my DevTerm and you can barely tell because it barely touches the CPU/RAM unless you tell it to do something fancy, and then I connect to it via drawterm and everything works fine.
@r@hakui If I consider how often I am awake at 14:15 UTC on a Saturday (or, using the magic of database queries, I can actually determine this), that may be less plausible.
@p@r@hakui Well baremetal bit is more that as nice a VM can be it's often quite limiting and just doesn't feels the same. Plus kind of want more OS diversity in my infra, so far it's all Linux, and BSDs aren't really the direction I want to go towards.
@lanodan@hakui@r Yeah, I can understand that some; I am almost never using the computer I am touching directly, everything I do is mediated by ssh or drawterm so it hardly matters to me whether it's a VM or an entire machine except that it's easier to remotely reboot a VM. (I expected to hate libvirt but it turns out that I do not hate libvirt, thought it is much more flaky than something with so much XML is usually allowed to be.)
@hakui@r It is not quite DST yet but I'd have to be on the east coast (NEVER but they are UTC-4 right now but also NEVER). I am in the Wild West and that puts me between UTC-6 to UTC-8, 14:00 - (6 to 8 hours) = 06:00 to 08:00.
@p@r@hakui Luckily I don't think I'll ever need libvirt, I'm familiar enough with qemu command lines and it's easy enough to dæmonize, should I ever want that (usually my VMs are more or less throwaways).
Although I do sometimes use remote-viewer(1)/virt-viewer from the libvirt project when I need a spice/vnc client different from remmina (I really need to write my own, all the ones I tried horribly suck and sadly devterm hasn't been adopted by non-⑨ systems)
> I don't think I'll ever need libvirt, I'm familiar enough with qemu command lines and it's easy enough to dæmonize, should I ever want that (usually my VMs are more or less throwaways).
I didn't think I'd ever need it! I swear, it's easier to work with than most uses of qemu and it just uses qemu and you can have it give you the qemu flags directly. I generally use qemu locally for throwaway VMs but virsh is a lot more convenient by comparison, like qemu nowadays wants you to specify the bus that the hard drive controller is connected to and then the controller that the drive is connected to and I worry that in a few releases it will make me start specifying jumper positions in argv.
@p@r@hakui So far qemu hasn't given me pain there, like -hda $file still works fine, same with -drive format=raw,file=$file although I don't use the latter much and wouldn't be surprised it API-broke few times.
That said it's also been a while since I virtualised anything non-x86 (arm stuff I got being quite potato so I much prefer having containers or kexec'ing/rebooting into the system I need), and maybe with some of those you'd need to pass bus numbers.
Yeah, you have to specify the disk and the image separately depending, it complains about the MBR if you use `-fda` instead of passing the `-drive format=` stuff, etc. I can never remember off the top of my head how to get it to do the NIC properly.
> That said it's also been a while since I virtualised anything non-x86
Yeah, KVM support on ARM isn't great and isn't easy to coax out of qemu and TCG is more heavily optimized so even on ARM, if I'm running a VM, it's usually x86. (That's the thing about ARM, though, like nobody really does "big ARM node", it's always "swarm of tiny ARM nodes".)