Install and run "btop".
You could scroll down to the screenshots on the GitHub page, but I had a friend recommend btop to me and seeing it for the first time running on my own machine was an experience. Highly recommend.
Jordan_U
joined 1 year ago
10 year old bug?
What are they talking about, that bug report is from 2014‽
... Fuck
One key problem with forced arbitration clauses is that company chooses and pays the "neutral" arbiter, who is inevitably biased against the consumer.
More than a decade ago a user came into #ubuntu-server on Freenode (now libera.chat ) and said that they had accidentally run "rm -rf /* something*" in a root shell.
Note the errant space that made that a fatal mistake. I don't remember how far it actually got in deleting files, but all of /bin/ /sbin/ and /usr/ were gone.
He had 1 active ssh connection, and couldn't start another one.
It was a server that was "in production", was thousands of miles away from him, and which had no possibility for IPMI / remote hands.
Everyone (but me) in the channel said that he was just SoL and should just give up.
I stayed up most of the night helping him. I like challenges and I like helping people.
This was in the sysv-init (maybe upstart) days, and so a decent number of shell scripts were running, and using basic *nix commands.
We recovered the bash binary by running something along the lines of
bash_binary_contents="$( </proc/self/exe)"
printf "%s" > /tmp/bash
(If you can access "lsof" then "sudo lsof | grep deleted" will show you any files that are open, but also "deleted". You may be surprised at how many there are!)
But bash needed too many shared libraries to make that practical.
Somehow we were able to recover curl and chmod, after which I had him download busybox-static. From there we downloaded an Ubuntu LiveCD iso, loop mounted it, loop mounted the squashfs image inside the iso, and copied all of /bin/ , /sbin/ , /etc , and so on from there onto his root FS.
Then we re-installed missing packages, fixed up /etc/ (a lot of important daemons, including the one that was production critical, kept their configuration files open, and so we were able to use lsof to find the magic symlinks to them in /proc/$pid/fd/ and just cp them back into /etc/.
We were able to restart openssh-server, log in again, and I don't remember if we were brave enough to test rebooting.
But we fucking did it!
I am certainly getting a lot of details wrong from memory. It's all somewhere at irclogs.ubuntu.com though. My nick was / is Jordan_U.
I tried to find it once, and failed.
It's at least gotten a bit better.
There was a time when Photoshop and other programs used a copy-protection scheme that overwrote parts of grub, causing the user not to be able to boot Linux or Windows.
They knew about it, and just DGAF. I don't remember their exact FAQ response, but it was something along the lines of "Photoshop is incompatible with GRUB. Don't dual boot if you use Photoshop."
Grub still has code for BIOS based installs that uses reed-solomon error correction at boot time to allow grub to continue to function even if parts of its core.img were clobbered by shitty copy protection schemes for Windows software.
I was helping you there and asked you to back up configs and post some information.
Once you've done that I think actually getting things back the way they should be will go fine.
I didn't know TWAIN, so I looked it up and am glad I did:
TWAIN: Technology Without An Interesting Name
Like me, that user wants to use ISO-8601 format for dates.
I didn't see that option in the screenshot. Anyone know if that's possible in this Beta?
Sorry again. I wrote this last comment (and this one, TBH) from my phone and "--iso=s" should have been "--iso-8601=s" . I've edited my comment and the command should now work (Making a backup of your grub.cfg containing the date, to the second, in the filename. I did that to hopefully avoid you running the same command again after trying some fixes and accidentally clobbering your backup).
Ahh, sorry.
For Fedora it looks like the default /etc/default/grub looks like this:
GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rhgb quiet" GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG=true
( Taken from https://discussion.fedoraproject.org/t/how-to-regenerate-etc-default-grub/72677/9 )
If you're using LVM / LUKS you may need additional kernel parameters, like resume=... for suspend to disk to work properly.
Please, before doing anything else, post the output of the following:
cat /proc/cmdline
And make a backup of your existing grub.cfg with:
sudo cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg-backup-$(date --iso-8601=s)
Also, be sure that you have a LiveUSB on hand. You don't want to be SOL if we break something and can't boot again without fixing it first.
What version of Ubuntu are you using?
What is the output of the following command?:
dpkg -l | grep grub
If you urgently want your grub menu to default to the first entry that can be done first, but unless that's needed I'd prefer to get to the root of the problem(s) and get a proper fix.
view more: next ›
Just keep "hollywood" running in another terminal at all times.