bittin-
https://www.bsdnow.tv/603
Mahdi
Greetings to my awesome friends and group members, While installing FreeBSD, I foolishly enabled the moused daemon. As we all know, moused is entirely useless anyway! Later, when I regretted it and tried to disable it, both the onestop and stop options in the service command didn’t work. I manually set moused_enable to NO in the rc.conf file, but it still didn’t solve the issue. Then, it gives the message: cannot stop moused. Set moused_enable to YES in /etc/rc.conf or use onestop instead of stop. In the end, the mouse is still stubbornly present. I also checked the kernel modules but didn’t find anything named moused. I even looked into the usr/local/etc/rc.conf file, but there was nothing significant in there. Any help would be much appreciated. Thanks in advance! Have a great FreeBSD day! 😊
Mahdi
I have painstakingly configured my beloved FreeBSD for my computer, adding numerous personal customizations. I absolutely do not want to redo everything from scratch, even though I’ve documented it all for myself. Please help me get that cursed mouse off my character-based display because it’s preventing me from seeing my terminal commands.
Mahdi
put your dotfiles and other configs into git then
I really don't understand. Does that mean I have to reinstall from the beginning?
Maxim
I really don't understand. Does that mean I have to reinstall from the beginning?
no, that means you should put your configs somewhere safe so that i you have to reinstall, you'll have them anyway
Mahdi
no, that means you should put your configs somewhere safe so that i you have to reinstall, you'll have them anyway
oh yes i have a local git on my personal server I'm not worried about losing my configs I'm just upset about that damn moused :)
Mahdi
Did you try bsdconfig ?
yes i installed it with bsdconfig, how?
Mahdi
oh i forget, that was bsdinstall
Mahdi
I tried very hard to remove it.
polyduekes
Did you try bsdconfig ?
wow, til that exists
Mahdi
what is the mouse Type in bsdconfig, to disable the moused, should i know what is the my mouse protocol ?
Mahdi
Is it still running ? pgrep, top, ps aux ....
yeah, please wait to check those
Mahdi
$ top | grep moused 682 root 1 20 0 14M 2468K select 3 0:00 0.00% moused
polyduekes
maybe you can setup a cron job to onestop moused everytime you boot
Mahdi
so, should i to kill that? or put the kill command on the shell startup command?
nami
Moused is not totally useless as you called it with it you can use your mouse in a text environment which is very useful for copy pasting text
B
$ top | grep moused 682 root 1 20 0 14M 2468K select 3 0:00 0.00% moused
Hmm, did you reboot after doing changes to rc.conf ?
Mahdi
i think i should to kill the moused but that's PID is not fixed and they changes every times after reboot and ... :)
Mahdi
when i try to use openstop, it says : $ sudo service moused onestop Password: moused not running? (check /var/run/moused.pid). i dont know what is this :)
B
i think i should to kill the moused but that's PID is not fixed and they changes every times after reboot and ... :)
That is what pkill is for ... But that's a hack it's best to see where it is getting started from .
Mahdi
$ ls /var/run/ | grep moused moused.ums0.pid so that is a bug?
Mahdi
Should I report this bug, if it is a bug?
nami
polyduekes
Mahdi
You are in graphical environment?
no, command based simple first command based in bash
B
really thanks for your helps but how can i fix it?
ASFAIK USB mice auto start moused .
Mahdi
wdym?
sorry, what is this?
B
IDK how to disable it .
polyduekes
sorry, what is this?
what do you mean
Mahdi
what do you mean
i should to disconnect the mouse from my PC?
polyduekes
i should to disconnect the mouse from my PC?
no, you can just cat /var/run/moused.pid and feed the output to kill or use pkill like said before
Mahdi
what do you mean
i meantI mean, what does this help?
polyduekes
i meantI mean, what does this help?
to kill moused, you said the pid changes every time
polyduekes
as long as it works i don't see a problem with a hack
Mahdi
ok, thanks But you didn't say, Is this a bug? Do I need to report the problem?
polyduekes
you could try asking on the freebsd-questions mailing list, many people involved in the active development of freebsd are there, they might know
B
Maybe look at devd.conf ?
B
ASFAIK USB mice auto start moused .
That's where this behavior should be defined in .
nami
ok, thanks But you didn't say, Is this a bug? Do I need to report the problem?
devd is running moused after connecting your device. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182150
Mahdi
devd is running moused after connecting your device. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182150
ok. maybe when i disconnect the my mouse jack from the pc, problem will fixed
Mahdi
And yessss, when I disconnect my mouse and reboot the system, the mouse daemon does not show up again.
Mahdi
thanks :)
Pouria
https://forums.freebsd.org/threads/why-netlink-over-bsd-routing-sockets.97276/
polyduekes
can anyone explain what does it mean by updating to p2
Pouria
can anyone explain what does it mean by updating to p2
FreeBSD "-p" suffixes indicate minor updates that are releases. When you run freebsd-update fetch, it always look up the minor revisions (such as 14.2-RELEASE-p2) unless you specify the -r flag for major releases. It also downloads the patches for your current system. https://docs.freebsd.org/en/books/handbook/cutting-edge/#freebsdupdate-upgrade
Pouria
i know that but did you noticed that i am on patch version 2 already? maybe check the freebsd-version -kru output i sent
weird, checkout the fetch_run() shell function at /usr/src/usr.sbin/freebsd-update/freebsd-update.sh. You may find it out yourself.
polyduekes
You manually built kernel, remember?
ok, but what does normally running make kernel as it is supposed to install kernel after git pulling src after p2 has been completely merged to do with that?
polyduekes
it's not like they pushed another p2 patch again
Jekyll
it's not like they pushed another p2 patch again
No, so if you run freebsd-update install now the kernel will be "updated" to 14.2-RELEASE-p1.
Jekyll
polyduekes
No, so if you run freebsd-update install now the kernel will be "updated" to 14.2-RELEASE-p1.
it's not saying p1 and the kernel version string doesn't go in any debug file which are all it is updating
Pouria
it's not saying p1 and the kernel version string doesn't go in any debug file which are all it is updating
cat /var/db/freebsd-update/tag cat /var/db/freebsd-update/tINDEX.present I'm curious what your index files says.
Pouria
You manually built kernel, remember?
it's probably the issue. maybe he should clear its /var/db/freebsd-update after building from source to reinforce the indexing. But, IDK
polyduekes
cat /var/db/freebsd-update/tag cat /var/db/freebsd-update/tINDEX.present I'm curious what your index files says.
freebsd-update|amd64|14.2-RELEASE|2|b2d24124bf6424d47972de2aa5fbe44099787d7cef1061b582cb707ada38dd98|1759276800 INDEX-ALL|812d71cc52bbaae6368c0df1304bcf5410ab5bea2cc73b0f2f79b173cf59bc59 INDEX-NEW|d71a7f70daf30fc465fba7a18547ff216a446d47317d5fcf49fed26461b0ecb1 INDEX-OLD|83987ba6574a2212ca9737df3b37e07c2565c33f86b1674fc0eca62c934bc808
Jekyll
it's probably the issue. maybe he should clear its /var/db/freebsd-update after building from source to reinforce the indexing. But, IDK
I think it is. The update freebsd-update does from 14.2-RELEASE-p1 to 14.2-RELEASE-p2 does not include kernel update, only userland.
polyduekes
I don't think I understand you.
well maybe you are right, maybe it is the kernel version string
polyduekes
lemme see if the p2 patch commits affects those files or not
polyduekes
https://cgit.freebsd.org/src/commit/?h=releng/14.2&id=ac2cbb46b5f1efa7f7b5d4eb15631337329ec5b2 https://cgit.freebsd.org/src/commit/?h=releng/14.2&id=4b8a2f716588e58ddb39ccdb60189e8c57239457 https://cgit.freebsd.org/src/commit/?h=releng/14.2&id=1920babc310ab8ebaa76188decf1aa5ed88e9d84 https://cgit.freebsd.org/src/commit/?h=releng/14.2&id=3ae196925d2915e95e549dbc1687c75845ce87a9 hmm, no the commits in the src don't affect the files it is upgrading so it's not because i built from src
Jekyll
Just try it.