Slackware 15.0 (64 bit Ed.) [sudo worked without the user than ran sudo being in the sudoers file].
 

After installing Slackware 15.0 (64 bit Ed.) I ran the sudo command (to format /dev/sda6) and it worked.

Then I ran it again and it said "...not in the sudoers file".

And yesterday night some windows would maximize and minimize without me using neither the mouse neither the trackpoint.

I don't know if that was someone remotely controlling my system or a "spirit".

An image of the CRT monitor that was connected to the computer I used to download Slackware 15.0 (64 bit Ed.) is attached.

were you in room 237 at the overlook hotel?

- In seriousness I only once had a phantom mouse when I had a used a Dell Latitude c600. https://www.techwalla.com/articles/h...-dell-latitude

I ended up snipping the wire to disable...


Did you add your user to the sudoers? Slackware does not do this by default? (as root you don't need sudo)

I downloaded, burned and used Slackware 13.37 when it came out.

root is added to the sudoers file by default. No other users or groups are setup to use sudo out of the box.

If you're having issues with your mouse, it is usually the mouse going bad or a bad USB port. Unless you've opened up your system to the internet and made your passwords easily guessable, nobody else is controlling your system.

(I didn't realize people still used CRTs. I haven't owned one in probably 15+ years.)

I had forgotten about CRTs too. I've seen them being sold at like 5 USD years ago here in Argentina.

Hey! Is that the Assembly version of Windows 7?

Stop trolling.

The fact that you did use Windows to download the Slackware installation media is probably not important. However, it could be important to after the download check the md5sum if the .iso file and the corresponding .iso.asc file with gnupg against the public GPG-KEY of Slackware to make sure that its contents really is as intended from Slackware.

Strange behavior like this could be because of a compromised system, broken software or broken hardware. As you haven't had much responses like "yes me too" the software were probably not broken out of the box. So the software could have become broken at download or if your system were compromised. Broken hardware sometimes shows signs in the output from dmesg, but I would start by running memtest from the Slackware installation media or some other boot-able media with memtest.

regards Henrik