Search results

I don't know why. I installed it, then tried running it both with and without the xhci_mouse = "yes" line, but I still saw both a mouse pointer, and a small dot, which seemed to be the mouse. It's not that important, as almost all my bhyve instances are usually done with console or ssh.

Why? Because it was an effort to help. I'm guessing that the why refers to why am I thanking you for the suggestion.

I just tried utouch-kmod. It didn't help (for me, anyway) but thanks for the suggestion.

XHCI seems to only work on older Linux kernels, e.g. RHEL-9.x and so on. I seem to remember reading somewhere that a Linux kernel update made it stop working. I can get it to work by leaving out xhci_mouse="yes" but like to OP, it's not synchronized. (and keyboard shortcuts don't work).

In my case, I didn't need oauth. I don't know if it's changed, but when I did it, I just had to set a special app password. It may have changed, Google gets more and more..proprietary seems the best word.

I use msmtp. Gmail did make changes making it more difficult to use with 3rd party apps, supposedly for our safety, more likely part of google's attempt to close out anyone else. I give instructions on my mutt page https://srobb.net/mutt.html#getmail It's about halfway down, you can search the...

I don't use Kimpanel to configure I just manually edit .config/fcitx5/profile. I don't use fcitx5 too much, so I just manually start i if I do need Japanese. At any rate, while I get a message that Kimpanel has a new owner, fcitx5 with anthy, is working fine for me with dwm. I haven't tried with...

It didn't work for me, which doesn't mean it's bad, I may have been too weak willed. However, MANY have had success with it, it's certainly worth a try.

And as a package, virtualbox-ose-additions-6.1.50

Note the package message if you install provides. On install: In order to use the pkg-provides plugin you need to enable plugins in pkg. To do this, uncomment the following lines in /usr/local/etc/pkg.conf file and add pkg-provides to the supported plugin list: PKG_PLUGINS_DIR =...

There's already another thread on this with some useful links. https://forums.freebsd.org/threads/backdoor-in-upstream-xz-liblzma-leading-to-ssh-server-compromise.92922/

pkg install fusefs-ext2 kldload fuse fuse-ext2 /dev/nda0p4 /mnt The first line, only if you don't yet have fuse-ext2 installed. I don't have a Linux partition to check right now, but I'm pretty sure that will mount it read-only. It requires root, sudo, or doas. Even though it says ext2, it...

That seems accurate to me. I think that might be their aim, not to make a new form of FreeBSD, but to make an easy for the inexperienced to use version of FreeBSD. (That's just my opinion).

I do remember the old joke about the guy who works on Windows copy dialogs on the phone with his wife, "I'll be home for dinner in 10 minutes..no, make that 5 minutes--no, make that two hours" I also vaguely remember an old Linux from Scratch book where they took a package as the baseline...

That was it! Many thanks, I'll mark this solved. I suspect that local_startup got messed up because the jail was moved. I'd had it in one spot, then had a crash. The jail was on a separate, unaffected drive, and I wound up changing the mountpoint. Adding that line to /etc/rc.conf fixed things.

It's correctly typed. I also have apache installed, (I was testing), and have the same issue. Both give the message about not existing in /etc/rc.d or the local startup. I tried your suggestion of moving the /etc/rc.conf.d/nginx to /usr/local/etc/rc.conf.d, but no luck. I still get the same...

Yes, I'm sorry, I thought I'd answered that.　申し訳ありません。(Sorry, just got off the phone with my wife, who's in Tokyo till Monday). Anyway, yes the file is right there in the jail's /usr/local/etc/rc.d. As mentioned, I can start it with (in the jail) cd /usr/local/etc/rc.d; ./ngninx start

Thanks for the suggestions. The pkg is installed in the jail, but I didn't know the pkg -j option, so I learned something. The rc.conf.d in the jail reads nginx_enable="YES" Running the service -j <jailname> nginx start just gives the same message as mentioned before nginx does not exist in...

Just a guess because this happened to me trying Wayland with Fedora. If I remember correctly, you're using Wayland. Is that when this started? If so, you can try changing your XDG_RUNTIME_DIR to something like $HOME/.cache/run. Again just a guess and it happened to me on Linux, not FreeBSD...

Sorry I never got back on this. Yes, that was a typo on my part, it was in rc.conf correctly.