How long will the DC 1 be supported with OS & Security updates?
I like how this St Louis Fed post blames people for banks’ failings.
Flip it around. Banks irresponsibly created way more claims for gold than they had gold, kept defaulting, and lost trust. So the government made gold illegal to own for like 40 years.
There was no “shortage” of gold in the Great Depression. There was an excessive amount of fraudulent promises for gold, made by commercial banks and central banks.
https://www.stlouisfed.org/open-vault/2017/november/why-us-no-longer-follows-gold-standard
“It’s not our fault! Stupid peeeeeoopleeee!!!”
I feel your pain bro. Have you tried the swipe typing feature? When my fingers go retarded I switch to swiping for a bit and move on
Gotta save that 10 mins bruh
Good luck with your troubleshooting.
I don’t have any advice for you since I’ve not dealt with this specifically, but out of curiosity asked Llama 3.1 405b.
———————————————
The error message "timed out waiting for the udev queue being empty" during boot on a Linux server is usually related to the udev daemon, which is responsible for managing device events and handling device initialization.
When the system boots, udev is responsible for creating device files and initializing devices. If the udev queue is not empty within a certain time limit (usually 30 seconds), the system will timeout and display this error message.
There are several possible causes for this error:
1. **Slow or failing disk**: If the disk is slow or failing, it can cause the udev queue to timeout.
2. **Incorrect or missing device drivers**: If the device drivers are not correctly installed or are missing, it can cause the udev queue to timeout.
3. **udev configuration issues**: Misconfigured udev rules or incorrect udev settings can cause the udev queue to timeout.
4. **Resource constraints**: Insufficient system resources, such as RAM or CPU, can cause the udev queue to timeout.
5. **Filesystem issues**: Filesystem corruption or issues can cause the udev queue to timeout.
To troubleshoot this error, you can try the following:
1. **Check the system logs**: Check the system logs (e.g., /var/log/syslog or /var/log/messages) for any errors related to udev or device initialization.
2. **Run udevadm info**: Run the command `udevadm info --export-db` to check the udev database and look for any errors or issues.
3. **Check the disk**: Check the disk for any errors or issues using tools like `fsck` or `smartctl`.
4. **Verify device drivers**: Verify that the device drivers are correctly installed and configured.
5. **Increase the udev timeout**: You can increase the udev timeout by editing the `/etc/udev/udev.conf` file and adding the `udev_timeout` option.
Thanks for that!
nostr:npub1c4vv0nrfh0drcfchs2mndw4uvjkd9k393v20x4kme2txev9hhz0qw4cqk7 what would it take for you to add this to your functionality?
That’s a chonker bro
And that joint is huge too!
🫶 hahah hope you guys are having fun
If someone paid you 1 whole bitcoin to never drink it again, would you?
