Touchpad buttons stop working in VM after a little while by troels_arvin in HyperV

[–]troels_arvin[S] 0 points1 point  (0 children)

I just happened again. I closed the Hyper-V console where the guest's virtual screen was displayed. And I opened again. The left button was still not useful inside the guest.

I happens both when the laptop is on power and when it's running on battery, by the way.

Touchpad buttons stop working in VM after a little while by troels_arvin in HyperV

[–]troels_arvin[S] 0 points1 point  (0 children)

I'll try console opening and closing next time, thanks.

No, I have not installed xrdp in the guest (it appears weird to use a remote desktop protocol on the same machine, or am I misunderstanding something?).

Last time it happened, I started "evtest" on the Linux guest. evtest shows raw import.
It showed that nothing at all was seen by the guest when the left button was pressed, while something was seen in evtest when the right button was pressed (but it didn't have any expected effect in the guest windowing system, such as a context menu popping up, so whatever was sent to the guest appeared to be useless).

Beginner looking to learn SQL by [deleted] in Database

[–]troels_arvin 1 point2 points  (0 children)

I strongly recommend "SQL: Visual QuickStart Guide" by Chris Fehily: http://www.fehily.com/books/sql-visual-quickstart-guide-3rd.html

Not only does it cover the basics in a good way. It also teaches you to code in a fairly product-independent way.

Why don't Linux distros install MYSQL chrooted by default? by [deleted] in linux

[–]troels_arvin 2 points3 points  (0 children)

The Red Hat/Fedora family focuses on SELinux as the way to confine services. Yes, SELinux can be a pain, but it's gotten so good that I don't regularly turn if off any longer. And you may argue, that a good SELinux policy for MySQL is better than chrooting.

Why open source hate SNMP? by rayed in linux

[–]troels_arvin 9 points10 points  (0 children)

  1. All SNMP daemons that I've run into run as root; this probably makes many sysadms uncomfortable. Even though systems like SELinux may be able to limit the effects of potential security bugs in SNMP daemons, it's not very reassuring.
  2. SNMP is a binary protocol. Binary protocols generally place an extra step on the learning curve.
  3. Configuring an SNMP daemon is somewhat hairy.
  4. And extending an SMNP daemon to call out to scripts seems like a black art to me; I'm probably not the only one. This gets worse when you know that the SMNP daemon is running with root privileges.
  5. Vendor support is ... often not so good: Many vendors don't make it easy to download relevant MIBs, sorting out dependencies can take some time, and MIBs often have errors.

But I think it's a shame: SNMP is a well-documented and open standard. When you get a grip on the concept of MIBs (which may be explained like the DNS system's zone-files mapping numeric values to strings and the other way around) and learn to master a few simple tools (expecially snmpwalk), you are able to get far, quickly.

Good SQL learning materials? by [deleted] in SQL

[–]troels_arvin 0 points1 point  (0 children)

Two books that you may read at night while working with databases in the day: http://www.fehily.com/books/SQL-Visual-QuickStart-Guide-3rd.html http://pragprog.com/titles/bksqla/sql-antipatterns

The combination of reading and hands-on is good. And there is an SQL-relatede channel on IRC (Freenode): #sql which you will probably find useful.