• 2 Posts
  • 54 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle





  • The easiest way to disable unnecessary services is to uninstall them with aptitude, or whichever package manager you like. Try terminating services one by one, and see if anything bad happens. If nothing bad happens, you can probably uninstall it. On the other hand, if the system does get wonky a reboot should fix it. Or, you can research the services by name and decide whether to uninstall them. (avahi-daemon for example is a good idea to uninstall.)

    To make the GUI not run, uninstall your display manager (gdm, xdm, nodm, or whatever) and uninstall your xorg server or wayland server. There may be GUI programs remaining after that, but they will only be consuming disk space, not RAM or CPU.

    If the battery is old and holds little charge, you may save a few watts by removing it and throwing it away, instead of letting the system keep it topped off.

    Get a power meter, such as a Kill-a-watt device. Then, experiment with different settings. If it’s consuming less than 30 watts, you’re probably fine. If you live in the US, one watt-year is about one US dollar (or a little more), so for every watt it consumes, that’s about how much you will pay per year for its electricity.


  • Looks like this program is really old. It appears to be designed for a 32-bit system, the way it casts between unsigned int and pointers.

    unsigned int is probably 32-bit even on your 64-bit system, so you’re only printing half the pointer with the printf, and only scanning half the pointer with the scanf. The correct data type to be using for this is uintptr_t , which is the same as uint32_t on a 32-bit system, and the same as uint64_t on a 64-bit system.

    Try changing the type of addr to uintptr_t , and change lines 14-17 to this:

    	printf("Address of main function: %p\n", (void *) &main);
    	printf("Address of addr variable: %p\n", (void *) &addr);
    	printf("\nEnter a (hex) address: ");
    	scanf("%p", &addr);
    

    You may have to include <stdint.h> . These changes should make the code portable to any 32-bit or 64-bit architecture.


  • NTFS is considered pretty stable on Linux now. It should be safe to use indefinitely.

    If you’re worried about the lack of Unix-style permissions and attributes in NTFS, then getting BTRFS or ext4 on Windows may be a good choice. Note that BTRFS is much more complicated than ext4, so ext4 may have better compatibility and lower risk of corruption. I used ext3 on Windows in 2007 and it was very reliable; ext4 today is very similar to ext3 from those days.

    The absolute best compatibility would come from using a filesystem natively supported by both operating systems, developed without reverse engineering. That leaves only vfat (aka FAT32) and exfat. Both lack Unix-style permissions and attributes.









  • Sounds like what you’re looking for is an ATX12V plug. It’s a 2x2 connector that normally has two yellow and two black wires. It normally goes into the 2x2 receptacle on the motherboard to power the processor. In this case, the eGPU enclosure needs it for some reason, maybe for more power.

    The good news is that the 2x4 breakaway connector (called EPS12V I believe) that splits into two 2x2 connectors is probably compatible with this receptacle. One of the two 2x2 pieces of the connector should fit into the eGPU’s power receptacle, and the other won’t. If it fits, it is probably the right connector. If two of the wires going to that connector are yellow, and two are black, then it’s almost certainly the right connector.

    You may have multiple of these 2x4 breakaway connectors. If so, they should behave identically, and you can break up any of them and try to fit the pieces into the ATX12V receptacle.

    List of ATX power supply connectors: https://en.wikipedia.org/wiki/Power_supply_unit_(computer)#Connectors (without images, unfortunately.)

    Don’t forget about the big 20-pin or 24-pin main ATX motherboard power connector. Your second power supply, since it is non-modular, will need something to simulate the motherboard’s power button. That’s can be as simple as a switch between the PS-ON wire (green) and any ground wire (black). But hopefully your eGPU has a place to plug in the ATX motherboard power connector, and handles that on-off switching for you.


  • If you are Microsoft, then yeah. You’d go to jail when a Windows vulnerability is found.

    In all seriousness though: it would be more likely to be just a civil penalty, or a fine. If we did want corporate jail sentences, there are a few ways to do it. These are not specific to my proposal about software vulnerabilities being crimes; it’s about corporate accountability in general.

    First, a corporation could have a central person in charge of ethical decisions. They would go to prison when the corporation was convicted of a jailable offense. They would be entitled to know all the goings on in the company, and hit the emergency stop button for absolutely anything whenever they saw a legal problem. This is obviously a huge change in how things work, and not something that could be implemented any time soon in the US because of how much Congress loves corporations, and because of how many crimes a company commits on a daily basis.

    Second, a corporation could be “jailed” for X days by fining them X/365 of their annual profit. This calculation would need to counter clever accounting tricks. For example some companies (like Amazon, I’ve heard) never pay dividends, and might list their profit as zero because they reinvest all the profit into expanding the company. So the criminal fine would take into account some types of expenditures.