• 1 Post
  • 345 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle







  • But even without , the arch way isn’t insane either: when something kernel-related breaks, boot with a live system on USB and fix it.

    That is not a replacement for “arrow-key down during boot to select an older kernel”.

    I have a server with a RAID card and the kernel at some point introduced a bug with the driver that prevented that server from booting. So I select the older kernel at boot, get the system up and running, mark that kernel as the default until the bug is fixed.

    It’s not crazy, it doesn’t take long, you just need to know how the system works.

    I know how the system works very well thankyouverymuch. But that’s an insane option when having multiple older kernels is so easy to do and common.



  • Don’t feel silly! It’s a common mistake, easy to fix, and easy to make. I’ve seen experienced developers do something similar.

    It seems you’ve resolved the issue at this point but remember you can always run commands by specifying their full path as well (should you end up in a similar situation). All the PATH variable does is set the default locations to search when you don’t provide a full path to a binary.

    e.g. /bin/ls or /usr/bin/vi





  • The drive got whipped [sic]

    Oh, it was just sitting there and “got wiped”? Not because of a command you ran?

    Sorry to be snarky but when asking for help you need to provide what you did, what error message you see now or what you expect to happen and what is actually happening. Also what OS you’re using would be helpful.

    Presumably you should be able to get the drive back into a usable state - but I’m not familiar with SAS drives.