How should I handle tasks that require several hours? I’ve been distracted a bit.
How should I handle tasks that require several hours? I’ve been distracted a bit.
Hello everyone, this is my little chat. Sometimes I get stuck during an upgrade – it took hours to fetch the files, and I fell asleep while checking. That was really frustrating. The same thing happened when using the password approval. At times the option to add the passwd appeared after hours, and honestly, I often drifted off during this long process. But it turns out updating is actually quite challenging for me. What should I do? My friends suggested some workarounds. Well, they mentioned using a specific command: yay -Syu --noconfirm. On first look, it seems like a good idea. But wait – there was another issue with the password. After hours of work, I didn’t actively monitor it anymore. How can I handle this? To be clear: Can I combine these two problems somehow?
Options:
a) Sure – try sudoloop
b) Yeah, use sudoloop and save...
The main problem came from the output during the upgrade of my Arch-based system. See the logs below. All updates went smoothly after a few steps.
Building the image from preset: /etc/mkinitcpio.d/linux.preset → default config used
Starting build hook: base → udev → autodetect → modconf → block → keyboard → consolefont (no font found) → resume
Warning: consolefont missing → resume
Running build hook: filesystems → fsck → module dependencies generated → zstd-compressed initcpio image created successfully
Building image from preset: /etc/mkinitcpio.d/linux.preset → fallback config used → successful update
After that, system updates continued without issues. I also checked for outdated modules and found several packages needing attention. It’s a bit messy, but the process is now more efficient.
Please let me know your thoughts – what do you think?